Database Develop

[Q] after Official 2.3.5 with sens 3.0 my incredible S transform into brick..

I bought my phone about a mount ago.. in store have told to me that phone is s-on and official and i believed in it(( After official update from htc it stoped working. Work only recovery and -revolutionary-.
this is info in it:
info frm revolutionary
"vivo pvt ship s-off rl
hboot-6.13.1002
radio-3805.06.03.03_M
eMMC-boot
apr 1 2011, 18:34:39"
phone info
imei: 358000045678255
s/n: HT1A2TD03837
old OS: android 2.3.3
could anyone help me with this.. sry for my bad eng..

Ertey said:
I bought my phone about a mount ago.. in store have told to me that phone is s-on and official and i believed in it(( After official update from htc it stoped working. Work only recovery and -revolutionary-.
this is info in it:
info frm revolutionary
"vivo pvt ship s-off rl
hboot-6.13.1002
radio-3805.06.03.03_M
eMMC-boot
apr 1 2011, 18:34:39"
phone info
imei: 358000045678255
s/n: HT1A2TD03837
old OS: android 2.3.3
could anyone help me with this.. sry for my bad eng..
Click to expand...
Click to collapse
The OTA update cannot be applied to a phone that was S-Off with Revolutionary. You should be able to pull the battery to reboot into Recovery mode and restore your backup to get going again.

official 2.3.5 with revolutionary S-OFF won't boot. Why don't give a try on ARHD 2.1 by mike?

keroro430 said:
official 2.3.5 with revolutionary S-OFF won't boot. Why don't give a try on ARHD 2.1 by mike?
Click to expand...
Click to collapse
i try it but it just don't want to setup.. in recovery then i want to install via sd card it says about signature and i can not turn it off in standart recovery(( in revolutionaty it don't setup too..

Same problem....
Can somebody tell WTF should I do to get the new frimware???? PLEASE HELP!

It is simple - restore S-ON and everything will be OK. Search this forum - there was nice manual to do that. Had this "fun" 2 days ago...

Which Recovery you are using? Give a try to 4EXTRecovery. And now, what is your Incs Bootloader version?

i tried to bring back s-on:
C:\ADB>fastboot flash hboot rom.zip
sending 'hboot' (257756 KB)...
OKAY [ 43.328s]
writing 'hboot'...
FAILED (remote: image error! (Platform check fail))
finished. total time: 43.328s
HBOOT now is 6.13.9999
and how could i setup new recovery when my phone is brick..

i want to write a recovery cwm, but..
C:\android-win-tools>fastboot flash recovery cwm.img
sending 'recovery' (3696 KB)... OKAY [ 1.328s]
writing 'recovery'...
about an hour i see this.. that a problem with it =\

You must go back to S-ON and everything is OK!!!

How to go back to S-ON..............

nikolaet said:
How to go back to S-ON..............
Click to expand...
Click to collapse
Please do not hijack a thread and then ask a question that isn't even relavent to the topic.
You need to search this forum and next time definitely give more information such as I used [fill in the blank] method to S-Off my IncS. What is the procedure I can use to get back to S-On?

Follow this beautiful guide go back to S-ON, tried myself AMD it works flawlessly..
http://forum.xda-developers.com/showthread.php?t=1359555
You should have the hboot version which you had previously..
Read carefully you will gain s-on..
After s-on run the RUU sense 3 exe file which you have downloaded but don't install from pc.. before doing this procedure you should make a goldcard.. search for that in google .. once you make a gold card, put the extracted file of that RUU from temp folder ( I guess you know how to do that ) , name it PG32IMG.zip and reboot your phone by pressing volume down+power phone will search for that file and follow on screen procedure.. it will install sense 3.0.. and your phone will start working again.. don't panic...
Info about making goldcard found here though it says for desire hd it works for incredible s too..
http://www.addictivetips.com/mobile/how-to-make-gold-card-for-htc-desire-hd/
PS : you have to make a gold card so your phone does not give you a signature error.. I was stuck with the same problem after updating the latest release but now my phone is working perfectly again..
Sent from my HTC Incredible S using Tapatalk

Nvr flash or ota update without fully reseaech.
Sent from my HTC Incredible S using XDA App

please help me my HTC ONE died

hi every one.
in order to flash this ROM I need to upgrade the firmware to latest one
and run the stock ROM in format of RUU right ?
this is what I did .
but when I want to run ROM in form of RUU it give this error
unknown error
or signature fail
I don't know what RUU to run I tried several RUU but no one success
attached some picture of boot loader
it may help to find the problem
my device is stack on the screen of boot loader
it's died

61 views without help ?

Can you re-upload your screen shots? They don't seem to be working. Also more information would be helpful. What version of the stock rom are you trying to use. Are you s-off or on. Do you have any form of recover eg twrp? Are you running a custom rom at the minute.
Info like this will help us to try and fix your issue.

Yes cannot help, cannot see screens. Sorry

+1 no images!
maybe best to post (IMHO opinion, better than screenshots):
1- link of the ROM you're trying to flash
2- which recovery (and version number, don't just say "latest")
3- a "fastboot getvar all" (copy/paste text output and remove IMEI and s/n before posting)

Ghost said:
Can you re-upload your screen shots? They don't seem to be working. Also more information would be helpful. What version of the stock rom are you trying to use. Are you s-off or on. Do you have any form of recover eg twrp? Are you running a custom rom at the minute.
Info like this will help us to try and fix your issue.
Click to expand...
Click to collapse
nkk71 said:
+1 no images!
maybe best to post (IMHO opinion, better than screenshots):
1- link of the ROM you're trying to flash
2- which recovery (and version number, don't just say "latest")
3- a "fastboot getvar all" (copy/paste text output and remove IMEI and s/n before posting)
Click to expand...
Click to collapse
thanks for your replay
see attached
what else you need
c:\adb>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.56.0000
INFOversion-baseband: 4A.14.3250.13
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 1.29.401.16
INFOversion-misc: PVT SHIP S-ON
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0710000
INFOcidnum: HTC__J15
INFObattery-status: good
INFObattery-voltage: 4319mV
INFOpartition-layout: Generic
and this
C:\Users\User>cd c:\adb
c:\adb>fastboot oem readcid
... INFOcid: HTC__J15
OKAY [ 0.000s]
finished. total time: 0.000s
c:\adb>
this is what I get with rumrunner
==================== rumrunner S-OFF 0.5.0 ==============================
rumrunner S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.
The entire risk of running rumrunner S-OFF lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.
Do you understand the implications of this warning?
(Yes/No)
Yes
Dear User: We will expect that YOU:
(1) Know how to use ADB and FASTBOOT binaries
---- [Yes, use these tools to test USB connection BEFORE running rumrunner] ----
(2) Realize that rumrunner S-OFF cannot support every CUSTOM rom in this world
(3) Understand that irc support IS NOT A GENERAL HELPDESK
(4) Are able to identify and download the CORRECT package for YOUR device
(5) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
ERROR: run rumrunner again and READ (no adb connection to device. Debugging on?
Drivers?)
Press ENTER to exit

Something that doesn't start or end with a 404
Sent from my HTC One using Tapatalk

nkk71 said:
Something that doesn't start or end with a 404
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
sorry I don't understand what do you mean
Can you please explain to me?
sorry friend

dida1 said:
INFOversion-bootloader: 1.56.0000
INFOversion-main: 1.29.401.16
INFOversion-misc: PVT SHIP S-ON
INFOmodelid: PN0710000
INFOcidnum: HTC__J15
c:\adb>
Click to expand...
Click to collapse
1- Attachments aren't working (at least for me, so I get 404).
2- how can u be on hboot 1.56 but fw 1.29 :what:
(especially with s-on)

nkk71 said:
1- Attachments aren't working (at least for me, so I get 404).
2- how can u be on hboot 1.56 but fw 1.29 :what:
(especially with s-on)
Click to expand...
Click to collapse
Excellent question.. It almost appears that it at one time was unlocked or S-OFF and was relocked thereafter.
To the OP: The signature fail is due to you being S-ON and not flashing the J15 RUU. But the only J15 RUUs I've found are 1.44 HBoots which will fail on your system without S-ON. Since your on FW 1.29 you need to get S-OFF A and then your free to flash RUUs
I could be wrong but I don't think we have a signed 1.56 RUU out yet
Sent from my Nexus 10 using Tapatalk 4

nkk71 said:
1- Attachments aren't working (at least for me, so I get 404).
2- how can u be on hboot 1.56 but fw 1.29 :what:
(especially with s-on)
Click to expand...
Click to collapse
I don't know how this come to me maybe because I tried several RUU ?
please help me to get my phone work again?
.what should I do now?

J15 (max 4.3, for the moment)
hboot 1.56 (has to be 4.4)
fw 1.29 (4.1.2)
?
Sent from my HTC One using Tapatalk

altimax98 said:
Excellent question.. It almost appears that it at one time was unlocked or S-OFF and was relocked thereafter.
To the OP: The signature fail is due to you being S-ON and not flashing the J15 RUU. But the only J15 RUUs I've found are 1.44 HBoots which will fail on your system without S-ON. Since your on FW 1.29 you need to get S-OFF A and then your free to flash RUUs
I could be wrong but I don't think we have a signed 1.56 RUU out yet
Sent from my Nexus 10 using Tapatalk 4
Click to expand...
Click to collapse
thank you friend
How can I get S-OFF I tried but failed
specially my phone stack on boot loader screen I can't do any thing even it's not reboot
help me please
see attached

Still can't see attachments
but, I'll bite:
* J15 (max 4.3, for the moment)
* hboot 1.56 (has to be 4.4)
* fw 1.29 (4.1.2)
* s-on
What colour is your bootloader?
Sent from my HTC One using Tapatalk

Got my eyes peeled on this one.. Would be interesting to resolve this, as I didn't know there was a 1.56 bootloader as well..

nkk71 said:
Still can't see attachments
but, I'll bite:
* J15 (max 4.3, for the moment)
* hboot 1.56 (has to be 4.4)
* fw 1.29 (4.1.2)
* s-on
What colour is your bootloader?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
SaHiLzZ said:
Got my eyes peeled on this one.. Would be interesting to resolve this, as I didn't know there was a 1.56 bootloader as well..
Click to expand...
Click to collapse
here is the screen
it's white screen with this info
****tampered***
****relocked****
****security warning***
M7_UL PVT SHIP S-ON RH
HBOOT 1.56.0000
RADIO 4A. 14.3250.13
open DSP- v26.128.274.0202
OS- 1.29.401.16 ( 4.06.1540.2)
eMMC-boot 2048MB
Nov 29 2013,

when trying to send a firmware file I got this
sending 'zip' (43288 KB)...
OKAY [ 3.277s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) signature checking...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 10.922s
some times this errors
error: device not found
C:\Users\User\Desktop\One_All-In-One_Kit_v\data>
...
(bootloader) Device was already locked!
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\User\Desktop\One_All-In-One_Kit_v\data>

dida1 said:
when trying to send a firmware file I got this
sending 'zip' (43288 KB)...
OKAY [ 3.277s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) signature checking...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 10.922s
Click to expand...
Click to collapse
Normally you will re-run the same command when you get to this point but I don't see you succeeding unless you're S-Off already. You might have to go with a custom rom and recovery for now.

dida1 said:
here is the screen
it's white screen with this info
****tampered***
****relocked****
****security warning***
M7_UL PVT SHIP S-ON RH
HBOOT 1.56.0000
RADIO 4A. 14.3250.13
open DSP- v26.128.274.0202
OS-1.29.401.16 ( 4.06.1540.2)
eMMC-boot 2048MB
Nov 29 2013,
Click to expand...
Click to collapse
I was briefly able to see the screenshot, and I must say WOW, how many things can go wrong at the same time?
so feel free to correct me, on what you did:
1- you were s-off and unlocked
2- you wanted to flash a 4.4 ROM, but thought you needed to upgrade firmware (but what you needed was updated recovery)
3- so you went ahead and relocked (because you thought bootloader needed locked to flash firmware (which is not the case with s-off)
4- you went ahead and rebooted to ruu mode, and flashed the firmware.zip; BUT you only did it once, whereas you should have flashed it TWICE (hence the red text in bootloader with two firmwares "OS-1.29.401.16 ( 4.06.1540.2)", and the updated hboot but not firmware)
5- you flashed a 4.4 ROM on an old recovery (ie not TWRP 2.6.3.3)
6- that resulted in a bootloop
7- so you panicked and tried an RUU
8- that didnt work, so you went s-on (or at least you did at one point)
-> and now you're stuck with s-on and a locked bootloader
so what to do next?
A) do you still have custom recovery -> if yes, install a rooted rom (you may need to try several, and don't use a 4.4 ROM) and try to get rumrunner to achieve S-Off
B) try to unlock by getting a new token from HTCdev

nkk71 said:
I was briefly able to see the screenshot, and I must say WOW, how many things can go wrong at the same time?
so feel free to correct me, on what you did:
1- you were s-off and unlocked
2- you wanted to flash a 4.4 ROM, but thought you needed to upgrade firmware (but what you needed was updated recovery)
3- so you went ahead and relocked (because you thought bootloader needed locked to flash firmware (which is not the case with s-off)
4- you went ahead and rebooted to ruu mode, and flashed the firmware.zip; BUT you only did it once, whereas you should have flashed it TWICE (hence the red text in bootloader with two firmwares "OS-1.29.401.16 ( 4.06.1540.2)", and the updated hboot but not firmware)
5- you flashed a 4.4 ROM on an old recovery (ie not TWRP 2.6.3.3)
6- that resulted in a bootloop
7- so you panicked and tried an RUU
8- that didnt work, so you went s-on (or at least you did at one point)
-> and now you're stuck with s-on and a locked bootloader
so what to do next?
A) do you still have custom recovery -> if yes, install a rooted rom (you may need to try several, and don't use a 4.4 ROM) and try to get rumrunner to achieve S-Off
B) try to unlock by getting a new token from HTCdev
Click to expand...
Click to collapse
I was wondering how he could get to that firmware configuration. This is a good lesson to carefully read the step by step instructions on XDA before you start flashing stuff.

Unable to unlock relocked hboot

I re-locked my phone with a custom recovery and attempted to unlock again and goes through successful though the unlock screen does not show up.(Probably because I have no OS installed?)
Code:
fastboot flash unlocktoken unlock_code.bin
target reported max download size of 1526722560 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.141s]
writing 'unlocktoken'...
(bootloader) unlock token check [COLOR="DeepSkyBlue"]successfully[/COLOR]
OKAY [ 0.003s]
finished. total time: 0.144s
My current information is:
*** Tampered ***
*** RELOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4T.21.3218.21
OpenDSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
Code:
version: 0.5
version-bootloader: 1.54.0000
version-baseband: 4T.21.3218.21
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: XXXXXXXXXXXX
imei: XXXXXXXXXXXXXX
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum:[COLOR="DeepSkyBlue"]GOOGL001[/COLOR]
battery-status: good
battery-voltage: 4288mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: RUU
commitno-bootloader: dirty-5d4c562c
hbootpreupdate: 11
gencheckpt: 0
Ive tried the method below with a few RUU's though I keep getting the error "FAILED (remote: 12 signature verify fail)" Their must some RUU that I can flash that correlates to my above information?
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip <path to zip>
Code:
C:\Users\chanik\Desktop\adt-bundle-windows-x86_64-20130917\sdk\platform-tools>fa
stboot flash zip rom.zip
target reported max download size of 1526722560 bytes
sending 'zip' (388870 KB)...
OKAY [ 15.220s]
writing 'zip'...
(bootloader) signature checking...
[COLOR="Red"]FAILED (remote: 12 signature verify fail)[/COLOR]
finished. total time: 53.263s
If someone could confirm I have fully bricked my device that be great so i can move on with my life

I foundout that i dont have a mainvar... is tjis bad?

ronniereiff said:
I foundout that i dont have a mainvar... is tjis bad?
Click to expand...
Click to collapse
Did you say custom recovery? Which one, I'll post instructions to unlock when I'm on my pc...
Sent from my HTC One using Tapatalk

nkk71 said:
Did you say custom recovery? Which one, I'll post instructions to unlock when I'm on my pc...
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Twrp, though i am unable to use it due to being relocked..

ronniereiff said:
Twrp, though i am unable to use it due to being relocked..
Click to expand...
Click to collapse
oh, just saw you're s-on, oops.
do you have the GPE bootloader or Sense bootloader? have you tried "fastboot oem unlock"
edit: also what are you trying to flash, link please

nkk71 said:
oh, just saw you're s-on, oops.
do you have the GPE bootloader or Sense bootloader? have you tried "fastboot oem unlock"
edit: also what are you trying to flash, link please
Click to expand...
Click to collapse
I have the GPE bootloader, really im trying to flash anything that will make my phone functional again.
Ive tried many zips from the htc one collection thread

ronniereiff said:
I have the GPE bootloader, really im trying to flash anything that will make my phone functional again.
Ive tried many zips from the htc one collection thread
Click to expand...
Click to collapse
have you tried "fastboot oem unlock"?
also check this: http://forum.xda-developers.com/showthread.php?p=48195194#post48195194 (read through the thread, to make sure it applies to you).

nkk71 said:
have you tried "fastboot oem unlock"?
also check this: http://forum.xda-developers.com/showthread.php?p=48195194#post48195194 (read through the thread, to make sure it applies to you).
Click to expand...
Click to collapse
Fastboot oem unlock does not work, ill try to flash an older hboot in ruu mode tomorrow though i have a feeling signiture check will fail.

ronniereiff said:
Fastboot oem unlock does not work, ill try to flash an older hboot in ruu mode tomorrow though i have a feeling signiture check will fail.
Click to expand...
Click to collapse
or use a same or higher version RUU, that should work; with s-on downgrade not possible, but same version or higher RUU will work.

nkk71 said:
or use a same or higher version RUU, that should work; with s-on downgrade not possible, but same version or higher RUU will work.
Click to expand...
Click to collapse
When you say version im guessing you are referring to mainver, a varible that comes back empty in fastboot. Mmy phhone has no mainver and idk why.

ronniereiff said:
When you say version im guessing you are referring to mainver, a varible that comes back empty in fastboot. Mmy phhone has no mainver and idk why.
Click to expand...
Click to collapse
yeah i saw that, dont know why it keeps happening, but you can infer from hboot 1.54 that it should be a 4.2.2 based firmware.
I don't know about GPE, but for Sense it was:
hboot 1.44 -> 1.xx firmware
hboot 1.54 -> 2.xx firmware
hboot 1.55 -> 3.xx firmware
hboot 1.56 -> 4.xx firmware
you would have to check if GPE has the same progression.
PS: though radio "4T.21.3218.21" doesnt really help, cause that looks the 4.4 GPE radio.
Anyway, I would try several RUUs in sequence, always starting with the lowest one, go up one at a time, till you find one that goes through, without failing. (has to be an official signed ruu.exe or ruu.zip, since you're s-on)

nkk71 said:
yeah i saw that, dont know why it keeps happening, but you can infer from hboot 1.54 that it should be a 4.2.2 based firmware.
I don't know about GPE, but for Sense it was:
hboot 1.44 -> 1.xx firmware
hboot 1.54 -> 2.xx firmware
hboot 1.55 -> 3.xx firmware
hboot 1.56 -> 4.xx firmware
you would have to check if GPE has the same progression.
PS: though radio "4T.21.3218.21" doesnt really help, cause that looks the 4.4 GPE radio.
Anyway, I would try several RUUs in sequence, always starting with the lowest one, go up one at a time, till you find one that goes through, without failing. (has to be an official signed ruu.exe or ruu.zip, since you're s-on)
Click to expand...
Click to collapse
I have successfully unlocked after flashing the 3.58.1700.5 kitkat firmware Just need to see how to get kitkat now

nkk71 said:
yeah i saw that, dont know why it keeps happening, but you can infer from hboot 1.54 that it should be a 4.2.2 based firmware.
I don't know about GPE, but for Sense it was:
hboot 1.44 -> 1.xx firmware
hboot 1.54 -> 2.xx firmware
hboot 1.55 -> 3.xx firmware
hboot 1.56 -> 4.xx firmware
you would have to check if GPE has the same progression.
PS: though radio "4T.21.3218.21" doesnt really help, cause that looks the 4.4 GPE radio.
Anyway, I would try several RUUs in sequence, always starting with the lowest one, go up one at a time, till you find one that goes through, without failing. (has to be an official signed ruu.exe or ruu.zip, since you're s-on)
Click to expand...
Click to collapse
So my current mainver is 3.06.1700.10, hboot 1.54.000, radio 4A.18.3263.15, cidnum: GOOGL001,modelid: PN0712000 with s-on
I tried installing roms on twrp recovery but everything is failing and cache unable to mount every time and i have to wipe it over and over to get it to mount. Any idea whats going on? ive tried formating everything.

ronniereiff said:
So my current mainver is 3.06.1700.10, hboot 1.54.000, radio 4A.18.3263.15, cidnum: GOOGL001,modelid: PN0712000 with s-on
I tried installing roms on twrp recovery but everything is failing and cache unable to mount every time and i have to wipe it over and over to get it to mount. Any idea whats going on? ive tried formating everything.
Click to expand...
Click to collapse
Cache unable to mount is ok, it's because it's wiped, so don't worry about that.
To be able to flash a 4.4 ROM, you need TWRP 2.6.3.3 or above, but since you're S-On you cannot flash a GPE 4.4 ROM as they require S-Off.
Use adb sideload, adb push, or OTG cable to get a ROM to TWRP.
Hit the thanks button if i've helped

nkk71 said:
Hit the thanks button if i've helped
Click to expand...
Click to collapse
After finally getting my phone fully working with 4.4. I have came onto XDA Forms to do just that, you have helped me out a lot, thank you!
Ronnie Reiff

ronniereiff said:
After finally getting my phone fully working with 4.4. I have came onto XDA Forms to do just that, you have helped me out a lot, thank you!
Ronnie Reiff
Click to expand...
Click to collapse
Can you post where did you get the rom you flashed?

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

HTC one bricked

Hi There,
I was wondering if anybody could help me please.
I have a HTC one m7 international version, which by mistake wiped the os, now only reboot in bootloader. I have tried to use various RUU but i can not get anywhere allways failed since is S-ON and relocked
I can not get which version the phone has, so i have used the cidnum and modelid. Here below see fastboot loader description.
May be you all have any ideas how to fix this problem.I have been trying for the last 3 days without getting anywhere.
B4 it went wrong I was using CM11 rom 4.4.2 kitkat
I have tried these 2 RUU but failed 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
RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1 (1)
Many thanks for you help.
version 0.5
version bootloader 1.44.0000
version baseband 4A.14.3250.13
version main? none
version misc pvt ship S-ON
product M7UL
Platform HB00T-8064
modelid PN0710000
cidnum HTC–001
partiton layout generic
security on
build mode ship

gauchosanto said:
Hi There,
I was wondering if anybody could help me please.
I have a HTC one m7 international version, which by mistake wiped the os, now only reboot in bootloader. I have tried to use various RUU but i can not get anywhere allways failed since is S-ON and relocked
I can not get which version the phone has, so i have used the cidnum and modelid. Here below see fastboot loader description.
May be you all have any ideas how to fix this problem.I have been trying for the last 3 days without getting anywhere.
B4 it went wrong I was using CM11 rom 4.4.2 kitkat
I have tried these 2 RUU but failed 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
RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1 (1)
Many thanks for you help.
version 0.5
version bootloader 1.44.0000
version baseband 4A.14.3250.13
version main? none
version misc pvt ship S-ON
product M7UL
Platform HB00T-8064
modelid PN0710000
cidnum HTC–001
partiton layout generic
security on
build mode ship
Click to expand...
Click to collapse
Can you boot to recovery?
Can't think of a good sig

donkeykong1 said:
Can you boot to recovery?
Can't think of a good sig
Click to expand...
Click to collapse
I am afraid not able any longer

gauchosanto said:
I am afraid not able any longer
Click to expand...
Click to collapse
Try to flash custom recovery via fastboot. it should work. If that works, you just need to sideload a ROM and flash it via custom recovery
Can't think of a good sig

gauchosanto said:
I am afraid not able any longer
Click to expand...
Click to collapse
we not need recovery
We need fastboot getvar all
Then we can help you
from HTC One

your correct rom is the 401 ruu, you don't want to be flashing the asia RUU that's the wrong one.
modelid PN0710000
cidnum HTC–001
(this is WWE Europe edition)
also, you have HBOOT 1.44, that is known to cause problems with windows 8 and above, make sure you are using windows 7 and your drivers and fastboot/adb is up to date.
but like yatindroid said, post your fastboot getvar all.

htc m7 pn07110 bricked
htc m7 pn07110 bricked
hi i have a problem when usin my phone it suddenly freezers and was not able to get acces to anything (Was rooted/Bootloader Unlocked/having Custom Rom/TRWP/S-ON).. tried to restore my rom by usin twrp 2.8. but there was no file and it cannot mount my storage...
Then, found on a thread to restore stock ROM via RUU, so i relocked my bootloader and then find myself stuck at everything
When I plug in AC adapter for charging, phone load in bootloader, and whenever i press "Fastboot/Factory Reset" my phone freezes
Even fastboot and ADB command freezes my phone,
I need help please.
Code:
*** TAMPERED ***
*** RELOCKED ***
*** SECURITY WARNING ***
M7_U PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.28.3218.04
OpenDSP-v32.120.274.0909
OS-6.09.401.111
eMMC-boot 2048MB
Nov 12 2014,21:44:28.0

lordtopher said:
htc m7 pn07110 bricked
hi i have a problem when usin my phone it suddenly freezers and was not able to get acces to anything (Was rooted/Bootloader Unlocked/having Custom Rom/TRWP/S-ON).. tried to restore my rom by usin twrp 2.8. but there was no file and it cannot mount my storage...
Then, found on a thread to restore stock ROM via RUU, so i relocked my bootloader and then find myself stuck at everything
When I plug in AC adapter for charging, phone load in bootloader, and whenever i press "Fastboot/Factory Reset" my phone freezes
Even fastboot and ADB command freezes my phone,
I need help please.
Code:
*** TAMPERED ***
*** RELOCKED ***
*** SECURITY WARNING ***
M7_U PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.28.3218.04
OpenDSP-v32.120.274.0909
OS-6.09.401.111
eMMC-boot 2048MB
Nov 12 2014,21:44:28.0
Click to expand...
Click to collapse
Which RUU you applied ?
6.09.401.111 is might not available
So your only chance is any how unlock it
flash TWRP
Restore nandroid backup

yatindroid said:
Which RUU you applied ?
6.09.401.111 is might not available
So your only chance is any how unlock it
flash TWRP
Restore nandroid backup
Click to expand...
Click to collapse
When i enter flashboot or bootloader... My phone freezers.. Any idea

lordtopher said:
When i enter flashboot or bootloader... My phone freezers.. Any idea
Click to expand...
Click to collapse
maybe hardware issues than

yatindroid said:
maybe hardware issues than
Click to expand...
Click to collapse
what must i do then ???

yatindroid said:
maybe hardware issues than
Click to expand...
Click to collapse
so what should i do?? will i be able to use my phone again ?????:crying:

Nope. It's dead. If it acted up on its own. Bury it. Throw it. Or blend it.

lordtopher said:
so what should i do?? will i be able to use my phone again ?????:crying:
Click to expand...
Click to collapse
take it service center