yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] ivoe:
id suggest being extremly careful i just noticed how much stuff broke when using this.. phone stoped working messeges broke when starting new rom on internal.. lost messages only ubuntu can pick up and alot of stuff.. wish there was a dual boot id feel more safer using it

its a great tool if you get it working but i mean id only ever flash a new rom to check out stuff real fast before going through and making it my main or not
[T-Mobile, Samsung Galaxy SIII] Tomb77:
I totally disagree. This recovery is solid as long as you follow the instructions. I have been running it since it was shared and none of my roms are broke in any way because of it. The most annoying quirk that I noticed is picture filing and that sd transferring seems to only work on internal. I have had absolutely no issues with any normal function such as calling messaging or apps. I say this because it is a great tool for checking of t other ROMs without backing up; you can jump to each ROM to ensure the function or setup you like will be there for you within seconds or a minute.

Edit: sometimes these this get frustrating in getting the hang of them. When you want I am sure you can get some more in depth help on here. Whoever likes to flash will really like this.
[T-Mobile, Samsung Galaxy SIII] :
I am using Multiboot 2.11 and normally just create extra ROMs on my internal SD card but I backup my apps to my external SD card. I'm running into an issue where my backup program cannot access my external SD card for the files even though I can access the data through a file explorer app. Has anybody else experienced this issue? Just wondering how you got around it?

Thanks.
[T-Mobile, Samsung Galaxy SIII] tokenpoke:
Are you dualbooting a KitKat ROM? New security features keep most apps from accessing folders not made by the app its self.

Many people discovered this while trying to use titanium backup.

Easy solution is to back up a single app in KitKat (any app) and use a root file explorer to move your other backups to the new folder created by titanium backup.

Or... Simply copy the apks you want to install again using a root explorer to a common use folder and just installing from there.

Only issue is you loose app data and can't batch install.
[T-Mobile, Samsung Galaxy SIII] :
Even happens on JB ROMs.

--EDIT-- I noticed on the ATT thread that they've run into the same issue. There's a new version for ATT that addresses the problem. I'm going to try to investigate that version.
[T-Mobile, Samsung Galaxy SIII] kristibaee:
Same apps

I looked around the thread and it doesn't look like this question's been answered.

If I have multiple ROMs, do they all have the same apps? Or do I need to install the apps separately on each ROM?
[T-Mobile, Samsung Galaxy SIII] Tomb77:
The ROMs are completely independent of each other.
[T-Mobile, Samsung Galaxy SIII] :
Well, the good news is that the new version of the recovery fixes the sd card issue. I've got the asserts changed on the AT&T version to flash to our device - I just need a place to put it. :)
[T-Mobile, Samsung Galaxy SIII] koz:
I'm a bit confused - how is this recovery different from TWRP? I thought TWRP already has multiboot? I haven't used either yet, so I'm trying to learn the differences before I choose one.
[T-Mobile, Samsung Galaxy SIII] Tomb77:
I don't see anything on the TeamWin site that says they do and never seen it on any versions other than this one. They have backups but not multiboot. Are you referring to backups?
[T-Mobile, Samsung Galaxy SIII] koz:
No, whatever it was I was reading made me think that TWRP already had multiboot and that this recovery added additional features. Thanks for the clarification.
[T-Mobile, Samsung Galaxy SIII] koz:
I finally installed the recovery - really great work. I didn' t have much time to explore it, so I went back to Philz CWM. This morning, I tried to reinstall this recovery to play around with it a bit more, and this was the error msg I got:

assert failed: getprop("ro.product.device") == "d2tmo" || getprop("ro.build.product") == "d2tmo" E:Error in /storage/sdcard1/download/d2tmo-twrp2.7-mb-v2.11.zip

(Status 7)

I can't seem to get the zip to install. Any ideas what's going on?

EDIT (Solution): Flashed back to stock recovery>reflashed Philz recovery (this step probably is not necessary)>Flashed Multiboot...success
[T-Mobile, Samsung Galaxy SIII] tokenpoke:
Same file?

