Related
hey guys,
once every serveal months i check for updates for my rom, my recovery, and some apps.
yesterday i wanted to update tp the latest recovery (1.52)
now, the phone connected, driver was installed correctly (windows 7 32-bit)
i used the adb commands as posted in the recovery topic.
now it updated it, but after a few minutes using and wiping the phone, the usb-connection will not come to live (in any way, not even a "unknown device") and when the phone booted it gave a message: "SD removed, please place sd-card." while it has a 8 gb on there. luckily i backed up all data i needed from the sd before i flashed. so i used recovery to recreate partitions and wipe sd. but nothing works anymore... when i select ANY option in recovery wich needs SD access it immediatly gives errors.
also tried a nother microsd of 1 gb which did also not work...
about the usb-connection, it also does not work in Recovery.
but in the bootloader, it installs without any problems the well known "My HTC" device. using fastboot to boot to recovery image works, but again: no usb connection
please guys... help me... without sd-card i find my phone completely useless. (because of many documents and pictures for my work.)
I've had this problem and I had to send my Hero for repair, but it could be difficult if you have custom software in there, thry to flash original rom. Not sure though if it can be done through fast boot.
Also if you have to send it back, pretend to be an idiot and say it just went wrong. "I didn't do anything" could work.
Use fastboot to revert to a stock ROM (update.zip)
This sounds very similar to this issue on Modaco - http://android.modaco.com/content-page/299174/no-adb-no-sd/
Still ongoing, as I (pulser) am trying to guide the OP through making the goldcard (need to find another android phone to do this) and then we need to try an RUU somehow???
adwinp said:
Use fastboot to revert to a stock ROM (update.zip)
Click to expand...
Click to collapse
ok, and how?
thanks for reply.
i was thinking of letting it be repaired, but as you all say, unlocked spl, recovery image, custom rom. it does not look so good when they disver that.
but i am a stupid guy, so pretending to be stupid should be easy for me
If you are just interested in getting it back to stock for returning under guarantee to HTC, here is what I would suggest.
(No guarantees, as I haven't had to try this, and won't, for obvious reasons)
Get the stock RUU file from the hero that you have. I would recommend the oldest one that is available for you. (eg. a 1.73 one).
DISCONNECT your phone, and run the exe file(Yes, sounds strange, but bear with me).
Wait till the splash screen for the RUU is up, asking you to accept the EULA etc.
Now browse in my computer to your temp directory (C:\Users\Username\AppData\Temp in Vista/7, C:\Documents And Settings\Username\Application Data\temp in XP)
Sort the folders/files by date modified, and the most recently modified (or one of the most recently modified) folder should contain the RUU stuff. Inside a subfolder is a file called rom.zip. Copy this file to the desktop or another safe place. Once file is copied, close the RUU.
Now get your phone plugged in and booted into fastboot. (hold back + power)
Then use the command
Code:
fastboot flashall C:\Users\Username\Desktop\rom.zip
No guarantees, but it should get you back to the stock recovery, system and boot (NOT HBOOT or SPL, the actual boot.img that android uses to boot the kernel)
can i also flash custom rom with fastboot? to test if something is wrong with the rom?
That would depend on what version of SPL/HBOOT you have. If it is security off, then maybe. Otherwise I doubt it. You usually need an original, HTC signed file to flash using that method.
Feel free to give it a go, but I don't think it would work.
Hello!
I've changed digitizer but now it doesn't react on any touch. I tried to make GoldCard, but I can't enter to menu to change connection to debug mode. There is any other solution to make the GoldCard?
Thx for help.
haller said:
Hello!
I've changed digitizer but now it doesn't react on any touch. I tried to make GoldCard, but I can't enter to menu to change connection to debug mode. There is any other solution to make the GoldCard?
Thx for help.
Click to expand...
Click to collapse
Hi, did you solve the problem? I have the exact same problem.
If you have, please let me know how.
jocke888 said:
Hi, did you solve the problem? I have the exact same problem.
If you have, please let me know how.
Click to expand...
Click to collapse
I have had the same problem with the screen and the debugging, I did however find a kind of workaround for the debugging issue.
I searched for hours and hours for posts on how to enable debugging via ADB command line. The bottom line is that you can't. When I say you I mean "us plebs" can't. I have read the arguments about security and I say cool fair enough. I also noticed that when you run the RUU with the phone connected via USB the RUU activates "USB Debugging" on the handset irrespective of if it was enabled via the handset menu. I can understand this is done for obvious reasons as the RUU is supposed to be an easy way for end users to update their ROM's. It does however beg the question of how a stock ROM can alter the USB debugging switch on the phone via software/usb interface and the rest of the internet claims it is not possible via ADB/command line. Anyone who seems to ask about it is immediately suspected of being a phone thief and the forum responses become a mud slinging match.
So I did some experimenting with the HTC Wildfire S:
Basically I ran the RUU and left it on the Readme page running in the background I could then access the handset via ADB. I don't know ADB well but I was able to see the device listed using adb devices where as before I got nothing. When in Fastboot mode I saw that the handset was also receiving data via the Console on the PC using the fastboot reboot type commands.
It didn't really help me too much as all I wanted to do was update the stock ROM to see if it resolved my touchscreen issue. Unfortunately it didn't. So I'm still stuck with a fully functional handset minus the touchscreen.
I then decided to try and unlock the bootloader so that I could try with a custom ROM. Following the process on HTCdev I got a "Radio" update for the handset. At first I couldn't load it because the base ROM was too old. I found the latest update. It failed with a USB connection error. I found an older version about halfway back between what I had (X.1.33.X) and the new (X.2.16.X) this was (X.1.66.X). It worked but the "Radio" update still needed the latest version. I re-ran the latest RUU and it failed with the same error.
Determined to get it done here is what I did:
1. Re-Ran the (X.2.16.X) Installer
2. At Readme screen I navigated to the standard %TEMP% directory (it helps if u empty this first then you will see the dir the install creates easily)
3. I copied the entire contents to a folder on my desktop
4. Closed the (X.2.16.X) Installer and re-ran the (X.1.66.X) Installer
5. At the Readme screen I navigated back to the %TEMP% directory (it helps if u empty this first then you will see the dir the install creates easily)
6. I pasted and replaced all the files back. Now you get a lot of failures because the Intaller is runnning so I just skipped those files.
7. Went back to the installer running in the background and completed the process.
I used the older installer to flash the newer ROM. I have no idea which files (apart from the rom.zip) were critical but if you copy only the rom.zip it fails on the device when checking the security certificates.
After that I successfully flashed the "Radio" update. The next step in the HTCdev process is to get a device ID via a Flashboot command. I still couldn't do this because the touchscreen still wasn't working after the update. So I Re-Ran the (X.1.66.X) Installer and left it in the background. The phone went into debug mode and I could run the command. I got the info and completed the process with HTCdev. This gave me a unique file to unlock the boot loader.
I then used the same method to get into debug mode and used the HTC Wildfire S All-In-One Toolkit (http://forum.xda-developers.com/showthread.php?t=1809751) to unlock the bootloader with the file HTC sent me.
I now have an HTC Wildfire S with the latest stock ROM, Bootloader unlocked and still no working touchscreen. This took me the better part of 10 hours. When I have the energy to continue I'll try a installing Root and custom ROM.
I apologise in advance for the RUU version number above being severely shortened but they have so many versions of the RUU depending on where you are and who your provider is and such, you will need to do your own research on the specific RUU's you will need and where to get them. The method to get debug I have illustrated should not change if you use a different version of RUU. If you're lucky your stock ROM is also updated and you can skip that part or the RUU you do download works without the tweaking l had to do.
jocke888 said:
Hi, did you solve the problem? I have the exact same problem.
If you have, please let me know how.
Click to expand...
Click to collapse
You have to install a custom recovery (CMW). If you enter recovery mode you can choose mounts and storage, and then mount USB storage. This way you enable usb mass storage. now you are able to get your CID
HI all. I am in serious need of help please.
My wifes M9 is stuck on a screen with only a backlight. How this came about is after several failed attempts of updating the system via Wi-Fi. South Africa does not have a RUU available and only over the air updates are available
After about 2 days on the net, searching and reading and trying and failing I have determined the following.
What I have tried
1. Boot to Bootloader and tried recovery. This give me an Error - "Failed to boot to recovery"
2. Tried a Official RUU from HTC, this failed due to CID - Error wrong Customer ID
3. Learned a bit of ADB but this is no use as It seems USB debugging is disabled on the phone
4. Tried Custom ROM's via the SD card but this is blocked as the phone is **Locked** and **S-On**
5. Fastboot sees the phone as I can push reboot commands but because of locked status I can not do much
6. I can not get a unlock token as OEM is locked and this must be unlocked for ADB command to get token to get unlock.bin from HTCDEV
Basically it seems like I am at a dead end as it appears that I need to get into a boot status to enable debugging and enable developer mode from phone settings to be able to work from ADB
So here is the Million dollar question, How can I "wipe" the phone with a SD card boot image/loader or does any one know of a RUU-.exe for South Africa CID_016 that I could flash the phone with or possibly any other methods to get a ROM on it that we can use it again
I repeat, phone goes to blank screen with only backlight after HTC Logo, S-on, USB debugging seems to be disabled and it is in Locked status. I am able to boot in download mode and bootloader and fastboor does see the device. ADB devices does not see the phone, even after trying loads of different drivers, ADB USB ADB Interface etc etc
Please I need help
I'm suffering from the same fate. Except I had rooted it before, then I tried to update it to 5.1 and I relocked my bootloader. Android 5.1 loaded successfully but it got stuck while booting and now I can't unlock my bootloader. I have tried EVERYTHING!
https://www.google.com/url?q=https:...261000&usg=AFQjCNEBlBxkVmymaiJO1eaxKcHsKsE-wg
1.download this zip file
2. Rename the file to 0PJAIMG.zip (zero not O)
03. Copy the file to the root directory of a SD card which is formatted to fat32
04. Put the card into your phone and boot to Download Mode.
05. You will be asked whether you want to flash the file. Confirm with the volume up button.
06. Your phone will reboot at least one time. Depending on your current firmware version it may reboot to Android instead of rebooting to Download Mode. If this happens you just need to shut your phone down and manually boot it to Download Mode.
07. Flashing may take some time.
08. At the end you will be asked to push the power button. You phone will shut down if you do so.
09. Wait some seconds and then turn your phone on, again.
10. First boot may take a while.
11. Congrats! thanks to flippy
YES!!! OP I tried this and it works!!! My phone is finally alive again thanks to flippy's instructions.
Maybe I missed it, but I spent an entire day yesterday trying to find THIS solution. I didn't know it was this particular one, but I would have tried it first if I could have found it somewhere obvious. It really should be stickied as a "How to unscrew what though hast screwed"!
Thank you so much for taking the time to answer this Degerli43! I know virtually every answer possible is available on this forum, but finding it is the trick!
Note to anybody else doing this, be sure to locate the correct image file for your provider and area, as the link above and the one below may not be the correct one for you. I am a T-Mobile US customer and used this one -
https://www.androidfilehost.com/?w=...6ce7fb817fc1524b58f67fe05270f032107d2306abcd4
This worked perfectly after I could not boot or enter TWRP recovery. Anybody who can still access Android Recovery the Downloader should be able to use it to get un-bricked to a clean carrier state if the image file will take.
ksnax said:
Maybe I missed it, but I spent an entire day yesterday trying to find THIS solution. I didn't know it was this particular one, but I would have tried it first if I could have found it somewhere obvious. It really should be stickied as a "How to unscrew what though hast screwed"!
Click to expand...
Click to collapse
Did you ever visit the general section? :silly: There's a sticky thread with stock files and linked instructions for recovering TWRP backups and flashing RUUs. Read the OP, follow it's instructions to my google sheet and you will see where the steps that helped you out are taken from.
Sent from my HTC One S using XDA Labs
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.