Database Users

MT3G 1.2 stuck in RUU, no fastboot/recovery

My phone is totally unresponsive to everything I try to do with it. Its a MT3G 1.2.
I tried rooting it. Created a goldcard, flashed the sappimg from the unlockr guide. then tried various combinations of stock files, all with the same "signature error". Today, I decided to try and go back to the stock with the RUU. it went fine, til it flashed the System partition, which it sat there for 30mins and did nothing... Now im stuck with a phone that only goes into RUU, and refuses to let me flash ANYTHING to it, reguardless of version/type/size/extension/ect. NOTHING works. every file I try gives me either a signature error or model ID error. The RUU fails, everytime. and Ive tried all three T-MO ones and a few from europe. RUU says my version is 2.53.707.2... Yet when i try flashing that RUU it says gives a wrong model error. I dont get it. My goldcard, which worked to flash the HTC Magic sappimg, is in the phone thru all of its. its like it doesnt see my sdcard. I know the goldcard is good, I just used it.
Displayed on phone:
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CLD-13
RADIO-2.22.23.27
-----
fastboot oem boot displays:
-----
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x98070CA0
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 32
(bootloader) TAG:hwid 0x1
(bootloader) TAG:skuid 0x22800
(bootloader) TAG:hero panel = 0x0
(bootloader) TAG:engineerid = 0x2
(bootloader) radio_flash_id=0x1543BCEC
(bootloader) die_size=0x2
(bootloader) radio_flash_id=0x1543BCEC
(bootloader) die_size=0x2
(bootloader) TAG:die_size = 0x2
(bootloader) Device CID is not super CID
(bootloader) CID is T-MOB010
(bootloader) setting.cid::T-MOB010
(bootloader) serial number: HT03YPB02450
(bootloader) commandline from head: no_console_suspend=1 console=null
(bootloader) command line length =337
(bootloader) active commandline: board_sapphire.disable_uart3=1 board_sap
(bootloader) phire.usb_h2w_sw=1 board_sapphire.disable_sdcard=1 smisize=3
(bootloader) 2 androidboot.baseband=2.22.23.02 androidboot.cid=T-MOB010
(bootloader) androidboot.carrier=TMUS androidboot.keycaps=qwerty androidb
(bootloader) oot.mode=normal androidboot.serialno=HT03YPB02450 androidboo
(bootloader) t.bootloader=1.33.0013 no_console_suspend=1 console=null
(bootloader) PARTITIOM_NUM_MAX =6 Valid partition num=6
FAILED (status read failed (Too many links))
finished. total time: 7.701s
-----------
Does this mean my SD Card is disabled??? Ive tried the codes to re-enable it, but they do nothing. "Fastboot oem enableqxdm 0" gives an error, and "fastboot -c board_sapphire.ect=0" says finished but nothing ever changes.
Im running out of ideas... am I missing something, or have i successfully bricked my phone... please help!

Run these commands and post here the output:
Code:
fastboot getvar version-main
fastboot oem h
Try also this:
Code:
fastboot oem enableqxdm 1

Tried those.
C:\Documents and Settings\Ryan>fastboot oem h
...
(bootloader) command list
(bootloader) keytest
(bootloader) heap
(bootloader) boot
(bootloader) reset
(bootloader) powerdown
(bootloader) rebootRUU
(bootloader) task
(bootloader) rtask
OKAY [ 0.000s]
finished. total time: 0.030s
C:\Documents and Settings\Ryan>fastboot getvar version-main
version-main: 2.53.707.2
finished. total time: 0.000s
C:\Documents and Settings\Ryan>fastboot oem enableqxdm 1
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.000s]
finished. total time: 0.000s
--------------------
I vaguely remember erasing the misc partition... and im pretty sure thats what screwed it all up. Now im stuck with a perfected hboot and no system or userdata partitions, and a blank mtd0 partition. Every time I try and flash a .zip, the image signature fails. If i try to flash a SAPPIMG.nbh or ROM.zip (extracted from RUU) it says "adopting signature" but then fails for either model ID or main version. it looks like i need a HTC signed SAPPIMG.zip with main version 2.53.707.2 and a model ID of SAPP31000... where on earth I can find said file, i have no idea.

either that, or a zip/recovery file that will pass the signature check...

Do you use a goldcard... if so, it seems like you are using a bad one..

yeah i actually bought a new sandisk 2gb card just to use for it. i just remade it last night. Im going to try making another one with a 4gb lexar card, and a 256mb kingmax. Maybe RUU mode doesnt like the sandisk?

Execute reset to try to get out of the ruu mode:
Code:
fastboot oem reset

-----
FAILED (status read failed (Too many links))
finished. total time: 0.010s
-----
I made two more goldcards, and it does the same thing: keeps kicking back signature and model id errors when i try to flash files. running out of ideas other than jtag or a custom file. but i have no idea how to do either

Well... you cannot flash files from fastboot using the coldcard...
It must be done from hboot mode ( Hold volume - (decrease) and power), then the process should pick up the sappimg.zip or sappimg.nbh file from the sdcard...

It wont go into fastboot... that key combo makes it go right back to the RUU screen.
I think what I need is the RUU file for the FRG83D update... it has a newer main version, so it should go thru. But I cant find it. I found the one for the SAPP30000 but not for my 31000.... i guess it hasnt been leaked yet.