I'm no dev but that looks like you are trying to install the tmobile version on a non tmobile/metropcs phone.
[T-Mobile, Samsung Galaxy SIII] koz:
Yes, same file. I even downloaded it again to verify. And it's definitely a tmobile version and tmobile phone. I may have to flash a stock recovery and then try it again.
[T-Mobile, Samsung Galaxy SIII] tokenpoke:
From what I can see that's the best bet to fix it.
[T-Mobile, Samsung Galaxy SIII] koz:
Usb-Otg Issues

Has anyone had issues with usb-otg mounting for this recovery? I'm noticing connection issues with my usb drives not mounting. I've tried one 8gb (generic) and 3 (PNYs) - one 32gb (2.0 usb) and two 32gb (3.0 usb). The 8gb mounts no matter what. The others (especially the 3.0 usb), are very flaky - sometimes they will mount, but usually not. All of them will mount when the phone is booted up to system and is fully operational - I have no problems using them. It's only when I'm in recovery. Anyone else with usb drive connection issues?
[T-Mobile, Samsung Galaxy SIII] mcgrabowski:
Anybody want to share some experiences getting TW based ROMs to boot as a secondary? I've been able to boot Dandroid ( a 4.3 based ROM ) but haven't had any luck getting Likewise LT to boot ( a 4.4.2 S5 port). I've tried a few things with different size partitions and on internal and external sdcards, but haven't been able to get it. Anyone else tried? Any successes?
[T-Mobile, Samsung Galaxy SIII] tnt8902:
I tried it also with touch wiz, especially with S3rx. The aroma stops at 43% and says it finished, when I boot the rom in recovery it doesn't switch over. The old recovery was OK but the new recovery update broke something. I tried vice versa tw|aosp aosp|tw . nothing stayed on 2nd boot, always reverted back to default ROM
[T-Mobile, Samsung Galaxy SIII] mcgrabowski:
I have AOSPA installed as my primary and haven't had any trouble booting any other AOSP ROMs. But so far with TW ROMs, I've only been able to get Dandroid to boot. The only other TW ROMs I've tried so far have been the kit kat sprint port and the likewise s5 port. Both appear to install fine, but get stuck on the boot logo and never finish booting.
[AT&T Samsung Galaxy Note II] BR7fan:
I tried this method and I got a Knox warranty void http://forum.xda-dev...555&postcount=1 . Not OP's fault,i'm sure it was my error.

Being I got the void anyway,I wiped and installed KIES_HOME_I317UCALJ2_I317ATTALJ2_215287_REV04_user _low_ship.tar.md5. It downgraded my BL to 4.1, then I rooted and flashed Slimbean 4.3 (with TWRP) with success. It counted against my binary download,but didn't trip knox again (Dont know if KNOX trips more then once). The only thing I did was used root explorer and deleted all Knox. Then I froze what was left with Titaniam.

EDIT

OK now I successfuly flashed the latest Slimkat with no problems what so ever. Still no trouble with Knox or bootloader. I have all backups of what I had installed if devs want to look and confirm what I have said is true.

Is this supposed to be possible or was people scared of tripping knox ????
[AT&T Samsung Galaxy Note II] dicksteele:
Link didn't work, so I couldn't see what you did....

You can check to see if Knox is tripped by turning off phone.

Once it’s off, you need to press this button combination: volume down, power button and home button. Keep them pressed until the download mode shows up. Once you’re there, you will be required to press volume up to enter the download mode or volume down to cancel and reboot the device. Press Up.

Upper left will show flash counts and last line will show if Knox is tripped.

Also to check which bootloader you are on:

search in play store - android system info - look in buildinfo

also there is an app called info - look in os

I should be in bed now..... I think this is right, open Android Terminal; type getprop ro.bootloader. That should tell you what bootloader you are on also.

I'm curious....
[AT&T Samsung Galaxy Note II] BR7fan:
13i7ucubmk6

Knox is tripped. It happened when I was trying to downgrade using one of members method. But I did it by just installing the old att firmware

xdaforums.com/showthread.php?t=2502464
[AT&T Samsung Galaxy Note II] dicksteele:
Interesting. Which firmware was it?
[AT&T Samsung Galaxy Note II] BR7fan:
_i317attalj2_215287_rev04
[AT&T Samsung Galaxy Note II] Ladyfinesse08:
this is the problem I've been having: Copy and pasted from a thread I created.

