Database Users

[Q] Messed up magic, can't flash anything

Hi,
Here's a magic on my desk, which only starts fastboot and nothing else. First of all it's not my fault I'm just trying to fix it. It was my phone then I gave it to my cousine. At this point there was running a cyanogenmod on the phone. Then there were some problems with the phone and a friend of my cousins boyfriend tried to fix it, but he didn't. He flashed something and messed it up. Now he's somewhere abroad and nobody really knows, what he did to the phone. So here we are.
What does or doesn't do the phone?
POWER ON -> Vodafone splash -> crash!
POWER ON + HOME -> Vodafone splash -> crash!
POWER ON + BACK -> three androids on skate boards!
This means I can only start fastboot. When I connect it to the pc, I can "fastboot devices" list the phone. So here are all information I could get from the phone:
-from the phone screen
Code:
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.33.0009 (SAPP10000)
CPLD-10
RADIO-6.35.16.19
May 8 2009,21:02:32
FASTBOOT USB...
-by fastboot commands
Code:
-bash-4.1$ fastboot getvar version
version: 0.5
-bash-4.1$ fastboot getvar version-bootloader
version-bootloader: 1.33.0009
-bash-4.1$ fastboot getvar version-baseband
version-baseband: 6.35.16.19
-bash-4.1$ fastboot getvar version-cpld
version-cpld: 10
-bash-4.1$ fastboot getvar version-microp
version-microp: None
-bash-4.1$ fastboot getvar version-main
version-main: 1.89.162.1
-bash-4.1$ fastboot getvar serialno
serialno: ************* <- replaced
-bash-4.1$ fastboot getvar product
product: sapphire
-bash-4.1$ fastboot getvar platform
platform: HBOOT-7201A
-bash-4.1$ fastboot getvar mid
mid: SAPP10000
-bash-4.1$ fastboot getvar cid
cid: VODAP102�"
-bash-4.1$ fastboot getvar battery-status
battery-status: good
-bash-4.1$ fastboot getvar battery-voltage
battery-voltage: 4119mV
-bash-4.1$ fastboot getvar partition-layout
partition-layout: HTC
-bash-4.1$ fastboot getvar security
security: on
-bash-4.1$ fastboot getvar build-mode
build-mode: SHIP
-bash-4.1$ fastboot getvar boot-mode
boot-mode: FASTBOOT
-bash-4.1$
SAPPHIRE PVT 32A <-- this is totally wrong. It is definitely a 32B! So it looks like the guy tried to flash a wrong image.
I already tried to flash some new images via fastboot, but I only get the error "FAILED (remote: signature verify fail)". The last two days on research told me this is because there is "S-ON" and no engineering SPL installed.
Next I tried to boot some recovery images directly via fastboot, but it only uploads the image, reboots, shows the vodafone splash and finally crashs. I tried recovery image versions for 32A and 32B.
Flashing with sappimg.zip or sappimg.nbh on SD-Card also crashs when he tries to update the radio.
My conclusion is that there is a wrong radio installed, but because of the SPL, which can't flash anything and every other action crashs, device might be bricked
Does anybody have an idea, how to bring the phone back to life again without going the JTAG-path?

It's pretty much bricked. Your not going to be able to get any RUU or sappimg files to run because it's going to try to update the radio first, but the radio partition is hosed because of the SPL.
The only thing I can possibly think you can do is to flash a 32A engineering SPL using the goldcard method and then fastboot flashing the correct SPL/radio combo. Again, this probably isn't going to work.

Thanks for your reply. I missed, that there's already a thread with exactly the same problem. So I'll continue there...

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.

[SOLVED]SPL/Radio mismatch HTC Magic 32a

