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
I bought a new KF and it has 6.3 on it. I would like to root via BuritooRoot3 but I need 6.2 to run his app. Is there any way to take a stock 6.3 KF and get it back to a stock 6.2 ???
Thanks !
Thibor69 said:
I bought a new KF and it has 6.3 on it. I would like to root via BuritooRoot3 but I need 6.2 to run his app. Is there any way to take a stock 6.3 KF and get it back to a stock 6.2 ???
Thanks !
Click to expand...
Click to collapse
Flash MoDaCo rom. It's a pre rooted stock with gapps and GFS included.
soupmagnet said:
Flash MoDaCo rom. It's a pre rooted stock with gapps and GFS included.
Click to expand...
Click to collapse
DO you think this is the best way to go ?........ or should I go ahead with the only 6.3 root guide I have seen here on this site. (pooky900 guide or something sorry forgot his name) Or do you think it best to wait for a easier newer 6.3 rooter to show up ?? Just your thoughts .... I am not holding you to anything here :O)
Thanks
Thibor69 said:
DO you think this is the best way to go ?........ or should I go ahead with the only 6.3 root guide I have seen here on this site. (pooky900 guide or something sorry forgot his name) Or do you think it best to wait for a easier newer 6.3 rooter to show up ?? Just your thoughts .... I am not holding you to anything here :O)
Thanks
Click to expand...
Click to collapse
I've tried to explain much of this a couple of times now, so here's my final attempt...
The generally accepted procedure for rooting or installing a ROM:
1) Get to fastboot mode by utilizing either...
a) a factory cable
b) fbmode
2) Install recovery and custom bootloader
3) Either root by installing su and Superuser.apk or flash a custom ROM
To get back to 6.2, you will still have to do #1 & #2 and flash the 6.2 zip package like you would any other ROM. Amazon's software will not allow you to downgrade the software through stock so you can use the BurritoRoot exploit.
It's not likely for someone to come up with a newer/easier method for rooting 6.3 because...
a) It's pretty straightforward as it is
b) No one spends the time to do it when the old way works perfectly well
I've laid out the procedure in excruciating detail here...
http://forum.xda-developers.com/showthread.php?t=1638452
I invite you to keep exploring easier ways to do this, so I can make the how-to above simpler and shorter, but I doubt you will find one. Good luck.
MoDaCo comes with 6.3 pre rooted along with gapps and Google Framework Services preinstalled. It is by far the easiest route to get a rooted stock because the work has already been done for you. All you have to do is flash it in recovery. (Assuming you have recovery installed of course)
Last time I heard, you still have to rename otacerts.zip to prevent any OTA updates screwing up everything but I'm not 100% on that. You should definitely look into it, though. People here are pretty good at staying on top of the latest updates and making flashable versions that won't undo everything you have so far (i.e. break root, uninstall recovery, etc.)
Pokey9000's rooting method is very effective and good if you want to learn but unnecessary IMO if you just want a rooted stock that works well. But I think you should definitely have fbmode on your device if you are using Windows. It could come in very handy when your drivers are being stupid.
It should be noted that I don't use stock and never have so I couldn't tell you much about the differences between MoDaCo and straight rooted, as in whether or not you can watch Prime Video with it, but there are plenty of stock users here that can help you sort it out.
Thibor69 said:
I bought a new KF and it has 6.3 on it. I would like to root via BuritooRoot3 but I need 6.2 to run his app. Is there any way to take a stock 6.3 KF and get it back to a stock 6.2 ???
Thanks !
Click to expand...
Click to collapse
Kindle Fire Utility .95 works easily on 6.3 and while it's not BurritoRoot it is still a simple one click root utility with a lot of features to make the rooting process easy. Any particular reason you want Burrito?
soupmagnet said:
MoDaCo comes with 6.3 pre rooted along with gapps and Google Framework Services preinstalled. It is by far the easiest route to get a rooted stock because the work has already been done for you. All you have to do is flash it in recovery. (Assuming you have recovery installed of course)
Last time I heard, you still have to rename otacerts.zip to prevent any OTA updates screwing up everything but I'm not 100% on that. You should definitely look into it, though. People here are pretty good at staying on top of the latest updates and making flashable versions that won't undo everything you have so far (i.e. break root, uninstall recovery, etc.)
Pokey9000's rooting method is very effective and good if you want to learn but unnecessary IMO if you just want a rooted stock that works well. But I think you should definitely have fbmode on your device if you are using Windows. It could come in very handy when your drivers are being stupid.
It should be noted that I don't use stock and never have so I couldn't tell you much about the differences between MoDaCo and straight rooted, as in whether or not you can watch Prime Video with it, but there are plenty of stock users here that can help you sort it out.
Click to expand...
Click to collapse
Just so everybody is on the same page and because I've done more rooting experiments the last few days than I care to admit.
Thibor69 said in another one of his threads that he wants to go to the Hellfire ROM. He's not interested in rooted stock, as far as I can tell. I agree though... I don't know why someone would take the time to root when MoDaCo seems to have done all the heavy lifting already. MoDaCo users also say that they can use some app (the name escapes me at the moment) that switches root on and off so they can watch videos.
pokey9000 doesn't have a rooting method. He has a fastboot exploit that is being used to root 6.3.x in a guide originally written by jcase. For 6.2.x, the rooting method was to use the BurritoRoot exploit to gain root and then get to fastboot mode by using idme. Amazon closed that hole so BurritoRoot can no longer be used for 6.3.x. Because jcase wasn't interested in building another root exploit, he published that guide as an alternative. The rooting method for 6.3.x is to use pokey9000's fbmode to get to fastboot and then install su privileges through TWRP... so, the process has been reversed... su -> fastboot for 6.2.x and now fastboot -> su for 6.3.x. So, you still have to use pokey9000's fbmode to get to fastboot and install a recovery (and bootloader) if you want to install any ROM.
Laquox said:
Kindle Fire Utility .95 works easily on 6.3 and while it's not BurritoRoot it is still a simple one click root utility with a lot of features to make the rooting process easy. Any particular reason you want Burrito?
Click to expand...
Click to collapse
KFU is broken for whatever reason. It does get you su, but doesn't install the Superuser.apk... I don't know why and I'm not interested in debugging it. I'm not sure if sideloading Superuser.apk is the only thing that needs to be done after its "rooting" process, but it also installs the old versions of FFF and TWRP. That causes headaches all around for people that don't know their way around the bootloader and recovery. Otherwise, it's great!
KFU uses the same fbmode exploit that I've outlined in my guide, so the process is essentially identical. If you follow along with what I have there, you'll get all the current software and a working Superuser. If you use KFU, you can go back and reinstall all the stuff I mentioned above.
kinfauns said:
...
Click to expand...
Click to collapse
Yeah, sorry about that. I was replying to his post and you beat me to the punch.
So, yeah...what kinfauns said
Thibor69 said:
I bought a new KF and it has 6.3 on it. I would like to root via BuritooRoot3 but I need 6.2 to run his app. Is there any way to take a stock 6.3 KF and get it back to a stock 6.2 ???
Thanks !
Click to expand...
Click to collapse
You can use the Kindle Fire Utility 0.9.5
That's what I used to root my Kindle on 6.3
You just have to sideload the superuser.apk file though
kinfauns said:
Thibor69 said in another one of his threads that he wants to go to the Hellfire ROM. He's not interested in rooted stock, as far as I can tell.
Click to expand...
Click to collapse
.....Yes that is what I want to do. I don't care about stock at all.
kinfauns said:
I agree though... I don't know why someone would take the time to root when MoDaCo seems to have done all the heavy lifting already. MoDaCo users also say that they can use some app (the name escapes me at the moment) that switches root on and off so they can watch videos.
Click to expand...
Click to collapse
.....I hear what you are saying. Since I don't care about amazon video's, I see no reason to keep any aspects of stock at all .... so I guess I should skip MoDaCo's method also ... right ?
kinfauns said:
pokey9000 doesn't have a rooting method. He has a fastboot exploit that is being used to root 6.3.x in a guide originally written by jcase. Because jcase wasn't interested in building another root exploit, he published that guide as an alternative. The rooting method for 6.3.x is to use pokey9000's fbmode to get to fastboot and then install su privileges through TWRP... So, you still have to use pokey9000's fbmode to get to fastboot and install a recovery (and bootloader) if you want to install any ROM.
Click to expand...
Click to collapse
.....Ok I understand. My question tho would be after I get to fastboot, you said to install a recovery and bootloader. Isn't TWRP the recovery method ? and which bootloader do I install ? And I do this all from within fastboot ? Also, what about FFF ? were does that come into play.
kinfauns said:
KFU uses the same fbmode exploit that I've outlined in my guide, so the process is essentially identical. If you follow along with what I have there, you'll get all the current software and a working Superuser. If you use KFU, you can go back and reinstall all the stuff I mentioned above.
Click to expand...
Click to collapse
But you mentioned that KFU is broken ... so I guess I should just follow your method.
ONE LAST NOTE: Were are the drivers for Kindle Fire. I plug into PC (win7) and it doesn't find driver for kindle, but I still have access to the internal somehow ..
I am ready to start this process now .... but I want to be 100% sure I have a recovery image in case I soft-brick somehow.
You guys are great ... and thank you for helping me !!!
Cheers
Thibor69 said:
I hear what you are saying. Since I don't care about amazon video's, I see no reason to keep any aspects of stock at all .... so I guess I should skip MoDaCo's method also ... right ?
Click to expand...
Click to collapse
Right, sort of. Any custom rom you flash will be rooted, but you need recovery to flash it.
.....Ok I understand. My question tho would be after I get to fastboot, you said to install a recovery and bootloader. Isn't TWRP the recovery method ? and which bootloader do I install ? And I do this all from within fastboot ? Also, what about FFF ? were does that come into play.
Click to expand...
Click to collapse
TWRP is the preferred recovery. You can install the latest bootloader from within recovery... http://forum.xda-developers.com/showthread.php?p=25598837 ...and use fastboot to change to recovery bootmode
But you mentioned that KFU is broken ... so I guess I should just follow your method.
ONE LAST NOTE: Were are the drivers for Kindle Fire. I plug into PC (win7) and it doesn't find driver for kindle, but I still have access to the internal somehow ..
Click to expand...
Click to collapse
The drivers for the KF can be found in the KFU folder along with an installation batch file.
Ok so to sum it up:
1) install kindle drivers, be sure PC see's Kindle and be sure adb is working
2) install TWRP
3) install latest bootloader (via link below)
4) then flash ROM ?
Cheers
soupmagnet said:
Right, sort of. Any custom rom you flash will be rooted, but you need recovery to flash it.
TWRP is the preferred recovery. You can install the latest bootloader from within recovery... http://forum.xda-developers.com/showthread.php?p=25598837 ...and use fastboot to change to recovery bootmode
The drivers for the KF can be found in the KFU folder along with an installation batch file.
Click to expand...
Click to collapse
Sounds about right. There's a possibility you may need to fix your drivers again at some point in the process. If for some reason you can't get fastboot to connect:
http://forum.xda-developers.com/showthread.php?t=1625356
&
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
soupmagnet said:
Sounds about right. There's a possibility you may need to fix your drivers again at some point in the process. If for some reason you can't get fastboot to connect:
http://forum.xda-developers.com/showthread.php?t=1625356
&
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
Click to expand...
Click to collapse
Many thanks !
Hey Everyone!
This is my first time doing an official ROM repact by injecting Root into the ROM itself so as to not trip the flash counter!
This is for Bell's Canadian S3 SGH-I747M firmware: I747MVLALE8
I know this has recently already been done by MrRobinson for the Canadian carriers but I have done mine slightly differently.
Most of you im sure know of Chainfire and his amazing work, well I love the work he does and it is my opinon that his Root app SuperSU is better then the Superuser one, this may be very minor or non exisist to some people and it all really boils down to Personal perference but as such I perfer SuperSU and love it and want to support his work!
I have tested this myself on my own S3 works great, counter does not increase, and flash time only took me 6 minutes! (some people were complaining about the other root injected roms taking 10 minutes and upwords to 20 to complete)
IMPORTANT NOTE:
This rom has been injected with Chainfires CF root but it is only his SuperSU root app and does not contain any custom CWM recovery or Manager app. Chainfire custom builds his CWM manager app specific to certain devices and is not compatible with the North American varients.
To get the North American LTE version of CWM Recovery please see team epics website at:
http://www.epiccm.org/2012/06/cwm-recovery-on-all-sgs3-lte-variants.html
To install this recovery without tripping the counter you will need to manually copy it over to the memory card block which contains the recovery section of your phone. Once downloaded extract the recovery.img file out of the tar and place it into your sdcard.
Either through ADB shell or using a terminal emulator app on the phone run the following commands:
Code:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18
Remember to do "su" first to grand root access to the ADB shell or terminal emulator otherwise you will not be given the permissions to do the recovery copy on the 2nd command as mentioned above.
1 final note, like all the other root injected roms for the S3, these root methods currently do have not busybox built into them so it is highly recommended for you to download and install the busybox app off the play store [the one by Stephen (Stericson)] to get even more functionality for your rooted device.
~~Link Removed~~
My apologies in advance for uploading to filefactory as they are known to be slow sometimes on downloads. If anyone is able to host it for faster speeds that would be awesome.
EDIT:
For some reason the cache file doesn't properly install and so you are left with a blank CSC. Currently trying to figure out why this is happening as I havn't done anything to the CSC file to begin with. In the mean time I have taken down the link. I recommend getting the one made by MrRobinson for flashing Bells Rom
View the sticky post for his here:
http://forum.xda-developers.com/showthread.php?t=1739426
There is already a thread for this under stickies, but thanks for your contribution anyways.
Sent from my SAMSUNG-SGH-I747 using xda premium
jthrasher47 said:
There is already a thread for this under stickies, but thanks for your contribution anyways.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
I am aware of this, I actually made a point of saying so in my post but I guess you skimmed it and didn't see that part?.
I also explain that mine is a bit different and why.
Correct me if I'm wrong, but SuperSu and Superuser and interchangable via. the Play Store. No need to redo the whole rooting process just to change the app.
dbzgod said:
It took me longer because I had to do it without a Linux box, funny enough I manage to do it using my Rooted S2 phone lol.
Click to expand...
Click to collapse
Am I understanding correctly that this method doesn't use odin, and you somehow used another android phone to do it?
danny6514 said:
Correct me if I'm wrong, but SuperSu and Superuser and interchangable via. the Play Store. No need to redo the whole rooting process just to change the app.
Click to expand...
Click to collapse
Yeah they can be changed out, but I released this anyways because I had started work on it right away when the firmware was released and even though MrRobinson had put out root injected roms before me I still wanted to complete what I started and not leave it half done.
I would of had this out at about the same time if not before the others but because of time contraints on my part as well as running into a few problems via doing the whole repack and inject a unique way on my rooted S2 Android phone. Instead of a Linux box I figured out how to do almost all of the repacking steps on an Android phone and then I was delayed trying to figure out 1 important step that required a full Linux box, but discovered an alternate means to do so on Windows.
At any rate I just wanted to post my work (even though late coming) and offer people this alternate root injection Rom.
qwer777 said:
Am I understanding correctly that this method doesn't use odin, and you somehow used another android phone to do it?
Click to expand...
Click to collapse
No you still need to use Odin to flash the firmware. I see your misunderstanding though, I was just trying to explain in my post that since I dont have a Linux box I had to do the repact and inject process over ADB shell via my Rooted Galaxy S II phone for a Linux eviroment.
dbzgod said:
No you still need to use Odin to flash the firmware. I see your misunderstanding though, I was just trying to explain in my post that since I dont have a Linux box I had to do the repact and inject process over ADB shell via my Rooted Galaxy S II phone for a Linux eviroment.
Click to expand...
Click to collapse
Damn! I was really excited! Oh well. I'll need to find me a windows pc.
Just upgraded my GN using OTA update to 4.2. Using GNex Toolkit (v9.4.0) I went to re-root my phone so went through the steps and selected:
2. SuperSU 0.98 by Chainfire] [SELECT THIS TO ROOT IF ON ANDROID 4.2]
Process went through fine but when I tried Titanium Backup it said my GN was not rooted. When I tried loading SuperSU, it prompts me saying it needs to be updated which I accept but then fails.
Any ideas?
Thanks.
manually flash the supersu zip and then update it and it should work.. rooting via the toolkit is a hit or miss on 4.2, it works for some and doesnt for others
selector said:
Just upgraded my GN using OTA update to 4.2. Using GNex Toolkit (v9.4.0) I went to re-root my phone so went through the steps and selected:
2. SuperSU 0.98 by Chainfire] [SELECT THIS TO ROOT IF ON ANDROID 4.2]
Process went through fine but when I tried Titanium Backup it said my GN was not rooted. When I tried loading SuperSU, it prompts me saying it needs to be updated which I accept but then fails.
Any ideas?
Thanks.
Click to expand...
Click to collapse
Since yesterday i had Android 4.1.2 (yakju, rooted). About 9PM i upgraded to 4.2 and Root Checker told me that I don't have a proper root access. Does Toolkit 9.4 easily roots yakju 4.2? Where I can find another guides about rooting my yakju 4.2? Ah, I forgot. Noob here.
ecthable said:
Since yesterday i had Android 4.1.2 (yakju, rooted). About 9PM i upgraded to 4.2 and Root Checker told me that I don't have a proper root access. Does Toolkit 9.4 easily roots yakju 4.2? Where I can find another guides about rooting my yakju 4.2? Ah, I forgot. Noob here.
Click to expand...
Click to collapse
Ditch the toolkit and follow this guide. Learning to use ADB and Fastboot empowers you to control your device and to fix any errors, should they occur ~ an unlikely scenario.
http://forum.xda-developers.com/showthread.php?t=1830108
rickbosch said:
Ditch the toolkit and follow this guide. Learning to use ADB and Fastboot empowers you to control your device and to fix any errors, should they occur ~ an unlikely scenario.
http://forum.xda-developers.com/showthread.php?t=1830108
Click to expand...
Click to collapse
This ^
I wish everyone would let tool kits die. No offence to the person making them but it's lazy and seeing as it takes 2 seconds to set adb/fastboot up it's not really necessary...
selector said:
Just upgraded my GN using OTA update to 4.2. Using GNex Toolkit (v9.4.0) I went to re-root my phone so went through the steps and selected:
2. SuperSU 0.98 by Chainfire] [SELECT THIS TO ROOT IF ON ANDROID 4.2]
Process went through fine but when I tried Titanium Backup it said my GN was not rooted. When I tried loading SuperSU, it prompts me saying it needs to be updated which I accept but then fails.
Any ideas?
Thanks.
Click to expand...
Click to collapse
Had the same problem as above.
As i wanted to keep stock recovery, here is a solution (edit: I have unlocked bootloader)
a) Copy to SDcard the file: CWM-SuperSU-v0.98.zip from the XDA SuperSU
b) boot Nexus to fastboot
c) use the GNex Toolkit (v9.4.0) to: 10.Boot to Custom Recovery without Permanently Flashing it
d) choose: 1.Flash Clockworkmod Touch Recovery 6.0.1.4
Nexus booting to Clockworkmod and flash CWM-SuperSU-v0.98.zip & reboot (allow stock rom to reflash boot.img)
After boot, got a Rooted 4.2 with stock recovery. SuperSU works OK :good:
I'm annoyed by these ****ty threads. Every person that wants to be freaking spoon fed every thing they need, should brick their device, for real, and never touch a smart phone again.
Sent from my i9250
aga2 said:
Had the same problem as above.
As i wanted to keep stock recovery, here is a solution (edit: I have unlocked bootloader)
a) Copy to SDcard the file: CWM-SuperSU-v0.98.zip from the XDA SuperSU
b) boot Nexus to fastboot
c) use the GNex Toolkit (v9.4.0) to: 10.Boot to Custom Recovery without Permanently Flashing it
d) choose: 1.Flash Clockworkmod Touch Recovery 6.0.1.4
Nexus booting to Clockworkmod and flash CWM-SuperSU-v0.98.zip & reboot (allow stock rom to reflash boot.img)
After boot, got a Rooted 4.2 with stock recovery. SuperSU works OK :good:
Click to expand...
Click to collapse
Thanks alot, had the same problem and this worked perfectly for me
Hi Guys,
This is my 1st thread to guide you to correct resource rather as many of us have struggled to root the AtT ICS version ROMs.
I was on leaked iCS v18f installed immediately when available, struggled hard to root it.. Tsparky, Doomlord, SuperOneClick, manual root,. No go for more than a couple of months.. Found the Bin4ry root method:
http://forum.xda-developers.com/showthread.php?t=1886460
Worked in 1st attempt.
Thought it should work on V20c as well,, upgraded to v20c.. rooted in 1st attempt again (no surprise there)
UI is smooth as silk and response is awesome..
Right now Rooted, no-frills CPU, ADW Launcher Ex and Network Selection Tweak by -ReaL-. (as the *#*#4636#*#* code to choose network selection is removed on V20c) THANKS A LOT..
http://forum.xda-developers.com/showthread.php?t=1823399
My Phone is a like a ripe cherry for the 1st time and I am jus loving it...
Thanks to all the mods and developers..
NOTE: Confirmed working on both ICS versions V18f and v20C, single attempts, though doesnt work on Gingerbread as explained in the linked post.
Doesnt work
I tried the method provided, and i followed the instructions and no luck for me with my LG nitro, with stock ICS on it
Device detection
Make sure USB Debugging under "Development section" and Unknown Sources under "Security" are selected.
Launch the "command prompt" as Administrator. Make sure it lists your mobile phone when you run the command "stuff\adb devices" U r good to go..
If it doesn't, then the drivers are not installed properly, check in Device Manager there are no unknown devices or devices with yellow exclamation marks etc.. Make sure drivers are installed properly. The above condition should be met to root your device.
Please go through the video tutorial in the link attached for Bin4ary root method
Attn Mods
Hi MODs,
If you think this should not be as a separate thread, please merge this with any existing thread about rooting P930 with AT&T ICS
Thanks..
Works like a charm
Many thanks, it took me 5 minutes to download and root my nitro(official ICS).
I recommend making this thread as sticky thread for rooting.
It works but you don't have full root, SU and CWM can be install but when I attempt to boot into recovery, I get the boot certification error. Damn LG for subscribing to the Secure Boot fad, started by Micro$oft. I have the LG MultFlash Tool, where can I download a Stock AT&T Gingerbread firmware?
Check in one of the various unbricking threads there you will find all the files and instructions required. Good luck
Sent from my LG-P930 using xda app-developers app
Anyone else get the same result on V20C, after rooting and flashing CWM cannot reboot into Recovery Mode? It just boots into Fastboot because of boot certificate error. Anyone have an ADB solution that can work in Fastboot?
Scotsman828 said:
Anyone else get the same result on V20C, after rooting and flashing CWM cannot reboot into Recovery Mode? It just boots into Fastboot because of boot certificate error. Anyone have an ADB solution that can work in Fastboot?
Click to expand...
Click to collapse
Okay, once again. YOU HAVE TO UNBRICK NOW. LOOK IN ONE OF SEVERAL UNBRICKING GUIDES FOR OUR DEVICE TO SOLVE THIS ISSUE. Sorry but there is simply no way around it.
Sent from my LG-P930 using xda app-developers app
Scotsman828 said:
Anyone else get the same result on V20C, after rooting and flashing CWM cannot reboot into Recovery Mode? It just boots into Fastboot because of boot certificate error. Anyone have an ADB solution that can work in Fastboot?
Click to expand...
Click to collapse
Unbrick to flash CWM... only way coming from V20C. If there was a simpler way it would have probably been posted, but there's not.
CWM wont work on ICS for now
lordcheeto03 said:
Unbrick to flash CWM... only way coming from V20C. If there was a simpler way it would have probably been posted, but there's not.
Click to expand...
Click to collapse
Yes, u r right,, CWM does not run on ICS, either V18f, V20(X) versions.. it would cause issues if u try CWM on ICS.. hence we have so many guides to go back to Stock GB, install CWM and install Custom ROMs, kernels etc
The thread is to get instructions to root your ICS P930.. so that we could install applications that need Root access...
Ok thanks, was attempting to just use LG Flash Tool to flash Gingerbread rom but the DLL that I have is for UPGRADE. I need a DLL to allow Downgrade, Looks like I have days of aggravation ahead to get CM10 on my Nitro.
Finally got unbricked and rooted. Now on to CM10 Thanks to everyone!
Scotsman828 said:
Finally got unbricked and rooted. Now on to CM10 Thanks to everyone!
Click to expand...
Click to collapse
Share?
Just followed the Unbricking Guide
HTML:
http://forum.xda-developers.com/showthread.php?t=1597488
once I got 10F.KDZ flashed, I ran SuperOneClick 2.3.2 to get root (make sure USB Debugging and Unknown Sources are checked and also make sure your computer has Microsoft's .NET 3.5 installed, I ran into a problem getting SuperOneClick to run without it) once rooted, I was able to side load an updated GooglePlay.apk, then downloaded ROM Manager, rebooted into recovery. I did discover that the current recovery cannot see SDCards larger than 2 Gigs, because it could not detect my 16 Gig card. So I used a 1 GIg card with CyanogenMod 10.0.0-P930.zip, did a wipe of all the partitions and Dalvik Cache. then installed CM10. After CM10 installed I flashed the AT&T baseband back into the phone using ADB. My Nitro looks awesome now. Had to download the latest gapps-jb-20121011-signed.zip and flashed with ROM Manager. One last thing once CWM Recovery is flashed to your phone, to get into it manually, simply hold the volume down + power until you see the screen asking you if you want to factory reset, click the power button confirming, instead of hard reset it will load CWM Recovery.:good:
I am using lg-su 640 with android 2.3.5. Can this thing work for that mobile???? pls help me . I tried evry thing to get root access... bt i failed again and again..... pls reply
Sent from my LG-SU640 using xda app-developers app
latif sachal said:
I am using lg-su 640 with android 2.3.5. Can this thing work for that mobile???? pls help me . I tried evry thing to get root access... bt i failed again and again..... pls reply
Sent from my LG-SU640 using xda app-developers app
Click to expand...
Click to collapse
SuperOneClick 2.3.2 should root it.
Superoneclick is not rooting it.......it hanged b/w rooting process.... at step 7. Any suggesion.......
Sent from my LG-SU640 using xda app-developers app
Scotsman828 said:
SuperOneClick 2.3.2 should root it.
Click to expand...
Click to collapse
Superoneclick is not rooting..... its just hanged up b/w rooting process... at step 7... any sugession??????
Sent from my LG-SU640 using xda app-developers app
reddevil_sen said:
Yes, u r right,, CWM does not run on ICS, either V18f, V20(X) versions.. it would cause issues if u try CWM on ICS.. hence we have so many guides to go back to Stock GB, install CWM and install Custom ROMs, kernels etc
The thread is to get instructions to root your ICS P930.. so that we could install applications that need Root access...
Click to expand...
Click to collapse
And the post that I quoted mentioned having boot problems when trying to flash ClockWorkMod AFTER rooting...