Develop Bugs

Dead USB port and MicroSD slot

So today, I was upgrading from modaco 2.7 to 2.7.1,
after the upgrade (using recover mode and the signed zip file (core chinese)), I did a system wipe and reboot the device with the USB still plugged in my PC, and everything seems to be normal until my pc's tray notification pops up with the "unknown device found" message - i thought it was a little bit odd, so then I waited for the hero to boot up completely - it reboots after showing the HTC logo once, and then it boots normally to the setup wizard (select language, etc);
I then followed the normal procedure of typing all the wifi, flickr, gmail stuff in, and when i got into Rosie, it shows a notification icon on the hero saying "SD Card removed". I can't access the SD card, nor my pc can recognize the hero. I ejected the SDCard and re-insert it but it's not detected either. HTC Sync on the device does not give a notification nor the mass storage notification shows up either.
I tried rebooting into recovery mode, (Hero 1.2.3) and i can see the menus just fine; however, when i try to mount SD card as usb, or flash update.zip or any zip, or fix ext3, or clear dalvik-cache or wipe the sdcard's ext partition, it keeps giving me errors saying
error: run 'whateverprogram' in terminal
when i try to set 'USB Mass storage on', it says "Error enabling USB mass storage! Run ums_enable manually from console.
I then try to login the device using adb shell through window's command prompt, it says device not found as well.
giving up, i tried to reboot teh device into fastboot mode, the PC recognizes the USB device just fine. it's really odd.
Anyway I can do a recovery on this to make these device work again?
p.s. when i try to choose zip file in recovery mode, it says
Code:
"E: Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory)
Can't mount sdcard, aborting".
after every reboot (shutdown, start), the setup wizard shows up again as if I have not written anything on my device after any setup.
I can't download anything to run on the Hero as it requires the SD card. I can't flash any recovery images either as again it requires the SD card.
Any ideas??? I'm left with a half-brick now

Update1: using ConnectBot I can login my own device using root,
it shows the following when i run df -h:
Code:
/dev/block/mtdblock3 1700M 157.3M 12.7M 93% /system
/dev/block/mtdblock5 165.8MB 12.8M 152.9M 8% /data
/dev/block/mtdblock4 130.0M 1.2M 128.8M 1% /cache

kazuni,
Can you read SD card in your PC?
Several persons reported problems with SD card after upgrading to modaco 2.7 or 2.7.1. They have to format SD card.

Al936 said:
kazuni,
Can you read SD card in your PC?
Several persons reported problems with SD card after upgrading to modaco 2.7 or 2.7.1. They have to format SD card.
Click to expand...
Click to collapse
Thanks for the quick reply.
I have tried doing so, in fact, i have 4 SD cards to try and none of them are readable in the Hero; they are readable using a card reader in my PC though.

kazuni said:
Thanks for the quick reply.
I have tried doing so, in fact, i have 4 SD cards to try and none of them are readable in the Hero; they are readable using a card reader in my PC though.
Click to expand...
Click to collapse
Update2: the only way that my pc can detect my device as "My HTC" is when i boot it into fastboot mode; unfortuantely there are no way for me to update the device in this mode, so i can't do anything to modify the rom, or to check it using dropbear or any shell client. =\
C:\Documents and Settings\user>fastboot devices
HT97RL900725 fastboot
it sees it just fine.
I wonder if the goldcard method + fastboot update will work or not; let me give it a shot and try to flash it back to 405.5 first ;\
update3: can't. fastboot update is still locked for any rom type.

damn man. its freaking. i am not going to update to 2.7.1 untill this issue is resolved.

still no go.
im left with a half-bricked device that:
1) clean wiped, normal boot, cannot detect SD card nor the Hero is detectable by XP.
2) clean wiped, recovery mode, can't run any of the script except :
Reboot System Now
Wipe data/factory reset
Fix apk uid mismatches
Fix rotate
3) can't download anythign from browser as it needs to save onto sd card.
4) android market doesn't have flashrec so i can't reinstall the recovery image.

