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.
Related
Hi folks,
I tried to modify the platform.xml file to enable some write permissions. As far as I can tell, the app I used to modify the file didn't write it back correctly, and now my device is what might be called "semi-bricked."
Almost everything force closes, WiFi and write permissions seem to be broken, and I can't seem to get my Galaxy Nexus to communicate with my PC via USB.
I tried booting into CWM and mounting some /system, but I'm not sure how to access it since fastboot/adb don't seem to recognize the device.
I've also booted into some sort of recovery (fastboot?) that looks like the attached image. But I can't get it to do anything except boot up into the normal OS when I click the power button.
Any suggestions on how I can get access back to my device so I can repair/replace the platform.xml file and restore functionality to my phone?
Thank you very much!
Deozaan said:
Hi folks,
I tried to modify the platform.xml file to enable some write permissions. As far as I can tell, the app I used to modify the file didn't write it back correctly, and now my device is what might be called "semi-bricked."
Almost everything force closes, WiFi and write permissions seem to be broken, and I can't seem to get my Galaxy Nexus to communicate with my PC via USB.
I tried booting into CWM and mounting some /system, but I'm not sure how to access it since fastboot/adb don't seem to recognize the device.
I've also booted into some sort of recovery (fastboot?) that looks like the attached image. But I can't get it to do anything except boot up into the normal OS when I click the power button.
Click to expand...
Click to collapse
No it is not bootloader. to access to the bootloader turn on your device long pressing power, volume up and volume down buttons together (don't use odin).
To access to cwm recovery from bootloader just press volume down button until you see "recovery" option, then press power button and it will boot in recovery.
which rom are you using?
solution: download the zip file of your rom and extract the file you modified, make a zip (if you can't make a flashable zip i'll post an attachment for you) and flash it in recovery
enryea123 said:
No it is not bootloader. to access to the bootloader turn on your device long pressing power, volume up and volume down buttons together (don't use odin).
To access to cwm recovery from bootloader just press volume down button until you see "recovery" option, then press power button and it will boot in recovery.
which rom are you using?
solution: download the zip file of your rom and extract the file you modified, make a zip (if you can't make a flashable zip i'll post an attachment for you) and flash it in recovery
Click to expand...
Click to collapse
Thanks for the reply.
I actually did manage to get my PC to recognize the device via USB/adb and I copied the file back to the way it should have been. But that didn't fix anything, so I ended up doing a wipe/factory reset. Everything works now but things still seem a bit. . . off. For instance, it takes a while after my phone boots up before the WiFi will actually connect. It used to be connected almost immediately. And it takes a while for the alarm icon to load/show up in the notification area at the top. And I can't find the option in the settings anymore to use USB debugging. There are lots of little things like that, where it works, but it just doesn't quite work like it used to. . .
And to answer your question, I'm using the stock ROM that came with the Galaxy Nexus (from Google Play Store).
Deozaan said:
Thanks for the reply.
I actually did manage to get my PC to recognize the device via USB/adb and I copied the file back to the way it should have been. But that didn't fix anything, so I ended up doing a wipe/factory reset. Everything works now but things still seem a bit. . . off. For instance, it takes a while after my phone boots up before the WiFi will actually connect. It used to be connected almost immediately. And it takes a while for the alarm icon to load/show up in the notification area at the top. And I can't find the option in the settings anymore to use USB debugging. There are lots of little things like that, where it works, but it just doesn't quite work like it used to. . .
And to answer your question, I'm using the stock ROM that came with the Galaxy Nexus (from Google Play Store).
Click to expand...
Click to collapse
first: to make the "developer settings" appear go settings/About phone and tap on build number 7 times (google has hidden it in 4.2).
said that, you can:
1) fix permissions in cwm recovery (under advanced menu)
2) download a zip of your rom and flash it in recovery
3) if your bootloader is unlocked (you see a padlock when you boot your phone) you can flash a factory image to return completely stock.
4) if your bootloader is locked you can follow the 3) method but you will lose all your sdcard data.
enryea123 said:
first: to make the "developer settings" appear go settings/About phone and tap on build number 7 times (google has hidden it in 4.2).
said that, you can:
1) fix permissions in cwm recovery (under advanced menu)
2) download a zip of your rom and flash it in recovery
3) if your bootloader is unlocked (you see a padlock when you boot your phone) you can flash a factory image to return completely stock.
4) if your bootloader is locked you can follow the 3) method but you will lose all your sdcard data.
Click to expand...
Click to collapse
Thanks again for the response.
I got developer settings to appear. Hooray! Fix Permissions is one of the first things I did to try to repair the platform.xml file when things were broken. I ran it again (but from ROM Manager rather than from CWM Recovery) and it didn't seem to have any effect on the weird sluggishness when first booting up.
My bootloader is unlocked. Will I have to root again if I flash one of those factory images? I'm currently backing up the contents of my "SD card" in case I have to completely wipe the entire thing.
Deozaan said:
Thanks again for the response.
I got developer settings to appear. Hooray! Fix Permissions is one of the first things I did to try to repair the platform.xml file when things were broken. I ran it again (but from ROM Manager rather than from CWM Recovery) and it didn't seem to have any effect on the weird sluggishness when first booting up.
My bootloader is unlocked. Will I have to root again if I flash one of those factory images? I'm currently backing up the contents of my "SD card" in case I have to completely wipe the entire thing.
Click to expand...
Click to collapse
well, you can firstly try to flash a zip of your rom (search on xda or google), it should fix.
the fastboot flash method is the google method so you won't need root (you just have to go into fastboot and connect your phone to your computer, doesn't matter if you have root, or a different rom/kernel/recovery).
If you don't know you to flash from fastboot try first to flash the rom zip.
having a backup of the sdcard is always a good idea :good:, i have 2 backups of mysdcard on 2 different hard drives of my computer and the pictures i take with the camera are automatically uploaded on my dropbox .
enryea123 said:
well, you can firstly try to flash a zip of your rom (search on xda or google), it should fix.
the fastboot flash method is the google method so you won't need root (you just have to go into fastboot and connect your phone to your computer, doesn't matter if you have root, or a different rom/kernel/recovery).
If you don't know you to flash from fastboot try first to flash the rom zip.
Click to expand...
Click to collapse
Weird things are happening. I was making a backup of the "SD Card" and partway through, things stopped copying over. And pretty much everything got erased from it. No big deal, since I'd already copied the important stuff first.
But CWM Recovery won't flash the zip file. It keeps telling me the update failed. I verified the hash on the zip I downloaded and it is the same as what is listed on Google's site. But it just won't flash in CWM.
Deozaan said:
Weird things are happening. I was making a backup of the "SD Card" and partway through, things stopped copying over. And pretty much everything got erased from it. No big deal, since I'd already copied the important stuff first.
But CWM Recovery won't flash the zip file. It keeps telling me the update failed. I verified the hash on the zip I downloaded and it is the same as what is listed on Google's site. But it just won't flash in CWM.
Click to expand...
Click to collapse
wait, are you in cwm recovery o just in stock recovery (they are different)? have you previously installed a cwm recovery using fastboot? which zip are you trying to flash?
edit: ok you know what is rom manager so i think that you are in cwm.
edit2: try this zip http://goo.im/devs/bigxie/maguro/bigxie_maguro_OTA_JOP40D-signed.zip
enryea123 said:
wait, are you in cwm recovery o just in stock recovery (they are different)? have you previously installed a cwm recovery using fastboot? which zip are you trying to flash?
edit: ok you know what is rom manager so i think that you are in cwm.
edit2: try this zip
Click to expand...
Click to collapse
I was in CWM Recovery. I was using the zip file that I extracted from the link you gave me for Google's stock ROMs (I can't post external links yet):
(Factory Images "takju" for Galaxy Nexus "maguro" (GSM/HSPA+) (with Google Wallet) --> Android 4.2.1 (JOP40D))
Strangely enough, after "failing" to flash the zip, I had to log into my Google account again because I had selected the option to Wipe Data and Cache, and most things seem to be working very well again. One odd thing I'm still noticing, though, is that some things don't seem to be syncing properly. For example, if I archive some of my email in the Gmail app, then log into Gmail on my PC, the mail is still unread in my inbox. My phone downloads the new mail just fine. But the changes I make on my phone (reading, archiving, deleting, etc.) don't seem to be syncing to anywhere else.
I'm downloading the zip you suggested. I'll give that a try. Thanks!
enryea123 said:
edit2: try this zip http://goo.im/devs/bigxie/maguro/bigxie_maguro_OTA_JOP40D-signed.zip
Click to expand...
Click to collapse
Try this one
Deozaan said:
I was in CWM Recovery. I was using the zip file that I extracted from here the link you gave me (I can't post external links yet):
(Factory Images "takju" for Galaxy Nexus "maguro" (GSM/HSPA+) (with Google Wallet) --> Android 4.2.1 (JOP40D))
Strangely enough, after "failing" to flash the zip, I had to log into my Google account again because I had selected the option to Wipe Data and Cache, and most things seem to be working very well again. One odd thing I'm still noticing, though, is that some things don't seem to be syncing properly. For example, if I archive some of my email in the Gmail app, then log into Gmail on my PC, the mail is still unread in my inbox. My phone downloads the new mail just fine. But the changes I make on my phone (reading, archiving, deleting, etc.) don't seem to be syncing to anywhere else.
I'm downloading the zip you suggested. I'll give that a try. Thanks!
Click to expand...
Click to collapse
That is not a flashable zip! It is a factory image, it must be flashed via fastboot using a computer.
enryea123 said:
That is not a flashable zip! It is a factory image, it must be flashed via fastboot using a computer.
Click to expand...
Click to collapse
Just to be sure I explained myself clearly, I downloaded that Google provided factory image (a .tgz file) and inside it I found a zip file named "image-takju-jop40d.zip" which is what I tried to flash.
That said, I've just recently finished downloading the one you just suggested to me and I will give that one a try soon. Thank you again for your help. I really appreciate it.
I got it working again. The ROM you gave me failed signature verification in CWM Recovery, but I told it to install anyway and it worked. Thank you.
The problem I was having with Gmail not syncing was that I used Titanium Backup to restore my data, but because all the data from my "SD card" got erased, Titanium Backup itself lots its settings, so my Device ID was different. I guess Gmail relies on the device ID for syncing.
Thank you so much for your help! I learned a lot from the experience.
Glad i helped you. well this is one of the reasons why i don't restore data with titanium (especially system data).
and by the way:
Deozaan said:
Just to be sure I explained myself clearly, I downloaded that Google provided factory image (a .tgz file) and inside it I found a zip file named "image-takju-jop40d.zip" which is what I tried to flash.
That said, I've just recently finished downloading the one you just suggested to me and I will give that one a try soon. Thank you again for your help. I really appreciate it.
Click to expand...
Click to collapse
To fully reset and install a clean rom using fastboot you have to extract the bootloader-blabla.img and radio-blabla.img files from the tar.gz archive and then extract the 4 .img files inside the zip (that is inside the tar.gz) and flash this 6 .img files connetting your phone in bootloader mode to your computer and using fastboot in terminal (in fact this procedure reinstall the recovery too).
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: !!
After spending hours upon hours reading through this forum I still haven't found a proper answer, so I am sorry if I start a thread that has been already answered somewhere else.
My phone apparently got a virus and it acts crazy: blocks on the start screen (the one that says HTC) and when I finally get it to start (through resetting to factory setting)s it starts to give me the message "People has stopped unexpectedly" over and over and over again.
It is locked
Has S-ON
CiD htc_Y13
So far I downloaded the fastboot
The RUU
The recovery image from here http://forum.xda-developers.com/htc-one-m8/general/guide-restore-european-htc-one-m8-to-t3072235
But I run into problems when I try to extract the rom.exe
And reading through the comments some people say that that method might end up bricking the device.
Can anyone give me a straight forward solution?
All I need to do is Return my phone to stock so that I can finally use it again
Thanks!
Flashing an RUU will format and restore all your phone's partitions to stock HTC condition - you'll lose all data, except your sd card.
1. Download the latest RUU file (in zip format) (6.12.401.4) from the link below:
https://www.androidfilehost.com/?fid=24369303960687057
2. Rename the file to:
0P6BIMG.zip
Note: The first character is zero, and make sure you don't rename it to 0P6BIMG.zip.zip
3. Put the file in the root directory of your sd card.
4. Boot into bootloader and follow the instructions to flash the ruu.
5. Enjoy
Thanks for the reply
shirreer said:
Flashing an RUU will format and restore all your phone's partitions to stock HTC condition - you'll lose all data, except your sd card.
1. Download the latest RUU file (in zip format) (6.12.401.4) from the link below:
2. Rename the file to:
0P6BIMG.zip
Note: The first character is zero, and make sure you don't rename it to 0P6BIMG.zip.zip
3. Put the file in the root directory of your sd card.
4. Boot into bootloader and follow the instructions to flash the ruu.
5. Enjoy
Click to expand...
Click to collapse
I get the following message when I tried this option :
Cancel Update!
Device halted due to large image update fail
Press Power to reboot
I also get wrong zipped image circa half way in the procedure
I guess you either have a corrupt download, file-system errors on your sd card or PC's hard disk, or you tried to flash the zip file from ADB.
Also, you can simply hard-reset your phone and start fresh. Then you can OTA up to 6.12.
Otherwise, if you want to flash the RUU, do this first:
1. Check your SD for errors and fix them.
2. Check your PC's hard disk for errors and fix them.
3. Download the file again and start over.
4. Follow my instructions to the letter.
5. Give us feedback
Thanks a million!!!!
shirreer said:
I guess you either have a corrupt download, file-system errors on your sd card or PC's hard disk, or you tried to flash the zip file from ADB.
Also, you can simply hard-reset your phone and start fresh. Then you can OTA up to 6.12.
Otherwise, if you want to flash the RUU, do this first:
1. Check your SD for errors and fix them.
2. Check your PC's hard disk for errors and fix them.
3. Download the file again and start over.
4. Follow my instructions to the letter.
5. Give us feedback
Click to expand...
Click to collapse
Thanks a million
All I had to do is FORMAT the SD and go through the process again. It worked like a charm- Thanks again Shirreer
You're very welcome. Glad I could help.
Cheers
So I followed this thread https://forum.xda-developers.com/one-m9/general/guide-root-install-twrp-htc-one-m9-t3061133
All was going fine, after finishing rooting and rebooting the phone went straight to download mode and at the bottom it says "File /mnt/media_rw\ext_sd\0PJAIMG.ZIP FILE NOT FOUND" and it is now stuck in the reboot loop with the screen only displaying the logo and the message "this build is for development purposes only...."
I then tried this thread https://forum.xda-developers.com/showthread.php?t=1996665 to recover from it, but the links needed were down.
So I went into the recovery mode and tried to restore, but found that there was nothing to restore from. Then I rebooted it and now I'm not able to go into the recovery mode "failed to boot to recovery mode". Also adb will no longer display my device after trying the command "adb devices".
Tried uninstalling and installing the drivers, but no luck.
Horagino said:
So I followed this thread https://forum.xda-developers.com/one-m9/general/guide-root-install-twrp-htc-one-m9-t3061133
All was going fine, after finishing rooting and rebooting the phone went straight to download mode and at the bottom it says "File /mnt/media_rw\ext_sd\0PJAIMG.ZIP FILE NOT FOUND" and it is now stuck in the reboot loop with the screen only displaying the logo and the message "this build is for development purposes only...."
I then tried this thread https://forum.xda-developers.com/showthread.php?t=1996665 to recover from it, but the links needed were down.
So I went into the recovery mode and tried to restore, but found that there was nothing to restore from. Then I rebooted it and now I'm not able to go into the recovery mode "failed to boot to recovery mode". Also adb will no longer display my device after trying the command "adb devices".
Tried uninstalling and installing the drivers, but no luck.
Click to expand...
Click to collapse
Okay, so first of all you're using old threads to guide you and in the latter case, a guide build for another model phone. Assuming you are using an HTC One M9, your one-stop resource is the readme thread in this forum.
It sounds like you're going to need a RUU for your device. Before you ask ANYTHING about that, read the readme thread. It answers most every common question (and many uncommon ones), provides guides, and has links.
Once you've read the thread, if you have questions, post them here. We're absolutely happy to help - the readme thread ensures that we all start from the same level of understanding.
computerslayer said:
Okay, so first of all you're using old threads to guide you and in the latter case, a guide build for another model phone. Assuming you are using an HTC One M9, your one-stop resource is the readme thread in this forum.
It sounds like you're going to need a RUU for your device. Before you ask ANYTHING about that, read the readme thread. It answers most every common question (and many uncommon ones), provides guides, and has links.
Once you've read the thread, if you have questions, post them here. We're absolutely happy to help - the readme thread ensures that we all start from the same level of understanding.
Click to expand...
Click to collapse
Hi there, thanks for the reply. I have checked out the thread and I'm trying to follow the instructions in the RUU section, however I'm bit stuck. The third step requires me to copy the file into the SD Card, but I unfortunately have no direct access to that sd card with my PC. And like I said I cannot really use my phone to copy that file, nor can I use adb to copy it, since it doesn't detect my phone, although fastboot does.
You will need a pc to recover your phone in any circumstances. No pc = no recovered phone.
Beamed in by telepathy.
shivadow said:
You will need a pc to recover your phone in any circumstances. No pc = no recovered phone.
Beamed in by telepathy.
Click to expand...
Click to collapse
Not quite sure what you mean by pc, or if I explained it poorly. I do have a computer, but my computer does not have slots for sd cards, hence why I can't put any files on there, and adb won't detect my phone any more.
@edit: I think I know why I goofed up, the sd card I was using is 2GB only, and so I can't even use the RUU provided in the link above, since it is 2.2GB. I will shortly get a new sd card and see how it goes from there. Although if there is a way of doing this without the sd card and just my PC, I'm happy to hear it.
Horagino said:
Not quite sure what you mean by pc, or if I explained it poorly. I do have a computer, but my computer does not have slots for sd cards, hence why I can't put any files on there, and adb won't detect my phone any more.
@edit: I think I know why I goofed up, the sd card I was using is 2GB only, and so I can't even use the RUU provided in the link above, since it is 2.2GB. I will shortly get a new sd card and see how it goes from there. Although if there is a way of doing this without the sd card and just my PC, I'm happy to hear it.
Click to expand...
Click to collapse
There is no easier way to move forward than using a computer (PC, not a Mac). Yes, you could use another device to copy the RUU file to a SD card, but the guides are written with a computer in mind.
Like I said I DO have a PC, it's what I'm using to view and write this thread. My question is, is there a way to execute the RUU file from the PC to the Phone via the usb cable? Since my SD card is too small for that file. The guide says that it is theoretically possible that do it through HTC_fastboot, however it warns that there have been to many problems, so I don't want to risk it, since my phone also has the security features on.
Horagino said:
Like I said I DO have a PC, it's what I'm using to view and write this thread. My question is, is there a way to execute the RUU file from the PC to the Phone via the usb cable? Since my SD card is too small for that file. The guide says that it is theoretically possible that do it through HTC_fastboot, however it warns that there have been to many problems, so I don't want to risk it, since my phone also has the security features on.
Click to expand...
Click to collapse
Yes it's possible. The readme thread doesn't explore how because there are so many different ways a PC-to-phone flash can fail, where as the SD card method is dead simple.
You need a pc to transfer any updates or files to internal memory.
As you said, your memory card is too small for that file. Your other choices are to flash from pc, copy files from pc to phone, copy files from internet to phone.
If the phone doesn't boot to os then your only option is adb. You need a pc to use adb. You will need to access the phones recovery for adb too.
You can get another memory card but if your phone wont boot to os you'll need a pc for adb as your pc doesn't have sd slots.
So basically, you need a pc unless you know some voodoo or something to magic the file onto the phone..
Beamed in by telepathy.
I got a new sd card, 16gb. I also put the file on it using adb commands "adb push C:\adb\0PJAIMG.zip /sdcard" and using the rather broken recovery mode of TWRP I was able to confirm that the file is on there. However, step 5 says that I should be asked if I want to flash the file after booting to download mode, well... That is not happening
Tried installing it via TWRP recovery, however it says that the ZIP file is corrupted somehow.
So I just redownloaded the RUU file, it still says it is corrupted. Any clues as to how to fix it?
Nevermind, fixed it by using another phone to format the sd card and download the file straight to the sd card, then I could follow the instructions without a problem.
I however have one more question, how can I root my phone without going through all this sh** again?
Horagino said:
I however have one more question, how can I root my phone without going through all this sh** again?
Click to expand...
Click to collapse
The readme thread has a section on rooting. Be sure you pay attention to the guide's directions about versions - some versions of SuperSU are incompatible with the M9 and certain versions of TWRP correspond to your firmware version.
Congratulations on getting your phone functioning. Always nice to hear a success story.
If you have marshmallow 6.0 and a gsm phone just:
1, unlock your bootloader via htcdev.com.
2, Flash twrp and mount as "read only" (seems to be version dependent, i used 2.9.0.1 for 6.0 and have no issues to date).
3, make a backup of everything except data (or just system, up to you), you WILL need it one day so make a copy and store it somewhere very, very safe as it is your only fallback.
4, in twrp mount system as read/write and flash chainfires supersu.zip (like twrp, it seems to be version dependent. I used supersu 2.65 for 6.0 and have no issues to date). (use systemless root if asked, not sure if an actual system root is any good for this phone?).
5, buy s-off via sunshine app for $25. This is essential if you want a reasonable chance of recovery should anything go drastically wrong later on. Being able to flash unsigned stuff gives an extra option towards recovery.
It's not too difficult once you get the hang of it, I was panicking too when I did mine. Rightly so, these things brick too easy!. I implore you to cross reference the steps against other material from other xda members just incase I missed something by accident. The last thing you need to do is bugger it up now but I'm confident I have it pretty damn close.
Beamed in by telepathy.
I decided to flash a different ROM; Android HD revolution. Everything went fine and everything works fine.
However, I do have one more question. Whenever I go into the download mode, I still get this message in yellow at the bottom of the screen "File /mnt/media_rw\ext_sd\0PJAIMG.ZIP FILE NOT FOUND", not sure if it's a left over from previous failures or if I'm missing something.
Hey everyone,
this is my first forum post on the xda website so I'll try to create an effective post as best I can.
Objective: Attempting to return to out-of-the-box stock android after using a custom ROM, LineageOS. I mainly want to return it to a condition where I would be able to hand it back to the carrier. It's also much more convenient for me to use the phone in stock. From my understanding, this is possible without much difficulty.
Issue: After many days of searching forums and following guides specific to the phone's model, I've put myself in a confusing position. The phone's current state is as follows: Installed OS[None], Bootloader[Relocked], S-ON[True], Boot to Recovery[Unsuccessful], SIM Card[None]. I'm unable to detect the phone on my computer(running Windows 10), and therefore can't utilize adb commands.
If anyone has any advice or guidance I would really appreciate it; and if you need me to provide any more information I would be happy to. I'll also try to respond as quickly as I can. Thanks!
jamcmich said:
Hey everyone,
this is my first forum post on the xda website so I'll try to create an effective post as best I can.
Objective: Attempting to return to out-of-the-box stock android after using a custom ROM, LineageOS. I mainly want to return it to a condition where I would be able to hand it back to the carrier. It's also much more convenient for me to use the phone in stock. From my understanding, this is possible without much difficulty.
Issue: After many days of searching forums and following guides specific to the phone's model, I've put myself in a confusing position. The phone's current state is as follows: Installed OS[None], Bootloader[Relocked], S-ON[True], Boot to Recovery[Unsuccessful], SIM Card[None]. I'm unable to detect the phone on my computer(running Windows 10), and therefore can't utilize adb commands.
If anyone has any advice or guidance I would really appreciate it; and if you need me to provide any more information I would be happy to. I'll also try to respond as quickly as I can. Thanks!
Click to expand...
Click to collapse
What is your CID/MID and software version? Just use an ruu for your device that's at your current firmware version or higher. Put it on the root of your sd card and run from download mode.
Tarima said:
What is your CID/MID and software version? Just use an ruu for your device that's at your current firmware version or higher. Put it on the root of your sd card and run from download mode.
Click to expand...
Click to collapse
I only have access to the CID(TMOBO10) and software version(2.51.531.32).
I've attempted to use an RUU, although after many attempts I couldn't get past the application setup screen. After the progress bar finished installing the RUU, it would close and never prompt me for anything else. I tried it multiple times.
I don't have a SIM/SD to use, unfortunately.
TWRP was installed as my Recovery, although trying to access it returns a boot-loop.
In terms of using adb, my phone will charge if plugged into the computer but it's not being recognized for file transfers.
I'm gathering that the only option left is to use something like a SIM card as you mentioned?
jamcmich said:
I only have access to the CID(TMOBO10) and software version(2.51.531.32).
I've attempted to use an RUU, although after many attempts I couldn't get past the application setup screen. After the progress bar finished installing the RUU, it would close and never prompt me for anything else. I tried it multiple times.
I don't have a SIM/SD to use, unfortunately.
TWRP was installed as my Recovery, although trying to access it returns a boot-loop.
In terms of using adb, my phone will charge if plugged into the computer but it's not being recognized for file transfers.
I'm gathering that the only option left is to use something like a SIM card as you mentioned?
Click to expand...
Click to collapse
You could troubleshoot your RUU issue, it should work if you have a windows computer. Try googling it. Unfortunately I can't help you much there, it's always worked fine on my machine.
Else, yea, the SD card method also works well. Find an ruu zip version first before trying to find an SD card. The ruu.exe you tried using won't work in this method.
Hi.
PC method
As @Tarima has mentioned the RUU is not running because of a Windows/PC issue.
Your best option is to try and run it in another computer or a friend's computer.
You can put your phone to download mode (volume down+power)
And run RUU again. Here is a link just to make sure you have the correct RUU. It is for your CID and its 2.51.531.32
https://androidfilehost.com/?fid=746010030569947237
For microSD card method
Use a friend's microSD card. It will need to be formatted to FAT32. So backup the microSD card data. Hehe!
To create an installable zip for that RUU, you again need a good computer.
Here is how you can get the installable zip from the RUU since it is encrypted you just cant extract it.
Download this decryption tool from here https://forum.xda-developers.com/chef-central/android/tool-universal-htc-ruu-rom-decryption-t3382928
Choose 32bit or 64bit as this is vital to its working. Also make sure dotnet framework 3.5 is installed on your machine or else this tool will not run.
Once decryption tool is ready to run, just drag and drop the RUU on top of HTC_Decrypt_Tool.exe
It will give you some options. From these say yes (Y) to get new keyfiles AND to create installable sdcard zip file. you will know it when you see.
All other options such as uploading new keyfiles to community and getting boot.img and system.img is optional.
Once you get the zip rename it to 2PS6IMG.zip if it already isnt renamed.
Transfer to the root of your microSD card (dont put in any folders, just put it direcly on microsdcard)
Put microSD card into the your htc 10.
Enter download mode (volume down+power)
Download mode should detect the zip file. Press volume up to install.
If you need anymore help please post back again
jamcmich said:
I only have access to the CID(TMOBO10) and software version(2.51.531.32).
I've attempted to use an RUU, although after many attempts I couldn't get past the application setup screen. After the progress bar finished installing the RUU, it would close and never prompt me for anything else. I tried it multiple times.
I don't have a SIM/SD to use, unfortunately.
TWRP was installed as my Recovery, although trying to access it returns a boot-loop.
In terms of using adb, my phone will charge if plugged into the computer but it's not being recognized for file transfers.
I'm gathering that the only option left is to use something like a SIM card as you mentioned?
Click to expand...
Click to collapse
ayyu3m said:
Hi.
PC method
As @Tarima has mentioned the RUU is not running because of a Windows/PC issue.
Your best option is to try and run it in another computer or a friend's computer.
You can put your phone to download mode (volume down+power)
And run RUU again. Here is a link just to make sure you have the correct RUU. It is for your CID and its 2.51.531.32
https://androidfilehost.com/?fid=746010030569947237
For microSD card method
Use a friend's microSD card. It will need to be formatted to FAT32. So backup the microSD card data. Hehe!
To create an installable zip for that RUU, you again need a good computer.
Here is how you can get the installable zip from the RUU since it is encrypted you just cant extract it.
Download this decryption tool from here https://forum.xda-developers.com/chef-central/android/tool-universal-htc-ruu-rom-decryption-t3382928
Choose 32bit or 64bit as this is vital to its working. Also make sure dotnet framework 3.5 is installed on your machine or else this tool will not run.
Once decryption tool is ready to run, just drag and drop the RUU on top of HTC_Decrypt_Tool.exe
It will give you some options. From these say yes (Y) to get new keyfiles AND to create installable sdcard zip file. you will know it when you see.
All other options such as uploading new keyfiles to community and getting boot.img and system.img is optional.
Once you get the zip rename it to 2PS6IMG.zip if it already isnt renamed.
Transfer to the root of your microSD card (dont put in any folders, just put it direcly on microsdcard)
Put microSD card into the your htc 10.
Enter download mode (volume down+power)
Download mode should detect the zip file. Press volume up to install.
If you need anymore help please post back again
Click to expand...
Click to collapse
Thanks for the helpful information. I'll try everything and give feedback regarding how it goes.