OK so I downloaded the official 2.2.1 update file from google's servers... tried to flash it with fastboot update and flash zip. One gave an error for no android-info file. The other failed, yet again, for security failures. what the hell is up with this phone? absolutely no files, including files from google, pass the signature check. What fricken signature is it looking for? The only files ive had pass the security check, its failed for some other reason (model ID, main version). I made my goldcard again, but I got the CID using my cousins Samsung Fascinate (gag), so I'm wondering if it spit out the right number. not sure. thou it did let me flash the 2.53.707.2 file with it... so i think it worked? Im seriously about to lose my mind. Im fairly confident that if I can somehow get the System and Userdata partitions flashed, it will be fine. Cuz the RUU successfully flashed everything except those last two partitions. Someone leak the RUU pleaseeeee

i have the same issue with my phone (3g 1.2)
i've tried so many things, goldcard, etc.. nothing worked.
when flashing sappimg, i always got stuck at system unzipping.

the one time i got RUU to actually flash the phone, it hung on the system partition. Now i cant even get it to go that far. every file either hangs or fails signature check or model/main version. luckily Im getting a Fender LE tomorrow so until the mythical RUU appears, my MT3G will be a charger dock.

My RUU update was stuck on system- unzipping for like half hour. i didnt know what to do so i turned off the phone and restarted it, it went into RUU mode and i couldnt update anything else, cuz all RUU upates would give me wrong version/ID, etc.
now i think it is because i dont have eng spl on the phone, thus it not allowing to update. the only thing i can think of to do, is get an eng RUU, to update it, and then it should get out of RUU mode.
and btw, How to flash it using goldcard, when i cant get to Hboot??

I believe yours is salvageable. U can fastboot from RUU so try flashing the engineering SPL from there. My understanding is the phone should "see" the goldcard and let RUU/Fastboot flash whatever files you want it to. This however hasnt been the case for me.

i will try to do that, but how do i flash an engineering spl?
get eng sappimg.zip?
and how do i do it?
i just made another goldcard with my friend's phone.

Soft bricked MyTouch 1.2 any help appreciated

Hello all. I’m wondering if I could get any help with a semi-bricked Mytouch 3g 1.2.
I’ve seen this problem posted, but I haven’t been able to find any thread that had a clearcut solution so I thought I’d try to post asking for help. Like other’s on the board, I followed the rooting instructions on the Unlockr.com not knowing the link to the sappimg.zip was incorrect.
I am now stuck with the information below. I am able to get into fastboot, and the phone is recognized. I have tried to flash the “correct” sappimg file, but the phone will freeze when it is trying to unzip the system file. ADB devices command does not list the phone at all for some reason any longer.
I do have a working gold card. Any help at this point to try to get this phone working would be greatly appreciated.
Sapphire Unknown 32A Ship S-on H
HBoot: 1.33.0009 (Sapp31000)
CPLD: 13
Radio: 3.22.20.17
May 8, 2009, 21:02:32
Fasbtoot Devices: SH04KPB00691

Run these commands:
Code:
fastboot getvar version-main

mumilover said:
Run these commands:
Code:
fastboot getvar version main
Click to expand...
Click to collapse
Mumilover,
Thanks for the reply. I've entered the command string but all it's giving me is a list of fastboot commands.
if I enter "fastboot getvar version" it gives me version 0.5

Code:
fastboot getvar version-main
Forgot the "-" character... my bad :0)

mumilover said:
Code:
fastboot getvar version-main
Forgot the "-" character... my bad :0)
Click to expand...
Click to collapse
nah...np. you're the one that's helping me.
I feel like a moron, though. I should have been able to figure that out.
Version-main: 2.16.707.3
God knows what I've done trying to get this thing back up including trying to flash another sappimg & it freezing when it tries to unzip the system file.

Use this guide:
http://forum.xda-developers.com/showthread.php?t=734617

I've actually tried that. when I try to use a new sapping the phone freezes when unzipping. if I try to push the radio, I get a signature validation error.

Hmm... that's kinda bad... because you need that flash..
The reason why this is failing is because you have radio/spl from a 32A rom - 2.16.707.3 Singapore, Philippines
Try this command:
fastboot oem h

mumilover said:
Hmm... that's kinda bad... because you need that flash..
The reason why this is failing is because you have radio/spl from a 32A rom - 2.16.707.3 Singapore, Philippines
Try this command:
fastboot oem h
Click to expand...
Click to collapse
I'm getting the following following string
...
comandlist
keytest
heap
boot
reset
powerdown
rebootruu
task
rtask

Try to force a boot and see if you get adb access:
fastboot oem boot