wget ftp://myhost/system.img /data/
flash_image system /data/system.img
hope this works

When you are in the shell check out the file /proc/cmdline.
Would be interresting to see if the HBOOT send a command line to the kernel to disable the SD card.

packetlss said:
When you are in the shell check out the file /proc/cmdline.
Would be interresting to see if the HBOOT send a command line to the kernel to disable the SD card.
Click to expand...
Click to collapse
can't. It doesn't even boot into normal mode, nor boot loop. it just holds at the HERO logo.

I think I have the same problem, i can charge my phone but trying to mount my phone to either my pc or mac it just won't be picked up

tried using RUU with a goldcard, no go. remote not allowed (fastboot flash system system_rel.img, nor fastboot boot boot.img or fastboot flash boot boot.img. no go. sigh.)
now i have a brick :\
wonder if there is any way to go into fastboot mode and flash ANY part of the blocks (device, recovery, or system, if at all).

Some progress: using hboot mode, i placed HEROIMG.zip into the sdcard and it loads successfully. it works! and im now rolled back to official 2.7.405.5; however, the USB and the sd card is still dead ;\

I guess I'll be bringing it back to HTC to see if they would do anything about it (fortunately It's now back to stock recovery and 2.74.405.5)

I managed to do the same thing, i'm hoping the tmobile will replace my phone

hi all,
I am having the same issue... what I don't understand is: it has to be a software problem, because, from what I've read, everyone of us have been installing radio and firmware updates to the htc hero, and since some of these updates the USB and sdcard mounting is not properly working... I believe it's not possible to break a USB port just by installing software...
so there should be a way to fix this other than sending the phones back... If anyone has any suggestion I can try it on my phone
cheers : )

I know it's weird! Funny thing is, official updates includes radio + recovery + pretty much every part of the rom is being re-flashed (including hboot, from what i understand); how ever, ONLY in hboot mode, the device is recognized properly as "Android USB" by windows.

Some of your problems I had to. To be exact: that my pc wouldn't recognize the phone when connected with usb except for fastboot and charging.
For weeks I searched and found some people with similar problems, but never a solution.
I had no problems with my sdcard however.
Now my problem is gone. How? I had the HTC Generic 2.73.405.5 ROM (pre-rooted and packaged as update.zip by MoDaCo) and decided to update to Paul's ROM v2.5.
After I was finished with the installation wizard and connected the phone with usb to my pc everything suddenly worked again!!!
So I got the usb and HTC Sync notification at the top of the screen and can mount the sdcard using the notification bar.
This tells me that in my case it definately wasn't a hardware problem as I always thought, but a software one.
I hope you can something with my experiences because I know how frustrating it is when this doesn't work!

dennis333 said:
Some of your problems I had to. To be exact: that my pc wouldn't recognize the phone when connected with usb except for fastboot and charging.
For weeks I searched and found some people with similar problems, but never a solution.
I had no problems with my sdcard however.
Now my problem is gone. How? I had the HTC Generic 2.73.405.5 ROM (pre-rooted and packaged as update.zip by MoDaCo) and decided to update to Paul's ROM v2.5.
After I was finished with the installation wizard and connected the phone with usb to my pc everything suddenly worked again!!!
So I got the usb and HTC Sync notification at the top of the screen and can mount the sdcard using the notification bar.
This tells me that in my case it definately wasn't a hardware problem as I always thought, but a software one.
I hope you can something with my experiences because I know how frustrating it is when this doesn't work!
Click to expand...
Click to collapse
I tried this but it didn't seem to work for me, so I just put the official rom update and sent the phone back to my network saying that it was broken, now i've gotta wait for another 2-3 weeks to get my phone back , but i'm hoping they'll give me a new phone as i did kinda drop it and there two scuff marks on it