Hi!
I think my phone is bricked... or semi-bricked.
I was using eyegor's radio switcher to switch SPL/Radio/Recovery every time I was changed the rom. I used:
hboot-1.33.2010OldSPL.img
Radio_HTC_PVT_32A_3.22.20.17OldRadio.img
recovery-RA-magic+-v2.2.1-bladyle
everything was nice, but my battery started to die... every day I had to charge it. So I bought a new battery and I thought, it would be nice to be formatted with a stock rom. So I started to install RUU_Sapphire_HTC_Europe_3.05.401.1_test_signed_NoDriver.exe (what I installed the same way like before with success). When it got to update RADIO_V2 my screen goes black and the update failed.
Now when I try to turn the phone on (showing me the same with POWER; BACK+POWER; HOME+POWER; VOL_DOWN+POWER), says:
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.76.0008 (SAPP10000)
CPLD-12
RADIO-3.22.20.17
I can access fastboot from computer, but adb not. I searched all over the internet to find solution to this.
Code:
fastboot oem boot
gives me in output:
Code:
...
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x8F083CA4
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 32
(bootloader) TAG:hwid 0x1
(bootloader) TAG:skuid 0x21401
(bootloader) TAG:hero panel = 0x0
(bootloader) TAG:engineerid = 0x2
(bootloader) Device CID is not super CID
(bootloader) CID is VODAPC23
(bootloader) setting.cid::VODAPC23
(bootloader) serial number: HT95XKF02109
(bootloader) commandline from head: no_console_suspend=1 console=null
(bootloader) command line length =365
(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=VODAPC23
(bootloader) androidboot.carrier=COMMON androidboot.mid=SAPP10000 android
(bootloader) boot.keycaps=qwerty androidboot.mode=normal androidboot.seri
(bootloader) alno=HT95XKF02109 androidboot.bootloader=1.76.0008 no_consol
(bootloader) e_suspend=1 console=null
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=cache
(bootloader) aARM_Partion[5].name=userdata
(bootloader) partition number=6
(bootloader) Valid partition num=6
(bootloader) 69466957
(bootloader) 69784520
(bootloader) 7473
(bootloader) 0
(bootloader) 0
(bootloader) 0
(bootloader) 0
(bootloader) 0
(bootloader) 0
(bootloader) 0
(bootloader) 0
(bootloader) 0
(bootloader) 0
(bootloader) 0
(bootloader) 0
(bootloader) 0
(bootloader) 0
(bootloader) 0
(bootloader) 0
(bootloader) 0
(bootloader) 0
(bootloader) 0
(bootloader) 0
(bootloader) 0
(bootloader) 0
(bootloader) 0
(bootloader) 0
(bootloader) 0
(bootloader) 0
(bootloader) 0
(bootloader) 0
(bootloader) 0
FAILED (status read failed (Too many links))
finished. total time: 8.454s
after 2-3 minutes brings up the old rom, but at the beginning force closes and restarts
I tried to install other ruu-s but with no success. I created a goldcard, tried to flash sappimg.zip from RUU_Sapphire_HTC_Europe_2.16.401.6_Vodafone_CZ_release_signed_NoDriver.exe but it fails at the very beginning with "43 main version check fail".
mumilover's fastboot commander's output:
Code:
###Calling fastboot with: getvar version-bootloader###
version-bootloader: 1.76.0008
finished. total time: 0.002s
********************************
###Calling fastboot with: getvar version-baseband###
version-baseband: 3.22.20.17
finished. total time: 0.004s
********************************
###Calling fastboot with: getvar version-main###
version-main: 3.05.401.1
finished. total time: 0.001s
********************************
###Calling fastboot with: getvar cid###
cid: VODAPC23âSÐ
finished. total time: 0.001s
********************************
###Calling fastboot with: getvar version-cpld###
version-cpld: 12
finished. total time: 0.001s
********************************
###Calling fastboot with: getvar product###
product: sapphire
finished. total time: 0.000s
********************************
###Calling fastboot with: getvar mid###
mid: SAPP10000
finished. total time: 0.001s
********************************
###Calling fastboot with: getvar security###
security: on
finished. total time: 0.000s
********************************
###Calling fastboot with: getvar build-mode###
build-mode: SHIP
finished. total time: 0.001s
********************************
I saw mumilover helped to someone with almost the same problem, maybe he or someone can help me.

So it can't be solved...
If someone in Serbia can JTAG, I would be send to him/her and pay for it...

Don't know why I was thinking like a noob... a had already extracted the RUU_Sapphire_HTC_Europe_3.05.401.1_test_signed_NoDriver.exe and I always tried to flash only the rom.zip which failed at radio update. So now I tried to flash the other zip... rom1.zip
Now I have working hboot, fastboot and a system which I cant access

It looks like no one can help me...
I tried to make a goldcard, with two cards. The first was 4gb Kingston sdcard and the second one is a noname 512mb sdcard. Without my goldcards I get Model ID error. With the goldcard inserted (never mind which one) I pass this check, but fails at main version check. I read on many forums and tutorials how to make a goldcard... On these sites I found many answers. Someone says the goldcard is good when passes the Model ID check. But there are a few responds where they say they can pass the main version check... Somewhere on this forum with almost the same problem (SPL/Radio mismatch) someone wrote that he had to make three goldcards to pass the main version check, but with first two he passed only the Model ID check...
Now I'm a little bit confused... I would appreciate if someone can confirm that the goldcard is then a good goldcard when it can pass the main version check (in RUU - ERROR 140 - BOOTLOADER VERSION ERROR).
If someone confirms this I will buy more sdcard (because I bought my phone without a sdcard (for those sdcards which comes with the phone everyone says these are good for creating a goldcard (said on the forums)) before two years)...

... and sorry for my really bad english

more than 140 views and no one replied...
wondering...
if XTC Clip can help me?

I wrote you a pm.
"Main version is older" is not something which a goldcard can fix...
But we can fix that :0)
We just need to get into the system, flash a different misc partition and you should be able to flash a different ruu file.
Once we have a matching spl/radio combo, we can flash a different combo matching your device (32A).

