Database Develop

[Q] Freezing while Flashing or just about anything.

Just going to start by saying I'm an absolute noob with Android, so I'm sorry for the burden.
Ok, Randomly my phone decided it wouldn't proceed past the HTC Splash screen. So obviously I searched for a problem and found this: http://forum.xda-developers.com/showthread.php?t=1337105
Now before anything is said on this I'm going to say being nooby and all I wasn't sure whether I should post on ^^ That or make a new thread about specifically this topic.
Back to topic, I managed to unlock the phone, but whenever I try to flash the recovery it does nothing and I get this on my command:
c:\Android>fastboot flash recovery recovery-clockwork-5.0.2.0-vivo.img
sending 'recovery' (3726 KB)...
OKAY [ 1.173s]
writing 'recovery'...
And the phone completely freezes. Also might be worth mentioning that when I unlocked it it did not go back to the HBOOT menu and I had to remove the battery.
I tried this multiple times with the same outcome.
Currently on the HBOOT menu the details are:
*** UNLOCKED ***
VIVO PVT SHIP S-ON RL
HBOOT-2.00.0000
RADIO-3822.10.08.28_M
eMMC-boot
Nov 1 2011, 20:33:03
My phone carrier is Optus (AUS) not sure if that helps with anything though.
I've searched all night for a solution but found nothing.

[SOLVED]Unable to unlock my bootloader

Here's my problem.
I've originally S-OFF my phone, Super CID afterwards. A week ago i sent my phone to warranty so made the humongous mistake to S-ON it.
Of course S-OFF didn't work again on 1.44 so i flashed some Asian RUU, S-OFF didn't work either(still 1.44 bootloader).
This is the time when i started considering unlocking my bootloader. Big surprise, the procedure completes successfully, i select yes, the phone reboots but the bootloader stays locked.
I applied the Dev Edition RUU, HBOOT 1.55 same problem.
Any solutions?
The solution is to restore your original CID

Wait, which ruu you've flashed?
However, it's stange, which cid do you have now?

I started with 1.29.401.11 then RUU_M7_UL_JB_50_hTC_Asia_WWE_1.29.707.3_R_Radio_4A.14.3250.13_10.33.1150.01_release_311678_signed and the latest was RUU_M7_UL_JB43_SENSE50_MR_BrightstarUS_WWE_3.22.1540.1.
I am currently super CID

Try this command:
Code:
fastboot getvar all
, remove the imei and the serial number of your phone and post here the log

version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.20.3263.16
version-cpld: None
version-microp: None
version-main: 3.22.1540.1
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: 11111111
battery-status: good
battery-voltage: 3792mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-fe1214a4f2
hbootpreupdate: 11
gencheckpt: 0

So, you're s-on with super cid...
If you try to reflash the first ruu you said, you can flash it or you've an error?

Yes,
I get an error.
What i can't understand is why i can't unlock it.

andrdnl said:
Yes,
I get an error.
What i can't understand is why i can't unlock it.
Click to expand...
Click to collapse
Are you using an old token? I recommend getting a new token from HTCdev, and try again to unlock.
But you still have a problem of being S-On and SuperCID, you will not be able to change that even if you unlock bootloader again. revone will only work with hboot 1.44.

I did get a new token about 7 times. It's not the problem i think.
I am convinced i can't get S-OFF for the moment but at least i wish i could unlock the bootloader.

andrdnl said:
I did get a new token about 7 times. It's not the problem i think.
I am convinced i can't get S-OFF for the moment but at least i wish i could unlock the bootloader.
Click to expand...
Click to collapse
Could be because of SuperCID. I know that the unlock token is tied to your CID as well as other things, but thought if you got a new one it could work.
And with 1.54/1.55 there is no way to get s-off at the moment, unless you can find someone with a Java Card.

This is the only logical explanation that i can found.

andrdnl said:
This is the only logical explanation that i can found.
Click to expand...
Click to collapse
how did you solve this?

slimldj said:
how did you solve this?
Click to expand...
Click to collapse
+1

slimldj said:
how did you solve this?
Click to expand...
Click to collapse
stoned99 said:
+1
Click to expand...
Click to collapse
Go S-OFF and change the cid, with your original CID...

Guich said:
Go S-OFF and change the cid, with your original CID...
Click to expand...
Click to collapse
bootloader is locked.. how can i then get S-OFF?
my issue is to unlock bootloader again. btw. i have my original CID