hello dennis333,
today I tried going from 2.8 to the HTC generic ROM you told, and then to 2.5. no results.
I also installed the official HTC / Orange Rom update, which I have now. It has improved a bit because now when I plug the USB cable the PC detects something, but it does'nt work... it says 'unknown device' (tried this on two computers)
when I boot to fastboot ( BACK + POWER BTN ) my computer detects Hero ok (My Htc)
I really don't know what else to try...
I saw another post from someone who had the exact same problem and got it fixed by installing SPL and ROM from fastboot menu
http://forum.xda-developers.com/showthread.php?t=556038
I tried it too, but when trying to use the SPL zip file he says I get an error ( I guess it's because he has a T-Mobile and I have an Orange Hero)
[update]: I finally got the SPL to flash correctly and then installed a modaco 2.8 ROM, but I still cannot connect the Htc Hero to the PC via USB.
regards

[Q] Bricked KF, no ROM, possibly corrupt /sdcard

I've done so much research on this and tried so many things and now I'm so confused on what to do.
I'm trying to bring this KF back from the dead. It was stuck in a bootloop, no computer would recognize it. So I soldered a factory cable..that made my computer actually see the KF.
After that I used the KFU to install TWRP and FFF. It's currently in fastboot mode. I have managed to get it into ADB a few times. Everytime I do that I get an "ACK" error.
I'm attaching a screenshot of an older verson of KFU and of my device manager as well as my .ini file. I added a line in my .ini file which you will see.
I have tried using most of the fastboot commands to reboot it into "normal" mode but it doesn't seem like it does anything.
Currently it's on the Kindle Fire boot screen (it's white & blue) and says v1.4a in the upper right corner. I've uninstalled/reinstalled drivers many times. Maybe I'm doing something wrong there.
I also tried the Kindle Fire Unbrick Utility with no luck. At this point I can't get into TWRP. I tried to mount the SD card in there last night so I could copy update.zip over but it threw an error. Something like E: /sdcard could not mount.
I have also had Clockwork recovery installed and I tried to mount the sd card in there. Similar error. Am I wrong in believing if TWRP was working I should be able to ADB in from there?
I feel like I've done a lot of research and tried very hard before making a thread..so any ideas at this point are very welcome!
Edit: It actually does boot into clockwork recovery at this point. The exact error is: E:Can't mount /sdcard

To mount your sdcard:
Boot into recovery and enter...
Code:
adb shell
echo /dev/block/mmcblk0p12 > /sys/devices/platform/usb_mass_storage/lun0/file[CODE]
And if you have to, format your sdcard FAT32 block size 4096
Obviously, by formatting your sdcard, you will lose all the data that's on it.

I need to keep rebooting/messing around until it's in ADB mode to do that correct? Or will it work in fastboot mode?

You can't use adb in fastboot.

I still can't get it in ADB mode again.. I tried ubuntu as well with no success..should I be using the factory boot cable at this point? Or should I just keep telling it to boot into "normal" (adb) mode and hope it does that one of these times? I wish I could just get the drive to show up in windows..
edit: I guess I had misunderstood before. I selected recovery mode in KFU (option 3) and then ran the stuff you told me to. this was the result: error: device not found and: the system cannot find the path specified

The factory cable probably won't do you much good.
In Ubuntu, did you install drivers and set up udev rules for adb? And are you using 32 or 64 bit?

Sorry I didn't post that earlier, I'm using windows vista- 32 bit. In ubuntu I simply used firekit. No other configuration was done. I did the jumper trick & it claimed it re-wrote the file system but it appears it didn't touch it. It did install an older version of TWRP & FFF.
I'm not completely convinced it has ever made it into ADB, everytime KFU claims it's online my internet connection is completely lost & that's where I get the ACK error.
I guess one thing I'm very unclear about- is it possible adb was completely removed? It certainly seems like it. It should load adb from the FFF screen, correct?
Just an FYI I got the kindle like this so please don't think I'm a complete moron!

Is your Ubuntu on a LiveUSB or full install? If it is a LiveUSB did you set it up with any persistence?

