My HTC Desire HD has developed the dreaded Boot Loop. Suddenly went this way whilst on charge in car.
I can get into HBoot - USB and Fastboot - USB menus, but if I select Recovery, it goes back into boot loop.
I can't see the phone on my laptop but can see my HD card when attached in a holder.
The following info is visible:
ACE PUT SHIP S-ON RL
HBOOT-2.00.0027
MICROP-0438
RADIO-26.14.04.28_M
eMMC-boot
Sep 7 2011, 19:06:24
I am not a developer, but with detailed instructions, I did manage to wipe my other phone and install a new RUU. Trouble is that I am in a dodgy reception area and that phone gets no signal here, so I'm dependent upon getting this one sorted.
Could any considerate chap out there help me, without using shorthand terms like "just flash xxx in yyy mode and then zzz using this link, which turns out to be dead. I have searched high and low, but the S-ON designation means, I understand, that "easy" options are off. Of course, I cannot enable USB debugging, or enable connection to PC as I can't complete the boot process.
I'll be very grateful for any help.
Did you relock your boot loader?
Hook up your device in Fastboot and run last official gingerbread update(2.3.5) from pc.
***RUU selection goes to the carrier that device came with. I hope these covers x > y > z
marknoll said:
Did you relock your boot loader?
Click to expand...
Click to collapse
This is an untouched phone.
Hook up your device in Fastboot and run last official gingerbread update(2.3.5) from pc.
Click to expand...
Click to collapse
I can't see my PC when USB'd to phone. Could I put it on the SD card, which I can see when in a USB holder, with any hope that it would work from there when replaced in phone?
Install min adb and fastboot. Run it and install it then plug in your phone. Let PC recognize it. Then open a cmd and type fastboot getvar all
marknoll said:
Install min adb and fastboot. Run it and install it then plug in your phone. Let PC recognize it. Then open a cmd and type fastboot getvar all
Click to expand...
Click to collapse
Thanks for that.....Just returned completely knackered from windsurfing so will have a go tomorrow when I'm less likely to foul it up!
marknoll said:
Install min adb and fastboot. Run it and install it then plug in your phone. Let PC recognize it. Then open a cmd and type fastboot getvar all
Click to expand...
Click to collapse
OK. done that and this is the result
C:\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0027
(bootloader) version-baseband: 26.14.04.28_M
(bootloader) version-cpld: None
(bootloader) version-microp: 0438
(bootloader) version-main: 3.12.405.1
(bootloader) serialno:
(bootloader) imei: 352668041228402
(bootloader) product: ace
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PD9810000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4199mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 743ca94a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) region-id: 0
all: Done!
finished. total time: 0.037s
"Hook up your device in Fastboot and run last official gingerbread update(2.3.5) from pc"
I have downloaded this gingerbread update but have no idea how to run it from my pc. I have put it in the root directory but it has no exe file and the Cmd prompt doesn't seem to help. I still can't see the phone in explorer.
Probably a simple process but I have no previous experience to guide me.
You have latest hboot
---------- Post added at 01:44 PM ---------- Previous post was at 01:42 PM ----------
Run the update that has baseband 12.69a. You're not supercid nor unlocked BL nor s offed.. This should help. Make sure u back up all u need as this will wipe the device with a clean slate.
---------- Post added at 01:51 PM ---------- Previous post was at 01:44 PM ----------
http://forum.xda-developers.com/showthread.php?t=2635479
marknoll said:
You have latest hboot
---------- Post added at 01:44 PM ---------- Previous post was at 01:42 PM ----------
Run the update that has baseband 12.69a. You're not supercid nor unlocked BL nor s offed.. This should help. Make sure u back up all u need as this will wipe the device with a clean slate.
---------- Post added at 01:51 PM ---------- Previous post was at 01:44 PM ----------
http://forum.xda-developers.com/showthread.php?t=2635479
Click to expand...
Click to collapse
Sorry. I understand S - off but that's all. I'm not a developer. Just a fairly computer literate Desire HD user with a problem!
I see the term baseband in your message and in my getvar report, but have no idea what it is. Could you be kind and give me a link to what I need to use, and explain where the .exe file is or whatever I need to run it? Much appreciated.
Don't panic...
Quick notes and probably last reply from me, I'll try to cover every aspect of your problem.
-RUU is a Stock ROM which should be in .exe format to run through pc while device is connected.
-To play around with device,doesn't necessary to be a developer.
-I'm also not a dev but if you spend more time here,you'll learn a lot.
So cut the crap and head over your issue.
now i don't know which carrier your device is locked Or from where you bought the device. But RUU should be from that carrier origin or at least country origin.
Check here: http://www.shipped-roms.com/index.php?category=android&model=Ace
These are stock rom for our device(Ace-code name of Desire HD/Inspire 4g)
Choose one with ending of .exe and according to your carrier or country from where you bought it.
As earlier you've mentioned that you may able to get into Fastboot,then put your device in fastboot mode and it should be in Hboot USB ,now to go into such way you need to connect your device through USB and wait a second or so then press power button and it will show you in RED color.
After that run RUU file through pc by double clicking on file. It will prompt you that it will upgrade your device hboot version,go ahead and click next. and let the process complete. But before all make sure your device has more than 30% of battery. If you encountered any problem,then head over to htc.com and ask for help regarding it. I'm just saying because your device is in Stock mode,nothing has been changed according their standard. Or you may look at here in forum regarding error that you get while running RUU.
If you successfully go through all steps,then your device probably back to life again,unless there isn't any hardware issue. Once you deal with this you may now able to unlock bootloader and root your device. But that's only when you actually done with above mentioned steps.
If some point you don't understand what i'm saying,then from my side i'm SORRY. But you've to spent more time with your device in order to learn it properly.
dr.patron99 said:
Quick notes and probably last reply from me, I'll try to cover every aspect of your problem.
-RUU is a Stock ROM which should be in .exe format to run through pc while device is connected.
-To play around with device,doesn't necessary to be a developer.
-I'm also not a dev but if you spend more time here,you'll learn a lot.
So cut the crap and head over your issue.
now i don't know which carrier your device is locked Or from where you bought the device. But RUU should be from that carrier origin or at least country origin.
Check here: http://www.shipped-roms.com/index.php?category=android&model=Ace
These are stock rom for our device(Ace-code name of Desire HD/Inspire 4g)
Choose one with ending of .exe and according to your carrier or country from where you bought it.
As earlier you've mentioned that you may able to get into Fastboot,then put your device in fastboot mode and it should be in Hboot USB ,now to go into such way you need to connect your device through USB and wait a second or so then press power button and it will show you in RED color.
After that run RUU file through pc by double clicking on file. It will prompt you that it will upgrade your device hboot version,go ahead and click next. and let the process complete. But before all make sure your device has more than 30% of battery. If you encountered any problem,then head over to htc.com and ask for help regarding it. I'm just saying because your device is in Stock mode,nothing has been changed according their standard. Or you may look at here in forum regarding error that you get while running RUU.
If you successfully go through all steps,then your device probably back to life again,unless there isn't any hardware issue. Once you deal with this you may now able to unlock bootloader and root your device. But that's only when you actually done with above mentioned steps.
If some point you don't understand what i'm saying,then from my side i'm SORRY. But you've to spent more time with your device in order to learn it properly.
Click to expand...
Click to collapse
Thanks for your forbearance. My phone is PAYG so not tied to anyone. Thank you for the link. I went searching round the forum and was trying something that had no .exe, so couldn't fathom where to go. I'm quite happy if I can find that, and even happier if it fixes the problem.
With considerate help, I rooted another phone so am confident to push the margins as you implore me to do. I'll get on with it!
Thanks again
Androidruu.com. I already told ya
---------- Post added at 01:09 AM ---------- Previous post was at 01:07 AM ----------
marknoll said:
You have latest hboot
---------- Post added at 01:44 PM ---------- Previous post was at 01:42 PM ----------
Run the update that has baseband 12.69a. You're not supercid nor unlocked BL nor s offed.. This should help. Make sure u back up all u need as this will wipe the device with a clean slate.
---------- Post added at 01:51 PM ---------- Previous post was at 01:44 PM ----------
http://forum.xda-developers.com/showthread.php?t=2635479
Click to expand...
Click to collapse
The ruu is in the second post... 3.20xxxx. That's what you need
---------- Post added at 01:13 AM ---------- Previous post was at 01:09 AM ----------
Baseband explanation.
http://www.droidforums.net/threads/what-is-a-baseband.36959/
dr.patron99 said:
Quick notes and probably last reply from me, I'll try to cover every aspect of your problem.
-RUU is a Stock ROM which should be in .exe format to run through pc while device is connected.
-To play around with device,doesn't necessary to be a developer.
-I'm also not a dev but if you spend more time here,you'll learn a lot.
So cut the crap and head over your issue.
now i don't know which carrier your device is locked Or from where you bought the device. But RUU should be from that carrier origin or at least country origin.
Check here: http://www.shipped-roms.com/index.php?category=android&model=Ace
These are stock rom for our device(Ace-code name of Desire HD/Inspire 4g)
Choose one with ending of .exe and according to your carrier or country from where you bought it.
As earlier you've mentioned that you may able to get into Fastboot,then put your device in fastboot mode and it should be in Hboot USB ,now to go into such way you need to connect your device through USB and wait a second or so then press power button and it will show you in RED color.
After that run RUU file through pc by double clicking on file. It will prompt you that it will upgrade your device hboot version,go ahead and click next. and let the process complete. But before all make sure your device has more than 30% of battery. If you encountered any problem,then head over to htc.com and ask for help regarding it. I'm just saying because your device is in Stock mode,nothing has been changed according their standard. Or you may look at here in forum regarding error that you get while running RUU.
If you successfully go through all steps,then your device probably back to life again,unless there isn't any hardware issue. Once you deal with this you may now able to unlock bootloader and root your device. But that's only when you actually done with above mentioned steps.
If some point you don't understand what i'm saying,then from my side i'm SORRY. But you've to spent more time with your device in order to learn it properly.
Click to expand...
Click to collapse
Your instructions were very welcome and gave me the knowledge I needed to proceed, paricularly a sourcs of .exe RUUs rather than the .zip I had found that had no .exe file within.
According to the on screen info, I have installed the Rom I selected successfully. Unfortunately the boot loop remains and it still goes into that when I click on recovery. Seems that this phone is probably cooked.
Whiskeymac said:
Your instructions were very welcome and gave me the knowledge I needed to proceed, paricularly a sourcs of .exe RUUs rather than the .zip I had found that had no .exe file within.
According to the on screen info, I have installed the Rom I selected successfully. Unfortunately the boot loop remains and it still goes into that when I click on recovery. Seems that this phone is probably cooked.
Click to expand...
Click to collapse
Okie. Good sign,that RUU successfully installed. Now time for next step.
-Do you able to boot your device? Or still has bootloop after installing appropriate RUU.
-If you can go into bootloader then just show everything what's mentioned there from top to bottom( hboot version,radio version etc. everything)
Well if stock recovery doesn't work then will try to Unlocked the bootloader and make it Flash custom recovery then.
Right, back at the coal face:
dr.patron99 said:
Okie. Good sign,that RUU successfully installed. Now time for next step.
-Do you able to boot your device? Or still has bootloop after installing appropriate RUU.
-If you can go into bootloader then just show everything what's mentioned there from top to bottom( hboot version,radio version etc. everything)
Well if stock recovery doesn't work then will try to Unlocked the bootloader and make it Flash custom recovery then.
Click to expand...
Click to collapse
It's still not booting. Just loops with a buzz every 10 secs or so, with a white screen and green HTC. Same when I hit recovery. When I plug it switched off into the PC, it switches on by itself into the boot loop.
Bootloader info:
ACE PVT SHIP S-ON RL
HBOOT-2.00.0027
MICROP-0438
RADIO-26.14.04.28_M
eMMC-boot
Sep 7 2011,19:06:24
RUU that I think I installed: RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_Radio_12.65.60.29_26.14.04.28_M_release_225512_signed.exe
Whiskeymac said:
Right, back at the coal face:
It's still not booting. Just loops with a buzz every 10 secs or so, with a white screen and green HTC. Same when I hit recovery. When I plug it switched off into the PC, it switches on by itself into the boot loop.
Bootloader info:
ACE PVT SHIP S-ON RL
HBOOT-2.00.0027
MICROP-0438
RADIO-26.14.04.28_M
eMMC-boot
Sep 7 2011,19:06:24
RUU that I think I installed: RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_Radio_12.65.60.29_26.14.04.28_M_release_225512_signed.exe
Click to expand...
Click to collapse
Get yourself a New Phone. I believe it's a hardware failure. Or if you want to play around more with it,nothing gonna harm it much since device doesn't know when should boot properly. So i advise you either you unlocked the bootloader! not by htcdev but using chinese tool. It does same thing unless if you want to go through long process of typing and creating account sort of troublesome method.
First of all, you need to use Chrome Browser to translate page automatically unless you chinese. then go to www.mgyun.com , Once site loads up completely first thing you'll notice a white box with monitor sign in circle with version 3.4.8, download and install it in your pc. Once that done. Connect your device in what ever stat it is. Or try putting it in bootloader mode,since it doesn't reboot on bootloader. It should detect your device if you have HTC Sync installed.
Once it gets detected,in that program go to settings > look for lock sign > click on it. It will load another window hit yes or follow on screen instructions.After a minute or so your device should reboot with prompt message that you're about to unlock bootloader. Use volume down to select and Power button to confirm. After that it will reboot again. And that's it later on you may go to bootloader you'll see ***UNLOCKED****
Well, If your device let's complete whole process then there is still some life left. I'm saying it because i do have same issue as yours. And solution to it only by replacing motherboard of the device. Which means time to buy a new device!
Well it can do no harm to try this as you say. I am not very impressed with the reliability of this model, or at least its robustness. I still have my original HD. That works, but HTC say it has "something wrong with the motherboard and will pack up in time". This after I sent it back when it was behaving like a mad thing, carrying out all sorts of actions without me touching it.. After hours and weeks rooting it from zero knowledge, and I mean absolute zero, the same problem was there. Only when I changed the charger which was plugged in, did it function normally. The other phone, the one with the boot loop, I bought second hand, when HTC said the first one needed a new motherboard. I told them to destroy the phone, not send it back for another wad of money. They sent it back for free. It works but does not receive weak signals as well as the replacement, and I'm in a weak signal area which means it doesn't work at home at all.
This boot loop problem started when, once again, it was being float charged in my car. I'm coming to the conclusion that they just don't like being on charge for a long time. Also possible that it may have overheated by being in the sun whilst charging.
Another thing I've discovered is that it starts the boot loop also when it is plugged into a charger even when the phone was switched off.
Anyway, thanks for this latest advice, I'm just about to drive across England to pick up a puppy and will be busy getting him settled in at home for a few days, so the phone will have wait until I have the time to focus properly on what I'm doing. I'll report back when I've ploughed through that, downloaded Chrome etc. I think, as you say, it's time to buy a new phone, but I'll still give it a bit of last ditch resuscitation in the hope that I can breath a bit of life back into it.
Thanks again. WM
dr.patron99 said:
Get yourself a New Phone. I believe it's a hardware failure. Or if you want to play around more with it,nothing gonna harm it much since device doesn't know when should boot properly. So i advise you either you unlocked the bootloader! not by htcdev but using chinese tool. It does same thing unless if you want to go through long process of typing and creating account sort of troublesome method.
First of all, you need to use Chrome Browser to translate page automatically unless you chinese. then go to www.mgyun.com , Once site loads up completely first thing you'll notice a white box with monitor sign in circle with version 3.4.8, download and install it in your pc. Once that done. Connect your device in what ever stat it is. Or try putting it in bootloader mode,since it doesn't reboot on bootloader. It should detect your device if you have HTC Sync installed.
Once it gets detected,in that program go to settings > look for lock sign > click on it. It will load another window hit yes or follow on screen instructions.After a minute or so your device should reboot with prompt message that you're about to unlock bootloader. Use volume down to select and Power button to confirm. After that it will reboot again. And that's it later on you may go to bootloader you'll see ***UNLOCKED****
Well, If your device let's complete whole process then there is still some life left. I'm saying it because i do have same issue as yours. And solution to it only by replacing motherboard of the device. Which means time to buy a new device!
Click to expand...
Click to collapse
Related
Hi, everyone.
I'm sorry to yet another person who has almost bricked their phone trying to upgrade it...
After S-OFFing my handset, and trying several different custom ROMs (non of which I was keen on), I discovered that Sky won't allow me to stream from the Sky Go service whilst my phone was rooted. I immediately tried to get the phone back to how it was, and failed dismally...
Now my phone is stuck on a black screen with a triangle in each corner, with the HTC logo on it.
I have spent all day trying to figure this out, and each time I think I've made a little progress, I get greeted with a new error message. I have come here as a last resort.
My HTC Desire was given to me by a friend, and used to be on the Vodafone (UK) network.
I've managed to get the boot loader back to v0.93.0001, but the options aren't all there. The only option I can see is "RUU", which does nothing when I select it.
I've tried flashing with a variety of RUUs, but to no avail. I've even tried using the SDK to manually push the rom.zip to the phone. Originally this failed with a signature check error, and then a boot loader version error, and now I'm stumped on a "remote: 43 main version check fail" error.
The most recent RUU I've tried was RUU_Bravo_Froyo_Vodafone_UK_2.33.161.2_Radio_32.49.00.32U_5.11.05.27_release_157522_signed.exe from shipped-roms.com, but I've had no luck at all.
Here are the vars from my phone:
version: 0.5
version-bootloader: 0.93.0001
version-baseband: 5.11.05.27
version-cpld: None
version-microp: 051d
version-main: 2.35.0.0
serialno: SH11NPL00562
imei: 356409045453555
product: bravo
platform: HBOOT-8x50
modelid: PB9920000
cidnum: VODAP001
battery-status: good
battery-voltage: 4133mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: RUU
commitno-bootloader: dirty-365c78d6
hbootpreupdate: 11
I'd been looking forward to getting this handset, and managed to stuff it up within 3 days. I guess you could say I'm more talented than the average idiot...
I'd really appreciate any help anyone can give me.
Many, many thanks in advance.
click bortaks guid in my sig, think its number [4] u go to
u could also use the 2.3 gb upgrade from HTCDev. that ruu is for all bravo's, brand, region etc. u can download that in bortaks guide aswell, just go down to resourses
jmcclue said:
click bortaks guid in my sig, think its number [4] u go to
u could also use the 2.3 gb upgrade from HTCDev. that ruu is for all bravo's, brand, region etc. u can download that in bortaks guide aswell, just go down to resourses
Click to expand...
Click to collapse
Many thanks for your reply.
I have followed the guide (which I have to say is very well researched and written), but I haven't made any progress.
I have two MicroSD cards, which I tried to use for the goldcard.img. The first attempt (Samsung 2GB) gave me another "remote: 43 main version check fail" error, and the second attempt (SanDisk 2GB) gave me a "ERROR [140]: BOOTLOADER VERSION ERROR". I assume one card is compatible with the goldcard.img (perhaps the SanDisk?), and the other is not.
I can't seem to find the ROM you're referring to on htcdev, either. All I can find are the unlocked HTBOOT images. I've tried the one for Vodafone, and it fails with "ERROR [191]: ROM IS NOT SUPPORTED".
If you could please post a link to the page, I'd really appreciate it.
Thanks again.
Just make sure ur stock hboot, even flash the alpharev downgrader from alpharev site to be sure. Anyway heres the link for the 2.3gb upgrade
http://www.htcdev.com/process/legal_download/152
RSK Sattelite SuperSense4.1
Thanks for your reply.
I'm fairly sure I'm using the stock ROM now because my phone is S-ON. I assume that the only way it can become S-ON after being S-OFF is by flashing it with the stock bootloader?
So far the process has run for longer than it has before, however, it has now been stuck on "Sending..." for the past 30 minutes. The dots are still moving, so I'm pretty sure it hasn't crashed, I'm just not sure how long I should leave it for, or if it's even safe to unplug the USB cable and start again? I have no userdata on the phone that I can't live without. I'd just prefer not to turn it into a brick if I can help it.
I tried the RUU and although it didn't throw any errors, it seemed to get stuck on "Sending...". After 40 minutes, I pulled the plug and tried to install the ROM manually, and it worked!
Many thanks for your help! The XDA forum won't allow me to give you the thanks you deserve, but if you have a PayPal account, feel free to PM me your email address and I'll treat you to a well earnt beer.
Sincere thanks!
Fuzzy.
Sent from my HTC Desire using xda app-developers app
TheFuzzy0ne said:
I tried the RUU and although it didn't throw any errors, it seemed to get stuck on "Sending...". After 40 minutes, I pulled the plug and tried to install the ROM manually, and it worked!
Many thanks for your help! The XDA forum won't allow me to give you the thanks you deserve, but if you have a PayPal account, feel free to PM me your email address and I'll treat you to a well earnt beer.
Sincere thanks!
Fuzzy.
Sent from my HTC Desire using xda app-developers app
Click to expand...
Click to collapse
Lol we're all here to help each other. I dont believe in "donate to me" so buy urself a beer and enjoy
Just so u know, the 2.3gb upgrade PB99IMG in my sig is the same ruu but just a different way to install it. (no need for computer) so if u want just download it and save it on ur computer, just incase anything happens again.
To install the PB99IMG, just put the PB99IMG.zip on ur sdcard then boot into bootloader (vol down + power) and it will find PB99IMG and ask to update? Volume up for yes and just let it finish. So its worth having the PB99IMG saved on ur computer.
RSK Sattelite SuperSense4.1
So I have been out of the XDA loop for a while as I had to send my shiny rooted Verizon HTC One (m7) back for warranty exchange because the sound card went out. The phone they replaced it with was refurbished and already was running KK 4.4. so I was stuck with the POS, until recently, when it took the sense 6 update all by itself, and broke itself!
Celebrate!!! Because they replaced that with a NEW HTC One (m7) that is fully stock, but running all OG software, see below:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 1.12.42.0731
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.10.605.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: X
(bootloader) imei: X
(bootloader) meid: X
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4124mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97af273845
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
However, now that I have been attempting to get my root back (I've missed it sooo much!!!!) I have realized I may have celebrated too soon.
SO my question is: Even though this is the first release version on this phone variant for Verizon (still not able to HTCdev unlock), did they patch the exploits to perm Root, unlock bootloader, S-off all that? Or is it just on the much later versions of the Android OS?
I apologize if this has been discussed elsewhere, but I simply have spent days searching the forums and internet looking for an answer to this, and simply cannot find one. :crying:
I have tried both firewater (weaksauce gains temp root fine, and the temp root method gains root just fine) but when I run firewater it hangs, and rumrunner, which seems like its running just fine, then ends up saying something along the lines of "Failed.....F*&% It!" and begins to run lines and lines of dots. Which I know usually is related to a security or firewall issue, but I have made sure multiple times all of that is absolutely off on my PC, and I have NO android related software (besides adb & fastboot) installed on my PC.
The only other thing I can think of to do is to roll back my HTC drivers to those which would have been the latest when 4.2.2 sense 5 HBoot 1.54 etc.etc. came out, and see if that makes a difference, but I cannot find info as to which drivers those would be either!
So I turn to the trusted community for some help and hopefully answers.
Thanks guys, pre-help, it's always nice to know I can ask!
***********************
UPDATE
***********************
I thought I would run rumrunner again to just give people an exact copy of what it says, every time I run it:
----------------------------------------------------------------------------------------------------------------------------
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (15/120)
Waiting
Test 2: Booting device
Waiting for ADB (29/120)
Device detected.....................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
FATAL: [email protected] it
.....................
----------------------------------------------------------------------------------------------------------------------------
Also, forgot to mention, that since I can use firewater with the temproot method partially sucessfully, I now have a bootloader that is still locked and S-on, but has a ***Tampered*** flag at the top in black.
Try running the 1.10.605.10 signed ruu from the below thread.
http://forum.xda-developers.com/showthread.php?t=2485319
After you do that try rumrunner again. Ensure all firewalls are off (even windows firewall) and any antivirus is disabled (anti malware also). Be sure you download the correct version of rumrunner.
Sent from my One using XDA Free mobile app
Uzephi said:
Try running the 1.10.605.10 signed ruu from the below thread.
http://forum.xda-developers.com/showthread.php?t=2485319
After you do that try rumrunner again. Ensure all firewalls are off (even windows firewall) and any antivirus is disabled (anti malware also). Be sure you download the correct version of rumrunner.
Sent from my One using XDA Free mobile app
Click to expand...
Click to collapse
Ok I will try that.
Would I run it in bootloader RUU mode as if I were S-off and Unlocked or just install like an .apk?
Thanks for the quick response! I will let you know how it all turns out
xenacick said:
Ok I will try that.
Would I run it in bootloader RUU mode as if I were S-off and Unlocked or just install like an .apk?
Thanks for the quick response! I will let you know how it all turns out
Click to expand...
Click to collapse
Just like if you were s-off.
"fastboot oem rebootRUU" be sure to type exactly like that. Caps matter when running oem fastboot commands.
Reason why I suggest running the signed ruu (signed ruus work whilst s-on) is firewater or weaksauce could have modified something that made rumrunner fail. "Tampered" means something in /system or deeper got modified while s-on.
Sent from my One using XDA Free mobile app
Uzephi said:
Just like if you were s-off.
"fastboot oem rebootRUU" be sure to type exactly like that. Caps matter when running oem fastboot commands.
Reason why I suggest running the signed ruu (signed ruus work whilst s-on) is firewater or weaksauce could have modified something that made rumrunner fail. "Tampered" means something in /system or deeper got modified while s-on.
Sent from my One using XDA Free mobile app
Click to expand...
Click to collapse
I just wanted to be sure I was going to flash it in the right area
Doing it right now, crossing fingers!
Thanks!
Whelp....
That did the exact same thing. No go
I'm wondering if it has to do with something with when it gets to this part of the process-
after it says:
Device detected.....................
[-------------------------------------------------**********] <-------------
Where the asterisks turn into underscores/dashes is it supposed to do something else after this? Because when it finishes turning all the asterisks it goes back to this dialogue:
Rebooting into bootloader (again)
Waiting for fastboot (7/120) <----------- Hangs on count 7 for about 60-90 seconds before moving on to the next line-
FATAL: [email protected] it
xenacick said:
Whelp....
That did the exact same thing. No go
I'm wondering if it has to do with something with when it gets to this part of the process-
after it says:
Device detected.....................
[-------------------------------------------------**********] <-------------
Where the asterisks turn into underscores/dashes is it supposed to do something else after this? Because when it finishes turning all the asterisks it goes back to this dialogue:
Rebooting into bootloader (again)
Waiting for fastboot (7/120) <----------- Hangs on count 7 for about 60-90 seconds before moving on to the next line-
FATAL: [email protected] it
Click to expand...
Click to collapse
I know this may seems like a silly troubleshooting question: are you using a USB 2.0 port and stock USB cable? USB 3.0 can cause issues.
Sent from my One using XDA Free mobile app
Uzephi said:
I know this may seems like a silly troubleshooting question: are you using a USB 2.0 port and stock USB cable? USB 3.0 can cause issues.
Sent from my One using XDA Free mobile app
Click to expand...
Click to collapse
Nope, I've seen enough posts on this site to know why that question is warranted....
However, I'm all good in both ways.
Have used, at this point, all 3 USB ports I have available to me on my laptop, have tried both HTC OEM cables, have uninstalled/installed outdated/current drivers, and made doubly sure I have no traces of any HTC Sync, PDANet, or anything else phone=software related where it may enable talking during the process. I'm running soju.exe as admin, with all security on my system OFF, firewall, anti-malware, even am using a guest network I created off my secured network just in case.
Probably missed other things too....
xenacick said:
Nope, I've seen enough posts on this site to know why that question is warranted....
However, I'm all good in both ways.
Have used, at this point, all 3 USB ports I have available to me on my laptop, have tried both HTC OEM cables, have uninstalled/installed outdated/current drivers, and made doubly sure I have no traces of any HTC Sync, PDANet, or anything else phone=software related where it may enable talking during the process. I'm running soju.exe as admin, with all security on my system OFF, firewall, anti-malware, even am using a guest network I created off my secured network just in case.
Probably missed other things too....
Click to expand...
Click to collapse
"Support
#rumrunners on andirc or freenode
Please don't clutter this thread with support issues, it's MUCH easier to help on IRC."
From the rumrunner thread.
Few other things to ensure:
Fast boot disabled. USB debugging enabled.
Other than that, I suggest going to their support on andirc or freenode, because I am lost on what is causing the issue
Sent from my One using XDA Free mobile app
Make sure this is unchecked:
Settings > security > Device administrator > Android Device Manager
santod040 said:
Make sure this is unchecked:
Settings > security > Device administrator > Android Device Manager
Click to expand...
Click to collapse
I did have the device manager, de-selected...
Well just thought I would update you guys who tried to help me :*(
After running rumrunner again, and again, and again trying different settings with regards to different HTC cords, USB ports, re-downloads, reinstall of adb, fastboot, and HTC drivers, and a few others, I'm still stuck.
At this point I have also had to flash the stock signed RUU twice, again, as rumrunner get's somewhere because it will sometimes during the rebooting check start process of sojo.exe get to the fastboot screen and if I glance over, it will have the black ***tampered*** flag!
I mean considering this is so OG, I am startled at how much trouble it's been giving me. When I rooted my first HTC One (m7) still Verizon, I got it to go S-off and unlocked first attempt.
So I have considered trying something new, and wanted to run it by you to see what you thought.
What would potentially happen if I downloaded the signed stock RUU for 2.10.605.1 and tried rumunner again?? Would my current config even allow me to do so? Thoughts? Related ideas?
THANKS!
xenacick said:
I did have the device manager, de-selected...
Well just thought I would update you guys who tried to help me :*(
After running rumrunner again, and again, and again trying different settings with regards to different HTC cords, USB ports, re-downloads, reinstall of adb, fastboot, and HTC drivers, and a few others, I'm still stuck.
At this point I have also had to flash the stock signed RUU twice, again, as rumrunner get's somewhere because it will sometimes during the rebooting check start process of sojo.exe get to the fastboot screen and if I glance over, it will have the black ***tampered*** flag!
I mean considering this is so OG, I am startled at how much trouble it's been giving me. When I rooted my first HTC One (m7) still Verizon, I got it to go S-off and unlocked first attempt.
So I have considered trying something new, and wanted to run it by you to see what you thought.
What would potentially happen if I downloaded the signed stock RUU for 2.10.605.1 and tried rumunner again?? Would my current config even allow me to do so? Thoughts? Related ideas?
THANKS!
Click to expand...
Click to collapse
I think 2.10 is firewater and weaksauce.
Edit- ...... You are right clicking and running as admin, right? Also, you are running win7?
Sent from my HTC6500LVW using XDA Free mobile app
Uzephi said:
I think 2.10 is firewater and weaksauce.
Edit- ...... You are right clicking and running as admin, right? Also, you are running win7?
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
Well I have tried Firewater/Weaksauce & Firewater/TempRoot methods too, I gain temp root no problem in either case, just can't get firewater to get anywhere, it hangs and hang and hangs, and I have to do a hard reboot to retry.
And,
Yep, running everything, every time as admin...and yes am on Windows 7 SP1, Home Premium.
So just to throw $H!T to the wall to see if it sticks, I have been throwing some of these ideas/questions around my head all day.
With regards to the OS version of windows, I do have firewall, defender, and anti-malware all OFF/disabled when I am make any attempt, but just in case have also added soju.exe to the allowed lists. With the exception of the newer Microsoft Security Essentials, as it's newish to me and I don't know how to add exceptions to it yet. I've just been turning it off.
Everything I can find about the point where it stops each time, say it's because of a security issue on the OS or network, anybody have ideas about any OTHER security type programs which may be running services in the background which may prevent the connection from being able to communicate each reboot?
Another thought I had was, would it be worth running it in compatibility mode for say XP SP2 along WITH the ADMIN permissions?
What about turning on network sharing (on the phone) to use the PC network connection for internet? My thinking being with the phone supplying the connection (with all the reboots and such), its causing some kind of hiccup because of reconnection timeout or something?
Lastly, I realized I hadn't asked probably one of the most obvious of questions, as I assumed the where. But I have been downloading and extracting the zipped package directly into my adb/fastboot folder. So when it runs, it does so from inside that environment, and I don't know if it would matter? Or even if the locale matters or not? Could it be the part of the problem too, having the other files in the zipped package extracted and in the same folder, along with the still zipped package when trying to run the exploit?
I appreciate your responses in advance! I feel like each day that passes I get another grey hair!
F#^$*(@)&*% VERIZON!!!!!
GURRRRRRR
Make an ubuntu Linux boot disc and run rumrunner using Linux.
disconnecktie said:
Make an ubuntu Linux boot disc and run rumrunner using Linux.
Click to expand...
Click to collapse
disconnecktie,
I would be fine and willing to try this, however I have never attempted to run any Linux as an OS, HD or otherwise (as you suggest with a boot disc). Could you point me in the right direction on where to find a good tutorial on how to create and run such a disk? Also, which ubuntu Linux version would you suggest that would have the best chance of success alongside my HTC phone version and the Rumunner exploit?
Thanks in advance!!
The ubuntu website has all the info you need for making a boot disc. I personally use 14.04. You should only have to boot into ubuntu from the disc. I don't think you should have to take it much further than that. Put rumrunner on a usb drive or something and then follow the instructions for running it in Linux.
xenacick said:
disconnecktie,
I would be fine and willing to try this, however I have never attempted to run any Linux as an OS, HD or otherwise (as you suggest with a boot disc). Could you point me in the right direction on where to find a good tutorial on how to create and run such a disk? Also, which ubuntu Linux version would you suggest that would have the best chance of success alongside my HTC phone version and the Rumunner exploit?
Thanks in advance!!
Click to expand...
Click to collapse
disconnecktie said:
The ubuntu website has all the info you need for making a boot disc. I personally use 14.04. You should only have to boot into ubuntu from the disc. I don't think you should have to take it much further than that. Put rumrunner on a usb drive or something and then follow the instructions for running it in Linux.
Click to expand...
Click to collapse
Ok I will give it a try in the AM and update the thread on here after to let ya know how it went! ;P
This might be a long shot, but are you using a router that may have built in security? can you temporarily bypass your router and hook your PC straight into the modem?
xenacick said:
Ok I will give it a try in the AM and update the thread on here after to let ya know how it went! ;P
Click to expand...
Click to collapse
Any word on how this went? I just recently got around to trying to get S-Off, and I'm in an extremely similar situation as you. I'm on 1.10.605.10 firmware, but rumrunner is failing in the same exact way as you and I've disabled and even uninstalled all antivirus/firewall software on my Windows 7 PC. I did try running the linux version of rumrunner using an Ubuntu boot disc/Live CD/whatever I made, but rumrunner still failed exactly the same way (i.e. "FATAL: [email protected] it" and then dots after the second "Waiting for fastboot"). Both adb and fastboot seem to be working because I can see my device with both the "adb devices" and "fastboot devices" commands. Just today I used weaksauce to gain root, but haven't yet tried firewater for S-Off. I'll try later tonight, but based on your post, I'm not feeling confident. If you figured it out, would appreciate it if you could post what worked for you.
Not to hijack the thread, but I was able to finally achieve S-Off, unlocked bootloader, the whole shebang, after running into similar walls as OP. Just thought I'd post my full efforts here if OP or anyone else comes looking for info.
As stated before, I was on some old software (kept declining software updates since I'd get around to S-Off/unlock/etc. sooner or later). I was on the 1.10.605.10 firmware. Since rumrunner wasn't working for me, I did the risky thing and took a software update, hoping it would be an incremental update and not a huge rollup of everything VZW has pushed so far, so I could try a different rumrunner version or maybe firewater. I was right, and I ended up on the 1.10.605.15 firmware. So I tried the *.15 version of rumrunner. I did get a little further in the process (messages like "must ferment longer" and "skunky rum is nasty") but it still failed, giving a message about downloading the latest packages from www.rumrunner.us. Obviously, that was not helpful. Also, for some unknown reason, my PC was no longer letting me boot from CD/DVD, so I couldn't try it in linux under the *.15 firmware. As a last ditch effort, I rooted with weaksauce, and tried the firewater method based on a single post/suggestion I found digging through the rumrunner thread. Bingo! I confirmed unlocked and S-Off in hboot. Hope this helps OP or anyone else!
Hi all.
I suspect this question has been asked before and I have found loads on how to do's, but I can't seem to achive what is needed, so any help, however small is greatly appriciated.... he goes.
Customer has brought in an HTC One M8. Details I can give from the Fastboot screen is:-=
***Software Status: Official***
***LOCKED***
M8_UL_CA PVT SHIP S-OFF
CID-111111111 (<---- 8X1'S)
HBOOT-3.10.0.0000
RADIO-1.29.214500021.12G
OpenDSP-V51.2.2-00593-M8974_FO.1015
OS-6.12.401.1
eMMC-boot 2048MB
Dec 17 2015,14:15:48.3
It is stuck in a boot loop that alsways shows the HTC boot screen, reboots to the HTC screen and promptly then to the Android recovery screen:-
Android Recovery
HTC/htc_m8/htc_m8
6.0/MRA58K/buildteam12171409
user/release-keys
Use volume up/down and power
Reboot system now
Reboot to bootloader
Apply update from ABD
Apply update from SD card
Wipe data/factory reset
Wipe cache partition
Power off
_________________________________
Supported API:3
handle_cota_install: install cwpkg to /cache/data/cwtemp/cwpkg.zip
handle_cota_install: install cwprop tp /cache/data/cwtemp/cw.prop
Write host_mode success
handle_cota_install: No CW files. Skip cw installation
Sorry to have to type this in as I cant seam to get images to upload.
Now, this seems to be a common problem and most suggestions are re flash the firmware using RUU. The first stumbling block I am hitting is the phone is not being detected on any PC that I use, by any cable I use, either by Windows ( USB detected sound plays and disconnected plays if I unplug but no detection in device manager, I have loaded the HTC ABD drivers, installed HTC manager and Android studio but again no detection) or on a Mac.
Question is, can I reset this phone back to a working state or should I direct the customer back to a HTC service centre?
BTW the phone phone is a European model and currently on 3.
Thanks in advance.
Marc
PC1staid said:
Now, this seems to be a common problem and most suggestions are re flash the firmware using RUU. The first stumbling block I am hitting is the phone is not being detected on any PC that I use, by any cable I use, either by Windows ( USB detected sound plays and disconnected plays if I unplug but no detection in device manager, I have loaded the HTC ABD drivers, installed HTC manager and Android studio but again no detection) or on a Mac.
Click to expand...
Click to collapse
Try another USB cable, and another port on the PC.
Also, go into bootloader, select fastboot (if not highlighted in red already) using vol keys, and confirm with power button. Then see if the phone's serial number is returned with the command: fastboot devices
PC1staid said:
Question is, can I reset this phone back to a working state or should I direct the customer back to a HTC service centre?
BTW the phone phone is a European model and currently on 3.
Click to expand...
Click to collapse
Its not the Euro version. Its US version, hacked to accept Euro software. Due to this, and SuperCID (11111111) its obviously been modified, and HTC won't honor any warranty (if that is what you are asking).
I also wouldn't be surprised if the back cover was replaced (again, voiding the warranty). What does the model number on the back say?
redpoint73 said:
Try another USB cable, and another port on the PC.
Attempted this with 2 PC's, 1 Laptop all running Windows 7 Pro with SP1 64 bit and a Mac. Tried the cable that came with my Samsung S5 ( Not the USB 3 cable) plus 2 other cables that I use in the workshop and the original cable suppled by the customer. Phone not detected in device manager on any of the PC's, however the plugged in and unplugged sounds do play. Mac sit's idoly twiddleing its thumbs...
Also, go into bootloader, select fastboot (if not highlighted in red already) using vol keys, and confirm with power button. Then see if the phone's serial number is returned with the command: fastboot devices
Went into bootloader and fastboot. only option I have to locate the S/N is via show barcodes. the S/N is:- HT444WM04348
Its not the Euro version. Its US version, hacked to accept Euro software. Due to this, and SuperCID (11111111) its obviously been modified, and HTC won't honor any warranty (if that is what you are asking).
I dont think it would be under warranty as customer reckons it is over 12 months old.
I also wouldn't be surprised if the back cover was replaced (again, voiding the warranty). What does the model number on the back say?
Click to expand...
Click to collapse
Shown on the back is OP6B110 M8x
Hope this gives some more helpfull info.
PC1staid said:
Shown on the back is OP6B110 M8x
Hope this gives some more helpfull info.
Click to expand...
Click to collapse
Now that you mention that, I think there may be an Australian variant (OP6B110) which also has the product ID (M8_UL_CA) indicated on the bootloader screen.
Either way, its not the Euro variant; and its been modified by a previous owner (as mentioned).
Any luck getting USB fastboot working? Once you do, do fastboot getvar all, and post the output (delete IMEI and serial number before posting) so we can verify the MID and make sure you are running the right RUU.
exactly the same problem
Hi.. I have also been facing the same problem since today morning. phone completely conked off and not connecting to pc either. the connecting and disconnecting sound is there but device driver error so not installed. pls help... phone model is OP6B100. Bought from US and being used in India
sonalgirdhar said:
Hi.. I have also been facing the same problem since today morning. phone completely conked off and not connecting to pc either. the connecting and disconnecting sound is there but device driver error so not installed. pls help... phone model is OP6B100. Bought from US and being used in India
Click to expand...
Click to collapse
No, its not the same problem. The OP is in a bootloop, which is very different from the screen not coming on.
Folks need to stop saying "same problem", because it really never never never is. Just a minor detail or 2 that is different, makes a huge impact on the condition and the way forward.
Leave the phone on charger for several hours, and then hold power for 30 seconds of so, and see if you can get the screen to come on.
If the screen doesn't come on, there isn't much we can do.
redpoint73 said:
No, its not the same problem. The OP is in a bootloop, which is very different from the screen not coming on.
Folks need to stop saying "same problem", because it really never never never is. Just a minor detail or 2 that is different, makes a huge impact on the condition and the way forward.
Leave the phone on charger for several hours, and then hold power for 30 seconds of so, and see if you can get the screen to come on.
If the screen doesn't come on, there isn't much we can do.
Click to expand...
Click to collapse
Sorry I meant I am also getting the same screen with phone stuck in bootloop amd not moving beyond this screen.
sonalgirdhar said:
Sorry I meant I am also getting the same screen with phone stuck in bootloop amd not moving beyond this screen.
Click to expand...
Click to collapse
"completely conked off" (your previous words) is not a good description of the above. Misleading, really.
Hold the vol down button during the bootloop cycle. Don't let go until you are on the bootloader screen. Then try to connect with fastboot.
My HTC is having same error after Android 6.0 update.
It's not getting connected to pc.. I bought my phone in USA and now using it in UK.
Called HTC and they said they will not accept US phone for repair even though it's in warranty..
tushard007 said:
My HTC is having same error after Android 6.0 update.
It's not getting connected to pc.. I bought my phone in USA and now using it in UK.
Called HTC and they said they will not accept US phone for repair even though it's in warranty..
Click to expand...
Click to collapse
Hi.. Did u find any solution to the problem. The service center here also refused to take a phone bought outside india.
Hi..
Please find attached the result of 'fastboot getvar all'. i had also shared the same with HTCDev team and the reply is as below:
"Hello Sonal
I sincerely thank you for sending us the information that was requested . According to the information you have provided, I was able to identify the reason why the device can not receive updates at this time. For your device to without any problem , it must have all the original software or settings and STOCK.
To begin , let me explain how our devices are distributed to security S -ON to protect your settings and to ensure proper operation. Security on your device has been disabled ( S -OFF) which has allowed the following parameters change at this time prevent the upgrade is installed
cidnum : 11111111 < ---- this parameter will not get your device updates
Here are the options for you:
Option 1 - Return all device settings to their original settings or STOCK. - First you must change the parameters specified as these were originally. Once this is done, now again to contact STOCK install the operating system.At this time, HTC doesn't officially support obtaining S-Off on our devices. Having said that, I'll be happy to take a look at what's going on and at least point you in the right direction. I know this may cause some limitations in the assistance I am able to provide to you but I am more than happy to do what I can to assist you through your issue . We are happy if you contact us about any problems you might, in any part of their development process. .To begin with, the following websites are some examples where we recommend you start your research on S-Off. http://forums.xda-developers.com http://www.androidcommunity.com http://androidforums.com Please note the above web sites are not operated by HTC. We can not validate or guarantee the information contained therein.
Do not hesitate to reach out to us if you have any questions. You can contact us back via email, using the second link listed below (The one at the end of the sentence "To send a reply to this message, please click here"). "
Can you please help with the next steps to get the phone working again.
sonalgirdhar said:
Please find attached the result of 'fastboot getvar all'.
Click to expand...
Click to collapse
Flash the 6.12.401.4 RUU.
See the download in Post #3 of the following thread, and instruction in Post #17 of that thread: http://forum.xda-developers.com/htc-one-m8/general/marshmallow-6-0-update-htc-m8-european-t3296141
sonalgirdhar said:
i had also shared the same with HTCDev team and the reply is as below:
Click to expand...
Click to collapse
Asking HTC for support by sharing info that indicates your phone was modded, was a bad idea. Of course they are going to say "we don't support this" and "return the phone to stock".
No need to go back s-on or change CID. Just run the RUU as I mentioned.
---------- Post added at 10:06 AM ---------- Previous post was at 10:04 AM ----------
tushard007 said:
My HTC is having same error after Android 6.0 update.
It's not getting connected to pc..
Click to expand...
Click to collapse
USB connection issues are usually due to issues on the PC, not the phone.
Try a different cable, different USB port (as I suggested in a previous post). Install (or re-install) HTC Sync. You may even need to try a different PC (Win7 and USB 2.0 get the best results).
Also, bear in mind that phone needs to be in bootloader-fastboot mode, for fastboot commands to work. Booted into OS or recovery for adb to work.
redpoint73 said:
Flash the 6.12.401.4 RUU.
See the download in Post #3 of the following thread, and instruction in Post #17 of that thread: http://forum.xda-developers.com/htc-one-m8/general/marshmallow-6-0-update-htc-m8-european-t3296141
Asking HTC for support by sharing info that indicates your phone was modded, was a bad idea. Of course they are going to say "we don't support this" and "return the phone to stock".
No need to go back s-on or change CID. Just run the RUU as I mentioned.
---------- Post added at 10:06 AM ---------- Previous post was at 10:04 AM ----------
USB connection issues are usually due to issues on the PC, not the phone.
Try a different cable, different USB port (as I suggested in a previous post). Install (or re-install) HTC Sync. You may even need to try a different PC (Win7 and USB 2.0 get the best results).
Also, bear in mind that phone needs to be in bootloader-fastboot mode, for fastboot commands to work. Booted into OS or recovery for adb to work.
Click to expand...
Click to collapse
@redpoint73 Thank you so much, have been able to update the RUU. Updating apps now
Hi!
Does anyone know about a tool to check (and maybe also fix) a bad NAND/EMMC? This is my story:
This Friday I was sitting in my couch and browsing the web on my M9 (HTC__Y13, Europe version) and suddenly it just reboots itself.
This is normal behavior (at least with my phone, happens now and then), but this time it just kept rebooting itself.
I can boot to FASTBOOT but not to "Download Mode" or "Recovery Mode". If I choose Download/Recovery-Mode, it starts to load but just to reboot itself
again.
Pressing VolUp+VolDwn+Pwr takes me to the FASTBOOT menu.
Choosing "Download Mode" takes me to a black screen with HTC logo in silver. After a couple of seconds, it reboots itself.
Choosing "Recovery Mode" takes me to a black screen with HTC logo in silver. After a couple of seconds it reboots itself.
Pressing VolDwn+Pwr takes me to a black screen with HTC logo in silver. After a couple of seconds, it reboots itself.
Trying to boot to RUU-mode (fastboot oem rebootRUU) gives me the same behavior.
S-ON: YES
Relocked: YES
Thanks in advance!
From getvar-command (looks pretty strange to me)
Code:
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:HT**********
I modified the value on row "(bootloader) serialno:" for this post, value is proper.
I can tell you from the getvar output that the emmc is kaput. It's forgotten what it is. Looks like, from my sherlock skills, it may have an m8 software on there as the serial starts HT where as I'm sure m9's are FA..
Beamed in by telepathy.
shivadow said:
I can tell you from the getvar output that the emmc is kaput. It's forgotten what it is. Looks like it may have been slowly dying over time.
If you live in the USA or taiwan, or have a warranty you can get a replacement from HTC free of charge.
Beamed in by telepathy.
Click to expand...
Click to collapse
Thank you so much for your response!
As I suspected
Unfortunately I'm live (and has bought the phone) in Sweden, so I think an unlocked/relocked bootloader = f*cked. But I will contact HTC support anyway.
shivadow said:
I can tell you from the getvar output that the emmc is kaput. It's forgotten what it is. Looks like, from my sherlock skills, it may have an m8 software on there as the serial starts HT where as I'm sure m9's are FA..
Beamed in by telepathy.
Click to expand...
Click to collapse
I agree with you that the EMMC is probably broken. However, the "HT" has nothing to do with the model of the device. (How to read Serialnumbers)
Very creepy. I'm having the same exact bootloop issue as the OP. Friday evening, got stuck on the bootloop. Earlier in the week, I thought I was stuck but hooked it up to my pc and was able to reboot fine. Now I'm most certainly screwed.
I'm ***software status: Official*** ***UNLOCKED*** ***S-OFF***.
Now I'm not sure my phone is even showing up when connected to my PC. When I'd run "adb devices" no devices would show up, but if I did "htc_fastboot getvar all" I had an output similar or same as the OP. I tried to uninstall/re-install HTC Sync Manager, and install the latest Minimal ADB, and now I can't even get that output as seen above.
Where do I go from here? I had the hardest time putting ViperOne on my phone a year ago. I spent three or four weekends studying the forums here. I need detailed instructions or I'll get lost. Thank you all for your work so far here in the forums. If you want to experiment on my phone to get it functional again please feel free to point me in the right direction. I had hoped this post would help, but like I said, I can't see my phone in task manager. (Also, I'm not sure about step 4., I don't see an MAF32 file in what I extracted from the latest minimal adb files.). Please help!
Download mode and then htc_fastboot getvar all.
Qualcomm makes publicly available software that controls the raw hardware so that the manufacturer can upload their firmware. I can't remember where I saw it but it was only a short google search to find it.
It may help. It may not help.
Beamed in by telepathy.
I left the phone on the bootloader screen, plugged in to the PC. I think it got a solid charge overnight, and I am now able to boot normally. In the interest of making my phone more stable, I've tried the No wipe.zip method as seen here to go from 3.35.401.12 to the M9_4.14.401.7_NoWipe_TWRP3030.zip, followed by a TWRP wipe. My Venom ROM would still be based on the older firmware. Also, download mode screen shows the older firmware OS version. Will this cause problems? What can I do to make my phone stable again?
Joining the flock
Hello all. My first post here. I have the same issue on my m9
Status modified, s-on, locked, security warning.
Can't access download mode or recovery. It gives me the green logo on white background with red warning text ('failed to load... This build is for...').
Adb can't see device.
Issue appeared after cracked display started ghost touching all over. Changed system language and such before I turned it off. I went to unofficial service to replace display/frame set and they said it's locked on bootloader.
From what I see here, others with screwed up NAND experience bootloop and can't access download mode..
I just want to be 100% shure it's bricked forever before selling it for parts. I want to fight for my 'baby' to the very end.
So how can I test this or are there any there any tricks I can use to make it boot/get to download mode?
Thank you!
Later edit: don't know if this means anything, but if I select Reboot to Bootloader, the security warning is missing. It just appears if I user the other options.
Well I see that im not the only one, same model, same problems, I was able to boot twrp using "fastboot boot twrp.img", but it shows 0 mb for internal storage, also trying to repair any partition using e2fsck results on "proces ended with ERROR: 8 unable to reapir data", I also was able to adb push the whole bad_boys custom rom zip without a problem but unfortunately i just recive errors while trying to install it.
groxack said:
Well I see that im not the only one, same model, same problems, I was able to boot twrp using "fastboot boot twrp.img", but it shows 0 mb for internal storage, also trying to repair any partition using e2fsck results on "proces ended with ERROR: 8 unable to reapir data", I also was able to adb push the whole bad_boys custom rom zip without a problem but unfortunately i just recive errors while trying to install it.
Click to expand...
Click to collapse
It seems that I have the same problems as you. Also booted into TWRP and tried to restore various 401 back-up options but without success; partly restores then get lots of red text about unable or failed to mount.....etc.
Did you find a solution to the problem?
ludemon said:
It seems that I have the same problems as you. Also booted into TWRP and tried to restore various 401 back-up options but without success; partly restores then get lots of red text about unable or failed to mount.....etc.
Did you find a solution to the problem?
Click to expand...
Click to collapse
Further to the above, whilst in TWRP I used the command adb shell getprop and in the result noticed that there are references to OmniROM. The main one being [ro.modversion]: [OmniROM-6.0.1-20171209-hima-HOMEMADE]. I assume that someone has previously flashed OmniROM and this has caused the brick.
As far as I know HTC devices are not supported by OmniROM.
Does anyone know if the phone is recoverable from this condition?
Hi,
I read a couple of other threads with similar symptoms but I do not know if I have the same problem. So I think it's better to start a new thread. In any case I hope some expert here can help me.
About 1,5 years ago I bought a secondhand HTC One M8 and it has been working fine up to last Tuesday. I use it to hike (to follow downloaded tracks and record my hike, using GPS, and when I do this I put it into flight mode to not use any more battery than necessary). I keep it in a pocket in my shorts when I hike. Last Tuesday, I was simply walking (not climbing, running or anything of that kind) and it had just started raining, but my phone was in my dry pocket, when I felt it vibrated. It had powered off by itself. I powered it on again, tried to reactivate my hiking application (Alpine Quest) but it didn't register my location nor track my moves. I didn't have any connection and it was stuck in flight mode.
At home, powering off and on, it all of a sudden asked me for a PIN code (I've never secured my phone with a code, and I've never seen this screen before) and it only lets me make emergency calls. I tried 0000 but that didn't work (using 1 of the 3 PIN code attempts... I've 2 left now). Powering it off and on a couple of times, it sometimes gives this screen, but sometimes it also allows me to access my phone without the code (the normal home screen). In doing so I was able to get rid of the flight mode (when it is powered it freezes when powering on or off flight mode, which than becomes greyed out). Sometimes it powers on and off by itself. But I have no connection, no baseband, EMEI is unknown, phone number is unknown.
If any of you has any idea as to solve this porblem, I would appreciate the help !
Thanks !
Judith
Ps Oh and by the way, I'm quite illiterated when it comes to phones... I may understand computers but because with phones the software is hidden and can only be accessed when the phone is rooted (and I already "bricked" my previous unlocked Samsung by trying to root it when it had a problem) I cannot learn and I'm scared I may do something wrong this time too . I find it ridiculous that when you BUY a (unlocked) phone you cannot access the software installed on it (and get rid of xxxxx MB of bloatware that fills up the memory, to name one thing...).
Phone: HTC One M8
Android version: 6.0
HTC Sense: 7.0
Software number: 6.12.401.4
Kernel version: 3.4.0-perf-g708019f
[email protected] #1
SMP PREEMPT
Baseband version: unknown
IMEI: unknown
IMEI SV: unknown
Phone number: unknown
IMSI: unknown
Judiver said:
Ps Oh and by the way, I'm quite illiterated when it comes to phones... I may understand computers but because with phones the software is hidden and can only be accessed when the phone is rooted (and I already "bricked" my previous unlocked Samsung by trying to root it when it had a problem) I cannot learn and I'm scared I may do something wrong this time too
Click to expand...
Click to collapse
What do you mean "I cannot learn"? Anybody can learn! But it requires you to take the time and effort to learn the proper info and methods.
If you don't understand enough to root a phone, then you don't know enough to be messing with the phone's software. This is the main reason they don't let users easily access the operating system (more likely to cause damage then do good).
Judiver said:
Software number: 6.12.401.4
Click to expand...
Click to collapse
If you know how, do fastboot getvar all, and post the results (delete IMEI and serial number, if they appear).
It appears you obtained the info from the phone settings (within OS) which is not a reliable way of obtaining this data.
If you don't know how to do fastboot getvar, at least go to bootloader screen, and confirm OS number, and tell us whether baseband number is listed as well.
Hi Redpoint,
Thank you for your reaction. Sorry for my slow reaction. I've been doing some reading and also finding out how to make a back-up without a connection. I ended up downloading HTC Sync Manager, which didn't want to connect my phone at first, and sometimes still doesn't. I am apparently not the only one who has this problem with HTC Sync Manager but I noticed that since my phone disconnected last week, that when I plug it to my pc with a USB cable (not an original HTC as that was not delivered with my 2nd hand phone...) I get the message that the driver doesn't install. I now sometimes I can connect my phone and sometimes not. This must be related to the problem with the phone, as formerly this never happened, I could always connect my phone to my pc with USB and never got a message about drivers not correctly having been installed. Also my phone powers off and on by itself now.
Off course I can learn ! I wouldn't have asked for help here if I didn't want to learn ! What I meant is that, opposed to computers, a normal user with an unrooted phone (like me) doesn't see nor can he/she access any software on a phone. When I had a problem with my previous phone (a Samsung), I asked for help on this forum but I didn't get any reaction. So I tried to figure things out myself and downloaded a file from the internet to (easily) root the phone. But the program appeared to be crap, it bricked my phone (I think my EMEI was stolen ?). That wouldn't happen on a pc, which is much more fool proof : you can see your system files, run malware and other scans, lots of security facilities are built in, lots ways to get back to a previous state from before messing up, etc. Everything I learnt about computers is done by reading & trying and I am much less afraid of doing something wrong because it is like walking in a city where I've been wandering around many times, seeing things that are either familiar or weird. With the experience of my Samsung in mind, I am afraid of doing something wrong with my HTC now, and especially afraid of downloading from websites that have not been recommended by a trustworthy source. That's all.
I just installed the Minimal ADB and Fastboot (https://forum.xda-developers.com/showthread.php?p=42407269#post42407269) and got this result :
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *****
(bootloader) imei: *****
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.080s
I bought it from Second-hand Phones in the UK in April last year.
Thanks for your help. I appreciate it.
Judith
Ps learned something already
Oh I forgot,
It says
***Software status: Official***
Judiver said:
When I had a problem with my previous phone (a Samsung), I asked for help on this forum but I didn't get any reaction. So I tried to figure things out myself and downloaded a file from the internet to (easily) root the phone. But the program appeared to be crap, it bricked my phone (I think my EMEI was stolen ?).
Click to expand...
Click to collapse
I don't know what Samsung phone (your info is too vague, maybe intentionally so) but there is plenty of info on XDA on how to root all the common Samsung phones. You may have been asking for an old device, where the forum is not very active anymore (the M8 forum itself is pretty quiet, only a few of us "helpers" left anymore. Or maybe asking a question that has already been answered too many times ("how to root" is one of those).
If you downloaded a random root program from websites outside XDA, that is a mistake. My advice would be to stick to XDA, and advice/files from reputable XDA members, and you won't go wrong.
---------- Post added at 09:41 AM ---------- Previous post was at 09:38 AM ----------
Judiver said:
Off course I can learn ! I wouldn't have asked for help here if I didn't want to learn ! What I meant is that, opposed to computers, a normal user with an unrooted phone (like me) doesn't see nor can he/she access any software on a phone.
Click to expand...
Click to collapse
This is a false statement. Linux systems are both computers and PCs. And Linux has root privileges just like Android.
If you are talking Windows specifically, I can tell you having tinkered with both Windows PCs and Android Phones, that phones are far easier to manipulate and restore, than PCs. You just know your way around PCs, than phones.
There are plenty of ways to restore an Android device. You just haven't learned them yet.
---------- Post added at 09:53 AM ---------- Previous post was at 09:41 AM ----------
Judiver said:
I've been searching for fastboot getvar all, but it looks like I need to download a program for that (?) and, as I said, I am a bit afraid of downloading from the wrong websites.
Click to expand...
Click to collapse
By installing HTC Sync, you already have fastboot installed. There are also fastboot/adb installers available on XDA (reputable and used by many) if you use the XDA search function and search "easy fastboot install" or similar search phrase. Also "fastboot guide" will help you find threads on the basics.
Fastboot is mandatory not just for the info I asked for, but also the recovery option I will suggest. So you need to learn how to use fastboot, at least on a basic level. Fastboot is handled through PC's command prompt interface. So if you are experienced with PCs, it really shouldn't be a problem for you to learn.
And when I say "recovery option I will suggest" keep in mind, it is just a clean install of the stock software/firmware. It sounds like your issue may or may not be a hardware failure. But in the even it is, my forthcoming suggestion won't fix your issue. But it's worth trying, to at least see if the problem is in the software/firmware.
redpoint73 said:
I don't know what Samsung phone (your info is too vague, maybe intentionally so) but there is plenty of info on XDA on how to root all the common Samsung phones. You may have been asking for an old device
Click to expand...
Click to collapse
It was indeed a bit of an old device. I didn't mention the model because it isn't relevant for this thread, but it was Samsung Galaxy i9003 S SCL, bought in 2012 (in Spain). It got a problem last year, but, if I remember well, as the software was outdated (and apparently not updated to anything newer?) I wanted to root it to be able to put something more recent on it (hoping to fix the problem at the same time).
redpoint73 said:
If you downloaded a random root program from websites outside XDA, that is a mistake. My advice would be to stick to XDA, and advice/files from reputable XDA members, and you won't go wrong.
Click to expand...
Click to collapse
I fully agree! It was a stupid action and I should have known better. I have enough experience with pc's to know the risks of downloading executable files from shady sources...
redpoint73 said:
You just know your way around PCs, than phones.
Click to expand...
Click to collapse
Well, I'm no expert in pc's but I try and learn, and stuff becomes easier on the go. But I am a blank page when it comes to mobiles phones !
redpoint73 said:
By installing HTC Sync, you already have fastboot installed. There are also fastboot/adb installers available on XDA (reputable and used by many) if you use the XDA search function and search "easy fastboot install" or similar search phrase. Also "fastboot guide" will help you find threads on the basics.
Fastboot is mandatory not just for the info I asked for, but also the recovery option I will suggest. So you need to learn how to use fastboot, at least on a basic level. Fastboot is handled through PC's command prompt interface. So if you are experienced with PCs, it really shouldn't be a problem for you to learn.
And when I say "recovery option I will suggest" keep in mind, it is just a clean install of the stock software/firmware. It sounds like your issue may or may not be a hardware failure. But in the even it is, my forthcoming suggestion won't fix your issue. But it's worth trying, to at least see if the problem is in the software/firmware.
Click to expand...
Click to collapse
I am glad that you think it's a software issue. So now that I have HTC Sync and the Minimal ADB and Fastboot, is that sufficient for what you (I hope) suggest I do next or do I need the full ADB?
Judiver said:
I am glad that you think it's a software issue. So now that I have HTC Sync and the Minimal ADB and Fastboot, is that sufficient for what you (I hope) suggest I do next or do I need the full ADB?
Click to expand...
Click to collapse
I never said I thought it was a software issue. I said it may or may not be a hardware issue. It's worth a try (and probably won't hurt) restoring the full stock software image (RUU). Sometimes this fixes the problem with no connection, sometimes not (such as with a hardware issue).
Just about any fastboot installation will do. In fact, you will need to download the htc_fastboot to flash the RUU file in the following post:
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Note that you do not need to lock the bootloader (first 2 bold type lines in the above guide) since your bootloader is still locked.
Also note that the RUU will wipe all data from the phone. So backup/move anything you want to keep from the phone (photos, personal data, etc.).
redpoint73 said:
I never said I thought it was a software issue. I said it may or may not be a hardware issue. It's worth a try (and probably won't hurt) restoring the full stock software image (RUU). Sometimes this fixes the problem with no connection, sometimes not (such as with a hardware issue).
Just about any fastboot installation will do. In fact, you will need to download the htc_fastboot to flash the RUU file in the following post:
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Note that you do not need to lock the bootloader (first 2 bold type lines in the above guide) since your bootloader is still locked.
Also note that the RUU will wipe all data from the phone. So backup/move anything you want to keep from the phone (photos, personal data, etc.).
Click to expand...
Click to collapse
I'm sorry, I was reading fast and apparently did some 'wishful reading' concerning the software/hardware issue.
In bootloader mode there are a couple of options, like Recovery mode and Factory reset. Couldn't I try this first before loading on a new RUU?
Judiver said:
In bootloader mode there are a couple of options, like Recovery mode and Factory reset. Couldn't I try this first before loading on a new RUU?
Click to expand...
Click to collapse
Those options won't do anything. If they had any possibility to help, I would have mentioned those options. The stock recovery is pretty useless. It will give you options to factory reset (see more info on that, next paragraph), and wipe cache. You can try to wipe cache if you like (won't harm anything) but it won't help your issue, I can guarantee.
In regards to factory reset, many folks have a misunderstanding of what that means. The term "factory reset is somewhat of a misnomer. It won't magically restore the OS. The only way to do that, is to re-install the OS from somewhere, like an RUU. The only thing the factory reset option in bootloader/stock recovery does, is wipe user data.
redpoint73 said:
Those options won't do anything. If they had any possibility to help, I would have mentioned those options. The stock recovery is pretty useless. It will give you options to factory reset (see more info on that, next paragraph), and wipe cache. You can try to wipe cache if you like (won't harm anything) but it won't help your issue, I can guarantee.
In regards to factory reset, many folks have a misunderstanding of what that means. The term "factory reset is somewhat of a misnomer. It won't magically restore the OS. The only way to do that, is to re-install the OS from somewhere, like an RUU. The only thing the factory reset option in bootloader/stock recovery does, is wipe user data.
Click to expand...
Click to collapse
Hi Redpoint,
I downloaded the htc_fastboot.exe and the RUU, but couldn't find a download for the 1.4.3 version of the ADB Installer last night. So today, still no luck, I tried 1.3 and followed the instructions on the links you gave me. At first I thought it hadn't changed anything as it was asking for a PIN again and when connecting to my pc with a USB cable the drivers didn't install correctly (i.e. same 2 symptoms that had occurred when I found myself without a connection). But this time the standard 0000 of my operator worked for the sim card PIN and it appeared I had a connection! But it wouldn't call. After re-installing my wifi connection I started updating all of the software. That took a while. And then restore from HTC Sync Manager back-up and getting all my apps and settings back that the back-up hadn't adressed (the HTC back-up was not very exhaustive... no ringtones, no Whatsapp history...).
During all the updates the first sms I received was spam and this telephone, for some reason, can blacklist calls but not sms. Lots of bloat ware you cannot get rid of but no sms blocker! And I forgot which sms blocker app (free, no ads) I had downloaded previously. Hmmm... I'll keep looking for something suitable...
But that aside, all seems to work as it should now (fingers crossed) !
So thanks a lot for your help. It helped me greatly :good::good:.
And I learned, although I still think it is a bit of a drastic procedure to do every time a phone has a problem. You have no idea what the problem is, severe or minor, and have no clue where to look! If every time I have a problem with my pc I need to re-install Windows, I wouldn't be doing much other than just that! Mobile phones (at least as far as I know) seem to lack a system where you can do a scan and repair system files, or a way to find out where the problem is and replace just a part (leaving your stuff in tact). All I read everywhere on android websites is about flashing and rooting, hardly ever less drastic solutions... But then... that's the opinion of someone you just made her first steps in the Android world ...
Judiver said:
I downloaded the htc_fastboot.exe and the RUU, but couldn't find a download for the 1.4.3 version of the ADB Installer last night.
Click to expand...
Click to collapse
You already has adb installed when you installed HTCSync. And again when you used the minimal fastboot/adb installer. I mentioned as much earlier. Any of these would work. Not sure why you tried installing adb yet again (3rd separate installation).
In any case, it sounds like you sorted it out, so glad the RUU helped.
Judiver said:
And I learned, although I still think it is a bit of a drastic procedure to do every time a phone has a problem.
Click to expand...
Click to collapse
What you experienced was probably a pretty serious issue, and not that common. I used the M8 as my daily driver for over 3 years, and never had to use the RUU to recover from such an issue.
redpoint73 said:
You already has adb installed when you installed HTCSync. And again when you used the minimal fastboot/adb installer. I mentioned as much earlier. Any of these would work. Not sure why you tried installing adb yet again (3rd separate installation).
I wasn't sure whether the minimal fastboot / HTC Sync was enough to install a RUU.
redpoint73 said:
What you experienced was probably a pretty serious issue, and not that common. I used the M8 as my daily driver for over 3 years, and never had to use the RUU to recover from such an issue.
Click to expand...
Click to collapse
We will never know what the problem was, but I'm very happy it is gone Thanks for helping me out Redpoint.
Click to expand...
Click to collapse