Getting the same notice running PAC man. Using goo is so convenient, guess I'll use adb
Sent from my SCH-I605 using xda premium
Just flashed it in recovery itself and worked without a problem
Getting the same notice running PAC man. Using goo is so convenient, guess I'll use adb
Sent from my SCH-I605 using xda premium
Seems to be working well for me so far!
Quick question.. I've installed AOSPA and I'm trying to get my SD card to FAT32 without an sd card reader, I'm assuming Wipe External Storage formats to exFat? I'm having the same ASOP SD issues after trying it.
Seems like i got an issue i cant find the answer too.
Everwyhere in touchwiz, the external sd card is referred to as extSdCard, but in TWRP it's referred to as external_sdcard. So when I use goomanager and say select a rom to flash with it, including backup, it wont do it because it doesnt recognize "extSdCard".
How can this be fixed?
I tried putting external_sdcard in goomanager as the path but it doesnt work.
Sorry I don't have the ability to fix it for you. Please try flashing in twrp directly.
I recently started having a weird issue. I am running the latest TWRP build.
I flashed a ROM (aroma based) and after the flash finished, I hit the finish button and it exited back out to TWRP, then the screen blanked out and the phone stopped responding. If I hit a button, the vibration/haptic feedback motor would vibrate, but no other response. I had to pull the battery.
I rebooted into recovery and made sure to wipe everything and reflashed the ROM to make sure it flashed properly. It flashed fine and I wiped the caches and then went to reboot.
Then a screen popped up telling me there was an issue with root and that it needed to fix root permissions. I selected "fix root" and it rebooted and everything runs fine.
But now I always get this warning after a flash... even if I select "don't fix root", the ROM runs fine and root seems to work.
I tried reflashing TWRP, but I still have this issue.
I have the same thing happen after every flash but this has been going on since before the latest update.
Sent from my SCH-I605 using xda app-developers app
I have the same thing happen after every flash but this has been going on since before the latest update.
Sent from my SCH-I605 using xda app-developers app
I recently started having a weird issue. I am running the latest TWRP build.
I flashed a ROM (aroma based) and after the flash finished, I hit the finish button and it exited back out to TWRP, then the screen blanked out and the phone stopped responding. If I hit a button, the vibration/haptic feedback motor would vibrate, but no other response. I had to pull the battery.
I rebooted into recovery and made sure to wipe everything and reflashed the ROM to make sure it flashed properly. It flashed fine and I wiped the caches and then went to reboot.
Then a screen popped up telling me there was an issue with root and that it needed to fix root permissions. I selected "fix root" and it rebooted and everything runs fine.
But now I always get this warning after a flash... even if I select "don't fix root", the ROM runs fine and root seems to work.
I tried reflashing TWRP, but I still have this issue.
Hmm, not sure about aroma, but I wonder if your ROM is copying su over every boot. What rom are you using?
You might want to ask the aroma dev about your issue.
Every ROM... I have been switching and checking them all out.
It makes me wonder if something happened during that glitch that caused this.
Was even considering redoing root completely. Not sure if I should unroot to stock and start over or start in the middle somewhere.
Just to toss my hat into the pile. I'm getting the Superuser fix request every time I flash a ROM as well. Only happened since the 2.4.3.0 update.
Hmm, not sure about aroma, but I wonder if your ROM is copying su over every boot. What rom are you using?
You might want to ask the aroma dev about your issue.
Beanstown106 is telling people over in the [Rom] Jelly 'Beans' - Build 13 [03/18/13][Aroma][Fully Customizable][VRBMB1] thread that we shouldn't click "fix root". He says:
"make sure you dont hit fix root. that is a bug with the newest twrp and breaks stuff root is perfectly fine"
Does anyone here know what he means by "breaks stuff"?
for some reason when im trying to update the recovery in goo manager it is telling me my device is not supported. I am running Rootbox does anyone have any idea wat the problem here may be?
I had the same problem, except what was weird about it was that it backed up slimrom to extsd just fine but when I switched to beans 25 and tried to back up, no cigar
twrp rocks...can't wait to use for kitkat...if u needs more testers im down...if not i will patiently wait.
I saw a post online that the new 2.7 version was release, but when I go to the official pages, or through goo.im, its still 2.6.3. Is there an updated link anywhere for the latest?