It is a live cd, and no- I didn't set it up with any persistence. I wouldn't be opposed to installing ubuntu if needed. I also have access to Osx (hackintosh) on the same machine, it's dual booting windows/osx.
Thanks for all your help.

do you have an 8 gig usb drive?

legojerry said:
It is a live cd, and no- I didn't set it up with any persistence. I wouldn't be opposed to installing ubuntu if needed. I also have access to Osx (hackintosh) on the same machine, it's dual booting windows/osx.
Thanks for all your help.
Click to expand...
Click to collapse
OSX should do. Get it booted up and PM me.

Nada, I'm headed to walmart now to get one though..lol

If you have OSX, there should be no need for LiveUSB.

Okay. PM was sent.

Format SD card
I Bricked, looped, KF. Resisted far too long just formatting the SD card and starting over. At some point that is likely your only option. Rebuilding your KF , rooting , and ROMing. Partial fixes cxan be frustrating as well.

Sadly I can't get the sdcard formatted..

legojerry said:
Sadly I can't get the sdcard formatted..
Click to expand...
Click to collapse
Wont mount? Your the second one this week. I have done both methods factory/data reset including sdcard contents and factory/ data reset wiped sd as well in twrp the only worked fine for me only thing is my sdcard is now known as removable storage on my computer. Theres got to be a way to get that card mounted to the system or unmounted and mounted to the pc for formating

I wish I could just see the file system from my computer..nothing, and TWRP errors out.

yeah I have been working with someone else on a the same issue with no avail
---------- Post added at 05:37 PM ---------- Previous post was at 05:35 PM ----------
Im wondering if the battery wasnt unplugged and replugged if it would force it to mount either way shutting down the system maybe windows would be able to grasp it for formatting my only fear with that is it might hand you the system partition instead

Interesting idea.. I just tried that, windows detected it- now it's showing an unknown device and it's sitting at the FFF bootloader.
edit: just tried it again, it went straight into fastboot.

Koop's One-Hour Guide To Update Your Phone

I wanted to update my phone from Software version/Baseband version PF4 to the latest Software and Baseband version PG1, but I wanted to KEEP EVERYTHING ELSE. All my apps, my ROM and my Kernel. I was able to do this in less than one hour by following these steps.
Necessary files first:
1) ODIN file. You want to have a folder with the Odin .exe and other files somewhere convenient, your desktop is fine.
2) Latest TAR file available. Currently, that is PF4. The file should end in .md5.
3) Latest CF-Auto-Root. The file should end in .md5.
4) Latest Recovery (TWRP) TAR file. The file should end in .tar.
All of these are available from thread here: http://forum.xda-developers.com/spr...uide-links-files-update-root-restore-t3366862
All Put the PF4, the CF-Auto-Root and the TWRP file in the folder where Odin is.
For convenience, I also recommend installing Minimal ADB. Grab that here: http://forum.xda-developers.com/showthread.php?t=2317790
Install the Minimal ADB. Run that and make sure that it sees your phone. Plug your phone in and type "ADB devices." Look at your phone and accept the security prompt if that comes up.
Once you have Minimal ADB installed the commands that you will use are "ADB Reboot Download" and "ADB Reboot Recovery." These just simplify things.
Is your phone Rooted with TWRP Recovery? Great, we can get started! If not, open ODIN. Flash CF-Auto-Root to get your phone rooted. Then flash the TWRP TAR file. And then you are ready to begin.
Make sure that you have Developer options selected and OEM unlock selected. Really. Make sure. Otherwise you will get the FRP lock.
1) From ADB, type "ADB Reboot Recovery." This should take you to TWRP. If it doesn't read up ^^^^ because you missed a step.
2) In TWRP, go to Backup. This should be the default but if not select Boot, System and Data. Make that backup, which will get stored in TWRP/Backups on your phone. Within that folder, you will see a folder with a long name with lots of numbers and letters that identifies that this backup is for your phone. I generally copy the whole Backup folder to my PC, just in case my phone gets totally wiped I can still restore it. It takes a few minutes and better safe than sorry. Backup done, you can go to the next step.
3) In ADB, type the command to put your file into Download mode. ("ADB reboot download.") Start ODIN. Click on the AP button and select the PF4 file. Let it load, it takes a while. Then click start. This will take few minutes, maybe 10, then your phone will restart back to stock. Again you are going to have to wait for a bit.
4) Let your phone finish rebooting. Once done, you can go to Settings -> System Update -> Download updates manually. You should have an update to PG1 available. Install that and again, your phone will reboot. Once that is done, check your Software version/Baseband version and they should both say PG1.
5) Again, use ADB to send your phone back to download mode and back to Odin. Select the CF-Auto-Root and Start. This should go much faster.
6) Back to Download mode and Odin one last time. Select the TWRP file and start.
7) In ADB, type "ADB reboot recovery".If you have done everything right, you should now be in TWRP.
8) I like to get rid of any bloat that may have been installed with the Stock. I go into Wipe and do both a Factory reset and then in Advanced wipe Caches, System and Data. Then go back to the TWRP main screen WITHOUT REBOOTING.
9) Click Restore and restore the backup that you did at the beginning.
Your phone is now updated to the latest Software and Baseband versions but with all your apps and data as it was before you started.
This literally took me 45 minutes today and that only because of the long rebooting times.
Have fun!