i get a text string that looks like this then everything freezes:
C:\androidsdk\tools>fastboot oem boot
...
(bootloader) setup_tag addr=0xA1200100 cmdline add=0x980728E0
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 32
(bootloader) TAG:hwid 0x1
(bootloader) TAG:skuid 0x22800
(bootloader) TAG:hero panel = 0x0
(bootloader) TAG:engineerid = 0x2
(bootloader) Device CID is not super CID
(bootloader) CID is T-MOB010
(bootloader) setting.cid::T-MOB010
(bootloader) serial number: SH04KPB00691
(bootloader) commandline from head: no_console_suspend=1 console=null
(bootloader) command line length =337
(bootloader) active commandline: board_sapphire.disable_uart3=0 board_sap
(bootloader) phire.usb_h2w_sw=0 board_sapphire.disable_sdcard=0 smisize=3
(bootloader) 2 androidboot.baseband=3.22.20.17 androidboot.cid=T-MOB010
(bootloader) androidboot.carrier=TMUS androidboot.keycaps=qwerty androidb
(bootloader) oot.mode=normal androidboot.serialno=SH04KPB00691 androidboo
(bootloader) t.bootloader=1.33.0009 no_console_suspend=1 console=null
(bootloader) PARTITIOM_NUM_MAX =6 Valid partition num=6

i am able to adb device list
C:\androidsdk\tools>fastboot devices
SH04KPB00691 fastboot
C:\androidsdk\tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
033c208242410197 device
C:\androidsdk\tools>

Very good....
Don't touch it... i'll update here when i have time (very soon, preparing for defending my bachelor thesis, so kinda busy)

I'm ready.
When ever you have time try to catch me on gtalk or skype.
I'll pm you my info...

time difference is about 12 hours, i believe

I'm on now... just catch me...
it's 8 pm now in Denmark

pm'd info, also think I tried to add you via gtalk just now.

[GUIDE] How to extract RUU & manually flash rom.zip HTC One M7

So, you may have made a bad flash, having trouble to S-OFF or just want to go back to 100% stock ROM and recovery. In that case, the easiest solution is to run your RUU (ROM Update Utility). But unlike the conventional method, this guide is about extracting the rom.zip from your RUU for a faster and more comprehensive installation. The extracted rom.zip will also allow the possibility to decrypt the RUU in order to get access to all the individual files inside the encrypted archive. So, if you want to flash, for example, only the stock recovery, you can do it without having to flash the entire RUU ROM, which will restore the phone's entire software.
Note: Your HTC One can be either S-ON or S-OFF in order to successfully flash RUU rom.zip. But if your device is S-OFF, you do not need to re/lock your bootloader.
Follow the instructions in the given order to avoid any hiccups or possible bricking of your device:
1. You will need to know your HTC One's MID and CID. These codes will allow you to find the required RUU for your phone.
You need adb and fastboot. Go to your Bootloader. Select Fastboot. Connect your HTC One with its original USB cable to your PC. Do:
Code:
fastboot getvar all
and you should see a list of important information about your device. In particular, note the modelid (MID) and cidnum (CID). If you get nothing, there is an issue with the USB connection between your phone and PC.
2. Find the correct RUU. Here's a thread: http://forum.xda-developers.com/showthread.php?t=2428276 to find the correct RUU from the filename but more importantly, make sure that both the MID and CID match exactly with your device. You also need to pay attention if you need the M7 UL or M7 U version, which is in the filename of the RUU. If you can't find your RUU from that site, just google or search on XDA. However, not all HTC One variants have RUUs. But if you are already S-OFF, you can change your MID and CID, which will allow you to use any RUU: http://forum.xda-developers.com/showthread.php?t=2322820
3. Extract the RUU and grab the rom.zip file. This is the most important file you need from the RUU and afterwards you can delete the RUU exe if you want. To get the rom.zip from your RUU exe file, you just need to run the RUU exe file once, and then when the window is ready and waiting for you to press on the "Next" button, just leave it open and go to your temp folder. I'm using Windows XP SP3 32-bit and my temp folder is located at this path: C:\Documents and Settings\Administrator\Local Settings\Temp
Now, you will see several files and folders. Sort everything in that temp folder based on "Date Modified" with the most recent folder showing up above all other folders. This is the folder you want. The folder name will be bunch of letters and numbers. Inside that folder you will find several files, but what you need is rom.zip and android-info.txt. Copy both these files and paste them somewhere safe on your hard drive. The android-info.txt contains crucial information about the compatibility of that RUU for your phone. Here's the android-info.txt extracted from my RUU exe:
Code:
modelid: PN0711000
cidnum: HTC__001
cidnum: HTC__J15
cidnum: HTC__A48
cidnum: HTC__M27
mainver: 1.29.401.2
btype:1
aareport:1
DelCache:1
hbootpreupdate:3
You can then verify that you have the correct RUU if the modelid matches that of your phone and if you can see your cidnum in that list. If either (or both) of the modelid or cidnum does not match that of your phone, the RUU process will fail. The mainver is the firmware that is going to be flashed onto your phone.
For easy reference, create a new folder and name it exactly like the RUU exe file and put the rom.zip and android-info.txt in there so you won't have trouble identifying that rom.zip file later if you need to flash it again. Now, you can close the RUU installation window and all the files in that temp folder containing rom.zip will be instantly erased. Note that if you open the rom.zip with Winzip/Winrar, you will see a list of all the files but if you try to extract or double-click to open any of these files, you will get an error saying that the file is corrupt. This warning is only due to the files being encrypted by HTC, since the RUU is an official release and is digitally signed. To access those encrypted files, you will need to decrypt them on Linux.
4. Go to your bootloader. Do:
Code:
fastboot oem rebootRUU
This will reboot your HTC One and you will see a black screen with a silver HTC logo.
Now, you will need to access the rom.zip file and flash it. I have copied my rom.zip to my adb folder located at: C:/mini-sdk/rom.zip
So, i type:
Code:
fastboot flash zip C:/mini-sdk/rom.zip
Don't touch anything during the flash process. It will start and after some time, you will see FAILED error. Don't worry, it's the file preparation process if you have firmware higher than that of the RUU. Just do the same command again and the flash process will complete successfully this time. Look at the Command Prompt to know when the flash is complete. At the same time if you look at your phone, you will notice a green progress bar. When the flashing is complete on the Command Prompt, you will notice that the green bar is stuck at about 95%. This is normal. It's just a bug in the progress bar - what matters is the output from the Command Prompt window.
5. Then, you reboot. Do:
Code:
fastboot reboot
This will restart your phone. Let it boot up. It might take a little longer for the first boot up sequence. You will then have completely stock software (firmware & ROM). Go to your bootloader and check. Your S-ON/OFF and Bootloader lock/unlock are unchanged from before the RUU rom.zip flashing procedure. You can now also receive OTA updates.
I hope this has been helpful. Just press the THANKS button! :good:

If you're S-OFF you do NOT need to relock the bootloader to flash an RUU - just putting that out there

Opening android-Info.txt
Hey man,
as first thanks a lot, i got it all thanks to you but i'm still having trouble finding the right RUU.
I know you said that opening android-info.txt would help, and that it wont work with WinRar.. which i can see.
I have downloaded the .zip RUU, so.. my question is how do i open this txt file if not without WinRar.
Thanks again

emir1396 said:
Hey man,
as first thanks a lot, i got it all thanks to you but i'm still having trouble finding the right RUU.
I know you said that opening android-info.txt would help, and that it wont work with WinRar.. which i can see.
I have downloaded the .zip RUU, so.. my question is how do i open this txt file if not without WinRar.
Thanks again
Click to expand...
Click to collapse
You don't know how to open a .txt extension file? :cyclops:
Just use any text viewer/editor. I use Notepad++ and you can download it here: http://notepad-plus-plus.org/

Hi I need help!
i do all the steps and i have this massage:" failed remote:24 persing android info fail"
---------- Post added at 08:00 PM ---------- Previous post was at 08:00 PM ----------
Hi I need help!
i do all the steps and i have this massage:" failed remote:24 persing android info fail"

italgal said:
Hi I need help!
i do all the steps and i have this massage:" failed remote:24 persing android info fail"
Click to expand...
Click to collapse
Where do you get this error? At which step? Please provide more information to help resolve your problem.

i try to install many ruu i need ruu 4A.17.3250.14

thanks I will try this method in future.:good::good::good:

i have those
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA38XW900273
(bootloader) imei: 354435053862991
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__K18
(bootloader) battery-status: good
(bootloader) battery-voltage: 4192mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.046s

italgal said:
i have those
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA38XW900273
(bootloader) imei: 354435053862991
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__K18
(bootloader) battery-status: good
(bootloader) battery-voltage: 4192mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.046s
Click to expand...
Click to collapse
4A.17.3250.14 is baseband version
you need to search for an RUU based on cidnum and model id
judging from your cid .. "HTC_K18" ..its kinda rare .. i think your cid belongs to Israel and to my knowledge there is no RUU for your model

Please Help
Hello dear friend, i am so confused, i changed from apple devices to android, and i still don`t know many things.....
I just need some help, i try to do everything as you wrote and explained but when i get to the
flash zip
Click to expand...
Click to collapse
i get some errors
This is the error:
target reported max download size of 1526722560 bytes
sending 'zip' (671277 KB)...
OKAY [35.288s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 93.188s
This is my information : version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.21.3263.04
version-cpld: None
version-microp: None
version-main: 3.62.401.1
version-misc: PVT SHIP S-ON
serialno: FA36RW901770
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__032
battery-status: good
battery-voltage: 3812mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-bb768ae1
hbootpreupdate: 11
gencheckpt: 0
This is the RUU i use : ota_m7_ul_jb43_sense55_mr_htc_europe_3-62-401-1-2-24-401-8_release_338160gxmo5sd9337kadux
Please help, if you cane xplain me what to do....I implore you i wan`t my HTC back to normal
---------- Post added at 10:29 PM ---------- Previous post was at 10:17 PM ----------
Hello dear friend, i am so confused, i changed from apple devices to android, and i still don`t know many things.....
I just need some help, i try to do everything as you wrote and explained but when i get to the
Quote:
flash zip
i get some errors
This is the error:
target reported max download size of 1526722560 bytes
sending 'zip' (671277 KB)...
OKAY [35.288s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 93.188s
This is my information : version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.21.3263.04
version-cpld: None
version-microp: None
version-main: 3.62.401.1
version-misc: PVT SHIP S-ON
serialno: FA36RW901770
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__032
battery-status: good
battery-voltage: 3812mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-bb768ae1
hbootpreupdate: 11
gencheckpt: 0
This is the RUU i use : ota_m7_ul_jb43_sense55_mr_htc_europe_3-62-401-1-2-24-401-8_release_338160gxmo5sd9337kadux
Please help, if you cane xplain me what to do....I implore you i wan`t my HTC back to normal

