Develop Bugs

[Q] flashed CWM via rom manager, now in recovery mode with android&red !

i just flashed cwm to my gnex with rom manager after rooting the phone (without unlocking the bootloader). when i try to boot into the recovery, i get this picture of an android with its chest open and an exclamation. i would assume that the recovery partition was not flashed correctly? are there any suggestions?
thanks for your help in advance!

That just means the recovery was not properly flashed, what you are seeing is stock recovery. Try again via rom manager, or do it manually using fastboot.

Your phone needs CPR.
iphone. helping computer illiteracy become popular since 2007.

pretty sure u need to unlock the boot loader to write a custom recovery
Sent from my Galaxy Nexus using xda premium

jasonpantuliano said:
pretty sure u need to unlock the boot loader to write a custom recovery
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Not true. If you have root, you are good to go.
@OP: the reason CWM is not sticking is because you updated your build with an OTA (or link). When you do this, the update adds 2 files to your ROM that re-flash the stock recovery on every reboot. You need to delete them and re-flash CWM.
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
Sent from my Galaxy Nexus using Tapatalk

efrant said:
Not true. If you have root, you are good to go.
@OP: the reason CWM is not sticking is because you updated your build with an OTA (or link). When you do this, the update adds 2 files to your ROM that re-flash the stock recovery on every reboot. You need to delete them and re-flash CWM.
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
thanks so much! managed to get itt to stick by getting rid of those.

joshtb86 said:
thanks so much! managed to get itt to stick by getting rid of those.
Click to expand...
Click to collapse
You still can boot into CWM Recovery without deleting or change the filenames..
Just before you want to boot into CWM recovery...from CWM App..clck flash recovery..after that click Reboot into recovery.. doing these 2 steps..you will get booting into CWM Recovery yet not losing the stock recovery..

hmanxx said:
You still can boot into CWM Recovery without deleting or change the filenames..
Just before you want to boot into CWM recovery...from CWM App..clck flash recovery..after that click Reboot into recovery.. doing these 2 steps..you will get booting into CWM Recovery yet not losing the stock recovery..
Click to expand...
Click to collapse
Yup, you can do that as well. But you would need to flash CWM every time.
Not sure why you are so concerned with having a stock recovery though. The "I want to be able to get the next ota" reason doesn't make any sense at all for these reasons:
1) The link for the next OTA update will show up on XDA before you get it. So in this case, you need either CWM or root to install.
2) Irrespective of whether you have a stock or custom recovery, you will receive notification of the next OTA update regardless. If you have the stock recovery, just click install. If you have CWM, start ROM Manager, install the stock recovery, and then install the update.
Sent from my Galaxy Nexus using Tapatalk

Rooting issue

I just ran into a problem when rooting. I unlocked the bootloader and flashed clockworkmod for GSM and then pulled the battery to reboot but it didn't wipe the phone so I'm not sure what to do. I have a 4.0.4 IMM761

a5pe4 said:
I just ran into a problem when rooting. I unlocked the bootloader and flashed clockworkmod for GSM and then pulled the battery to reboot but it didn't wipe the phone so I'm not sure what to do. I have a 4.0.4 IMM761
Click to expand...
Click to collapse
Why did you pull battery? Did you unlock and flash cwm manually?
Sent from my Galaxy Nexus using Tapatalk 2

The tutorial I'm watching said to. I am unlocking manually. So I figured out that once the phone reboots the recovery seems to be erased. I am able to flash the recovery and then immediately go into it but if I power off the recovery won't work and I end up with a dead android with a red triangle above it. I want to flash superuser also but I think I will still have this recovery issue if I am not mistaken?

a5pe4 said:
The tutorial I'm watching said to. I am unlocking manually. So I figured out that once the phone reboots the recovery seems to be erased. I am able to flash the recovery and then immediately go into it but if I power off the recovery won't work and I end up with a dead android with a red triangle above it. I want to flash superuser also but I think I will still have this recovery issue if I am not mistaken?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=25902280#post25902280´
checkout this post from efrant for an updated su.zip: http://forum.xda-developers.com/showthread.php?p=26356773#post26356773

bk201doesntexist said:
http://forum.xda-developers.com/showthread.php?p=25902280#post25902280´
checkout this post from efrant for an updated su.zip: http://forum.xda-developers.com/showthread.php?p=26356773#post26356773
Click to expand...
Click to collapse
I got impatient and ended up just flashing the recovery, superuser, and the AOKP ROM all in one go. Works for now! Hope my recovery is still there when I reboot tho...