slimldj said:
bootloader is locked.. how can i then get S-OFF?
my issue is to unlock bootloader again. btw. i have my original CID
Click to expand...
Click to collapse
He solved restoring his stock CID.
Which hboot do you have?
And you had S-OFF in past?

Guich said:
He solved restoring his stock CID.
Which hboot do you have?
And you had S-OFF in past?
Click to expand...
Click to collapse
Yes i was unlocked and had s-off in the past
I had to return it to stock for warranty to change the camera and it came back.
I want to unlock back now and cant.
Hboot is 1.54

slimldj said:
Yes i was unlocked and had s-off in the past
I had to return it to stock for warranty to change the camera and it came back.
I want to unlock back now and cant.
Hboot is 1.54
Click to expand...
Click to collapse
You've the same error of the guy?
So, after the flash of the unlock_code your bootloader won't be unlocked?

Guich said:
You've the same error of the guy?
So, after the flash of the unlock_code your bootloader won't be unlocked?
Click to expand...
Click to collapse
After i flash the Unlock_code.bin i get this result:
sending 'unlocktoken' (0 KB)...
OKAY [ 0.143s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.004s]
finished. total time: 0.150s
Next step is for disclaimer to pop up on phone screen but it doesnt.. it just remains on the hboot screen.

slimldj said:
After i flash the Unlock_code.bin i get this result:
sending 'unlocktoken' (0 KB)...
OKAY [ 0.143s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.004s]
finished. total time: 0.150s
Next step is for disclaimer to pop up on phone screen but it doesnt.. it just remains on the hboot screen.
Click to expand...
Click to collapse
Strange...
Have you tried to request another unlock code?

Which RUU on SuperCID 11111111?

Hello,
can i install every RUU on a HTC One with SuperCID 11111111?
Thanks

Mr.Nieto said:
Hello,
can i install every RUU on a HTC One with SuperCID 11111111?
Thanks
Click to expand...
Click to collapse
If you have a gsm htc one then yes, you would need to change android-info.txt to match cid number.

Mr.Nieto said:
Hello,
can i install every RUU on a HTC One with SuperCID 11111111?
Thanks
Click to expand...
Click to collapse
wrong forum... ask in Q & A :good:

passion8059 said:
If you have a gsm htc one then yes, you would need to change android-info.txt to match cid number.
Click to expand...
Click to collapse
Hi. Where is that android-info.txt? When i download RUU files they're .exe Files...
Is it required to have bootloader unlocked to install a RUU?

Thread Moved to Q&A, Help & Troubleshooting forum.
As a future reference, all questions get posted in Q&A, NOT development. Even if you have a development related question in future, it still belongs in Q&A.
Regards,
- KidCarter93
Forum Moderator

Mr.Nieto said:
Hi. Where is that android-info.txt? When i download RUU files they're .exe Files...
Is it required to have bootloader unlocked to install a RUU?
Click to expand...
Click to collapse
SuperCID will not allow you to install "Any" RUU
The MID must also match your phone and you must lock the bootloader before running the RUU
your brightstar RUU failed because the MID mismatch
also post a fastboot getvar all without imei/sn

clsA said:
SuperCID will not allow you to install "Any" RUU
The MID must also match your phone and you must lock the bootloader before running the RUU
Click to expand...
Click to collapse
Here is the getvar all result:
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.21.3263.04
version-cpld: None
version-microp: None
version-main: 3.63.161.6
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: 11111111
battery-status: good
battery-voltage: 4288mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-ea0bccbd
hbootpreupdate: 11
gencheckpt: 0
I got the follwing info in my bootloader:
****TAMPERED***
***RELOCKED***
M7_UL PVT SHIP S-ON RH
HBOOT 1.55.0000
RADIO 4A-21.3263.04
What can i do now? I want a stock Google Play ROM or HTC Stock ROM on my phone...

Mr.Nieto said:
Hi. I got the follwing info in my bootloader:
****TAMPERED***
***RELOCKED***
M7_UL PVT SHIP S-ON RH
HBOOT 1.55.0000
RADIO 4A-21.3263.04
What can i do now? I want a stock Google Play ROM on my phone...
Click to expand...
Click to collapse
First you have to get s-off
use rumrunner or firewater to get S-Off: http://firewater-soff.com/ or http://rumrunner.us/
Fast and easy way to GPE is here
http://forum.xda-developers.com/showthread.php?t=2356654