DrDrake23 said:
Hello dear friend, i am so confused, i changed from apple devices to android, and i still don`t know many things.....
I just need some help, i try to do everything as you wrote and explained but when i get to the i get some errors
This is the error:
target reported max download size of 1526722560 bytes
sending 'zip' (671277 KB)...
OKAY [35.288s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 93.188s
This is my information : version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.21.3263.04
version-cpld: None
version-microp: None
version-main: 3.62.401.1
version-misc: PVT SHIP S-ON
serialno: FA36RW901770
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__032
battery-status: good
battery-voltage: 3812mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-bb768ae1
hbootpreupdate: 11
gencheckpt: 0
This is the RUU i use : ota_m7_ul_jb43_sense55_mr_htc_europe_3-62-401-1-2-24-401-8_release_338160gxmo5sd9337kadux
Please help, if you cane xplain me what to do....I implore you i wan`t my HTC back to normal
---------- Post added at 10:29 PM ---------- Previous post was at 10:17 PM ----------
Hello dear friend, i am so confused, i changed from apple devices to android, and i still don`t know many things.....
I just need some help, i try to do everything as you wrote and explained but when i get to the
Quote:
flash zip
i get some errors
This is the error:
target reported max download size of 1526722560 bytes
sending 'zip' (671277 KB)...
OKAY [35.288s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 93.188s
This is my information : version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.21.3263.04
version-cpld: None
version-microp: None
version-main: 3.62.401.1
version-misc: PVT SHIP S-ON
serialno: FA36RW901770
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__032
battery-status: good
battery-voltage: 3812mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-bb768ae1
hbootpreupdate: 11
gencheckpt: 0
This is the RUU i use : ota_m7_ul_jb43_sense55_mr_htc_europe_3-62-401-1-2-24-401-8_release_338160gxmo5sd9337kadux
Please help, if you cane xplain me what to do....I implore you i wan`t my HTC back to normal
Click to expand...
Click to collapse
When you get the failed message, run the flash zip command again.
Sent from my Nexus 4 using Tapatalk 2

fridgeman said:
When you get the failed message, run the flash zip command again.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Lol that's not what that error is. That's a signature verify fail and I'm pretty sure that means they're trying to flash an unsigned file or a file for another CID on a phone with security on.