[Q] New Android user :)

Hi guys, blackberry convert here.
So I just bought a "docomo" carrier nexus and it's been working good so far.
It's running 4.01 and recently got an update notification but when i tried to update it rebooted to a green android with its chest opened up and a red exclamation mark. I did some searching and noticed that happens when you try to OTA upgrade a rooted phone am I correct?
So my question is what are my options? Can I flash 4.04 ? Do i need to lock my bootloader and wipe back to stock? If I do.. Will i get the unpleasant surprise of everything being in japanese?
What about flashing a custom rom such as aokp? Will that upgrade me to 4.04 or not?
TIA

KrizTM said:
Hi guys, blackberry convert here.
So I just bought a "docomo" carrier nexus and it's been working good so far.
It's running 4.01 and recently got an update notification but when i tried to update it rebooted to a green android with its chest opened up and a red exclamation mark. I did some searching and noticed that happens when you try to OTA upgrade a rooted phone am I correct?
So my question is what are my options? Can I flash 4.04 ? Do i need to lock my bootloader and wipe back to stock? If I do.. Will i get the unpleasant surprise of everything being in japanese?
What about flashing a custom rom such as aokp? Will that upgrade me to 4.04 or not?
TIA
Click to expand...
Click to collapse
Yes that means its rooted, you should have a custom Recovery. If you power off and hold the volume keys and the power button then a green android will pop up use the volume keys and hit up twice to the "recovery mode" then hit the power button... then if you could tell me what you see? At the bottom it should say Clockworkmod 5.x.x.x or it will have TWRP which it will show TeamWin at first and a curtain will pull up. If you do have custom recovery you could just simply flash a custom ROM like AOKP for you device .

KrizTM said:
Hi guys, blackberry convert here.
So I just bought a "docomo" carrier nexus and it's been working good so far.
It's running 4.01 and recently got an update notification but when i tried to update it rebooted to a green android with its chest opened up and a red exclamation mark. I did some searching and noticed that happens when you try to OTA upgrade a rooted phone am I correct?
So my question is what are my options? Can I flash 4.04 ? Do i need to lock my bootloader and wipe back to stock? If I do.. Will i get the unpleasant surprise of everything being in japanese?
What about flashing a custom rom such as aokp? Will that upgrade me to 4.04 or not?
TIA
Click to expand...
Click to collapse
No, that doesn't happen because of root. Root has NO IMPACT WHATSOEVER on your ability to install updates OTA. It will happen if your recovery does not match your ROM.
You have a few options:
1) you can go to the "update" link in my signature, find the update for your build, and install it manually as per the instructions in that thread.
2) you can go to the "flash" link in my signature and flash stock (yakju) 4.0.4 as per the instructions.
3) you can flash a 4.0.4-based custom ROM.
Sent from my Galaxy Nexus using Tapatalk 2

efrant said:
No, that doesn't happen because of root. Root has NO IMPACT WHATSOEVER or your ability to install updates OTA.
Click to expand...
Click to collapse
UH YES it does... why do you think we get so many "broken android red exclamation mark!" threads started... because people who root tried to accept the OTA. OTA's require the stock Recovery to install... when it sees that thats been changed or something has been modified.. then it errors. Get it straight.

ÜBER™ said:
UH YES it does... why do you think we get so many "broken android red exclamation mark!" threads started... because people who root tried to accept the OTA. OTA's require the stock Recovery to install... when it sees that thats been changed or something has been modified.. then it errors. Get it straight.
Click to expand...
Click to collapse
Uh, excuse me... having root makes no difference. You get it straight. But you are right, having the wrong recovery (custom recovery or incorrect stock version) will give you that screen.
I've applied every single update on a rooted phone. Details in the update link in my signature.
Sent from my Galaxy Nexus using Tapatalk 2

efrant said:
Uh, excuse me... having root makes no difference. You get it straight. But you are right, having the wrong recovery (custom recovery or incorrect stock version) will give you that screen.
I've applied every single update on a rooted phone. Details in the update link in my signature.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Heh... i dont see people with just superuser and no custom recovery the two go hand in hand... which is why i say Root does to play a part. At least on certain devices.