So I have a AT&T Samsung Galaxy Note 2 that as of 5 hours ago was completely stock and running android 4.3 (the official one from AT&T). I got bored last night and decided I wanted to root my phone (something I hadn't yet done in the entire year I had my phone). So I looked up how to root, read the instructions all the way (I thought my research was complete). I rooted using the CF auto method. After doing that I flashed TWRP using ODIN. I also downloaded Titanium Backup, Rom Manager & My Backup Root. I tried to use all three of these applications to make a backup of my device so that I could flash the custom Rom I wanted without losing all my information. That is when my troubles began.

Whenever I tried to access any of these apps I got a pop up saying Unfortunately, SuperSU has stopped and a notification stating An attempt to access a secure area on your phone without authorization has been blocked. None of the apps would run either and just kept freezing or loading forever.Thinking I'd done something wrong I repeated the root process all over again. I still kept getting the same notifications though. I typed in the unauthorized access notification message into google and discovered about Knox. Doing some tinkering of my own I went to settings (more tab)>>security>>device administrators>> unchecked knox>>deactivate. After deactivating Knox I once again tried to gain root access and had no success. I followed the advice from previous threads and tried to change all Knox.apk files to knox.apk.bak using Explorer, I downloaded Android terminal and tried to delete knox via the command line su pm... That also did nothing. I went to the market and tried to download the SuperSU app by CHAINFIRE, it wouldn't work as it already says the app is installed but offers me no updating options. I also downloaded the Update SuperSU zip file and tried to flash it. My phone wont boot into recovery though so that hasn't gotten me anywhere. Downloaded Rom Manager and GooManager to try to get into recovery mode and still no success. later flashed philz_touch via ODIN as people who had similar problems had posted about it working for them. Didn't work for me. Flashed TWRP again using ODIN and am now just scratching my head trying to figure out how to fix this issue.

I'm personally not worried much about the warranty stuff but am more concerned with the fact that I can't root my phone. All I want is to be able to load a custom rom (MIUI v5) onto my phone. Any and all help would be greatly appreciated.... If you've seen someone else with an issue like mine please just redirect me to the proper thread then.

p.s. I also tried running the root verify app and it got stuck on a loading page.

When I power my phone off and boot into recovery mode (or whatever its called) my stats read as:

ODIN MODE

Product name: SGH-I317

Custom Binary Download: Yes (7 counts) - this is from all my attempts to reroot and flash different recoveries

Current Binary: Custom

System Status: Custom

Knox Warranty Void: 1

AP SWAEV: A2
[AT&T Samsung Galaxy Note II] dicksteele:
I think I'm tracking.....

First try going to settings, More, them go to application manager.

Remove super su. Go back to Google Play and download latest supersu.

Superuser executable does not get deleted when removing supersu app

See if that works
[AT&T Samsung Galaxy Note II] BR7fan:
or flash download.chainfire.eu/282/SuperSU/ SuperSu with TWRP
[AT&T Samsung Galaxy Note II] dicksteele:
That looks better.

I looked at updater script and it deletes old stuff first before installing.
[AT&T Samsung Galaxy Note II] Ladyfinesse08:
Thanks so much for your help. I tried doing what you said. When I go to SuperSU application under application manager it won't allow me to reomove it. All I can do is Turn it OFF. When If I go to the play market after turning it off the only option I get is to enable it again. Looking under App Info though it's showing that I'm on version 1.93 of SuperSu. I think from all the stuff I've been reading I'm supposed to be on version 1.95.

As for flashing it your TWRP I can't because I can't load into recovery mode with TWRP. The only thing thats working for me is ODIN. Not sure if there's a way to flash from ODIN or not but I personally don't know of one (I'm new to ODIN).
[AT&T Samsung Galaxy Note II] dicksteele:
http://goo.im/devs/OpenRecovery/t0lteatt/openrecovery-twrp-2.6.3.1-t0lteatt.img.tar

Here's a copy to flash in ODIN. If you can't boot into recovery after this, there are other things we can try from ODIN.
[AT&T Samsung Galaxy Note II] dicksteele:
K. I understand now. I think.

You were on MK6, the 4.3 OTA bootloader.

You tried flashing seanz MJ4 4.3 Leak bootloader and Knox didn't appreciate that.

You could still ODIN back to the LJ2 because it doesn't include a bootloader.
[AT&T Samsung Galaxy Note II] BR7fan:
I dont want to falsh back. What had me puzzled is that I thought that with knox you couldnt flash any rom because of secure bootloader. I am able to flash what ever I want with out any extra steps. Its like it was before knox came around.
[AT&T Samsung Galaxy Note II] dicksteele:
Knox wasn't/isn't as restrictive as we imagined. It's more of an annoyance.

Biggest annoyance is not being able to flash older bootloaders, and the easily viewable notice that Knox had been tripped.

We've had it long enough to know our limitations

Man's got to know his limitations.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] h_rladeveze:
Hello. I am in desperate need of help. I left my blueangel charging in the craddle last night only to find it this morning with a blank screen. After trying to soft and hard reset it without any success all it shows is the blue imate startup screen and the software versions in the bottom right hand corner of the screen. I would appreciate any advice on the matter.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] vastloper:
sounds like rom problems

first try remove battery for couple of minutes

also remove sdcard (if any inserted)

replace battery and reset device

if this won't help

Only thing you can try is to update the rom
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] h_rladeveze:
I would also appreciate the contact details for a service center in spain. I have an Imate PDA2K bought in the UAE.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] h_rladeveze:
Thank you vastloper, I have tried that several times but makes no difference. On top of everything else I cant update the ROM as ActiveSync will not recognise the device, basically it will not connect to any other device. Any clue?
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] xplode:
You do not need activesync to upgdate your rom, you need latest rom no matter which provider or version, reflas and then connect via activesync
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] starik:
why would ROM become defective all of a sudden? makes no sense.

