Related
If you regularly install/test custom firmwares, ROMs and mods on your HTC One, it can be quite annoying and time-consuming if you want to go back to the latest stock software with official manufacturer OTA support (for example, to check if the latest official OTA update has been released for your region). Flashing the RUU is arguably the easiest and fastest way, but many of us have only older RUU's available which means having to download some quite big OTA updates every time. To avoid this inconvenience, i've done some research about the various methods to return to the latest stock version as hassle-free and as quickly as possible and i've come up with the following solution. This idea is not ground-breaking and might not be new to some (or most) of you, but i believe this guide should be useful for "noobs" or those who never thought of or didn't know how to handle OTAs and also to find the easiest and fastest way to swap any custom software (ROM/firmware) on your HTC One with the last 100% stock installation right before you flashed a custom recovery.
The procedure described below tries to eliminate the need to look for and flash stock firmware and stock ROMs uploaded by others, which may not necessarily exactly match with the original stock software of your phone especially since there exists dozens of HTC One variants. Using downloaded stock firmware/ROM from others might cause incompatibilities, degradation in performance, lost of signal, poor reception, etc. Ideally, you want to be able to flash whatever ROM/firmware and at any time, if you wish, you should be able to switch back to your own stock ROM and firmware. This is usually done by flashing your RUU (Rom Update Utility) according to your phone's MID and CID. However, most of you would need to go through an annoying and time-consuming update process to download several OTAs before finally reaching the current latest stock version. But here's a solution!
Minimum requirements:
1. Your HTC One's bootloader must be unlocked.
If your device is already S-OFF and if you relocked/locked your bootloader, then you can unlock the bootloader without having to use the official htcdev website. Just follow this guide to set the Bootloader as UNLOCKED: http://forum.xda-developers.com/showthread.php?t=2497712
2. You need to find your device's RUU (decrypted is even better as it allows going through the process faster) or your 100% stock software backup (firmware and ROM). If you made a nandroid backup after unlocking the Bootloader, it won't work since some data was wiped from your phone's memory during the unlocking process from the official htcdev website.
It's advised to use the RUU to restore which is specifically designed for a set of devices according to their MID and CID, rather than trying your luck at finding a compatible stock firmware and ROM for your HTC One variant. Here's a thread with a collection of RUUs and stock firmware/ROMs: http://forum.xda-developers.com/showthread.php?t=2428276
3. Your device should be S-OFF.
This is not an absolute requirement but S-OFF makes the whole procedure much easier. For the purpose of this guide, it will be assumed that your device is S-OFF.
Advantages of this method:
1. You will save time by being able to restore back to the latest 100% stock version very quickly (some OTA updates are around 400 MB which can take some time to download). You will only have to download the OTA's one time and then back up these OTA's to use later for updating/restoring your stock software.
2. You won't need an internet connection to update to your last stock version backup. The update process to previously downloaded (and backed up) OTA's will not require an internet connection. However, you will have to download any newer OTA's if available.
3. You will not have to rely on other sources to find your latest stock firmware and stock ROM. Therefore, you can be certain that you're getting a perfectly matching firmware and ROM for your specific HTC One model (the restored firmware and ROM will be exactly as if you never tampered with your device, with official manufacturer OTA support).
4. You will not have to downgrade if using an older RUU or older stock firmware/ROM, and then have to update it again via OTA. Your HTC One will be restored to 100% stock with the same software version just before you flashed a custom firmware/ROM.
5. If you absolutely need to run the RUU to go back to 100% stock, then you will not have to run the RUU process more than once (which will wipe all your nandroid backups as well as all your data, assuming you have a decrypted RUU, otherwise you will have to run the RUU twice only).
Procedure:
To summarize, if you want to go back to 100% stock using the method in this guide, all you will have to do is restore your nandroid backup and flash the firmware from the latest OTA. You will then get stock software with full OTA support within a few minutes from a custom installation. The method itself consists of handling official OTAs and extracting the most recent firmware in order to restore. But you will need a starting point where your device is 100% stock and able to receive and install official OTAs from the manufacturer. Let's assume that your HTC One is 100% stock. Whatever means you used to reach 100% stock, you will need it again. So, keep that RUU (preferably try to find your decrypted RUU zip) or stock files handy.
Check if you have any OTA update available:
No update available
If no OTA updates are available for your device, you can flash your custom recovery and then do a nandroid backup (very important). Then, you can root, flash a custom ROM and if you're S-OFF, you can even flash custom firmware.
Going back to stock: if you want to check for OTA availability at any time or you just want to go back to 100% stock, the easiest and safest way is to run your RUU. But if you found your decrypted RUU zip, you can go back to stock even faster; first restore your nandroid backup and then extract firmware.zip from the decrypted RUU zip and flash it. That's it. You're now back to 100% stock. You can check if there are any available OTAs and then go back to using custom ROMs again if you like.
Update available
Here is the more interesting part of this guide:
1. You will need the original firmware.zip file for your current stock software version. If you ran the RUU to go back to stock, extract rom.zip (follow this guide: http://forum.xda-developers.com/showthread.php?t=2497614) and then extract firmware.zip from the decrypted RUU rom.zip file. If the RUU rom.zip is not decrypted, it will give you an extraction error about all the files contained within being corrupt. In that case, you should try to find a decrypted version of the same RUU or decrypt it yourself (requires Linux, as decrypting an RUU is currently not possible on other OS). Use Winrar/Winzip to open the firmware.zip and extract recovery.img and place it in your adb folder.
2. Check for software update in the Settings menu. If you get OTA update notification, accept it. Note the file size of the OTA download, as it'll be useful to easily identify it later when searching in your device's internal memory. Let it download but do not install it. Select the option "Install Later" when prompted.
3. In the Settings menu, disable fastboot and enable USB Debugging.
4. Flash custom recovery. Root your device. Boot up to Android.
5. Install ES File Explorer from the Play Store (it's free) and give it root permission from its settings. Use ES File Explorer to search for the OTA on your phone. I found Root Explorer to be much faster at searching files although it's a paid app. You will usually find the downloaded OTA in your /sdcard/Download/ folder or /data/data/com.android.providers.downloads/cache/ folder. The OTA will have the keyword "OTA" in its filename and it will be a single zip file. You can also confirm that it's the OTA file by its file size from the earlier OTA pop-up notification. If you still can't find your OTA zip, you can search for "OTA" or "zip" through ES File Explorer or Root Explorer (much faster). Then go through the search results. Here's the original filename of one of my OTA's: OTA_M7_U_JB_50_S_HTC_Europe_2.24.401.2-1.29.401.2_R_P_release_325145_signedn3pctn48i51c9iue.zip. When you've found the OTA, copy it using ES File Explorer to the /sdcard/ location on your phone. Then plug in a USB cable to your HTC One and copy the OTA to a safe place on your PC hard drive.
6. Now, connect your phone via USB, reboot and go to your bootloader. We'll be flashing recovery.img from step 1. Use command "fastboot erase cache" then "fastboot flash recovery recovery.img" and finally "fastboot reboot". Now, you have 100% stock again with OTA support. The SuperUser/SuperSU app will still be visible on your phone but it won't work since the su binary will have been wiped during the stock recovery restore process.
7. Check for OTA software update again from the Settings menu. Install the downloaded file through the update notification menu. But if the update re-downloads, cancel it. Instead, you can manually flash it by copying the OTA zip to the phone's internal memory (don't have to rename the OTA zip but for simplicity, rename it to update.zip) and go to your Bootloader. Select Recovery using the Power button and then press the Power and Volume Up buttons to load the stock recovery menu. Then, select 'apply from phone storage' and navigate the menu as you would in a custom recovery to find update.zip and select it to install. It will follow the official update procedures and will reboot a few times before going back to your homescreen. Check attachments below for the stock recovery menu and options.
8. When your phone reboots, check for OTA again. If update is found, download it but choose "Install Later".
9. Then, just follow the same steps above; 4 through 8. Redo the same steps to copy the OTA to your PC and extract firmware.zip. The principle is that you should backup all the successive OTAs until there are no more updates available. The very last OTA's firmware.zip is the most important file. Keep it separately from the other firmwares. You should also save the previous complete OTA zips to be able to update quickly if you ever need to run RUU again.
10. After you've made a backup for the last OTA zip file, check for software update and install the already download OTA zip through the normal update notification menu. If the OTA update re-downloads, cancel it and do a manual flash for the OTA update that you saved previously, as explained in step 7. Note that an official OTA will update both the firmware and ROM.
11. Then, flash a custom recovery and make a complete nandroid backup to secure your last updated stock ROM. Copy the nandroid backup to your PC. Keep the nandroid backup and the last firmware.zip file (extracted from the last downloaded OTA zip file) safely as these two files are the only ones you will need to restore quickly back to 100% stock with OTA support, unless you were to run the RUU, in which case, you'll have to install all the OTA zip files successively.
12. Now, you can flash whatever you like on your HTC One. If you're S-OFF, you can flash custom firmware as well.
Going back to stock: if you want to check quickly if any OTA's are available or just want to easily go back to 100% stock software, all you have to do is first, restore the last nandroid backup of the stock ROM and then flash the firmware.zip from the last OTA update that you downloaded. That's it. Now, you can check and update easily to any new OTA that might have been released while your device was on custom ROM/firmware. Obviously, you can also backup any available OTA's, by following the same steps above.
I will probably expand this guide further if there is any interest in it.
If this guide was helpful to you, just press the "THANKS" button!
Hi, I found the guide useful, specially now with the upcoming 4.4 OTA. I'm confused thou, I heard you can't apply an OTA having a custom recovery, is this true? If so, shouldn't you have to flash stock recovery after loading a nandroid backup from recovery to be able to receive OTA's?
Arjen_Arg said:
Hi, I found the guide useful, specially now with the upcoming 4.4 OTA. I'm confused thou, I heard you can't apply an OTA having a custom recovery, is this true? If so, shouldn't you have to flash stock recovery after loading a nandroid backup from recovery to be able to receive OTA's?
Click to expand...
Click to collapse
You need to have 100% stock ROM and stock recovery in order to successfully apply an official OTA update. In order words, if you have custom recovery, you won't be able to update. You need to flash in the following order: stock nandroid backup, stock recovery, then download/install any new OTA.
Tried to update my wife's Nexus 10 tonight. It's unlocked and rooted, formerly on the stock version of Jelly Bean. I thought this would be an easy update since it was stock jellybean to kitkat with the official OTA file but I guess I was wrong. Got the OTA update notification so I allowed it to reboot and install. CWM Touch Recovery picked it up and I told it to install the unsigned zip. Got near the end and it had an error. Now it's stuck in boot (appears to be Kit Kat boot). Just sits on the 4 colored circles going in/out in the middle of the screen.
I need to fix this without wiping data. It's her only computer that she uses daily so she's got a million things on there she uses all the time. If I have to wipe data, she'll be pissed (and I'll lose my hard earned game saves).
Attached is a picture of the error. I've got WUG's toolkit if it's necessary to use to fix this. Any ideas what's going on and how to fix it? Thanks.
Stinger2300 said:
Tried to update my wife's Nexus 10 tonight. It's unlocked and rooted, formerly on the stock version of Jelly Bean. I thought this would be an easy update since it was stock jellybean to kitkat with the official OTA file but I guess I was wrong. Got the OTA update notification so I allowed it to reboot and install. CWM Touch Recovery picked it up and I told it to install the unsigned zip. Got near the end and it had an error. Now it's stuck in boot (appears to be Kit Kat boot). Just sits on the 4 colored circles going in/out in the middle of the screen.
I need to fix this without wiping data. It's her only computer that she uses daily so she's got a million things on there she uses all the time. If I have to wipe data, she'll be pissed (and I'll lose my hard earned game saves).
Attached is a picture of the error. I've got WUG's toolkit if it's necessary to use to fix this. Any ideas what's going on and how to fix it? Thanks.
Click to expand...
Click to collapse
I have a rooted/unlocked Nexus 10, I used wugfresh's kit also. I got the OTA update last night. it installed. CWM never came up or did anything. During one of the boots after the green droid bot was saying "installing" the boot finished, but my green bot is now on his side. stomach open and it says "Error" in red bold letter.
I had to go to work, so I couldnt trouble shoot, but power off/on and soft reset (power+volume up select reset) didnt help. always comes to that "error".
I have data that is also not currently backed up with TBpro. hindsight I should have made sure I turned the scheduler on.
So I'm stuck also. not sure how to proceed. Got one recommendation to flash stock back on. But I think that will for sure wipe all my data. And beyond that, I dont know how, unless WUGs kit will do that.
Your best bet it is to sideload. Grab the OTA and the FULL 4.4
Pull the recovery.img from the full 4.4 rar (its in the zip), fastboot flash it, reboot into bootloader, go to recovery and sideload the OTA and that should restore it just fine
EDIT: http://forum.xda-developers.com/showpost.php?p=47656450&postcount=8
my detailed instructions there for sideloading
planet_x69 said:
Your best bet it is to sideload. Grab the OTA and the FULL 4.4
Pull the recovery.img from the full 4.4 rar (its in the zip), fastboot flash it, reboot into bootloader, go to recovery and sideload the OTA and that should restore it just fine
EDIT: http://forum.xda-developers.com/showpost.php?p=47656450&postcount=8
my detailed instructions there for sideloading
Click to expand...
Click to collapse
I was about to say. whaaaaat? then saw the link with some details. Never done that stuff before, just used other tools kits, like wugs. But doesnt sound to bad. Will try when I get home. I presume when you say into a adb directory, its something on the desktop pc you are connected to. outside of perhaps some drivers, do I need other applications on the PC to facilitate the adb stuff you mention?
jetguat said:
I was about to say. whaaaaat? then saw the link with some details. Never done that stuff before, just used other tools kits, like wugs. But doesnt sound to bad. Will try when I get home. I presume when you say into a adb directory, its something on the desktop pc you are connected to. outside of perhaps some drivers, do I need other applications on the PC to facilitate the adb stuff you mention?
Click to expand...
Click to collapse
Well if you are unfamiliar with the process you will need to get the android SDK installed or find one of the pre-packaged current adb loads. It's very simple, get this package here: http://downloadandroidrom.com/file/Nexus10/Nexus10RootNew.zip# (yes its a crappy ad link but hey the guy packaged it all up so...).
If you are on a PC extract these to a folder of your choice.
Open file manager
Navigage to the folder you extracted the files to
on the left pan select the folder, press SHIFT and Right Click mouse, then select "Open command window here"
You can now follow my instructions from the other page - Do the following below FIRST
If you are prompted to accept security allowance on your device do so. you will likely only see this once you are back into the Android OS not in recovery.
This folder has all the basics you need to fastboot and run adb.
Connect your device to your pc and run >fastboot reboot-bootloader.
If your device restarts and goes into the bootloader you can relax and follow my instructions.
Hope this helps.
One other thing, that su zip is dated, you will need to flash the 1.51 version and you should be good to complete root process.
Wow, this seems about 3 miles over my head but I guess I'll dive in and try it. Thanks for the info. I'm sure I'll be back with problems/questions.
planet_x69 said:
Well if you are unfamiliar with the process you will need to get the android SDK installed or find one of the pre-packaged current adb loads. It's very simple, get this package here: http://downloadandroidrom.com/file/Nexus10/Nexus10RootNew.zip# (yes its a crappy ad link but hey the guy packaged it all up so...).
If you are on a PC extract these to a folder of your choice.
Open file manager
Navigage to the folder you extracted the files to
on the left pan select the folder, press SHIFT and Right Click mouse, then select "Open command window here"
You can now follow my instructions from the other page - Do the following below FIRST
If you are prompted to accept security allowance on your device do so. you will likely only see this once you are back into the Android OS not in recovery.
This folder has all the basics you need to fastboot and run adb.
Connect your device to your pc and run >fastboot reboot-bootloader.
If your device restarts and goes into the bootloader you can relax and follow my instructions.
Hope this helps.
One other thing, that su zip is dated, you will need to flash the 1.51 version and you should be good to complete root process.
Click to expand...
Click to collapse
OK, I downloaded the packaged linked above and extracted it to the desktop. Then I used file manager to "open command window here". Where do I get su zip 1.51? I tried to google a link but they all seemed newer (1.75 for example). Does it matter if it's 1.51 exactly or can it be any version 1.51 or newer? One last question regarding su zip, does that need to be updated after this whole process is complete and I'm up and running again, or does it need to be done before I move on to the instructions you linked to above? Thanks.
Stinger2300 said:
OK, I downloaded the packaged linked above and extracted it to the desktop. Then I used file manager to "open command window here". Where do I get su zip 1.51? I tried to google a link but they all seemed newer (1.75 for example). Does it matter if it's 1.51 exactly or can it be any version 1.51 or newer? One last question regarding su zip, does that need to be updated after this whole process is complete and I'm up and running again, or does it need to be done before I move on to the instructions you linked to above? Thanks.
Click to expand...
Click to collapse
You don't need to root at all but the updated supersu 1.75 will be just fine as its universal. You can get the official from here: http://download.chainfire.eu/368/SuperSU/UPDATE-SuperSU-v1.75.zip
You will install that ONLY after you have installed the OTA's and your custom recovery and only if you want root.
good luck!
planet_x69 said:
Your best bet it is to sideload. Grab the OTA and the FULL 4.4
Pull the recovery.img from the full 4.4 rar (its in the zip), fastboot flash it, reboot into bootloader, go to recovery and sideload the OTA and that should restore it just fine
EDIT: http://forum.xda-developers.com/showpost.php?p=47656450&postcount=8
my detailed instructions there for sideloading
Click to expand...
Click to collapse
In this link, you said to do the following:
Pull the full stock 4.4 image from here : https://developers.google.com/androi...mages#mantaray
open it and pull out from the zip in the rar the recovery.img, move a copy to your adb folder along with a copy of your custom recovery ( for discussion sake I'll use twrp.recovery.img)
Put copy of the patch in the adb folder and rename it to a short name like krt16s.zip
I got the full stock 4.4 image downloaded, extracted it, extracted the zip file inside (image-mantaray-krt16s.zip) and that provided me with "recovery.img" you mentioned above.
Now I have 2 problems, where is this "adb folder" you say to put the recovery.img in, and where is the custom recovery? I assume it's on the N10 after I connect it to my laptop. Is there a preferred custom recovery I should use? I saw mention of TWRP not working with Kit Kat elsewhere. Not sure if that is dated info or not.
Lastly, just to confirm this is true, none of this whole process will wipe my data correct?
planet_x69 said:
You don't need to root at all but the updated supersu 1.75 will be just fine as its universal. You can get the official from here: http://download.chainfire.eu/368/SuperSU/UPDATE-SuperSU-v1.75.zip
You will install that ONLY after you have installed the OTA's and your custom recovery and only if you want root.
good luck!
Click to expand...
Click to collapse
OK, downloaded that and will hold it for later. Hopefully after the questions I just asked are answered, I'll have enough info to proceed. Thanks for the help so far.
Stinger2300 said:
In this link, you said to do the following:
Pull the full stock 4.4 image from here : https://developers.google.com/androi...mages#mantaray
open it and pull out from the zip in the rar the recovery.img, move a copy to your adb folder along with a copy of your custom recovery ( for discussion sake I'll use twrp.recovery.img)
Put copy of the patch in the adb folder and rename it to a short name like krt16s.zip
I got the full stock 4.4 image downloaded, extracted it, extracted the zip file inside (image-mantaray-krt16s.zip) and that provided me with "recovery.img" you mentioned above.
Now I have 2 problems, where is this "adb folder" you say to put the recovery.img in, and where is the custom recovery? I assume it's on the N10 after I connect it to my laptop. Is there a preferred custom recovery I should use? I saw mention of TWRP not working with Kit Kat elsewhere. Not sure if that is dated info or not.
Lastly, just to confirm this is true, none of this whole process will wipe my data correct?
Click to expand...
Click to collapse
Correct - if you SIDELOAD the OTA it will UPGRADE and retain all data and application settings etc...
If you run the 4.4 update from the factory image it will WIPE ALL. So do not do that ....just pull the recover.img from it and get rid of the rest.
If you downloaded this: http://downloadandroidrom.com/file/N...10RootNew.zip#
and extracted it to a new folder - do this first!!!
then copy the recovery.img you just extracted from the factory 4.4 rar to the same folder as the adb and fastboot commands
copy the OTA file to same folder and rename it ota.zip to make your life easier
>fastboot reboot-bootloader to validate your computer can see the device and that the next steps will go as planned
If you are now back bootloader then:
>fastboot flash recovery recover.img
wait till its done..will take about 15 seconds tops
>fastboot reboot-bootloader again and go to recovery using the volume buttons
select and enter recovery mode
wait for dead droid to appear
press both Volume UP and Power at same time and you should get the load menu
select "apply updated from adb" and press power after selecting
orange colored type will now appear at the bottom of the screen
on your PC
>adb sideload ota.zip
wait till you see its completed successfully
then reboot
(you can also apply the smaller ota (1.7MB) this same way)
If all went well you have now booted up successfully and see that your ass has been saved from eternal hell from your wife's wrath...
reboot and fastboot flash your favorite custom recovery reboot again to recovery and apply the su update for root access
I hope this helps
You can also read this: http://www.androidpolice.com/2013/1...-download-and-install-android-4-4-now-krt16o/
You said: "just pull the recover.img from it and get rid of the rest."
So is your instruction from the original link to: "Put copy of the patch in the adb folder and rename it to a short name like krt16s.zip" replaced by the OTA file I renamed to ota.zip in order to retain all data? For reference, krt16s.zip is 390mb, ota.zip is 225mb.
Stinger2300 said:
You said: "just pull the recover.img from it and get rid of the rest."
So is your instruction from the original link to: "Put copy of the patch in the adb folder and rename it to a short name like krt16s.zip" replaced by the OTA file I renamed to ota.zip in order to retain all data? For reference, krt16s.zip is 390mb, ota.zip is 225mb.
Click to expand...
Click to collapse
not sure i follow you but from the 4.4 factory image you will need the recovery.img file thats it. You will also need the OTA upgrade that takes you from 4.3 to 4.4. You need the OTA so that you wont lose your wifes data and will upgrade only and not image the device.
I have to leave and wont be back on till later this weekend.
Going well so far...had an issue but figured it out.
Got to sideloading ota.zip, then after it got to 100% it started verifying the update package. Got an error:
'/system/app/BasicDreams.apk" has unexpected contents
E:Error in /tmp/update.zip
(status 7)
Installation aborted.
Now what?
I found this in the Nexus 7 section but not sure if it applies here or if there is a better way, if it's guaranteed to not wipe data, etc.: http://forum.xda-developers.com/showpost.php?p=47474021&postcount=26
Did you try this solution? I'm stuck on the "Error in /tmp/update.zip" as well. Having the same issues, and I hope to update without loosing data.
No, I haven't tried it as I can't risk losing data by randomly trying stuff I don't understand. I need someone who knows what they are doing to confirm that the steps in this link http://forum.xda-developers.com/showpost.php?p=47474021&postcount=26 won't wipe data or do anything that will require wiping data to finish this process.
have well
Stinger2300 said:
No, I haven't tried it as I can't risk losing data by randomly trying stuff I don't understand. I need someone who knows what they are doing to confirm that the steps in this link http://forum.xda-developers.com/showpost.php?p=47474021&postcount=26 won't wipe data or do anything that will require wiping data to finish this process.
Click to expand...
Click to collapse
I just tried it. And it worked. Didn't loose any data.
Flashing the img files, and then proceeding to sideload the OTA zip. Booting didn't take too long, Android then started upgrading ("Optimizing app..."), and booted successfully. It took a while to open de app drawer though... But everything was still there.
Regaining root access is something I'll try later. I'm just happy to have my N7 booting again.
Just a small disclaimer. I don't really know what I'm doing (I kinda like messing around with my device, it's only way to learn something), so I cannot guarantee it will work for you.
Glad it worked for you, it didn't work for me. I got another error after doing the following commands:
Then, run the following commands:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system
fastboot flash system system.img
then I rebooted back to bootloader, then "apply updated from adb" and then from the command line: >adb sideload ota.zip
It again loaded 100% and then started verifying the package. Then I got this error:
Package expects build fingerprint of google/mantaray/manta:4.3/JWR66Y/776638:user/release-keys or google/mantaray/manta:4.4/KRT160/907817:user/release-keys; this device has google/mantaray/manta:4.4/KRT16S/920375:user/release-keys.
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
What a F***ing nightmare...
Why do I apparently have the wrong version?
Hmm, might be the wrong OTA zip idd...
I downloaded mine from here: http://www.droid-life.com/2013/11/2...ial-update-for-nexus-7-2012-and-nexus-7-2013/
Hi guys.
First of all, Please understand although I'm not good at English.
I have rooted wifi version m3. (BTV-W09C233B030)
I use TWRP and installed SuperSU.
I used erecovery to erase and install TWRP.
and now. I want rollback rooting and upgrade to nougat.
To do that, I heard that the stock firmware was needed, and I downloaded the full version of the file(full version BTV-W09C233B029) using the firmware finder.
Can you tell me in detail from here?
Thanks : )
First of all, I would like to let you know that :
- I've successfully installed Nougat BTV-DL09-C100-B302 but... I was unable to root it with "twrp_BTV-DL09_5_greatslon.img" + "TWEP-SuperSU-v2.79.zip".
- I've then done a rollback thanks to the "C900B300 - ROLLBACK from 7.0 EMUI 5.0 to 6.0 EMUI 4.1 6.0" package from the Huawei website.
- Then, successfully re-installed BTV-DL09-C100-B009
(1) By putting update.app inside "dload" folder (to be created or to be emptied) on the external sdcard
(2) Switched off the mediapad.
(3) Switch on pressing Volume up+down+power button and install will start.
- Successfully upgraded to BTV-DL09-C100-B010 -> BTV-DL09-C100-B301 with "Firmware finder 4.2" downloaded the from Google Store.
Unfortunately, again, I was unable to root it and I've identified this error while flashing "TWEP-SuperSU-v2.79.zip" with "twrp_BTV-DL09_5_greatslon" : "Boot image patching" process fails to patch "sepolicy" and give the error "--- failure, aborting" ; basically, the SU binary is not installed in the System. It's a kernel issue and I guess TWRP has to be patched for these new ROMS or the concerned file must be patched differently, with another tool (BTV-XX09-XXX-B301/B302). Or I'm doing something wrong if someone else has managed to root its mediapad running these updates.
If you don't need your mediapad to be rooted or if you know how to root it , installing Nougat is quite simple :
1) First replace TWRP with the stock recovery image. To do so, extract recovery.img from BTV-W09C233B029 with "HuaweiUpdateExtractor" for Windows.
Considering that you have the ADB drivers correctly installed, reboot in fastboot mode with the command : "adb reboot-bootloader" (or adb reboot bootloader). Then type : fastboot flash recovery recovery.img and then "fastboot reboot". I'm doing all that under parallel destop (Windows 10) on a macbook pro.
2) Then, install you stock rom BTV-W09C233B029 :
(1) Put the file "update.app" inside a dload" folder (to be created or to be emptied) on the external sdcard.
(2) Switched off the mediapad.
(3) Switch it on while pressing volume up+down+power buttons. Install will start.
3) Download Firmware finder 4.2 from the google store and install the required Nougat OTA file for your mediapad thanks to the proxy method (localhost / port:8080 ; you will be proposed to download a Firmware Finder ADD-ON from the Google Store. It helps to push the local file to the official system updater in Settings). Not that you don't have to download the OTA file with the Firmware Finder ; you can just use Firmware Finder to trick the local update installation and then manually put the update.zip file on the internal sdcard in this directory : HWFF/null/update.zip. (Firmware Finder servers are very slow at times so you better download the OTA file yourself on the site mentioned in other xda threads).
Good luck.
Thank you
thank you very much!
It's a really easy way. I learned a lot thanks to this.
Unroot was completed without any problems.
Thanks again
My pleasure, glad you've been able to sort this out. :good:
You can try a factory reset. Used to happen to mine also when running BTV-DL09-C100-B006. Not occurred on B009 and Nougat. Can be caused by many things when unlocked / rooted / xposed framework and so on installed. If stock, I would do a backup and try a factory reset. I also remember having tried to activate both navigation menu + fingerprint sensor for navigation than removed the navigation menu and it had solved the issue if I remember well. Maybe a coincidence though... don't know.
Hi everyone!
This is my second guide, but it was the first one written. Like I said in my first guide on how to systemlessly root your Pixel XL, I started writing these for myself so that I can keep straight all the things I like to do. I like simple, concise instructions that written clearly in way that anyone could understand. I've decided to start sharing these with the community!
This guide will teach you to manually flash Google's updates, like monthly security patches or version updates (like Oreo) to your Pixel XL while keeping your apps, settings, and data. It's a very simple and easy process. This guide assumes you know what the ADB/Fastboot and what flashing to your device means.
Pre-requisites:
1) The current ADB/Fastboot Platform Tools
2) A Pixel XL with an unlocked bootloader. This is essential, as a locked bootloader will not allow you to flash anything to your device
3) You should also be fully stock, meaning that you are not running a custom ROM (like PureNexus) and that you are not running a custom Kernel (like Franco or ElementalX)
4) OPTIONAL: Have a file structure for your device on your PC that makes sense to you - for Oreo updates, I use C:\Users\groov\Pixel XL\Oreo\ where I unzip the image and rename the folder to the month of the update, like August 2017 Stock. For the Platform Tools, I use C:\Users\groov\Pixel XL\platform-tools. I copy the necessary files into this folder for flashing.
STEPS:
1) Download the latest stock image
2) Unzip the stock image zip into your designated folder OR just unzip it right into platform-tools
3) Right click ‘flash-all.bat’ and click ‘edit’. You can use any text editor, like Notepad or Notepad++ (I like Notepad++ better because of the font highlighting and better tabbing)
4) Remove the ‘-w’ from near the end of the file; save the file
5) Put the device into bootloader mode (adb reboot bootloader OR power+volume down). Make sure the phone is connected to computer.
6) Double click ‘flash-all.bat’. The update will flash (this takes 5-10 minutes) and the phone will boot with the update installed and all data/settings preserved.
Please note that when you flash the update, it will seem at a few points like it is hanging; it is not. The process will clearly inform you when it is finished, and you will also get visual confirmation in the form of your device booting to system.
I have used this method twice so far - once to go back to 7.1.2 August Stock when I got into a TWRP bootloop trying to root (although I did not keep my data), and then to update to Oreo on Monday (I kept my data then). It worked successfully both times. This method will work for the regular Pixel as well (presuming you download the correct image).
This will obviously only work until Google stops supporting the first gen Pixels, but thankfully we have a long time until then
Please feel free to ask me any questions you might have. I will answer to the best of my ability, and if I don't know something I'll do my best to redirect you.
Good luck and happy flashing!
You can flash with locked bootloader if you download OTA image from same link just select "Full OTA Images" on left menu.
It will automatically preserve all the data, just follow instructions on the page.
I just used this method to update to the latest update. I'm still getting prompted on my phone to install the OTA. How can I stop the OTA update prompts?
[DEPRECATED] no longer working on due to real life issues. [DEPRECATED]
Please feel free to use my post and work on it yourselves, sorry.
Nexus 5x BLOD fix (OPM2.171019.029)
I recently purchased a Nexus 5x from ebay; it had the BLOD issue and, after many days I managed to fix it.
So I have decided to update the boot image to the 'latest' android factory image; this will allow people who have applied the patch to use a later version of Android or a custom ROM.
A huge thanks to @XCnathan32 for the original fix!
The steps below will wipe all data from your device!
For Rooting Information and Google Pay fix, see 2nd post.
Changelog
02/05/2018 - Updated method and added custom ROM method.
01/05/2018 - Updated TWRP from version 3.1.1.0 to 3.2.1-0.
What does this do?
There are two versions;
The first process will install the 'newest' stock version of Android onto your device; it will then install a custom recovery, and finally flash the updated boot.img file.
The boot.img has been modified slightly to only use 4 out of the 6 cores on the processor, this fixes the overheating issue with the Nexus 5x devices.
The other version is similar except using a custom version of Lineage OS.
Instructions
For detailed instructions and more info please visit the original thread.
Please make sure to have all of the downloaded file ready.
First Method - Stock Image
1. Boot into fastboot mode.
2. Extract factory image zip file and go into its directory.
3. With the phone in fastboot mode and connected the computer, open 'flash-all.bat'.
3a. Let the process finish; the device will reboot.
4. Go back into fastboot mode.
4a. [optional] you may wish to flash a custom recovery. If so move into the directory where you have the custom image downloaded. follow step 6a and type in
Code:
fastboot flash recovery [filename].img
5. Now move into the directory in which you downloaded the boot.img file.
6. Once inside; shift-right-click in the file manager and select 'open in powershell' or 'open in cmd'
7. Once the command window has opened: type in
Code:
fastboot flash boot boot.img
8. Now reboot the device!
Second Method - Custom ROM
1. Boot the device into fastboot mode
2. Download the ROM [linked below].
3. Download the GAPPS package [linked below].
4. Download Magisk [linked below].
5. Download the stock factory image; this is important as it contains the newest version of the bootloader, radio and vendor images, which is needed for Lineage to work [linked below].
6. Extract the stock factory image and go into it’s directory.
6a. There should be a file called ‘flash-all.bat’ - double-click to run it (Make sure phone is plugged in and in fastboot mode!).
6b. Let the process finish; the device should reboot.
7. Once the device has rebooted, again make sure it’s in fastboot mode.
8. Now download the custom version of TWRP; go into it’s directory then shift-right-click and select ‘open with cmd’ or ‘open with powershell’.
9. Then type the following:
Code:
fastboot flash recovery [filename].img
10. Once that process has finished (it should only take a sec), boot into recovery mode by selecting it via the volume up & down keys; the using the power button to select.
11. Once in recovery;
11a. Copy and paste the ROM zip archive, Magisk and the GAPPS package to the phone. You should be able to view your phone in the file explorer. If not please install the adb & fastboot drivers.
11b. Once done; go to ‘Install’ -> the select the zip file you transfered. It will now ask you to confirm, drag the bar across to accept the flash.
12. The ROM will now be flashing; leave it until it is done!
13. Once that process has finished; go back into the install section.
13a. Now you need to flash the GAPPS package.
14. Once the GAPPS has finished flashing; you now need to flash Magisk. This allows you to root your device and use services like Google Pay.
15. Now reboot!
If all is good then the device will reboot. You should see a boot animation (This can take up to 30 mins, so please wait!), after you should now see the android setup process.
Downloads
The fixed boot image can be downloaded from here.
The factory image: please make sure the version you are downloading matches the updated boot images'. It can be found here.
Modified Lineage OS ROM (boot image updated to the fix); it can be found here.
Magisk -> here.
GAPPS -> here. (Download for ARM64).
A fixed version of TWRP created by @XCnathan32 and updated by me to work with the 4-core boot image. Download Here.
Disclaimer
I will not be held responsible for anyone that decides to proceed with the steps listed above. If there are any issues please post them below with as much detail as you can. I will try my best to answer them, but I do have real-life stuff to deal with.
The original mod was not created myself! I have simply updated it.
Rooting info & Google pay fix
Rooting info & Google Pay fixFlashing Magisk after ROM will allow you to have root privileges and will also allow you to use
Magisk: it's HERE
My phone has bootloader locked. Is it needed?
lollazzo said:
My phone has bootloader locked. Is it needed?
Click to expand...
Click to collapse
Unfortunately, it is required so that you can flash the images. If you can't turn the device on then try the steps linked below;
https://forum.xda-developers.com/nexus-5x/general/untested-nexus-5x-bootloop-death-fix-t3641199
Goto the "*If your phone is bootloader locked/OEM locked:" section, I had the same issue and freezing my phone for 15 mins worked great.
Might work for you to
could you please fix the link to the Modified Lineage OS ROM.
thank you
deoneR said:
could you please fix the link to the Modified Lineage OS ROM.
thank you
Click to expand...
Click to collapse
Fixed it sorry for the wait; was busy with college etc.
if i do all your steps for the second method i always get a reboot to TWRP after ~ 3mins
what am i doing wrong?
deoneR said:
if i do all your steps for the second method i always get a reboot to TWRP after ~ 3mins
what am i doing wrong?
Click to expand...
Click to collapse
Try following method #1 first, then If you want; flash the custom ROM etc.
The custom ROM I provided works for me so I'm not 100% sure why it's not working. Trying the first method may help :|
lollazzo said:
My phone has bootloader locked. Is it needed?
Click to expand...
Click to collapse
Freezing did not worked for me , I put mine the oven and heated it to about 60 Grad Celsius.
That even gave me enough time to back up my data .
however, is back to live because of this tread.
Thanks.
This is the clear and simple instructions that always make things work first try! Thank you so much!
For June 5th security update I managed to work with those instructions, works perfect with making my own 4 core boot image and recovery.
http://aurelio.net/articles/nexus-5x-bootloop-fix.html
First fix that actually brought my phone back to life
Wow, amazing job, thank you very much! I tried many other methods to fix my device, and some allowed me to boot back into my phone, but I encountered errors like my wifi died etc. So I thought it was the end for my device and it turned into a very expensive USB flash drive lol. I don't know how your fix differs from the other ones on xda ( I used the first method), but it worked for me. So thanks again!
Something happened to my phone today. Its running 8.1 Pixel rom with the bload fix applied. All of a sudden my phone turned off today after running fine from so many months with blod fix. Now it doesn't boot. Google logo and turns off. Not even recovery is working (TWRP 4 core, patched). Can anyone suggest what's wrong?
Dragon's Fedora said:
Nexus 5x BLOD fix (OPM2.171019.029)
I recently purchased a Nexus 5x from ebay; it had the BLOD issue and, after many days I managed to fix it.
So I have decided to update the boot image to the 'latest' android factory image; this will allow people who have applied the patch to use a later version of Android or a custom ROM.
A huge thanks to @XCnathan32 for the original fix!
The steps below will wipe all data from your device!
For Rooting Information and Google Pay fix, see 2nd post.
Changelog
02/05/2018 - Updated method and added custom ROM method.
01/05/2018 - Updated TWRP from version 3.1.1.0 to 3.2.1-0.
What does this do?
There are two versions;
The first process will install the 'newest' stock version of Android onto your device; it will then install a custom recovery, and finally flash the updated boot.img file.
The boot.img has been modified slightly to only use 4 out of the 6 cores on the processor, this fixes the overheating issue with the Nexus 5x devices.
The other version is similar except using a custom version of Lineage OS.
Instructions
For detailed instructions and more info please visit the original thread.
Please make sure to have all of the downloaded file ready.
First Method - Stock Image
1. Boot into fastboot mode.
2. Extract factory image zip file and go into its directory.
3. With the phone in fastboot mode and connected the computer, open 'flash-all.bat'.
3a. Let the process finish; the device will reboot.
4. Go back into fastboot mode.
4a. [optional] you may wish to flash a custom recovery. If so move into the directory where you have the custom image downloaded. follow step 6a and type in
Code:
fastboot flash recovery [filename].img
5. Now move into the directory in which you downloaded the boot.img file.
6. Once inside; shift-right-click in the file manager and select 'open in powershell' or 'open in cmd'
7. Once the command window has opened: type in
Code:
fastboot flash boot boot.img
8. Now reboot the device!
Second Method - Custom ROM
1. Boot the device into fastboot mode
2. Download the ROM [linked below].
3. Download the GAPPS package [linked below].
4. Download Magisk [linked below].
5. Download the stock factory image; this is important as it contains the newest version of the bootloader, radio and vendor images, which is needed for Lineage to work [linked below].
6. Extract the stock factory image and go into it’s directory.
6a. There should be a file called ‘flash-all.bat’ - double-click to run it (Make sure phone is plugged in and in fastboot mode!).
6b. Let the process finish; the device should reboot.
7. Once the device has rebooted, again make sure it’s in fastboot mode.
8. Now download the custom version of TWRP; go into it’s directory then shift-right-click and select ‘open with cmd’ or ‘open with powershell’.
9. Then type the following:
Code:
fastboot flash recovery [filename].img
10. Once that process has finished (it should only take a sec), boot into recovery mode by selecting it via the volume up & down keys; the using the power button to select.
11. Once in recovery;
11a. Copy and paste the ROM zip archive, Magisk and the GAPPS package to the phone. You should be able to view your phone in the file explorer. If not please install the adb & fastboot drivers.
11b. Once done; go to ‘Install’ -> the select the zip file you transfered. It will now ask you to confirm, drag the bar across to accept the flash.
12. The ROM will now be flashing; leave it until it is done!
13. Once that process has finished; go back into the install section.
13a. Now you need to flash the GAPPS package.
14. Once the GAPPS has finished flashing; you now need to flash Magisk. This allows you to root your device and use services like Google Pay.
15. Now reboot!
If all is good then the device will reboot. You should see a boot animation (This can take up to 30 mins, so please wait!), after you should now see the android setup process.
Downloads
The fixed boot image can be downloaded from here.
The factory image: please make sure the version you are downloading matches the updated boot images'. It can be found here.
Modified Lineage OS ROM (boot image updated to the fix); it can be found here.
Magisk -> here.
GAPPS -> here. (Download for ARM64).
A fixed version of TWRP created by @XCnathan32 and updated by me to work with the 4-core boot image. Download Here.
Disclaimer
I will not be held responsible for anyone that decides to proceed with the steps listed above. If there are any issues please post them below with as much detail as you can. I will try my best to answer them, but I do have real-life stuff to deal with.
The original mod was not created myself! I have simply updated it.
Click to expand...
Click to collapse
With the second method, I flash all the files separately, and when I reboot it, the bootagement of Lineage OS started, but it got stuck, how do I fix it?
Dragon's Fedora said:
Nexus 5x BLOD fix (OPM2.171019.029)I recently purchased a Nexus 5x from ebay; it had the BLOD issue and, after many days I managed to fix it.
So I have decided to update the boot image to the 'latest' android factory image; this will allow people who have applied the patch to use a later version of Android or a custom ROM.
Click to expand...
Click to collapse
Good job! Works great for me and my similarly acquired device. Easy to read and follow write up too!
For others who may have done something weird like myself during the flash all process. The only issue I had initially was getting a boot and recovery sig not verified error message (or something like that). Worked around it by extracting the zipped image-bullhead-opm file and copying my fastboot files within the folder then fastboot flashing recovery, system and vendor manually. Then everything per steps explained worked as described. This is probably a common, well known error and fix to the BLOD Nexus 5X owners but I've just had this crazy device 2 days.
Thanks again!
Used 2nd method and worked perfectly.
Phone has been on non-the-less for a solid 3 hours and battery is stable (had really bad battery drain before, and the system was locking up and freezing and unresponsive as well 2-3 weeks before the BLOD.
I had also previously tried to flash a few other newer 8.1 roms after getting this BLOD, however phone crashed several times during installation and returned to BLOD and was unable to return to TWRP/recovery.
Glad the phone is back to life. Thanks a bunch for the modified rom, TWRP link, and guide!
On a side note, do you feel it is safe to try to flash other vendor images + roms + kernels now... or will the device go back to BLOD. From what I understood this is hardware issue, not software? @Dragon's Fedora
only4dank said:
Used 2nd method and worked perfectly.
Phone has been on non-the-less for a solid 3 hours and battery is stable (had really bad battery drain before, and the system was locking up and freezing and unresponsive as well 2-3 weeks before the BLOD.
I had also previously tried to flash a few other newer 8.1 roms after getting this BLOD, however phone crashed several times during installation and returned to BLOD and was unable to return to TWRP/recovery.
Glad the phone is back to life. Thanks a bunch for the modified rom, TWRP link, and guide!
On a side note, do you feel it is safe to try to flash other vendor images + roms + kernels now... or will the device go back to BLOD. From what I understood this is hardware issue, not software? @Dragon's Fedora
Click to expand...
Click to collapse
Whilst the issue is caused by the hardware; it's actually the software that causes the BLOD. The phone tries to use the 6 cores, but when it detects two of them failing it reboots the device. You can try use other; newer vendor images BUT you must make sure to change the boot.img file within the vendor zip folder.
Whilst the issue is caused by the hardware; it's actually the software that causes the BLOD. The phone tries to use the 6 cores, but when it detects two of them failing it reboots the device. You can try use other; newer vendor images BUT you must make sure to change the boot.img file within the vendor zip folder.
Dragon's Fedora said:
Whilst the issue is caused by the hardware; it's actually the software that causes the BLOD. The phone tries to use the 6 cores, but when it detects two of them failing it reboots the device. You can try use other; newer vendor images BUT you must make sure to change the boot.img file within the vendor zip folder.
Click to expand...
Click to collapse
there is a modified rom that is not stock to boot with the 4 cores, and flashed this boot and the recovery fixed and my nexus is restarted every 5 seconds I would appreciate your help and read many post and I think there is no solution
only4dank said:
Used 2nd method and worked perfectly.
Phone has been on non-the-less for a solid 3 hours and battery is stable (had really bad battery drain before, and the system was locking up and freezing and unresponsive as well 2-3 weeks before the BLOD.
I had also previously tried to flash a few other newer 8.1 roms after getting this BLOD, however phone crashed several times during installation and returned to BLOD and was unable to return to TWRP/recovery.
Glad the phone is back to life. Thanks a bunch for the modified rom, TWRP link, and guide!
On a side note, do you feel it is safe to try to flash other vendor images + roms + kernels now... or will the device go back to BLOD. From what I understood this is hardware issue, not software? @Dragon's Fedora
Click to expand...
Click to collapse
Which version of gapps did you use?