clsA said:
First you have to get s-off
use rumrunner or firewater to get S-Off: http://firewater-soff.com/ or http://rumrunner.us/
Fast and easy way to GPE is here
http://forum.xda-developers.com/showthread.php?t=2356654
Click to expand...
Click to collapse
Yes, i already done that before i did S-ON again...
After that i got to change the CID?
For the GPE you have posted i dont need a S-OFF, right?

Mr.Nieto said:
Yes, i already done that before i did S-ON again...
After that i got to change the CID?
For the GPE you have posted i dont need a S-OFF, right?
Click to expand...
Click to collapse
why did you go s-on ?
it's much easier if your s-off with any GPE
what recovery do you use ?

clsA said:
why did you go s-on ?
it's much easier if your s-off with any GPE
what recovery do you use ?
Click to expand...
Click to collapse
I currently got no recovery but i install TWRP...
Why S-OFF? I have heard that is very insecure...

Mr.Nieto said:
I currently got no recovery but i install TWRP...
Why S-OFF? I have heard that is very insecure...
Click to expand...
Click to collapse
good .. install TWRP 2.6.3.3 and use the ARHD GPE you'll love it it's very refined

clsA said:
good .. install TWRP 2.6.3.3 and use the ARHD GPE you'll love it it's very refined
Click to expand...
Click to collapse
So now i try to unlock my device again and it says:
target reported max download size of 1512640512 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.142s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.146s
even when i try to install TWRP it says:
target reported max download size of 1512640512 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.161s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.889s
What happened?

Mr.Nieto said:
So now i try to unlock my device again and it says:
target reported max download size of 1512640512 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.142s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.146s
even when i try to install TWRP it says:
target reported max download size of 1512640512 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.161s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.889s
What happened?
Click to expand...
Click to collapse
probably because your s-on relocked and SuperCID
@SaHiLzZ @nkk71
is their anything he can do ?

clsA said:
probably because your s-on relocked and SuperCID
Click to expand...
Click to collapse
What can i do now?

Can you generate a NEW unlock token from htcdev website. ?
sent from my mobile device

SaHiLzZ said:
Can you generate a NEW unlock token from htcdev website. ?
sent from my mobile device
Click to expand...
Click to collapse
That worked, thanks! Now i try to install TWRP...

Hold on. WHAT is your final goal?
sent from my mobile device

Installing TWRP worked too! Very nice! Thanks!
Got a question... i am currently able to S-OFF and change CID...
What is required to install the RUU
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed
Do i need to set the CID to a special One? And what is required too for that step? Is that possible?

SaHiLzZ said:
Hold on. WHAT is your final goal?
sent from my mobile device
Click to expand...
Click to collapse
My first goal is to install RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe
I want a stock rom from HTC on my device... when that isnt possible i install the GPE Custom ROM

[Q] pls someone to help me HTC ONE M7

I am asking for help
HTC ONE M7
No OS, no any data no nothing
I try to use RUU to restore but its give me error 155
the phone is with unlocked bootloader and relocked again
what shall i do?
additionl info about the model
++++tampered++++
++++relocked++++
++Security Warning+++
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4A.17.3250.14
OpenDSP_v32.120.274.0909
OS-6.12.161.8
eMMC_boot 2048MB
sep 3 2014, 10:26:40​

Cirez said:
I am asking for help
HTC ONE M7
No OS, no any data no nothing
I try to use RUU to restore but its give me error 155
the phone is with unlocked bootloader and relocked again
what shall i do?
additionl info about the model
++++tampered++++
++++relocked++++
++Security Warning+++
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4A.17.3250.14
OpenDSP_v32.120.274.0909
OS-6.12.161.8
eMMC_boot 2048MB
sep 3 2014, 10:26:40​
Click to expand...
Click to collapse
There is no ruu you can use for that version with s-on.
If you have a nandroid backup of your phone, push it back and restore it.
You can also push a rom to your phone and install it from a custom recovery then optionally you can try to s-off using that rom and then restore back to stock using a ruu with s-off
and btw questions must be posted in the q&a section not in general (a moderator will probably move you thread there)

