Related
Who should read this post?
You have updated your One X to a newer version via OTA, then you want to restore the software/ return stock but the latest RUU is not available. (boot to fastboot mode and type the following command "fastboot getvar version-main", This is the true version of your phone!)
You have some basic skills to flash things using "fastboot"
Those who want to back to stock and wait for the JB OTA.
Those with ICS hboot should works without any problem, someone had test it on JB hboot and works(updated in step 6, 7). but we need more testers.
The concept behind.
1. Fool the RUU to make it believe that it is flashing the latest ROM, but actually, we are flashing an older version.
2. after that, boot up the phone with older version of software, then OTA and update the phone to latest software.
How to do that?
0. backup all your stuff including those in SD, all your stuff in your phone will be lost. Then wipe all data (including SD) using your custom recovery. (important! Otherwise, you may not be able to receive OTA).
1. You have to download a "custom RUU" that can be found here.
http://db.tt/z8ajRTuH
Feel free to give a thanks to billd2439, he provide this working link to download the custom RUU.
Just go to #115 http://forum.xda-developers.com/showthread.php?p=35139501#post35139501 and give him a thanks
2. Download the ROM file, it should be in zip format. (You can also extract the rom file by running a RUU, just run the RUU, don't click anything and search the computer for "rom.zip") (In my case, I have an older version 1.29.708.15 rom extracted from RUU)
you may want to find RUU here http://www.htcruu.com
3. unzip the customRUU.zip to a folder, e.g. "customRUU"
4. unzip and extract "android-info.txt", "boot_signed.img" and "system.img" to a folder
5. open android-info.txt with "notepad" (notepad++ is highly recommended)
6. type the following command to get the information from your phone.
fastboot getvar all
you should pay attention to the following information
modelid:
cidnum:
mainver:
hbootpreupdate:
7. edit the value of "modelid", "cidnum", "mainver" and "hbootpreupdate" to match the information you get from step 6.
by doing this your will try to fool the RUU to belive that you are going to flash a newer version e.g (I have OTA my phone to 2.17.708.7, but now I want to fool the RUU with this old rom with a version number of 1.29.708.15, so I change the value to 2.17.708.7 )
Thanks ahmedaljaf for telling me to modify hbootpreupdate to makes JB downgrade works
8. save the file.
9. zip "android-info.txt", "boot_signed.img" and "system.img" and rename the zip to "rom.zip". (remember only zip the files, not the whole folder!)
10. place the "rom.zip" you just created to the "customRUU" folder
11. make sure your phone is still "unlock", remember to turn on USB Debugging, unplug the USB cable and reboot your phone, then goto fastboot mode and connect the USB cable.
(important, do the above to avoid error messages in RUU)
12. run the file "ARUWizard.exe" inside the folder "customRUU" (see the Attached Readme_Eng.pdf if the customRUU cannot display in correct language)
You can change the customRUU to English version by just delete or rename the language file "ARUWizard_Eng.lng" (Thanks ahmedaljaf for telling me this :good
13. follow the on screen instruction,
14. your phone should reboot and boot up with and old version of software.
15. restart the phone and go to fastboot mode.
16. extract the "recovery_signed.img" from your old "rom.zip" (not the rom.zip you create! ) and place it to some where.
17. flash the recovery by typing the following command "fastboot flash recovery recover_signed.img"
18. relock the phone
19. boot up the phone and try OTA
18. if the OTA download finish but fail to reboot to recovery update automatically, just manually boot to recovery and the update will be ok.
If you can return stock with this method, please reply and list the version here. And you can give me a "thanks" :good:
I wonder, if you put in the "rom.zip" the "hboot_0.95.0000.img" from an older RUU will you be able to downgrade the 1.28 hboot also?
There's NO way to downgrade hboot unless you have s-off.
Sent from my HTC One X using xda premium
ionut.micu said:
I wonder, if you put in the "rom.zip" the "hboot_0.95.0000.img" from an older RUU will you be able to downgrade the 1.28 hboot also?
Click to expand...
Click to collapse
They are somebody on chinese forum who use this method claimed he was able to do hboot downgrade through this method, but no one seem suceed so for.
Well, technically this method able to get you spoof ROM version because it check on your PC. While for hboot it validate the signature and version on the phone before upgrading itself. You can see the process if you push the firmware yourself via fastboot.
HebeGuess said:
They are somebody on chinese forum who use this method claimed he was able to do hboot downgrade through this method, but no one seem suceed so for.
Well, technically this method able to get you spoof ROM version because it check on your PC. While for hboot it validate the signature and version on the phone before upgrading itself. You can see the process if you push the firmware yourself via fastboot.
Click to expand...
Click to collapse
What if we hex edit the 0.95.0000 before we put it into the rom.zip to make it think that it's a newer version, will that brake the signature?
Sorry but I don't have the guts to try it myself
a good link
hokoonho said:
Who should read this post?
You have updated your One X to a newer version via OTA, then you want to restore the software/ return stock but the latest RUU is not available.
You have some basic skills to flash things using "fastboot"
Those who want to back to stock and wait for the JB OTA.
The concept behind.
1. Fool the RUU to make it believe that it is flashing the latest ROM, but actually, we are flashing an older version.
2. after that, boot up the phone with older version of software, then OTA and update the phone to latest software.
How to do that?
0. backup all your stuff including those in SD, all your stuff in your phone will be lost.
1. You have to download a "custom RUU" that can be found here (you can also found a rom that for One X for HK only).
http://pan.baidu.com/share/link?shareid=64762&uk=1042525484
If your phone is from other region, you may want to find the rom or RUU here http://www.htcruu.com
2. Download the ROM file, it should be in zip format. (You can also extract the rom file by running a RUU, just run the RUU, don't click anything and search the computer for "rom.zip") (In my case, I have an older version 1.29.708.15 rom extracted from RUU)
3. unzip the customRUU.zip to a folder, e.g. "customRUU"
4. unzip and extract "android-info.txt", "boot_signed.img" and "system.img" to a folder
5. open android-info.txt with "notepad" (notepad++ is highly recommended)
6. edit the value of"cidnum" to match your phone, e.g. ("HTC__622" for HK, "HTC__621" for Taiwan)
7. edit the value of "mainver" to the current software version your phone. e.g (I have OTA my phone to 2.17.708.7, but now I want to fool the RUU with this old rom with a version number of 1.29.708.15, so I change the value to 2.17.708.7 )
8. save the file.
9. zip "android-info.txt", "boot_signed.img" and "system.img" and rename the zip to "rom.zip". (remember only zip the files, not the whole folder!)
10. place the "rom.zip" you just created to the "customRUU" folder
11. make sure your phone is still "unlock"
12. run the file "ARUWizard.exe" inside the folder "customRUU"
13. follow the on screen instruction,
14. your phone should reboot and boot with and old version of software.
15. restart the phone and go to fastboot mode.
16. extract the "recovery_signed.img" from your old "rom.zip" (not the rom.zip you create! ) and place it to some where.
17. flash the recovery by typing the following command "fastboot flash recovery recover_signed.img"
18. relock the phone
19. boot up the phone and try OTA
18. if the OTA download finish but fail to reboot to recovery update automatically, just manually boot to recovery and the update will be ok.
Click to expand...
Click to collapse
link to custom ruu its dead. any alternative?
ionut.micu said:
I wonder, if you put in the "rom.zip" the "hboot_0.95.0000.img" from an older RUU will you be able to downgrade the 1.28 hboot also?
Click to expand...
Click to collapse
No, if you include the old hboot, the process will be fail.
Sent from my HTC One X using xda premium
darckreign1984 said:
link to custom ruu its dead. any alternative?
Click to expand...
Click to collapse
link updated, enjoy
Sent from my HTC One X using xda premium
or you could just cook yourself a flashable zip from the rom.zip. Then fastboot flash rec and boot. Chances are ics wont boot on the newer hboots. Still the ota can be flashed as update.zip maybe.
usefull for some case
bookmarked
BRILLIANT! Absolutely brilliant! Thanks a million hokoonho. This method worked like a treat on my HK_621 HOX which was running ARHD 9.7.2
unsucces
speedofheat said:
BRILLIANT! Absolutely brilliant! Thanks a million hokoonho. This method worked like a treat on my HK_621 HOX which was running ARHD 9.7.2
Click to expand...
Click to collapse
arhd 12 and hboot 1.28 - not working
the 10 min time to flash its useles.... nothing its flashing in this time
darckreign1984 said:
arhd 12 and hboot 1.28 - not working
the 10 min time to flash its useles.... nothing its flashing in this time
Click to expand...
Click to collapse
The method works well with ICS, even with other HTC model as well, but I am not sure if it still work will JB and latest hboot. But it won't kill your phone.
Sent from my HTC One X using xda premium
I have followed the instructions, and now I am at the point where I run "ARUWizard" and follow the onscreen instructions...
However, The test is not English, it is funny looking as if the language is corrupt/unrecognised.
See attachment.
Any advice?
lukems said:
I have followed the instructions, and now I am at the point where I run "ARUWizard" and follow the onscreen instructions...
However, The test is not English, it is funny looking as if the language is corrupt/unrecognised.
See attachment.
Any advice?
Click to expand...
Click to collapse
It's OK, The RUU may not be able to select the right language to display, but It still works, since the RUU only use adb and fastboot to finish its process, and all these adb and fastboot are run in English...
A brief translation was made for those cannot Open the customRUU in correct language. go to OP for the pdf file
hokoonho said:
It's OK, The RUU may not be able to select the right language to display, but It still works, since the RUU only use adb and fastboot to finish its process, and all these adb and fastboot are run in English...
I am translating the Text to English and will upload a guide, just follow the guide to click the buttons... wait for a few minutes please.
Click to expand...
Click to collapse
No problem, I have found an English version.
I am finding that I get a Error 170 USB error... I believe this is because I have an unlocked bootloader.
So I re-locked the bootloader... and found myself unable to get past the bootloader.
I managed to run the RUU whilst phone was at the bootloader screen,
Replaced the temp rom.img with the created rom.img in your guide,
But it ended up failing with a Error 132 signature check.
I am not sure how to proceed.
lukems said:
No problem, I have found an English version.
I am finding that I get a Error 170 USB error... I believe this is because I have an unlocked bootloader.
So I re-locked the bootloader... and found myself unable to get past the bootloader.
I managed to run the RUU whilst phone was at the bootloader screen,
Replaced the temp rom.img with the created rom.img in your guide,
But it ended up failing with a Error 132 signature check.
I am not sure how to proceed.
Click to expand...
Click to collapse
Could you provide a ling to the English version you've got ? Thanks
lukems said:
No problem, I have found an English version.
I am finding that I get a Error 170 USB error... I believe this is because I have an unlocked bootloader.
So I re-locked the bootloader... and found myself unable to get past the bootloader.
I managed to run the RUU whilst phone was at the bootloader screen,
Replaced the temp rom.img with the created rom.img in your guide,
But it ended up failing with a Error 132 signature check.
I am not sure how to proceed.
Click to expand...
Click to collapse
Don't relock at this moment, otherwise, you will not be able to flash the stock recovery. Unlock it first. Make sure USB debugging is on, then REBOOT to fastboot and start the RUU. Or...Try another USB cable, DON'T connect via a USB hub...
Sent from my HTC One X using xda premium
hokoonho said:
Don't relock at this moment, otherwise, you will not be able to flash the stock recovery. Unlock it first. Make sure USB debugging is on, then REBOOT to fastboot and start the RUU. Or...Try another USB cable, DON'T connect via a USB hub...
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Ok will try now.
Edit: I am now waiting for it to finish... we will see soon enough if it works.
Screenshot showing upgrade screen uploaded.
Edit 2: It completed successfully
build downgraded from 2.17.401.2 to 1.28.771.9
lukems said:
I have followed the instructions, and now I am at the point where I run "ARUWizard" and follow the onscreen instructions...
However, The test is not English, it is funny looking as if the language is corrupt/unrecognised.
See attachment.
Any advice?
Click to expand...
Click to collapse
lukems said:
Ok will try now.
Click to expand...
Click to collapse
I have updated step 11. should disconnect the USB cable during reboot. If it still not work, restart both your phone and PC.
Hey all,
So I received a notification for a system update to 4.4.3, and I had survival mode in SuperSU checked, so I went ahead and followed the procedure. Turns off, then reboots into TWRP. From there I reboot again using the TWRP option, and it boots into android just fine. Notification is gone, still with root. But then I go to settings >> about to find that I'm still running on 4.4.2. Manually check for update, says there isn't one available. Give it a day or so and the notification comes up again. Repeat, and same thing. I'm stuck with the notification again.
So, how do I get rid of the notification, or more preferably, how to I update to 4.4.3 keeping the root? Thanks.
UnfriendlyTurtle said:
Hey all,
So I received a notification for a system update to 4.4.3, and I had survival mode in SuperSU checked, so I went ahead and followed the procedure. Turns off, then reboots into TWRP. From there I reboot again using the TWRP option, and it boots into android just fine. Notification is gone, still with root. But then I go to settings >> about to find that I'm still running on 4.4.2. Manually check for update, says there isn't one available. Give it a day or so and the notification comes up again. Repeat, and same thing. I'm stuck with the notification again.
So, how do I get rid of the notification, or more preferably, how to I update to 4.4.3 keeping the root? Thanks.
Click to expand...
Click to collapse
You can't update the "normal way" like that with a custom recovery. When you try to do that, it tries to boot into the stock recovery to update, but since you have a custom recovery, it will fail everytime if you do it that way. What you have to do is flash the OTA zip using TWRP. You can find the OTA zip in /cache on your device. Or you can just download the update zip from these forums.
UnfriendlyTurtle said:
Hey all,
So I received a notification for a system update to 4.4.3, and I had survival mode in SuperSU checked, so I went ahead and followed the procedure. Turns off, then reboots into TWRP. From there I reboot again using the TWRP option, and it boots into android just fine. Notification is gone, still with root. But then I go to settings >> about to find that I'm still running on 4.4.2. Manually check for update, says there isn't one available. Give it a day or so and the notification comes up again. Repeat, and same thing. I'm stuck with the notification again.
So, how do I get rid of the notification, or more preferably, how to I update to 4.4.3 keeping the root? Thanks.
Click to expand...
Click to collapse
Since 4.4.4 is out, just download the full firmware package from Google and flash system, boot. Only those two.
If you don't know how to do that, the Nexus 5 forums has some great stickies that are mostly relevant to this device.
charesa39 said:
You can't update the "normal way" like that with a custom recovery. When you try to do that, it tries to boot into the stock recovery to update, but since you have a custom recovery, it will fail everytime if you do it that way. What you have to do is flash the OTA zip using TWRP. You can find the OTA zip in /cache on your device. Or you can just download the update zip from these forums.
Click to expand...
Click to collapse
Right, thanks for the information. So I repeated and booted into TWRP again. Tapped 'Install', navigated to /cache, saw a couple of folders named 'back up', 'lost+found', and then a file name of a large string of letters followed by the recognisable "razor KTU70 from KOT49H", so I went ahead and flashed the latter, checking 'verify signature'. Runs through a few commands and in a few seconds comes back as failed, so I reboot into the OS.
Any ideas?
Aerowinder said:
Since 4.4.4 is out, just download the full firmware package from Google and flash system, boot. Only those two.
If you don't know how to do that, the Nexus 5 forums has some great stickies that are mostly relevant to this device.
Click to expand...
Click to collapse
I think I have an idea, but I'll check just to be sure. Thanks for the direction.
Exactly the same for me. Installing the ota sent me to my TWRP recovery. Reboot - > still in 4.4.2.
Reading this thread, I went to TWRP recovery, installed the update from cache and like you, it failed.
Any suggestions? Did your idea work?
Where do I find the 4.4.4 mentioned here and how do I flash it in TWRP? Is install the same as flash in TWRP?
Thanks.
Anderson2 said:
Exactly the same for me. Installing the ota sent me to my TWRP recovery. Reboot - > still in 4.4.2.
Reading this thread, I went to TWRP recovery, installed the update from cache and like you, it failed.
Any suggestions? Did your idea work?
Where do I find the 4.4.4 mentioned here and how do I flash it in TWRP? Is install the same as flash in TWRP?
Thanks.
Click to expand...
Click to collapse
If it fails look to see what the specific error is. It would help to know that. If you pulled it from your cache then I assume it was downloaded by itself and should be the correct OTA. I do NOT have the "Zip file signature verification." box checked or "Enable MD5 verification of backup files." but I am extremely careful to flash/install the correct files. The OTA installed fine for me two days ago using TWRP 2.7.1.0. The 4.4.4 mentioned earlier is the factory image. You will need adb and fastboot installed on your computer to flash the factory image or any image that is pulled from inside the factory image. Wug's toolkit will work also, I think, but I've never used any toolkits. Eventually there will be a stock 4.4.4 rom that you can flash/install in TWRP but I'm not aware of one right now.
You can take the normal updates with root and TWRP (I did), but a custom kernel will prevent them from installing.
I retried to install the downloaded ota file from cache, but this time I checked zip file verification and got the error message that zip verification failed.
File name was
df43279bcf6bb6a0ae403249c3e6f314d0a7eb77.signed-razor-KTU84L-from-KOT49H.df43279b.zip
So it seems the downloaded ota file may be corrupted. How do I get my Nexus 7 2013 to re-download a new one?
(The ota download for my Nexus 5 installed with no problems - but I think it didn't go through TWRP even though TWRP is installed there too).
Thanks
---------- Post added at 04:05 AM ---------- Previous post was at 03:59 AM ----------
Further
I renamed the ota file and in settings checked for system update and got a response that my system is upto date. But it is still 4.4.2.
Need to re-download the ota. How?
Changed the system date to 2 weeks earlier and succeeded in re-downloading the ota file.
So I retried installing it and it again took me to my TWRP recovery screen. I again installed the ota from cache and again the zip verification failed : 1
And the update failed again.
Still on 4.4.2
Did not change any system files as far as I know.
Need help.
Why don't you guys download the stock firmware from Google (link in my signature), and use fastboot to flash system.img, boot.img (DO NOT run the batch file)? If it's a lack of knowledge, all you need do is ask, and I or someone else would be happy to teach you how to use it (fastboot). If you're going to be modifying your Nexus device, you need to learn fastboot. You guys have got to learn the proper way to do things.
You've put forth so much effort to fix a system that is not meant for modified (rooted, customized) phones. You can't fix it, stop trying. Just do it the proper way. And do not use a toolkit. They don't teach you anything, they spoon-feed.
Aerowinder said:
Why don't you guys download the stock firmware from Google (link in my signature), and use fastboot to flash system.img, boot.img (DO NOT run the batch file)? If it's a lack of knowledge, all you need do is ask, and I or someone else would be happy to teach you how to use it (fastboot). If you're going to be modifying your Nexus device, you need to learn fastboot. You guys have got to learn the proper way to do things.
You've put forth so much effort to fix a system that is not meant for modified (rooted, customized) phones. You can't fix it, stop trying. Just do it the proper way. And do not use a toolkit. They don't teach you anything, they spoon-feed.
Click to expand...
Click to collapse
I don't use a toolkit and would be happy to flash the system.Img and boot.img but need instructions on how to do it. You said the stock firmware link is in your signature but it isn't.
I would like to skip 4.4.3 and go directly from 4.4.2 to 4.4.4. I'm talking about a nexus 7 2013 wifi.
So I need the following information to proceed .
1. The Link to download system.img and boot.img for the nexus 7 2013 wifi. Which files exactly?
2. I have fastboot and adb installed on my windows 7 laptop because I used them (once) to root but I don't remember how I used them that one time. How exactly do I use fastboot to flash 4.4.4 ?
3. I presume I will lose root. How do I regain it after the above.
Thank you.
Anderson2 said:
I don't use a toolkit and would be happy to flash the system.Img and boot.img but need instructions on how to do it. You said the stock firmware link is in your signature but it isn't.
I would like to skip 4.4.3 and go directly from 4.4.2 to 4.4.4. I'm talking about a nexus 7 2013 wifi.
So I need the following information to proceed .
1. The Link to download system.img and boot.img for the nexus 7 2013 wifi. Which files exactly?
2. I have fastboot and adb installed on my windows 7 laptop because I used them (once) to root but I don't remember how I used them that one time. How exactly do I use fastboot to flash 4.4.4 ?
3. I presume I will lose root. How do I regain it after the above.
Thank you.
Click to expand...
Click to collapse
1. The Google firmware link in my signature is the one you want. You say you have the 2013 wifi model, aka flo, aka razor. "Factory Images "razor" for Nexus 7 [2013] (Wi-Fi)" is the proper section for you. You want 4.4.4 (KTU84P), and that's at the bottom of the razor section. Click the link to download.
2. Download the most up to date ADB/Fastboot from the link in my signature (19.0.2 (API 19)). Don't extract it yet.
3. You will lose root. Download SuperSU from my signature. 2.00 is the current version. After you download that, you can put it on your device so you can flash it in recovery in a few minutes.
The firmware you downloaded is razor-ktu84p-factory-b1b2c0da.tgz. This is a compressed archive, and you will need to extract it. If you don't know how, 7-Zip should work.
So, you've extracted the files. Delete flash-all.bat, flash-all.sh, flash-base.sh (so you don't accidentally run them).
Now, all you have left is bootloader-flo-flo-04.02.img and image-razor-ktu84p.zip.
Extract image-razor-ktu84p.zip to the current directory, so you will now have bootloader-flo-flo-04.02.img, boot.img, cache.img, recovery.img, system.img, userdata.img, android-info.txt, image-razor-ktu84p.zip in your folder.
Delete userdata.img, flashing this on accident will wipe your data. Delete image-razor-ktu84p.zip, android-info.txt, cache.img, recovery.img (this is stock recovery, you want TWRP).
Now you have boot.img, bootloader-flo-flo-04.02.img, system.img.
Remember the ADB & Fastboot zip you downloaded from my signature? Extract it to the directory with bootloader-flo-flo-04.02.img, boot.img, system.img. All 4 files. This directory now contains 7 files.
Back out of the razor-ktu84p folder. Just one step back. Now, hold shift the right-click the razor-ktu84p folder. Select Open command window here.
Reboot your device to bootloader mode. Do so by shutting it down. Then while the power is off, hold volume down and press the power button. Release these buttons when you see the big green Android.
In your command window, type the command: fastboot devices
Your device with it's serial number should show up on the list. If it does not there is a problem and you need to stop here.
If the device shows up, let's update it.
fastboot flash bootloader bootloader-flo-flo-04.02.img
<wait for it to finish>
fastboot reboot-bootloader
<wait for it to reboot>
fastboot flash system system.img
<wait for it to finish>
fastboot flash boot boot.img
<wait for it to finish>
fasboot reboot-bootloader
Done with fastboot.
At this point, enter recovery (TWRP) and wipe cache and Dalvik under advanced wipe.
Remember the SuperSU you downloaded earlier and put on your device for later? Flash that now.
Reboot, all done. Most of this is just juggling files around. If you have any questions ask.
You are wonderful aerowinder. This is just what I needed to go ahead. Thank you so much.
About your signature, it doesn't show the links when viewed in my Tapatalk version, but I went to the Web view and got it from there. (just FYI if others ask about your links).
is it possible to just flash the system img in fastboot? It's still the same bootloader, not updated? Could I just flash the whole zip by sideloading in adb and TWRP? Just a lottle confused. Thanks!
droider137 said:
is it possible to just flash the system img in fastboot? It's still the same bootloader, not updated? Could I just flash the whole zip by sideloading in adb and TWRP? Just a lottle confused. Thanks!
Click to expand...
Click to collapse
If you were already on 4.4.3, all you need to do is fastboot flash system.img, that is correct.
No, you can't flash that firmware zip in recovery.
thanks
Hi Aerowinder
Thanks again for the excellent instructions. Everything went like clockwork until it didn't ?......
I got to the point where I issued the command fastboot devices which did show the tablet serial number. But my next command to flash the bootloader img gave me the error:
Cannot open 'bootloader-flo-flo-04.02.img
(I had copy pasted the command from your instructions).
The subdirectory below the command window contains that file (one of 7 files)
Sorry. What should I do?
In case you need the info, the device screen showed
Fastboot mode
Product name - flo
Variant - flo 32G
Hw version - rev_e
Bootloader version - flo-04.02
Carrier info = none
Serial number - xxxx
Signing - yes
Secure boot enabled
Lock state - unlocked
Thanks again.
Aerowinder, you are not only an expert but an excellent teacher. Your instructions above should be a sticky.
I'm all done. Everything is fine.
The problem I had above was a file path problem. Not sure why you told me to open the command window in the parent folder. When I opened it in the folder containing the seven files all your commands worked fine. (Except for your last one where you had a spelling mistake: fasboot instead of fastboot).
Thank you very much.
Hi,
I did a mistake by not S off my mobile prior to upgrade. However, I under stood from the response (http://forum.xda-developers.com/verizon-htc-one/help/sunshine-su-access-denied-t2845121/) that I'll have to wait till sunshine 3.0 come out.
Meanwhile, I've a long history of ROM/OS issues with this device. Now it got OTA update from 4.4.4 to Lollipop
Unfortunately, there seems to be missing files from my last system erasing
For example, the Exchange ActiveSync keep deciding on random basis not to sync, asking for the password (which is not changed) then it resolve the issue by itself. Another example is the camera, where I cannot enable video recording from inside the camera, I seem to be able to make from within messenger apps!!! :S
So, my question would be how can I reapply the Lollipop ROM again?
I've downloaded both, the exe file from HTC support site, and the zip file from RUU famos article on this forum.
The exe version says it will reboot to recovery but it never finish (stops on black screen with HTC gray logo)
The zip file installation through recovery failed, and through renaming it to 0P6BIMG.zip and put it on the SD root failed as well.
Any ideas?
Need to add, I've downloaded the file "RUU_M8_UL_L50_SENSE60_MR_BrightstarUS_WWE_4.16.1540.8_Radio_1.24.21331147A1.09G_20.68.4196.01_F_release_411207_signed_2.exe"
Now, when running this tool, it says the update will be:
From Image version: 4.16.401.10
To Image version: 4.16.1540.8
I'm not sure, but is this file for another model?
Read carefully here
http://forum.xda-developers.com/showthread.php?t=2701376
Read it well and it has all the answers to get back to stock backup and update again.
If you are s-on you can't flash any other ruu than the one that matches your phone.
Getting the 2.10.401.1 step by step, crystal clean instructions.
This guide is mostly for the people who are stuck on lower versions where "About" says that there are no updates and that their device is up to date. Especially users who previously did 1.32.401.17 RUU. This version is know to have some major flaws and it tends not to read any updates, accept auto and manual OTAs nor zipped RUUs.
- Alright so I saw good number of people being stuck on European 1.32.401.17, 1.32.401.15 and 1.32.401.8 and unable to grab auto OTA and unable to manual OTA install due to various errors being thrown in twrp. There are also users who are having issues with SD transfers, transfers from PC to to phone especially when they transfer zipped RUU (0PJAIMG). Do not worry, I am going to help you with this. Just follow my simple steps. Note that you can forget about custom recoveries, microsds, system dumps, zipped ruus that "wont copy" to your device and others. You won't need any of these in my procedure. Simply ignore them. Now focus on my steps.
Step 1; Download the 1.32.401.17 exe RUU from here; DO NOT RUN THIS YET.
Step 2; Download the 1.40.401.8 0PJAIMG (ZIPPED RUU). Do not open/modify this yet.
Step 3; Backup your data on the phone such as contacts, SMS and so on. I personally use Wondershare mobilego for those things.
Step 4; Navigate to temp folder by typing %temp% in the search bar or C:\Users\Username\AppData\Local\Temp\ >>
Step 5; Under that folder you may or may not delete the files you don't need for easier navigation. Now this part is very important. Focus on that folder.
Step 6; Go back to 1.32.401.17 exe you downloaded in the step 1. Right click on it and Run it as admin. Once ran, it might take several minutes to open actual installer. Let it load all they where you see next/cancel. Stay there and do not cancel it or hit next.
Step 7; Go in your temp folder under step 4. You will see two newly created folders. You only need this one. Under that folder you should see another one with few random files. Go into other subfolder and navigate to the file named rom.zip. Delete this folder.
Step 8; Now go back to the file you downloded in step 2. Name that file to rom.zip and place it where you previously deleted the zip file from temp subfolder.
Step 9; Go back to the RUU installer interface and press next and do the procedure like you did with version x.17. You should see this. Now let the RUU installer updates your phone.
Step 10; Go under Settings > About > Updates. Now if you did all right you should see the magic: http://i.imgur.com/aqR4YwD.png >> Grab this new 100% fresh and stock OTA update and enjoy.
- I tested this few times on several devices and it works for every one of them. I am not aware of the other carrier users are having issues but same procedure can be done. Do not install custom recovery or root your device before you updated your device to 2.10. If in any case updater wont pick the 2.10 update you can flash your recovery and firmware from 1.40.401.8 version (prior to the 2.10 update). Do not panic if update is taking a while, it will reboot your device few times and thats it. To be on more safe side you can always flash the firmware once device is properly updated to 2.10.
*Flashing the firmware to 2.10*
Download from here and put it where your ADB interface is;
Put your device to download mode and open up the cmd where adb interface and latest firmware is.
do the following commands:
a.) fastboot oem rebootRUU
b.) fastboot flash zip firmware.zip
c.) fastboot reboot
- Make sure the phone is not rooted or tampered with. If something is not clear feel free to ask. I hope this helped to you.
Nikola
Nikolay82 said:
*Flashing the firmware to 2.10*
Download from here and put it where your ADB interface is;
Put your device to download mode and open up the cmd where adb interface and latest firmware is.
do the following commands:
a.) fastboot oem rebootRUU
b.) fastboot flash zip firmware.zip
c.) fastboot reboot
- Make sure the phone is not rooted or tampered with. If something is not clear feel free to ask. I hope this helped to you.
Nikola
Click to expand...
Click to collapse
S-ON Users should not try to do this if they weren't able to get and install the 2.XX.XXX.X uptdate before they get to this step. The firmware pack does not update the rom and it can only be flashed on S-ON devices if the bootloader is locked or relocked. HTC introduced a new "security feature" with the 2.XX.XXX.X firmware. This "feature" blocks the Bootloader Unlock if the option "OEM unlocking" in the Developer Options isn't activated. Without an up to date rom you won't be able to activate this option because it does not exist in earlier versions. Since there are no international 2.XX.XXX.X RUUs S-ON Users who follow this part of the guide and did not install the OTA beforehand would then be stuck with the 2.XX.XXX.X firmware and a 1.XX.XXX.X rom.
Except for that missing warning it's a very nice written guide.
I've tested this on S-ON device. I've successfully flashed 2.x for the sake of testing, both s-off and s-on. That part is probably not something many people will need, but its there just to be on safe side. The RUU itself will throw an error if there is a CID conflict anyway. Personally, I am not a fan of tampering with CID unless it is a must. User should be able to find proper RUU/OTA to match their CID.
I am working with the phones and I often have people who likes to tamper with their device. Good number of them will even write different CID, or even "universal" one just so they can go through RUU process and update. However, later they stuck on "no mobile data" unable to fix things. 99.9% of them failed to update their current model to latest so they resort to changing CID and putting in different country ROM just because it is newer. As for HTC introducing new security feature I wont go much into detail about it because it falls under hacking and reverse engineering in order to benefit from said action. Let's just say they never got around some crucial elements which pretty much made their security feature vain. Apple claimed similar thing. One day I sat down and put in the windows OS just because "tiles" were trend back then. I am yet to see a safe and totally secure update. Apple was the closest with their icloud and findmyphone but I decided for droid mostly because i wanted more freedom for what I pay. Cheers.
Nikolay82 said:
I've tested this on S-ON device. I've successfully flashed 2.x for the sake of testing, both s-off and s-on.
Click to expand...
Click to collapse
I never said that you won't be able to flash the firmware with S-ON. And please don't get me wrong. Your guide is very good.
The problem is that there is a special kind of xda readers which tends to skip some of the important steps that are described in instructions. If those people flash the firmware without installing the OTA beforehand they will be stuck with an unlockable, (re-)locked bootloader and a 1.XX.XXX.X rom on a 2.XX.XXX.X firmware. There are already plenty of threads which describe similair scenarios here on xda. That's the reason for the warning in my last post.
I know this is a bit late, but i needed it this afternoon and didn't have it, I am not good at guides but ill do my best, so here goes nothing.
use sunshine obviously! this will get you s-off and unlocked bootloader for any htc 10 version! (Google it if you dont know what it is!)
now that you have s-off how do you install a recovery and gain root...
boot to download mode
turn off your phone then hold volume down and power for a few seconds
once in download mode get your CID, MID, and system version and write them down somewhere, then reboot the phone to system
create a text file named "android-info.txt"
type the following into the txt file replacing the us unlocked oreo info with your own
Code:
modelid: [COLOR="Red"]2PS650000[/COLOR]
cidnum: [COLOR="red"]BS_US001[/COLOR]
mainver: [COLOR="red"]3.16.617.2[/COLOR]
hbootpreupdate: 1
nohardreset: 1
save the file.
download the latest TWRP img and rename it to "recovery.img"
move recovery.img and android-info.txt to the same folder select them both and add them to a zip folder named "2PS6IMG.zip"
copy the zip you just created directly to the root of your sd card
boot back into download mode using the steps you followed earlier , you should be prompted to flash the zip you just made, flash it, if everything went well you should now have twrp recovery installed.
boot back up, download superSU, or other root apps or ROMS of your choice
boot into recovery, flash away... proffit!
THC Butterz said:
I know this is a bit late, but i needed it this afternoon and didn't have it, I am not good at guides but ill do my best, so here goes nothing.
use sunshine obviously! this will get you s-off and unlocked bootloader for any htc 10 version! (Google it if you dont know what it is!)
now that you have s-off how do you install a recovery and gain root...
boot to download mode
turn off your phone then hold volume down and power for a few seconds
once in download mode get your CID, MID, and system version and write them down somewhere, then reboot the phone to system
create a text file named "android-info.txt"
type the following into the txt file replacing the us unlocked oreo info with your own
save the file.
download the latest TWRP img and rename it to "recovery.img"
move recovery.img and android-info.txt to the same folder select them both and add them to a zip folder named "2PS6IMG.zip"
copy the zip you just created directly to the root of your sd card
boot back into download mode using the steps you followed earlier , you should be prompted to flash the zip you just made, flash it, if everything went well you should now have twrp recovery installed.
boot back up, download superSU, or other root apps or ROMS of your choice
boot into recovery, flash away... proffit!
Click to expand...
Click to collapse
Hey I had a question. Does it work if you have no root on nougat/oreo firmware? Because I heard you need root on nougat firmware for sunshine to work.
jhadsfi said:
Hey I had a question. Does it work if you have no root on nougat/oreo firmware? Because I heard you need root on nougat firmware for sunshine to work.
Click to expand...
Click to collapse
Anyone? Cant use sunchine cause is asking for root.Im on Nougat without root and im trying to unlock the bootloader but htcdev.com cant let me register and this mod dont work for me cause the root asking..
alek889 said:
Anyone? Cant use sunchine cause is asking for root.Im on Nougat without root and im trying to unlock the bootloader but htcdev.com cant let me register and this mod dont work for me cause the root asking..
Click to expand...
Click to collapse
Sorry can't help much. I had bootloader unlocked already so I flashed MaximusHD with root and went S off through that. There are a couple of threads regarding downgrading firmware. Try going to MM firmware and go S Off from there. I think the method works on S on devices.
Im on htc 10 ( an au converted) oreo with same CID, MID, and mainver
Downloaded a latest twrp img and zip them together in external, flash and stuck in "start ui_updating
chaoticnoize said:
Im on htc 10 ( an au converted) oreo with same CID, MID, and mainver
Downloaded a latest twrp img and zip them together in external, flash and stuck in "start ui_updating
Click to expand...
Click to collapse
https://forums.androidcentral.com/a...stuck-bootloop-recovery-seems-impossible.html
andybones said:
https://forums.androidcentral.com/a...stuck-bootloop-recovery-seems-impossible.html
Click to expand...
Click to collapse
Amazingly, I was able to escape that situation with volume - and power button for about 10 second, and brought me back to download mode and reboot system from there, just sad that the twrp zip is not working coz'I have no source to type c usb cable data to do adb with pc
Thx alot dude
Btw the zip is not working on htc 10 oreo s-off stock recovery
It worked like a charm! Thank you. My USB not working for ADB and this save me from trowing my phone to the trash