take out the main battery and leave it for a few hours, (or overnight), so that the backup battery drains.

Then reassemble the phone - it should perform a hard reset on its own.

If this doesn't work, u may have a hardware problem.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] imatrix:
try this for whoever get stuck at boot screen or in bootloader mode

1. Download mtty v1.42 from http://files.pdamobiz.com/ROMs/XDA/mtty1.42.rar

2. Stop ActiveSync, by Task Manager (press Ctrl + Alt + Delete)

kill two processes rapimgr.exe and wcescomm.exe

3. put your device into Bootloader Mode by pressing Power + Record Button and Soft Reset.

4. Run mtty (from downloaded) Choose WCEUSBSH001

5. type "set 14 0" without the quotes to tell bootloader to boot the OS after reset.

6. type "task 28" to get your device formatted

7. type "task 0" to ask your device reboot

8. take the device out of the cradle, and manually reset it if it does not do that already.

good luck.

imatrix
[Samsung Galaxy Exhibit 4G] det0xx:
Greetings, i was wandering if there were any devs out there that would like to help me out with some questions about building custom roms and set up, etc,

.

Once im able to get a full comprehensive knowledge i'm hoping to contribute to this community as it has contributed to me.

My first question is what are pros and cons from building from a Virtual machine compared to booting up an actual os?

Also, what linux OS is recommended and why?
[Samsung Galaxy Exhibit 4G] jfbs:
I use both native and VM. Only difference you'll likely notice is updating the kernel on VM will take an extra step depending on the configuration. VM's will also have slightly less resources allocated than host, but will hardly notice with multi-cores and multi-threading.

Ubuntu 12.04 is good for compiling android since there is plenty of support and documention, however subjective. Try a VM first to find which distro compliments you.
[Samsung Galaxy Exhibit 4G] det0xx:
thanks for the reply, i want to try native but idk how it would affect my PC. probably not in a harmful way. and well i was planning to use this guide i found on xda but idk if it was reliable? http://soupdawg.wordpress.com/2014/...4-04-lts-trusty-tahr-to-compile-android-roms/

either way im more confortable with ubuntu.

what would be a ood guide to follow or what would i need o learn first before anything?
[Samsung Galaxy Exhibit 4G] smartguy044:
I use native Linux not a vm. If you are new to Linux I would say use ubuntu since like jfbs said there is a lot of documentation for using it. The guide seems to include everything you'll need to compile.