ÜBER™ said:
Heh... i dont see people with just superuser and no custom recovery the two go hand in hand... which is why i say Root does to play a part. At least on certain devices.
Click to expand...
Click to collapse
Well, lots of users in the forums root and keep the stock recovery, but yeah, not as many as those who use a custom recovery along with root. That is why I make the distinction. Adding files to /system (which is what rooting does ) doesn't affect anything. Deleting or replacing system files does however.
Additionally, you can still update even with a custom recovery. Just put the update file in /sdcard, reboot into recovery and flash it. No difference than having it flashed by a stock recovery.
Sent from my Galaxy Nexus using Tapatalk 2

efrant said:
Well, lots of users in the forums root and keep the stock recovery, but yeah, not as many as those who use a custom recovery along with root. That is why I make the distinction. Adding files to /system (which is what rooting does ) doesn't affect anything. Deleting or replacing system files does however.
Additionally, you can still update even with a custom recovery. Just put the update file in /sdcard, reboot into recovery and flash it. No difference than having it flashed by a stock recovery.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Gotcha now that we are done bickering.. i hope the OP can find his way.

ycholish siempre
3) you can flash a 4.0.4-based custom ROM.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Is aokp a 4.04 based ROM? I keep refering to aokp because from what ive read its the best rom out there.
then if you could tell me what you see?
Click to expand...
Click to collapse
Well it tells me im on prime and that my lock mode is : unlocked. So i suppose i'm rooted.
So if i flash a custom 4.04 rom i'm all set for future upgrades? Or should I flash androids stock 4.04 and then flash a custom rom?
Thanks for the help guys .

KrizTM said:
Is aokp a 4.04 based ROM? I keep refering to aokp because from what ive read its the best rom out there.
Well it tells me im on prime and that my lock mode is : unlocked. So i suppose i'm rooted.
So if i flash a custom 4.04 rom i'm all set for future upgrades? Or should I flash androids stock 4.04 and then flash a custom rom?
Thanks for the help guys .
Click to expand...
Click to collapse
Aokp just has a bunch more options which is quite overwhelming especially for a new user such as yourself. I would suggest using CM9 first. Okay that means your boot loader is unlocked... I said you have to go into recovery mode... which when at the boot loader screen you use the volume keys and hit up twice it change from start to recovery mode in red. Press the power button and tell me if you see a cyan blue recovery or team win on a blue curtain that pulls up.
Sent from my Galaxy Nexus using xda premium

ÜBER™ said:
Aokp just has a bunch more options which is quite overwhelming especially for a new user such as yourself. I would suggest using CM9 first. Okay that means your boot loader is unlocked... I said you have to go into recovery mode... which when at the boot loader screen you use the volume keys and hit up twice it change from start to recovery mode in red. Press the power button and tell me if you see a cyan blue recovery or team win on a blue curtain that pulls up.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Ok. i did the recovery mode thing and it gave me the android with its chest open and a red exclamation mark thing again
What's going on?

Check my sig to get yourself on AOKP.

KrizTM said:
[snip]
Well it tells me im on prime and that my lock mode is : unlocked. So i suppose i'm rooted.
Click to expand...
Click to collapse
Ok, I think you are confusing things here:
(1) An unlocked bootloader
(2) Root
(3) A custom recovery
The three items above are completely separate. Having one does not mean the others, nor does one require any of the others. Just because your bootloader is unlocked does not mean your OS is rooted, nor does it mean you have a custom recovery.
KrizTM said:
So if i flash a custom 4.04 rom i'm all set for future upgrades? Or should I flash androids stock 4.04 and then flash a custom rom?
Click to expand...
Click to collapse
ONLY stock ROMs can receive OTA updates. If you want updates, you need to be running a stock ROM. Period.
If you want to run a custom ROM, you will either get updates from the developer, or you will need to flash an updated version of that custom ROM.
Again, don't confuse flashing an updated version of ROM (i.e., a complete ROM), vs updating a ROM (i.e., an incremental update).
KrizTM said:
Ok. i did the recovery mode thing and it gave me the android with its chest open and a red exclamation mark thing again
What's going on?
Click to expand...
Click to collapse
That screen IS the stock recovery. (FYI, to access the menu, you need to press vol up and power simultaneously and repeatedly).
I would suggest you follow the instructions here to flash the yakju 4.0.4 build (do all the optional steps in part D) and then you will be set for all future OTA updates. (And besides, it is always wiser to run stock for a while, so that when you switch to a custom ROM, you have a basis for comparison.)
If you want to run a custom ROM, download whichever ROM it is to your /sdcard.
No you must first flash a custom recovery. Do this:
Assuming you already have the drivers set up and you have fastboot.exe on you computer (instructions found in the link above), do the following:
1) Download CWM from here;
2) Rename the file to cwm.img, and make sure it is in the same directory as your fastboot.exe file;
4) Restart your device in fastboot mode and plug into computer;
5) Open a command prompt in the directory mentioned above and type: fastboot flash recovery cwm.img
6) Now you have a custom recovery. Use the volume buttons on your device to navigate to "recovery", and use the power button to select;
7) Wipe your device using the CWM menus;
8) Flash the ROM by using the CWM menus (something like flash zip or something).

