Android 6.0 1/2 Update problem - One (M9) Q&A, Help & Troubleshooting

Hello XDA, hello M9 users!
So, i rooted my phone back in September just to use some simple apps like Greenify, AdAway, etc. Yesterday the official Android 6.0 update arrived and I wanted to update. So I flashed the stock recovery and relocked my bootloader aaaand that was it. Everything was going ok untill the phone got in to the recovery. When it started to update the loading bar filled like 1/4. After that the red sign appeared on my screen. After that i just hard reseted my phone and everything was working ok and tried again but the same problem persisted. I started looking here on forums but i didn't find exact answeres except one. The guy sad: "The problem was solved. It took me 6 hours to manage this. All you need to do is re flash the stock backup with TWRP. ". Sadly I don't have the stock backup from my phone. And I'm thinking to reinstall TWRP recovery and flash version 1.32.401.8* from the thread called "HTC ONE M9 Stock File Collection (RUUs, Backups, etc.) - with linked Instructions" because I think that's the most stock version of this phone. So i have this question: should I do this or not? I am kinda noob, I am definetly not a pro with these things. I only know the basics and I am kindly asking for help. I will attach photos with phone info and everything that I mentioned here in the text. (sorry for my english, I'm trying my best)
If you guys find any solution I will be pleased to hear them!
Phone status:
-Rooted
-Bootloader: Relocked
-S ON
-Stock recovery (recovery version 2.10.401.1)
-SD Card capacity: 8GB only (i don't know if this helps)
-Stock 5.1 HTC Sense 7.0 (Software nr. 2.10.401.1)
-CID number: HTC__102
Thank you in advance!

Remember any changes with system such as root will cause OTA not work well.All you need to do is flash a RUU with right version.Or you can restore from TWRP with stock backup and flash stock recovery then you can get OTA.

If you want to install that update you either need the 2.10.401.1 backup or the corresponding RUU. As soon as you flash anything via TWRP your system gets mount as read/write. OTAs check the status of your system and fail if it's modified (=uninstalled system apps, root, etc.) and/or not mounted as read-only. Unrooting is not enough. You need to reflash an untouched system image (either via RUU or TWRP). Instructions can be found in my google sheet which is linked in post #5 of the thread where you found the 1.32.401.8 backup or in my signature.
Edit: Looks like I didn't type my answer fast enough.

Flippy498 said:
If you want to install that update you either need the 2.10.401.1 backup or the corresponding RUU. As soon as you flash anything via TWRP your system gets mount as read/write. OTAs check the status of your system and fail if it's modified (=uninstalled system apps, root, etc.) and/or not mounted as read-only. Unrooting is not enough. You need to reflash an untouched system image (either via RUU or TWRP). Instructions can be found in my google sheet which is linked in post #5 of the thread where you found the 1.32.401.8 backup or in my signature.
Edit: Looks like I didn't type my answer fast enough.
Click to expand...
Click to collapse
So the only thing i need to do is download "2.10.401.1.zip" RUU from your google sheet, copy it to my SD Card and enter in download mode and just wait untill it's done? Is this working with S-On?

It needs to be renamed correctly and the SD card needs to be formatted to fat32 (as stated in the instructions above the download links ). With S-ON you can use RUUs that have the same or a higher version than your phone. You only need S-OFF if you want to flash RUUs with a lower version (=downgrade) or one with a different SKU (the three numbers behind the second dot of the firmware version) than the one your phone got shipped with.

Flippy498 said:
It needs to be renamed correctly and the SD card needs to be formatted to fat32 (as stated in the instructions above the download links ). With S-ON you can use RUUs that have the same or a higher version than your phone. You only need S-OFF if you want to flash RUUs with a lower version (=downgrade) or one with a different SKU (the three numbers behind the second dot of the firmware version) than the one your phone got shipped with.
Click to expand...
Click to collapse
I am S-On and i don't want to S-Off. I don't want a lower version of RUU and i just want to simply upgrade to Android 6.0. So am I doing the right thing?

strikercs said:
I am S-On and i don't want to S-Off. I don't want a lower version of RUU and i just want to simply upgrade to Android 6.0. So am I doing the right thing?
Click to expand...
Click to collapse
Flippy498 said:
With S-ON you can use RUUs that have the same or a higher version than your phone.
Click to expand...
Click to collapse
Your version is 2.10.401.1 and the RUU has version 2.10.401.1, too.
Re-read my last post. I never said that you should S-OFF. You wanted to know whether you can use a RUU with S-ON and I explained why S-OFF is not needed in your situation.

Flippy498 said:
Your version is 2.10.401.1 and the RUU has version 2.10.401.1, too.
Re-read my last post. I never said that you should S-OFF. You wanted to know whether you can use a RUU with S-ON and I explained why S-OFF is not needed in your situation.
Click to expand...
Click to collapse
I have downloaded and copied the file on my SD Card using an SD Card reader because it wouldn't let me copy it using USB. The SD Card is FAT32 and i renamed the file to "0PJAIMG.zip". When i boot into the download mode it just enters download mode. It doesn't ask me if i want to flash the file. Any ideas what could be wrong?

Flippy498 said:
Your version is 2.10.401.1 and the RUU has version 2.10.401.1, too.
Re-read my last post. I never said that you should S-OFF. You wanted to know whether you can use a RUU with S-ON and I explained why S-OFF is not needed in your situation.
Click to expand...
Click to collapse
I have downloaded and copied the file on my SD Card using an SD Card reader because it wouldn't let me copy it using USB. The SD Card is FAT32 and i renamed the file to "0PJAIMG.zip". When i boot into the download mode it just enters download mode. It doesn't ask me if i want to flash the file. Any ideas what could be wrong? I attached a screesnshot.

Are you sure you didn't rename it to "0PJAIMG.zip.zip". Looking at the "nmdsdcid" file I assume that file extensions aren't visible on your pc which could be the reason for your mistake.

Flippy498 said:
Are you sure you didn't rename it to "0PJAIMG.zip.zip". Looking at the "nmdsdcid" file I assume that file extensions aren't visible on your pc which could be the reason for your mistake.
Click to expand...
Click to collapse
I told you that I'm a noob. That's exactly what happened..

strikercs said:
I told you that I'm a noob. That's exactly what happened..
Click to expand...
Click to collapse
Thank you @Flippy498! Succesfully updated to Android 6.0!

So @Flippy498 saved my day with #3.
After getting to his really nice collection which can be found here and here I downloaded a TWRP Backup for my CID.
Remember fastboot getvar cid ?
Then I followed his nice tutorial until Step 5, but skipped 1 - 3.
Flippy498 said:
01. Format your SD card with a PC to exfat and put it back into your phone.
02. Boot to TWRP.
03. Create a backup on your external SD card. (Backing up "Boot" is more than enough. We only want TWRP to create the needed directories on your SD card.)
04. Download the correct backup for your firmware version. (It is stated in the line with "OS" at the beginning when you boot to download mode. The "firmware version" in "settings>about>software information>more" is only the base of the rom you are running.)
05. Unzip the downloaded backup.
06. Copy the unzipped backup folder to "TWRP/BACKUPS/<YourSerialnumber>/"on your SD card. Sometimes this is only possible if the SD card is directly connected to your PC and not put into your phone. I don't know why some M9s refuse the copy process.
Click to expand...
Click to collapse
So here was my problem, I have no external sd-card in my phone and trying to copy the 4.2 GB File via "Android Transfer" brought up the error, that files largen then 4GB are not supported to copy.
So I first made sure I prepared the following steps:
Flippy498 said:
07. I recommend wiping everything except "Micro SDcard", "USB-OTG" and "SD-Ext".
08. Check the "Mount system as read-only" box in the Mount menu.
Click to expand...
Click to collapse
Now make a folder structure like in Step 6 (if you are still in TWRP, no problem use the "mkdir <foldername>" command via the advanced tools tab. (read on, I tell you where it is)
So then, instead I copied the 2GB zip file in that folder and went to advanced tools in TWRP. There I chose the "execute command" tool, went inside the folder with the serialnumber and clicked select.
Now a command line appears and I entered "unzip" and the name of the zipfile ... well that took some time ... dont tend to klick kill ... you can make 3 coffees in that time (I advise you to drink only two :silly: otherwise you get overexcited)
After that another folder with the name of the zipfile shows up. Go back and click restore - then check that folder and three X Marks will appear, showing you that these mounts will be overwritten.
Now swipe to restore and go on:
Flippy498 said:
09. Restore the backup.
10. Boot to system (ignore the warning that no OS is installed). This process may actually take a while!
11. Congrats! Your system is now stock and able to receive and install official OTAs, again.
Click to expand...
Click to collapse
and thats's it. Worked like a charm. Thanks again @Flippy498 :highfive: !!

Related

[Q] Help With Unrooting HTC One M8

Hey everyone, here's the situation that I am in right now:
I rooted my phone and flashed an Insert Coin ROM but wanted to return it back to complete stock form.
I have a HTC One M8 thats currently locked to T-Mobile. The CID is T-MOB010 and the Build Number is 2.22.401.4
There is TWRP installed on this phone, version 2.8.1.0.
The problem that I am having is this: when I boot into TWRP recovery mode, I go to restore and look for the stock ROM, but it does not show up in the menu. I looked in both internal storage and SD Card storage, but it does not show up in either. I also tried moving the files manually through TWRP, but no luck.
I looked through the phones files using the File Manager App and I see the files are there, but once again I cannot see them when I use TWRP recovery mode.
Does anyone know why this is happening?
http://forum.xda-developers.com/showthread.php?t=2701376
read that all...hint 1 : your OFFICIAL build number is NOT 2.22.401 !
Not sure I follow. I checked the build number on my phone to confirm.
MW2 said:
Not sure I follow. I checked the build number on my phone to confirm.
Click to expand...
Click to collapse
That's the ROM base (software build). What you need to know is your firmware version. Boot into your bootloader (turn off phone, then hold power + vol down). What it says under OS is your firmware version.
You can also hook up to your PC/ADB in fastboot, and issue the command fastboot getvar all. What it says under version-main is your firmware.
xunholyx said:
That's the ROM base (software build). What you need to know is your firmware version. Boot into your bootloader (turn off phone, then hold power + vol down). What it says under OS is your firmware version.
You can also hook up to your PC/ADB in fastboot, and issue the command fastboot getvar all. What it says under version-main is your firmware.
Click to expand...
Click to collapse
I have done that and the OS version is not stated.
MW2 said:
I have done that and the OS version is not stated.
Click to expand...
Click to collapse
That is caused by your recovery being out of date. It`is also reported to be caused with TWRP 2.8.1.0. Update to TWRP 2.8.0.3. There is another newer version, but 0.3 seems to be the most stable.
Updated TWRP, still no OS version listed.
In order to explain fully I need to show the process I tried using.
I followed the instructions from this site: http://theunlockr.com/2014/06/08/how-to-unroot-the-htc-one-m8-video/
I boot my phone into recovery mode and select the Restore option in TWRP. I try to find the Nandroid backup that I transferred to my phone but it does not show up. I try looking through both the internal storage and SD card but nothing shows up there either.
MW2 said:
Updated TWRP, still no OS version listed.
Click to expand...
Click to collapse
[Recovery] [RUU 2.22.531.6] [TWRP Nandroid Backups] [Radio IMGs][ OTA 3.32.531.2
Just do an RUU and get back to stock, seeing as you are T-Mobile US yes? T-MOB010 is T-Mobile US...
There you'll get RUU, recoveries, radios, nand backups and OTA's (Which contains firmware already).
I don't get what the problem is?
The problem is when I boot into TWRP Recovery and go to the Restore option, the files are not showing. I checked both internal and SD Card storage but it does not show either. I am using TWRP 2.8.0.3
MW2 said:
The problem is when I boot into TWRP Recovery and go to the Restore option, the files are not showing. I checked both internal and SD Card storage but it does not show either. I am using TWRP 2.8.0.3
Click to expand...
Click to collapse
Try making a backup of just the boot to either internal/sdcard, so that TWRP can create the directory for you. Maybe you didn't unpack it into the right directory.
Make sure you have your devices "serial number" folder and not the one from the person that backed it up(If you're using a downloaded nand). When it's unpacked you have to place just the backup folder into the directory, if they kept it "default" it'll start with the date--time--release for example: 2014-12-06--05-20-22-KTU84P release-keys The highlighted area can ofcourse change depending on the version it has backed up, as will date and time(Logically). Inside that folder you'll have plenty of files like boot.emmc.win, system.ext4.win000 (etc) data.ext4.win etc etc. You need to place that folder inside the TWRP Backups folder.
Like I said, make backup of boot so that TWRP can create the directory for you, then it'll end up something like:
/storage/ext_sd/TWRP/BACKUPS/yourserialnumberfolder/2014-12-06--05-20-22-KTU84Prelease-keys/
Thanks for the advice.
I managed to fix the issue using RUU. I don't know why TWRP was acting this way, but my I'm ok now.
Thank you everyone for the help
Here is the method I used just for future references: http://www.android.gs/downgrade-t-mobile-htc-one-m8-to-official-stock-firmware-with-ruu/

Help with Android_revolution_HD - Wifi doesn't work, Wiping phone assistance

Hi guys!
I'm selling my HTC one m8 Today, and i would like to sell it with the newest version of android, so i installed ARHD 34.0 for HTC one m8 through twrp v2.8.4.0, and it installs without any errors but i can't toggle wifi when it boots up.
i was using One_M8_2.22.401.4_odexed before and i didnt get any OTA's which was very annoying.
what would be easiest to completely unroot my phone delete twrp and find a Stock rom.
Or fix wifi on ARHD 34.0?
i have searched for hours for a fix for either one i beg of your assistance
my HTC one m8 is european, so i guess the international stuff works for me.
and i have S-on
Thanks in advance !
Bombi22 said:
Hi guys!
I'm selling my HTC one m8 Today, and i would like to sell it with the newest version of android, so i installed ARHD 34.0 for HTC one m8 through twrp v2.8.4.0, and it installs without any errors but i can't toggle wifi when it boots up.
i was using One_M8_2.22.401.4_odexed before and i didnt get any OTA's which was very annoying.
what would be easiest to completely unroot my phone delete twrp and find a Stock rom.
Or fix wifi on ARHD 34.0?
i have searched for hours for a fix for either one i beg of your assistance
my HTC one m8 is european, so i guess the international stuff works for me.
and i have S-on
Thanks in advance !
Click to expand...
Click to collapse
Your firmwae is old and that's why wifi is not working.
You have 2 option either S-OFF or flash stock nand and do officail OTA upto 4.4.4 because 5.0 will arrive this week .
Post the result of "fastboot getvar all" and i will provide you backup link.
Hide imei and serial number before posting result of abve command,..
ahsan64 said:
Your firmwae is old and that's why wifi is not working.
You have 2 option either S-OFF or flash stock nand and do officail OTA upto 4.4.4 because 5.0 will arrive this week .
Post the result of "fastboot getvar all" and i will provide you backup link.
Hide imei and serial number before posting result of abve command,..
Click to expand...
Click to collapse
where do i find stock nand ?
should i take the stock nandroid backup from here ?
http://forum.xda-developers.com/showthread.php?t=2701376
and load it, would that do it ?
thanks alot for your response
Bombi22 said:
where do i find stock nand ?
should i take the stock nandroid backup from here ?
http://forum.xda-developers.com/showthread.php?t=2701376
and load it, would that do it ?
thanks alot for your response
Click to expand...
Click to collapse
Yes take nandroid form there and load it and update officially but remmeber to take backup of your own or any WWE base CID number .
ahsan64 said:
Yes take nandroid form there and load it and update officially but remmeber to take backup of your own or any WWE base CID number .
Click to expand...
Click to collapse
i cant see that .rar file in twrp Restore, tried to open the rar file and put the folder on Sdcard too but cant see it in Restore :s
how do i use that backup file ?
Bombi22 said:
i cant see that .rar file in twrp Restore, tried to open the rar file and put the folder on Sdcard too but cant see it in Restore :s
how do i use that backup file ?
Click to expand...
Click to collapse
You have to unpack it and place it inside the TWRP backup folder. If you can't see it then perhaps you're looking at the wrong storage location.
Check in both the internal and SD card. Else let TWRP "recreate" the directory for you, can easily do it by making a backup of just boot.
Make sure to copy the contents of the "serial number folder" into "your" own serial number folder(on device).
TWRP/Backups/serialnum/ serialnum is of course the serial number for your own device. Though the backups you download will have the serial number for a different device, which is why I said copy the contents of that folder and not the entire folder.
BerndM14 said:
You have to unpack it and place it inside the TWRP backup folder. If you can't see it then perhaps you're looking at the wrong storage location.
Check in both the internal and SD card. Else let TWRP "recreate" the directory for you, can easily do it by making a backup of just boot.
Make sure to copy the contents of the "serial number folder" into "your" own serial number folder(on device).
TWRP/Backups/serialnum/ serialnum is of course the serial number for your own device. Though the backups you download will have the serial number for a different device, which is why I said copy the contents of that folder and not the entire folder.
Click to expand...
Click to collapse
i have installed Stock Recovery and and done a factory reset but it didnt install the Stock rom that i thought it would do..
what do i do now ? how can i install this stock rom : 0P6BIMG_M8_UL_K444_SENSE60_MR_HTC_Europe_3.28.401.9_R_Radio_1.22.21331147A1.29G_20.67.4196.01_release_402839_signed-decrypted
with stock recovery and fastboot ? :s
Hey again, im still stuck with this issue
how do i flash twrp, with Fastboot ?, i have S-on. and it says that no devices is found in cmd when i run fastboot.exe
Bombi22 said:
Hey again, im still stuck with this issue
how do i flash twrp, with Fastboot ?, i have S-on. and it says that no devices is found in cmd when i run fastboot.exe
Click to expand...
Click to collapse
cmd you'll need to change directory to fastboot/adb folder. It'll be faster though to just open the adb folder, hold shift and right click anywhere in the white area of the folder(not on the files) and select open command prompt here. The command to check for the device isn't fastboot.exe, it's fastboot devices <<<Only if you're in fastboot mode, while in recovery or running Android system it'll be adb devices
You'll have to go to HTCDev.com and follow instructions on how to unlock your bootloader(I saw the other thread you made locking the bootloader ).
You can't flash a custom recovery if the bootloader is locked. So follow on screen instructions at http://www.htcdev.com/bootloader
On a side note to original question, the command to flash a custom recovery is fastboot flash recovery name_of_the_recovery.img <<<Recovery image file must be placed inside directory cmd is in, in this case, adb/fastboot folder.
BerndM14 said:
cmd you'll need to change directory to fastboot/adb folder. It'll be faster though to just open the adb folder, hold shift and right click anywhere in the white area of the folder(not on the files) and select open command prompt here. The command to check for the device isn't fastboot.exe, it's fastboot devices <<<Only if you're in fastboot mode, while in recovery or running Android system it'll be adb devices
You'll have to go to HTCDev.com and follow instructions on how to unlock your bootloader(I saw the other thread you made locking the bootloader ).
You can't flash a custom recovery if the bootloader is locked. So follow on screen instructions at http://www.htcdev.com/bootloader
On a side note to original question, the command to flash a custom recovery is fastboot flash recovery name_of_the_recovery.img <<<Recovery image file must be placed inside directory cmd is in, in this case, adb/fastboot folder.
Click to expand...
Click to collapse
Hey again mate !
i just unlocked my bootloader again and flashed latest version of twrp, installed the latest Android revolution 34.0 but the result is the same, wifi doesnt work. and i have the .401 firmware.zip but for some reason it doesnt want to flash it, i still have S-on but the Firmware might be really old too im not sure ?
Bombi22 said:
Hey again mate !
i just unlocked my bootloader again and flashed latest version of twrp, installed the latest Android revolution 34.0 but the result is the same, wifi doesnt work. and i have the .401 firmware.zip but for some reason it doesnt want to flash it, i still have S-on but the Firmware might be really old too im not sure ?
Click to expand...
Click to collapse
Yeah it's because you still didn't update the firmware for your device, so it won't work!
Download the TWRP nandroid backup(like mentioned before) and place it inside the TWRP backup folder and restore it. After it's restored, flash back the stock recovery and let it do OTA updates.
will it get the OTA's if i install .401 odexed and stock recovery ?
Bombi22 said:
will it get the OTA's if i install .401 odexed and stock recovery ?
Click to expand...
Click to collapse
I suppose your first post here probably answered that question for you already...
i was using One_M8_2.22.401.4_odexed before and i didnt get any OTA's which was very annoying.
Click to expand...
Click to collapse
Why try and make things more complicated than it needs to be. Download a nandroid backup, restore it, flash stock recovery and do OTA's. That's it...
yea but i didnt have stock recovery might be therefor i could'nt install the OTA's
i have deleted ARHD 34.0 now, im gonna find another nandroid backup now and figure out where to put it
should the nandroid backup be in zip ?
- Edit
i found a backup named 2014-10-25--04-09-42 KTU84L release-keys
where should i put it ?
Bombi22 said:
yea but i didnt have stock recovery might be therefor i could'nt install the OTA's
i have deleted ARHD 34.0 now, im gonna find another nandroid backup now and figure out where to put it
should the nandroid backup be in zip ?
Click to expand...
Click to collapse
No...I said it in post 6 already, unpack it(in other words, unzip it).
Once it's unzipped you'll probably see a folder named something like yyyy-mm-dd--hh-mm-ss BASENAME release-keys - for example 2014-10-15--23-07-49 KTU84L release-keys... Dates, Time and "BASE"(KTU84L) will obviously change. Inside that folder you'll find files like boot.emmc.win , system.ext4.win000 , recovery.log etc.
That entire folder "2014 [...] release-keys" must be placed inside your serial number folder. If you don't have one yet, create a backup of "Boot" only so that TWRP can create the directory for you. So when it's finished the directory will look something like this:
/storage/ext_sd/TWRP/BACKUPS/SH41RMW18761/2014-10-15--23-07-49 KTU84L release-keys/
Storage location might change depending on whether you use SD Card or not. Better to use it anyways. Of course Serial Number SH41RMW18761 is a made up serial number, your devices serial number WILL be different.
Once you placed it in the correct serial folder, you can go into TWRP, select the storage location(Like I said it'll be better to do SD Card) and TWRP should pick up the nandroid backup from there. Select it and swipe to restore.
BerndM14 said:
No...I said it in post 6 already, unpack it(in other words, unzip it).
Once it's unzipped you'll probably see a folder named something like yyyy-mm-dd--hh-mm-ss BASENAME release-keys - for example 2014-10-15--23-07-49 KTU84L release-keys... Dates, Time and "BASE"(KTU84L) will obviously change. Inside that folder you'll find files like boot.emmc.win , system.ext4.win000 , recovery.log etc.
That entire folder "2014 [...] release-keys" must be placed inside your serial number folder. If you don't have one yet, create a backup of "Boot" only so that TWRP can create the directory for you. So when it's finished the directory will look something like this:
/storage/ext_sd/TWRP/BACKUPS/SH41RMW18761/2014-10-15--23-07-49 KTU84L release-keys/
Storage location might change depending on whether you use SD Card or not. Better to use it anyways. Of course Serial Number SH41RMW18761 is a made up serial number, your devices serial number WILL be different.
Once you placed it in the correct serial folder, you can go into TWRP, select the storage location(Like I said it'll be better to do SD Card) and TWRP should pick up the nandroid backup from there. Select it and swipe to restore.
Click to expand...
Click to collapse
Thanks ill try that out !
should i change KTU84L to the BASENAME of the backup i made ?
my backup basename is LRX22C should i change the nandroid backup name from KTU84L to LRX22C ?
Bombi22 said:
should i change KTU84L to the BASENAME of the backup i made ?
my backup basename is LRX22C should i change the nandroid backup name from KTU84L to LRX22C ?
Click to expand...
Click to collapse
No just copy the folder in the serial number folder. Then go to TWRP, Select Restore, If you must select SD Card / Internal depending where you place nandroid, then Select the nandroid and swipe to restore.
BerndM14 said:
No just copy the folder in the serial number folder. Then go to TWRP, Select Restore, If you must select SD Card / Internal depending where you place nandroid, then Select the nandroid and swipe to restore.
Click to expand...
Click to collapse
the backup restoration went smooth but..
can i reset phone in Backup & reset under phone settings ? cause there is so tonz of crap apps that i cant delete in my menu :s
would it delete everything if i reset phone from settings ?
Bombi22 said:
the backup restoration went smooth but..
can i reset phone in Backup & reset under phone settings ? cause there is so tonz of crap apps that i cant delete in my menu :s
would it delete everything if i reset phone from settings ?
Click to expand...
Click to collapse
Yeah you can do a factory reset. It won't get rid of any "system" apps though. Facebook, Twitter and crap like that will stay there.

[Q] Need advice on the final stages of back to stock

Ive successfully gone through every stage of converting my M9 from EE to an unbranded M9.
Im stuck on the CID... My ORANG001 wont accept the compatible CIDs for wwe 401.8.. 001 or 002, benups on SS Live chat says its an EE app.
is it safe to use super su to remove them...
Any advice there please?
Then whats next, how do i flash the ruu as theres so many threads on what to do with the ruu, sd card (ntfs or exfat) or adb flash and how should i flash it..
Please keep it simple..
Theres so much info... Its all confusing.
NightOrchid said:
[...]
Click to expand...
Click to collapse
First, it's hard to help with that little information you give. I have to assume some things so some assumptions may be wrong.
Your current state is:
Security: S-OFF? (since you already changed your CID and mentioned that you talked to beaups)
CID: ORANG001
Firmware: 1.32.401.8 or 1.40.401.8? (x.xx.401.8 is all you mentioned)
And your device doesn't boot into android and keeps rebooting if you change your CID
Well, I don't think that you converted you phone successfully to the international unbranded version since your phone doesn't accept the different CIDs.
Please read my whole answer before you start flashing since I'm describing more than one solution.
Solution using signed HTC files (inludes the stock rom):
If I were you I would convert the CID to HTC__001 and run a RUU. It's actually quite simple and afterwards your phone should boot even if you don't use your original CID. Just be aware of the fact that all your data and files are going to be deleted during this process. So backup everything that is important for you (e.g. SMS or contacts). Since you seem to be S-OFF and I don't know your current firmware version I'm going to use the 1.32.401.8 version in my instructions. It might downgrade your system but since it's a signed HTC file it won't harm your device and you can update your device using the OTA function of the stock system afterwards.
If your bootloader is unlocked you can leave it like that. There is no need to relock if you are S-OFF.
Get a SD-card that is not bigger than 32 gb and formatted to fat32 (I've always been using the formatting function of the m9 for this step).
Change your CID using
Code:
fastboot oem writecid HTC__001
in download mode.
Download this RUU.
Rename the RUU to "0PJAIMG.zip".
Copy that file into the root direction of your SD-card.
Put the card back into your phone.
Be sure that your phone is charged enough (more than 50 %; around 100 % might be better since you'll have to do some updates later).
Boot into download mode (reboot the download mode if you didn't leave it since the CID change).
Follow the instructions on the screen.
Wait some minutes.
Done.
After you followed these steps you only need to download and install the official updates via the settings menu. After that you can start flashing TWRP and SuperSu or you install a custom rom if you like.
Don't forget: 1.32.401.8 is the first officially published firmware version so your phone might get quite hot until you downloaded and installed the first update.
For being able to install later updates you either have to flash the corresponding RUU (version 1.40.401.8 if you followed the above instructions) or you need to create a backup of your untouched system:
Do not install the latest update (1.40.401.8). Only download the file.
Copy the update from /data/data/com.htc.updater/files/ to your pc.
Get the recovery from the firmware folder of that zip-file.
Format your SD-card to exfat and put it back into your phone.
Install the update.
Flash the latest TWRP version.
Boot into TWRP and mount the system as read-only. (Look at the instructions of your m9's screen.)
Create a backup on your SD-Card that contains a system image and the recovery, too.
Copy the backup to your pc and delete the "recovery.emmc.win" file. If you created md5-files you need to delete the corresponding file, too.
Copy the recovery you grabbed from the update earlier into your backup folder.
Rename the recover file to "recovery.emmc.win".
If you now want to get back to stock you simply need to copy your backup back onto your SD-card, boot into TWRP, mount the system as read-only again (mount menu) and restore the backup. TWRP will replace itself with the stock recovery then so that you can install any upcoming update. Nevertheless you need to redo this procedure every time you want to update your system.
Solution using unsigned files (you need to flash a rom afterwards):
Follow the instructions in Sneakyghosts thread.
Thanks Flippy498..
ALL SORTED )
Thanks for the clear instructions and taking the time.. Im now on unbranded WWE 1.40.401.8. When I flashed the 1.32 through download mode I flashed the same rom twice, just to make sure it got everything. Then took the 2 OTAs up to 1.40 "camera" update, updated and setup play store apps so everything is working great now, wow that was a tough flash.. as so many things can go wrong.
I alsokept s-off and unlocked.. so i can jump between roms if i want
Thanks for the patience and thanks to all who helped as Ive learned so much.. Appreciated
Flippy498 said:
First, it's hard to help with that little information you give. I have to assume some things so some assumptions may be wrong.
Your current state is:
Security: S-OFF? (since you already changed your CID and mentioned that you talked to beaups)
CID: ORANG001
Firmware: 1.32.401.8 or 1.40.401.8? (x.xx.401.8 is all you mentioned)
And your device doesn't boot into android and keeps rebooting if you change your CID
Well, I don't think that you converted you phone successfully to the international unbranded version since your phone doesn't accept the different CIDs.
Please read my whole answer before you start flashing since I'm describing more than one solution.
Solution using signed HTC files (inludes the stock rom):
If I were you I would convert the CID to HTC__001 and run a RUU. It's actually quite simple and afterwards your phone should boot even if you don't use your original CID. Just be aware of the fact that all your data and files are going to be deleted during this process. So backup everything that is important for you (e.g. SMS or contacts). Since you seem to be S-OFF and I don't know your current firmware version I'm going to use the 1.32.401.8 version in my instructions. It might downgrade your system but since it's a signed HTC file it won't harm your device and you can update your device using the OTA function of the stock system afterwards.
If your bootloader is unlocked you can leave it like that. There is no need to relock if you are S-OFF.
Get a SD-card that is not bigger than 32 gb and formatted to fat32 (I've always been using the formatting function of the m9 for this step).
Change your CID using
Code:
fastboot oem writecid HTC__001
in download mode.
Download this RUU.
Rename the RUU to "0PJAIMG.zip".
Copy that file into the root direction of your SD-card.
Put the card back into your phone.
Be sure that your phone is charged enough (more than 50 %; around 100 % might be better since you'll have to do some updates later).
Boot into download mode (reboot the download mode if you didn't leave it since the CID change).
Follow the instructions on the screen.
Wait some minutes.
Done.
After you followed these steps you only need to download and install the official updates via the settings menu. After that you can start flashing TWRP and SuperSu or you install a custom rom if you like.
Don't forget: 1.32.401.8 is the first officially published firmware version so your phone might get quite hot until you downloaded and installed the first update.
For being able to install later updates you either have to flash the corresponding RUU (version 1.40.401.8 if you followed the above instructions) or you need to create a backup of your untouched system:
Do not install the latest update (1.40.401.8). Only download the file.
Copy the update from /data/data/com.htc.updater/files/ to your pc.
Get the recovery from the firmware folder of that zip-file.
Format your SD-card to exfat and put it back into your phone.
Install the update.
Flash the latest TWRP version.
Boot into TWRP and mount the system as read-only. (Look at the instructions of your m9's screen.)
Create a backup on your SD-Card that contains a system image and the recovery, too.
Copy the backup to your pc and delete the "recovery.emmc.win" file. If you created md5-files you need to delete the corresponding file, too.
Copy the recovery you grabbed from the update earlier into your backup folder.
Rename the recover file to "recovery.emmc.win".
If you now want to get back to stock you simply need to copy your backup back onto your SD-card, boot into TWRP, mount the system as read-only again (mount menu) and restore the backup. TWRP will replace itself with the stock recovery then so that you can install any upcoming update. Nevertheless you need to redo this procedure every time you want to update your system.
Solution using unsigned files (you need to flash a rom afterwards):
Follow the instructions in Sneakyghosts thread.
Click to expand...
Click to collapse
great details. Just wanna clarify, using the SD card method, after flashing the 0PJAIMG.zip, does the recovery go back to stock if the person was on twrp before? because I noticed you mentioned "After that you can start flashing TWRP"? Just asking.
also was there a reason not to suggest supercid in this case? tia.
simonbigwave said:
great details. Just wanna clarify, using the SD card method, after flashing the 0PJAIMG.zip, does the recovery go back to stock if the person was on twrp before? because I noticed you mentioned "After that you can start flashing TWRP"? Just asking.
also was there a reason not to suggest supercid in this case? tia.
Click to expand...
Click to collapse
Yes, flashing RUUs overwrites TWRP with the stock recovery. Of course you can use the SupcerCID for the RUU but I'm not sure if you are able to install offcial updates afterwards since I always stay on my original CID. That's the reason why I suggested HTC__001 because as far as I know it is the corresponding unbranded CID to ORANG001.
Flippy498 said:
Yes, flashing RUUs overwrites TWRP with the stock recovery. Of course you can use the SupcerCID for the RUU but I'm not sure if you are able to install offcial updates afterwards since I always stay on my original CID. That's the reason why I suggested HTC__001 because as far as I know it is the corresponding unbranded CID to ORANG001.
Click to expand...
Click to collapse
I wasnt aware about corresponding cids. So how do we know what is the 'corresponding unbranded cid' for our device? (Is it just the numerals eg 001 have to match from ORANG001 to HTC_001 or how?) Tia.
There are many CID lists on the internet. Just google "HTC CID list". All CIDs with HTC__*** are unbranded ones. It's actually not necessary to use the corresponding one since all of them can be used with the x.xx.401.xx firmware versions. It's just my personal preference to change CIDs to the corresponding ones.

[A5_CHL] Need TWRP Backup

SuperSU told me that my SU binary was out of date and so i tried to update it through TWRP like it recommended. Well that ended up failing in the middle of it (I don't have logs) and it seems like the backup I had is missing from my SD card. Whenever I load android it goes black screen, it'll show the back button and the status bar but none of that will be interactive. I can power it down but if i wait too long the buttons won't work. Anyways I was hoping someone had a backup for the a5_chl phone.
end360 said:
SuperSU told me that my SU binary was out of date and so i tried to update it through TWRP like it recommended. Well that ended up failing in the middle of it (I don't have logs) and it seems like the backup I had is missing from my SD card. Whenever I load android it goes black screen, it'll show the back button and the status bar but none of that will be interactive. I can power it down but if i wait too long the buttons won't work. Anyways I was hoping someone had a backup for the a5_chl phone.
Click to expand...
Click to collapse
Sorry your having problems. Why not just get the stock RUU file directly from HTC/downloads and flash back your stock recovery by running the RUU on your computer and before hitting start type %temp% into the search box and go to the RUU's running files and in one of the numbered files will be the rom.zip and within that file will be the recovery image. Copy that to your ADB/fastboot folder then flash it over your TWRP recovery but first I'd wipe the system and data in advanced wipe in TWRP to get your system partition clean( THIS WIPES THE WHOLE PHONE SO BE AWARE OF THAT AND MOVE FILES TO YOUR COMPUTER ACCORDINGLY OR BACK UP USING GOOGLE STOCK BACKUP IN SETTINGS IF YOU'RE NOT ALREADY FOR CONTACTS AND NUMBERS ETC). Then relock your bootloader with the stock recovery flashed back and run the RUU or put it in your ext SD and rename the file to OP9CIMG and reboot into your bootloader and it should automatically pick up the file and start flashing it. I have this same model phone and I keep my stock RUU that I got from HTC on my computer for just such a problem. I got a stock recovery zip from somewhere else but i can't remember where but it's also within the RUU itself. Try to find the link for you in a bit.
EDIT: here's a link to someone I know who had a whole tutorial for the a5_ul version of our phone on how to flash back a stock RUU from your computer or from within your ext SD card. Obviously the links with the files aren't valid for our phone but the steps are . Also has instructions for restoring using a TWRP backup but I wouldn't use someone else's TWRP backup if my hair was on fire. Especially since we have access to the pure stock RUU with our version why not take advantage of it. That's all I'm saying.
http://forum.xda-developers.com/desire-816/help/guide-how-to-flash-stock-recovery-ruu-t3308502
And here's the HTC RUU downloads link below
http://www.htc.com/us/support/rom-downloads.html
And lastly a link to a tutorial on extracting the stock recovery from the RUU .
http://androidforums.com/threads/guide-re-flash-stock-rom-ruu-after-bricking-a-rooted-device.565203/
Well not lastly I guess because here is a link to the stock recovery provided by FoxyDrew. Don't use the RUU link it's to kitkat but the recovery link below it is the same for lollipop as it's for the a5_chl
http://forum.xda-developers.com/desire-816/general/ruu-t2952058/post57019175#post57019175
thoctor said:
Sorry your having problems. Why not just get the stock RUU file directly from HTC/downloads and flash back your stock recovery by running the RUU on your computer and before hitting start type %temp% into the search box and go to the RUU's running files and in one of the numbered files will be the rom.zip and within that file will be the recovery image. Copy that to your ADB/fastboot folder then flash it over your TWRP recovery but first I'd wipe the system and data in advanced wipe in TWRP to get your system partition clean( THIS WIPES THE WHOLE PHONE SO BE AWARE OF THAT AND MOVE FILES TO YOUR COMPUTER ACCORDINGLY OR BACK UP USING GOOGLE STOCK BACKUP IN SETTINGS IF YOU'RE NOT ALREADY FOR CONTACTS AND NUMBERS ETC). Then relock your bootloader with the stock recovery flashed back and run the RUU or put it in your ext SD and rename the file to OP9CIMG and reboot into your bootloader and it should automatically pick up the file and start flashing it. I have this same model phone and I keep my stock RUU that I got from HTC on my computer for just such a problem. I got a stock recovery zip from somewhere else but i can't remember where but it's also within the RUU itself. Try to find the link for you in a bit.
EDIT: here's a link to someone I know who had a whole tutorial for the a5_ul version of our phone on how to flash back a stock RUU from your computer or from within your ext SD card. Obviously the links with the files aren't valid for our phone but the steps are . Also has instructions for restoring using a TWRP backup but I wouldn't use someone else's TWRP backup if my hair was on fire. Especially since we have access to the pure stock RUU with our version why not take advantage of it. That's all I'm saying.
http://forum.xda-developers.com/desire-816/help/guide-how-to-flash-stock-recovery-ruu-t3308502
And here's the HTC RUU downloads link below
http://www.htc.com/us/support/rom-downloads.html
And lastly a link to a tutorial on extracting the stock recovery from the RUU .
http://androidforums.com/threads/guide-re-flash-stock-rom-ruu-after-bricking-a-rooted-device.565203/
Well not lastly I guess because here is a link to the stock recovery provided by FoxyDrew. Don't use the RUU link it's to kitkat but the recovery link below it is the same for lollipop as it's for the a5_chl
http://forum.xda-developers.com/desire-816/general/ruu-t2952058/post57019175#post57019175
Click to expand...
Click to collapse
My thread has the KitKat and Lollipop RUU, which is the latest one from HTC, and should work fine for his issue
FoxyDrew said:
My thread has the KitKat and Lollipop RUU, which is the latest one from HTC, and should work fine for his issue
Click to expand...
Click to collapse
Cool. You're the man.

HTC 10 - Wiped system - any clever way to re-install stock image?

I hope this is the correct forum to post this...
I have a rooted HTC 10 with TWRP and Magisk.
Things were working up to a point: I was trying to resolve an SD card (microSD) access issue, and carelessly wiped "system" on the phone. I also stupidly didn't get a backup of the system via TWRP before I started mucking around.
When plug in the phone to my laptop via USB, it is still recognized where the internal and SD storage comes up in Windows Explorer, but the phone will not boot. It can boot into TWRP and all of that seems to work fine.
I tried running RUU (.exe) for the stock image from HTC on my Windows 10 laptop (after loading a bunch of Visual C++ redistributables), but it doesn't connect to the phone. I tried leaving the phone in "download mode" and "recovery mode" and just booting the phone and leaving it at the point where just the red text is shown, but the RUU tool would not connect in any case.
I tried to use the "ROM.zip" file, which is extracted when running the RUU (.exe) on Windows, by copying that file to the phone but that didn't work (in TWRP). As a matter of fact, TWRP shows no files when selecting "Install", either ".zip" or ".exe". When using the TWRP file explorer, it sees everything.
I am am very inexperienced with the phone OS and manipulation and just got to root previously via a utility (with some help).
I am pretty sure I have all the correct stuff loaded on this laptop, since I used this laptop to root this phone in the first place. Again, it was seemingly working fine except for the SD card (writing) issue I was trying to resolve.
I am hoping that there is some clever way to either recover the "system" partition data (to stock or whatever) or re-load the stock firmware (which I have from HTC, though it's probably missing some OTA update I would guess). I've read a lot but many articles either assume lots of phone hacking experience or they are missing pieces (because the posters already know a lot): I've exhausted all the options I could come up with.
Thanks for any help!
[edit]
When my HTC is in download mode, it doesn't display the CID. I was going to try to copy system from a stock image elsewhere on this site, but there are several to choose from and I didn't want to do more damage.
On the screen:
*** UNLOCKED ***
*** FUSED ***
htc_pmewl PVT S-ON
LK-1.0.0.0000
[email protected]
Open-DSP-v23.0.8996.00007_1028
OS-3.16.617.2
Jan 2 2018, 18:22:58(1012001)
WintelRob said:
I hope this is the correct forum to post this...
I have a rooted HTC 10 with TWRP and Magisk.
Things were working up to a point: I was trying to resolve an SD card (microSD) access issue, and carelessly wiped "system" on the phone. I also stupidly didn't get a backup of the system via TWRP before I started mucking around.
When plug in the phone to my laptop via USB, it is still recognized where the internal and SD storage comes up in Windows Explorer, but the phone will not boot. It can boot into TWRP and all of that seems to work fine.
I tried running RUU (.exe) for the stock image from HTC on my Windows 10 laptop (after loading a bunch of Visual C++ redistributables), but it doesn't connect to the phone. I tried leaving the phone in "download mode" and "recovery mode" and just booting the phone and leaving it at the point where just the red text is shown, but the RUU tool would not connect in any case.
I tried to use the "ROM.zip" file, which is extracted when running the RUU (.exe) on Windows, by copying that file to the phone but that didn't work (in TWRP). As a matter of fact, TWRP shows no files when selecting "Install", either ".zip" or ".exe". When using the TWRP file explorer, it sees everything.
I am am very inexperienced with the phone OS and manipulation and just got to root previously via a utility (with some help).
I am pretty sure I have all the correct stuff loaded on this laptop, since I used this laptop to root this phone in the first place. Again, it was seemingly working fine except for the SD card (writing) issue I was trying to resolve.
I am hoping that there is some clever way to either recover the "system" partition data (to stock or whatever) or re-load the stock firmware (which I have from HTC, though it's probably missing some OTA update I would guess). I've read a lot but many articles either assume lots of phone hacking experience or they are missing pieces (because the posters already know a lot): I've exhausted all the options I could come up with.
Thanks for any help!
[edit]
When my HTC is in download mode, it doesn't display the CID. I was going to try to copy system from a stock image elsewhere on this site, but there are several to choose from and I didn't want to do more damage.
On the screen:
*** UNLOCKED ***
*** FUSED ***
htc_pmewl PVT S-ON
LK-1.0.0.0000
[email protected]
Open-DSP-v23.0.8996.00007_1028
OS-3.16.617.2
Jan 2 2018, 18:22:58(1012001)
Click to expand...
Click to collapse
Download the 3.16.617 ruu.zip from here, rename the file to 2PS6IMG.zip and copy it to your SDCARD, boot to download mode and flash it.
https://androidfilehost.com/?fid=962157660013070850
Mr Hofs said:
Download the 3.16.617 ruu.zip from here, rename the file to 2PS6IMG.zip and copy it to your SDCARD, boot to download mode and flash it.
Thanks! I will give that a shot today and update this thread.
Click to expand...
Click to collapse
Mr Hofs said:
Download the 3.16.617 ruu.zip from here, rename the file to 2PS6IMG.zip and copy it to your SDCARD, boot to download mode and flash it.
So, the "flash it" part is where noobs like me are not sure what to do. So I have the phone in "download" and the image is on the microSD. I assume "flash it" means to either run adb or fastboot, and either indicates that the device is not found. I thought this was likely due to me wiping the system partition on the phone, not sure if it's using the recovery or the phone itself.
So, on the flash, I have downloaded stock ROMs, like from HTC, but they are all ".exe" files. I finally found a ".zip" that is supposedly stock. I renamed it as suggested and put in on the microSD, and then I used TWRP in recovery to "Install", but it says "Invalid zip file format!".
FYI, I do not have "S-OFF" and the original file I found was named "2PS6IMG_PERFUME_WL_O80_SENSE90GP_MR_NA_Gen_Unlock_3.16.617.2.zip" which I renamed to "2PS6IMG.zip".
Click to expand...
Click to collapse
When you renamed the file properly download mode will automatically confirm to flash the file, no need to do anything other than press volume button and power button to confirm the flash, the yellow text in the bottom is what you need to follow. No need for adb or anything difficult otherwise i would have mentioned it.
Check the file, make sure you don't hide file extensions in windows because when it's named 2PS6IMG.zip.zip it doesn't work.
And put the file on the external sdcard, not internal storage. That doesn't work either. Format the sdcard in twrp if you have to first.
Don't do anything else than what i write, it doesn't work like that. Don't fiddle around with adb or fastboot, you can't flash it in recovery because the zip is an encrypted HTC ruu and NOT a custom rom which are meant to be flashed with a custom recovery.
Make sure to place the file in the *root* of the external sdcard.
branko.s67 said:
Make sure to place the file in the *root* of the external sdcard.
Click to expand...
Click to collapse
That's what i already said twice right ?
Mr Hofs said:
When you renamed the file properly download will automatically confirm to flash the file, no need to do anything other than press volume button and power button to confirm the flash, the yellow text in the bottom is what you need to follow. No need for adb or anything difficult otherwise i would have mentioned it.
Check the file, make sure you don't hide file extensions in windows because when it's names 2PS6IMG.zip.zip it doesn't work.
And put the file on the external sdcard, not internal storage. That doesn't work either. Format the sdcard in twrp if you have to first.
Don't do anything else than what i write, it doesn't work like that.
Click to expand...
Click to collapse
I believe I did everything as you explained. I work with computers and I have a basic and general understanding of this process: I renamed the only ZIP that I could find online, I put it on the microSD, renamed it to "2PS6IMG.zip", I used "Install" from the recovery, then got the zip error.
From you follow-up reply, I realize that you meant for me to put the file 2PS6IMG.zip into the "root" of the microSD (top level of the file structure), whereas I had it in a sub-directory, and then use "download" on the bootloader. So, now I "get" how the "download" option works! I thought that had something to do with downloading from a laptop or computer via adb, but it's obviously "downloading" the ROM from the external microSD card.
So, NOW it is reflashing!!
I know these kinds of noob issues lead to eye-rolling, so thanks for the patient help!
Now I am back to the stock starting point, and I can try a different rooting option to get back to fixing the external SD writing permissions issue I was trying to resolve in the first place!
Mr Hofs said:
That's what i already said twice right ?
Click to expand...
Click to collapse
Just wanted to point out that the file must be placed in the root. Not in a subdirectory.
That was not stated anywhere. That could have been the reason it didn't work for the OP.
WintelRob said:
I believe I did everything as you explained. I work with computers and I have a basic and general understanding of this process: I renamed the only ZIP that I could find online, I put it on the microSD, renamed it to "2PS6IMG.zip", I used "Install" from the recovery, then got the zip error.
From you follow-up reply, I realize that you meant for me to put the file 2PS6IMG.zip into the "root" of the microSD (top level of the file structure), whereas I had it in a sub-directory, and then use "download" on the bootloader. So, now I "get" how the "download" option works! I thought that had something to do with downloading from a laptop or computer via adb, but it's obviously "downloading" the ROM from the external microSD card.
So, NOW it is reflashing!!
I know these kinds of noob issues lead to eye-rolling, so thanks for the patient help!
Now I am back to the stock starting point, and I can try a different rooting option to get back to fixing the external SD writing permissions issue I was trying to resolve in the first place!
Click to expand...
Click to collapse
I never mentioned to put it in a folder anywhere. I write like this so the chance on errors are minimal. It's following to the letter where it goes wrong. Don't try to push it all to hard, read easy and patiently then it will be very simple.
Good thing to know it worked. Back to start.
Cheers
---------- Post added at 06:54 PM ---------- Previous post was at 06:53 PM ----------
branko.s67 said:
Just wanted to point out that the file must be placed in the root. Not in a subdirectory.
That was not stated anywhere. That could have been the reason it didn't work for the OP.
Click to expand...
Click to collapse
I never said to place it in a subfolder. It's the reading where it goes wrong. Following instructions can be difficult ....I know.
Same as going to recovery and try to flash it, flash it via adb or fastboot.....never mentioned that either. It's the haste and maybe a bit of despair that is kicking in but i do this all for a reason.
Cheers.
Mr Hofs said:
That's what i already said twice right
Click to expand...
Click to collapse
So first off, I clicked the "Thanks" button on your original reply.
So I don't seem like a total moron, your original reply just said to copy the file to the SD card: I already had a folder structure on that card and so I moved the file to where I wanted to use it, not realizing at the time how "download" worked and that the "download" would look only in the *root* of the SD card. So, that's why I stated my understanding of what you meant on my follow-up reply. Had I started with a blank SD card, I would have naturally just copied it and it would have been in the root.
Thanks again for the help!
I know this thread is a bit old, but I am in a similar situation. I wish to restore my unlocked HTC 10 to oreo stock. I have tried the tried the RUU (for NA) as listed but when the install is completed I do not have any radio capability. Do I need to completely wipe the internal memory before flashing the RUU? I noticed when I tried my backup restoral using TWRP I ended with with no radio as well. Please advise.

Categories

Resources