Related
hey all, currently have a g2x rooted with cm7, and i've been looking to unroot;
just to make sure i dont do anything stupid, i wanna run this through with you guys:
first i would flash the stock 2.3.3 ota rom for g2x
then use the http://forum.xda-developers.com/showthread.php?t=1056847 (one click nv flasher) to get back to lg stock recovery by clicking 'flash stock recovery' (do i need to dl anything extra for this?)
then im done, correct? if i boot up, ill get all the stock rom and apps and bloatware and etc back right?
thanks!
edit: how do i know which version of clockwork mod i have installed? im not sure if i did the external sd support or not...
You've gone back to a stock ROM, you've gone back to the stock recovery, but you haven't actually unrooted.
Whichever method you used to root, you should be able to use that same method to unroot.
UPDATE:
I was originally under the assumption that your 2.3.3. ROM was rooted. If it is stock you should be fine.
sorry for bump, but i read in tga_gunmans post that ppl should flash a rooted 2.3.3 rom and use superoneclick to unroot...would my method work too?
No your way would not work because the stock OTA by xboarder is rooted. Do what tga_gunman said. Flash the rom, use my unroot zip in CWM (deletes root files) and then flash the stock recovery. Busybox will still be on the phone but nobody should be looking for that.
Unroot zip: http://www.mediafire.com/?2vr7cmgg7qcdn14
Easiest way to confirm if your not rooted would be to install Superuser from the market. It'll tell you if the phone's not rooted.
There is an app on the market called Root Checker which is free. It will tell you if you are rooted or not.
A little extra help for me?
jboxer said:
No your way would not work because the stock OTA by xboarder is rooted. Do what tga_gunman said. Flash the rom, use my unroot zip in CWM (deletes root files) and then flash the stock recovery. Busybox will still be on the phone but nobody should be looking for that.
Unroot zip:
Click to expand...
Click to collapse
Thanks for your help jboxer. Forgive my noob-like understanding of rooting/unrooting terminology. Hopefully you'll be able to understand what I did.
Last night I went ahead with the unrooting process on my G2X which was running Gingerbread & CM7 following this youtube video (can't post link due to noobiness: watch?v=ryGIv8KQVIE), the order that this guy goes in is:
1. Wiping all cache/user data/formatting in CWM recovery
2. Restore to a barebones stock data in CWM recovery
3. Flash to go back to Stock using OneClickRecovery
4. SuperOneClick to unroot phone
What I ended up doing was restoring my phone to the backup that I created on my sd card when first rooting my phone rather than download that zip file in the video description which is a completely fresh start.
However, whenever I flashed to go back to stock using OneClickRecovery, it gave me that total barebones fresh start where I had to completely set up my Android from the first start screen and I lost my backup. Also, when I go to unroot the phone with that zip file, I don't know how to 'install from zip' after I've lost CWM Recovery menu. So, I flashed back to CWM so I could recover my backup from my SD Card again and install the 'unroot.zip' that you linked and it ran alright and I restarted, but I still had 'SuperUser' in my App drawer telling me that I was still rooted.
I ended up calling it good last night after spending two hours on it. I left my phone rooted, with CWM recovery still on my phone, but I at least I had my backup Gingerbread image with no CM7 mod. So, my phone is functional, but I would like to complete this process of unrooting completely.
Could you perhaps give a little guidance and clarity to what I'm missing or not understanding? I'd love to unroot/flash back to stock recovery/remove all evidence of rooting AND keep my recovered backup that I have before I even started rooting my phone.
Thank you so much for all your help, everybody.
Hello all,
sorry if this is a repeated question. I tried to read as much as I can in the Q&A and general sections, but could not find it.
I have a NS that was running CNA 1.4 for sometime. I got tired from the performance and I decided to give phone to my better half. Since my wife does not care much about custom roms, I decided to go back to stock so I can give her a care-free phone. She would be capable of doing the OTA updates on her own.
so, these are the steps I did to get to custom:
1. phone came with 2.3.4
2. unlock BL using ADB
3. root and install CWM
4. Nandroid backup
5. OTA update to 2.3.6
6. Nandroid backup
7. Custom ICS rom
when I tried to go back to stock I did a restore to step 6 above, the OTA was pushed automatically to my phone, but when I tried to install, the phone rebooted but did nothing and it seemed stuck at the android with an ! in a triangle.
I removed the battery, restored back to step 4 above and tried again and I got the same results.
I know I am probably forgetting something but I am not sure what is it.
Could someone please offer some direction?
thanks in advance.
Flash official factory images with fasttboot .
You cant get official OTAs when your device is rooted
thanks guys for your reply.
but what is the main cause for not being able to install OTA updates?
1. is it because the BL in unlocked?
2. or because of root?
if because of root, has anyone tried that app from the Market? could it be used to regain root after OTA?
https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper
thanks again.
You can get ota just fine on a stock (unmodified) rom with root. You will loose root when it updates. Then just reroot it.
Bootloader state is irrelevant.
albundy2010 said:
You can get ota just fine on a stock (unmodified) rom with root. You will loose root when it updates. Then just reroot it.
Bootloader state is irrelevant.
Click to expand...
Click to collapse
thanks for the info.
one last question, when I rooted my 2.3.4, it also installed CWM recovery.
Does CWM interfere with the OTA update or just the root?
if it interferes, I'll have to find a way to go back to stock recovery, right?
Yes and no.
For the OTA process to go as "normal' stock recovery needs to be there. Normal as in get the OTA notifcation/auto download reboot and install.
No as in if you manually download or place the ota zip file on your internal storage it will flash in cwm like any other zip.
Also since ICS you currently have to flash the ota zips with aftermarkt recoverys if you do it manually. The pick zip from sd card in stock recovery is broken now.
In the stock rom under /system/etc there is a script that overwrites custom recovery with the stock one on every boot. Rename that file to .bak or something instead of its default .sh If you want to stock recovery back just change the file extenstion back and reboot the phone fully. Next time you boot back into recovery it will be stock again.
Or you don t go to stock recovery and flash the updates by yourself on your phone. Downloaf them and then flash them through CWM. But i think u havent got CWM anymore after grtting an official update. You ll get the original recovery again
thanks again guys.
currently I can go back to either 2.3.4 or 2.3.6 stock roms but both have CWM and root.
ultimately what I want to do is:
1. be able to un-root (probably using this market app)
2. download OTA on phone, do normal "reboot and install"
3. boot up with updated OTA rom.
4. regain root (probably using the same market app)
so, what I understand from prev posts, that I must put back the stock recovery (which I do not mind) for my steps above to work.
can I use ADB and fastboot to push the stock "recovery.img"? and where to find it?
I'll do some searching in the forums, but if someone happens to have link to the thread, it would be fantastic.
thanks again
Why dont you keep the root and flash the official firmware that you downloaded per CWM. So you dont have to unroot and root again later. Or do a factory wipe.
ok guys, so whatever I tried to do I was not able to get the stock recovery back to go with the "normal OTA download on phone, reboot and install thing", so here is what I ended up doing.
1. I had 2.3.6 (GRK39F), rooted stock rom, cwm recovery.
2. Download/install "OTA Rootkeeper" free app from Google Play Market. link below
3. Using "OTA Rootkeeper" app, did a "backup root", then "temp un-root"
4. Download official signed Google ICS update package to upgrade from 2.3.6 (GRK39F) to 4.0.4 (IMM76D) and move it to sd card. link below
5. Reboot into cwm recovery
6. Install update from sd card and choose Zip from #4
7. Go back and reboot system
8. After upgrade to ICS is complete, use "OTA Rootkeeper" app, did a "restore root" and voila
9. So now I have rooted stock ICS rom, and cwm recovery.
notes:
these steps should also work on whatever stock GB rom you have as long as:
a. rooted
b. have cwm
c. download the proper update package in step 4 above.
links:
2. https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper
4. http://www.randomphantasmagoria.com/firmware/nexus-s/
thanks again guys, couldn't have done without your help
good luck for anyone trying to do the same.
1.Download appropriate rom for your phone
i9020T or i9023
http://downloadandroidrom.com/file/NexusS/roms/ota/2.3.6/i9020t_i9023.zip
and i9020a
http://downloadandroidrom.com/file/NexusS/roms/ota/2.3.6/i9020a.zip
2.Copy it to sdcard
3.Install it through recovery (CWM)
4.Restart system
5.Reboot phone into bootloader
6. Hit recovery and once you get the lil droidy and the !, Push Vol up + Power until you get blue menu
7. Go to wipe data/fact reset
8.Reboot to bootloader
9.then go into adb and type fastboot oem lock
By this time you shouldve completely returned your phone to stock and you are able to get ota updates and everything!!! YAY!!!!
http://www.randomphantasmagoria.com/firmware/nexus-s/
if you wanna go back to 100% stock unrooted, download any rom from that thread and install through cwm then reboot and you will be stock and unrooted with stock recovery and then just lock the boot loader and you will be 101% factory stock and ready to receive ota updates. I would recommend the 2.3.6 because it will give you the 4.0.4 ota right after you reboot.
So I got my 300T a few nights ago.
It's already got Asus's JB on it.
Wanted to root to use the SwitchMe app for multiple profiles.
I was able to get the system to see fastboot, and ran all of the commands. Was able to boot to CWM and install root-signed. When I was trying to reboot, it said root was possibly lost, asked me to fix it, i said yes.
When I open up the SwitchMe app, it just keeps trying to open a SuperUser window about 7 times, and then does nothing else.
Have I done something wrong?
SuperUser just says No Apps in List.
edit: tried to update SuperUser. It says "gaining root access.....fail!". Guess I'll try to install root-signed again. Not sure how I could've messed it up the first time.
edit 2: wiped cache and dalvik, installed root-signed again, same problem. SwitchMe says I haven't granted superuser permissions. SuperUser shows no apps, is set to auto-allow root access, and fails getting root access when running binary updater.
im pretty sure you have to unlock the bootloader
and go through some crazy process before you can root with JB
My tablet was running JB when I bought it. I unlocked and still could not get my tablet to root using CWM. On top of that, CWM would not make a proper backup. I highly recommend you switching to TWRP. I did, flashed a rooted custom ROM and haven't had anymore issues.
Many people are having issues with CWM. TWRP is definitely the way to go. :good:
1 wrong section
2 root checker app(s)
Well, what I did to root my stock using TWRP was to flash the root-signed in the CWM thread, but as this didn't really got me full root, I flashed the flashable zip from here, downloaded SuperSU from market, there then chose "update binary" and then I had root
I'm pretty sure flashing the root-signed of the CWM thread wasn't needed, but if you do this steps (need to be unlocked to flash a recovery, strangely recommend TWRP 2.3.1 or 2.2.2 for 4.1 ROMs and 2.3.3 for 4.2 ROMs (as 4.2 has this sdcard/0 directions because of Multiusers, 2.3.3 uses this directories too))
So what should work:
1. unlock bootloader
2. flash CWM / TWRP / MobileODIN installable ZIP: CWM-SuperSU-v0.99.zip from here
3. download SuperSU from market and there update binary (don't know how it's called exactly)
4. enjoy!
if you decide to use a Custom ROM, you just need to flash the ROM in TWRP and should get Root too with the ROM (as all of them include Root afaik)
I'm really confused about something and before I get flamed for not searching before posting, let me preface by saying that I have and still can't find a definitive answer given that nobody seems to reference the problem I'm having - at least it doesn't show up in my attempts to search.
My Question: Once I'm rooted, what is the process for accepting an OTAs (over the air updates) from Verizon? Whenever I download and install them, I get the "Custom" Lock Icon during bootup.
Here are the steps I've followed:
1. Flashed back to stock 4.1.1
2. Flashed the VRALEC bootchain
3. Flashed CWMR
4. Booted into CWMR recovery and ran the SuperSU_Bootloader_FIXED.zip (Note: no message appeared asking me about locking
5. Flashed the 4.1.1 bootchain
6. Downloaded and it auto rebooted to install the OTA (I wanted to see what it's like the NEXT time verizon pushes out an OTA so I know what the process is once all my apps are installed)
7. When finished applying the update it asks me: A. Do I want to Disable recovery flash? and B. Do I want to preserve root?
At first I tried answering both questions with yes and yes since I saw the message about that here: http://forum.xda-developers.com/showthread.php?t=2046439
My Problem: As soon as I rebooted, I get the custom lock icon message during bootup. So then I repeated the entire process and answered No and No to those questions. And again, I get the custom lock icon message during bootup.
Yes, I realize, I can and probably should install the OTA and then root the device. But that's not my point. I want to understand what to do the NEXT time Verizon pushes out an OTA. Do I have to flash back to stock every time I install the OTA and root the device only after installing the OTA just to avoid getting the custom lock icon? If not, how do I accept the OTA without getting the custom lock icon? (Obviously I can't seem to figure out how to do it now, so I won't be able to do it the next time an OTA rolls around - thus the reason for my question).
Thanks,
Jonathan
you might have to flash a custom ROM to block Verizon from pushing OTA.
http://forum.xda-developers.com/showthread.php?t=1762709
Reference section 5 for me. It looks like you already know how to get to that point. It has great instructions for recovering to stock from the triangle.
As far as disabling updates go I would recommend titanium backup, and freezing the update service. "FWUpgrade" as well as "SDM" are the names. You can also uninstall it, but freezing it in Titanium is my recommendation.... This will prevent your phone from pinging OTA updates in the future even when big red pushes them.
Honestly, if you want the new feature just wait a day or two after the release. There is always a lovely developer waiting to debloat, deodex, and optimize the official OTA update for your use without breaking root access.
Have I helped with your question? Or have I misinterpreted your needs?
First, thanks for the replies!
ManiakalSealion said:
http://forum.xda-developers.com/showthread.php?t=1762709
Reference section 5 for me. It looks like you already know how to get to that point. It has great instructions for recovering to stock from the triangle.
Click to expand...
Click to collapse
I think you misunderstood me on this point. When installing an OTA after root, I never get the yellow triangle, so there is no need to recover. The problem I'm having is that on the very first screen that appears when you first power on the phone (after installing the OTA on top of a rooted version of Android) it adds a large lock icon with the word "CUSTOM" to black screen (think it says Samsung but I don't recall) to indicate that Verizon has detected something custom about the phone.
I was trying to determine if after having rooted my phone if there was a way to accept the OTA and still maintain root - rather than having to flash back to stock or flash an update using ODIN. It's a pain to have to always flash something at home - I'd like to be able to accept the OTA if possible while I'm away from home. I tried OTA Rootkeeper but that didn't seem to do anything for me - perhaps I'm not using it correctly???
ManiakalSealion said:
http://forum.xda-developers.com/showthread.php?t=1762709
As far as disabling updates go I would recommend titanium backup, and freezing the update service. "FWUpgrade" as well as "SDM" are the names. You can also uninstall it, but freezing it in Titanium is my recommendation.... This will prevent your phone from pinging OTA updates in the future even when big red pushes them.
Click to expand...
Click to collapse
So if I understand correctly, an app such as OTA Rootkeeper is useless for Verizon Galaxy S3 - the only way to get root and the Verizon OTA is to either 1. flash back to stock, install all OTAs and then re-root OR else 2. flash the custom OTA from a forum member, is that correct? In other words, once I've rooted, I always have to use ODIN to get an update - there is no other option?
jkrueger2020 said:
First, thanks for the replies!
I think you misunderstood me on this point. When installing an OTA after root, I never get the yellow triangle, so there is no need to recover. The problem I'm having is that on the very first screen that appears when you first power on the phone (after installing the OTA on top of a rooted version of Android) it adds a large lock icon with the word "CUSTOM" to black screen (think it says Samsung but I don't recall) to indicate that Verizon has detected something custom about the phone.
Click to expand...
Click to collapse
I'll suggest using EZ Unlock v1.2, just tap to lock then immediately tap to unlock your bootloader and you'll hear an audio confirmation upon pressing unlock. I think that should take care of the custom lock when booting up.
I was trying to determine if after having rooted my phone if there was a way to accept the OTA and still maintain root - rather than having to flash back to stock or flash an update using ODIN. It's a pain to have to always flash something at home - I'd like to be able to accept the OTA if possible while I'm away from home. I tried OTA Rootkeeper but that didn't seem to do anything for me - perhaps I'm not using it correctly???
Click to expand...
Click to collapse
I'll say this, most custom roms block Verizon OTA's from installing so you'll just have to accept that you need to flash back to stock to accept an OTA OR just stick to a rooted OTA based rom. There's at least seven of these, one per OTA or leak that we've seen to date.
So if I understand correctly, an app such as OTA Rootkeeper is useless for Verizon Galaxy S3 - the only way to get root and the Verizon OTA is to either 1. flash back to stock, install all OTAs and then re-root OR else 2. flash the custom OTA from a forum member, is that correct? In other words, once I've rooted, I always have to use ODIN to get an update - there is no other option?
Click to expand...
Click to collapse
Absolutely correct. Can I ask you something? Do you intend on using custom roms or do you just want to use rooted stock OTA's? Cuz you're inquiring an awful lot about OTA's for someone who would be using custom roms. That said, XDA devs have posted a rooted version of each OTA available. Each is in the dev section, they'll be titled something like "Stock Root JB 4.1.2 - I535VRBMB1 Official Update". You could easily just flash any one of these then pull down an OTA since these are left untouched with the only addition being SuperUser. Even still, you would need to re-root after accepting an OTA since OTA's wipe out root so you'll be doing this for as long as we see updates on this phone.
If you're rooted you can use OTA Rootkeeper to back up root, install OTA and then use it again to restore root. I just did this for the current OTA without any issues. Just make sure you also have stock recovery reinstalled if you installed TWRP or CWM, and relock the boot loader first.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
I'll suggest using EZ Unlock v1.2, just tap to lock then immediately tap to unlock your bootloader and you'll hear an audio confirmation upon pressing unlock. I think that should take care of the custom lock when booting up.
Click to expand...
Click to collapse
Yes! That removed the lock icon. So my next question is, when my phone booted back up and said the OTA failed (yet still shows the incremented version number making it appear like the update actually was successful) was there anything that got messed up as part of the upgrade? Or would I be better off going the route of another person's reply which said I should lock the bootloader and flash back to stock recovery first before accepting the OTA?
SlimSnoopOS said:
I'll suggest using EZ Unlock v1.2
Can I ask you something? Do you intend on using custom roms or do you just want to use rooted stock OTA's?
Click to expand...
Click to collapse
Currently I'm not really looking for custom ROMS - my experience with ROMS with my original Galaxy S was just a buggy experience (i.e. call volumes that kept reverting to max for every call, etc) and was not very enjoyable. As long as I stay rooted and current with Android I'm happy at this point (of course that could change down the road).
mav3rick478 said:
If you're rooted you can use OTA Rootkeeper to back up root, install OTA and then use it again to restore root. I just did this for the current OTA without any issues. Just make sure you also have stock recovery reinstalled if you installed TWRP or CWM, and relock the boot loader first.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Thank you!!!! That was exactly what I was hoping to find! I tried this out just for kicks to see if it would work for me and it did!
For anyone interested, here are the steps I took with my rooted device :
1. Lock the boot loader using EZ-Unlock 1.2
2. Using EZ-Recovery 2.2, I flashed the stock recovery
3. Backed up root access using OTA Root Keeper
4. Downloaded and installed the OTA
Note: The lock icon appeared still
5. Used EZ-Recovery 2.2. to flash CWM recovery in place of the stock recovery (I couldn't get it to flash the same tar.md5 file I used with ODIN though - don't know what kind of file EZ-Recovery needs - so I used the version of CMWR that it provided)
6. Restored root access using OTA Root Keeper (needs reboot I think for this step)
7. Unlocked boot loader using EZ-Unlock 1.2
I may have gotten these steps slightly out of order but this successfully allowed me to install the OTA (with a successful install message too) and got rid of my lock icon!!!
jkrueger2020 said:
Thank you!!!! That was exactly what I was hoping to find! I tried this out just for kicks to see if it would work for me and it did!
For anyone interested, here are the steps I took with my rooted device :
1. Lock the boot loader using EZ-Unlock 1.2
2. Using EZ-Recovery 2.2, I flashed the stock recovery
3. Backed up root access using OTA Root Keeper
4. Downloaded and installed the OTA
Note: The lock icon appeared still
5. Used EZ-Recovery 2.2. to flash CWM recovery in place of the stock recovery (I couldn't get it to flash the same tar.md5 file I used with ODIN though - don't know what kind of file EZ-Recovery needs - so I used the version of CMWR that it provided)
6. Restored root access using OTA Root Keeper (needs reboot I think for this step)
7. Unlocked boot loader using EZ-Unlock 1.2
I may have gotten these steps slightly out of order but this successfully allowed me to install the OTA (with a successful install message too) and got rid of my lock icon!!!
Click to expand...
Click to collapse
Almost worked flawlessly... I had to reboot from SuperSU to get root again.
I found the sdm thing to freez
smalrus said:
Almost worked flawlessly... I had to reboot from SuperSU to get root again.
Click to expand...
Click to collapse
I found the sdm thing to freez but could not find the fwupgrade one. I was also not able to fine the ez unlocker is that in the play store?
I am not sure if the sdm will block the update but now when I go to about phone and select software update it errors out. Also I am only rooted do I realy need to worry about the update? Also looking for a good stable rom. If anyone wants recomend one. Just got my phone like a week ago. Thank you guys. Xda has been great help.
joker66599 said:
I found the sdm thing to freez but could not find the fwupgrade one. I was also not able to fine the ez unlocker is that in the play store?
I am not sure if the sdm will block the update but now when I go to about phone and select software update it errors out. Also I am only rooted do I realy need to worry about the update? Also looking for a good stable rom. If anyone wants recomend one. Just got my phone like a week ago. Thank you guys. Xda has been great help.
Click to expand...
Click to collapse
Re-read the thread to find EZ Unlock, I'm fairly certain someone posted a link. I will say it's been removed from the Play Store for awhile now.
Freezing sdm 1.0 is all you really need to do. That's normal that it errors out now. You froze that setting so it won't be polling for an OTA nor allow you to manually search for an OTA. Whether you want the OTA or not is on you, there isn't much present that we do not already have in custom roms plus the OTA has already been rooted.
Sent from my SCH-I535 using xda app-developers app
This is what worked for me except I reversed step 5 and 6 (I edited the quote below to match what I did). Thanks!
jkrueger2020 said:
Thank you!!!! That was exactly what I was hoping to find! I tried this out just for kicks to see if it would work for me and it did!
For anyone interested, here are the steps I took with my rooted device :
1. Lock the boot loader using EZ-Unlock 1.2
2. Using EZ-Recovery 2.2, I flashed the stock recovery
3. Backed up root access using OTA Root Keeper
4. Downloaded and installed the OTA
5. Restored root access using OTA Root Keeper
6. Used EZ-Recovery 2.2. to flash TWRP recovery in place of the stock recovery
7. Unlocked boot loader using EZ-Unlock 1.2
I may have gotten these steps slightly out of order but this successfully allowed me to install the OTA (with a successful install message too) and got rid of my lock icon!!!
Click to expand...
Click to collapse
Stock rooted MB1 here w/ TWRP. Tried to update earlier and completely soft bricked my phone. Had to do some fancy work to get it back and restore.
Now I tried this process:
1. Lock the boot loader using EZ-Unlock 1.2
2. Using EZ-Recovery 2.2, I flashed the stock recovery
3. Backed up root access using OTA Root Keeper
4. Downloaded and installed the OTA
5. Restored root access using OTA Root Keeper
6. Used EZ-Recovery 2.2. to flash TWRP recovery in place of the stock recovery
7. Unlocked boot loader using EZ-Unlock 1.2
and when I get to the step of actually installing the OTA - it reboots into stock recovery - and about 15 seconds in it fails and shows the android guy on his back. lol
It actually boots back into the phone properly & says that the update failed. Status page shows the baseband got updated, but not the ROM. Any ideas?
thanks
Edit: Bah. It's the stupid 'E: Error in /tmp/sideload/package.zip error.' According to my searches there's no easy fix.
Edit #2: I just wound up dirty flashing the full stock root package from Scott & Beans. That worked.
I'm running the MD3 on the stock ROM and rooted. Now when I originally rooted my phone (using this guide: http://forum.xda-developers.com/showthread.php?t=2046439), I'm fairly confident that I did NOT unlock the bootloader and also installed the CWM Touch recovery. After the process was over I had an unlocked padlock image show up on my phone every time it booted.
Now, I tried to install the new update via OTA (I defrosted all apps I had frozen) and when the phone re-booted to start the update, I received the warning message "System software not authorized by Verizon...." and in the upper left hand corner it says in red, "Secure: Kernel". The phone will continue to boot to this message. When I try to boot into recovery, it goes to this message, not the CWM recovery. The only way to get out of that message is to boot into Odin mode and hit Vol DOWN to cancel.
SO.....what do I need to do in order to install this new update?
UPDATE: I unlocked via EZ Unlock and rebooted into recovery and this time I was able to get into my CWM recovery and updated the zip file posted on another thread in the general forum. All is well now.
Can I upgrade OTA after root but on STOCK ROM?
So if I'm rooted, but still running one of the VERIZON's STOCK ROM,
1. Can I upgrade OTA?
2. Will suck OTA upgrade unroot my phone?
Thanks
mandar_h said:
So if I'm rooted, but still running one of the VERIZON's STOCK ROM,
1. Can I upgrade OTA?
2. Will suck OTA upgrade unroot my phone?
Thanks
Click to expand...
Click to collapse
As of this moment, yes to both. The newest ota is VRBMF1 and you can still root/unlock that version just as easy as any other.
Hi,
Basically I'm trying to update to lollipop via OTA so I dont lose all my data, but whenever I try and install the update, my phone reboots into TWRP, but then it just goes to the main menu and doesn't update anything.
Just wondering how I should update? Do I have to install the stock recovery? Or will that make me lose my data too?
Cheers,
Jack
I don't think it's a very good idea to update ota when your phone is rooted. I don't think it will update either because you don't have the stock recovery.
What I did personally... I backed up my 4.4 ROM and followed the instructions on bixie's stock ROM. I didn't delete my internal storage and everything carried over.
If you don't have the latest twrp. You can either download flashify from the market or you can use adb/fast boot.
Sent from my Nexus 5 using XDA Free mobile app
So I used TWRP to install that rom but lost my root in the process. Any idea's what I screwed up?
I made sure to backup using TWRP before starting.
Root is removed as the OTA removes it, just root again (if you read any of the guide threads on here you'd know this)