efrant said:
Ok, I think you are confusing things here:
(1) An unlocked bootloader
(2) Root
(3) A custom recovery
The three items above are completely separate. Having one does not mean the others, nor does one require any of the others. Just because your bootloader is unlocked does not mean your OS is rooted, nor does it mean you have a custom recovery.
ONLY stock ROMs can receive OTA updates. If you want updates, you need to be running a stock ROM. Period.
If you want to run a custom ROM, you will either get updates from the developer, or you will need to flash an updated version of that custom ROM.
Again, don't confuse flashing an updated version of ROM (i.e., a complete ROM), vs updating a ROM (i.e., an incremental update).
That screen IS the stock recovery. (FYI, to access the menu, you need to press vol up and power simultaneously and repeatedly).
I would suggest you follow the instructions here to flash the yakju 4.0.4 build (do all the optional steps in part D) and then you will be set for all future OTA updates. (And besides, it is always wiser to run stock for a while, so that when you switch to a custom ROM, you have a basis for comparison.)
If you want to run a custom ROM, download whichever ROM it is to your /sdcard.
No you must first flash a custom recovery. Do this:
Assuming you already have the drivers set up and you have fastboot.exe on you computer (instructions found in the link above), do the following:
1) Download CWM from here;
2) Rename the file to cwm.img, and make sure it is in the same directory as your fastboot.exe file;
4) Restart your device in fastboot mode and plug into computer;
5) Open a command prompt in the directory mentioned above and type: fastboot flash recovery cwm.img
6) Now you have a custom recovery. Use the volume buttons on your device to navigate to "recovery", and use the power button to select;
7) Wipe your device using the CWM menus;
8) Flash the ROM by using the CWM menus (something like flash zip or something).
Click to expand...
Click to collapse
Awesome. That clears up a lot of things. Thanks a lot You're right. Gonna stick to stock 4.04 till I get better at this hehe.
Thanks

problem flashing clockwork mod t999....only Android system recovery opens

Hey, if anyhow could help that would be great. I followed ask the instructions to flash Clockwork mod on my t999. Odin recognized phone, i pda'd clockworkmod.tar file, it passed and rebooted. Then i held power up+home+power and entered Android system recovery. Have done a few times and i continue to get Android system recovery. Obviously my phone isn't rooted yet, just got it. Is there an alternate way to get clockwork mod or am i doing something wrong? Thank you, any help is much appreciated...
Jake

U need root to flash clockwork
Sent from my SGH-T999 using xda app-developers app

tructo said:
U need root to flash clockwork
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
but when i read the instructions on rooting the phone it says must install clockworkmod first through Odin. You know what, ill look over it again, thanks for your quick reply..Jake

tructo said:
U need root to flash clockwork
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Ok, i just read the instructions again and it won't be possible to get past step 3 then
1. Copy cwm_superuserv3.0.7.zip
2.power off the phone
3. Bout your phone into clockworkmod
So if you know a way i can root my phone without being clockworkmod, can you paste a link? Because it's telling me i need clockworkmod to root phone....thanks again

Check out MrRobinsons thread in development. Very easy!
Sent from my SGH-T999 using xda app-developers app

themadzionist said:
Hey, if anyhow could help that would be great. I followed ask the instructions to flash Clockwork mod on my t999. Odin recognized phone, i pda'd clockworkmod.tar file, it passed and rebooted. Then i held power up+home+power and entered Android system recovery. Have done a few times and i continue to get Android system recovery. Obviously my phone isn't rooted yet, just got it. Is there an alternate way to get clockwork mod or am i doing something wrong? Thank you, any help is much appreciated...
Jake
Click to expand...
Click to collapse
Have you installed recent LH2 OTA update? This is a known issue with this update,quite well described here. To root your phone, you should flash CWM with ODIN, then don't let the phone boot normally (by pulling out the battery), then boot in CWM once and flash root. Finally, after booting the phone normally, CWM will be rewritten, but you will have rooted phone. Hope this helps.

