Related
[K1] "Unsupported menu option selected" error & where to get TimmyDean rooted 13-13?
I just got a brand new K1. Fresh out of the box with 3-3 pre-installed, I downloaded and used TimmyDean's permanent root tool, flashing a rooted 2-2 firmware. I then enabled the backdoor and ran all the OTA updates up to 14-14. This took several hours in all. I then ran the BusyBox and SU Tools install script. Everything was looking okay. I selected the choice to exit the script with reboot. The K1 turned off and came back on with the Lenovo logo, but, at the top of the screen was red writing:
Unsupported menu option selected: 1
Unrecoverable bootloader error (0x00000002).
It stops there and goes no further. No bootup.
Attempting to research the error, it seems this is not an error too many people encounter or know about, so my guess is that my only way of fixing this problem is to flash the whole thing over again from the beginning. (Unless someone here knows something about this problem. That would be tremendously helpful.)
Having already experienced what it took to go from 2-2 to 14-14 the first time with the permanent root package, I'd certainly like to shortcut it however possible. In this thread, http://forum.xda-developers.com/showthread.php?t=1404351 , TimmyDean posted a rooted 13-13 that we can start from. However, the link to the download file for it is Multiupload.com, and Multiupload.com does not seem to be up for me. Does anyone know where else I can go to try and download a copy?
I'd have posted directly in that Development thread, but, since I am an XDA noob, the forum system only allows me to post in this General section.
After experimenting with the "permanent root" package several times now, each time ending up with the "Unsupported menu option selected: 1" error after any OTA update, I have to believe there is an incompatibility between the K1 I have and the bootloader files in the "permanent root" package. I do not know if my K1 is recently manufactured and they are now doing something different with them that causes this incompatibility or what, but I felt I should warn you all that flashing the "permanent root" package could cause your K1 to not take official updates or to otherwise brick it with the "unsupported menu option" error. Perhaps the 13-13 package, which I don't have and can't test, didn't have this problem.
My serial number is CB1245XXXX. Manufacture date is "11/11/27."
I have now given up on getting root on my K1 and would just be happy to get it back to a working condition that can take Lenovo's OTA updates without bricking. I am currently trying these instructions and will update as to whether or not that resolves the problem: rootzwiki.com/topic/13877-guide-ideapad-k1-restore-to-mostly-stock-with-ota-updates/ (The forum software will not allow me to post hot links, so copy and paste that to browser.)
The rootzwiki procedure did not work to correct the problem. After any update, the tablet is bricked with the error. There are a few threads on the Lenovo support forum on this issue now, and there is no solution.
forums.lenovo.com/t5/IdeaPad-Slate-Tablets/K1-not-booting-after-update/td-p/548285
forums.lenovo.com/t5/IdeaPad-Slate-Tablets/Unrecoverable-Boot-Loader-Error/td-p/683633
I believe these old bootloader files will not work and will brick newer K1's, so my warning is:
DO NOT ATTEMPT TO ROOT YOUR K1'S. DO NOT CHANGE THE EXISTING BOOTLOADER IN ANY WAY WITH NVFLASH. SOMETHING HAS CHANGED.
This might only apply to more recently manufactured K1's, but, since we do not know when this problem begins, it is not possible to know beforehand whether or not you will brick yours.
To be on the safe side, DO NOT ATTEMPT TO ROOT YOUR K1'S. DO NOT CHANGE THE EXISTING BOOTLOADER IN ANY WAY WITH NVFLASH. SOMETHING HAS CHANGED.
Unfortunately, there was no backup option in the rooting packages, so I could not get a copy of the stock bootloader or any other files, if they are indeed of a different and newer variety. If someone has a recently manufactured K1, perhaps you can get those files and share them, because a lot of people are starting to see this problem now.
I have one with sn#1250xxxx, mfg dt 11/11/29. I wasn't even trying to root the thing. I happened during an OTA update. I tried probably all the recovery/rooting option out there. None of them worked. I have the tablet booting at lenovo screen. But I think you are right about the bootloader. If we can get the correct bootloader, we might be able to the the tablet back to life.
fix?
Has anyone come out with the fix for your issue.. I have the same issue . Used TImmy Dean's method.. and anything updating past the 02_02 (loaded from the tool I get the error... Anyone here have access to contact JimmyDean to ask him for help?
I see that he updated the tool to K1_A301_13_13_111209_US and maybe K1_A301_14_14_111209_US but all the links are dead.. anyone have a good place to download the files?
Try out the downloads on the following Lenovo's link -
download.lenovo.com/slates/k1/OTA
those are just OTs.. not image files.. If you don't have a compatable boot loader, you can't load those files.. We don't have a compatable bootloader.. so this is why we need ver 13 of timmy dean..
rezapatel said:
Try out the downloads on the following Lenovo's link -
download.lenovo.com/slates/k1/OTA
Click to expand...
Click to collapse
Can someone who's getting this bootloader error send me a pm. I put together a stock 120109 update that may work around the issue and I need someone to test.
Was this issue ever resolved, I didnt attempt to root mine, only attempted to wipe it clean and got this..
No, no real resolution. What I ended up doing was NVFlashing one of khanning's ROMs, like this one: http://forum.xda-developers.com/showthread.php?t=1560441
I don't know what's going to happen when I have to update again, such as the upcoming Ice Cream Sandwich update promised by Lenovo.
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.
If you are having issues rooting your kindle with guides online the reason behind it is that you are using an outdated version of "Root_with_Restore_by_Bin4ry_v*" Currently most of the guides all have you downloading and using Root_with_Restore_by_Bin4ry_v17. You want to use a version of Root_with_Restore_by_Bin4ry_v version 21 or above. I did mine with version 21 and my gf's with version 28. I just wanted to make sure that it would work with a latest i could find.
Root_with_Restore_by_Bin4ry_v21 can be found with the link provided below. You can also google other Root_with_Restore_by_Bin4ry_v and try them out until you get your kindle rooted.
apparently i can't link outside
d -h.st /dm9
just copy it and paste it then backspace on the spaces to make it a usable url
Re Routing kindle that has updated
Ferrous said:
If you are having issues rooting your kindle with guides online the reason behind it is that you are using an outdated version of "Root_with_Restore_by_Bin4ry_v*" Currently most of the guides all have you downloading and using Root_with_Restore_by_Bin4ry_v17. You want to use a version of Root_with_Restore_by_Bin4ry_v version 21 or above. I did mine with version 21 and my gf's with version 28. I just wanted to make sure that it would work with a latest i could find.
Root_with_Restore_by_Bin4ry_v21 can be found with the link provided below. You can also google other Root_with_Restore_by_Bin4ry_v and try them out until you get your kindle rooted.
apparently i can't link outside
d -h.st /dm9
just copy it and paste it then backspace on the spaces to make it a usable url
Click to expand...
Click to collapse
hi, thanks for the above.
as a total noob to this, i sppent most of thursday researching how to do this, then carried it out eventually successfully too, only to wanke up on friday morning to see my device had updated to 7.3.1.
ive now downloaded binary v28, root with restore - how do i use this version? i used this guide -
androidforums com/kindle-fire-hd-all-things-root/669366-idiots-guide-rooting-kindle-fire-hd-7-7-2-3-a.html
to carry out my rooting, so i now need to know how to do it using the v28 version, and if there is any differences to the process linked above.
also, i downloaded droidwall, and thought i had blocked the updating app, but it obviously hadnt. then i noticed at the top it said "firewall disabled" how do i enable this?
and finally, how do i get to change the launcher / user interface/ how can i change this to a one similar to the galaxy tab or something else like this?
yes, i am a noob, and all help is welcome guys. many thanks in advance.
jaktlad said:
hi, thanks for the above.
as a total noob to this, i sppent most of thursday researching how to do this, then carried it out eventually successfully too, only to wanke up on friday morning to see my device had updated to 7.3.1.
ive now downloaded binary v28, root with restore - how do i use this version? i used this guide -
androidforums com/kindle-fire-hd-all-things-root/669366-idiots-guide-rooting-kindle-fire-hd-7-7-2-3-a.html
to carry out my rooting, so i now need to know how to do it using the v28 version, and if there is any differences to the process linked above.
also, i downloaded droidwall, and thought i had blocked the updating app, but it obviously hadnt. then i noticed at the top it said "firewall disabled" how do i enable this?
and finally, how do i get to change the launcher / user interface/ how can i change this to a one similar to the galaxy tab or something else like this?
yes, i am a noob, and all help is welcome guys. many thanks in advance.
Click to expand...
Click to collapse
Yeah the only difference is that you are using an upgraded version of program they have so instead of using v17 use newer version. I think once you install the new google play store all you have to do is find GO Launcher in the market place.
Ferrous said:
Yeah the only difference is that you are using an upgraded version of program they have so instead of using v17 use newer version. I think once you install the new google play store all you have to do is find GO Launcher in the market place.
Click to expand...
Click to collapse
thanks for that. how do i install it and launch it once ive rerooted and downlaoded go launcher?
also, if this works, can anyone advise on the correct way to disable updates - as said above, i thought i had done it, but obviously not lol.
jaktlad said:
thanks for that. how do i install it and launch it once ive rerooted and downlaoded go launcher?
also, if this works, can anyone advise on the correct way to disable updates - as said above, i thought i had done it, but obviously not lol.
Click to expand...
Click to collapse
Download DroidWall from the googplaystore, that app disables updates. I don't know much about golauncher. If you follow the guide and have googleplaystore then you should be able to download everything.
I have confirmed that Bin4ry (I used v26) method works fine for both 7.3.0 and the new 7.3.1 update that is just rolling out. Here are some instructions that hopefully is clear for everyone (link). Obviously the main credit goes to the root method.
Was having trouble getting root again after my kindle went to 7.3.1. This worked for me. Thanks for the help!
Problems with attempting to root on 7.3.1
Hello-
I have used the "Root with Restore by Bin4ry_v29" to no avail and I am extremely perplexed as to whats going wrong. I have followed all the instructions outlined and during the process I do see multiple instances within the application saying "permissions denied" yet it continues as if everything is ok. Well, once it says everything is finished and I have rebooted the device multiple times, its EXTREMELY sluggish and borderline unresponsive. It also doesn't have root access as Superuser isn't on the device. So I am asking for any advice/guidance anyone can provide that maybe knows whats up or has had this happen and knows what the problem is.
Please help!
ps: Not new to rooting either as I have rooted all the android phones I have ever had with no problems but I know the Kindle is a different beast.
Thanks!
I'm on my phone so I can't post the link but if you search you'll find it, but I just rooted a new KFHD four days ago by using prokenexus how to root for noon guide. I followed it from start to finish and was completely successful. Took a total of about 45 minutes. He has two ways to root in his thread, automated and manual. I always like doing manual so I can see everything that is going on. But it worked like a charm. So might want to give that a look.
from my Viped out one x
Used this method on my kindle and it worked flawlessly without issue
7.4.1!
Coderedpl said:
Used this method on my kindle and it worked flawlessly without issue
Click to expand...
Click to collapse
So did I - and it worked happily for three seconds until it rebooted again and I found I had 7.4.1 on the Kindle.
I can't find anything else on the web atm on 7.4.1 so either I've been hacked or I'm one of the first to get it.
I just did mine a second ago. Second time Ive done this, but I cant rememeber what i did last time to remedy the issue. Once I did it, it fixed the lag. hmmm... someone please help me remember....
DroidJay123 said:
Hello-
I have used the "Root with Restore by Bin4ry_v29" to no avail and I am extremely perplexed as to whats going wrong. I have followed all the instructions outlined and during the process I do see multiple instances within the application saying "permissions denied" yet it continues as if everything is ok. Well, once it says everything is finished and I have rebooted the device multiple times, its EXTREMELY sluggish and borderline unresponsive. It also doesn't have root access as Superuser isn't on the device. So I am asking for any advice/guidance anyone can provide that maybe knows whats up or has had this happen and knows what the problem is.
Please help!
ps: Not new to rooting either as I have rooted all the android phones I have ever had with no problems but I know the Kindle is a different beast.
Thanks!
Click to expand...
Click to collapse
---------- Post added at 03:06 AM ---------- Previous post was at 02:51 AM ----------
Found this article and worked.
Super slow after boot solved!
Ok even though this guide stated that if you are on version 7.2.3, you don't need to run rootqemu. Bat method, that was not true in my case. After running through the runme phase in cmnd prompt, choosing normal root, and letting the process finish and reboot, my device was ridiculously slow, and not rooted might I add. Here's the trick though, immediately after that process finishes, you need to run the Rootqemu method also. But when you try to run Rootqemu.bat by right clicking and running as administrator, it doesn't recognize the device. What I had to do was left click on ONLY the folder that contained the Rootqemu files, and while only that folder is highlighted, you hold down the shift key and right click on the folder. Then you are going to click on "run command prompt here". Once the command prompt opens, you are going to type Rootqemu.bat and press enter. Then you can press 1 to root, let the program run through its few stages, and after it reboots several times and finishes it's process, voila no more lag, and you should be finally rooted. Also after that process, download a program called Kindlefree. It's an absolutely amazing, and simple way to install all the essential Google apps "aka" Gapps to your rooted Kindle fire hd. I hope this helps everyone like it did me!
scooby092477 said:
I just did mine a second ago. Second time Ive done this, but I cant rememeber what i did last time to remedy the issue. Once I did it, it fixed the lag. hmmm... someone please help me remember....
Click to expand...
Click to collapse
Funny thing
cthonus said:
So did I - and it worked happily for three seconds until it rebooted again and I found I had 7.4.1 on the Kindle.
I can't find anything else on the web atm on 7.4.1 so either I've been hacked or I'm one of the first to get it.
Click to expand...
Click to collapse
I Have i too but i accidentally cut the kindle off in the prosses so i kinda have it. all i got out of it was adding the batt % in status bar. also amazon says it is a minor update so there are no release notes.
For future referencef any further visitors
Hello fellow users and visitors. I've been following this site for a while now, yes I'm considered a "noob" here but I have my experiences well beyond the level of a "noob." This is my first post, and I indeed have a KF HD 7. Since there is so much confusion as far as CLEAR NEWBIES INSTRUCTIONS, I've decided to give everyone the guide I used to root my Kindle, which was derived from a guide here at XDA itself. You can find it here at
androidcowboy (DOT) com /2013/04/root-kindle-fire-hd-7-3-0-firmware/
This DOES indeed work for 7.3.1 as mine was, it took me two tries. But heed my warning, rooting this beauty MAY cause some issues as it has to mine such as randomly shutting off, battery showing up as 0% on some occasions when it is turned on, and sometimes refusing to charge more frequently than it used to. Those issues eventually happen without root, some people have these problems the first week of having a fresh new KFHD7, and I have friends with the same Kindle, rooted, and theirs do not present same issue, so I guess some do some don't.
Good luck and happy rooting. Now you can revive Google Play!
Another confirmation for 7.3.1. I followed Android Cowboy's procedures for both rooting and installing Google Play. Very easy. Thanks Cowboy!
Sent from my KFTT using Tapatalk HD
If you have issues rooting, please go to my thread in my signature. I addressed the issue of rooting on 7.3.1, and have written quick explanation for rooting with Bin4ry's method. The guide goes on to help you flash a custom ROM, should you so desire to get rid of that nasty Amazon OS interface.
*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?
I have rooted countless phones accross all different manufacturers but never found one as stupid to root as this phone!
There isn't an up to date thread about rooting the phone so I thought I'd share how I did it and got through various things that were not supposed to happen but did!
Firstly, unlocking the Bootloader - as Huwai don't provide a code anymore, I went down the https://www.dc-unlocker.com/ route. It is cheap at £4 and they take PayPal. The unlock code video is out of date which didn't help and I presse3d the wrong button first and got a unlock network code by mistake, so had to pay another £4 to do it again. I used this tool (minimal adb) from this thread (https://forum.xda-developers.com/showthread.php?t=2317790) to put the code in the phone but noticed that my phone wouldn't keep the USB Debugging active and had to slide it on each time I connected to the computer (even had to revoke the computer at one point and reconnect).
From an unlocked bootloader the biggest problem I had was finding a way to put TWRP on the phone. All the threads I could see contained the wrong code to flash and so it always failed. However Dru79 showed the correct form which was to connect in fastboot then use minimal adb (on windows 10, open from the start menu, not left shict right click and 'open window here') and use " fastboot flash recovery_ramdisk TWRP-3.2.3-0-Hi6250-Askuccio-v1.0.img " - the correct TWRP is here (https://forum.xda-developers.com/p8.../recovery-twrp-3-2-3-0-huawei-hi6250-t3859959)
HOWEVER - my phone would not keep TWRP and more often (over 75% of the time) would boot to stock recovery, SO after I flashed the TWRP I typed in "fastboot reboot" and as I pressed ENTER, I took the power cord out from the phone and used the volume UP and the Power key to get into TWRP. I don't know why my phone wouldn't keep TWRP but it didn't.
Getting root through SuperSU was IMPOSSIBLE no matter how I tried, eventually I downloaded Magisk from (https://www.xda-developers.com/how-to-install-magisk/) and flashed it through TWRP.
Once rooted, I downloaded the PixyOS from https://forum.xda-developers.com/p8lite/p8-lite-2017-development/rom-pixysos-huawei-hi6250-t3852152 and flashed it...perfect!
Hope this helps someone.
The funny thing is, I actually wanted to post a thread about it in General Section as I had the same frustration as you whole trying to root and install custom ROM on this phone (I've done countless Root's, flashes, unlocking before on couple of phones) and just couldn't find a thread that explains this properly.
Anyway since you already done this, this should be moved to General Section so people can see this properly.
I've flashed Pixy's OS on my phone about 4 weeks ago and just one thing you didn't mention is that if you're on 7.1 nougat then you need to upgrade to Oreo and then install TWRP (I found that out when I tried getting it on nougat and then got errors while flashing and realised the TWRP was developed to work on Oreo). Just get a stock image of Oreo and flash it, the link for it it's somewhere around in the forum, I think it's some kind of Russian website but works well.
Anyway great job, if we can just ask Mod to move this to General section so that this guide can aid new users in rooting their phones properly and efficiently so that they can minimize their changes of encountering errors (as me and OP did).
proadi96 said:
The funny thing is, I actually wanted to post a thread about it in General Section as I had the same frustration as you whole trying to root and install custom ROM on this phone (I've done countless Root's, flashes, unlocking before on couple of phones) and just couldn't find a thread that explains this properly.
Anyway since you already done this, this should be moved to General Section so people can see this properly.
I've flashed Pixy's OS on my phone about 4 weeks ago and just one thing you didn't mention is that if you're on 7.1 nougat then you need to upgrade to Oreo and then install TWRP (I found that out when I tried getting it on nougat and then got errors while flashing and realised the TWRP was developed to work on Oreo). Just get a stock image of Oreo and flash it, the link for it it's somewhere around in the forum, I think it's some kind of Russian website but works well.
Anyway great job, if we can just ask Mod to move this to General section so that this guide can aid new users in rooting their phones properly and efficiently so that they can minimize their changes of encountering errors (as me and OP did).
Click to expand...
Click to collapse
I have asked