[MENTION=4657373]jfbs[/MENTION] when you get time pm me I have a couple of questions for you
[Galaxy Note 3 Q&A, Help & Troubleshooting] tclocki:
So I tried using the s4 i9500 boot sound to get rid of the chinese boot sound of my dual sim note 3, and it worked! My question now is if someone has tried using the boot screen say from a snapdragon s4 to a snapdragon note 3. Just want to check if someone has a similar experience...
[Nexus 5 Q&A, Help & Troubleshooting] slider112:
Hey guys,

Dumb question that I'm pretty sure I know the answer to, but I'll ask anyway just to double check:

Stock, rooted N5: Can I use TiBu to uninstall Google apps that are pre installed as system apps, then turn around and install those same apps through the Play Store as regular user apps? Any ill effects to this? Primarily looking at Google Music, so I can then Greenify it once it's installed as a regular app. Everything I know tells me this is fine but it never hurts to ask, right? May do the same with Keep, Currents, G+, etc...

Thanks in advance :D
[Nexus 5 Q&A, Help & Troubleshooting] GUGUITOMTG4:
Yep, you can uninstall Google apps, like music, plus, magazine, etc... and download as user apps, then greenify them.

I removed some them on day 1 when was on stock and now whenever I flash a new Rom with Gapps. Just be careful with what you choose. I recommend to first back them up then if everything is fine, delete backups.
[Nexus 5 Q&A, Help & Troubleshooting] slider112:
Great, thanks for confirming. Just gonna stick to the basics, but will back up through TiBu first as a precaution. Google Music was at the forefront because at times it runs in the background when bluetooth is turned on. It was either go this route or purchase the full version of Greenify so I could hibernate all system apps. Greenify is well worth the support, but would rather just de-clutter things this way.

Thanks again, much appreciated. :good:
[Nexus 5 Q&A, Help & Troubleshooting] danarama:
Don't delete. Freeze. There is nothing to gain by deleting
[Nexus 5 Q&A, Help & Troubleshooting] TheReverend210:
You lose OTA ability if you outright delete.

Like was stated, freeze them. If you were going to uninstall them through Titanium anyway.....
[Nexus 5 Q&A, Help & Troubleshooting] slider112:
So freeze Google Music as a system app, then install as a user app from the play store? Seems kind of redundant. I understand that logic and have followed that for other system apps in the past on other devices, but is that really the preferred method if I'm only dealing with Google apps that were installed as system apps from the factory, only by default, and can be easily reinstalled via the play store? Oh, and I'm running Franco's kernel so the OTA capability ship has already sailed anyway... :D
[Nexus 5 Q&A, Help & Troubleshooting] danarama:
Why would you then install it as a user app? System apps that are also available in play can still be updated via play anyway.
[Nexus 5 Q&A, Help & Troubleshooting] slider112:
Yes, I know that. So I can greenify it. Google Music will run in the background once bluetooth is turned on. Can't greenify system apps with the basic app, so for that particular app I think this would be the easiest method.
[Nexus 5 Q&A, Help & Troubleshooting] danarama:
Ah well, yep. Non-donators are forced to do weird things.
[Nexus 5 Q&A, Help & Troubleshooting] slider112:
Lol. Nothing weird about it. Worked fine. Google apps really shouldn't be installed as system apps if they're available in the play store. The user should have the choice of what they want and don't want. Easily corrected.
[Nexus 5 Q&A, Help & Troubleshooting] danarama:
They do. Its called "custom rom"
[Nexus 5 Q&A, Help & Troubleshooting] slider112:
They also have "titanium backup". Uninstalled. Done. "Custom roms" aren't for everyone. I've run plenty since my original droid days and just never use half the features included. I want rooted stock, and I have it. Thanks for everyones input.
[Nexus 5 Q&A, Help & Troubleshooting] danarama:
Yep. Can get custom roms based on stock that have skeleton gapps. To answer your statement earlier

"Google apps really shouldn't be installed as system apps if they're available in the play store"

Well yes they should as that is where they are designed to be. They are on the play store to allow updating outside the scope of OTA.

And of course it's your prerogative to remove apps as system apps and make them user apps, but I do get the feeling you're only doing it to continue using greenify without donating. But then again, it's none of my business whether you donate or not.