There's another really helpful tutorial on rooting without tripping the flash counter. It's stickied around here somewhere, I'll see if I can find it.
http://forum.xda-developers.com/showthread.php?t=1771687
And you may want to bookmark this thread too:
http://forum.xda-developers.com/showthread.php?t=1723175

ega2oo2 said:
Have you installed recent LH2 OTA update? This is a known issue with this update,quite well described here. To root your phone, you should flash CWM with ODIN, then don't let the phone boot normally (by pulling out the battery), then boot in CWM once and flash root. Finally, after booting the phone normally, CWM will be rewritten, but you will have rooted phone. Hope this helps.
Click to expand...
Click to collapse
Thank you very much, I did update it right when i got the phone. I will try that exactly when i get home, thanks alot, i appreciate all the help

ega2oo2 said:
Have you installed recent LH2 OTA update? This is a known issue with this update,quite well described here. To root your phone, you should flash CWM with ODIN, then don't let the phone boot normally (by pulling out the battery), then boot in CWM once and flash root. Finally, after booting the phone normally, CWM will be rewritten, but you will have rooted phone. Hope this helps.
Click to expand...
Click to collapse
By the way, it worked perfectly, i suggest though, when in Odin, uncheck auto reboot, so it didn't reboot after it passes, then i just pulled battery out and tried booting in CWM and it worked. Guess you can't let it reboot or you have to do it again. My last question is, do i keep my phone in usb debugging mode with root on stock rom? I had a galaxy s2 and i know some custom roms had to have usb debugging on. Just not sure if stock with root i should or shouldn't. Thanks again, i hit all the thanks meters on this one, was driving me nuts....Jake

Recorvery
themadzionist said:
By the way, it worked perfectly, i suggest though, when in Odin, uncheck auto reboot, so it didn't reboot after it passes, then i just pulled battery out and tried booting in CWM and it worked. Guess you can't let it reboot or you have to do it again. My last question is, do i keep my phone in usb debugging mode with root on stock rom? I had a galaxy s2 and i know some custom roms had to have usb debugging on. Just not sure if stock with root i should or shouldn't. Thanks again, i hit all the thanks meters on this one, was driving me nuts....Jake
Click to expand...
Click to collapse
I use TRWP is a better recovery for sg3

[Q] [[SOLVED]] Recovery Broken, Need Help

[[SOLVED]]
Alright, so I checked through a few pages on the forums, and I didn't see anyone posting about this issue I am having..
I purchased my S3 a few days ago, and instantly rooted it. I used the Odin3 v3.07 method with "root66_SPR_L10VPBLJ7.7Z" ROM. That went well and fine. Then I tried flashing CWM recovery, and when I booted into recovery, it was still the stock. So I downloaded ROM Mangager and flashed the touch CWM recovery, after it finished, it asked if I wanted to boot into recovery. I agreed. Then the phone restarted, and upon starting, it showed the SAMSUNG logo, and "recovery booting" in the top left corner for about half a second. Then it just stayed on a black screen. I could do nothing after that. I then took the battery out for about 5 minutes, threw it back in, and the phone started. So I tried to manually boot into recovery, and the same issue. Took the battery out again, phone started properly, so I then tried to get into download mode. That worked fine, so I downloaded the CWM recovery on my laptop, and connected the phone through Odin, and flashed CWM onto my phone. Odin said it passed, but I still have the same issue when I try to boot into recovery.
Any ideas on something I'm doing wrong?

It is likely that your ROM is detecting the custom recovery and replacing it with the stock one. This was a change made to the stock ROM several versions ago. Before that you did not have to do anything extra to load the custom recovery.
The versions LG8 and later have code to detect an unsigned recovery and replace it with stock. You need to:
- Download TeamEpic-Root-from-Recovery-v5.zip and place it on your ineternal sdcard.
- Get into Download Mode and connect ODIN.
- Flash the custom recovery with ODIN but do not check the "Auto Reboot" box in Odin.
- Disconnect the phone from the PC once the recovery is flashed.
- Pull the battery to power down
- Boot directly into recovery (Hold Volume Up, Home and Power buttons until recovery appears. Do not allow the ROM to start).
- Once in the recovery you need to flash the Team Epic Root from Recovery.
- Reboot
All Done

