I rooted my Nexus 7 with Nexus Root Toolkit without any problems but I've just bought a Nexus 4 and can't seem to root it.
I let it update to Android 4.2.2 then ran NRT (v1.6.3) on my PC. After a few goes the drivers installed and it passed the final driver test so I assume all is well there. I then unlocked it without any trouble but I ran into problems when I came to root it.
It seemed to be going smoothly until it reached "Booting TWRP temporarily" but nothing happened, it just sat in the bootloader screen and didn't move on, although the message changed to "Rooting" and then "Waiting for your device to finish booting back up". In the end I pressed the power button which rebooted the 'phone and appeared to finish the procedure but it hadn't rooted or installed SuperSU or BusyBox.
I tried flashing it back to stock and re-rooting it but it was the same, I even re-locked it and went through the procedure again but it was the same.
Can anyone help please?
:sly:
Sent from my Nexus 4 using Tapatalk 2
SimonP2 said:
I rooted my Nexus 7 with Nexus Root Toolkit without any problems but I've just bought a Nexus 4 and can't seem to root it.
I let it update to Android 4.2.2 then ran NRT (v1.6.3) on my PC. After a few goes the drivers installed and it passed the final driver test so I assume all is well there. I then unlocked it without any trouble but I ran into problems when I came to root it.
It seemed to be going smoothly until it reached "Booting TWRP temporarily" but nothing happened, it just sat in the bootloader screen and didn't move on, although the message changed to "Rooting" and then "Waiting for your device to finish booting back up". In the end I pressed the power button which rebooted the 'phone and appeared to finish the procedure but it hadn't rooted or installed SuperSU or BusyBox.
I tried flashing it back to stock and re-rooting it but it was the same, I even re-locked it and went through the procedure again but it was the same.
Can anyone help please?
Click to expand...
Click to collapse
Yes, uninstall and forget about root kits and look and (most importantly) learn from here http://forum.xda-developers.com/showthread.php?t=2010312.
This is also a good source to read: http://forum.xda-developers.com/showthread.php?t=1469909
Thanks for the suggestions, guys. I still don't know why Nexus Root Toolkit didn't do the job when it worked so well and easily on my Nexus 7 but in the end I used the hippowise.com rooting instructions (using Google Nexus 4 Toolkit) and it worked a treat so I'm a happy bunny again
http://hippowise.com/how-to-unlock-root-and-install-a-custom-recovery-on-a-nexus-4/
I know it's more sensible to do it manually so that I know what has happened but in this case I just wanted the job done as quickly and easily as possible. I'll look into exactly what happened when time permits.
Cheers,
Simon.
^^ Learning opportunity lost.
Ditto, I've heard nothing good about toolkits and never used them, and consequently have never had the weird problrms I hear associated with them. Set up fast boot, setting it up can be a pain sometimes but its a one time thing. Using it is too easy and it never fails.
I do get what you guys mean and I will be interested to look into the procedures to see what's going on and how it unlocks and roots when time permits but, aside from being short of time at the moment, these toolkits are just automating the list of commands that you would issue manually so as long as someone has seen it working on the device and OS that you want, they should be fine so I'm happy to use them and learn more if/when I need to resolve problems. I am techie by nature but I'm not familiar with *nix and the inner workings of Android so it's a lot to study for something that only needs doing occasionally.
Anyway, thanks again for pointing me in the right direction and encouraging me to not be so lazy
SimonP2 said:
I do get what you guys mean and I will be interested to look into the procedures to see what's going on and how it unlocks and roots when time permits but, aside from being short of time at the moment, these toolkits are just automating the list of commands that you would issue manually so as long as someone has seen it working on the device and OS that you want, they should be fine so I'm happy to use them and learn more if/when I need to resolve problems. I am techie by nature but I'm not familiar with *nix and the inner workings of Android so it's a lot to study for something that only needs doing occasionally.
Anyway, thanks again for pointing me in the right direction and encouraging me to not be so lazy
Click to expand...
Click to collapse
To be honest, the learning curve with manual rooting is very straightforward. Heck, I found it quicker to unlock and root manually than through toolkits. You are literally just inputting a few lines into command prompt.
Sent from my Nexus 4 using Tapatalk 2
I can confirm that I have the same problem. Stuck at "Booting TWRP Temporarily" logo, doesn't move... Nexus 7 2012 Grouper 16GB.
Related
Well unlocking the boot loader is possible but when rooting the nexus 7 gets stuck in fastboot when its suppose to be rebooting its self oh well I been at it all night so now I realized its impossible
Sent from my Nexus 7 using xda app-developers app
Use the toolkit, worked great for me. I couldnt get the adb right so I tried that. My nexus 4 was easy without the toolkit though..
Sent from my Nexus 4
I get a error saying failed <remote: <>
Sent from my Nexus 7 using xda app-developers app
If you can unlock the boot loader, you can do *anything* to your tablet starting with fastboot.
Learning to install drivers is a Windows issue - the skills needed to analyze & resolve driver problems have almost nothing to do with what device is attached to the other end of the USB cable.
Toolkits are a crutch for avoiding learning a very small number of skills; if you don't want to learn those skills, probably you shouldn't be rooting.
Throw away your toolkit and read the fastboot thread. The whole process is far easier than you think.
How come y'all help everyone else but I can't even get a hint on what I'm suppose to do I'll just return my tablet and get a new one Cruz obviously its gotta be my tablet
Sent from my Nexus 7 using xda app-developers app
I'll just go to yahoo answers I'll have more help there
Sent from my Nexus 7 using xda app-developers app
Class_of_punk26 said:
How come y'all help everyone else but I can't even get a hint on what I'm suppose to do I'll just return my tablet and get a new one Cruz obviously its gotta be my tablet
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
If you unlocked the bootloader and you're having trouble rooting your device then I don't see you being able to relock the device either, which is critical to do before returning it as technically an unlocked device is out of warranty.
And you say no one is helping you, but you haven't provided any information at all. We have no idea what you did to even cause that error, and you were recommended just to use a toolkit if you want, as that is an easy approach, and you haven't responded on whether you have done that either.
Exactly, how is anyone supposed to help if you don't tell us what you did.
How did you unlock fast boot? What did you try to get rooted?........etc
User is informed of multiple posts. So hopefully, with your help, the root issue can get resolved.
User MUST tell people exactly the steps taken to replicate the error. Including PC type and Operating System.
I hope we do not see duplicated posts anymore.
So if some of you more experienced users, can do some "hand holding" and walk him through the steps, then it will be appreciated. As clearly, he has issues on his own.
Do it for XDA...
MD
bftb0 said:
If you can unlock the boot loader, you can do *anything* to your tablet starting with fastboot.
Learning to install drivers is a Windows issue - the skills needed to analyze & resolve driver problems have almost nothing to do with what device is attached to the other end of the USB cable.
Toolkits are a crutch for avoiding learning a very small number of skills; if you don't want to learn those skills, probably you shouldn't be rooting.
Throw away your toolkit and read the fastboot thread. The whole process is far easier than you think.
Click to expand...
Click to collapse
I agree 100% on Toolkits
That sounds like a windows driver issue. I had a similar issue when rooting my N7.
Open device manager
Look for Nexus 7
Does it have the yellow triangle on it? If yes, then your ADB driver is not installed, or not installed correctly
In ADB mode it should show up in the device manager as Android ADB Device (or something similar)
arclight25 said:
That sounds like a windows driver issue. I had a similar issue when rooting my N7.
Open device manager
Look for Nexus 7
Does it have the yellow triangle on it? If yes, then your ADB driver is not installed, or not installed correctly
In ADB mode it should show up in the device manager as Android ADB Device (or something similar)
Click to expand...
Click to collapse
Yeah, this was my problem.. That's the only reason I used the toolkit. It wouldnt install right after downloading USB driver through SDK . got me pissed off and uninstalled every driver, and installed my nexus 4 all over also. Some how that one went easy..
Sent from my Nexus 4
LOL op went to yahoo answer, hilarious!
If he is still reading this, USE THE GOD DAMN TOOLKIT FFS, its pretty much idiot proof.
Yea, toolkit is the only way to go.
I think he is stuck in the same place I am stuck in. Whenever I get to the "Reboot Bootloader" in the Toolkit, it fails to go any further. I've made a thread about it here: http://forum.xda-developers.com/showthread.php?p=37524971
The toolkit isn't for everyone, unless of course I'm doing something wrong.
as long as toolkit detects your device, you can simply flash the google image and have everything reset, i dont see how that isnt for everyone honestly......
I used Wugfresh's toolkit and everything worked easily. I dont know any other way to do it, and the toolkit makes it easy for Gnex or Nexus 7.
Hi, now most people here are smart with this type of thing soooo i wanted to ask you how i can root the nexus 7 running 4.2.2. I tried to use the wugfresh NRT but when I was installing drivers a problem occurred. Instead of having ADB drivers or something like that I had ADB Composite drivers installed even though i followed the guide completely and I have tried several times to correct this but i havent found a solution. Also i attempted to carry on the rooting process but it said i did not have the correct drivers installed and etc. So can someone give me a fool proof way of getting the right drivers for this thing so i can root so i can finally install some kernels and use the sixaxis controller app! sorry for the essay and all help is appreciated
hrsedJe Something
Use the THE GOOGLE NEXUS 7 TOOLKIT at : http://forum.xda-developers.com/showthread.php?t=1809195 and then use the files from here : http://forum.xda-developers.com/showpost.php?p=37989110&postcount=1650 and then start the tool and root. easiest solution I know.
If 4.2.2 doesn't show up in the device list, pick 4.2.1, worked fine for me.
How about instead on relying on a tool you know nothing about, you learn how your device works and how to root it manually? This way you aren't stuck dealing with problems like this in the first place.
I could understand the need/desire/etc. for special tools/kits on some branded and locked down devices. But the N7 is as open as it gets. If you have the SDK installed on your computer and a flashable SU zip, you could have your device unlocked and rooted in about 2 minutes.
phonic said:
How about instead on relying on a tool you know nothing about, you learn how your device works and how to root it manually? This way you aren't stuck dealing with problems like this in the first place.
I could understand the need/desire/etc. for special tools/kits on some branded and locked down devices. But the N7 is as open as it gets. If you have the SDK installed on your computer and a flashable SU zip, you could have your device unlocked and rooted in about 2 minutes.
Click to expand...
Click to collapse
Because:
a) It's not necessary.
b) I have been rooting using the manual way, like you described, on every Android phone I've had for the past few years. And every single time I forget how to do it. I always have to look up what I'm doing to refresh my memory.
Spending 2 hours on something won't make you a master, and unless you plan on consistently refreshing your memory and playing around with your phone (when most JUST want root), then there's no ****ing reason to manually learn how to do it.
Kaaji1359 said:
Because:
a) It's not necessary.
b) I have been rooting using the manual way, like you described, on every Android phone I've had for the past few years. And every single time I forget how to do it. I always have to look up what I'm doing to refresh my memory.
Spending 2 hours on something won't make you a master, and unless you plan on consistently refreshing your memory and playing around with your phone (when most JUST want root), then there's no ****ing reason to manually learn how to do it.
Click to expand...
Click to collapse
Dude, most commands for doing stuff on the N7 manually are four words. It really isn't a lot to remember. Also I don't think you understand the purpose of this site/forum.
..That being said.
Use Wug's toolkit and update the adb files in its install directory. Then just use the 4.2.1 settings if 4.2.2 doesn't show.
Here is a post with the files: http://forum.xda-developers.com/showpost.php?p=37989110&postcount=1650
sucks that the toolkit is only for windows, sucky windows
Kaaji1359 said:
Because:
a) It's not necessary.
b) I have been rooting using the manual way, like you described, on every Android phone I've had for the past few years. And every single time I forget how to do it. I always have to look up what I'm doing to refresh my memory.
Spending 2 hours on something won't make you a master, and unless you plan on consistently refreshing your memory and playing around with your phone (when most JUST want root), then there's no ****ing reason to manually learn how to do it.
Click to expand...
Click to collapse
There is a big difference between memorizing commands and actually understanding what they mean. Your post made it very clear that in the "years" you've been doing it, you never possessed the latter.
It is not a complicated process. Unlock bootloader, run custom recovery, flash su zip. Voila. In the amount of time it took you to make your original post you could have been done. If it takes you two hours then you are doing something seriously wrong.
This is a developer forum geared towards people who want to learn how things work, not just look for quick one click tools, and then get upset when things don't work out for them using said tools and people tell them to spend some time educating themselves. If people here spent more time actually learning instead of relying on quick fixes, then we would have to deal with hundreds of posts complaining on how OTA updates were failing because of asserts every time a new one came out.
And your last sentence makes no sense. Obviously there is a reason isn't there?
Sent from my Nexus 7 3G using Tapatalk
http://forum.xda-developers.com/showthread.php?t=2019519
had the same problems
Just google fastboot files for n7, get sdk and pack files AND the recovery into the sdk tool folder.
Shift+right click -> start command here
Fastboot flash recovery recovery.img
Start tab abd sideload the SU.zip (google superuser)
Flash
Done ))
Did it yesterday no issues!
phonic said:
There is a big difference between memorizing commands and actually understanding what they mean. Your post made it very clear that in the "years" you've been doing it, you never possessed the latter.
It is not a complicated process. Unlock bootloader, run custom recovery, flash su zip. Voila. In the amount of time it took you to make your original post you could have been done. If it takes you two hours then you are doing something seriously wrong.
This is a developer forum geared towards people who want to learn how things work, not just look for quick one click tools, and then get upset when things don't work out for them using said tools and people tell them to spend some time educating themselves. If people here spent more time actually learning instead of relying on quick fixes, then we would have to deal with hundreds of posts complaining on how OTA updates were failing because of asserts every time a new one came out.
And your last sentence makes no sense. Obviously there is a reason isn't there?
Sent from my Nexus 7 3G using Tapatalk
Click to expand...
Click to collapse
Well said phonic. I prefer the manual way as well. It is always good to know what you are doing, but knowing how it works and learning something is always better.
I would much rather learn something than to have someone do it for me. If ever I need help and ask someone, they say I'll do it for you I say no, please show me how to do it!
Sent from my Nexus 7 using Tapatalk 2
kidujp said:
Use the THE GOOGLE NEXUS 7 TOOLKIT at : http://forum.xda-developers.com/showthread.php?t=1809195 and then use the files from here : http://forum.xda-developers.com/showpost.php?p=37989110&postcount=1650 and then start the tool and root. easiest solution I know.
If 4.2.2 doesn't show up in the device list, pick 4.2.1, worked fine for me.
Click to expand...
Click to collapse
You may receive an error message "ABD" is offline, in this case download the latest Android SDK manager and upgrade all USB drivers before using the toolkit again.
Sent from my Nexus 7 using xda app-developers app
phonic said:
How about instead on relying on a tool you know nothing about, you learn how your device works and how to root it manually? This way you aren't stuck dealing with problems like this in the first place.
I could understand the need/desire/etc. for special tools/kits on some branded and locked down devices. But the N7 is as open as it gets. If you have the SDK installed on your computer and a flashable SU zip, you could have your device unlocked and rooted in about 2 minutes.
Click to expand...
Click to collapse
Never ceases to amaze me how many pretentious pricks use XDA.... Reminds me of Apple snobs.
command line is the way to go
command line is the way to go m8!!
cheers,
geek endangered
Hey guys, my first post here. I signed up for this forum a little while ago and I've just been a lurker since today. Lots of great stuff on this forum!
I finally got my Nexus 4 phone when they went back on sale in late January, I came from an iPhone 3GS and I've been loving the switch every day since!
But now I have a problem that I hope you guys can help me with.
When I first got my phone the first thing I did was unlock the bootloader and root the device, I had 4.2.1 on my phone and forced the 4.2.2 update by clearing the cache/data of a few apps when it was mentioned on this forum (Bad mistake I think). I went to download titanium with root the other day to start to backup my apps/phone before I started messing with kernels and audio upgrades in case I messed something up and needed to reinstall. Unfortunately since this is my first Android phone I didn't know that upgrading would also remove my root access. Not a problem I though, I'll just go ahead and re-root the device, well that's where I started to see various problems.
I installed the SUser 1.0.4 zip on my phone (After I tried .98), booted up into the clockwork recovery option, extracted the zip from within clockwork to root my device again and nothing. I tried a couple of times, even tried the Nexus 4 toolkit but that didn't seem to work either. Rootchecker won't recognize that my phone is rooted.
In fastboot mode it shows my phone is
Secure boot - enabled (Green)
Lock State - unlocked (red)
When I was in the Nexus 4 toolkit I also noticed that it wouldn't recognize my phone's serial USB debugging mode even when I turned it on (Pressing the build number 7 times and checking the usb debugging box in developer options). When in fastboot mode my computer recognized my phone without a problem. I am still able to move stuff on and off of the phone through windows explorer, but only when it's NOT in debugging mode, my computer beeps like something is connected when in USB debugging mode but nothing shows up anywhere except in device manager. I tried installing the drivers that were posted for 4.2.2 and also tried installing the drivers through the toolkit but neither would fix that problem. Another thing I noticed was that I never got a prompt on my phone to allow my computer access to debugging mode like people mentioned that I should get.
Now either I messed something up somewhere along the lines, (good chance)
or I'm an idiot and i'm missing something really obvious (better chance)
Anyone have any suggestions as to what I can do or how I can get my root access back?
Thanks a bunch in advance for any help you guys can give me, and if I left some info out of here that you need let me know.
kelmino said:
Now either I messed something up somewhere along the lines, (good chance)
or I'm an idiot and i'm missing something really obvious (better chance)
Click to expand...
Click to collapse
Oh wow... yup I'm an idiot and missed something really obvious....
I just installed the SuperSU app from the playstore and I do have root access again and apps request access.
ugh I'm a moron, I spent hours on this yesterday and as soon as I post this I fix the issue
Sorry guys
Now my only problem is I can't see my phone from the playstore on my computer but I'm not worried about that, I think I can fix that as I see another post up here for that same issue.
perhabs this helps
http://forum.xda-developers.com/showthread.php?t=2159744
u dont need to extraxt su zip file....download drivers..use tool kit to unlock bootloader..then flash temporary clockwork recovery...flash su in recovery....download goo manager from playstore to flash permanent recovery
Sent from my Nexus 4 using xda app-developers app
dont use toolkit. do it the long way so you know what you're doing otherwise you're walking in a room blindedly hoping you'd get through the maze.
in the long run, it'll be worth it. very simple & easy to do.
*Now Working for 4.3 Update* Will require an up-to-date install of 4.1.x first and then after re-boot, it will update to 4.3 (read post on next page).
Warning:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Background:
I'm certainly not a developer but can wiggle my way around XDA and figure out what to do and how to do it from time to time without having to ask too many questions. This morning I got the notification that an OTA (over the air) Update was available for my HTC One Dev Edition (running the stock ROM) and I simply downloaded it and tried to flash the zip in Clockwork like I've done with countless other updated nightlies on various phones. It didn't work.
Solution:
I figured out after researching that the custom recovery wouldn't allow the OTA to be flashed and that the stock recovery would be needed to flash the OTA update. I also realized that it took a bunch of different threads to figure out how to make it all work and there didn't seem to be one thread on the HTC One forum that discussed how to do it so I figured I may as well write up what I did to help someone else--after all, so many folks have helped me on this forum and I've rarely had much to contribute of any real depth anyway--just repeating what others already had taught me.
How to:
You need to re-flash the original recovery to your phone so that CWM or TWRP are no longer your recovery. Obviously, now is the time to do a backup and I'd put it somewhere other than on the phone in case you really mess this up.
1. Get the stock recovery bits here https://www.dropbox.com/s/9wbux6a4kn0ndz9/StockRecovery-signed.zip
2. You'll need to un-pack the rar and there is a text file that has the instructions.
3. Of course, I didn't follow the instructions, I just plugged my phone into USB with debugging on and fired up cmd, changed into the directory where I extracted the files, cd'd into fastboot and typed "adb reboot bootloader" and waited until the phone rebooted into bootloader
4. I typed "fastboot devices" and hit enter to make sure I was connected to the phone still
5. Cd.. to get back to where the .bat files are and type install-recovery-windows.bat and the stock recovery is flashed to your HTC One.
6. Now unplug the thing and reboot and you'll get the notification again that the OTA update is ready to install and it will start to install.
7. Mine locked up. That's right, the damn OTA update stopped at about 1/4 of the way through. I figured I bricked the phone. I always figure I bricked it if something doesn't go exactly how I thought it would but I've never actually done it to any of my 6 or so devices. Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2306996&page=2 and I turned off the phone by holding down the power and restarting it. It got all the way through and hung again so I reset the phone again. Then, it rebooted a few times and looked like it was going to never work right again, but I just let it keep rebooting and left it be and after a few minutes, less than 10, probably more than 5, I was back up and running and saw the android applications updating as expected after an update.
8. Now you'll want to re-flash your custom rom (TWRP, CWM) and I did that with Hasoon's All-in-one tool.
9. Re-get Root. You can do that with Hasoon's tool I suppose or however you prefer to root.
AGAIN:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Hopefully someone will come up with a better way to do this and start a new thread and we can delete this one forever.
jay_ntwr said:
Warning:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Background:
I'm certainly not a developer but can wiggle my way around XDA and figure out what to do and how to do it from time to time without having to ask too many questions. This morning I got the notification that an OTA (over the air) Update was available for my HTC One Dev Edition (running the stock ROM) and I simply downloaded it and tried to flash the zip in Clockwork like I've done with countless other updated nightlies on various phones. It didn't work.
Solution:
I figured out after researching that the custom recovery wouldn't allow the OTA to be flashed and that the stock recovery would be needed to flash the OTA update. I also realized that it took a bunch of different threads to figure out how to make it all work and there didn't seem to be one thread on the HTC One forum that discussed how to do it so I figured I may as well write up what I did to help someone else--after all, so many folks have helped me on this forum and I've rarely had much to contribute of any real depth anyway--just repeating what others already had taught me.
How to:
You need to re-flash the original recovery to your phone so that CWM or TWRP are no longer your recovery. Obviously, now is the time to do a backup and I'd put it somewhere other than on the phone in case you really mess this up.
1. Get the stock recovery bits here http://www.androidrevolution.nl/downloader/download.php?file=Flash_recovery_2.17.401.1.rar
2. You'll need to un-pack the rar and there is a text file that has the instructions.
3. Of course, I didn't follow the instructions, I just plugged my phone into USB with debugging on and fired up cmd, changed into the directory where I extracted the files, cd'd into fastboot and typed "adb reboot bootloader" and waited until the phone rebooted into bootloader
4. I typed "fastboot devices" and hit enter to make sure I was connected to the phone still
5. Cd.. to get back to where the .bat files are and type install-recovery-windows.bat and the stock recovery is flashed to your HTC One.
6. Now unplug the thing and reboot and you'll get the notification again that the OTA update is ready to install and it will start to install.
7. Mine locked up. That's right, the damn OTA update stopped at about 1/4 of the way through. I figured I bricked the phone. I always figure I bricked it if something doesn't go exactly how I thought it would but I've never actually done it to any of my 6 or so devices. Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2306996&page=2 and I turned off the phone by holding down the power and restarting it. It got all the way through and hung again so I reset the phone again. Then, it rebooted a few times and looked like it was going to never work right again, but I just let it keep rebooting and left it be and after a few minutes, less than 10, probably more than 5, I was back up and running and saw the android applications updating as expected after an update.
8. Now you'll want to re-flash your custom rom (TWRP, CWM) and I did that with Hasoon's All-in-one tool.
9. Re-get Root. You can do that with Hasoon's tool I suppose or however you prefer to root.
AGAIN:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Hopefully someone will come up with a better way to do this and start a new thread and we can delete this one forever.
Click to expand...
Click to collapse
I appreciate you writing this up. It seems like I've never been able to find a good solution to installing the OTA updates post-root. That being said, do you have any idea what happened in Step 7 that made it finally work? I just don't understand how doing the same thing over and over finally just worked. I want to try installing an update, but I'm a little nervous to do it. And I don't know how else to make the pesky update notification go away without installing it.
trickinit said:
I appreciate you writing this up. It seems like I've never been able to find a good solution to installing the OTA updates post-root. That being said, do you have any idea what happened in Step 7 that made it finally work? I just don't understand how doing the same thing over and over finally just worked. I want to try installing an update, but I'm a little nervous to do it. And I don't know how else to make the pesky update notification go away without installing it.
Click to expand...
Click to collapse
I really have no idea why Step 7 got so strange. The only thing that gave me a warm fuzzy whatsoever was that others were reporting that it was hanging and they just rebooted the phone over and over until it got all the way through the process. It could have something to do with the stock recovery for all I know--a bug perhaps. Again, it made me nervous and I won't do it again. I only did the write up so folks could see what happens and make a call whether or not they wanted to try it themselves and see the steps all on one page instead of getting stuck like I did and then finding the rest of the steps. That part sucked. At least you'll know what you're getting into though. Good luck one way or the other. Please post up if you do go through with it and what your results are.
Thank you for the info! Does sound like an awful lot of work though
jay_ntwr said:
I really have no idea why Step 7 got so strange. The only thing that gave me a warm fuzzy whatsoever was that others were reporting that it was hanging and they just rebooted the phone over and over until it got all the way through the process. It could have something to do with the stock recovery for all I know--a bug perhaps. Again, it made me nervous and I won't do it again. I only did the write up so folks could see what happens and make a call whether or not they wanted to try it themselves and see the steps all on one page instead of getting stuck like I did and then finding the rest of the steps. That part sucked. At least you'll know what you're getting into though. Good luck one way or the other. Please post up if you do go through with it and what your results are.
Click to expand...
Click to collapse
I'm thinking I'll give it a go. I'll do a nandroid backup and store it on my pc. Worst case scenario, I'll just start over from scratch, re-root, and restore my backup. I'll make sure to report my results.
I just makes me wonder why bother using the OTA update if you already went through rooting and flashing custom recovery? It's just one step more to flash the custom ROM and at least you will get constant updates with the developer who created the custom ROM. To me it seems like you either stay stock if you want OTA updates or go the whole hog and use custom ROMs. Just my 2 cents.
shadowboy23 said:
I just makes me wonder why bother using the OTA update if you already went through rooting and flashing custom recovery?
Click to expand...
Click to collapse
Well, in my case, I purchased the Dev edition straight from HTC so I automatically have a de-bloated OS from HTC instead of the ATT ROM that I would have gotten had I purchased the phone from the ATT Store. In that case, I'd no question have a custom ROM from the forum. I just didn't see the need this time around. I would have left the stock recovery, but I do like to make backups so ClockworkMod is something I can't live without. I suppose there are others in that same boat but they are probably few and far between. Really, I just hate to update my ROM since the phone is working how I want at the moment. It's hard to justify just blowing away a functioning OS, setting up everything again, etc. but I may do it again if the OTAs come frequently and/or the process is as strange as it was this past go around.
jay_ntwr said:
Warning:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Background:
I'm certainly not a developer but can wiggle my way around XDA and figure out what to do and how to do it from time to time without having to ask too many questions. This morning I got the notification that an OTA (over the air) Update was available for my HTC One Dev Edition (running the stock ROM) and I simply downloaded it and tried to flash the zip in Clockwork like I've done with countless other updated nightlies on various phones. It didn't work.
Solution:
I figured out after researching that the custom recovery wouldn't allow the OTA to be flashed and that the stock recovery would be needed to flash the OTA update. I also realized that it took a bunch of different threads to figure out how to make it all work and there didn't seem to be one thread on the HTC One forum that discussed how to do it so I figured I may as well write up what I did to help someone else--after all, so many folks have helped me on this forum and I've rarely had much to contribute of any real depth anyway--just repeating what others already had taught me.
How to:
You need to re-flash the original recovery to your phone so that CWM or TWRP are no longer your recovery. Obviously, now is the time to do a backup and I'd put it somewhere other than on the phone in case you really mess this up.
1. Get the stock recovery bits here http://www.androidrevolution.nl/downloader/download.php?file=Flash_recovery_2.17.401.1.rar
2. You'll need to un-pack the rar and there is a text file that has the instructions.
3. Of course, I didn't follow the instructions, I just plugged my phone into USB with debugging on and fired up cmd, changed into the directory where I extracted the files, cd'd into fastboot and typed "adb reboot bootloader" and waited until the phone rebooted into bootloader
4. I typed "fastboot devices" and hit enter to make sure I was connected to the phone still
5. Cd.. to get back to where the .bat files are and type install-recovery-windows.bat and the stock recovery is flashed to your HTC One.
6. Now unplug the thing and reboot and you'll get the notification again that the OTA update is ready to install and it will start to install.
7. Mine locked up. That's right, the damn OTA update stopped at about 1/4 of the way through. I figured I bricked the phone. I always figure I bricked it if something doesn't go exactly how I thought it would but I've never actually done it to any of my 6 or so devices. Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2306996&page=2 and I turned off the phone by holding down the power and restarting it. It got all the way through and hung again so I reset the phone again. Then, it rebooted a few times and looked like it was going to never work right again, but I just let it keep rebooting and left it be and after a few minutes, less than 10, probably more than 5, I was back up and running and saw the android applications updating as expected after an update.
8. Now you'll want to re-flash your custom rom (TWRP, CWM) and I did that with Hasoon's All-in-one tool.
9. Re-get Root. You can do that with Hasoon's tool I suppose or however you prefer to root.
AGAIN:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Hopefully someone will come up with a better way to do this and start a new thread and we can delete this one forever.
Click to expand...
Click to collapse
hi,
one question. this recovery.img i also can use for my htc one 802w? i use the original rom (4.1.2) on my htc one. i make s-off over htcdev.com install cwm802w.img . i become the info the system update to 4.2.2 is available but the phone cant install the update.
any people like help me?
best regards,
ps: sorry for my bad english
Does sound like an awful lot of work though
greengoose_at said:
hi,
one question. this recovery.img i also can use for my htc one 802w? i use the original rom (4.1.2) on my htc one. i make s-off over htcdev.com install cwm802w.img . i become the info the system update to 4.2.2 is available but the phone cant install the update.
any people like help me?
best regards,
ps: sorry for my bad english
Click to expand...
Click to collapse
Just find a stock recovery for 802w, flash it to your phone and you should be fine to to OTA. The original post didn't mention if he's using 802w. If he's not, then the recovery.img can't be used for 802w.
How to get s_off , supercid 11111111
and return to s_on with supercid ?please tell me quickly
Thanks for all friends
Sent from my HTC One using xda premium
Sent from my HTC One using xda premium
I haven't been able to get this to work. I flashed back to the stock recovery, but when I attempt to install the update it gets about half way through before rebooting. It goes back into recovery, starts installing again, but then stops and just shows a red triangle with an exclamation mark. I can get the phone to reboot by holding the power button for 10 seconds, which boots it up normally. When it gets up and running, it's like nothing ever happened, but then the update notification reappears.
trickinit said:
I haven't been able to get this to work. I flashed back to the stock recovery, but when I attempt to install the update it gets about half way through before rebooting. It goes back into recovery, starts installing again, but then stops and just shows a red triangle with an exclamation mark. I can get the phone to reboot by holding the power button for 10 seconds, which boots it up normally. When it gets up and running, it's like nothing ever happened, but then the update notification reappears.
Click to expand...
Click to collapse
I'm experiencing the same thing, can't seem to find anything about it...
With the new 4.3 rolling out on the Dev editions, I decided it was time to try this again. What I found was I had to update to a something prior to the new 4.3. In other words, it was still one of the 1.29 streams that updated first and did just like the last time I did this. The thing stopped, locked up, had to hold the power button down, locked up again, reset again, then it was fine. As soon as the phone booted, the 4.3 update was available and I installed that without any issues. So, the method above still works and even with the weirdness I felt a little better this go around.
Good luck.
sunnyyen said:
Just find a stock recovery for 802w, flash it to your phone and you should be fine to to OTA. The original post didn't mention if he's using 802w. If he's not, then the recovery.img can't be used for 802w.
Click to expand...
Click to collapse
I haven't really checked this thread in weeks. I'm not sure what an 802w is. If you can clarify, I'll check and post.
Totally ran just fine
I had to as stated roll back to the attached recovery, did that with fastboot and no problems, then restarted the phone, then had it start the OTA update, then read around debating if I want CWM or TeamWin, but before I notice, the progress bar got up past half way. Looked away for what must've been less than 5 minutes until it vibrated and was restarting itself. It restarted again, and then it loaded and updated all the apps... Seemed like the smoothest rooted update I've ever done, no forced restarting or anything!
I just bought my HTC One last friday, and I think I screwed up things a little bit, because the first thing I did after I charged it, was updating everything to 4.3, before unlocking the bootloader, getting s-off and before rooting the phone. So I ended up with the latest 4.3 on my phone, but it was a pain in the ass to root it properly. I was able to unlock the bootloader, but something must be different with the way 4.3 treats the internal storage distribution, because I was only able to get root, using TWRP and the latest version of SuperSu, but I wasn´t able to install Busybox.
It's a little bit weird, because although I was able to use Titaniumbackup to install some apps, apps like OTA Rootkeeper don't work properly. I also lost the stock calculator, flashlight and voice recorder, but I was able to install older versions again.
I think the only thing I regret is not getting s-off first, but I think this will only mean that I will have to wait for a revone update, or I will have to flash the boot.img after flashing a custom rom as I always did with my One X.
jay_ntwr said:
I haven't really checked this thread in weeks. I'm not sure what an 802w is. If you can clarify, I'll check and post.
Click to expand...
Click to collapse
802w is Chinese dual sim version with different radio frequency
Sent from my HTC One dual sim using xda app-developers app
deepforest said:
802w is Chinese dual sim version with different radio frequency
Sent from my HTC One dual sim using xda app-developers app
Click to expand...
Click to collapse
That is not the one I have then.
I have a rooted HTC one with stock rom. I relock the bootloader and I also have stock recovery.
I am on 4.19.401.5 version.
So, will it be possible for me to have new OTA update including Sense 6?
Should I install the missing applications also, like calculator and flashlight?
Hi all, I've messed up with my nexus 7 2013 and i think its soft bricking.
I was using multirom and accidentally installed the wrong kernel. Every time I boot into android (4.4) it loads slow and then instead of displaying the screen it shows two duplicated top left hand corners and remains unresponsive.
Unfortunately i never got the chance to enable usb debugging and my bootloader is locked.
I tried a few things suggested online but they didn't work and multiform appears to have been wiped.
Recovery still works (TWRP) but I'm really in a bind.
Any help on getting back to stock android 4.4 would be amazing, but please bear in mind I'm new to android, so please provide detailed instructions.
Probably your best way would be using fastboot, can't give you details but I have seen it on here. Google fastboot nexus 7.
Sent from my Nexus 10 using XDA Free mobile app
gandy92 said:
Hi all, I've messed up with my nexus 7 2013 and i think its soft bricking.
I was using multirom and accidentally installed the wrong kernel. Every time I boot into android (4.4) it loads slow and then instead of displaying the screen it shows two duplicated top left hand corners and remains unresponsive.
Unfortunately i never got the chance to enable usb debugging and my bootloader is locked.
I tried a few things suggested online but they didn't work and multiform appears to have been wiped.
Recovery still works (TWRP) but I'm really in a bind.
Any help on getting back to stock android 4.4 would be amazing, but please bear in mind I'm new to android, so please provide detailed instructions.
Click to expand...
Click to collapse
Wugfresh toolkit should also work, especially if you are not familiar with or interested in learning fastboot & adb.
wtherrell said:
Wugfresh toolkit should also work, especially if you are not familiar with or interested in learning fastboot & adb.
Click to expand...
Click to collapse
I used the Wugfresh tookkit and it worked like a charm!
Thank you both for getting back to me and helping me fix this. I really appreciate it!