So I always have a space issue with this. I don't have enough free space on my device to hold a backup.
Do you know if there's any way to backup to an external/usb device. I have one of the micro USB to female USB adapters...and I can see the USB drive connected while in the phone, but I don't see an option to use that as a backup destination from TWRP.
Is there a way to backup off the device?
Sent from my SM-G920P using XDA-Developers mobile app

Saafir said:
Mount the USB OTG then you should be able to backup too it
Click to expand...
Click to collapse
I thought I tried that. Ill try again.
Going off the top of my head, if I remember right, it said that the external drive was non-writable.
Is there a specific partition type the USB drive had to be (fat32, ext4, etc) or is there a specific process that I need to follow to mount the drive in TWRP?
Sent from my SM-G920P using XDA-Developers mobile app

Alright. I tried again this morning. The problem is, when I go into mount the USB in TWRP, it does nothing. I can't check it off. I've tried with 2 different USB sticks and I cant get it to work. When the phone is booted to system, I can see the USB, read/write without any problems.

hotwired34 said:
Alright. I tried again this morning. The problem is, when I go into mount the USB in TWRP, it does nothing. I can't check it off. I've tried with 2 different USB sticks and I cant get it to work. When the phone is booted to system, I can see the USB, read/write without any problems.
Click to expand...
Click to collapse
I just tested and OTG seems to be working fine for me.
I went into TWRP, selected Mount, selected USB Storage. Tapped on Select Storage (same screen) and selected USB Storage. (Did you miss this last step?)
I don't know what to tell you beyond the old "It works on my computer/phone."
Are you sure that you are using the right version of TWRP? From here: https://dl.twrp.me/zerofltespr/

koop1955 said:
I just tested and OTG seems to be working fine for me.
I went into TWRP, selected Mount, selected USB Storage. Tapped on Select Storage (same screen) and selected USB Storage. (Did you miss this last step?)
I don't know what to tell you beyond the old "It works on my computer/phone."
Are you sure that you are using the right version of TWRP? From here: https://dl.twrp.me/zerofltespr/
Click to expand...
Click to collapse
I have the right version of TWRP. It might be my otg cable. It's one of the cheap ones. I think I got a 3 pack for something like $0.99.
I was able to use the cable from within the phone and do a full Titanium backup. It's not going to be 100% like your method, but at least my apps and data will be preserved (for the most part). I probably have enough space to do the backup of system and boot, then just restore the apps with data.
Thanks for your help!

5x Hard Bricked??