I have to say... many thanks to mumilover, because he wanted to help me. I told him in Monday that I ordered a XTC Clip by Raskal and I want to try it first... Today I got the Clip and successfully unlocked it... it said S-OFF and showed in fastboot:
before:
SAPPHIRE PVT 32A ENG S-ON H
HBOOT-1.76.0008 (SAPP10000)
CPLD-12
RADIO-3.22.20.17
after:
SAPPHIRE PVT 32A ENG S-OFF H
HBOOT-1.76.0008 (SAPP*****)
CPLD-12
RADIO-3.22.20.17
downloaded the original ROM, which was for me RUU_Sapphire_HTC_Europe_2.16.401.6_Vodafone_CZ_release_signed_NoDriver because of my phone was VODAPC23... now in fastboot with command:
fastboot oem boot
it gives me "CID is super CID" and "setting.cid::11111111"
when the unlock succeeded I type in cmd:
fastboot oem rebootRUU
unpacked, the downloaded RUU and installed the "update"(downgrade):
fastboot flash zip rom.zip
everything went well! So now my phone works like new, but it is unlocked If someone will have same problem I suggest to buy a XTC Clip from Raskal...

Anyway, how can I make it solved?

How did you do it?
I have the same issue. My phone is stuck in ruu mode. I have an xtc clip but when I try it, it does nothing. I assume its because the phone is still stuck in ruu mode but how do I get it out of ruu mode?
Can you help me?
SPL and Radio are exactly as above.
Thanks.

Here is my exact device info.
...........................................................
Operating system: Windows.
Tools folder and fastboot file(s) created.
The folder containing the IMG files was not found.
No Nandroid folder was not found - "Restore" button disabled.
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
SPL/hboot version: 1.76.0008.
Radio version: 3.22.20.17.
Main software version: 3.05.401.1.
cid: roger001.
cpld: 12.
product: sapphire.
mid: sapp50000.
security: on.
build-mode: ship.
-----------------------------------.
Print of device info SUCCESSFUL.
This device does not have s-off nor eng hboot.

To get into fastboot/hboot and get rid of ruu screen:
1.a. Download RUU_Sapphire_HTC_Europe_3.05.401.1_test_signed_NoDriver.exe and extract it.
Find rom.zip and rom1.zip files
1.b. Or download rom.zip and rom1.zip
2. Put these zip files in the same folder where is fastboot.exe
3. Connect your phone to PC in RUU mode
4. Run the commands from the same directory:
Code:
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip rom.zip
This will fail. Disconnect the phone, get the battery out for 10secs, put back and connect to PC.
Code:
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip rom1.zip
This will be successfully installed. And now you have fastboot/hboot. In XTC Clip make the goldcard. Put the card in the phone and power on with VOLUME_DOWN+POWER.

jeBACH said:
To get into fastboot/hboot and get rid of ruu screen:
1.a. Download RUU_Sapphire_HTC_Europe_3.05.401.1_test_signed_NoDriver.exe and extract it.
Find rom.zip and rom1.zip files
1.b. Or download rom.zip and rom1.zip
2. Put these zip files in the same folder where is fastboot.exe
3. Connect your phone to PC in RUU mode
4. Run the commands from the same directory:
Code:
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip rom.zip
This will fail. Disconnect the phone, get the battery out for 10secs, put back and connect to PC.
Code:
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip rom1.zip
This will be successfully installed. And now you have fastboot/hboot. In XTC Clip make the goldcard. Put the card in the phone and power on with VOLUME_DOWN+POWER.
Click to expand...
Click to collapse
Thanks.
I figured this out last night but thanks anyway.
Just to add, to get back to a bootable system, I had to flash another rom after completing the above steps.

Is there a way to get the Tom and rom1 rehosted? If not where can i get it from?

