How to resolve bootloop in a S-ON desire - Desire Q&A, Help & Troubleshooting

Hi there,
I've got a desire that keeps looping on the HTC screen. Stays there for a few seconds and then restarts.
I can go into the HBOOT menu and FASTBOOT mode, I can easily access it through the fastboot from windows as well. But I wasn't able to get revolutionary to detect it. (I guess it needs the device to be in the OS which can't happen cuz of the boot loop).
I tried to fastboot boot into 4ext recovery through recovery.img file it says:
downloading 'boot.img'...
OKAY [ 0.563s]
booting...
FAILED (remote: not allowed)
finished. total time: 0.568s
When I try to fastboot flash an img it says:
sending 'recovery' (3784 KB)...
OKAY [ 0.564s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.227s
I also can't use the method on htcdevs for unlocking the bootloader cuz it says :
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.009s
Here's my fastboot vars dump:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.02.0001
(bootloader) version-baseband: 5.17.05.23
(bootloader) version-cpld: None
(bootloader) version-microp: 031d
(bootloader) version-main: 3.14.405.1
(bootloader) serialno: HT047PL00475
(bootloader) imei: 357841032013118
(bootloader) product: bravo
(bootloader) platform: HBOOT-8x50
(bootloader) modelid: PB9920000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3982mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: a7cdbe26
(bootloader) hbootpreupdate: 11
all: Done!
finished. total time: 0.030s
I've also tried creating a goldcard but I can't read the goldcard's CID from windows, none of the applications work for me, even when I am using a card slot on my laptop and not a USB card reader.
Can anyone guide me here?
I am pretty much banging my head on the wall right now
Thanks a ton.

Did you unlock your bootloader?
Two beer or not two beer, that's the question

Nope, I couldn't unlock the bootloader cuz I couldn't complete the htcdev tutorial.
Neither could i use revolutionary

At this point RUU would be safest bet
Try the 2.3.3 gingerbread RUU

eddiehk6 said:
At this point RUU would be safest bet
Try the 2.3.3 gingerbread RUU
Click to expand...
Click to collapse
Great!
So, looking at my fastboot vars dump above, can you recommend a link for the RUU, cuz I've tried a number of RUUs but most of them give that "you need to upgrade" message and don't work .

eddiehk6 said:
At this point RUU would be safest bet
Try the 2.3.3 gingerbread RUU
Click to expand...
Click to collapse
In fact, I am trying this one: http://www.htcdev.com/process/legal_download/152 as mentioned in the thread http://forum.xda-developers.com/showthread.php?t=1931014.
Lets hope it works.
Is this the right one?

shabeepk said:
Nope, I couldn't unlock the bootloader cuz I couldn't complete the htcdev tutorial.
Neither could i use revolutionary
Click to expand...
Click to collapse
Why can't you use revolutionary?
Your hboot is supported and you have obviously fastboot working.
So this should be the easiest method for you to unlock and get s-off!

tom0769 said:
Why can't you use revolutionary?
Your hboot is supported and you have obviously fastboot working.
So this should be the easiest method for you to unlock and get s-off!
Click to expand...
Click to collapse
Revolutionary stays stuck at "waiting for device". I don't know why but for some reason it does. It seems to be that it needs the phone to be in the OS loaded with usb debugging enabled.
No?

shabeepk said:
In fact, I am trying this one: http://www.htcdev.com/process/legal_download/152 as mentioned in the thread http://forum.xda-developers.com/showthread.php?t=1931014.
Lets hope it works.
Is this the right one?
Click to expand...
Click to collapse
:S I downloaded the RUU, and now it keeps saying ur battery is less than 30% ...

eddiehk6 said:
At this point RUU would be safest bet
Try the 2.3.3 gingerbread RUU
Click to expand...
Click to collapse
Eddie,
Do you think you could help me with this battery issue?
I downloaded the RUU, and now it keeps saying ur battery is less than 30%, even though I think I've charged the battery, the charge LED shows green and fastboot vars say:
(bootloader) battery-status: good
(bootloader) battery-voltage: 4187mV
Do you know what might be wrong ?

shabeepk said:
Eddie,
Do you think you could help me with this battery issue?
I downloaded the RUU, and now it keeps saying ur battery is less than 30%, even though I think I've charged the battery, the charge LED shows green and fastboot vars say:
(bootloader) battery-status: good
(bootloader) battery-voltage: 4187mV
Do you know what might be wrong ?
Click to expand...
Click to collapse
Okay, after trying for a few hours I was finally able to run the RUU... some how :S. I really don't know how.
However, the update process went smooth, no issues, BUT ! :s the bootloop is still there.
Do you think this might be a hardware fault? Do you think this phone doesn't have its actual stuff i.e. the ROM. the RADIO and HBOOT? Do you think I should check other info on the phone tag or something to guess the correct firmware?
This RUU seemed like an all Desire one. No ?
Dead end ... :S

So the RUU successfully flashed but it still won't even boot? Strange
Try revolutionary again, did you install the relevant hboot drivers? Find the revolutionary.io documentation page, instructions should be on there

eddiehk6 said:
So the RUU successfully flashed but it still won't even boot? Strange
Try revolutionary again, did you install the relevant hboot drivers? Find the revolutionary.io documentation page, instructions should be on there
Click to expand...
Click to collapse
Yes, I know its very strange :S
I did try that, however, it wasn't that simple. The drivers present on the revolutionary website didn't detect my device in HBOOT, it was only detecting the device in FASTBOOT, and in FASTBOOT revolutionary still didn't detect the device.
Then I had to download the altered driver and then install it manually. Now My device is detected in both; Fastboot and HBOOT mode. But revolutionary still can't detect it, in neither of the modes.
Any Idea why ? And what I may have done wrong there.

Try and follow this exactly, see if it makes any difference. The video helps
http://theunlockr.com/2011/08/02/ho...android-phone-using-the-revolutionary-method/

eddiehk6 said:
Try and follow this exactly, see if it makes any difference. The video helps
http://theunlockr.com/2011/08/02/ho...android-phone-using-the-revolutionary-method/
Click to expand...
Click to collapse
Tried that, but the problem I am probably facing is that to gain s-off, revolutionary needs to phone to be in USB debugging mode i.e. adb mode with the OS running ofcourse. While I can't get past HBOOT / FASTBOOT. So revolutionary ain't working for me.
I don't know what to do now.
Any suggestions?

ah...
Only thing I can think of is keep trying the RUU until it boots properly.
Print out any error messages if it has any.

Related

[Q] Flashing Recovery - Stuck

Was helping my friend install a custom rom
I unlocked the bootloader at HTCDev.
Code:
***UNLOCKED***
ENDEAVORU PVT SHIP S-ON RL
HBOOT- 0.95.0000
CPLD - None
MICROP - None
RADIO - 1.1204.105.14
eMMC - bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM PATH : OFF
May 8 2012, 21:32:10
But I can't seem to flash recovery?
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash recover
y recovery-clockwork-touch-5.8.4.0-endeavoru.img
sending 'recovery' (5742 KB)...
And then nothing happens, waited about 10+ minutes. Any idea what's up?
Thanks
Bump
Should I have installed an RUU prior to unlocking?
eRadicant said:
Bump
Should I have installed an RUU prior to unlocking?
Click to expand...
Click to collapse
Make sure you're in fastboot USB mode in hboot... Also ensure in cmd type...
cd c:/(directory of fastboot folder)
Mine would be...
cd c:/android
Then...
fastboot flash recovery (nameofrecovery).img
Sent from my HTC One X
smidgeox said:
Make sure you're in fastboot USB mode in hboot... Also ensure in cmd type...
cd c:/(directory of fastboot folder)
Mine would be...
cd c:/android
Then...
fastboot flash recovery (nameofrecovery).img
Sent from my HTC One X
Click to expand...
Click to collapse
Thanks for replying but I'm pretty sure I did that part right.
I don't think I would have got this line otherwise:
Code:
sending 'recovery' (5742 KB)...
eRadicant said:
Thanks for replying but I'm pretty sure I did that part right.
I don't think I would have got this line otherwise:
Code:
sending 'recovery' (5742 KB)...
Click to expand...
Click to collapse
You're right, about the commands, but you'd get that if you weren't in fastboot usb as well...
It's called process of elimination good luck... lmao.
smidgeox said:
You're right, about the commands, but you'd get that if you weren't in fastboot usb as well...
It's called process of elimination good luck... lmao.
Click to expand...
Click to collapse
Well I was actually directing my friend to do it over a Skype/TeamViewer call, so maybe he wasn't actually in fastboot usb when I sent it.
I assumed that the sending message meant he was in it.
I'll try again with him tomorrow, thanks. (Out of thanks for the day)
Edit:
One more thing, are there any benefits of running an RUU first (my CID is HTC__023).
And if so, what would the process be considering I have already unlocked the bootloader?
eRadicant said:
Well I was actually directing my friend to do it over a Skype/TeamViewer call, so maybe he wasn't actually in fastboot usb when I sent it.
I assumed that the sending message meant he was in it.
I'll try again with him tomorrow, thanks. (Out of thanks for the day)
Edit:
One more thing, are there any benefits of running an RUU first (my CID is HTC__023).
And if so, what would the process be considering I have already unlocked the bootloader?
Click to expand...
Click to collapse
Running the ruu would flash everything back to stock as well as wiping all data such as apps, contacts etc, so best to back up first if you're considering this that will also flash the recovery you mentioned earlier, I THINK you'd need to relock the bootloader to run a ruu (not certain).
You'd just do the same, run the ruu on your computer (or friends), I suggest again to be in fastboot USB mode although I'm not certain this is essential, I just do it to be extra sure that the process will pick the device up
Sent from my HTC One X
smidgeox said:
Running the ruu would flash everything back to stock as well as wiping all data such as apps, contacts etc, so best to back up first if you're considering this that will also flash the recovery you mentioned earlier, I THINK you'd need to relock the bootloader to run a ruu (not certain).
You'd just do the same, run the ruu on your computer (or friends), I suggest again to be in fastboot USB mode although I'm not certain this is essential, I just do it to be extra sure that the process will pick the device up
Sent from my HTC One X
Click to expand...
Click to collapse
Yeah I did a search, and found a thread that seems to be relevant. So it is only if wanting to revert to stock, nothing else (no other benefits)? Hopefully someone can clarify
Still unable to flash recovery.
Bootloader definitely unlocked.
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot oem readcid
...
(bootloader) DEBUG: cid: HTC__023
OKAY [ 0.017s]
finished. total time: 0.019s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5a
(bootloader) version-bootloader: 0.95.0000
(bootloader) version-baseband: 1.1204.105.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.728.12
(bootloader) serialno: HT24EW118901
(bootloader) imei: 356581040178625
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4611000
(bootloader) cidnum: None
(bootloader) battery-status: good
(bootloader) battery-voltage: 3864mV
(bootloader) devpower: 59
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.899s
When I try and flash recovery nothing happens on the phone, can't use Vol up/down. Even after I cancel the operation in cmd I can't use the buttons or fastboot commands.
I double-checked md5 of recovery as well.
bump
Have you tried a different USB cable/port?
Michealtbh said:
Have you tried a different USB cable/port?
Click to expand...
Click to collapse
Yep
Can you flash anything? A kernel for example?
Michealtbh said:
Can you flash anything? A kernel for example?
Click to expand...
Click to collapse
I can try but how would I revert back to my current stock kernel?
Try this tool
http://forum.xda-developers.com/showthread.php?t=1734365
Sent from my HTC One X using xda premium
joewong1991 said:
Try this tool
http://forum.xda-developers.com/showthread.php?t=1734365
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Doesn't get past 'Flashing recovery'.
In fact, the computer bluescreens after a minute.
edit:
Tried twrp as well, same result.
I'm getting the same thing. One Click and flash recovery in CMD both just freeze and don't do anything.
Do you have framework 3.5 installed on your pc theres a link in the oneclick op
Sent from my HTC One X using xda premium
joewong1991 said:
Do you have framework 3.5 installed on your pc theres a link in the oneclick op
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Yeah and it's my friends computer
I have a feeling it might be all the random security programs he has installed
I told him to try on a different computer when he can get hold of one
eRadicant said:
bump
Click to expand...
Click to collapse
hi
dont get it u want to install CWM or stock recovery
anyway see this use the tool it is easy
link : http://forum.xda-developers.com/showpost.php?p=27913286&postcount=1
u can also read this post by me hope it helps
link : http://forum.xda-developers.com/showpost.php?p=32368798&postcount=112

Computer won't connect to phone with updated drivers.

So yeah I think I really screwed the pooch on this one.
Here's what's going on.
-My stupid self tried to flash CM10 with a HBOOT v 1.14. Yeah... save it. I know.
-Now I've gotten so far into this thing that my computer won't recognize my phone in order to utilize fastboot to total wipe and retry to run the RUU.
-Computer has been updated with current drivers. I can get into bootloader, but anything I try after that is unable to be done. Cannot get into recovery, if it's even still there. I tried to reflash TWRP, unsuccessfully. When I try to even boot into recovery, it gets stuck on HTC's boot splash screen.
CID: 1111111
HBOOT: 1.14
Relocked
I am totally lost on this. I just want to get it back working ASAP.
do you have a nandroid backup?
robchongke said:
do you have a nandroid backup?
Click to expand...
Click to collapse
I don't. My dumbass self didn't make one.
And anytime I use the toolkit, to do ANYTHING, *device not found*. So i've royally screwed something up. Even after getting all the drivers. I think.
More info: version: 0.5
version-bootloader: 1.14.0002
version-baseband: 0.19as.32.09.11_
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: HT29TW302342
imei: 359691048634839
product: evita
platform: HBOOT-8960
modelid: PJ8310000
cidnum: 11111111
battery-status: good
battery-voltage: 4107mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 1a7fdca3
hbootpreupdate: 11
gencheckpt: 0
KMiracle1984 said:
I don't. My dumbass self didn't make one.
Click to expand...
Click to collapse
if TWRP dont work maybe try CWM.
maybe you flash the wrong custom rom. this thread is for endeavour(international version) yours is evita, that's htc one xl.
robchongke said:
if TWRP dont work maybe try CWM.
Click to expand...
Click to collapse
I would, if I could get it to respond. I get notihing in either fastboot or through the toolkit.
The computer does it's beeping when you connect, but nothing happens.
Attempting to force a boot.img to the phone....
sending 'boot' (5248 KB)...
OKAY [ 0.889s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.274s
You are in the wrong forum mate, go to the HTC one XL forum. This is all for the endevouru !

			
				
Blaine999 said:
Click to expand...
Click to collapse
What's the matter mate.....trying to gather posts or what ?
Please bring something to the table other than a rolleyes !!! :thumbdown:
This is the second thread already ......

[Q] [RUU] Error: 152. Unable to Restore TMob One M8

Hi, thanks for reading.
I was running the latest version of CM on my One M8. Decided I wanted to revert to stock ROM to regain HTC camera and wifi calling functionality. Figured an RUU would be the easiest way.
Here's where I probably screwed up. Downloaded and ran the RUU for ver. 2.xxx from HTC. Forgot to relock bootloader, but it rebooted early back into CM no problem. Relocked bootloader. Ran again.
I should have known to pause when I saw that my version was 1.5xx but it seemed fine with updating versions as part of the process.
Then it failed again, error 152. Was able to reboot into CM again this time.
I did some googling and reading and saw one guy say that he was able to fix by simply running the RUU again once it was in the "four exclamation marks in triangles" screen, which is where I was after the next try, so I ran again. Another error 152.
So finally I realized maybe I needed the 1.5xx RUU. DL'd that, tried running, "error, wrong version." Because now it thinks my phone is on ver 2.xxx.
Now I can't get the phone to boot into recovery or into bootloader. No clue where to go from here. I'd really appreciate your help. Gosh I screwed up.
The last lines in the RUU log (1.5xx) are:
Code:
<T205408><DEBUG><OUT>Execution time is 6(s)</OUT>
</DEBUG></T205408>
<T205408><DEBUG><OUT>FAIL43 main version check fail</OUT>
</DEBUG></T205408>
<T205408><DEBUG><OUT>FAILED (remote: 43 main version check fail)</OUT>
and the prior try, RUU log 2.xx:
Code:
<T202916><DEBUG><OUT>(bootloader) [RUU]WP,system,37</OUT>
</DEBUG></T202916>
<T202917><DEBUG><OUT>(bootloader) [RUU]WP,system,42</OUT>
</DEBUG></T202917>
<T202939><DEBUG><OUT>(bootloader) ...... Failed</OUT>
</DEBUG></T202939>
<T202941><DEBUG><OUT>(bootloader) current_image_number=0</OUT>
</DEBUG></T202941>
<T202941><DEBUG><OUT>Execution time is 216(s)</OUT>
</DEBUG></T202941>
<T202941><DEBUG><OUT>FAIL51 partition update fail</OUT>
</DEBUG></T202941>
<T202941><DEBUG><OUT>FAILED (remote: 51 partition update fail)</OUT>
</DEBUG></T202941>
<T203947><DEBUG><CMD>adb kill-server</CMD>
</DEBUG></T203947>
<T203948><DEBUG><OUT />
</DEBUG></T203948>
</LOG>
Thanks.
Update 1: can recognize device using "fastboot devices" but not "adb devices." haven't tried pushing/pulling anything yet. Saw someone in another thread tried installing via command line. Not sure which .zip I should use, as there are a ton of options on XDA, or if this is what I should try next.
Update 2: there are seemingly two versions of the "four exclamation points" screen: one is dim and has the orange led showing and the other is bright without led. Bright without LED is what I got after "flashboot reboot-bootloader". Worried that the bright one may deplete battery.
3: Since I can't otherwise boot into a recovery, should I try to flash a recovery?
4: Not sure if this is useful but:
Code:
getvar version-main is indeed listed as 2.22.531.5
phone CID T-MOB010
phone MID 0P6B13000
5: Phone was S-ON. Wasn't able to get S-OFF using the free method.
6: Was reading another thread with similar error (but One X), this seemed to be useful to the one guy:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.213311491.03G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.22.531.5
(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: 0P6B13000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.036s
7: Tried to flash a stock recovery:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery Tmo-M8-2
.22.531.5-recovery.img
target reported max download size of 1830612992 bytes
sending 'recovery' (24576 KB)...
OKAY [ 1.533s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 2.430s
8: Tried to create some RUU .zips per this method http://forum.xda-developers.com/showthread.php?t=2534428 but the zips say that archive is corrupted. EDIT: MD5's for the .exe's do check out.
9: Used a zip repair to repair those RUU .zip's. Noticed that their android-info files have "hbootpreupdate:12" but my phone has "hbootpreupdate:11" might that be an issue?
Sad Edit: I tried some stuff, nothing seemed to work. Freshly downloaded from an alternative mirror the 2.2xx RUU and booted into RUU via fastbooth before running it. Everything said it went perfectly "CONGRATULATIONS ROM UPDATED! Rebooting!" etc.
My phone is bricked. Never woke up from that reboot. My computer keeps trying to recognize the device via usb, but nothing.
I didn't think you could use unsigned zips with s-on. Also you couldn't flash stock recovery because your boot loader was locked. If your boot loader wasn't locked it would be worked. So it doesn't show anything in fastboot anymore? Have you tried charging it them plugging back up to computer to see if fastboot will recognize it again?
grim489 said:
I didn't think you could use unsigned zips with s-on. Also you couldn't flash stock recovery because your boot loader was locked. If your boot loader wasn't locked it would be worked. So it doesn't show anything in fastboot anymore? Have you tried charging it them plugging back up to computer to see if fastboot will recognize it again?
Click to expand...
Click to collapse
Yeah I tried unlocking the bootloader while fastboot was still recognizable, but it wouldn't work.
Not sure about the unsigned zips thing. Would that also go for the RUU? I thought those were signed/straight from HTC.
I'll try it once more, but it should have been fully charged last time I gave it a try. Computer shows an intermittent "QHSUSB_Bulk" but not sure where to go from there. Found threads for other HTC phones and tried their methods, but it got to the point where the one guy was supposed to go through Ubuntu to manually install individual .imgs to the phone, but I think he had somehow managed to get fastboot to work.
Ruu is straight from HTC they are .exe files. If it is an ruu.zip I think that only works with s-off. Hm I'm not sure what do to either, I was thinking maybe it just needed to force reboot then press power and volume down for hboot/fastboot I don't understand why it wouldn't just reboot.
grim489 said:
Ruu is straight from HTC they are .exe files. If it is an ruu.zip I think that only works with s-off. Hm I'm not sure what do to either, I was thinking maybe it just needed to force reboot then press power and volume down for hboot/fastboot I don't understand why it wouldn't just reboot.
Click to expand...
Click to collapse
Yeah it's especially weird because I thought with S-ON it was supposed to be hard/impossible to override ?boot.ini (not sure, don't quote me on that) anyway. But yep, won't boot at all.

HTC m8 not starting up correctly. Tried everything i can think of and find.

Hello there!
I have now searched and searched and come upon many great threads in this massive forum however i have yet to find a solution to my current problem. Every time i have went here i have always managed to find something to help me fix my phones over the years but this this time I've hit a wall it seems.
What happened was that my phone started to crash the google apps like gallery etc. No big deal at first but then i decided to do a factory reset thinking that might fix the problem but then my phone just starts up to the HTC logo and throws several different error messages that Google.xxx.xxx could not start/has crashed. IF i click these away they appear after a while again and the phone will be stuck like that.
I can start the phone in fastboot mode to be able to use ADB etc..
The phone is currently bootloader unlocked and with S-on
Now this is what i have done:
First of all the phone wasn't in debugging mode when it crashed so I'm guessing its still not which might complicate the matter further.
* Using a TWRP.img file i managed to get the phone in to the TWRP mode on the phone. (Fastboot boot TWRPfilename.img)
I do not have any TWRP files on my phone nor any apps this was all from the files on the PC. I just mention this because thats the only sign of life the phone has given me so far.
*I tried to go in from the adb shell and enabling it using the following code:
Adb shell
echo "persist.service.adb.enable=1" >>/system/build.prop
echo "persist.service.debuggable=1" >>/system/build.prop
echo "persist.sys.usb.config=mass_storage,adb" >>/system/build.prop"
reboot
I have no idea as to if it worked or not but the phone rebooted again.
* Tried to reflash with the right RUU for my phone with the right CID thanks to guides on this forum -- i get error 159 (this is because the CID is wrong from what ive read in other threads)
* Tried changing the CID to 11111111 but that did not work i got another error doing that:
C:\adb>fastboot oem writecid 11111111
...
(bootloader) SecuritySDInit: counter = 3
(bootloader) m8_init_sd, SD card already power on
(bootloader) [SPEW] GPIO 0 status is 0
(bootloader) sdhci_open: id=0
(bootloader) Initializing MMC host data structure and clock!
(bootloader) mmc slot#2 clock enabled
(bootloader) sdhci_set_clock: slot 2, freq 192000000
(bootloader) GPLL0 is enabled
(bootloader) clock_update_cfg_sd is done
(bootloader) sd clock set done
(bootloader) sdhci_set_bus_width: bus width 0
(bootloader) sdhci_clk_supply: freq 400000
(bootloader) Decoded CID fields:
(bootloader) Manufacturer ID: 2
(bootloader) OEM ID: 0x544d
(bootloader) Product Name: SA16G
(bootloader) Product revision: 1.1
(bootloader) Product serial number: 37A24E6D
(bootloader) Manufacturing date: 10 2013
(bootloader) sdhci_clk_supply: freq 50000000
(bootloader) sdhci_set_bus_width: bus width 1
(bootloader) Done initialization of the card
(bootloader) erase_grpsize: -16777216
(bootloader) erase_grpmult: 261077976
(bootloader) wp_grpsize: 0
(bootloader) wp_grpen: 0
(bootloader) perm_wp: 0
(bootloader) temp_wp: 0
(bootloader) [Tuxera][Error] No exFAT partition found
(bootloader) [FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
(bootloader) [JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 0.132s]
finished. total time: 0.132s
* Tried flashing from a .zip file with the fastboot commands.
ALL of these things I have tried with the bootloader locked and unlocked. (if this is any important info)
The phone ran the 6.12.401.4 version at the moment of the crash and that's what shows in the RUUs ive tried as well. Also the phone is not rooted.
Now is there a way to completely flush the phone out of any info and just reinstalling it like you can do with windows on a PC for example since whatever i try is met by an error message or a failed flash etc..?
some more info about the phone from getvar:
(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) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__Y13
(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.028s
1. remove your serial & imei no. on your post
2. http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
3. relock bootloader with command -
fastboot oem lock
fastboot reboot-bootloader
4. http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Thank you for your fast reply!
I have removed the lines from the post as you said and tried your links unfortunately without success. This is why im hoping you like a challange! hehe.
This is the result from the cmd when trying to flash the new RUU:
C:\Users\Genocide\Desktop\RUU>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.010s]
finished. total time: 0.011s
C:\Users\Genocide\Desktop\RUU>htc_fastboot flash zipp RUU.zip
sending 'zipp' (1687272 KB)... OKAY
writing 'zipp'... (bootloader) signature checking...
FAIL12 signature verify fail
FAILED (remote: 12 signature verify fail)
Execution time is 109(s)
C:\Users\Genocide\Desktop\RUU>htc_fastboot flash zipp RUU.zip
sending 'zipp' (1687272 KB)... OKAY
writing 'zipp'... (bootloader) signature checking...
FAIL12 signature verify fail
FAILED (remote: 12 signature verify fail)
Execution time is 109(s)
I followed your steps 1 by 1 downloaded all needed files and installs etc... Something is terribly wrong with my device it seems.
Any further ideas?
Did you skip no.3 ?
Why it is zipp not zip ?
Try again ..
If still fails, tomorrow I'll give you another method.. already in bed.
oh! ive done goofed!
It was my bad with some **** spelling there.
IT WORKED!!
I thank you sooooo much from the bottom of my heart I was sure my phone was unsaveable for a moment.
what was the difference with that RUU and the ones I've tried before? I must have tried like 4 different ones in the end out of desperation.
or was it the fastboot that was the trick?
I'm just curious on how you could spot the problem so that i can learn more about how it works.
Thanks again! Truly great work!
Sambeg said:
what was the difference with that RUU and the ones I've tried before? I must have tried like 4 different ones in the end out of desperation.
or was it the fastboot that was the trick?
Click to expand...
Click to collapse
We can't say if the RUUs you tried were correct or not, as you didn't give any specific on those (file names, where you found them, etc.).
But you do need the htc_fastboot to run the RUU.zip with fastboot command, the "generic" fastboot.exe does not work.
And you absolutely need to have a LOCKED or RELOCKED bootloader to RUU with s-on (this requirement is bypassed with s-off). So you were also compounding one wrong thing with another (when trying to flash RUU with bootloader UNLOCKED) making it even less likely you would have the successful combination of variables.
Unlocked bootloader is okay to OTA, so that is where I think some folks get confused on when to have the bootloader locked or not. But OTA and RUU are two very different things (with different requirement), and its important to remember that fact.
redpoint73 said:
We can't say if the RUUs you tried were correct or not, as you didn't give any specific on those (file names, where you found them, etc.).
Click to expand...
Click to collapse
I found them all in XDA guides/lists of stock roms, checked with my CID and European versions etc...
redpoint73 said:
But you do need the htc_fastboot to run the RUU.zip with fastboot command, the "generic" fastboot.exe does not work.
Click to expand...
Click to collapse
I think this is where all else failed since all the ones i tried had either the ADB or a file called only Fastboot.exe not this one that said HTC_fastboot.exe
redpoint73 said:
And you absolutely need to have a LOCKED or RELOCKED bootloader to RUU with s-on (this requirement is bypassed with s-off). So you were also compounding one wrong thing with another (when trying to flash RUU with bootloader UNLOCKED) making it even less likely you would have the successful combination of variables.
Click to expand...
Click to collapse
I tried all the solutions in both locked/relocked state just to be sure i had no real understanding of this before but I am now enlighten thanks to you
redpoint73 said:
Unlocked bootloader is okay to OTA, so that is where I think some folks get confused on when to have the bootloader locked or not. But OTA and RUU are two very different things (with different requirement), and its important to remember that fact.
Click to expand...
Click to collapse
Yeah those things are clear for me as well. I just had the problem with the RUU not working for me. Thanks again for all the help and the good information provided even after my problem has been solved
Sambeg said:
I found them all in XDA guides/lists of stock roms, checked with my CID and European versions etc...
Click to expand...
Click to collapse
That still doesn't tell me much about what RUUs you tried. What are the actual file names, version numbers, etc.?
Only if you are still curious why the RUUs didn't work, of course. I understand its somewhat of a moot (or purely academic) point, now that the phone is working.
redpoint73 said:
That still doesn't tell me much about what RUUs you tried. What are the actual file names, version numbers, etc.?
Click to expand...
Click to collapse
these two I've tried and it was the ones in most of the guides etc. However I tried a few more as well but i had them deleted now.
0P6BIMG_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417809_signed
0P6BIMG_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417003_signed
These 2 i just tried in the end when i had given up. I know they are not really for my phone.
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4
RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_6.20.651.3
Sambeg said:
these two I've tried and it was the ones in most of the guides etc. However I tried a few more as well but i had them deleted now.
0P6BIMG_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417809_signed
0P6BIMG_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417003_signed
These 2 i just tried in the end when i had given up. I know they are not really for my phone.
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4
RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_6.20.651.3
Click to expand...
Click to collapse
Somewhat as I figured. All those RUUs failed for good reason.
First and second ones: These RUUs are older (lower version number) than the main version that was on the phone (6.12.401.4), otherwise known as a "downgrade" in version. With s-on, that isn't allowed. You can only flash the same or higher version (later) RUUs; and the only way to bypass that requirement is with s-off.
Third RUU: As you know, this isn't for your phone. You can run it a million times, and it will still fail every time; as its intended to fail since the CID and MID on your device doesn't match what the RUU is looking for. The only way to run this RUU is to s-off and change your phone's CID and MID.
Forth RUU: Again, not for your phone. Plus, the Sprint version, which has partition differences from your M8 version (and most other M8 versions). You absolutely should stay away from any Sprint or Verizon firmware, as if they do manage to flash, will often lead to a radio brick on your device.
This would never flash anyway with s-on, and the safeguards of the CID and MID did their job and saved you, in this case.
So in short, you can only run RUUs that have the "401" in the spot x.xx.401.x as these are for your CID and MID. And you can only run versions equal or greater than 6.12.401.4, of which there is currently the only one (the one that worked - 6.12.401.4).
Hope that clears things up a bit for you.
redpoint73 said:
Somewhat as I figured. All those RUUs failed for good reason.
First and second ones: These RUUs are older (lower version number) than the main version that was on the phone (6.12.401.4), otherwise known as a "downgrade" in version. With s-on, that isn't allowed. You can only flash the same or higher version (later) RUUs; and the only way to bypass that requirement is with s-off.
So in short, you can only run RUUs that have the "401" in the spot x.xx.401.x as these are for your CID and MID. And you can only run versions equal or greater than 6.12.401.4, of which there is currently the only one (the one that worked - 6.12.401.4).
Hope that clears things up a bit for you.
Click to expand...
Click to collapse
Yes indeed this cleared up most of my suspicions as well as i said i knew the 3rd and 4th was wrong from the get go it was more of a test..
Thank you for all this good info i feel like im starting to get a good grip on whats good and whats working etc... I really appreciate it! Thumbs up indeed.
I have another question tho.... Why would it not let me change the CID to the supercid 11111111?
IS that due to the phone not being in debug mode or the S-on option perhaps since i know that is a security feature from the get go.
Sambeg said:
I have another question tho.... Why would it not let me change the CID to the supercid 11111111?
IS that due to the phone not being in debug mode or the S-on option perhaps since i know that is a security feature from the get go.
Click to expand...
Click to collapse
You can only change the CID (and also MID) with s-off.
redpoint73 said:
You can only change the CID (and also MID) with s-off.
Click to expand...
Click to collapse
Right as I thought then Well thanks again for helping out and clearing up my questions.
I shall now retire from this thread in peace

Not sound at all - Flashing something a long time ago

So, like I found in another threads my old phone, has not sound at all. I tried to fix it years ago, with not luck, but I wanna give it another chance since still it's a great phone.
This is my getvar all
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.21331147A1.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(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: 0P6B16000
(bootloader) cidnum: ROGER001
(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: dcdaa6e0
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
I tried almost everything, it's currently S-ON, I tried a millon times going S-OFF with HTCDev steps, but nothing. It's UNLOCKED.
If anyone would give me a hand with this, would be awesome.. since my actual phone is broke, like my wallet. :crying:
Thanks! :fingers-crossed:
Stranyer said:
I tried almost everything, it's currently S-ON, I tried a millon times going S-OFF with HTCDev steps, but nothing.
Click to expand...
Click to collapse
HTCDev is not a process to get s-off. It is a process to unlock the bootloader (but you say it's already UNLOCKED). Sunshine is the only valid method to s-off. You can try anything else a billion times, and it will never work.
You most likely also do not need s-off to get the phone working properly again.
I have a feeling that no sound is due to outdated firmware, possibly in conjunction with a custom ROM (ROM - firmware mismatch).
My suggestion, try to relock the bootloader (command: fastboot oem lock) then the following RUU:
http://gsm-firmware.com/index.php?a=downloads&b=file&id=14070
The RUU will wipe all personal data on the phone.
redpoint73 said:
HTCDev is not a process to get s-off. It is a process to unlock the bootloader (but you say it's already UNLOCKED). Sunshine is the only valid method to s-off. You can try anything else a billion times, and it will never work.
You most likely also do not need s-off to get the phone working properly again.
I have a feeling that no sound is due to outdated firmware, possibly in conjunction with a custom ROM (ROM - firmware mismatch).
My suggestion, try to relock the bootloader (command: fastboot oem lock) then the following RUU:
http://gsm-firmware.com/index.php?a=downloads&b=file&id=14070
The RUU will wipe all personal data on the phone.
Click to expand...
Click to collapse
Hey thanks for replying!
I tried that, I keep getting this error
Code:
target reported max download size of 1826418688 bytes
sending 'zip' (1734001 KB)...
OKAY [ 49.344s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 112.683s
I tried doing a reboot and reinstaling.. but still getting error 12 :/
Any clue?
Stranyer said:
I tried that, I keep getting this error
Code:
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
Click to expand...
Click to collapse
"Signature verify fail" usually means the bootloader is unlocked. Did you relock the bootloader as I advised (mandatory in order to install the RUU)? Or if you did, can you verify is says RELOCKED near the top of the bootloader screen?
redpoint73 said:
"Signature verify fail" usually means the bootloader is unlocked. Did you relock the bootloader as I advised (mandatory in order to install the RUU)? Or if you did, can you verify is says RELOCKED near the top of the bootloader screen?
Click to expand...
Click to collapse
Yeah, I did relocked the bootloader. And it does says RELOCKED.
Stranyer said:
Yeah, I did relocked the bootloader. And it does says RELOCKED.
Click to expand...
Click to collapse
I believe you need to flash 6.13.631.7 firmware first before you can install the RUU
https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
Also you need htc_fastboot to fastboot flash RUU zip
ckpv5 said:
I believe you need to flash 6.13.631.7 firmware first before you can install the RUU
https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
Also you need htc_fastboot to fastboot flash RUU zip
Click to expand...
Click to collapse
Good point, and makes sense, as most of the US M8 variants require firmware to be flashed for Marshmallow RUU. Even though Rogers is Canadian, that version tends to follow the same rules as the US versions!
ckpv5 said:
I believe you need to flash 6.13.631.7 firmware first before you can install the RUU
https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
Also you need htc_fastboot to fastboot flash RUU zip
Click to expand...
Click to collapse
redpoint73 said:
Good point, and makes sense, as most of the US M8 variants require firmware to be flashed for Marshmallow RUU. Even though Rogers is Canadian, that version tends to follow the same rules as the US versions!
Click to expand...
Click to collapse
Sorry I took long time to reply.
I tried flashing the firmware, using htc_fasboot and fastboot. Both will give me this error.
Code:
c:\adb>htc_fastboot flash zip fw.zip
sending 'zip'... (53849 KB) OKAY
sending time = 2.408 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILnot allowed
FAILED (remote: not allowed)
Execution time is 5(s)
And still, won't flash RUU.zip
----
I retried a few more times, and it worked! It flashed firmware and ruu
But now is stuck on HTC logo boot. Won't let install a rom over fastboot :/
Code:
sending 'zip'... (360264 KB) OKAY
sending time = 10.763 secs
writing 'zip'... FAILnot allowed
FAILED (remote: not allowed)
Execution time is 11(s)
Stranyer said:
But now is stuck on HTC logo boot. Won't let install a rom over fastboot :/
Code:
sending 'zip'... (360264 KB) OKAY
sending time = 10.763 secs
writing 'zip'... FAILnot allowed
FAILED (remote: not allowed)
Execution time is 11(s)
Click to expand...
Click to collapse
Hard to tell exactly what you tried to do here, since you didn't include the actual command, name of the file you tried to flash, etc. Always include as much specific info as possible. "install a rom" is not sufficient info.
You tried flashing a custom ROM over fastboot? If so, that isn't the proper way to flash a custom ROM. You need custom recovery (TWRP) to do that. So that is the reason for "not allowed" (since it isn't).
But before doing so, we should look closer at the RUU (why it isn't booting) first. Since installing TWRP requires unlocking the bootloader, etc. Better to eliminate the RUU as a solution first, so we don't have to keep going back and forth unlocking/relocking bootloader.
Did the RUU finish successfully without any errors? If there were errors, what did it say specifically? If you don't know the answers to those questions, you can run the RUU again. Even cut/paste the output so we can look at it.

Categories

Resources