Related
First post here, please excuse my ignorance. This is a Virgin Mobile HTC One V. I never rooted a phone before, and was just trying to do a basic rooting, and somehow got into trouble. I would like to return the phone to stock and start over.
Right now the phone boots itself into bootloader, and shows me this:
Relocked
Security warning
PRIMOC PVT SHIP S-ON RL
HBOOT-1.57.0000
RADIO-1.00.00.0928
eMMC-boot
Jun 18 2012, 10:22:43
I am able to do this: fastboot getvar cid. The response is this: cid: SPCS_002.
I am also able to do this: fastboot devices. The response is this: FA2AKX405758 fastboot.
I have attempted to use this RUU:
RUU_PRIMO_C_ICS_40A_Sprint_WWE_VM_1.08.652.6_Radio_1.00.00.0521_2_NV_VM_3.46_0503_PRL61008_release_262414_signed.exe
It gives me error 170, USB connection error (even though I have installed the HTC drivers). I relocked the phone in an attempt to get that RUU to work, but it didn't help. I also tried to extract the rom.zip from the RUU.exe (by finding it in a temp folder, as described on another XDA thread), but the rom.zip acts corrupt. Various zip programs refuse to open it.
Before relocking the phone (in an attempt to get the RUU to work) I tried this:
fastboot flash boot boot.img
I did that with various boot.img files I found via threads here. This just created various problems. One result was that I was in a bootloop. Another result was that I booted to the screen that said "this build is for development purposes only do not distribute outside of htc without written permission." And it would hang there.
Now my condition is that I boot directly to bootloader.
Starting from the beginning: I unlocked the phone using the unlock bootloader procedure at htcdev. No problem. Then I figured I should do a backup right away, so I installed CM Recovery. Right away I knew I had a problem because it did not run correctly. It would present a menu. Then I would select "backup and restore." It would present a splash screen (with the hat) and just hang there. When I pressed power, it would return to the menu. That's when I started trying various other things.
I never got as far as doing anything with superboot or superuser, which is what I thought I was going to do after doing the backup.
I have read a zillion threads here, and tried various things from those threads, but I'm afraid that without specific help I'm just going to make it worse. I'm pulling my hair out, so I hope someone here can help me while I still have a few left. Thanks!
OK, I have made some progress but I'm still pretty stuck.
I have been able to solve two problems I had before. Before when I ran the RUU, it gave me a USB error. And I could not extract recovery.img from the RUU. I solved both those problems by moving to a different PC.
So now I can run the RUU, and it gives me a bunch of progress messages I didn't see before, but at the end it tells me this:
"Error 155, unknown error. The ROM Update Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again."
So then I tried the procedure described here:
http://forum.xda-developers.com/showpost.php?p=27301573
I unlocked the phone again, and I did this:
fastboot flash recovery recovery_signed.img
I did that using the img file I extracted from the RUU. Then I relocked the bootloader, and I ran the RUU again. But it gave me the exact same error (155).
What should I try next? I notice that the RUU also contains these img files:
system.img
radio.img
boot_signed.img
Should I try flashing those?
Any ideas would be greatly appreciated!
Edit: One more thing. When I ran the RUU, at the end the phone said this:
RUU
Hboot version is older!
Update Fail!
OK, the next thing I tried is the method described here:
http://forum.xda-developers.com/showthread.php?t=1674226
I extracted rom.zip from the RUU, and I renamed it PK76IMG.zip, and I put it on the sdcard, and then I rebooted the phone. The phone found that file and tried to install it, but in the end it gave me the same error message: "Hboot Version is older." On that same screen I see that my current Hboot is 1.57.0000. I guess the RUU contains an older Hboot?
Anyway, that's the same error I get when I run the RUU as an exe.
I notice a couple of people in that thread reported the same problem (Hboot is older), but it's not clear how or if they got around this.
Any ideas?
OK, so here's the next stage in this saga.
Looking around, it seems that there is no RUU for this phone, because I have Hboot 1.57.0000 and radio 1.00.00.0928. I have noticed that people with those specs cannot find a RUU that works, but they have been able to get the phone working with RhythmicRom. I see that discussed here:
http://forum.xda-developers.com/showthread.php?t=2147407
So what I'm trying to do now is install RhythmicRom, but I'm having trouble doing that, I guess because I don't have CM Recovery installed, so the standard recovery is running instead.
I have placed RhythmicRom_v1.4.zip on my sdcard. I am able to boot into bootloader, and I have done factory reset. In the bootloader, I can select Recovery and I see a screen that indicates the phone is looking for something (green circle containing green arrow pointing down, and with a progress bar at the bottom, and an icon of an sdcard). But I guess it doesn't find what it's looking for, and then I see the screen with the red triangle/exclamation mark.
I'm thinking that maybe it will work if on the sdcard I rename RhythmicRom_v1.4.zip to whatever the phone is looking for. Maybe I should rename it to PK76IMG.zip? Just a guess.
Many thanks in advance.
OK, that sort of almost worked. On the sdcard, I renamed RhythmicRom_v1.4.zip to PK76IMG.zip. I booted into bootloader, and it looked like the phone found that file, and loaded it. Then I did this:
fastboot flash boot boot.img
With the boot.img that was inside RhythmicRom_v1.4.zip. Then I rebooted. Now the phone gets to the red animated Virgin Mobile splash screen with the annoying audio. That seems like a good sign, since I haven't seen that in a while. But instead of continuing to boot, then I see the white HTC screen that says "this build is for development purposes only do not distribute outside of htc without written permission." And then it continues to loop between those two screens, so I am stuck in a bootloop. Although I found I was able to interrupt it and get back to the bootloader.
Not sure what to try next. Any suggestions?
Wow, I can't believe you haven't had a single reply.
Ok. First of all.... Use TeamWinRecoveryProject
( TWRP ) as your recovery img
So easy to use
Use fastboot the flash
fastboot flash recovery recovery.img
Then boot into your new touch screen recovery
Now click wipe
Cashe,Dalvick,Factory Reset, System
In that order. It makes sure every thing is wiped thoroughly.
Now navigate to where the Rom is you would like to use and flash it in recovery.
After It's flashed click the wipe cashe/dalvick
Then click home,reboot,bootloader.
Once in bootloader, flash the kernel/bootimg
fastboot flash boot boot.img
After the boot.img is finished,
fastboot reboot
Victory and enjoy the awesomeness of custom ROMs!
P.S. don't forget to unlock your bootloader again. First and foremost
fastboot flash unlocktoken Unlock_code.bin
Russell, thank you for your response. After 24 hours with over 100 views and zero replies, I figured that meant that I had already done the proper steps, and there wasn't some obvious solution I was missing. Although I can see now that I should have tried TWRP. It couldn't have made things worse, and maybe it would have worked better for me than CM Recovery (which seemed to fail as soon as I installed it).
Another key thing was when I figured out that there is no RUU for my specs (because there was an OTA that installed a newer hboot and radio). I like the idea of trying different custom ROMs, but I don't like the idea of never being able to go back to stock, since I would expect that all the custom ROMs have some quirks that I might find unacceptable. But I notice that you have the same hboot and radio, and I assume you have a backup of your stock ROM, so maybe you could have helped me with that.
Anyway, at literally the exact moment that you were posting your comment, I was standing at the UPS counter handing them the phone. If the phone had been working, we would have heard it buzzing inside the box as your email came in! The phone is heading to the HTC repair facility in Houston. They told me they would unbrick it for me for less than $35. I haven't seen anyone else report this, so maybe I was misled and it's too good to be true? We'll see. I don't like being without the phone for a week, but $35 seems like a cheap price to clean up the mess I made.
Anyway, thanks again for speaking up.
Check out the CDMA development thread
Whenever you get your phone back.....
Good luck
I see the thread you're talking about. I just did the download (might as well have it handy). Thank you.
Hope it helped or helps in some way
:beer:
---------- Post added at 02:40 AM ---------- Previous post was at 02:35 AM ----------
I gave you a thanks for first download
Similar problem
Hi,
I had a similar problem. Following this thread I have successfully "unbricked" my phone. My main concern though is activating my phone on VM, which I'm unable to do as I can't go back to stock. I bought the phone as is from craigslist. Any suggestions?
Edit: Internet seems to work though. No go on phone calls or texts, when trying to call this is what I get(Audio):"Account couldn't be verified"
Visit the HTC one v CDMA thread I have a stock rooted Rom there for the taking
Yes, here's the link to that thread:
http://forum.xda-developers.com/showthread.php?t=2321904
It would be interesting to hear if your rom works for cellphoneman.
Hi developers,
I have just today gotten my M8 HTC One S-Off'd, and went ahead with google play edition conversion. It went well, but I missed some sense features. So I tried to follow the tutorial on how to get back to sense, but after rebooting to bootloader - and flashing the 54meg firmware thru fastboot - didn't notice to flash custom recovery. Phone is not booting (bootloop after first logo screen), and recover is a stock one. Now I have tried flashing some random RUUs I found on graffixnyc's website, but the stock recovery says "Finding update package", then "Opening", then "verifying" and then returns with error - exclamation mark in red, and "Installation aborted" message.
I have no connectivity thru fastboot or adb, just this recovery.
Is there any help, or is the device bricked for good? Supercid (11111111), S-off and unlocked bootloader.
Also, seems like I cannot enter HBOOT in any way - holding button up or down... just the recovery.
Best regards
Mike
EDIT: When I downloaded OTA 5.0.1 update from graffixnyc's website, the Verification didn't abort at the beginning, in fact it threw quite different error messages:
"Package expects buld fingerprint of htc/m8_google/htc_m8:4.4.4/KTU84P.H1/356549 (...) or 5.0.1, this device has htc_wurope/htc_m8:4.4.2/KOT49H" and then installation aborted. So I need another OTA package???
EDIT: Somehow I managed to enter FASTBOOT, just holding vol- and power between reboots and it worked finally. Now I'll flash twrp and hopefully it'll go better after that. Don't know what firmware to flash then though to have sense6 and 5.0.1.
Did you make a note of the software version you were on before you flashed the GPe? It would've been helpful to know for recovery purposes. It'd also have helped in case there was an RUU available to make the process easier
I bought an AT&T M8 on eBay a few months ago. My carrier is T-Mobile. Everything actually worked fairly well but there are a few nagging issues. No OTA updates, MMS doesn't work, etc.
I did some research on the forums here and elsewhere and the solution seemed to be flashing the phone to a stock T-Mobile firmware. Tonight I set out to do that.
I downloaded and paid for Sunshine. Installed with no issues.
I installed HTC Synch and ADB on my PC
I flashed CWM recovery onto the phone using fastboot. TWRP wouldn't work for some reason.
I used CWM to install SuperSU to root the phone.
I used fastboot to change the CID to T-MOB010.
I used scotty1223's instructions here to change the MID from 0P6B12000 to 0P6B13000.
There were some false steps along the way but I think everything worked fine to this point.
Next I used fastboot to flash the firmware I found here. At this point I don't even remember why I decided that was the right choice.
The firmware flash failed the first time but apparently that isn't uncommon. I ran it a second time and it seemed to succeed. I rebooted the phone using fastboot. When it comes up I see the HTC logo on a white background and I can still hear the AT&T "chimes" but I don't see the AT&T globe. And that's it. The phone won't finish booting. I can reboot into the fastboot menu but Recovery just gives me an red triangle with an exclamation point. ADB can't communicate with the phone anymore. So I feel like I'm stuck.
Any advice on what to do next?
AlphaJ23 said:
I bought an AT&T M8 on eBay a few months ago. My carrier is T-Mobile. Everything actually worked fairly well but there are a few nagging issues. No OTA updates, MMS doesn't work, etc.
I did some research on the forums here and elsewhere and the solution seemed to be flashing the phone to a stock T-Mobile firmware. Tonight I set out to do that.
I downloaded and paid for Sunshine. Installed with no issues.
I installed HTC Synch and ADB on my PC
I flashed CWM recovery onto the phone using fastboot. TWRP wouldn't work for some reason.
I used CWM to install SuperSU to root the phone.
I used fastboot to change the CID to T-MOB010.
I used scotty1223's instructions here to change the MID from 0P6B12000 to 0P6B13000.
There were some false steps along the way but I think everything worked fine to this point.
Next I used fastboot to flash the firmware I found here. At this point I don't even remember why I decided that was the right choice.
The firmware flash failed the first time but apparently that isn't uncommon. I ran it a second time and it seemed to succeed. I rebooted the phone using fastboot. When it comes up I see the HTC logo on a white background and I can still hear the AT&T "chimes" but I don't see the AT&T globe. And that's it. The phone won't finish booting. I can reboot into the fastboot menu but Recovery just gives me an red triangle with an exclamation point. ADB can't communicate with the phone anymore. So I feel like I'm stuck.
Any advice on what to do next?
Click to expand...
Click to collapse
check that your cid and mid are now correct for T-Mo by doing a fastboot get var all.
Firmware you flashed is fine.
your phone is stuck in a bootloop which isn't un-common, due to the rom version and firmware version mis-maych I expect.
red triangle is stock recovery, so that's also normal.
at this point, rather than trying to reboot the phone, you should of just booted back to the bootloader fastboot usb mode and run the T-mo RUU, the first thing the RUU does anyway is boot your phone to the bootloader anyway, your just manually doing the first part yourself.
Thanks a lot for the help. A couple of follow-up questions for you. Adb/fastboot can't connect to the phone now. I've tried at the HTC white screen and the bootloader fastboot screen. It just says '< waiting for device >'.
I'm also having a problem with the RUU. When I accept the license agreement on the install it seems to crash. No errors but nothing else happens and the process isn't running. I'm going to try that on a different machine and see what happens. Thanks again.
Another update. The RUU install works fine on a different machine. I think that was a Windows 8.1 issue. The problem now is that the RUU can't see the phone either. So I can't get a PC to see the phone over USB at all. I assume that's because of the bootloop. Is there anything I can do from the bootloader to fix this?
Some progress. The RUU finally found the phone. I guess that was a timing issue. Now it seems to be stuck at 'Updating.... (1/7) Sending....'. It's been doing that for over an hour.
Finally, success!! I found a Reddit thread about the RUU failure. It recommended finding the ROM.zip that gets dropped in a temp folder by the installer, renaming that to 0P6BIMG.zip, moving it to the sdcard, and rebooting. It worked like a charm. Fastboot found the zip automatically and prompted me to install it. It took a little while to update but now I have a stock T-Mobile HTC One.
please help
AlphaJ23 said:
Finally, success!! I found a Reddit thread about the RUU failure. It recommended finding the ROM.zip that gets dropped in a temp folder by the installer, renaming that to 0P6BIMG.zip, moving it to the sdcard, and rebooting. It worked like a charm. Fastboot found the zip automatically and prompted me to install it. It took a little while to update but now I have a stock T-Mobile HTC One.
Click to expand...
Click to collapse
my phone has exactly the same problem but i really dont know what to do from here
Hi all,
My m8 is rooted, with CWM. I was having issues with it, so I decided to wipe it and flash the marshmallow GPE update to see if that would help (since my OTA alert was there). However, it's now stuck in a bootloop, and I can't get into recovery, or get a computer to recognize it.
If I hold the power and volume buttons down, it will restart, I can get the white screen with HTC logo and red writing stating the build is for development purposes only, but after that it goes right to the loading screen again, instead of going into recovery like it normally would (and like it's done a thousand times for me in the past). I'm not the techiest person, but I thought I'd done enough research on this to do it properly.. apparently not I've tried everything I (and google) can think of, but everything seems to rely on getting to recovery to flash a new rom/wipe the cache/etc or hooking it up to a computer, neither of which I can do. Do I have any other options? This is a "new" phone (bought it refurbished from tmobile to replace my old m8 which I also had issues with... obviously a bad choice), and the thought of buying a new phone again just really kills me. Any help would be SO greatly appreciated. Thanks!
butneveragain said:
Hi all,
My m8 is rooted, with CWM. I was having issues with it, so I decided to wipe it and flash the marshmallow GPE update to see if that would help (since my OTA alert was there). However, it's now stuck in a bootloop, and I can't get into recovery, or get a computer to recognize it.
If I hold the power and volume buttons down, it will restart, I can get the white screen with HTC logo and red writing stating the build is for development purposes only, but after that it goes right to the loading screen again, instead of going into recovery like it normally would (and like it's done a thousand times for me in the past). I'm not the techiest person, but I thought I'd done enough research on this to do it properly.. apparently not I've tried everything I (and google) can think of, but everything seems to rely on getting to recovery to flash a new rom/wipe the cache/etc or hooking it up to a computer, neither of which I can do. Do I have any other options? This is a "new" phone (bought it refurbished from tmobile to replace my old m8 which I also had issues with... obviously a bad choice), and the thought of buying a new phone again just really kills me. Any help would be SO greatly appreciated. Thanks!
Click to expand...
Click to collapse
One big problem with what you are doing is you are using CWM. That recovery hasn't been maintained in about two years now. It's obsolete. You need to flash the latest TWRP instead. Also, you should make sure your firmware is up to date. You can find that in your bootloader listed under "OS"
Let's get you out of your bootloop first.
Hold down power + vol up until your phone reboots. AS SOON AS THE SCREEN GOES BLACK switch from holding vol up to vol down. This will take you to your bootloader. Check your OS version. It should be 6.xx.xxx.x
Now that you are in bootloader, flash TWRP with fastboot.
When that is done fastboot reboot-bootloader and go to your phone. Navigate to hboot on the bootloader menu, and you will have the option to boot to recovery. Flash the ROM again, and all should be working for you.
Go to this link to get TWRP. The downloads for the M8, and instructions on how to flash it in fastboot are all there for you.
Good luck!
xunholyx said:
One big problem with what you are doing is you are using CWM. That recovery hasn't been maintained in about two years now. It's obsolete. You need to flash the latest TWRP instead. Also, you should make sure your firmware is up to date. You can find that in your bootloader listed under "OS"
Let's get you out of your bootloop first.
Hold down power + vol up until your phone reboots. AS SOON AS THE SCREEN GOES BLACK switch from holding vol up to vol down. This will take you to your bootloader. Check your OS version. It should be 6.xx.xxx.x
Now that you are in bootloader, flash TWRP with fastboot.
When that is done fastboot reboot-bootloader and go to your phone. Navigate to hboot on the bootloader menu, and you will have the option to boot to recovery. Flash the ROM again, and all should be working for you.
Go to this link to get TWRP. The downloads for the M8, and instructions on how to flash it in fastboot are all there for you.
Good luck!
Click to expand...
Click to collapse
You are a lifesaver! Didn't even think about trying to switch from volume up to down, but that did it.
Ok, so now I have TWRP, but my OS was definitely NOT 6 (it was 4.something). I assume that was one of my issues? Honestly, at this point, I just want to go back to stock lollipop, like I had before.. I bounced around a few stock marshmallow roms before my bootloop (realized I hated GPE, that HTC transfer didn't support my device on those versions, CWM wouldn't restore any of my backups--which now makes sense, etc), so I think I just want to quit messing with it at this point and count my blessings. I've had issues finding stock roms though, obviously. Could you point me in the right direction? I just want stock tmobile lollipop, with sense. I didn't think it'd be so difficult, but I'm clearly not very up-to-date on this stuff. Thanks SO much again!
butneveragain said:
You are a lifesaver! Didn't even think about trying to switch from volume up to down, but that did it.
Ok, so now I have TWRP, but my OS was definitely NOT 6 (it was 4.something). I assume that was one of my issues? Honestly, at this point, I just want to go back to stock lollipop, like I had before.. I bounced around a few stock marshmallow roms before my bootloop (realized I hated GPE, that HTC transfer didn't support my device on those versions, CWM wouldn't restore any of my backups--which now makes sense, etc), so I think I just want to quit messing with it at this point and count my blessings. I've had issues finding stock roms though, obviously. Could you point me in the right direction? I just want stock tmobile lollipop, with sense. I didn't think it'd be so difficult, but I'm clearly not very up-to-date on this stuff. Thanks SO much again!
Click to expand...
Click to collapse
Okay. 4.xx firmware will actually work with 6.xx ROMs, but I'll instruct you on getting back to stock lollipop.
Backup anything important to you, such as photos and stuff, because this is going to wipe your phone. Don't worry about the apps. Google takes care of that for you. You might lose a little data from the apps, but if you want to be completely stock, this will do it. (you will probably get a prompt to update to Marshmallow via OTA eventually afterwards, but it will be the official stock version of it)
Also, this is assuming that you are T-Mo US, not a European T-Mo version.
Download this RUU onto your PC.
When the download if finished, hook up your phone and get into fastboot. You'll have to re-lock your bootloader first. The command is fastboot oem lock, then fastboot reboot
After you have re-locked your bootloader, double click on the RUU download and follow the prompts.
If there are problems with the RUU flash, try again while booted to bootloader. Sometimes that is needed for some reason.
That's it. You are now on stock T-MoUS 4.20.531.4
Good luck!
xunholyx said:
Okay. 4.xx firmware will actually work with 6.xx ROMs, but I'll instruct you on getting back to stock lollipop.
Backup anything important to you, such as photos and stuff, because this is going to wipe your phone. Don't worry about the apps. Google takes care of that for you. You might lose a little data from the apps, but if you want to be completely stock, this will do it. (you will probably get a prompt to update to Marshmallow via OTA eventually afterwards, but it will be the official stock version of it)
Also, this is assuming that you are T-Mo US, not a European T-Mo version.
Download this RUU onto your PC.
When the download if finished, hook up your phone and get into fastboot. You'll have to re-lock your bootloader first. The command is fastboot oem lock, then fastboot reboot
After you have re-locked your bootloader, double click on the RUU download and follow the prompts.
If there are problems with the RUU flash, try again while booted to bootloader. Sometimes that is needed for some reason.
That's it. You are now on stock T-MoUS 4.20.531.4
Good luck!
Click to expand...
Click to collapse
Thanks so much. I still have everything backed up from before (well, my CWM nandroid is useless now, but I'll live). I read about the RUUs originally when I was trying to get the stock rom, but some people were saying you had to be S-OFF for them. I'm S-ON--is that a problem?
butneveragain said:
Thanks so much. I still have everything backed up from before (well, my CWM nandroid is useless now, but I'll live). I read about the RUUs originally when I was trying to get the stock rom, but some people were saying you had to be S-OFF for them. I'm S-ON--is that a problem?
Click to expand...
Click to collapse
No it's not a problem, and something that I have already assumed.
If you were S-Off, you wouldn't need to re-lock your bootloader before running the RUU.exe
Those "some people who were saying" are incorrect.
butneveragain said:
I read about the RUUs originally when I was trying to get the stock rom, but some people were saying you had to be S-OFF for them.
Click to expand...
Click to collapse
Yeah, people need to stop saying that. Its completely false. RUU is an official HTC recovery tool, and its intended to work on stock (s-on) devices.
You only need s-off to flash RUU as unintended by HTC, such as:
- flash an older version RUU than what is on the phone ("downgrade")
- Change CID/MID to flash another version's RUU
- Flash RUU with unlocked bootloader
- Flash a hacked/unsigned RUU
xunholyx said:
One big problem with what you are doing is you are using CWM. That recovery hasn't been maintained in about two years now. It's obsolete. You need to flash the latest TWRP instead. Also, you should make sure your firmware is up to date. You can find that in your bootloader listed under "OS"
Let's get you out of your bootloop first.
Hold down power + vol up until your phone reboots. AS SOON AS THE SCREEN GOES BLACK switch from holding vol up to vol down. This will take you to your bootloader. Check your OS version. It should be 6.xx.xxx.x
Now that you are in bootloader, flash TWRP with fastboot.
When that is done fastboot reboot-bootloader and go to your phone. Navigate to hboot on the bootloader menu, and you will have the option to boot to recovery. Flash the ROM again, and all should be working for you.
Go to this link to get TWRP. The downloads for the M8, and instructions on how to flash it in fastboot are all there for you.
Good luck!
Click to expand...
Click to collapse
My phone is stuck on boot screen... How can I turn off the device if my vol+ button does not work?
HTC One M9, no branding, official software, locked and S-ON.
one month ago my phone got (for no apparent reason) serious software problems, so spend a lot of time on the internet to find a solution. in the end, i downloaded the correct stock rom, put it on a sd card and reinstalled stock android via the download mode. it worked out really well, my phone was running like new.
but 2 days ago i pick up my phone and realize it's stuck in a bootloop. (again for no apparent reason) using the right button combinations, i am able to get into the bootloader.
when i try to flash the stock rom with the exact same method that worked last time, it says "start ui_updating" and gets caught in the bootloop again. (i dont think i did anything wrong because the exact same procedure worked last time)
when i enter recovery mode, i get the infamous red triangle. using the right buttons, i can still access the recovery mode from there. now, when i try to factory reset from here, i get the following errors: E: failed to mount /preload (invalid argument).. try emmc mount E: Cant find device node for mount point again E: mount /cache fail, format it and mount again ----- about 5 more similar errors after those 3.
I tried to flash recovery img with fastboot but i get an error similar to:
9 RU_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCKE
I guess this is because my phone doesn't have usb debugging enabled or it doesn't have an unlocked bootloader.
I also tried to unlock the bootloader but after running the command: fastboot oem get_identifier_token i don't get the token so i can post it to htcdev and unlock my bootloader.
Anybody help or had the same issue and fixed it?
Thanks in advance
DE2IS said:
HTC One M9, no branding, official software, locked and S-ON.
one month ago my phone got (for no apparent reason) serious software problems, so spend a lot of time on the internet to find a solution. in the end, i downloaded the correct stock rom, put it on a sd card and reinstalled stock android via the download mode. it worked out really well, my phone was running like new.
but 2 days ago i pick up my phone and realize it's stuck in a bootloop. (again for no apparent reason) using the right button combinations, i am able to get into the bootloader.
when i try to flash the stock rom with the exact same method that worked last time, it says "start ui_updating" and gets caught in the bootloop again. (i dont think i did anything wrong because the exact same procedure worked last time)
when i enter recovery mode, i get the infamous red triangle. using the right buttons, i can still access the recovery mode from there. now, when i try to factory reset from here, i get the following errors: E: failed to mount /preload (invalid argument).. try emmc mount E: Cant find device node for mount point again E: mount /cache fail, format it and mount again ----- about 5 more similar errors after those 3.
I tried to flash recovery img with fastboot but i get an error similar to:
9 RU_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCKE
I guess this is because my phone doesn't have usb debugging enabled or it doesn't have an unlocked bootloader.
I also tried to unlock the bootloader but after running the command: fastboot oem get_identifier_token i don't get the token so i can post it to htcdev and unlock my bootloader.
Anybody help or had the same issue and fixed it?
Thanks in advance
Click to expand...
Click to collapse
Hi Sorry to say, I have " Exactly" the same problem and have also reached the same place, I asked on these forums without success. in the end I sent it back to HTC and they want £200 to repair it or £29.00 diagnostic fee. I have asked them to send it back and will have to pay the £29.00. If it is within warrantee send it back.
m01y1i00 said:
Hi Sorry to say, I have " Exactly" the same problem and have also reached the same place, I asked on these forums without success. in the end I sent it back to HTC and they want £200 to repair it or £29.00 diagnostic fee. I have asked them to send it back and will have to pay the £29.00. If it is within warrantee send it back.
Click to expand...
Click to collapse
Thanks for your fast reply.
I will get in contact with them and see what they will say. My phone is under warranty so i will pay only for shipping charges.
I bought it from a german eshop and i am from Cyprus.
The problem is, the official distributor for HTC here in Cyprus is Greece and i had a bad experience with them. I sent an old HTC One X 4 years before which had a board issue, and after waiting for a month they sent it back and guess what. It had the same problem. So i got in contact with the US website, described the problem and mentioned also the "official distributors" in Cyprus and Greece and how their "service" was and they told me i will have a brand new phone here in Cyprus within a week (which became a reality).
So before i experience the same issues i will clear everything from here (if anybody know a successful solution) and then communicate with HTC how to resolve this.
Thanks again for your reply!
Is this a general/common problem on htc? I am worried
Spike97 said:
Is this a general/common problem on htc? I am worried
Click to expand...
Click to collapse
I'd be lying if I'd say that I haven't read about the issue several times, already. However, you need to be aware of the fact that most of the time only people with problems are creating threads whereas people who have no issues at all won't do the same for praising the phone.
In other words: Yes, this problem does exist but no, not everyone faces it. I know many users whose M9 is still working fine.
DE2IS said:
HTC One M9, no branding, official software, locked and S-ON.
one month ago my phone got (for no apparent reason) serious software problems, so spend a lot of time on the internet to find a solution. in the end, i downloaded the correct stock rom, put it on a sd card and reinstalled stock android via the download mode. it worked out really well, my phone was running like new.
Click to expand...
Click to collapse
I also have a bootloop issue with Locked and S-ON... Care to let me know how you managed to get it working the 1st time?
Where to find the corrent stock ROM and the method you did to get it working..
i have the same problem. Where can i get a rom.zip
Bootloop
gmayer1212 said:
i have the same problem. Where can i get a rom.zip
Click to expand...
Click to collapse
Take the new OTA Nougat, separate those three files on your sd card
Install it with fastboot
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
and it will be working takes 5-10 minutes to restart
kwaichang said:
Take the new OTA Nougat, separate those three files on your sd card
Install it with fastboot
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
and it will be working takes 5-10 minutes to restart
Click to expand...
Click to collapse
Please don't give such advice. If the firmware isn't matching the system version users will face bugs and lags or the phone won't even boot. (The latter happens for example if you try to use an Android M system with an Android L firmware.) Besides a user with a locked bootloader and a firmware/system-mismatch won't be able to install any OTAs unless that person flashes a RUU for fixing the mismatch*. The catch is there is no publicly available Android N RUU for every variant of the M9, at the moment. And with S-ON you aren't able to use older RUUs. That means people might have to contact Llabtoofer's RUU Service (which isn't for free!) if they followed your recommendation.
* Users with an unlocked bootloader need to fix the mismatch, as well, but at least they have twrp backups as an alternative solution for the problem.
@gmayer1212 & @htcm9guy: You may want to read the ReadMe thread. It's pinned above the normal threads here in this section.
Flippy498 said:
Please don't give such advice. If the firmware isn't matching the system version users will face bugs and lags or the phone won't even boot. (The latter happens for example if you try to use an Android M system with an Android L firmware.) Besides a user with a firmware/system-mismatch won't be able to install any OTAs unless that persons flashes a RUU for fixing the mismatch. The catch is there is no publicly available Android N RUU for every variant of the M9, at the moment. And with S-ON you aren't able to use older RUUs. That means people might have to contact Llabtoofer's RUU Service (which isn't for free!) if they followed your recommendation.
@gmayer1212 & @htcm9guy: You may want to read the ReadMe thread. It's pinned above the normal threads here in this section.
Click to expand...
Click to collapse
Sorry for that. Mine was also hanging in bootloop but unlocked S-on T-mobile Germany
kwaichang said:
Sorry for that. Mine was also hanging in bootloop but unlocked S-on T-mobile Germany
Click to expand...
Click to collapse
Don't get me wrong, I don't want to discourage you from helping others. It's just important that you know which variant of the M9 the user with the problems owns in such cases. Just recommending to flash random stock files only causes more problems than it solves.
Just to chime in --- same problem happened to me yesterday.
Phone has been working fine --- then yesterday phone went unstable so I reset and got caught in bootloop.
After doing a factory reset and many tries -- got it to boot to android, only to get bombarded by google play service errors -- most likely wrong version of google play services for android?? I manually installed google play services apk... Reset and after many tries was able to boot again -- system was smooth. But did a quick reset to check whether problem was fixed and now i'm back in boot loop.
I wonder if there's a problem with a recent google apps update over playstore that's killing boot?
Hello,
i have the same problem but in some ways different. My M9 was running nearly fine until yester der evening. I just plugged the power supply and suddenly black screen, bootloop. But the really big problem is i don't come in any different stable mode than bootloader. If i try to get into download or recovery mode, the silver htc-logo appears for less than a secound, short vibration and reboot - and this is in loop also.
So for me i don't se a way to factory reset or reinstall any RUU or anything else?
Is it destroyed? :crying:
I was complete S-Off before, running on the last firmware with ViperOneM9 6.1.0.
Thans for your support,
Bond
That sounds like the dead nand issue. It's a hardware failure (c.f. the FAQ of the ReadMe thread).
Sent from my HTC One M9 using XDA Labs
If your phone is under warranty, it has a stock rom, and bootloader is still locked, then send it to HTC after contacting them via chat.
They will replace either the board or the device.
This is whhat they did for me.
DE2IS said:
HTC One M9, no branding, official software, locked and S-ON.
one month ago my phone got (for no apparent reason) serious software problems, so spend a lot of time on the internet to find a solution. in the end, i downloaded the correct stock rom, put it on a sd card and reinstalled stock android via the download mode. it worked out really well, my phone was running like new.
but 2 days ago i pick up my phone and realize it's stuck in a bootloop. (again for no apparent reason) using the right button combinations, i am able to get into the bootloader.
when i try to flash the stock rom with the exact same method that worked last time, it says "start ui_updating" and gets caught in the bootloop again. (i dont think i did anything wrong because the exact same procedure worked last time)
when i enter recovery mode, i get the infamous red triangle. using the right buttons, i can still access the recovery mode from there. now, when i try to factory reset from here, i get the following errors: E: failed to mount /preload (invalid argument).. try emmc mount E: Cant find device node for mount point again E: mount /cache fail, format it and mount again ----- about 5 more similar errors after those 3.
I tried to flash recovery img with fastboot but i get an error similar to:
9 RU_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCKE
I guess this is because my phone doesn't have usb debugging enabled or it doesn't have an unlocked bootloader.
I also tried to unlock the bootloader but after running the command: fastboot oem get_identifier_token i don't get the token so i can post it to htcdev and unlock my bootloader.
Anybody help or had the same issue and fixed it?
Thanks in advance
Click to expand...
Click to collapse
is your phone recongized - what shows "fastboot devices"
pear-i said:
Just to chime in --- same problem happened to me yesterday.
Phone has been working fine --- then yesterday phone went unstable so I reset and got caught in bootloop.
After doing a factory reset and many tries -- got it to boot to android, only to get bombarded by google play service errors -- most likely wrong version of google play services for android?? I manually installed google play services apk... Reset and after many tries was able to boot again -- system was smooth. But did a quick reset to check whether problem was fixed and now i'm back in boot loop.
I wonder if there's a problem with a recent google apps update over playstore that's killing boot?
Click to expand...
Click to collapse
I too wonder the same - recently had the bootloop issue with my M9, just when it was updating apps from the Playstore... quite suspicious...
My HTC M9 is also in boot loop
htcm9guy said:
I also have a bootloop issue with Locked and S-ON... Care to let me know how you managed to get it working the 1st time?
Where to find the corrent stock ROM and the method you did to get it working..
Click to expand...
Click to collapse
It happened at last Saturday, when I've just tried to perform a regular reset to my HTC M9 (from the regular device's menu).
I can't enter to download mode (fail), wipe cache and wipe all (factory reset) didn't help.
Is there any chance to fix it at home? Or just to buy a new phone?
And, does this issue can occur in other devices, HTC or any other brand?
Please advise.
(Can't upload a picture of my device, since I'm a new user...)
Thanks!
As far as I know there's nothing you can do. There are no reports of successful diy repairs of a dead nand M9.
Theoretically this issue can happen with any phone. However, it looks like the probability of its occurence on a M9 increased a lot during the last months.
I´m also stuck in bootloader mode
recovery mode / download mode endup with red text:
"failed to boot to download mode"
***Software status: Modified***
***LOCKED***
***S-ON***
***Security Warning***
Cannot get the token as fastboot oem commands end up empty or unknown command.
I think USB-debbugging is "off"
How can i get S-OFF
or how can i get token
Thanks.