Related
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
Hi all,
Bit of a noob query, apologies.
I had never rooted a device until last night when I took the plunge with WugFresh's (thankyou so much) program. Great program had an issue with the adb drivers (turned out I needed more power for the USB port) hence I plugged the USB into the rear port and it magically appeared and installed, thus if you have problems installing the driver make sure you are plugged into the rear.
But I am now on the 4.04 google factory flash.
Now my query is, now I am on this 4.04, I presume I am no longer rooted. Can I use WugFresh's program to root the phone again or do I have to wait for another update to the program?
I was rather twitchy during rooting, expecting power cuts across the UK, earth tremor to knock the lead out at the wrong time, aliens to come down and screw it up etc that I dare not try it (don't really understand what I did even though it has worked)...
There is a program on now called superuser, but does not seem to have root access, so I presume I am not rooted now??
Any help would be appreciated.
Thanks
Darren
I did refer to a guide but can't post the link to it.
this is why you don't use toolkits... when you use them you dont know what's going on.
fastboot oem unlock (bootloader unlocked already?)
fastboot flash recovery <get clockwork recovery img>
get su.zip (find it on forum)
flash it in clockwork
you have root.
alternatively, you can flash a custom rom.
zephiK said:
this is why you don't use toolkits... when you use them you dont know what's going on.
fastboot oem unlock (bootloader unlocked already?)
fastboot flash recovery <get clockwork recovery img>
get su.zip (find it on forum)
flash it in clockwork
you have root.
alternatively, you can flash a custom rom.
Click to expand...
Click to collapse
Yip, I can agree with the statement, I don't know what was happening.
However, I could follow some of it, I think the bootloader is unlocked (can boot into with vol and off switch), I have clockwork and su, the installer did flash with clockwork.
Wonder if I am indeed rooted then???
pittnuma said:
Yip, I can agree with the statement, I don't know what was happening.
However, I could follow some of it, I think the bootloader is unlocked (can boot into with vol and off switch), I have clockwork and su, the installer did flash with clockwork.
Wonder if I am indeed rooted then???
Click to expand...
Click to collapse
When you boot the phone is there an unlocked lock at the bottom of the Google screen? That means your bootloader is unlocked. You can always get into the bootloader using the volume buttons and power.
Once again...using toolkits suck. Now you're stuck in limbo. Try installing an app that needs root like Titanium Backup and see if it works.
zephiK said:
this is why you don't use toolkits... when you use them you dont know what's going on.
fastboot oem unlock (bootloader unlocked already?)
fastboot flash recovery <get clockwork recovery img>
get su.zip (find it on forum)
flash it in clockwork
you have root.
alternatively, you can flash a custom rom.
Click to expand...
Click to collapse
Actually no, not with 4.04
I flashed su.zip with CWM and no dice and I used 3 toolkits as well as that method and still no root.
foreman31 said:
Actually no, not with 4.04
I flashed su.zip with CWM and no dice and I used 3 toolkits as well as that method and still no root.
Click to expand...
Click to collapse
does the toolkit update itself to include the 4.0.4 root? no, so download the new toolkit..also u dont need to try 3 toolkits, u need the latest and select gsm 4.0.4
if u use the su.zip, u need the latest working with the 4.0.4
again what make u say "still no root"? with no details we can't help u
foreman31 said:
Actually no, not with 4.04
I flashed su.zip with CWM and no dice and I used 3 toolkits as well as that method and still no root.
Click to expand...
Click to collapse
Download Superuser-3.0.7-d-signed.zip from here: Link
and flash that through CWM... It definately works on 4.0.4.
hEaTLoE said:
When you boot the phone is there an unlocked lock at the bottom of the Google screen? That means your bootloader is unlocked. You can always get into the bootloader using the volume buttons and power.
Once again...using toolkits suck. Now you're stuck in limbo. Try installing an app that needs root like Titanium Backup and see if it works.
Click to expand...
Click to collapse
Thanks, yes there is, so the bootloader is unlocked.
I am flashed correctly so just the root I presume
pittnuma said:
Thanks, yes there is, so the bootloader is unlocked.
I am flashed correctly so just the root I presume
Click to expand...
Click to collapse
If you see a superuser app in your app drawer then you have a proper root. If not then something went wrong.
Hi guys, just curious but is there anyway to gain root temporarily in 4.0.4 without unlocking bootloader? Similar to the escalation of privileges hack that worked on 4.0.1/4.0.2.
I want to remove the /system/bin/su and /system/app/Superuser.apk files on the device to get rid of the "Unsupported Device" warning in Google Wallet.
Thanks in advance.
jonnyg1097 said:
If you see a superuser app in your app drawer then you have a proper root. If not then something went wrong.
Click to expand...
Click to collapse
Ahh right, I have the Superuser, however when I tried the app suggested earlierit stated device not rooted...
Got it...
Installed new SU.zip, I had a slightly older version and the recovery-clockwork-5.5.0.4
Thanks all.
Can't post links yet but this is the link for the su I used just add the www etc
box.com/s/jvcf196j7x8f8vrc9cyt
jonnyg1097 said:
If you see a superuser app in your app drawer then you have a proper root. If not then something went wrong.
Click to expand...
Click to collapse
This is not entirely true. You can have the Superuser app in your app drawer and still not have root. The permissions on su need to be set properly.
Diger36 said:
Download Superuser-3.0.7-d-signed.zip from here: Link
and flash that through CWM... It definately works on 4.0.4.
Click to expand...
Click to collapse
pittnuma said:
Got it...
Installed new SU.zip, I had a slightly older version and the recovery-clockwork-5.5.0.4
Thanks all.
Can't post links yet but this is the link for the su I used just add the www etc
box.com/s/jvcf196j7x8f8vrc9cyt
Click to expand...
Click to collapse
A look at the first page.... Ah well, glad you sorted it out...
Sent from my Galaxy Nexus using xda premium
So I downloaded the superboot files replaced the outdated boot image with the IMM76D insecure boot image. Copied and pasted the commands into Terminal:
chmod +x install-superboot-mac.sh
then
./install-superboot-mac.sh
which leads to
downloading 'boot.img'... OKAY
booting... OKAY
but when it finishes restarting it's still not rooted. I've tried this over 10x. I've rooted this thing before with no problems, but now it doesn't want to root.
I'm running OS X 10.7.4
Bump...
rashad1 said:
Bump...
Click to expand...
Click to collapse
Boot.img =/= root? I don't understand what you're getting at... you need a custom recovery and flash superuser?
All you did was flash insecure kernel so you can flash su binary and apk..you only did the first step
You still need to flash the su.zip and app the superuser.apk to your phone.
This is a pretty nice step-by-step tutorial which helped me to regain root last night: http://forum.xda-developers.com/showpost.php?p=19583168&postcount=1
If you follow the directions carefully, you won't have any issues. Of course, if you are flashing from a mac (like I did yesterday) you will need to rename the faastboot-mac file to fastboot, or change the name in the terminal commands accordingly.
The tutorial also tells you how to permanently install CWM, which can be very handy if root access gets lost during a future firmware update.
Good luck!
Cheers
CT
Thanks, i just ended up using the gnex toolkit on a PC...it made things extremely simple. I flashed JB today
Glad to hear you managed to make it work. However, for future reference, flashing and rooting from a Mac is not a hassle either if those fastboot instructions are closely followed. It also helps you understand what is going on.
I know how annoying it can be to come across all those one-click tools for windows without having a PC around...
Maybe you'll give your oil' Mac the chance next time.
Cheers
CT
Sent from my Galaxy Nexus using xda app-developers app
root on 4.0.4
rashad1 said:
Thanks, i just ended up using the gnex toolkit on a PC...it made things extremely simple. I flashed JB today
Click to expand...
Click to collapse
Hi, i've a gnex on 4.0.4 the toolkit´ll work on 4.0.4?I've got a mac but can run the toolkit on bootcamp.
thanks
As far as I know, there is no way to keep root if you get the OTA 4.3 update, right? I want to just get the OTA and not deal with the roms. Unlocked bootloader here...
According to Voodoo OTA Rootkeeper, it doesn't work with the 4.3 update: http://forum.xda-developers.com/showthread.php?t=1241517&page=6
That's a true bummer.
Gbcue said:
As far as I know, there is no way to keep root if you get the OTA 4.3 update, right? I want to just get the OTA and not deal with the roms. Unlocked bootloader here...
According to Voodoo OTA Rootkeeper, it doesn't work with the 4.3 update: http://forum.xda-developers.com/showthread.php?t=1241517&page=6
That's a true bummer.
Click to expand...
Click to collapse
If your bootloader is unlocked then it's easy... you just flash SuperSU in recovery after the update. No ROMs to deal with. On a Nexus device with an unlocked bootloader root is never an issue.
phazerorg said:
If your bootloader is unlocked then it's easy... you just flash SuperSU in recovery after the update. No ROMs to deal with. On a Nexus device with an unlocked bootloader root is never an issue.
Click to expand...
Click to collapse
Even with stock recovery this is possible? I don't want to re-root and lose data.
Gbcue said:
Even with stock recovery this is possible? I don't want to re-root and lose data.
Click to expand...
Click to collapse
Not with stock recovery. But if you have an unlocked bootloader it's still no problem. You can boot to a custom recovery without even having to actually flash it if you want to keep stock recovery. So you just let the OTA install as normal then use fastboot to boot CWM or TWRP and flash SuperSU and you're done and rooted.
If your bootloader is unlocked, you might as well take advantage of it even if you want to remain mostly stock
Just keep in mind that SuperSU runs a daemon all the time can result in 70% cpu usage peaks. Don't blame 4.3 for it.
madd0g said:
Just keep in mind that SuperSU runs a daemon all the time can result in 70% cpu usage peaks. Don't blame 4.3 for it.
Click to expand...
Click to collapse
Do we have any idea what triggers that? Thankfully I haven't had that experience and haven't had any extra CPU usage before or after flashing 4.3 yesterday.
phazerorg said:
Do we have any idea what triggers that? Thankfully I haven't had that experience and haven't had any extra CPU usage before or after flashing 4.3 yesterday.
Click to expand...
Click to collapse
No, it seems fairly random so far. I have seen it once but can not reproduce it.
Chainfire is working on the issue though.
Questions in the Q&A, this is the general forum..
Read the rules sticky..
Beamed from my Maguro.
GldRush98 said:
No, it seems fairly random so far. I have seen it once but can not reproduce it.
Chainfire is working on the issue though.
Click to expand...
Click to collapse
SuperSU 1.43 update
add3421 said:
So is there a like guide on how to keep root when doing a system update? I have STOCK 4.2 Rooted and it is saying I should download an update. I do have TWRP installed. Is there another stock already rooted 4.3 I can download? Any help would be great so I dont have to factory reset.
Thanks!
Click to expand...
Click to collapse
Why even bother with this crap, flash the update, boot, flash custom recovery after and flash new SuperSU. You would be done before even typing this post.
I used the Nexus Root Toolkit by WugFresh to root my Galaxy Nexus on 4.3, and didn't lose any data...
All I did as usual was:-
1) Flash the update
2) Boot into TeamWin recovery (I keep the stock recovery installed)
3) Flash SuperSU 1.43
Simple, no issues.
If I have CMW Touch recovery can I install the OTA? I have received the notification but I don't know if I will be able to install it. Is there any way to revert back to Google's recovery just like installing a custom recovery? I mean not loosing data or having to so a factory reset.
Enviado desde mi Galaxy Nexus
str355 said:
All I did as usual was:-
1) Flash the update
2) Boot into TeamWin recovery (I keep the stock recovery installed)
3) Flash SuperSU 1.43
Simple, no issues.
Click to expand...
Click to collapse
How do you boot into twrp without flashing it? I know "fastboot flash recovery twrp.img" permanently overrides the built in recovery, but how would you boot into it just once?
AMKhatri said:
I used the Nexus Root Toolkit by WugFresh to root my Galaxy Nexus on 4.3, and didn't lose any data...
Click to expand...
Click to collapse
Which version of the toolkit?
krackers said:
How do you boot into twrp without flashing it? I know "fastboot flash recovery twrp.img" permanently overrides the built in recovery, but how would you boot into it just once?
Click to expand...
Click to collapse
This is the command you want "fastboot boot twrp.img"
---------- Post added at 08:45 PM ---------- Previous post was at 08:41 PM ----------
add3421 said:
ok cool, do you happen to have a link to the exact update i can download? for some reason when i click install it says restarting now.. but never does.
Click to expand...
Click to collapse
I used the link in this thread --> http://forum.xda-developers.com/showthread.php?t=2377390
SuperSU.zip from here (v1.45 now) --> http://forum.xda-developers.com/showthread.php?t=1538053
Gbcue said:
Which version of the toolkit?
Click to expand...
Click to collapse
1.6.4 after running update.
FWIW: Even though I've successfully used this kit a dozen times on four different devices, root was not working correctly (no su binary found) for me so I had to load the app via twrp which did correctly load from the toolkit after the kit installed 4.3.
Gbcue said:
Which version of the toolkit?
Click to expand...
Click to collapse
1.6.4 and it worked perfectly for me
ok, I got stock 4.4.4 but with root, bootloader is locked..
I wanna be able to receive the OTA update what do I need to do in order to be able to receive that?
or do I need to unlock the bootloader, install a recovery and flash lollipop threw that?
If you have stock system, kernel, and recovery, (no altered system files, either) being rooted won't keep you from getting the OTA. Locked/unlocked bootloader doesn't matter. If you rooted with SuperSu, just use its settings to uninstall root (you'll lose it anyway). However, I think you have to unlock bootloader to reroot, which, of course, will wipe your device. The OTA zip is now available for adb sideload if you're interested.
nvm got stock recovery back on, lol still learning, is it better to side load or can i use flash stock + unroot on the nexus root toolkit v1.9.3 to do the same?
Cobra11Murderer said:
nvm got stock recovery back on, lol still learning, is it better to side load or can i use flash stock + unroot on the nexus root toolkit v1.9.3 to do the same?
Click to expand...
Click to collapse
OTA won't wipe regardless of how you get it--over the air or sideloaded. Wug's will wipe unless you tell it not to (Options>Flash Stock>Enable no wipe). He also has the LRX21P build available. IMO, one way isn't better than another.
ok, I just tried to sideload and looks like i got a driver issue :\ lol followed the steps in the installation guide and did the test.. it works great up till i go into stock recovery and hit sideload lol then it disconnects and tells me no driver found...
i might just try flash stock + unroot and choosing LRX21P, that wont lock my bootloader correct? and should I be a little worried that the driver cant be found for that specific thing? thanks for all the help btw!
You probably already did all this, but you have to specifically send command to lock boot loader. I don't get how your device wasn't recognized through stock recovery but is on NRT, but it doesn't matter. Just use the kit which is what you probably did.
What you should do is back up what you need and want, then unlock the bootloader. You're not gonna get root without it on Android L since it requires a custom kernel.
Cobra11Murderer said:
ok, I just tried to sideload and looks like i got a driver issue :\ lol followed the steps in the installation guide and did the test.. it works great up till i go into stock recovery and hit sideload lol then it disconnects and tells me no driver found...
i might just try flash stock + unroot and choosing LRX21P, that wont lock my bootloader correct? and should I be a little worried that the driver cant be found for that specific thing? thanks for all the help btw!
Click to expand...
Click to collapse
Based on this, I assumed you unlocked your bootloader since first posting. NRT recognizes the device, right? Have you gotten it all sorted out yet.
idk why adb sideloading would kick the connection out, then the pc would say nexus 7 but wrong driver?, anyways i just went ahead and flashed the factory image using flash stock + unroot since I had it all backed up anyways, and that went great now I got lollipop on it, and should be able to root no probs now
thanks everyone, I hope i dont have a issue with adb again, im not sure if it was the samsung cord or what but it kept disconnecting at that part asking for a driver.. funny thing everything from bootloader, fastboot and all worked great with the driver that I installed using the steps in the toolkit..
Glad it's all good. Root with the toolkit. Just for the heck of it, you may want to try running CMD from wug's ADB folder. I've experienced just the opposite with older versions of the kit. NRT wouldn't recognize device. I'd go to CMD and device recognized. Return to NRT, all good again.
alrighty will do!, thanks for all your help