m20120 said:
It is likely that your ROM is detecting the custom recovery and replacing it with the stock one. This was a change made to the stock ROM several versions ago. Before that you did not have to do anything extra to load the custom recovery.
The versions LG8 and later have code to detect an unsigned recovery and replace it with stock. You need to:
- Download TeamEpic-Root-from-Recovery-v5.zip and place it on your ineternal sdcard.
- Get into Download Mode and connect ODIN.
- Flash the custom recovery with ODIN but do not check the "Auto Reboot" box in Odin.
- Disconnect the phone from the PC once the recovery is flashed.
- Pull the battery to power down
- Boot directly into recovery (Hold Volume Up, Home and Power buttons until recovery appears. Do not allow the ROM to start).
- Once in the recovery you need to flash the Team Epic Root from Recovery.
- Reboot
All Done
Click to expand...
Click to collapse
Correct; and the reason for this is because the updated stock firmware as a script basically that re-flashes stock recovery upon boot if stock isn't detected. The team epic zip removes that. After doing that; I'd recommend flashing the twrp recovery.

Need some Help!
Ok guys got a problem! I have a new Samsung Galaxy Sprint S3 SPH-L710 4.1.1 and I flashed CMW ROM and did not do a back up of the stock OS. The phone still works with the ROM that I flashed cm-10.1m1. I already know befor you say it dumb right! Lol I'm kicking myself because I know better. I need help finding a mirror of the stock OS with all the drivers and kernels! Can anyone help out, thanks. :crying:

Re: [Q] Recovery Broken, Need Help
shadowcop9514 said:
Ok guys got a problem! I have a new Samsung Galaxy Sprint S3 SPH-L710 4.1.1 and I flashed CMW ROM and did not do a back up of the stock OS. The phone still works with the ROM that I flashed cm-10.1m1. I already know befor you say it dumb right! Lol I'm kicking myself because I know better. I need help finding a mirror of the stock OS with all the drivers and kernels! Can anyone help out, thanks. :crying:
Click to expand...
Click to collapse
So whats your issue? Why do you need the stock rom...? The drivers are the same and the stock kernel is for stock only, not aosp
Sent from my PG06100

Okay I did some research, and I found online that the Samsung phones need .tar.md5 not .img files for recovery.
http://forum.xda-developers.com/showthread.php?t=1484304
I did not use these directions since I don't run linux, and I wasn't going to download VMWare. Anyways, the way I fixed it, I purchased and downloaded Mobile Odin from the Play store. I put the recovery.img on my external SDcard, then opened the app. Under "recovery" I selected recovery.img and then scrolled down to "Flash" It flashed the recovery.img with no problems, then booted me into recovery. I then flashed mrRobinson_Ashaman.v2.20_signed.zip so I could uninstall some bloatware.
That last part was mostly for me, until I find a ROM I like.

CNexus said:
So whats your issue? Why do you need the stock rom...? The drivers are the same and the stock kernel is for stock only, not aosp
Sent from my PG06100
Click to expand...
Click to collapse
I'm selling my phone and getting the Galaxy S4 and the person wants the stock back on the phone.

shadowcop9514 said:
I'm selling my phone and getting the Galaxy S4 and the person wants the stock back on the phone.
Click to expand...
Click to collapse
Oh ok then, just run the latest Supersonic RUU (4.67 i think)
Sent from my PG06100

CNexus said:
Oh ok then, just run the latest Supersonic RUU (4.67 i think)
Sent from my PG06100
Click to expand...
Click to collapse
Ok, where do I find that ?

shadowcop9514 said:
Ok, where do I find that ?
Click to expand...
Click to collapse
WHOOPS. Sorry, I was thinking about another phone
Look up "flash back to stock galaxy s3" on google and you should get some good hits. Ignore the RUU thing, I thought I was on the OG evo forums
Sent from my PG06100

CNexus said:
WHOOPS. Sorry, I was thinking about another phone
Look up "flash back to stock galaxy s3" on google and you should get some good hits. Ignore the RUU thing, I thought I was on the OG evo forums
Sent from my PG06100
Click to expand...
Click to collapse
Ok thanks!