tlipur said:
Is there a way to get the Tom and rom1 rehosted? If not where can i get it from?
Click to expand...
Click to collapse
You can get the ROM from HTC Dev. You need to sign up for an HTC Dev account and then go to the HTC bootunlocker page (you have to google as I'm not allowed to post the link). You can download the RUU there and then once downloaded open the file and when its open go to %temp% (or your temp file directory) and find the most recent modified folder. Inside of there you will find another folder which will contain, amongst other things rom[1].zip file(s).

rom.zip
rom1.zip

Awesome thanks
Sent from my GT-P7510 using Tapatalk 2

[Q] HELP: adb,ruu,bootloader,fastboot freeze stuck

Hi guys,
I've searched all over the internet and offcourse XDA but I don't know what to do anymore.
Somehow my HTC Desire Z frooze a few weeks back, and after pulling the battery the phone was stuck at the HTC screen. I tried factory reset,recovery etc but that all didn't work. The phone just freezes.
The phone is NOT rooted, unlocked etc. No apps where installed before the phone froze.
Some information:
Code:
VISION PVT SHIP S-ON
HBOOT-0.85.0013
MICROP-0425
RADIO-26.10.04.03_M
eMMC-boot
Apr 11 2011,23:36:27
"fastboot getvar all" output:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.85.0013
(bootloader) version-baseband: 26.10.04.03_M
(bootloader) version-cpld: None
(bootloader) version-microp: 0425
(bootloader) version-main: 2.42.405.4
(bootloader) serialno: SH0B9RT0****
(bootloader) imei: ****************
(bootloader) product: vision
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PC1011000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 4124mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 81c588a7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
1. Downloaded this RUU which i'm sure it's correct.
RUU_Vision_Gingerbread_S_HTC_WWE_2.42.405.2_Radio_12.56.60.25_26.10.04.03_M_release_199043_signed
2. Drivers are installed and recognized (fastboot and bootloader) on Windows 7 x64 and Windows XP Home Edition. (have 2 PC's just in case)
3. I have installed the latest Android SDK.
4. I have installed HTC Sync. (messed around with drivers from Google and HTC)(believe me I know what i'm doing so it can't be because of the drivers)
5. I don't have or need a goldcard.
6. ADB is recognized by Windows but shows
Code:
error: device not found
7. Fastboot lists my device as "fastboot devices"
Code:
SH0B9RT0**** fastboot
8. When in HBOOT I can manually switch back and forth between fastboot and bootloader, but when selecting "reboot bootloader" from the fastboot menu the phone immediatly freezes again.
9. When the RUU reboots the bootloader the phone freezes.
10. When the RUU says "waiting for bootloader", and I manually power on the phone to HBOOT (seen as "Android Bootloader Interface" by Windows) the phone still isn't recognized.
11. Also tried updating the device list for ADB from the command line "androind update adb" - no result
12. Manually add the device ID "0BB4" to "adb_usb.ini" - still not seen by ADB.
I really believe I tried everything google threw at me. Can my bootloader be corrupted somehow? Any suggestions?
--------------------
UPDATE:
I extracted the ROM.zip from the RUU, renamed it to PC10IMG.zip and placed it in the root of my SD card. Booted up the phone in HBOOT and it automaticly started the update process. At this point it is once again stuck at the bootloader.
At this point I think the eMMC chip is dead.
Code:
[COLOR="Blue"]HBOOT[/COLOR]
[COLOR="Green"]Parsing PC10IMG.zip [SD ZIP]
[1] BOOTLOADER [COLOR="Magenta"]- Updating[/COLOR]
[2] BOOT
[3] RECOVERY
[4] SYSTEM
[5] SPLASH1
[6] SPLASH2
[7] USERDATA
[8] TP
[9] TP
[10] RADIO_V2
[11] RADIO_CUST[/COLOR]
[COLOR="Blue"]Do you want to start update?[/COLOR]
[COLOR="Red"]<VOL UP> Yes
<VOL DOWN> No[/COLOR]
[COLOR="Blue"]Update is in progress...[/COLOR]
[COLOR="Red"]Do not power off the device![/COLOR]

I have the same issue with a TMOUS G2
tried all the steps like you
also tried flashing just the hboot first and also the whole rom through ADB in fastboot but i get a weird error that the command was incorrect by 1byte or something like that
did you ever get anywhere with your phone?

You've probably got a fried emmc, which is a hardware issue.
if it is that, there is nothing you can do about it, except get a warranty replacement (if its still under warranty)
Being unrooted and S-ON limits anything you can do even if the emmc isn't fried.
-Nipqer

Nipqer said:
You've probably got a fried emmc, which is a hardware issue.
if it is that, there is nothing you can do about it, except get a warranty replacement (if its still under warranty)
Being unrooted and S-ON limits anything you can do even if the emmc isn't fried.
-Nipqer
Click to expand...
Click to collapse
yup :/
it was even a pain in the ass to try to do the PC10 method because all zips I found from the gude to restore to stock were too old.. fortunately I was able to extract the rom from the update from a few weeks ago and that would have worked, but as you say, I think my emmc is hosed
wish there was a tool like on the evo where you purposely 'hardbrick' the phone but can flash/repartition the bootloader in ubuntu

[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...