I have a rooted and unlocked VZW Galaxy Nexus and I wish to flash the stock ROM and unroot, then lock the boot loader in order to download the OTA update, will this wipe all my data? If so, how would I restore the backed up files once I am back to stock?
This will wipe all your data.
You will still be able to update using the OTA method with or without root, so use TitaniumBackup to backup all your stuff and restore when you are back on stock ROM.
i think relocking bootloader does not wipe userdata.
that said, op, you dont need to relock bootloader to take the ota.
sent from my i9250
stevejr47 said:
I have a rooted and unlocked VZW Galaxy Nexus and I wish to flash the stock ROM and unroot, then lock the boot loader in order to download the OTA update, will this wipe all my data? If so, how would I restore the backed up files once I am back to stock?
Click to expand...
Click to collapse
What ROM are you currently using? If you are running stock IMM76K, no need to re-flash the stock ROM again.
Root makes no difference, neither does an unlocked bootloader.
See screenshot, I just wanted to get the official update without too much hassle.
Sent from my Galaxy Nexus using Tapatalk 2
stevejr47 said:
See screenshot, I just wanted to get the official update without too much hassle.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Based on your screen shot, I can point you in the right direction. Although you may think it is a lot of hassle, it isn't. Follow the steps to flash mysid IMM76K in the "flash" link in my signature. Then you should get prompted for the OTA -- if not, follow the steps in the "update" link in my signature to manually update your device (after doing the procedure in the "flash" link). If things are not clear, have a read of the "basics" link.
I don't advocate using shortcuts, as people come back when the next update comes around asking similar questions yet again.
Locking the bootloader will not wipe your data. I did it before with no problems whatsoever.
bk201doesntexist said:
i think relocking bootloader does not wipe userdata.
that said, op, you dont need to relock bootloader to take the ota.
sent from my i9250
Click to expand...
Click to collapse
I mean if he flash stock, phone will be nuked.
Beamed from my Grouper.
Not sure what you mean by "nuked", but I did the OTA update successfully after reverting back to 4.0.4 and unrooting. I am stil unlocked, but when i was proceeding to reroot, everything seemed to work, but when i went to the superuser app to regain root access, it fails. Also, not sure if it is a related issue, but when i try to save a screenshot or take a picture, the picture will not save to the gallery, it says "Cannot capture screenshot, storage may be in use."
efrant said:
Based on your screen shot, I can point you in the right direction. Although you may think it is a lot of hassle, it isn't. Follow the steps to flash mysid IMM76K in the "flash" link in my signature. Then you should get prompted for the OTA -- if not, follow the steps in the "update" link in my signature to manually update your device (after doing the procedure in the "flash" link). If things are not clear, have a read of the "basics" link.
I don't advocate using shortcuts, as people come back when the next update comes around asking similar questions yet again.
Click to expand...
Click to collapse
Awesome guides.
fmcfad01 said:
Awesome guides.
Click to expand...
Click to collapse
Now if we could only get people to read them :S
stevejr47 said:
Not sure what you mean by "nuked", but I did the OTA update successfully after reverting back to 4.0.4 and unrooting. I am stil unlocked, but when i was proceeding to reroot, everything seemed to work, but when i went to the superuser app to regain root access, it fails. Also, not sure if it is a related issue, but when i try to save a screenshot or take a picture, the picture will not save to the gallery, it says "Cannot capture screenshot, storage may be in use."
Click to expand...
Click to collapse
Any help on this?
stevejr47 said:
Any help on this?
Click to expand...
Click to collapse
How did you try to root? Did you follow the links I gave you?
http://goo.gl/wgDF2
stevejr47 said:
Not sure what you mean by "nuked", but I did the OTA update successfully after reverting back to 4.0.4 and unrooting. I am stil unlocked, but when i was proceeding to reroot, everything seemed to work, but when i went to the superuser app to regain root access, it fails. Also, not sure if it is a related issue, but when i try to save a screenshot or take a picture, the picture will not save to the gallery, it says "Cannot capture screenshot, storage may be in use."
Click to expand...
Click to collapse
What i mean is if you flash a stock image that you downloaded from Google Dev website, your virtual SD card will be wiped if you flash the userdata.img(this is your /data/ i believe).
Just follow Efrant's instructions, disregard what i said.
efrant said:
How did you try to root? Did you follow the links I gave you?
Click to expand...
Click to collapse
Yes, I sucessfully rerooted using those links, still having the picture/screenshot issue though where it is unable to save pictures and screenshots
stevejr47 said:
Yes, I sucessfully rerooted using those links, still having the picture/screenshot issue though where it is unable to save pictures and screenshots
Click to expand...
Click to collapse
try this
danger-rat said:
If you have any directories/files that you can't modify or delete, then boot into CWM recovery, plug in the USB cable, go into adb shell. Also make sure that /data is mounted in the CWM mounts menu. Then:
cd /data/media
chown -R media_rw.media_rw *
Click to expand...
Click to collapse
tried that, no dice
I am just hoping for a fix without wiping everything and starting over, but I'll do that if it is absolutely necessary
Sent from my Galaxy Nexus using Tapatalk 2
so i got a nexus today .. however i found it was already boot unlocked and pre rooted .. and had sm fkd up apex mod ics .. how do i revert to stock ? so i cont to t official updates ?
kunalwanvari said:
so i got a nexus today .. however i found it was already boot unlocked and pre rooted .. and had sm fkd up apex mod ics .. how do i revert to stock ? so i cont to t official updates ?
Click to expand...
Click to collapse
oh come on, seriously??? how lazy can people be these days. read the rules, search before you post.
and did you even read this thread at all?!
follow links in efrant's signature, reflash official google factory images with fastboot.
sent from my i9250
Related
Go here for a much better proceedure:
http://androidforums.com/incredible...ng-nov-ota-rooted-incredible.html#post1876792
dsb9938 said:
Rooted Inc, otherwise factory ROM. S-OFF in effect.
If I flash a factory recovery, will the OTA update take?
Can I not simply reflash ClockWork after the update?
Thanks guys.
Click to expand...
Click to collapse
Im pretty sure it will take if you've got factory recovery. It doesn't seem to be as secure as the vaunted froyo update was.
And yes, you can simply reflash clockwork, but from bootloader, as a PB32IMG.zip
S-Off is wonderful.
Fretless said:
Im pretty sure it will take if you've got factory recovery. It doesn't seem to be as secure as the vaunted froyo update was.
And yes, you can simply reflash clockwork, but from bootloader, as a PB32IMG.zip
S-Off is wonderful.
Click to expand...
Click to collapse
What if I'm rooted without stock recovery?
thevoiceless said:
What if I'm rooted without stock recovery?
Click to expand...
Click to collapse
When you get the update nag, you ignore it, flash the stock recovery, which I am in process of getting now, then apply the patch, then reflash Clockwork.
Fretless said:
Im pretty sure it will take if you've got factory recovery. It doesn't seem to be as secure as the vaunted froyo update was.
And yes, you can simply reflash clockwork, but from bootloader, as a PB32IMG.zip
S-Off is wonderful.
Click to expand...
Click to collapse
Thanks, now to get the stock recovery from the RUU. Wee Haw!!!!
dsb9938 said:
When you get the update nag, you ignore it, flash the stock recovery, which I am in process of getting now, then apply the patch, then reflash Clockwork.
Click to expand...
Click to collapse
I'm still pretty new to this, how should I go about getting the stock recovery and flashing it? All I've done is use Unrevoked and Unrevoked Forever, then install ClockworkMod via Rom Manager, so pretty much everything has been done for me :/
thevoiceless said:
I'm still pretty new to this, how should I go about getting the stock recovery and flashing it? All I've done is use Unrevoked and Unrevoked Forever, then install ClockworkMod via Rom Manager, so pretty much everything has been done for me :/
Click to expand...
Click to collapse
I've asked in a couple places for the stock recovery. If/when I get it I will post a short how to.
I just don't want to lose everything on my phone to get this update.
I did a NAND backup and installed the update manually and there are several improvements I would like to have, such as significantly reduced charging time. But right now, without a custom ROM, the only way to get it is the RUU, and that wipes the phone.
Dennis
dsb9938 said:
I've asked in a couple places for the stock recovery. If/when I get it I will post a short how to.
I just don't want to lose everything on my phone to get this update.
I did a NAND backup and installed the update manually and there are several improvements I would like to have, such as significantly reduced charging time. But right now, without a custom ROM, the only way to get it is the RUU, and that wipes the phone.
Dennis
Click to expand...
Click to collapse
Awesome! Keep me updated
Please Hold.
dsb9938 said:
Please Hold.
Click to expand...
Click to collapse
What do you mean?
Go here for a much better proceedure:
http://androidforums.com/incredible...ng-nov-ota-rooted-incredible.html#post1876792
I am stuck at the bootloader not finding update.zip
any ideas?
stock 2.2 rooted s-off
I am assuming that you can't just apply the update.zip from clockwork because it fails to find the stock apps (which it is trying to update, such as AppSharing, and Flickr, etc.) that I removed.
p.s. step 7 is worded in a misleading way, although I understood what you meant. (reads like - rename the deleted file)
thanks for your help
JDubbz said:
I am stuck at the bootloader not finding update.zip
any ideas?
stock 2.2 rooted s-off
I am assuming that you can't just apply the update.zip from clockwork because it fails to find the stock apps (which it is trying to update, such as AppSharing, and Flickr, etc.) that I removed.
p.s. step 7 is worded in a misleading way, although I understood what you meant. (reads like - rename the deleted file)
thanks for your help
Click to expand...
Click to collapse
Having this issue with somebody else. I'm not sure if you can name it PB31IMG.zip or not, but you can try. Worst care, it doesn't load that way either.
I'm helping somebody else with the same issue right now, but his phone is totally hosed up, so I'm taking him back to stock 2.2 first. He has a good Titanium backup, so he won't lose anything.
If anybody else knows why the loader might ignore an update.zip please let me know.
JDubbz said:
I am stuck at the bootloader not finding update.zip
any ideas?
stock 2.2 rooted s-off
I am assuming that you can't just apply the update.zip from clockwork because it fails to find the stock apps (which it is trying to update, such as AppSharing, and Flickr, etc.) that I removed.
p.s. step 7 is worded in a misleading way, although I understood what you meant. (reads like - rename the deleted file)
thanks for your help
Click to expand...
Click to collapse
Okay, I have confirmed that you may perform "install sd/update.zip" from ROM Manager. It does work.
I'm still confused; do I have to have the stock recovery to do this?
I am not sure of these steps because I have read the threads from here and the post you put on Android forums as well and both threads are mentioning some issues.
Some posts state payload-update is unneccesary.
Some posts state that these steps are failing.
The post I am most concerned about states that "Rooted STOCK ONLY" means you can't have removed any bloatware either before doing this update. I have several apps removed, do I have to restore them before I take these steps?
Also not sure why folks are asking if they must have stock recovery. The instructions don't say anything about that.
I have noticed that the nagging has stoped on my dinc however if I go to the about update section in setup I find it states that the update has been successfully downloaded and is ready to install. Will this try to install the next time I boot the phone or is OK to boot?
Edit: Forgot to mention Some posts state that the process fails and you have to wait a few hours to continue, that's confusing and not in the instructions.
In summary
1) Do you have to re-install bloatware to make these steps work?
2) Is payload-update really necessary? What does each install in these steps do?
3) Does the process fail at some point if you don't allow the device to sit for a while, if so what step should you let it sit? It would be nice if someone understood this part also, anyone have a possible reason for this requirement?
I was asking if stock recovery is required because I've been told that OTAs won't install correctly if you don't. I was wondering if that still applied.
I got the update notification tonight and I clicked for it to install, and it counted down from ten seconds and said it was going to reboot and install updates, but it never did reboot. I'm guessing this is because I have unrevoked recovery? My gf's non rooted phone did get the update tonight as well, and hers installed without a hitch.
Sent from my HTC Incredible «•» Rooted/S-off/Froyo 2.2 «•»
Rooted, Stock 2.2, S-off, Clockwork; some bloatware removed
Install initiated through clockwork halted on vznav.apk, so I'm guessing it needs the original bloatware. I know that I should have backed it up but I guess my hatred of VZ pushiness got the better of me. Anyone have a work-around?
BrooklynAlex said:
Rooted, Stock 2.2, S-off, Clockwork; some bloatware removed
Install initiated through clockwork halted on vznav.apk, so I'm guessing it needs the original bloatware. I know that I should have backed it up but I guess my hatred of VZ pushiness got the better of me. Anyone have a work-around?
Click to expand...
Click to collapse
I guess we need someone to share the bloat apk's; I removed some of them without backing up, too :/
So I'm running the stock OS and now it won't install the OTA update. I'm unlocked and rooted and the update downloads, then the phone reboots. I see the install starts and runs for about 3 seconds and then it stops with the red triangle exclamation point.
What's going on, anyone else having this issue?
How many times per day does this thread need to be made?
You're either going to have to flash just the update via fastboot on your own, or unroot and accept the OTA normally.
Well I appreciate the answer, sorry to be a bother...
Anyway, is this the way it's always going to be since I'm rooted and unlocked? Where will I be able to download the OTA updates so I can flash manually with fastboot?
It won't work if you have ClockworkMod's recovery, you need the stock recovery.
Sent from my Galaxy Nexus using XDA App
105437 said:
So I'm running the stock OS and now it won't install the OTA update. I'm unlocked and rooted and the update downloads, then the phone reboots. I see the install starts and runs for about 3 seconds and then it stops with the red triangle exclamation point.
What's going on, anyone else having this issue?
Click to expand...
Click to collapse
Dowload from http://code.google.com/android/nexus/images.html. It needs 7Zip to uncompress the file. Once decompressed it has a file with no extension, decrompress that again and you will have the several file.
The just power the phone off and power back on with the volume up and down pressed. Same as when you rooted it.
Then run these commands:
fastboot flash bootloader bootloader-maguro-primekk15.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-maguro-i9250xxkk6.img
fastboot reboot-bootloader
sleep 5
fastboot update image-yakju-icl53f.zip
This will not wipe your phone!
You will need to root it again.
This is what I just did and works prefectly!
Root and unlocked bootloader shouldn't prevent you from installing if you still have stock recovery. If you have ClockworkMod recovery instead, you can use that to flash it manually. If your phone downloaded the update zip, it should be located in /cache.
You'll probably have to re-root after applying the update, regardless of how you install it.
Thanks for the replies guys! I guess I'd like to stay unlocked & rooted and be able to get OTA updates. Is there any risk in doing this? If not, how do I uninstall CWM?
Thanks again!
105437 said:
Thanks for the replies guys! I guess I'd like to stay unlocked & rooted and be able to get OTA updates. Is there any risk in doing this? If not, how do I uninstall CWM?
Thanks again!
Click to expand...
Click to collapse
I believe that in rom manager you should be able to set the recovery back to the default.
Bad Liar said:
I believe that in rom manager you should be able to set the recovery back to the default.
Click to expand...
Click to collapse
ROM Manager only has the option to flash ClockworkMod, not stock recovery. But the stock recovery can be extracted from the Google factory images and flashed with fastboot.
I have same problem like yours, how can i solved it? my device is SE WT19i
Happened to me as well - but I also ran into problems initially trying to do the image upgrades, because I had ended up changing a couple values in the build.prop file (wifi scan time, and disabling the boot animation). I'm assuming changes like that would cause the OTA update to fail, if doing it manually fails as well?
Also remember when trying to resolve my issue, reading through other people who went through similar sequences.
Had unlocked/rooted. Tried OTA - got the red warning symbol.
Tried installing the zip from sdcard through CWM but ran into various warnings/errors because of minor tweaks that either they had done, or something that had been installed had done.
Try mskip's GNex Toolkit. Super easy to use and everything explained in the thread. The guy's a genius!
http://forum.xda-developers.com/showthread.php?t=1392310
Think option 10 will reflash stock recovery.
Dark Tapatalk (GSM Galaxy Nexus)
+1. GNex Toolkit made my life worth living, I got the OTA 4.0.4 update (IMM76I), and I'm rooted and unlocked.
I also highly recommend GNex Toolkit. It has an option to restore the factory recovery and also helps you to get root again after update.
Voodoo OTA Root Keeper only helps partially.
ceribaen said:
Happened to me as well - but I also ran into problems initially trying to do the image upgrades, because I had ended up changing a couple values in the build.prop file (wifi scan time, and disabling the boot animation). I'm assuming changes like that would cause the OTA update to fail, if doing it manually fails as well?
Also remember when trying to resolve my issue, reading through other people who went through similar sequences.
Had unlocked/rooted. Tried OTA - got the red warning symbol.
Tried installing the zip from sdcard through CWM but ran into various warnings/errors because of minor tweaks that either they had done, or something that had been installed had done.
Click to expand...
Click to collapse
Each if those warnings that you are getting is because something is not stock. You will need to download the appropriate stock file for each of those warnings. I have already posted the stock build.prop and boot image in the main IMM76I update thread. If you need others, instructions can be found in the update link in my signature.
Sent from my Galaxy Nexus using Tapatalk 2
philipdeane said:
Try mskip's GNex Toolkit. Super easy to use and everything explained in the thread. The guy's a genius!
http://forum.xda-developers.com/showthread.php?t=1392310
Think option 10 will reflash stock recovery.
Dark Tapatalk (GSM Galaxy Nexus)
Click to expand...
Click to collapse
bingefister said:
+1. GNex Toolkit made my life worth living, I got the OTA 4.0.4 update (IMM76I), and I'm rooted and unlocked.
Click to expand...
Click to collapse
toxaris said:
I also highly recommend GNex Toolkit. It has an option to restore the factory recovery and also helps you to get root again after update.
Voodoo OTA Root Keeper only helps partially.
Click to expand...
Click to collapse
All of you guys recommending using a toolkit: do you even understand the OP's issue? I don't think so, otherwise you would know that a toolkit won't do what he needs done.
My opinion:
On an unrelated note: you need to figure out how to do things manually before you start using toolkits, otherwise you will never learn anything. There is a reason they teach you long division in school before letting you use a calculator...
Sent from my Galaxy Nexus using Tapatalk 2
My USB connector is broken on my nexus. Amazon has sent me a replacement, which I have at hand. I would like to lock my boot loader on my nexus with the broken USB connector before sending it back to amazon.
Any thoughts as to how I may accomplish this?
If not, can you at the least convince me amazon won't care that my boot loader is unlocked?
EDIT: Never mind, it seems the awesome developers have figured out ways to relock the bootloader.
https://play.google.com/store/apps/details?id=aperture.ezekeel.gladoscontrol
Potentially.
MAYBE.
Just Maybe you can re-lock with this.
I'm not sure if it requires SU or not.
And I haven't given anyone this advice yet, so you'll be the first.
But as the above poster said...
Mobile Odin first.
mt6272 said:
My USB connector is broken on my nexus. Amazon has sent me a replacement, which I have at hand. I would like to lock my boot loader on my nexus with the broken USB connector before sending it back to amazon.
Any thoughts as to how I may accomplish this?
If not, can you at the least convince me amazon won't care that my boot loader is unlocked?
Click to expand...
Click to collapse
Not sure if Amazon will even care if it is locked or not.
Thanks to AdamOutler and a few others, you can re-lock the bootloader without being plugging into a computer, but root (and busybox) is required.
Download the attachment from this post, and extract the files to the root of /sdcard. Then open a terminal emulator on your device and type the following commands:
su
dd if=/sdcard/param.lock of=dev/block/platform/omap/omap_hsmmc.0/by-name/param
That should re-lock your bootloader.
Now you need to make sure you are running a stock ROM and stock recovery.
Once that is done, you can then remove busybox, and finally, you can delete /system/app/Superuser.apk and su.
EDIT: For those that are curious, to unlock your bootloader without wiping, replace the command above with this:
su
dd if=/sdcard/param.unlock of=dev/block/platform/omap/omap_hsmmc.0/by-name/param
efrant said:
Not sure if Amazon will even care if it is locked or not.
Thanks to AdamOutler and a few others, you can re-lock the bootloader without being plugging into a computer, but root (and busybox) is required.
Download the attachment from this post, and extract the files to the root of /sdcard. Then open a terminal emulator on your device and type the following commands:
su
dd if=/sdcard/param.lock of=dev/block/platform/omap/omap_hsmmc.0/by-name/param
That should re-lock your bootloader.
Now you need to make sure you are running a stock ROM and stock recovery.
Once that is done, you can then remove busybox, and finally, you can delete /system/app/Superuser.apk and su.
Click to expand...
Click to collapse
Awesome efrant, thank you.
I'll reference to this later if need be.
efrant said:
Not sure if Amazon will even care if it is locked or not.
Thanks to AdamOutler and a few others, you can re-lock the bootloader without being plugging into a computer, but root (and busybox) is required.
Download the attachment from this post, and extract the files to the root of /sdcard. Then open a terminal emulator on your device and type the following commands:
su
dd if=/sdcard/param.lock of=dev/block/platform/omap/omap_hsmmc.0/by-name/param
That should re-lock your bootloader.
Now you need to make sure you are running a stock ROM and stock recovery.
Once that is done, you can then remove busybox, and finally, you can delete /system/app/Superuser.apk and su.
Click to expand...
Click to collapse
couldnt you take it a step further?
doesnt mobile odin work properly even if the bootloader is locked?
Zepius said:
couldnt you take it a step further?
doesnt mobile odin work properly even if the bootloader is locked?
Click to expand...
Click to collapse
Yeah, he could use mobile odin to flash to stock (and thus, no need to remove custom recovery, root, etc.), but mobile odin will not re-lock his bootloader.
efrant said:
Yeah, he could use mobile odin to flash to stock (and thus, no need to remove custom recovery, root, etc.), but mobile odin will not re-lock his bootloader.
Click to expand...
Click to collapse
ah i figured you could still use mobile odin to restore to stock with the bootloader already locked when you first run it.
ive never used it so i guess i didnt understand completely what it did.
Zepius said:
ah i figured you could still use mobile odin to restore to stock with the bootloader already locked when you first run it.
ive never used it so i guess i didnt understand completely what it did.
Click to expand...
Click to collapse
No, you're right. You CAN use mobile odin with a bootloader already locked. However, you need root to use it.
efrant said:
No, you're right. You CAN use mobile odin with a bootloader already locked. However, you need root to use it.
Click to expand...
Click to collapse
so you could then change the param file, which locks the bootloader, then use mobile odin to go back to 100% stock and still have a locked bootloader.
Zepius said:
so you could then change the param file, which locks the bootloader, then use mobile odin to go back to 100% stock and still have a locked bootloader.
Click to expand...
Click to collapse
Yes. That's what I was trying to say in my earlier post, but I guess it wasn't clear. Mobile Odin will not change the lock state of the bootloader, but will work in either a locked state or an unlocked state, assuming you have root.
More details on my phone: It is rooted, running aokp m5 & franco m3. It sounds like there is a solution to my problem contained within this thread - however, things are a bit hazy to me when it comes to what order to perform these operations and which apps to use when.
My thanks to the first person who compiles a step-by-step (albeit brief and concise) guide to unrooting, re-locking the bootloader, and restoring to stock WITHOUT being connected to the computer!
I don't know how you have broken USB, but my friend had it broken - it didn't want to charge longer than few seconds, connection to PC was extremely inconsistent...
Samsung told him that it happens on SGNs sometimes and that it is caused by oxidation of USB. It isn't covered by warranty.
But he solved it very simply - you can clean the USB by soft toothbrush and it works like a charm again. Hope this helps you.
mt6272 said:
More details on my phone: It is rooted, running aokp m5 & franco m3. It sounds like there is a solution to my problem contained within this thread - however, things are a bit hazy to me when it comes to what order to perform these operations and which apps to use when.
My thanks to the first person who compiles a step-by-step (albeit brief and concise) guide to unrooting, re-locking the bootloader, and restoring to stock WITHOUT being connected to the computer!
Click to expand...
Click to collapse
It is not that difficult, and I'm sure you do not need a step by step.
I haven't tried this on my device, as I don't really feel like wiping, but:
1) Lock your bootloader as per my post above. EDIT: I just looked at Mobile Odin, and it seems that Chainfire has implemented flashing the param partition as well in his app, so you can skip this step and go straight to step two.
2) Download the param file from the same post mentioned in step 1, and extract it to the root of your /sdcard.
3) Rename the param.lock file to param.img
4) Download version of the stock ROM for your device from here, e.g., if you have a GSM device, download the maguro factory image, if you have a Verizon device, download the toro factory image.
5) Extract the system, boot, userdata and recovery images from within and place them on the root of your /sdcard.
6) Buy Mobile Odin Pro from the Play Store. [You can use get the free version from the XDA thread here, but it needs setting up, and I'm not going to guide you through that.]
7) Run Mobile Odin Pro and follow the instructions here. It should be pretty obvious what you need to do.
I'm running AOKP 4.2, their latest release. I, too, have a failed USB connection. I downloaded the latest recovery from the link for my Verizon Toro. When I used the paid version of Mobile Odin, it says "partition could not be found in file". I tried the older, ICS image, but it just factory reset my AOKP install, not reflash to stock. So far, I've locked the boot loader, but I can't get rid of AOKP. I think it is because Mobile Odin doesn't reflash the bootloader, which I learned after my attempt, and I attempted to Odin back to factory ICS, which is a different bootloader. My other thought was to get into TWRP and flash an older AOKP ICS build, which flashes the older bootloader(right??), and try again, but I have no recovery, stock or otherwise after my Mobile Odin attempt. Any advice at this point? Should I just send it to Verizon as-is and let the chips fall where they may?
Quick update: I used Goomanager from the market to instantly flash TWRP. BAM! Recovery restored! I just finished flashing AOKP Jellybean Milestone 1, which is 4.1.2. I also figured out my JRO030 issue. It was a bad .tar file. When I browsed it with Winrar, it containted another file with the same name and no extension. I found another .tar file with the entire file structure inside. I'm currently booting into AOKP M1 as I type. I'll attempt to Mobile Odin with the JRO030 factory image (4.1.1) over 4.1.2 and then update this thread again. I hope I can save others some heartache.
The JRO030 update said something about "unable to extract update script". So I gave up on Jelly Bean and went futher back. I found an old AOKP ICS build, Milestone 6, flashed to that and used the monster 470 mb 4.0.2 update file that was linked to in a galaxynexusforums post with Mobile Odin. TADA! It worked like a charm. No root. Stock software. The only downside is that recovery is broken. It shows an Android guy with a red exclamation point over his belly. Whatever. I'm on 4.0.2 stock VZW software. That's all I care about. Let me know if anyone needs help with this.
scubamike said:
Snip
The only downside is that recovery is broken. It shows an Android guy with a red exclamation point over his belly. Whatever. I'm on 4.0.2 stock VZW software. That's all I care about. Let me know if anyone needs help with this.
Click to expand...
Click to collapse
That IS the stock recovery.
Sent from my Nexus 4 using Tapatalk 2
efrant said:
That IS the stock recovery.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I thought it was too, but, just for the heck of it, I tried taking the OTA. It rebooted and stuck on the android guy with the red exclamation. I had to pull the battery.
It is the stock recovery and no, you did not have to pull the battery. The Android with the red triangle is the main screen of the stock recovery . To access the menu from the main screen, hold power and press volume up. This is covered in at least 2 of the stickies in the General section.
Sent from my Nexus 4 using Tapatalk 2
I'm trying to update to 4.1.2 and I'm getting "apply_patch_check("system/lib/libwebrtc_audio_preprocessing.so" as not being the original file.
I have no idea what changed that or how I can return it to normal. Any ideas?
Not enough information.
Was your phone completely stock and unaltered before you tried going to 4.1.2? What method are you using to get to 4.1.2?
garyd9 said:
Not enough information.
Was your phone completely stock and unaltered before you tried going to 4.1.2? What method are you using to get to 4.1.2?
Click to expand...
Click to collapse
I was on stock, then used CF-AutoRoot. Pretty much nothing besides that. According to other threads, if I used voodoo OTA and just unfreeze the AT&T apps it should work, it has for them.
Would this be due to some other root app?
OmegaNemesis28 said:
I was on stock, then used CF-AutoRoot. Pretty much nothing besides that. According to other threads, if I used voodoo OTA and just unfreeze the AT&T apps it should work, it has for them.
Would this be due to some other root app?
Click to expand...
Click to collapse
Okay.. so you were NOT completely stock. You also didn't mention what method you used for the update. Was it pushed to you over the air, or did you download it and copy it to your phone?
If you are following instructions from other threads on the update, then you might consider posting this question on one of those other threads.
I can tell you what *I* did, but I won't support that: I used ODIN to get my phone 100% back to stock (ODIN to replace the stock firmware/kernel/recovery, factory reset to erase the phone) and then installed the update via external SD. After the update was installed, I used ODIN to replace recovery, and then used that recovery to re-root and restore my backups.
Take care
Gary
garyd9 said:
Okay.. so you were NOT completely stock. You also didn't mention what method you used for the update. Was it pushed to you over the air, or did you download it and copy it to your phone?
If you are following instructions from other threads on the update, then you might consider posting this question on one of those other threads.
I can tell you what *I* did, but I won't support that: I used ODIN to get my phone 100% back to stock (ODIN to replace the stock firmware/kernel/recovery, factory reset to erase the phone) and then installed the update via external SD. After the update was installed, I used ODIN to replace recovery, and then used that recovery to re-root and restore my backups.
Take care
Gary
Click to expand...
Click to collapse
Sorry.
And no, I guess not completely stock. Just CF-AutoRoot.
I tried both OTA update and copying the update to my /cache and using ODIN. Where is where I was getting the error.
If I flash back to stock and don't factory reset/erase my phone, would this still fix any modded files like audio_preprocessing in my /system/? Flashing back to a stock ROM won't erase my apps/settings correct? I'm still pretty new to this.
What backup method did you use? ADB nandroid or something like Titanium?
OmegaNemesis28 said:
I tried both OTA update and copying the update to my /cache and using ODIN. Where is where I was getting the error.
Click to expand...
Click to collapse
That statement is confusing. You got the error trying the OTA or when updating via a manual copy to /cache?
OmegaNemesis28 said:
If I flash back to stock and don't factory reset/erase my phone, would this still fix any modded files like audio_preprocessing in my /system/?
Click to expand...
Click to collapse
If you flash back to stock via ODIN, it should completely rewrite everything in /system to revert it back to factory (as well as unroot your device.)
OmegaNemesis28 said:
Flashing back to a stock ROM won't erase my apps/settings correct? I'm still pretty new to this.
Click to expand...
Click to collapse
It shouldn't, but that doesn't mean it won't. That's why I'm a big fan of backing things up.
OmegaNemesis28 said:
What backup method did you use? ADB nandroid or something like Titanium?
Click to expand...
Click to collapse
I have an external memory card and use TWRP (replacement recovery) to backup. I ALSO backup with titanium backup pro to the external sdcard.
Gary
A summary of my situation:
- Got Pixel XL
-Downloaded snapchat
-Logged into snapchat
-Rooted phone
-Accidentally logged out of snapchat
-Snapchat checks for root before it lets you log in
-I cannot log in until I first unroot
I have tried searching the Pixel XL reddit as well as the XDA Pixel XL forums, but I could not find a guide/program for unrooting the phone. If anyone knows how I could go about this, please let me know. Thank you.
Open SuperSu, cgo to settings, click on Unroot, reboot. Done
Why does Snapchat not like root? Been reading it a lot on other posts but not why.
FFutstuFF said:
A summary of my situation:
- Got Pixel XL
-Downloaded snapchat
-Logged into snapchat
-Rooted phone
-Accidentally logged out of snapchat
-Snapchat checks for root before it lets you log in
-I cannot log in until I first unroot
I have tried searching the Pixel XL reddit as well as the XDA Pixel XL forums, but I could not find a guide/program for unrooting the phone. If anyone knows how I could go about this, please let me know. Thank you.
Click to expand...
Click to collapse
you cant youre stuck forever
*sarcasm*
ZeroHart said:
Open SuperSu, cgo to settings, click on Unroot, reboot. Done
Click to expand...
Click to collapse
This doesn't work. Uninstall fails.
I mean, ultimately you can choose to flash the factory image or sideload the full OTA update which will reset you back to stock. (Be careful with the flashall bat file in the factory image...edit it and remove the -w from the fastboot update command if you don't want to wipe data). That is a cannon, yes.
FFutstuFF said:
This doesn't work. Uninstall fails.
Click to expand...
Click to collapse
Just flash a kernel and you should lose root
jjayzx said:
Why does Snapchat not like root? Been reading it a lot on other posts but not why.
Click to expand...
Click to collapse
Makes it easier to get around notifications that you have watched a post or the notification that you have performed a screen shot.
Instead of going after the exploits individually they go after the "root" of the cause. Pun so intended.
cwalker0906 said:
Just flash a kernel and you should lose root
Click to expand...
Click to collapse
Oh that's right, Chainfire fixed it so it's a boot img only patch now. Yea, do this and you're good to go.
Say I needed to remove root and relock the bootloader to return this phone in exchange for the 128gb model. Is that possible? I've read that relocking will instantly brick my phone. I'm nervous about doing anything to this phone now haha.
Anthony825 said:
Say I needed to remove root and relock the bootloader to return this phone in exchange for the 128gb model. Is that possible? I've read that relocking will instantly brick my phone. I'm nervous about doing anything to this phone now haha.
Click to expand...
Click to collapse
Relocking if you have modified it MAY soft brick it. If you changed anything just go ahead and restore using a stock image and then relock.
The only thing I did after unlocking it is root it. Nothing custom. I downloaded titanium backup, granted it root access and that's it....didn't do anything else with it. Theoretically I should be able to remove root and relock the bootloader correct?
Anthony825 said:
The only thing I did after unlocking it is root it. Nothing custom. I downloaded titanium backup, granted it root access and that's it....didn't do anything else with it. Theoretically I should be able to remove root and relock the bootloader correct?
Click to expand...
Click to collapse
Any luck with un-rooting it?
Haven't attempted it yet. Going to call around at all the Verizon in my area to see if any of them have the 128gb in either size pixel on my break at work today first. If they do, then I'll attempt unroot this evening and let you guys know what happens.
Anthony825 said:
The only thing I did after unlocking it is root it. Nothing custom. I downloaded titanium backup, granted it root access and that's it....didn't do anything else with it. Theoretically I should be able to remove root and relock the bootloader correct?
Click to expand...
Click to collapse
Why not just download the factory image flash back to stock. Longer process because you have to download that file but ultimately you probably want the stock image laying around just in case anyway..
https://developers.google.com/android/images
I have it downloaded as of last night. That's what I'll end up doing if I find a store with the 128gb in stock.
Turns out there are no stores around in my whole state that have the 128gb in stock. So no point in removing root for me unless I want my bluetooth connectivity with my car back.
Just flash the stock boot.img from the version you're currently on. Then uninstall the SU app.
spaceman860 said:
Just flash the stock boot.img from the version you're currently on. Then uninstall the SU app.
Click to expand...
Click to collapse
I can confirm that this works
I downloaded the factory image: marlin-nde63v-factory-a66866ba.zip
Found boot.img inside and extracted it and then flashed by
fastboot flash boot_a /path/to/boot.img
fastboot flash boot_b /path/to/boot.img
Snapchat now opens then i rerooted via chainfires steps here
https://plus.google.com/+Chainfire/posts/CBL8pnKtA8F?sfc=true
I had rooted with with boot to root. I use fastboot to flash stock boot.img to boot_a and boot_b. When my phone rebooted it wiped it self. Was I supposed to get boot.img from the OTA image> Ws there something that I could have done to avoid the wipe? I'm very sad to have lost lots of data.
Thanks.
~Josh