I think I've done goofed my nexus.
Yesterday, I made a backup of my phone, and then booted it up. Everything was working fine prior to the backup, but as soon as I booted it after making the backup, it got stuck on the google logo. I tried restarting it several times, but it's just been stuck in a bootloop ever since. I've tried numerous things, like formatting it, flashing factory images, and so on, but it turns out fastboot won't detect my device. ADB detects my device fine, but only in recovery. As far as I know, I don't have usb debugging enabled (since I formatted it). It currently has no OS since I formatted it. I've tried installing stock android since formatting it but it still gets stuck in a bootloop.
All my drivers are correct (I've re-installed them probably 10 times by now), and the images aren't corrupted (as far as I know).
I've run out of ideas, as I've been trying to figure this out for the past 2 days with no success. Any help would be appreciated.

I've had a similar issue a couple times after doing something stupid (ADB or FASTBOOT could not detect the phone). The fix was to look in Windows Device Manager and make sure the phone really was detected and a driver installed. Windows would say that it could not find a driver but telling it to install manually did the trick..... as I recall there were a couple driver choices, so it might be trieal and error. Might not be the issue in your case since it does sound like the hardware has a problem, but worth looking into?
Paul

pgoelz said:
I've had a similar issue a couple times after doing something stupid (ADB or FASTBOOT could not detect the phone). The fix was to look in Windows Device Manager and make sure the phone really was detected and a driver installed. Windows would say that it could not find a driver but telling it to install manually did the trick..... as I recall there were a couple driver choices, so it might be trieal and error. Might not be the issue in your case since it does sound like the hardware has a problem, but worth looking into?
Paul
Click to expand...
Click to collapse
I've re-installed the drivers a couple of times now, and it doesn't seem to be fixing the problem.
I don't think it's a hardware problem, because I don't see what making a backup would do to the hardware of the phone (of course, I don't really know much about the hardware, so I might be wrong.) Thanks for the help, though!

ItsMason said:
I've re-installed the drivers a couple of times now, and it doesn't seem to be fixing the problem.
I don't think it's a hardware problem, because I don't see what making a backup would do to the hardware of the phone (of course, I don't really know much about the hardware, so I might be wrong.) Thanks for the help, though!
Click to expand...
Click to collapse
Hi, since you're communicating with the device via ADB and can boot to recovery, I'm pretty sure you can still do something about it. I've had this issue and I can recommend starting to read up on Ubuntu or some type of Linux with a decent user interface. It's easier for starters.
You see, if you don't detect the device via the 'fastboot devices' command, then you have one of two big problems:
a) drivers are messed up - it implies you uninstall everything from Device Manager related to ADB / Bootloader interface. After that, shut off the phone, connect your type-c usb cable, boot up the phone into bootloader and let it install the drivers again (I didn't have much success with this but I read others have. Worth a try)
b) something messed up deeper, as in device permissions. When I had the issue, I used Mint (a Debian distribution) and installed all the drivers via the command line there. After that, when I ran fastboot devices, I got something. It was my lost N5x showing with 'no permissions' and no serial ID. I ran 'sudo fastboot devices' and lo' and behold, I saw the device. After that, I just used sudo fastboot flash recovery/system/etc with it and that was it.

exige34 said:
Hi, since you're communicating with the device via ADB and can boot to recovery, I'm pretty sure you can still do something about it. I've had this issue and I can recommend starting to read up on Ubuntu or some type of Linux with a decent user interface. It's easier for starters.
You see, if you don't detect the device via the 'fastboot devices' command, then you have one of two big problems:
a) drivers are messed up - it implies you uninstall everything from Device Manager related to ADB / Bootloader interface. After that, shut off the phone, connect your type-c usb cable, boot up the phone into bootloader and let it install the drivers again (I didn't have much success with this but I read others have. Worth a try)
b) something messed up deeper, as in device permissions. When I had the issue, I used Mint (a Debian distribution) and installed all the drivers via the command line there. After that, when I ran fastboot devices, I got something. It was my lost N5x showing with 'no permissions' and no serial ID. I ran 'sudo fastboot devices' and lo' and behold, I saw the device. After that, I just used sudo fastboot flash recovery/system/etc with it and that was it.
Click to expand...
Click to collapse
I made some progress: my device is now detected in fastboot. I have literally absolutely no clue what happened. I guess it was a bit of randomness or luck or something (maybe wacky and goofy). I've done some flashing - I've flashed system, boot, recovery, cache, data, and radio, but it's still stuck in a bootloop. I don't know what's going on it with it now, but it seems like I haven't made any progress with fastboot.

