I recently rooted my phone and flashed the stock google build via nexus toolbox. I wanted to be on the stock rom so that I can get OTA updates.
I tried the update today only to find I have clockworkmod recovery and the OTA doesn't work. I have some questions about this and I'm pretty new to it all so please be gentle. My main goal is to be on stock, get OTA updates and not have to wipe my phone in any way.
1 can I get rid of the clockworkmod and go back to stock recovery without wiping my phone? If so, how do I do it?
2 can I flash jelly bean via clockworkmod/tool kit without wiping my phone? If so, how do I do it?
3 which of the above methods is recommended?
Thanks, I appreciate any help I can get
Cheers, Dean
dwphoto said:
1 can I get rid of the clockworkmod and go back to stock recovery without wiping my phone? If so, how do I do it?
Click to expand...
Click to collapse
Flash the stock recovery via Fastboot. Do this if you intend to stay completely stock.
2 can I flash jelly bean via clockworkmod/tool kit without wiping my phone? If so, how do I do it?
Click to expand...
Click to collapse
If you want to keep CWM, then yes you can flash by putting the flashable update.zip on the SDcard and flashing it via CWM. Do this if you intend to keep CWM.
3 which of the above methods is recommended?
Click to expand...
Click to collapse
Via Fastboot. NOT a toolkit.
1 - Yes get the factory image from here
Extract the recovery.img and stick it in your fastboot folder
boot into fastboot and type fastboot erase recovery
type fastboot flash recovery recovery.img
wait for flash
type fastboot reboot-bootloader
Reboot into nexus.
2 yes but its not recommended as it will probably screw something up having different data on there you just install from sdcard.
3. You should always wipe cache, Advanced Wipe Dalvik Cache, and wipe Data before installing any rom from sdcard. Reinstall your apps afterword using something like Titanium Backup. If you want to stay OTA, I suggest stock bootloader and if you are rooted using OTA rootkeeper before updating.
martonikaj said:
Flash the stock recovery via Fastboot. Do this if you intend to stay completely stock.
If you want to keep CWM, then yes you can flash by putting the flashable update.zip on the SDcard and flashing it via CWM. Do this if you intend to keep CWM.
Via Fastboot. NOT a toolkit.
Click to expand...
Click to collapse
Thanks for the response. Will either of those methods wipe my phone - like rooting does?
I think I want to stay completely stock - the nexus tookit offers an option to reflash the stock recovery. Should I us this since I'm not sure how to do it via fastboot?
Once I'm back to stock recovery, will the OTA update become avaiable again ( I just checked for system updates via the phone and it says I'm up to date rather than offering the update again)
Thanks
Rooting doesn't wipe your phone, Unlocking your bootloader does.
Flashing a recovery doesn't mess with data
To get the OTA to push again you will have to clear data from the app "Google Services Framework"
NeoMagus said:
Rooting doesn't wipe your phone, Unlocking your bootloader does.
Flashing a recovery doesn't mess with data
To get the OTA to push again you will have to clear data from the app "Google Services Framework"
Click to expand...
Click to collapse
Proper answer here ^
Just to follow up, I ended up flashing the stock recovery via the gnex toolkit which worked fine. The update then ran fine and I'm now enjoying some tasty jelly beans.
Thanks to all for the help and advice
dwphoto said:
Just to follow up, I ended up flashing the stock recovery via the gnex toolkit which worked fine. The update then ran fine and I'm now enjoying some tasty jelly beans.
Thanks to all for the help and advice
Click to expand...
Click to collapse
Glad it worked out.
Related
guys, I am have stock 4.0.2 rooted with CWM, is there a way to update stock rom (when stock 4.0.3 comes out) without wiping data?
I know I could do all kinds of MyBackupPro or Titanium Backup, but still it's quite a bit of hassle especially I can't keep anything in Internal Storage, anyone got an idea on this?
Easiest way would be to go ahead and flash the factory recovery back rather than clockworkmod. If you are on stock now and are wanting to get the 4.0.3 OTA when its pushed than you really don't need clockwork. If you flash the factory recovery back that we will be able to get the OTA and not worry about a data wipe. Flashing the factory recovery will not effect your current root at all so you stay rooted.
badassirocz said:
Easiest way would be to go ahead and flash the factory recovery back rather than clockworkmod. If you are on stock now and are wanting to get the 4.0.3 OTA when its pushed than you really don't need clockwork. If you flash the factory recovery back that we will be able to get the OTA and not worry about a data wipe. Flashing the factory recovery will not effect your current root at all so you stay rooted.
Click to expand...
Click to collapse
wow, thanks, so, I'm assuming I could use the same tool (GNex Toolkit) to flash back my factory recovery, right? besides, what if I did flash a custom kernel (like Jame Bond), do I need to flash back that too? or I could just leave it and the OTA would overwrite the kernel with stock kernel?
thanks!
You should be able to use that tool kit or you can just use fastboot and do the following after downloading the proper factory image from google and extracting the recover.img as for the kernel I don't believe it will effect the OTA at all.
- copy the recovery.img file to the directory that contains your fastboot utility
- start-up a terminal/command session
- put your phone into fastboot / bootloader mode
- type the following fastboot command to flash the stock recovery:
Code:
fastboot flash recovery recovery.img
OP, your internal storage doesn't get wiped when flashing a new ROM.. The virtual SD card is left untouched.
Also I'm pretty sure you lose root if you accept an OTA update.. but you can easily reroot.
badassirocz said:
You should be able to use that tool kit or you can just use fastboot and do the following after downloading the proper factory image from google and extracting the recover.img as for the kernel I don't believe it will effect the OTA at all.
- copy the recovery.img file to the directory that contains your fastboot utility
- start-up a terminal/command session
- put your phone into fastboot / bootloader mode
- type the following fastboot command to flash the stock recovery:
Code:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
thanks! would give it a try!
joshnichols189 said:
OP, your internal storage doesn't get wiped when flashing a new ROM.. The virtual SD card is left untouched.
Also I'm pretty sure you lose root if you accept an OTA update.. but you can easily reroot.
Click to expand...
Click to collapse
um. I am not so sure it would be the case for Galaxy Nexus, data wipe before (like my GS2) just means user data, but for Galaxy Nexus, last time i tried it wipe my internal storage as well. when I'm using the GN toolkit to flash 4.0.2 image downloaded from Google, it wiped my data and storage, do you mean there is a way to flash Google image without wiping for GN ?
Found answer.....
speedin said:
Found answer.....
Click to expand...
Click to collapse
answer of....?
hongkongtom said:
answer of....?
Click to expand...
Click to collapse
I asked if it was possible to update OTA when your phone is unlocked, and with CWM.. The answer is "yes" if you have stock recovery instead of CWM....
speedin said:
I asked if it was possible to update OTA when your phone is unlocked, and with CWM.. The answer is "yes" if you have stock recovery instead of CWM....
Click to expand...
Click to collapse
great, while knowledge never have enough, my next question is "How could I manually flash (instead of OTA) stock Google image (in case 4.0.x got out) without wiping my GN?" (assuming I am coming from earlier stock rom)
So I was attempting to try a new rom - Android Revolution HD 3.0.0 -. I downloaded the rom, and super wipe script and booted into CWM recovery.
Ran the Super Wipe script and now it just hangs on reboot. I can still get into fastboot but I can't get into Android or Recovery. Whenever I try to boot into Recovery I get Andy with the spinning sphere. The blue loading bar hangs about 1/5 of the way across. Eventually the phone reboots and repeats.
I've tried gnex toolkit v5.6. I tried flashing a new recovery via the toolkit and I tried option 7(1-click for all). Both say they successfully installed the recovery but I still can't boot.
Any ideas?
and this is why you dont use toolkits because you dont have a full understanding of what you're doing and relying on a program.
fastboot flash google stock images OR fastboot flash clockwork recovery in bootloader mode and then proceed to go into recovery mode and wipe factory(data)/cache/dalvik and flash a rom
i advise doing the second that i suggested. if all else fails, flash google images as a last resort
zephiK said:
and this is why you dont use toolkits because you dont have a full understanding of what you're doing and relying on a program.
fastboot flash google stock images OR fastboot flash clockwork recovery in bootloader mode and then proceed to go into recovery mode and wipe factory(data)/cache/dalvik and flash a rom
i advise doing the second that i suggested. if all else fails, flash google images as a last resort
Click to expand...
Click to collapse
Thanks for the quick reply. I just assumed the toolkit would be a quicker way of doing the commands manually. That being said even fastboot flash recovery recovery-clockwork-5.5.0.2-maguro.img nets me the exact same results, so it looks like I'm off to google stock images
AverageCanadian said:
Thanks for the quick reply. I just assumed the toolkit would be a quicker way of doing the commands manually. That being said even fastboot flash recovery recovery-clockwork-5.5.0.2-maguro.img nets me the exact same results, so it looks like I'm off to google stock images
Click to expand...
Click to collapse
It is quicker in a sense. But with every short cut that you take, you're losing knowledge. Sure, you're rooting and doing all that fancy stuff. But you're not realizing what you're doing so when you have a problem.. you're unable to diagnosis it because you aren't aware of what that toolkit just did.
Okay. Then just flash google stock images.. after it boots into Android, just fastboot flash recovery again and then wipe and then flash your ROM.
back on stock rom for now . Will have to flash custom recovery later but for now I have a working phone again which is nice.
AverageCanadian said:
back on stock rom for now . Will have to flash custom recovery later but for now I have a working phone again which is nice.
Click to expand...
Click to collapse
Glad to hear it was happy to see that you didn't panic and claim your phone being 'bricked.' Definitely weird how the superwipe script caused that problem on your phone. Personally not a fan of "superwipe" that's just me. Manually wiping factory(data)/cache/dalvik is good enough for me.
Same happened to me trying to install HD 3.0. I also had to go back to flashing Google stock after getting the boot loop you described. Would it have anything to do with that script trying to format partitions to ext3??
Sent from my Galaxy Nexus using XDA
Dear All
yes, I am new and I feel exactly as the intro-video when registering was referring to ("noob", "loser",...)
After half a year, thought it was time to root my galaxy nexus. Used the Gnexus Toolkit. Everything worked fine.
So, I wanted to take things a bit further and as I've read interesting things on the franco.kernel, I tried to flash a new kernel using the app's automatic flash tool.
Device restarted, stuck at the Google logo.
I went inro recovery mode and followed some guidelines I found here and on other fora telling me to wipe data, wipe cache, wipe dalvik cache, format data,....
First tried to restore the "recovery"-thing clockworkmod creates for you when first using it. Didn't work.
Tried to wipe/format once again... Nothing helps and now I've even lost the "recovery"-thing.
only option seems to adb sideload... but I do not seem to get that working.
Well... hm. Here I am then. Having no idea to continue...
And, yes,... I have to repeat... I feel exactly as the intro-video of xda is suggesting I should feel
Install GNex TOOLKIT in the PC, download a custom rom and push the file to the phone with adb in fastmode. With this toolkit you can also flash recovery (CWM for example) again.
http://forum.xda-developers.com/showthread.php?t=1392310
joooe said:
Install GNex TOOLKIT in the PC, download a custom rom and push the file to the phone with adb in fastmode. With this toolkit you can also flash recovery (CWM for example) again.
http://forum.xda-developers.com/showthread.php?t=1392310
Click to expand...
Click to collapse
Thanks: I was indeed able to start in fastboot and used the Gnex Toolkit. I installed the stock image (4.0, then it updated to 4.2.1 later).
Pfffew, everything now works. hehe.
Thanks.
:good: Good result then.
joooe said:
I would probably start all over again.
Download latest version of ClockworkMod Recovery, go to fastboot mode, flash it.
Download rom, push it to the "sdcard" with adb, then go to CWM recovery and flash the rom.
Click to expand...
Click to collapse
That's indeed what I wanted to do.
Need to get some work done now. Will try it in the weekend. Thanks for the help.
After years of successful rooting I think I may have killed an SG3.
I was running OTA 4.3 from vzw and wanted to root it. I ha used Casual in the past I tried it again and it failed. I noted it was for 4.1/4.2 so I tried to Odin back to 4.1 from OTA 4.3 Little did I know this was bad juju. Now I have a phone that won't boot, it keeps saying firmware upgrade an issue. I can get to download mode but have no idea what to try and flash to it since I've read that flashing anything less than 4.3 won't work and the 4.3 official isn't available.
So, is it dead?
there's so much hope for your fone
drekalots said:
After years of successful rooting I think I may have killed an SG3.
I was running OTA 4.3 from vzw and wanted to root it. I ha used Casual in the past I tried it again and it failed. I noted it was for 4.1/4.2 so I tried to Odin back to 4.1 from OTA 4.3 Little did I know this was bad juju. Now I have a phone that won't boot, it keeps saying firmware upgrade an issue. I can get to download mode but have no idea what to try and flash to it since I've read that flashing anything less than 4.3 won't work and the 4.3 official isn't available.
So, is it dead?
Click to expand...
Click to collapse
first of all your phone isn't dead alright there is so much hope for that device you have now.
ok boot to recovery mode and wipe cache and dalvik cache and reboot system...
If that fails,i'll advice that you use an official SG os that your phone came with and flash it with odin...
yup that should help
senatoduro88 said:
first of all your phone isn't dead alright there is so much hope for that device you have now.
ok boot to recovery mode and wipe cache and dalvik cache and reboot system...
If that fails,i'll advice that you use an official SG os that your phone came with and flash it with odin...
yup that should help
Click to expand...
Click to collapse
It won't boot into recovery mode.
drekalots said:
It won't boot into recovery mode.
Click to expand...
Click to collapse
i guessing u can boot into download mode...
since u downgraded the fone,i'm pretty sure u av EFS issue at hand
u should get a current CWM and flash using odin...then boot into recovery and do the caches clearing\
if it doesnt work...please explain ur problem properly to me so that i can help u out
The device is not rooted. So flashing CWM or TWRP isn't going to work.
Here's what I did:
1. The phone is running NON-ROOTED stock 4.3 OTA from VZW.
2. Decided to root device so I tried Casual's Root app which I later realised only worked on 4.1/4.2 devices.
3. Since step 2 didn't work I tried to flash 4.1 to the phone via Odin.
4. Step 3 caused the device to no longer boot. It gives a firmware upgrade error and will only boot into download mode.
5. I obtained the 4.3 OTA and tried to flash it via Odin, no go. It didn't work.
The phone is effectively dead with only download mode working.
Phone is not dead till you can get to Recovery or Download mode.
You possibly have problem of new bootloader which might not be downgradable.
My suggestion would be :
1, Flash some Custom Recovery like CWM or PhilZ through PC ODIN.
2. Enter Recovery and format System,Data, Cache and Dalvik.
3. Flash some 4.3 based Custom ROM. (download it and place it on your External SDcard before doing anything)
4. Clear Cache and Dalvik again.Reboot.
Good luck !!!
I tried to flash CWM and TWRP, both failed. However, the device rebooted and worked after flashing the failed TWRP.
I recently installed a root zip file VIA CWM Recovery. After installing said root file, my device won't load. It will turn on and give me the Samsung boot logo, but will not go any further that. I get the "kernel is not seandriod enforicing" text and set bit warranty : kernel.
I tried factory wipe, cache wipe and davlik wipe. nothing is working.
I can however, go into recovery.
How can I get my phone working normally again?
lordramos said:
I recently installed a root zip file VIA CWM Recovery. After installing said root file, my device won't load. It will turn on and give me the Samsung boot logo, but will not go any further that. I get the "kernel is not seandriod enforicing" text and set bit warranty : kernel.
I tried factory wipe, cache wipe and davlik wipe. nothing is working.
I can however, go into recovery.
How can I get my phone working normally again?
Click to expand...
Click to collapse
Did you do a NAND Backup using CWM before the flash? If so, restore it.
Assuming you are on Stock, since most Custom ROMs are already rooted, you way want to use ODIN to flash the full firmware. That will get rid CWM, root, etc. But, you should be able to get past the boot logo. Do you know which version of Stock you were on?
You can download the previous firmwares here:
http://forum.xda-developers.com/galaxy-s4-tmobile/general/firmwares-official-mdl-mk2-nb4-t2816508
and, the latest is here:
http://forum.xda-developers.com/gal...mware-firmware-kernel-modem-recovery-t3193835
Rob
rlichtefeld said:
Did you do a NAND Backup using CWM before the flash? If so, restore it.
Assuming you are on Stock, since most Custom ROMs are already rooted, you way want to use ODIN to flash the full firmware. That will get rid CWM, root, etc. But, you should be able to get past the boot logo. Do you know which version of Stock you were on?
You can download the previous firmwares here:
http://forum.xda-developers.com/galaxy-s4-tmobile/general/firmwares-official-mdl-mk2-nb4-t2816508
and, the latest is here:
http://forum.xda-developers.com/gal...mware-firmware-kernel-modem-recovery-t3193835
Rob
Click to expand...
Click to collapse
I was on the latest OTA Update T mobile pushed out. Should be 4.4.4 , since T-Mobile didn't bless us with Lollipop
Once you get straightened out use the CF Autoroot to get your root. I use the one you flash with Odin and it has worked every time.
Jim