alray said:
There is no ruu you can use for that version with s-on.
If you have a nandroid backup of your phone, push it back and restore it.
You can also push a rom to your phone and install it from a custom recovery then optionally you can try to s-off using that rom and then restore back to stock using a ruu with s-off
and btw questions must be posted in the q&a section not in general (a moderator will probably move you thread there)
Click to expand...
Click to collapse
Thank you but i don´t have nandroid back up
Can you please be more spasific i am little new in the forum
i try to flash with fastboot but its give me a error
target reported max download size of 1514139648 bytes
sending 'zip' (1313670 KB)...
OKAY [ 57.437s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 203.298s
can you please send me a post
thank you in advance and sorry about the post here
i will know for next time

for reference, OP started a second thread here in the q&a: http://forum.xda-developers.com/htc-one/help/help-suggestion-to-t2929174
thanks

[Q] Need help desperately - Back to stock

I was using the latest Viper Rom and my Camera busted on my phone. So naturally I needed to get the M7 back to stock. I have never done it before so I did some searching and found the method right in this same forum.
So Walking through the instructions everything went well
I locked the bootloader
went through the process of flashing the stock rom with fastboot and it keeps erroring out. I am consistently getting "FAILED (status read failed (Too many links))" I tried the RUU and I keep getting unknown errors from those too. I have tried multiple PC and different usb cables and ports. I am completely stumped.
I was under the impression that it didn't matter which stock ROM you tried but I did try many different ones.
Would anyone have any suggestions?

I'm not sure what RUU guide you used, but I and a few others have had success with the guide I wrote. Try it and follow up here or in that thread if you have issues (or if it worked for you).
http://forum.xda-developers.com/spr...de-reset-phone-using-ruu-htcfastboot-t2876110

Thanks for the links and the response. I followed your step to a tee and got to step 6 and tried to flash the firmware. I am s-off and when I pushed the firmware o am now getting;
target reported max download size of 1514139648 bytes
sending 'zip' (39656 KB)...
OKAY [ 2.917s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 7.830
Any suggestions?
Thanks again for your help.

Just another thing I noticed with your guide
4. If you are s-off, you do not need to lock the bootloader. If you are s-on, then you need to lock the bootloader by typing "fastboot oem lock" (again, no quotes)
s-off means the bootloader is unlocked and s-on means that it is locked. so your instructions are a little unclear. I am assuming that you meant that you need the bootloader locked.
On a whim I unlocked my bootloader again using fastboot and my BIN file and my phone did finally boot back to the Viper rom instead of being stuck on the Bootloader screen. I am curious why going s-on is making the phone fail and soft bricking the phone. Maybe my HBOOT is wrong? Could my Twerk recovery corrupted HBOOT?
Thanks again for your help!

raremind said:
Thanks for the links and the response. I followed your step to a tee and got to step 6 and tried to flash the firmware. I am s-off and when I pushed the firmware o am now getting;
target reported max download size of 1514139648 bytes
sending 'zip' (39656 KB)...
OKAY [ 2.917s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 7.830
Any suggestions?
Thanks again for your help.
Click to expand...
Click to collapse
raremind said:
Just another thing I noticed with your guide
4. If you are s-off, you do not need to lock the bootloader. If you are s-on, then you need to lock the bootloader by typing "fastboot oem lock" (again, no quotes)
s-off means the bootloader is unlocked and s-on means that it is locked. so your instructions are a little unclear. I am assuming that you meant that you need the bootloader locked.
On a whim I unlocked my bootloader again using fastboot and my BIN file and my phone did finally boot back to the Viper rom instead of being stuck on the Bootloader screen. I am curious why going s-on is making the phone fail and soft bricking the phone. Maybe my HBOOT is wrong? Could my Twerk recovery corrupted HBOOT?
Thanks again for your help!
Click to expand...
Click to collapse
I think this is the issue: since you are s-off, you should have ignored step 4 and not have locked your bootloader. A locked bootloader will not allow you to flash the firmware (it fails the security check since it wasn't created by HTC). Unlock your bootloader and try to flash the firmware file again. The reason I'm not sure is because it was my impression that an s-off phone ignores the locked/unlocked flag. But, I never lock my bootloader so I'm not sure.
By the way, s-off =/= unlocked and s-on =/= locked. Phones start as locked and s-on. Unlocking the bootloader through HTC Dev allows you to install custom recoveries and ROMs. However, it is limited because you are still s-on (security on). For example, you can only upgrade hboots, but can never downgrade to an older one. Same with RUUs. Being s-off is very flexible but more dangerous as you can access normally protected partitions. Hope that clears things up some.

Thank you again for your help. I seem to be a little more confused now. Line 4 of your guide states;
4. If you are s-off, you do not need to lock the bootloader. If you are s-on, then you need to lock the bootloader by typing "fastboot oem lock" (again, no quotes)
Click to expand...
Click to collapse
Why would I lock the the bootloader using "fastboot oem lock" if I already have s-on. You said you can not flash firmware with s-on but line 4 says I should before I flash firmware. What I just got from you, am I understanding right that I should not "fastboot oem lock" before you flash the firmware? If you are s-on the bootloader is already locked and you would not be able to do step 5.
I am s-off right now. Would I flash the firmware now, then s-on when run the RUU?

Unlocked bootloader does not = s-off.
My guess is you are unlocked not s-off.
S-OFF explained - by a Developer

So if I need to update the firmware do I need to be s-on or s-off? I need to get the phone back to stock and am having a really hard time.

raremind said:
So if I need to update the firmware do I need to be s-on or s-off? I need to get the phone back to stock and am having a really hard time.
Click to expand...
Click to collapse
Easiest way to go back to stock is to RUU. If you are s-on you need to re-lock (it will tell you in bootloader if you are s-on or s-off)
Updating firmware can be done s-on (need to re-lock bootloader) or s-off (no locking required).

BD619 said:
Easiest way to go back to stock is to RUU. If you are s-on you need to re-lock (it will tell you in bootloader if you are s-on or s-off)
Updating firmware can be done s-on (need to re-lock bootloader) or s-off (no locking required).
Click to expand...
Click to collapse
That's just the thing. I am s-on and relocked and every RUU I have tried failed. I have tried it with fastboot the exe and everything else under the sun. Everything I have tried has failed. here is what I am seeing:
Code:
*** TAMPERED ***
*** RELOCKED ***
*** Security warning ***
M7_WLS PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO- 1.01.20.0984_2
OpenDSP- v32.120.274.0909
OS-5.05.651.2
eMMC-boot 2048MB
Sep 24 2014, 16:58:42:0
I rooted and flashed TEAMWIN recovery and Viper 7.1 - My Camera started acting up and I couldn't talk on calls so I wanted to get it back to stock. The only thing I was able to do successfully trying to get it back to stock was lock the bootloader. Everything beyond that has failed.
This is what I get updating the firmware:
Code:
target reported max download size of 1514139648 bytes
sending 'zip' (39656 KB)...
OKAY [ 2.917s]
writing 'zip'...
(bootloader) signature checking..
FAILED (remote: 12 signature verify fail)
finished. total time: 7.830s
This is what I got when I locked the bootloader:
Code:
D:\Downloads\HTC\Try this\Minimal ADB and Fastboot>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (No such file or directory))
finished. total time: 1.199s
Trying to flash RUU I get:
Code:
D:\Downloads\HTC\Try this\Minimal ADB and Fastboot>fastboot flash zip Sprint_HTC
_One_m7wls_1.29.651.7_encrypted_ROM.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1029700 KB)...
OKAY [ 37.166s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (status read failed (Too many links))
finished. total time: 133.077s
Running the RUU.exe I recieve an unknown error. Am I screwed?

Ok first off you are using the wrong RUU.
You need to use the 5.05.651.2 RUU

So, you are s-on and relocked (you said s-off before so that threw me off). Because you are s-on, you may not be successful flashing the firmware, hence the security warning in the first box (see the link explaining s-off that @BD619 left). I probably need to fix my guide to reflect that issue. In the second box, you get an error trying to relock which makes sense since you are already locked. In the third box, it looks like you get an error since you are trying to flash an older RUU (not allowed since you are s-on).
At this point, as BD said, you should be able to just go here and download the ruu exe (it's the first link). I run it as an administrator just to be safe. Follow the prompts and wait around ten minutes for it to do its thing.
Don't get too frustrated. The (forced) learning process from this is very valuable. BD and I are just members who have been on here long enough to have a good understanding of what's going on. Not speaking for BD, but I started on here knowing next to nothing about Android except it's based on Linux.

Not speaking for BD, but I started on here knowing next to nothing about Android except it's based on Linux.
Click to expand...
Click to collapse
You knew more then me lol.
My first couple posts were me begging for help because I bricked my sons Epic 4G Touch lol (posted in Development...reasoning I thought it would get more exposure and I would get helped faster lol)

BD619 said:
(posted in Development...reasoning I thought it would get more exposure and I would get helped faster lol)
Click to expand...
Click to collapse
Haha, noob! I would have replied with "Cool ROM, bro".

Well thank you both! I was able to successfully flash the 5.05.651.2 RUU. Such a simple thing that was causing me such problems. I was under the impression that the RUU version didn't make a difference. I wish they would add that to the guides! Well thanks to both of you!