ItsMason said:
I think I've done goofed my nexus.
Yesterday, I made a backup of my phone, and then booted it up. Everything was working fine prior to the backup, but as soon as I booted it after making the backup, it got stuck on the google logo. I tried restarting it several times, but it's just been stuck in a bootloop ever since. I've tried numerous things, like formatting it, flashing factory images, and so on, but it turns out fastboot won't detect my device. ADB detects my device fine, but only in recovery. As far as I know, I don't have usb debugging enabled (since I formatted it). It currently has no OS since I formatted it. I've tried installing stock android since formatting it but it still gets stuck in a bootloop.
All my drivers are correct (I've re-installed them probably 10 times by now), and the images aren't corrupted (as far as I know).
I've run out of ideas, as I've been trying to figure this out for the past 2 days with no success. Any help would be appreciated.
Click to expand...
Click to collapse
Do you use 3.02.1. Twrp

Since you mention ADB works fine from recovery, have you tried to adb push a rom zip, and then flash it from your recovery?
Code:
adb push "/path/to/rom.zip" /data/media

ItsMason said:
I made some progress: my device is now detected in fastboot. I have literally absolutely no clue what happened. I guess it was a bit of randomness or luck or something (maybe wacky and goofy). I've done some flashing - I've flashed system, boot, recovery, cache, data, and radio, but it's still stuck in a bootloop. I don't know what's going on it with it now, but it seems like I haven't made any progress with fastboot.
Click to expand...
Click to collapse
Good. I see you mention flashing system, boot, recovery, cache(?), data(?) and radio. What do you mean by flash cache&data? You mean you've cleaned it? Formatting data is not usually a thing you have to do to recover from a bootloop.
What ROM have you flashed? Are you flashing stock? It's important you give more details so I can help you.
Have you flashed vendor.img? If you have been on a ROM that had it's own vendor.img and you went back to stock, then the vendor.imgs are different enough to cause a bootloop.
If all and all fails, we just want to see your system running so I'd recommend drop everything you are doing and follow these steps:
1. Access recovery (make sure you're using v 3.0.2.2)
2. Tap Wipe - > Advanced Wipe - > And check:
Dalvik / ART Cache
System
Internal Storage
Cache
3. Go to -> Pixel ROM (7.1.1) Get V 3.0 which was just uploaded recently. Please note it comes preconfigured with Gapps so no need to get that
4. You have to unzip the archive and you will see all the necessary img files (includes boot/vendor which are critical for boot). I strongly recommend manually flashing them. You can open the flash-all.bat file with a .txt editor and just follow the steps there.
After you have finished these steps, you should be free of a bootloop. From there, it is your decision where you. Either stay on a stock ROM or flash safely and always remember that you can make a backup and flash that backup in case you bootloop.
Good luck.
EDIT
Decay3 said:
Since you mention ADB works fine from recovery, have you tried to adb push a rom zip, and then flash it from your recovery?
Click to expand...
Click to collapse
I think his problem is deeper than a /system error. I'm guessing the wrong boot/vendor is flashed for the ROM he is trying to install and trying to guess which ROM would work on his current config would take more time than just starting from a clean flash.

Thanks for the help guys, but I gave up. I contacted Google and they sent me a replacement. Sorry for kind of wasting time.

HTC M9 Stuck in loop after trying to root

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.