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.
Related
I am running my S3 on TMO, with 4.3 booloader & latest modem. I was also running a 4.3.2 TW rom.
This morning, I decided to wipe the rom, then restore it, as it was the one I had in backup. I was having stuttering problems, and thought that because I had added & deleted so much stuff in the past few days, restoring my clean backup would clear it up.
I have the latest TWRP recovery, and wiped the cache & dalvik, then went to restore the rom. But when it finished, and I rebooted, got stuck at the ktoonez (my kernel) logo. I did a battery pull, and went back into recovery, did a full wipe, then tried to restore the rom. This time, 3/4 of the way through, it rebooted on its own, and started to bootloop. When I tried to get back into recovery, it would only boot to the Samsung logo, so I knew that now my recovery was gone. I used Odin on my PC to restore it, but it does the same thing. I do a complete wipe, restore the backup, but it again reboots by itself out of recovery about 3/4 of the way through, then it gets stuck at the kernel logo.
I don't have anything other than the backup stored on the phone. Is there a way that I can load a rom from my PC through recovery so that I can just start over? Or will I probably have to Odin everything back to stock, and start from there (which I've never done from the PC. I have used mobile odin though)?
Update:
I decided to do a odin back to stock. Now though, after setting for a few minutes, it says optimizing apps, goes through it, gets to the little android guy shooting upwards, goes to the Samsung logo, then starts all over again. It just keeps going through it again & again.
anyone?
Did you go into recovery and do a factory reset?
Sent from my SGH-M919 using Tapatalk
serio22 said:
Did you go into recovery and do a factory reset?
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Yes, a couple times.
I have also tried taking the card out the phone and putting it into the pc to manually place the rom on it, then flash it, but my pc wont see the card. It makes the sound that something has been inserted to a usb port, but shows nothing on the computer.
What if you flash a recovery and then a ROM?
Sent from my SGH-M919 using Tapatalk
Kamau54 said:
Update:
I decided to do a odin back to stock. Now though, after setting for a few minutes, it says optimizing apps, goes through it, gets to the little android guy shooting upwards, goes to the Samsung logo, then starts all over again. It just keeps going through it again & again.
Click to expand...
Click to collapse
In TWRP recovery there is an option to sideload a file. Go to Advanced>ADB Sideload. From here you should be able to use the command:
Code:
adb sideload location/of/ROM.zip
This should transfer the ROM to your internal sd card.
You should make sure that your computer detects the phone before the transfer with the command:
Code:
adb devices
It should should return:
Code:
List of devices attached
phone id recovery
If it returns the above, you know you're okay to transfer. If it doesn't show your phone's model, that means that the computer doesn't recognize your phone as being detected (probably driver related); therefore, your file will not transfer with the sideload command.
I saw your post in the S3Rx thread that your computer won't read your sd card either. I'm not sure if you're using Windows/OSX/Linux, but if you're using Windows, you might want to try installing Linux on a USB drive, booting from that, then plugging in your sd card. In the past, I have had success mounting drives on Linux that would not mount on Windows. I know that this is a little more effort than is probably necessary lol. But I'm not nearly as versed as others here. I just like to tinker a little.
I hope you're able to get your phone booting again!
serio22 said:
What if you flash a recovery and then a ROM?
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
The phone doesn't have a rom to start with I don't think. This is what I Odin:
http://www.androidfilehost.com/?fid=23212708291682181
It's the right one, as I have the TMO S3, and I already had it on my phone to begin with. I thought it came with the stock rom included, but when I rebooted, it just gets caught in a bootloop after it says optimizing apps. I can get the recovery back, but I don't know how to get a rom on the card to flash. I even tried to use a old card, but again, my pc won't see it, so I can't put a rom on it to flash.
VolcanicSkunk said:
In TWRP recovery there is an option to sideload a file. Go to Advanced>ADB Sideload. From here you should be able to use the command:
Code:
adb sideload location/of/ROM.zip
This should transfer the ROM to your internal sd card.
You should make sure that your computer detects the phone before the transfer with the command:
Code:
adb devices
It should should return:
Code:
List of devices attached
phone id recovery
If it returns the above, you know you're okay to transfer. If it doesn't show your phone's model, that means that the computer doesn't recognize your phone as being detected (probably driver related); therefore, your file will not transfer with the sideload command.
I saw your post in the S3Rx thread that your computer won't read your sd card either. I'm not sure if you're using Windows/OSX/Linux, but if you're using Windows, you might want to try installing Linux on a USB drive, booting from that, then plugging in your sd card. In the past, I have had success mounting drives on Linux that would not mount on Windows. I know that this is a little more effort than is probably necessary lol. But I'm not nearly as versed as others here. I just like to tinker a little.
I hope you're able to get your phone booting again!
Click to expand...
Click to collapse
I am on a windows, and have only used the command prompt once a couple years ago, so my experience with it is limited.
But when I tried the command "adb devices", I got an error message saying that it was not a recognized command .
Also, What is Linux? If it is bigger than a couple gigs, then I don't have any place to put it.
Kamau54 said:
I am on a windows, and have only used the command prompt once a couple years ago, so my experience with it is limited.
But when I tried the command "adb devices", I got an error message saying that it was not a recognized command .
Also, What is Linux? If it is bigger than a couple gigs, then I don't have any place to put it.
Click to expand...
Click to collapse
The reason you get the "adb is not a recognized command" is because you don't have the Android Software Development Kit (SDK) installed. The SDK contains an executable command called Android Debug Bridge (adb). You can download and install it from the developer.android.com website. But chances are, you aren't going to have the drivers installed for your computer to recognize your phone in recovery if you don't have the SDK already installed.
If you aren't familiar with Linux, then I would say that going with that route is far more work than you're likely to want to put in to get your phone functioning.
If you'd like to try it though:
Linux is free to use, it is designed and compiled by several different companies. The more well known are: Ubuntu, Mint, Red Hat, and Backtrack. There are many more.
You can visit any of those sites, download the software, and install it on a USB drive. It usually requires a 4GB USB drive. Instructions to install it to a USB drive are usually listed on the site.
After installing it, you can boot your computer from the USB and use Linux like a fully functioning OS right from the USB drive. You won't be required to install it.
You can then try downloading the ROM while on Linux and transferring it to your sd card.
Sidenote:
Linux is an open source operating system on which Android is based. That is why Android is open source, it is ruled by the same GNU General Public License that governs Linux.
VolcanicSkunk said:
The reason you get the "adb is not a recognized command" is because you don't have the Android Software Development Kit (SDK) installed. The SDK contains an executable command called Android Debug Bridge (adb). You can download and install it from the developer.android.com website. But chances are, you aren't going to have the drivers installed for your computer to recognize your phone in recovery if you don't have the SDK already installed.
If you aren't familiar with Linux, then I would say that going with that route is far more work than you're likely to want to put in to get your phone functioning.
If you'd like to try it though:
Linux is free to use, it is designed and compiled by several different companies. The more well known are: Ubuntu, Mint, Red Hat, and Backtrack. There are many more.
You can visit any of those sites, download the software, and install it on a USB drive. It usually requires a 4GB USB drive. Instructions to install it to a USB drive are usually listed on the site.
After installing it, you can boot your computer from the USB and use Linux like a fully functioning OS right from the USB drive. You won't be required to install it.
You can then try downloading the ROM while on Linux and transferring it to your sd card.
Sidenote:
Linux is an open source operating system on which Android is based. That is why Android is open source, it is ruled by the same GNU General Public License that governs Linux.
Click to expand...
Click to collapse
Sounds like I'm screwed then. I don't know why my pc is not seeing it now, because it always sees it when I'm copying files from & to it.
Kamau54 said:
Sounds like I'm screwed then. I don't know why my pc is not seeing it now, because it always sees it when I'm copying files from & to it.
Click to expand...
Click to collapse
Have you tried going to your computer's device manager and seeing if it's picking it up, but just has an error?
VolcanicSkunk said:
Have you tried going to your computer's device manager and seeing if it's picking it up, but just has an error?
Click to expand...
Click to collapse
When I insert it, and go to that, it shows up as removable disk E, but when I double click on it, it says to insert a disk into removable disk E. I think whats happening is that it's seeing the adapter, but not the card that's in it.
Kamau54 said:
When I insert it, and go to that, it shows up as removable disk E, but when I double click on it, it says to insert a disk into removable disk E. I think whats happening is that it's seeing the adapter, but not the card that's in it.
Click to expand...
Click to collapse
When you right-click on the E:/ do you have the option to format the drive? If so, you may want to try formatting it. That may fix your issue. Hopefully you don't have anything on the external sd that you can't put back on it.
VolcanicSkunk said:
When you right-click on the E:/ do you have the option to format the drive? If so, you may want to try formatting it. That may fix your issue. Hopefully you don't have anything on the external sd that you can't put back on it.
Click to expand...
Click to collapse
When I try that, it tells me there's no disk in drive E, to insert a disk and try again.
VolcanicSkunk said:
Have you tried going to your computer's device manager and seeing if it's picking it up, but just has an error?
Click to expand...
Click to collapse
This happened to me to after I installed the latest s3rx Rom...I haven't been able to recover my data or get anything to read my card.
After researching online a lot of people have had success running the chkdsk command... check it out here
http://www.ehow.com/how_7233441_restore-damaged-memory-stick-data.html
Ok, under Device Manager, the computer does see the phone as "MTP". I tried the troubleshooting process, and it went all the way through its thing, but at the end it said "failed" trying to install drivers. I just installed the proper drivers earlier today from Samsung, so I know they are correct. Also, this is as I am connected to the phone, not the card reader. The phone itself is flashing the Samsung logo, and that's as far as it has gone.
This is so frustrating because all I need to do is to get a rom onto the card. If I can get that, I can get into recovery and straighten this all out.
Anyone else with any ideas? I'm beginning to go a bit nuts thinking I have lost my phone just because I can't get a rom placed on my card.
Flash twrp or cwm, they have options to mount SD card, after that you can copy the zip and flash
Sent from my SGH-M919 using Tapatalk
serio22 said:
Flash twrp or cwm, they have options to mount SD card, after that you can copy the zip and flash
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
I have the latest twrp, and have seen that option. You mean, I can copy from the pc to the card, because that's what I need to do.
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
Hello!
I think I did something exceptionally stupid. I already had a rooted phone, and was attempting to update the modem via the flashable to H811 20i files on TWRP; but had the bootloader also downloaded and accidentally flashed that in haste. Now the screen is black/nothing turns on/leds etc, and windows reads it as "QHSUSB__BULK" when connected. I do have the *kdz file if there is a way that can be managed to flash it (as LGUP will not recognize it).
Read around googling, but it seems a bit more on the LG 2/3 side of things in unbricking. Would anyone know a way to unbrick it, or am I proper screwed? (Am still reading what I find over, but am making sure I don't mess things up even more by making in post in case there is a way)
Thank you very much for any help!
[email protected] said:
Hello!
I think I did something exceptionally stupid. I already had a rooted phone, and was attempting to update the modem via the flashable to H811 20i files on TWRP; but had the bootloader also downloaded and accidentally flashed that in haste. Now the screen is black/nothing turns on/leds etc, and windows reads it as "QHSUSB__BULK" when connected. I do have the *kdz file if there is a way that can be managed to flash it (as LGUP will not recognize it).
Read around googling, but it seems a bit more on the LG 2/3 side of things in unbricking. Would anyone know a way to unbrick it, or am I proper screwed? (Am still reading what I find over, but am making sure I don't mess things up even more by making in post in case there is a way)
Thank you very much for any help!
Click to expand...
Click to collapse
It is hard bricked but fixable search the threads here and you should be able to find the fix
TheMadScientist said:
It is hard bricked but fixable search the threads here and you should be able to find the fix
Click to expand...
Click to collapse
Yup! Thanks! Just found the thread that I was going to attempt! (LG G4 H811 Complete Unbrick Guide - 100% Working) but before I could, it now lists the device from "QHSUSB__BULK" to "Unknown Device" (On both laptop and desktop), another new problem. Gonna try reinstalling the drivers and cleaning the contacts.
*edit*
Reinstalling the drivers at least went from "QHSUSB__BULK" to "Qualcomm HS-USB QDLoader 9008 (COM3)", so that's a good direction. Just waiting for the SD card to finish low-level formatting.
*edit #2*
Huzzah!! It worked!
Alrightly @madscientist! Not sure if I should make a new thread or not, but properly unbricked it now (which is darned great) now have a new strange issue w/ flashing custom roms.
>Have restored it to H81120o_00_0613
>For some odd reason, the bootloader was already unlocked after unbricking
>Did the normal process of flashing/booting into TWRP that worked fine (USB Debugging/OEM Unlock, then used ADB to fastboot to recovery)
>Flashing UPDATE-SuperSU-v2.48.zip is successful, but makes it bootloop on the T-Mobile logo.
>ANY custom roms I attempt to copy over to the internal memory gives me this error: "Cannot copy item: The device either stopped responding or has been disconnected" but copying over files like Gapps or Magisk work fine (anything but roms basically). If I copy custom roms to either a microsd or internal memory outside recovery, makes both not readable within TWRP, but if I delete them all files internal/in microsd can be read again.
Not sure what to do, because do not wanna brick it again by accident (so am being a bit extra cautious). Any help would be greatly appreciated!
Whi[email protected] said:
Alrightly @madscientist! Not sure if I should make a new thread or not, but properly unbricked it now (which is darned great) now have a new strange issue w/ flashing custom roms.
>Have restored it to H81120o_00_0613
>For some odd reason, the bootloader was already unlocked after unbricking
>Did the normal process of flashing/booting into TWRP that worked fine (USB Debugging/OEM Unlock, then used ADB to fastboot to recovery)
>Flashing UPDATE-SuperSU-v2.48.zip is successful, but makes it bootloop on the T-Mobile logo.
>ANY custom roms I attempt to copy over to the internal memory gives me this error: "Cannot copy item: The device either stopped responding or has been disconnected" but copying over files like Gapps or Magisk work fine (anything but roms basically). If I copy custom roms to either a microsd or internal memory outside recovery, makes both not readable within TWRP, but if I delete them all files internal/in microsd can be read again.
Not sure what to do, because do not wanna brick it again by accident (so am being a bit extra cautious). Any help would be greatly appreciated!
Click to expand...
Click to collapse
make sure the sd card is formatted fat 32
TheMadScientist said:
make sure the sd card is formatted fat 32
Click to expand...
Click to collapse
Yup! It is. I had to make sure it was FAT32 or else the unbrick wouldn't have worked.
Also, it let me flash "LG-G4-H811-20V-Stock-Debloated-Rooted" completely fine, but again, anything custom not at all.
[email protected] said:
Yup! It is. I had to make sure it was FAT32 or else the unbrick wouldn't have worked.
Also, it let me flash "LG-G4-H811-20V-Stock-Debloated-Rooted" completely fine, but again, anything custom not at all.
Click to expand...
Click to collapse
I had the sprint varient so I dont know there. Maybe flashing with wrong kernel or modem
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.
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.