Didn`t work
fridgeman said:
When you get the failed message, run the flash zip command again.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I did it still the same thing
---------- Post added at 03:33 PM ---------- Previous post was at 03:18 PM ----------
xcesivemastub8ah said:
Lol that's not what that error is. That's a signature verify fail and I'm pretty sure that means they're trying to flash an unsigned file or a file for another CID on a phone with security on.
Click to expand...
Click to collapse
Yes i got S-ON please help me what can i do to make it work

Iam using mac, can i use this steps or not? I have sucseed to unlock my htc one S-on but when i try to do recovery the mobile stucks every time ,

@DrDrake23
To find the correct RUU compatible with your HTC One, you need to look at these information:
modelid: PN0710000
cidnum: HTC__032
Then search for the RUU. I was able to find 2 versions at this location: http://www.htc1guru.com/downloads/ruu-file-downloads/
Also, according to this list: http://forum.xda-developers.com/showthread.php?t=2445289 your CID matches the region HTC-EastEurope HTC__032
These 2 RUU's should work for your device. You need to use only one of these.
RUU M7 UL JB 50 HTC Europe 1.20.401.1 Radio 4A.13.3227.06 10.27.1127.01 Release 308001 Signed 2 4
or
RUU M7 UL JB 50 HTC Europe 1.28.401.7 Radio 4A.13.3231.27 10.31.1131.05 Release 310878 Signed
It is usually recommended to use the most recent RUU. In this case, you should first try the 1.28.401.7 RUU.
However, read the description in the comment section on the site for each of these RUU's.
From your phone information:
version-main: 3.62.401.1
This means that you will need to S-OFF first before you are able to run the RUU since your main version is higher than both of these RUU's.
On another note, you should always read up and do enough research before attempting to modify your phone. Do you really need to go back to 100% stock? You could simply flash a stock ROM or even better, a custom ROM. But if you believe you need to return your device to 100% stock condition, start here: http://forum.xda-developers.com/showthread.php?t=2488772 and then you can flash hboot 1.44 and finally run the RUU.

marjanna said:
Iam using mac, can i use this steps or not? I have sucseed to unlock my htc one S-on but when i try to do recovery the mobile stucks every time ,
Click to expand...
Click to collapse
I tested the entire procedure successfully on my Windows XP SP3 32-bit. So, i cannot say if this would work on another OS or if the commands would be the same for that matter. Maybe someone with a Mac can confirm and help you out.

electronical said:
I tested the entire procedure successfully on my Windows XP SP3 32-bit. So, i cannot say if this would work on another OS or if the commands would be the same for that matter. Maybe someone with a Mac can confirm and help you out.
Click to expand...
Click to collapse
Ok i see. It seems that most use pc:s , i have tryied and still trying to find a Mac user , but no luck so far,
I got a 4.2.2 HTC One
HTC Sense Version 5.0
S-On
Unlocked
Tampered
I have heard that its better and safer to change the S-On to S-Off but no luck yet. this guide looks great but i might wait to be secure so i dont brick the phone trying to.
Take care and thanks for replying ..
:laugh::good::laugh::good::laugh:

This process saved me.
I had a bad flash and could not get adb to recognize my device.
Just a quick note, bootlocker must be re-locked if you on S-on.
Thanks for the help man!

DrDrake23 said:
I did it still the same thing
Yes i got S-ON please help me what can i do to make it work
Click to expand...
Click to collapse
If u are s-on you have to re-lock the bootloader...

[GUIDE][S-ON] Restore your (European) HTC One M8 back to stock

Hi all,
I've created a simple guide to restore your HTC One M8 back to stock firmware while still being on S-ON.
This guide will provide you with all the files required to restore your EUROPEAN device back to stock.
If you have an device from another region, you'll need to find the RUU & recovery image yourself. (see below)
Prerequisites:
- HTC Drivers (just install HTC Sync and the included drivers, then remove HTC Sync)
- Fastboot package
- Stock recovery.img (you'll need the recovery.img with the same fw version as the RUU you're going to flash) (Link to 4.16.401.10 recovery.img for European non-carier devices)
- The RUU for your region/carrier. (Link to 4.16.401.10 for European non-carier devices)
If you have an USA /USA carrier device, go here for the RUU files
If you have an device from another region than Europe or USA, good luck finding the correct RUU
Look here to find recovery.img files for all regions (thanks to @exocetdj)
Because this guide is intended for S-ON, only the RUU for your region/carrier will work.
If you don't have an RUU or cannot find one for your region/carrier, S-OFF your device and follow this guide to restore your HTC One M8 back to stock. (thanks to @EddyOS)
After you've gone trough all steps;
- The red text during boot will be gone
- You'll have the stock firmware, system, recovery and boot.img
- Your bootloader will say "Relocked"
- Your bootloader will say "Software status: Official"
Let's start:
Step 1:
Start the RUU exe by double clicking on it, it will take a few seconds before it starts. After it has started, do not continue but go to your temp folder (type %TEMP% in your address bar)
Find the folder with the temporary files from the RUU (mine was called: {C48DBAA3-1CC0-4DF6-B069-B9CCB27F93C9})
Inside this folder there should be a few files and another folder with a long code as name (mine was called: {50F2F878-636A-496F-A7CB-544C067E0C4B})
Inside this folder, scroll down until you find rom.zip, open this file
Extract boot_signed.img and place it in a folder with the downloaded stock recovery and the fastboot.exe file
Now close the RUU installation wizard
Step 2:
Turn off your device
Hold VOL-Down + Power, after a few seconds you'll be in the bootloader. Now release the buttons
Navigate with the volume buttons to fastboot and confirm with the power button.
Step 3:
You should now have a folder with the following files:
- fastboot.exe
- AdbWinApi.dll
- AdbWinUsbApi.dll
- boot.img (extracted from the rom.zip)
- recovery.img (see prerequisites)
Inside the folder while holding shift, click right mouse and choose Open command window here
Before starting, it's recommended to rename the recovery file to recovery.img and the kernel to boot.img
Type the following commands in order (make sure to check the output and see if every command is successful before executing the next command)
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot oem lock
This will push the stock kernel & recovery and relock your device.
Step 4:
Open the RUU installation wizard again and follow the instructions.
It will start flashing the RUU on your device.
After 8-12 minutes, the installation will be complete and your device will boot into system.
Step 5: (optional)
Power off your device
Hold VOL-Down + Power, after a few seconds you'll be in the bootloader. Now release the buttons
Verify that your bootloader says "Relocked" & "Software status: Official"
Congratulations, your device is back to stock again. After it's finished booting and optimizing 261(!) pre installed apps, you'll be greeted by the setup wizard on your phone.
If you have any questions, let me know.
Common problems:
Fastboot cannot find my device?
- try reinstalling the HTC drivers included with HTC Sync, and make sure to remove HTC Sync afterwards but leaving the drivers installed
I've got error 155 when trying to flash the RUU
- make sure your bootloader is locked. This tool only works when you have stock kernel, recovery and your bootloader is locked or relocked.

Reserved

TAMPERED
UNLOCK
M8_UL PVT SHIP S-ON
HBOOT- 3.16.0.0000
RADIO-1.16.2133156.UA15g
OpenDSP-v38.2.2-00542-m8974.0311
OS-1.54.401.10
eMMC-boot 2048MB
ــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــ
This is my phone , should i do any thing more or just the steps u mentioned???
I was told that i must upgrade my firmware, must i ??
Thanks

This is a great guide for those that just want to return to stock for their own purposes. However, this will not be enough for sending the phone into warranty, for that you'll need to take a few more steps with S-Off to get that RELOCKED flag to say LOCKED.

dima470 said:
This is a great guide for those that just want to return to stock for their own purposes. However, this will not be enough for sending the phone into warranty, for that you'll need to take a few more steps with S-Off to get that RELOCKED flag to say LOCKED.
Click to expand...
Click to collapse
From my experience with HTC warranty repairs, they don't really care about the bootloader being 'relocked', S-Off is a more common cause for them to not repair the device.
But, above differs per repair center / per country
al_wizard said:
TAMPERED
UNLOCK
M8_UL PVT SHIP S-ON
HBOOT- 3.16.0.0000
RADIO-1.16.2133156.UA15g
OpenDSP-v38.2.2-00542-m8974.0311
OS-1.54.401.10
eMMC-boot 2048MB
ــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــ
This is my phone , should i do any thing more or just the steps u mentioned???
I was told that i must upgrade my firmware, must i ??
Thanks
Click to expand...
Click to collapse
Where did you bought your device?

al_wizard said:
TAMPERED
UNLOCK
M8_UL PVT SHIP S-ON
HBOOT- 3.16.0.0000
RADIO-1.16.2133156.UA15g
OpenDSP-v38.2.2-00542-m8974.0311
OS-1.54.401.10
eMMC-boot 2048MB
ــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــ
This is my phone , should i do any thing more or just the steps u mentioned???
I was told that i must upgrade my firmware, must i ??
Thanks
Click to expand...
Click to collapse
You are S-ON so you need to relock the bootloader and run the ruu.
If you want to give all info to work with you need to post the outcome of :
Fastboot getvar all
Delete the serial and imei and post the list here.
Or check the firmware & nand backup thread here in the general section. Restore the stock rom and recovery and perform ota updates which also will upgrade the firmware
---------- Post added at 07:45 PM ---------- Previous post was at 07:43 PM ----------
Joery360 said:
From my experience with HTC warranty repairs, they don't really care about the bootloader being 'relocked', S-Off is a more common cause for them to not repair the device.
But, above differs per repair center / per country
Where did you bought your device?
Click to expand...
Click to collapse
Has nothing to do with where he bought it from, it is depending on the phones hardware & software, for all we know its imported.
The specs are important not where he got it from. And you can't tie it down on how repair centers handle the phones....that's a matter of good luck !

Joery360 said:
Where did you bought your device?
Click to expand...
Click to collapse
I bought it second-hand from Qatar if you mean country.

Hi. I tried to use this guide but it I couldn't follow it through. I have relocked, tempered, S-ON, CID : TMOB102 phone. It is stuck in the HTC logo after a full wipe from twrp. I don't have OS, and the main version is empty. So far I have tried all the European RUU which gave CID error and 2 T-Mobile RUU's with MID error both. Can anyone give me a suggestion?

Problem extracting boot_signed.img
When I try to extract the boot_signed.img akk I get from Winzip is "cant find central directory"
Any ideas??

This is a great guide for those that just want to return to stock for their own purposes.

Hi,
I just needs to get OTA on my phone and i dont mind it being tampered or unlocked.
Will this method work on my phone ?
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.2133156.UA15G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH495WM01309
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__J15
(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: 098a72e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

:/
I tried to flash the boot.img but I get this error:
C:\Users\Ali\Desktop\Fastboot>fastboot boot boot.img
creating boot image...
creating boot image - 8994816 bytes
downloading 'boot.img'...
OKAY [ 0.894s]
booting...
FAILED (remote: not allowed)
finished. total time: 0.895s
I have no OS now if I try to reboot I get stuck on boot logo. What can I do to get back to stock with OTA and everything?
C:\Users\Ali\Desktop\Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.21331147A1.29G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.33.61.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: ORANG001
(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: 4c3fbd70
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.020s

thanks this helped me revive my m8

Pc can't identify my device. phone gets htc logo then it turns black and disconnects from pc. RUU wiz error (170) usb connection error.

royalkalana said:
Hi,
I just needs to get OTA on my phone and i dont mind it being tampered or unlocked.
Will this method work on my phone ?.....
Click to expand...
Click to collapse
Yes
gorner92 said:
I tried to flash the boot.img but I get this error:
C:\Users\Ali\Desktop\Fastboot>fastboot boot boot.img
creating boot image...
creating boot image - 8994816 bytes
downloading 'boot.img'...
OKAY [ 0.894s]
booting..
Click to expand...
Click to collapse
Please check if your device is unlocked. You can't flash boot.img's while on a locked bootloader.
Cpre said:
Pc can't identify my device. phone gets htc logo then it turns black and disconnects from pc. RUU wiz error (170) usb connection error.
Click to expand...
Click to collapse
Reinstall the HTC drivers.

gorner92 said:
I tried to flash the boot.img but I get this error:
C:\Users\Ali\Desktop\Fastboot>fastboot boot boot.img
creating boot image...
creating boot image - 8994816 bytes
downloading 'boot.img'...
OKAY [ 0.894s]
booting...
FAILED (remote: not allowed)
finished. total time: 0.895s
I have no OS now if I try to reboot I get stuck on boot logo. What can I do to get back to stock with OTA and everything?
C:\Users\Ali\Desktop\Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.21331147A1.29G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.33.61.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: ORANG001
(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: 4c3fbd70
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.020s
Click to expand...
Click to collapse
You are using the wrong command ! It's :
Fastboot flash boot boot.img
NOT
Fastboot boot boot.img ! That's why you got stuck. And indeed make sure the bootloader is UNLOCKED before you flash !
While i don't even know flashing the boot.img and recovery seperatly first is actually needed because all that's needed is to relock the bootloader and run the ruu.exe or the temp rom.zip via sd card.
afaik the ruu method takes care of the boot.img and recovery on its own.

Got a problem with 3rd command (locking oem) in step 3. It goes like this:
C:\adb>fastboot flash boot boot.img
target reported max download size of 1826021376 bytes
sending 'boot' (8780 KB)...
OKAY [ 1.001s]
writing 'boot'...
OKAY [ 0.464s]
finished. total time: 1.465s
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 1826021376 bytes
sending 'recovery' (16044 KB)...
OKAY [ 1.710s]
writing 'recovery'...
OKAY [ 0.646s]
finished. total time: 2.357s
C:\adb>fastboot oem lock
...
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) [PGFS] partition_update_pgfs: pg2fs_sec_recovery
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = -1610744452 (0x9FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
FAILED (status read failed (Too many links))
finished. total time: 1.194s
My getvar all before flashing:
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.22.21331147A1.29G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
meid: 0000000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cindum: HTC__032
Now my phone is stuck on my ROM's boot logo and now I can't access bootloader.
EDIT:
I've managed to access bootloader by holding power + volup and then holding vol down. After that installing via RUU went smooth.

Hi, I followed your instructions, but before I could start with 4th device booted up and i accidentaly accepted upgrade. It rebooted and upgraded the device, and then stuck on boot screen. Now I try to update it through RUU but it says image version 4.16.401.13, and I can't find RUU for that version. Any ideas? Can I somehow reinstall twrp and restore nandroid backup?
P.S. in bootloader it still says software status: modified :/
P.P.S. I still managed to make RUU go through all the steps, from a billionth time. It would usually stuck on steps 0, step 1, or step 3. Now it seems like it's booting fine... Time to shower away all the cold sweat from my body.

Hi Guys,
I have windows 8.1 and can't open rom.zip file. I have an error : The compressed Folder is invalid. Installed winzip, 7-zip - can't go ahead.

If you are having trouble sending the ruu and you are stuck at sending 0/7 or 1/8 and only htc logo. then just delete htc sync manager from your pc!!!

HTC One M9, Original, Locked, S-ON

Good day everyone.
After two weeks of trying and searching the web for an answer I have finally given up and decided to post my question here, perhaps someone has an idea that can help.
I have an HTC One M9 that was stashed away in a cupboard, I decided that I am going back to it as my current phone is just not working for me, however, I LOVE the hardware on the One M9 but I do not like the HTC Sence UI and decided that I will flash it with a custom ROM. Needless to say I completely stuffed it up. (I probably should have S-OFF and unlocked before I tried flashing. (Also didn't enable developer options or USB debugging - stupid stupid me)
Herewith the symptom. I can boot into download mode but not recovery, when i boot into recovery the black HTC logo appears and then disappears, appears, disappears etc etc so ABD does not work.
I have tried the RUU route but as soon as the installer reboots the phone it does the whole black logo loop thing. the get_identifier_token command also returns bank (see output below) so can't even use the htcdev procedure.
I have tried manually flashing zip and img files and get a 9 RU_SECURITY_FAIL boot and bootloader isn't BL_UNLOCK also tried flashing stock recovery.img rom.
Rom:
M9_3.35.401.12_FullStock_wipe.zip
M9_3.35.401.12_NoWipe_TWRP2871b1.zip
0PJAIMG_HIMA_UHL_M60_SENSE70_HTC_Europe_3.35.401.12_Radio_01.01_U11440792_97.00.51203G_F_release_signed.zip
RUU_HIMA_UHL_L50_SENSE70_HTC_Europe_1.32.401.17_Radio_01.01_U11440261_56.02.50306G_2_F_release_429340_signed_2_4.exe
Manually flashing with extracted rom in RUU file
hima_uhl_n70_hosd_signed.img
HTC_One_M9_1.32.401.8_recovery_signed.img
twrp-3.2.1-0-hima.img
Used the SDCARD option
I did the fastboot erase cache process
At some point I was able to htc_fastboot flash zip rom.zip and it sent up to 50% but just remained there
Original Software
LOCKED
S-ON
htc_fastboot "works"
D:\Desktop\HTC\HTC One M9 Toolkit 2 1.6.1\adb>htc_fastboot.exe getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: XXXXXXXXXXXX
(bootloader) version-main: 3.35.401.12
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440792_97.00.51203G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__016
all:
finished. total time: 0.004s
htc_fastboot finished. total time: 1.143s
flash example:
D:\Desktop\HTC\HTC One M9 Toolkit 2 1.6.1\adb>htc_fastboot.exe flash zip d:\roms\M9_3.35.401.12_FullStock_wipe.zip
htc_fastboot.exe v3.0.7 (2015-03-30)
target reported max download size of 800000000 bytes
sending 'zip' (134610 KB)...
OKAY [ 8.962s]
writing 'zip'...
(bootloader) HOSD CL#671758
FAILED (remote: 9 RU_SECURITY_FAIL zip from usb command in download mode)
finished. total time: 10.121s
htc_fastboot finished. total time: 12.576s
D:\Desktop\HTC\HTC One M9 Toolkit 2 1.6.1\adb>htc_fastboot.exe oem get_identifier_token
...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.162s]
finished. total time: 0.162s
htc_fastboot finished. total time: 1.335s
Please help or even tell me I am doing something wrong.
Thank you

Wrong forum, pal. This is the One M9 PLUS forum.

My bad apologies.