[Q] Radio ROM backup - Click Android Development
Hi,
I'm creating a new thread because I did not find anything here related to that specific topic.
I would like to backup my radio ROM before flashing a WWE one. My intent is to test the WWE and if anything goes wrong with e.g the simlock I'll restore the original one.
Some directions : all /dev/block/mtdblock* are not used (appart from system, cache & data) should it be there ? maybe not using yaffs2 ?
Any enlightening suggestions appreciated !
Cheers
gelim said:
Hi,
I'm creating a new thread because I did not find anything here related to that specific topic.
I would like to backup my radio ROM before flashing a WWE one. My intent is to test the WWE and if anything goes wrong with e.g the simlock I'll restore the original one.
Any enlightening suggestions appreciated !
Cheers
Click to expand...
Click to collapse
you can find your own radio image inside of the wwe.. nowadays there are 2 radio for tattoo: orange and stock.
let's say I'm not trusting the WWE content downloaded via an untrusted source ?
Is there really no technical way to achieve that when being root on the phone ?
Thanks
gelim said:
let's say I'm not trusting the WWE content downloaded via an untrusted source ?
Is there really no technical way to achieve that when being root on the phone ?
Thanks
Click to expand...
Click to collapse
don't know, but to achieve your own radio.img from the phone you shoud dump it from the internal memory. Maybe a full backup from recovery saves that image.
> you shoud dump it from the internal memory
yes but it's unclear how to do it. There are several kind of memory in the phone... My bet goes on the NAND one but ATM I don't know how to access the first mtdblocks)
# mount -t yaffs2 -o ro /dev/block/mtdblock0 /sdcard/radio
mount: mounting /dev/block/mtdblock0 on /sdcard/radio failed: Invalid argument
Click to expand...
Click to collapse
(same for 1 & 2)
some kernel log to illustrate that :
[ 5261.980407] yaffs: Attempting MTD mount on 31.0, "mtdblock0"
[ 5261.980926] yaffs: NAND geometry problems: chunk size 2048, type is yaffs2, inbandTags 0
[ 5266.192199] yaffs: dev is 32505856 name is "mtdblock0"
[ 5266.192474] yaffs: passed flags ""
Click to expand...
Click to collapse
> Maybe a full backup from recovery saves that image.
No full backup from recovery (using amora's one) doesn't dump radio.img. That's why I'm asking here.
When you open an official RUU from HTC, all .img are extracted on temp folder. So you can take it from here.
Actually my problems changed a little bit after doing the mount yaffs2 whitout success I issued a reboot from adb.
From now on, my Tattoo won't pass the (vibrate)Tattoo boot logo. I can't go into recovery either (should be just after the Tattoo logo displaying). The only functionnal thing is the fastboot menu and doing a fastboot flash boot boot.img (got that from the RUU) I'm left with the classis FAILED (remote: not allow) thing.
I think I'm doomed and I bricked that little piece of hardware :-(
applying an official RUU should unbrick it
it only needs fastboot usb mode
Yes, should.
potattoo: there is a CID check on this device, it needs to be bypassed using the Goldcard technique AFAIK.
Another protection is hboot has S-ON (signature verification) so I'm out of luck with the manual fastboot flash or update (required some *.sig apparently)
I did an RUU flash from Windows XP (inside a Virtualbox) it managed to reboot the phone (I wasn't able to do that with fastboot reboot !) and timeout on the "waiting for bootloader...". During that time the phone is frozen with the HTC logo.
UPDATE: on a physical windows it's better, the RUU WWE cleans userdata, and then tries to flash the zipped ROM... until it fails. I can now reproduce this behavior manually with fastboot.exe. Here are the log messages :
c:\fastboot>fastboot flash zip rom.zip
sending 'zip' (88968 KB)
...
OKAY [ 14.052s]
writing 'zip'...
INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 41.400s
Click to expand...
Click to collapse
Let's try an oem boot to see what it could say :
c:\fastboot>fastboot oem boot
...
INFO[ERR] partition_read::Failed to read page
INFO22912 or it is empy
INFOsetup_tag addr=0xA0000100 cmdline add=0x8D05E538
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 0
INFOTAG:hwid 0x1
INFOTAG:skuid 0x1FC04
INFOTAG:hero panel = 0x0
INFOTAG:engineerid = 0x0
INFOMCP dual-die
INFOMCP dual-die
INFOTAG:mono-die = 0x0
INFODevice CID is not super CID
INFOCID is HTC__247
INFOsetting.cid::HTC__247
INFOserial number: HT9BRLG00XXX
INFOcommandline from head: no_console_suspend=1 console=null
INFOcommand line length =413
INFOactive commandline: board_bahamas.disable_uart3=0 board_baha
INFOmas.usb_h2w_sw=0 board_bahamas.disable_sdcard=0 diag.enabled
INFO=0 board_bahamas.debug_uart=0 smisize=0 androidboot.baseban
INFOd=3.35.07.20 androidboot.cid=HTC__247 androidboot.carrier=HT
INFOC-FRA-Bouygues androidboot.mid=CLIC10000 androidboot.keycaps
INFO=qwerty androidboot.mode=normal androidboot.serialno=HT9BRLG
INFO00145 androidboot.bootloader=0.52.0001 no_console_suspend=1
INFOconsole=null
INFOaARM_Partion[0].name=misc
INFOaARM_Partion[1].name=recovery
INFOaARM_Partion[2].name=boot
INFOaARM_Partion[3].name=system
INFOaARM_Partion[4].name=cache
INFOaARM_Partion[5].name=userdata
INFOpartition number=6
INFOValid partition num=6
INFO0
INFO0
INFOXXXXXXX
INFOXXXXXXX
INFOXXXXXXX
INFOXXXX
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
FAILED (status read failed (Too many links))
finished. total time: 0.657s
C:\fastboot>
Click to expand...
Click to collapse
(I intentionnaly blanked by 'XX'ing some numbers thinking they are not relevant to the analysis)
The "FAILED (remote: 42 custom id check fail)" message when flashing shows clearly that the Goldcard I did following "[HOWTO] Create a GoldCard - Bypassing the RUU/SPL CID check to Root/Downgrade" topic is not recognized by HBOOT. Why ?
I tried as well not reversing the CID (as seen on another site) and doing the online generation again. Same problem : CID check FAILS miserably.
Questions that arise are :
1- what is the difference between the CID "HTC__247" seen in the boot log and the big alpha-numeric chain I got doing an "adb shell cat $path-to-mmc-cid" ?
2- does the CID change by mounting the sdcard on another android device ?
I'm pretty conscious we're derivating from the initial topic of this thread... but thanks for the help anyway.
Okay, I got it solved. Feeling much much better.
The CID reversing was clumsy so my goldcard was not correct. I wiped the card : did a mkfs.vfat -F 32 -S 4096 /dev/sdb1.
Tried that site for CID manipulation http://hexrev.soaa.me/, generated the goldcard.img again via http://psas.revskills.de/?q=goldcard.
dd if=golcard.img of=/dev/sdb.
Guess what, now CID check passes successfuly.
Just for the record here is a successful fastboot flashing log
(yes now I switch to a windows 7 for the fastboot step, it's of course not mandatory, I could have done everything from a linux...)
c:\fastboot>fastboot flash zip rom.zip
sending 'zip' (88968 KB)... OKAY [ 14.695s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
INFOstart image[hboot] unzipping for pre-update check...
INFOstart image[boot] unzipping & flushing...
INFO[RUU]UZ,boot,0
INFO[RUU]UZ,boot,51
INFO[RUU]UZ,boot,100
INFO[RUU]WP,boot,0
INFO[RUU]WP,boot,50
INFO[RUU]WP,boot,100
INFOstart image[hboot] unzipping & flushing...
INFO[RUU]UZ,hboot,0
INFO[RUU]UZ,hboot,100
INFO[RUU]WP,hboot,0
INFO[RUU]WP,hboot,100
INFOstart image[radio] unzipping & flushing...
INFO[RUU]UZ,radio,0
INFO[RUU]UZ,radio,6
INFO[RUU]UZ,radio,14
INFO[RUU]UZ,radio,19
INFO[RUU]UZ,radio,24
INFO[RUU]UZ,radio,33
INFO[RUU]UZ,radio,38
INFO[RUU]UZ,radio,43
INFO[RUU]UZ,radio,48
INFO[RUU]UZ,radio,53
INFO[RUU]UZ,radio,62
INFO[RUU]UZ,radio,67
INFO[RUU]UZ,radio,76
INFO[RUU]UZ,radio,81
INFO[RUU]UZ,radio,86
INFO[RUU]UZ,radio,91
INFO[RUU]UZ,radio,96
INFO[RUU]UZ,radio,100
INFO[RUU]WP,radio,0
INFO[RUU]WP,radio,7
INFO[RUU]WP,radio,12
INFO[RUU]WP,radio,17
INFO[RUU]WP,radio,26
INFO[RUU]WP,radio,31
INFO[RUU]WP,radio,36
INFO[RUU]WP,radio,41
INFO[RUU]WP,radio,46
INFO[RUU]WP,radio,51
INFO[RUU]WP,radio,58
INFO[RUU]WP,radio,63
INFO[RUU]WP,radio,68
INFO[RUU]WP,radio,100
INFOstart image[recovery] unzipping & flushing...
INFO[RUU]UZ,recovery,0
INFO[RUU]UZ,recovery,45
INFO[RUU]UZ,recovery,87
INFO[RUU]UZ,recovery,100
INFO[RUU]WP,recovery,0
INFO[RUU]WP,recovery,44
INFO[RUU]WP,recovery,89
INFO[RUU]WP,recovery,100
INFOstart image[sp1] unzipping & flushing...
INFO[RUU]UZ,sp1,0
INFO[RUU]UZ,sp1,100
INFO[RUU]WP,sp1,0
INFO[RUU]WP,sp1,100
INFOstart image[system] unzipping & flushing...
INFO[RUU]UZ,system,0
INFO[RUU]UZ,system,2
INFO[RUU]UZ,system,5
INFO[RUU]UZ,system,8
INFO[RUU]UZ,system,11
INFO[RUU]UZ,system,14
INFO[RUU]UZ,system,16
INFO[RUU]UZ,system,19
INFO[RUU]UZ,system,22
INFO[RUU]UZ,system,25
INFO[RUU]UZ,system,28
INFO[RUU]UZ,system,31
INFO[RUU]UZ,system,34
INFO[RUU]UZ,system,36
INFO[RUU]UZ,system,39
INFO[RUU]UZ,system,42
INFO[RUU]UZ,system,45
INFO[RUU]UZ,system,48
INFO[RUU]UZ,system,51
INFO[RUU]WP,system,0
INFO[RUU]WP,system,2
INFO[RUU]WP,system,5
INFO[RUU]WP,system,8
INFO[RUU]WP,system,11
INFO[RUU]WP,system,14
INFO[RUU]WP,system,16
INFO[RUU]WP,system,19
INFO[RUU]WP,system,22
INFO[RUU]WP,system,25
INFO[RUU]WP,system,28
INFO[RUU]WP,system,31
INFO[RUU]WP,system,34
INFO[RUU]WP,system,36
INFO[RUU]WP,system,39
INFO[RUU]WP,system,42
INFO[RUU]WP,system,45
INFO[RUU]WP,system,48
INFO[RUU]WP,system,51
INFO[RUU]UZ,system,51
INFO[RUU]UZ,system,53
INFO[RUU]UZ,system,56
INFO[RUU]UZ,system,59
INFO[RUU]UZ,system,62
INFO[RUU]UZ,system,65
INFO[RUU]UZ,system,68
INFO[RUU]UZ,system,71
INFO[RUU]UZ,system,74
INFO[RUU]UZ,system,76
INFO[RUU]UZ,system,79
INFO[RUU]UZ,system,82
INFO[RUU]UZ,system,85
INFO[RUU]UZ,system,88
INFO[RUU]UZ,system,91
INFO[RUU]UZ,system,94
INFO[RUU]UZ,system,97
INFO[RUU]UZ,system,100
INFO[RUU]WP,system,51
INFO[RUU]WP,system,53
INFO[RUU]WP,system,56
INFO[RUU]WP,system,59
INFO[RUU]WP,system,62
INFO[RUU]WP,system,65
INFO[RUU]WP,system,68
INFO[RUU]WP,system,71
INFO[RUU]WP,system,74
INFO[RUU]WP,system,76
INFO[RUU]WP,system,79
INFO[RUU]WP,system,82
INFO[RUU]WP,system,85
INFO[RUU]WP,system,88
INFO[RUU]WP,system,91
INFO[RUU]WP,system,94
INFO[RUU]WP,system,97
INFO[RUU]WP,system,100
INFOstart image[userdata] unzipping & flushing...
INFO[RUU]UZ,userdata,0
INFO[RUU]UZ,userdata,100
INFO[RUU]WP,userdata,0
INFO[RUU]WP,userdata,100
OKAY [132.319s]
finished. total time: 147.015s
c:\fastboot>fastboot reboot
rebooting...
finished. total time: 0.031s
Click to expand...
Click to collapse
Here we go for the NAND restore (I of course did a NAND backup before all the fudging)
Celebration time
Thanks for the support.
Related
Revert back to STock with Gold card-Fast Boot-locked S-On devices-Security warning..
Well, I’m a starter.. But I have to share this with you all..!! I have gone through various posts to revert back to Stock rom. In this I’m summing it all Up.. I Hope this will help someone. Before Reverting Rom make sure Your mainver >= your current mainver. Before You revert Rom Read This : http://forum.xda-developers.com/showpost.php?p=16684717&postcount=38 Read this to revert back : http://forum.xda-developers.com/showthread.php?t=1287111 If a error Comes Like this after S-On your device C:\Android>fastboot erase cache erasing 'cache'... OKAY [ 0.144s] finished. total time: 0.144s C:\Android>fastboot oem rebootRUU ... OKAY [ 0.188s] finished. total time: 0.188s C:\Android>fastboot flash zip rom.zip sending 'zip' (257756 KB)... OKAY [ 43.671s] writing 'zip'... INFOadopting the signature contained in this i mage... INFOsignature checking... INFOzip header checking... INFOzip info parsing... INFOchecking model ID... INFOchecking custom ID... FAILED (remote: 42 custom id check fail) finished. total time: 84.377s Click to expand... Click to collapse And Your Phone will be displaying this Message *****LOCKED******* ****Security warning **** Hboot-2.00.000 Radio - 3822.10.08.28_M Click to expand... Click to collapse You’re Screwed dewd..!! Here are the steps to Unlock.. Step 1 : Read this http://forum.xda-developers.com/showpost.php?p=16684717&postcount=38 and do exactly what he says..(Every single Word ) It may help.. if the phone again showing “CID Failed “ or remote 42: Custom id failed” message. Don’t worry.. What I did is creating a Gold Card and Reverted..!! Here are the steps of creating gold card with another HTC phone when you’re in fastboot and Romless.. Step 1: Find another htc phone like Sensation , evo3d or similar phones. Step 2 :Read thishttps://sites.google.com/site/roothtchero/goldcard-2 Step 3: Make a Gold card with the use of other phone based on steps in the above Link.. Step 5: Unmount the sd card from the other phone. Step 4 : Copy the RUU(PG32IMG.zip) in the memory card , put it back into phone and Update it..!! Done.. I’m also Adding Goldcard tool along with this Post.. Thanks to Nonverbose, santhoshpirate, John Anderton, klutsh's Goldcard Tool and XDA developers..
This goldcard tool actually worked for you? Our devices are using MMC2 and this isn't an option on the tool.
It worked like charm..!!
[Q] [Help] Is my phone bricked?
Hi, I tried to S-ON my HTC Incredible S. I've not changed the rom, I just rooted it 3months ago and installed clockworkmod by following a tutorial I found on the web which used revolutionary etc.
Got my handset in Singapore I just got an update available message, but it will not install due to the S-OFF. So I started to follow the procedure above hoping to unroot and S-ON.
I guess I selected the wrong Stock RUU and now I'm stuck with SECURITY WARNING BOOTLOADER with S-ON. However, I'm still able to run my phone, just that it can't detect SDcard and SIM card when I'm using it. (The phone is able to detect my SDcard when it is in the bootloader)
Tried following http://forum.xda-developers.com/showpost.php?p=16684717&postcount=38 to solve my problem, but I doesn't know which is the correct RUU to get, so i downloaded several RUUs, get the rom.zip and tried flashing them via fastboot.
All the RUUs I downloaded gave me this error.
Code:
C:\Android>fastboot erase cache
erasing 'cache'... OKAY [ 0.220s]
finished. total time: 0.221s
C:\Android>fastboot oem rebootRUU
... OKAY [ 0.155s]
finished. total time: 0.156s
C:\Android>fastboot flash zip PG32IMG.zip
sending 'zip' (263083 KB)... OKAY [ 45.473s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 94.601s
This is my phone's "fastboot getvar all"
Code:
C:\Android>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.13.0000
INFOversion-baseband: 3805.04.03.27_M
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 2.12.708.4
INFOserialno: *removed
INFOimei: *removed
INFOproduct: vivo
INFOplatform: HBOOT-7630
INFOmodelid: PG3213000
INFOcidnum: HTC__044
INFObattery-status: good
INFObattery-voltage: 4178mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-8a731c6e
INFOhbootpreupdate: 12
INFOgencheckpt: 0
all: Done!
finished. total time: 0.019s
RUU that gave me security warning:
RUU_Vivo_Gingerbread_S_HTC_WWE_2.12.405.7_Radio_20.2804.30.085AU_3805.04.03.22_M_release_187295_signed
RUUs I tried after getting security warning:
RUU_Vivo_Gingerbread_S_hTC_Asia_HK_2.12.708.4_Radio_20.2805.30.085AU_3805.04.03.27_M_release_189979_signed
RUU_Vivo_Gingerbread_S_HTC_WWE_2-1.30.405.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199308_signed
RUU_VIVO_SENSE30_S_hTC_Asia_HK_3.09.708.2_Radio_20.4802.30.0822U_3822.10.08.28_M_release_227715_signed
Not sure if this will help, but this is what revolutionary.exe shows when I run it:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
GZY said: Hi, I tried to S-ON my HTC Incredible S. I've not changed the rom, I just rooted it 3months ago and installed clockworkmod by following a tutorial I found on the web which used revolutionary etc. Got my handset in Singapore I just got an update available message, but it will not install due to the S-OFF. So I started to follow the procedure above hoping to unroot and S-ON. I guess I selected the wrong Stock RUU and now I'm stuck with SECURITY WARNING BOOTLOADER with S-ON. However, I'm still able to run my phone, just that it can't detect SDcard and SIM card when I'm using it. (The phone is able to detect my SDcard when it is in the bootloader) Tried following http://forum.xda-developers.com/showpost.php?p=16684717&postcount=38 to solve my problem, but I doesn't know which is the correct RUU to get, so i downloaded several RUUs, get the rom.zip and tried flashing them via fastboot. All the RUUs I downloaded gave me this error. Code: C:\Android>fastboot erase cache erasing 'cache'... OKAY [ 0.220s] finished. total time: 0.221s C:\Android>fastboot oem rebootRUU ... OKAY [ 0.155s] finished. total time: 0.156s C:\Android>fastboot flash zip PG32IMG.zip sending 'zip' (263083 KB)... OKAY [ 45.473s] writing 'zip'... INFOadopting the signature contained in this i mage... INFOsignature checking... INFOzip header checking... INFOzip info parsing... INFOchecking model ID... INFOchecking custom ID... FAILED (remote: 42 custom id check fail) finished. total time: 94.601s This is my phone's "fastboot getvar all" Code: C:\Android>fastboot getvar all INFOversion: 0.5 INFOversion-bootloader: 1.13.0000 INFOversion-baseband: 3805.04.03.27_M INFOversion-cpld: None INFOversion-microp: None INFOversion-main: 2.12.708.4 INFOserialno: *removed INFOimei: *removed INFOproduct: vivo INFOplatform: HBOOT-7630 INFOmodelid: PG3213000 INFOcidnum: HTC__044 INFObattery-status: good INFObattery-voltage: 4178mV INFOpartition-layout: Generic INFOsecurity: on INFObuild-mode: SHIP INFOboot-mode: FASTBOOT INFOcommitno-bootloader: dirty-8a731c6e INFOhbootpreupdate: 12 INFOgencheckpt: 0 all: Done! finished. total time: 0.019s RUU that gave me security warning: RUU_Vivo_Gingerbread_S_HTC_WWE_2.12.405.7_Radio_20.2804.30.085AU_3805.04.03.22_M_release_187295_signed RUUs I tried after getting security warning: RUU_Vivo_Gingerbread_S_hTC_Asia_HK_2.12.708.4_Radio_20.2805.30.085AU_3805.04.03.27_M_release_189979_signed RUU_Vivo_Gingerbread_S_HTC_WWE_2-1.30.405.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199308_signed RUU_VIVO_SENSE30_S_hTC_Asia_HK_3.09.708.2_Radio_20.4802.30.0822U_3822.10.08.28_M_release_227715_signed Click to expand... Click to collapse RUU_Vivo_Gingerbread_S_hTC_Asia_HK_2.12.708.4_Radio_20.2805.30.085AU_3805.04.03.27_M_release_189979_signed Reboot your PC and retry the RUU I have highlighted above. That is the version that matches your current settings and should work just fine.
tpbklake said: RUU_Vivo_Gingerbread_S_hTC_Asia_HK_2.12.708.4_Radio_20.2805.30.085AU_3805.04.03.27_M_release_189979_signed Reboot your PC and retry the RUU I have highlighted above. That is the version that matches your current settings and should work just fine. Click to expand... Click to collapse Hi, I rebooted my PC and retried the RUU you highlighted. But I'm still getting the same error message. Code: Microsoft Windows [Version 6.1.7600] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\zy>cd C:\Android C:\Android>fastboot erase cache erasing 'cache'... OKAY [ 0.140s] finished. total time: 0.140s C:\Android>fastboot oem rebootRUU ... OKAY [ 0.188s] finished. total time: 0.188s C:\Android>fastboot flash zip PG32IMG.zip sending 'zip' (263083 KB)... OKAY [ 44.970s] writing 'zip'... INFOadopting the signature contained in this i mage... INFOsignature checking... INFOzip header checking... INFOzip info parsing... INFOchecking model ID... INFOchecking custom ID... FAILED (remote: 42 custom id check fail) finished. total time: 94.087s C:\Android>
You need an Asia wwe ruu for that Cid. Gimme a few mins I'll try find a link. Had to get sense 3 ruu because your main version is higher than the Asia pacific 2.1. Its a Chinese web page, just click the white button next to the red vip button to download it http://115.com/file/c24bggir Edit: found thread in dev forum with another link http://forum.xda-developers.com/showthread.php?t=1421805
Nonverbose said: You need an Asia wwe ruu for that Cid. Gimme a few mins I'll try find a link. Had to get sense 3 ruu because your main version is higher than the Asia pacific 2.1. Its a Chinese web page, just click the white button next to the red vip button to download it htt p://115.c om/ fil e/c24 bggir Click to expand... Click to collapse Thanks so much!!! Will post the result soon.
GZY said: Thanks so much!!! Will post the result soon. Click to expand... Click to collapse Maybe not soon, from experience that download site is quite slow. You might have to add a .exe on the end of the filename if there's not one already, I couldn't see on my tab. If it works out for you, could you please upload to dropbox or something? Others might need it in the future.
Nonverbose said: Maybe not soon, from experience that download site is quite slow. You might have to add a .exe on the end of the filename if there's not one already, I couldn't see on my tab. If it works out for you, could you please upload to dropbox or something? Others might need it in the future. Click to expand... Click to collapse Code: Microsoft Windows [Version 6.1.7600] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\zy>cd C:\Android C:\Android>fastboot erase cache erasing 'cache'... OKAY [ 0.175s] finished. total time: 0.175s C:\Android>fastboot oem rebootRUU ... OKAY [ 0.174s] finished. total time: 0.174s C:\Android>fastboot flash zip PG32IMG.zip sending 'zip' (342985 KB)... OKAY [ 57.578s] writing 'zip'... INFOadopting the signature contained in this i mage... INFOsignature checking... INFOzip header checking... INFOzip info parsing... INFOchecking model ID... INFOchecking custom ID... INFOchecking main version... INFOstart image[hboot] unzipping for pre-update check... INFOstart image[hboot] flushing... INFO[RUU]WP,hboot,0 INFO[RUU]WP,hboot,100 INFOstart image[radio] unzipping for pre-update... INFOstart image[radio] flushing... INFO[RUU]WP,radio,0 INFO[RUU]WP,radio,6 INFO[RUU]WP,radio,14 INFO[RUU]WP,radio,22 INFO[RUU]WP,radio,30 INFO[RUU]WP,radio,38 INFO[RUU]WP,radio,48 INFO[RUU]WP,radio,53 INFO[RUU]WP,radio,61 INFO[RUU]WP,radio,69 INFO[RUU]WP,radio,77 INFO[RUU]WP,radio,85 INFO[RUU]WP,radio,91 INFO[RUU]WP,radio,100 FAILED (remote: 90 hboot pre-update! please flush image again immediately) finished. total time: 225.335s C:\Android>fastboot flash zip PG32IMG.zip sending 'zip' (342985 KB)... OKAY [ 57.041s] writing 'zip'... INFOadopting the signature contained in this i mage... INFOsignature checking... INFOzip header checking... INFOzip info parsing... INFOchecking model ID... INFOchecking custom ID... INFOchecking main version... INFOstart image[boot] unzipping & flushing... INFO[RUU]UZ,boot,0 INFO[RUU]UZ,boot,32 INFO[RUU]UZ,boot,72 INFO[RUU]UZ,boot,100 INFO[RUU]WP,boot,0 INFO[RUU]WP,boot,99 INFO[RUU]WP,boot,100 INFOstart image[recovery] unzipping & flushing... INFO[RUU]UZ,recovery,0 INFO[RUU]UZ,recovery,21 INFO[RUU]UZ,recovery,42 INFO[RUU]UZ,recovery,63 INFO[RUU]UZ,recovery,83 INFO[RUU]UZ,recovery,100 INFO[RUU]WP,recovery,0 INFO[RUU]WP,recovery,99 INFO[RUU]WP,recovery,100 INFOstart image[system] unzipping & flushing... INFO[RUU]UZ,system,0 INFO[RUU]UZ,system,2 INFO[RUU]UZ,system,5 INFO[RUU]UZ,system,8 INFO[RUU]UZ,system,11 INFO[RUU]UZ,system,14 INFO[RUU]UZ,system,17 INFO[RUU]UZ,system,19 INFO[RUU]UZ,system,22 INFO[RUU]UZ,system,25 INFO[RUU]UZ,system,28 INFO[RUU]UZ,system,31 INFO[RUU]UZ,system,34 INFO[RUU]UZ,system,37 INFO[RUU]UZ,system,42 INFO[RUU]UZ,system,45 INFO[RUU]UZ,system,48 INFO[RUU]UZ,system,51 INFO[RUU]UZ,system,54 INFO[RUU]UZ,system,57 INFO[RUU]WP,system,0 INFO[RUU]WP,system,2 INFO[RUU]WP,system,5 INFO[RUU]WP,system,8 INFO[RUU]WP,system,11 INFO[RUU]WP,system,14 INFO[RUU]WP,system,17 INFO[RUU]WP,system,19 INFO[RUU]WP,system,22 INFO[RUU]WP,system,25 INFO[RUU]WP,system,28 INFO[RUU]WP,system,31 INFO[RUU]WP,system,34 INFO[RUU]WP,system,37 INFO[RUU]WP,system,39 INFO[RUU]WP,system,42 INFO[RUU]WP,system,45 INFO[RUU]WP,system,48 INFO[RUU]WP,system,51 INFO[RUU]WP,system,54 INFO[RUU]WP,system,57 INFO[RUU]UZ,system,57 INFO[RUU]UZ,system,59 INFO[RUU]UZ,system,61 INFO[RUU]UZ,system,63 INFO[RUU]UZ,system,66 INFO[RUU]UZ,system,68 INFO[RUU]UZ,system,71 INFO[RUU]UZ,system,74 INFO[RUU]UZ,system,77 INFO[RUU]UZ,system,79 INFO[RUU]UZ,system,81 INFO[RUU]UZ,system,84 INFO[RUU]UZ,system,87 INFO[RUU]UZ,system,90 INFO[RUU]UZ,system,93 INFO[RUU]UZ,system,95 INFO[RUU]UZ,system,98 INFO[RUU]WP,system,57 INFO[RUU]WP,system,59 INFO[RUU]WP,system,62 INFO[RUU]WP,system,65 INFO[RUU]WP,system,68 INFO[RUU]WP,system,71 INFO[RUU]WP,system,74 INFO[RUU]WP,system,77 INFO[RUU]WP,system,79 INFO[RUU]WP,system,82 INFO[RUU]WP,system,85 INFO[RUU]WP,system,88 INFO[RUU]WP,system,91 INFO[RUU]WP,system,94 INFO[RUU]WP,system,97 INFO[RUU]WP,system,100 INFOstart image[lib] unzipping & flushing... INFO[RUU]UZ,lib,0 INFO[RUU]UZ,lib,8 INFO[RUU]UZ,lib,15 INFO[RUU]UZ,lib,23 INFO[RUU]UZ,lib,31 INFO[RUU]UZ,lib,39 INFO[RUU]UZ,lib,47 INFO[RUU]UZ,lib,52 INFO[RUU]UZ,lib,57 INFO[RUU]UZ,lib,63 INFO[RUU]UZ,lib,68 INFO[RUU]UZ,lib,73 INFO[RUU]UZ,lib,78 INFO[RUU]UZ,lib,85 INFO[RUU]UZ,lib,94 INFO[RUU]UZ,lib,100 INFO[RUU]WP,lib,0 INFO[RUU]WP,lib,10 INFO[RUU]WP,lib,21 INFO[RUU]WP,lib,31 INFO[RUU]WP,lib,42 INFO[RUU]WP,lib,52 INFO[RUU]WP,lib,63 INFO[RUU]WP,lib,73 INFO[RUU]WP,lib,84 INFO[RUU]WP,lib,94 INFO[RUU]WP,lib,100 INFOstart image[sp1] unzipping & flushing... INFO[RUU]UZ,sp1,0 INFO[RUU]UZ,sp1,100 INFO[RUU]WP,sp1,0 INFO[RUU]WP,sp1,100 INFOstart image[dzdata] unzipping & flushing... INFO[RUU]UZ,dzdata,0 INFO[RUU]UZ,dzdata,100 INFO[RUU]WP,dzdata,0 INFO[RUU]WP,dzdata,100 INFOstart image[rcdata] unzipping & flushing... INFO[RUU]UZ,rcdata,0 INFO[RUU]WP,rcdata,0 INFO[RUU]WP,rcdata,100 OKAY [160.421s] finished. total time: 217.463s C:\Android>fastboot oem rebootRUU ... OKAY [ 0.158s] finished. total time: 0.160s C:\Android>fastboot reboot-bootloader rebooting into bootloader... OKAY [ 0.154s] finished. total time: 0.154s C:\Android> Hey it works! Thanks so much. First time using dropbox, not sure if I'm doing it right. Will finish uploading within the next 1-2 days. http://dl.dropbox.com/u/50679842/RU...22U_3822.10.08.28_M_release_226940_signed.exe EDIT: uploaded!
Problem with flashing firmware 2.24.401.1
Hi all! I'm sticking with the update of my firmware using the super vomer's guide here: http://forum.xda-developers.com/showpost.php?p=42556698&postcount=24958&nocache=1&z=7697684632189703 i've got this : MacBook-Pro-de-jules:Android julesbecker$ fastboot flash zip /Users/julesbecker/Desktop/fw_2.24.401.1_custom.zip sending 'zip' (26802 KB)... OKAY [ 2.276s] writing 'zip'... (bootloader) zip header checking... (bootloader) zip info parsing... (bootloader) checking model ID... (bootloader) checking custom ID... (bootloader) start image[hboot] unzipping for pre-update check... (bootloader) start image[hboot] flushing... (bootloader) [RUU]WP,hboot,0 (bootloader) [RUU]WP,hboot,99 (bootloader) [RUU]WP,hboot,100 (bootloader) ...... Successful FAILED (remote: 90 hboot pre-update! please flush image again immediately) finished. total time: 3.844s MacBook-Pro-de-jules:Android julesbecker$ fastboot flash zip /Users/julesbecker/Desktop/fw_2.24.401.1_custom.zip < waiting for device > sending 'zip' (26802 KB)... ERROR: usb_write failed with status e00002ed FAILED (data transfer failure (Operation timed out)) finished. total time: 2.239s MacBook-Pro-de-jules:Android julesbecker$ fastboot flash zip /Users/julesbecker/Desktop/fw_2.24.401.1_custom.zip ERROR: could not get pipe properties ERROR: could not get pipe properties sending 'zip' (26802 KB)... ERROR: bulkOut endpoint not assigned FAILED (command write failed (No such file or directory)) finished. total time: 0.000s MacBook-Pro-de-jules:Android julesbecker$ fastboot flash zip /Users/julesbecker/Desktop/fw_2.24.401.1_custom.zip ERROR: could not get pipe properties ERROR: could not get pipe properties sending 'zip' (26802 KB)... ERROR: bulkOut endpoint not assigned FAILED (command write failed (No such file or directory)) finished. total time: 0.000s I can't flash the zip with fastboot.... What's wrong? Can i restart my phone or will he remain bricked? Thank you so much in advance if someone can help me!
I fixed the problem this thread can be closed. just reconnect the USB cable....
TWRP Won't Boot After Firmware Update
I pushed the latest recovery found here: http://forum.xda-developers.com/show...light=firmware which went fine. Afterwards I went to reboot to recovery and flash the updated radio and the "Entering Recovery" message displays but never loads TWRP. The phone then reboots and loads the ROM. Note: I did receive an initial error message and then re-ran the firmware flash. Various things stated they were bypassed: Initial push: sending 'zip' (39722 KB)... OKAY [ 4.738s] writing 'zip'... INFOzip header checking... INFOshift signature_size for header checking... INFOzip info parsing... INFOchecking model ID... INFOchecking custom ID... INFOstart image[hboot] unzipping for pre-update check... INFOstart image[hboot] flushing... INFO[RUU]WP,hboot,0 INFO[RUU]WP,hboot,99 INFO[RUU]WP,hboot,100 INFO...... Successful FAILED (remote: 90 hboot pre-update! please flush image again immediately) finished. total time: 6.405s Subsequent pushes: INFOstart image[sbl1-1] unzipping & flushing... INFO[RUU]UZ,sbl1-1,0 INFO[RUU]UZ,sbl1-1,100 INFOsignature checking... INFOverified fail INFO..... Bypassed INFOstart image[sbl1-2] unzipping & flushing... INFO[RUU]UZ,sbl1-2,0 INFO[RUU]UZ,sbl1-2,100 INFOsignature checking... INFOverified fail INFO..... Bypassed Once the flash finishes, the device sits there with the black screen and HTC logo with the green progress bar about 95% of the way across and refuses to move. It requires a fastboot reboot-bootloader command. I've tried the fastboot erase cache, fastboot flash recovery RECOVERYFILE, fastboot erase cache method to no avail. I've even tried different versions of TWRP. Any ideas? EDIT: PEBKAC. Made the mistake of grabbing the recovery for the M7 and not the M7wls for Sprint. Sigh. Issue resolved. EDIT: It now looks like the cache partition isn't mounting correctly. How do I go about getting it partitioned correctly? -- Killed it all in TWRP with fixing permissions, wiping cache/dalvik a few times.
Flash the stock recovery, do a factory reset and reflash TWRP
[PLACEHOLDER: HTC ONE M8] Newest Firmware WITH Modified HBOOT, (No Red warning)
Hi Everyone, OP UPDATELACEHOLDER ONLY...!! This firmware is WITH OUT the development disclaimer overlay: This build is for development purposes only Do not distribute outside of HTC without HTC's written permission. Failure to comply may lead to legal action. ** With Latest Radio ** Upgrade your HTC Sync to 2.4.36.0 if you flash this firmware.. FirmwareXXXXX, NO Red Warning, --md5: -- 8f3a59cdbcc84b9ff2319495eee6ae98 These Firmwares DO NOT delete the contents in SD Card. But please make a back up before flashing for safety. **N.B. Thanks and Donations are most welcome ** Requirements for flashing: S-OFF Please Follow the instructions carefully!! Otherwise you may BRICK your device. Please note that it is for the HTC One M7 UL Only. Not Tested with Sprint Version!! You may change the MID (at your own risk) in the android-info.txt attached and replace the one inside the firmware.zip if you have another MID. If you have Super CID "11111111", you don't need to worry about the CID lists inside the android-info.txt file DON'T FORGET TO CLICK THANKS IF YOU FIND THIS THREAD USEFUL. Dear All, I have noted a lot downloads of the firmware and most of them just don't even bother clicking thanks :silly: I appreciate your encouragements and appreciation for my work so that it will give motivation to keep all you updated. Thanks a lot for everyone contributed.. To Check ModelIDs: Code: adb reboot bootloader ----- Mobile reboots--- Code: fastboot getvar all ----Check the following line in the command window: INFOmodelid: PN0714000---- Steps for flashing: ----- Windows users, need to do these steps first: - move the file you downloaded and renamed (firmware.zip) to the C:\adb\ folder. - next, in the C:\adb\ folder hold down SHIFT key and RIGHT-CLICK and select "Open command window here". ----- Next, plug in phone to PC and type this in terminal/command prompt: Code: adb reboot bootloader ----- Mobile reboots--- Now type: Code: fastboot reboot-bootloader After that, type: Code: fastboot oem rebootRUU Note: You should see a silver HTC logo come up on your phone after executing this command. Note: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again. Finally: Code: fastboot flash zip C:\adb\firmware.zip Got this: Code: sending 'zip' (24557 KB)... OKAY [ 3.053s] writing 'zip'... INFOzip header checking... INFOzip info parsing... INFOchecking model ID... INFOchecking custom ID... INFOstart image[hboot] unzipping for pre-update check... INFOstart image[hboot] flushing... INFO[RUU]WP,hboot,0 INFO[RUU]WP,hboot,99 INFO[RUU]WP,hboot,100 INFO...... Successful FAILED (remote: 90 hboot pre-update! please flush image again immediately) finished. total time: 4.681s Repeat the same command: !! IMPORTANT !! -- PLEASE WAIT A FEW SECONDS BEFORE ISSUING THE COMMAND AGAIN; Otherwise the cmd prompt will be non-responsive saying "Sending data...", If this happens, try disconnecting the USB cable and reconnect. Code: fastboot flash zip C:\adb\firmware.zip You will see this: Code: sending 'zip' (24840 KB)... OKAY [ 3.233s] writing 'zip'... INFOzip header checking... INFOzip info parsing... INFOchecking model ID... INFOchecking custom ID... INFOstart image[rpm] unzipping & flushing... INFO[RUU]UZ,rpm,0 INFO[RUU]UZ,rpm,100 INFO[RUU]WP,rpm,0 INFO[RUU]WP,rpm,100 INFO...... Successful INFOstart image[sbl1-1] unzipping & flushing... INFO[RUU]UZ,sbl1-1,0 INFO[RUU]UZ,sbl1-1,100 INFOsignature checking... INFOverified fail INFO..... Bypassed INFOstart image[sbl1-2] unzipping & flushing... INFO[RUU]UZ,sbl1-2,0 INFO[RUU]UZ,sbl1-2,100 INFOsignature checking... INFOverified fail INFO..... Bypassed INFOstart image[sbl1-3] unzipping & flushing... INFO[RUU]UZ,sbl1-3,0 INFO[RUU]UZ,sbl1-3,100 INFOsignature checking... INFO[RUU]WP,sbl1-3,0 INFO[RUU]WP,sbl1-3,100 INFO...... Successful INFOstart image[sbl2] unzipping & flushing... INFO[RUU]UZ,sbl2,0 INFO[RUU]UZ,sbl2,100 INFO[RUU]WP,sbl2,0 INFO[RUU]WP,sbl2,100 INFO...... Successful INFOstart image[sbl3] unzipping & flushing... INFO[RUU]UZ,sbl3,0 INFO[RUU]UZ,sbl3,100 INFO[RUU]WP,sbl3,0 INFO[RUU]WP,sbl3,100 INFO...... Successful INFOstart image[tp] unzipping & flushing... INFO[RUU]UZ,tp,0 INFO[RUU]UZ,tp,100 INFO..... Bypassed INFOstart image[tz] unzipping & flushing... INFO[RUU]UZ,tz,0 INFO[RUU]UZ,tz,100 INFO[RUU]WP,tz,0 INFO[RUU]WP,tz,100 INFO...... Successful INFOstart image[radio] unzipping & flushing... INFO[RUU]UZ,radio,0 INFO[RUU]UZ,radio,6 INFO[RUU]UZ,radio,12 INFO[RUU]UZ,radio,18 INFO[RUU]UZ,radio,24 INFO[RUU]UZ,radio,30 INFO[RUU]UZ,radio,37 INFO[RUU]UZ,radio,43 INFO[RUU]UZ,radio,49 INFO[RUU]UZ,radio,55 INFO[RUU]UZ,radio,62 INFO[RUU]UZ,radio,68 INFO[RUU]UZ,radio,74 INFO[RUU]UZ,radio,80 INFO[RUU]UZ,radio,86 INFO[RUU]UZ,radio,93 INFO[RUU]UZ,radio,99 INFO[RUU]UZ,radio,100 INFO[RUU]WP,radio,0 INFO[RUU]WP,radio,24 INFO[RUU]WP,radio,49 INFO[RUU]WP,radio,74 INFO[RUU]WP,radio,99 INFO[RUU]WP,radio,100 INFO...... Successful INFOstart image[rcdata] unzipping & flushing... INFO[RUU]UZ,rcdata,0 INFO[RUU]WP,rcdata,0 INFO...... Successful OKAY [ 16.837s] finished. total time: 20.072s Note:The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on. Last Step: Code: fastboot reboot Then I went back to the bootloader mode (after the phone reboots successfully): If Boot-Loop Occurs*: Code: fastboot erase cache Restart in boot-loader to check whether everything is fine*: Code: adb reboot bootloader --Phone reboots into bootloader-- Code: fastboot getvar all The resulting variable may look like this: Code: INFOversion: 0.5 INFOversion-bootloader: 1.56.0000 INFOversion-baseband: 4A.23.3263.28 INFOversion-cpld: None INFOversion-microp: None INFOversion-main: 4.19.401.9 INFOversion-misc: PVT SHIP S-OFF INFOserialno: HTXXXXXXXXXX INFOimei: INFOmeid: 00000000000000 INFOproduct: m7_ul INFOplatform: HBOOT-8064 INFOmodelid: PN0714000 INFOcidnum: XXXXXXXX INFObattery-voltage: 4129mV INFOpartition-layout: Generic INFOsecurity: off INFObuild-mode: SHIP INFOboot-mode: FASTBOOT INFOcommitno-bootloader: dirty-4dab9d12 INFOhbootpreupdate: 11 INFOgencheckpt: 0 all: Done! Q: Do I need S-OFF for firmware flashing? A: YES, It is a must. Q: Do I need to update my firmware? A: NO, but updating firmware ensures optimal phone performance. Q: Does it matter when I flash the firmware (before or after new ROM install) A: No. Q: Will updating the firmware erase my SD card or Apps? A: No, The firmware files provided here does not erase none of those. Q: If I only flash the ROM, will I get updated to the latest firmware? A: No. You must flash the firmware separate in most cases. Q: Can I install a UL edition firmware on a U edition phone? A: Yes (may be), but you won't have LTE or may experience some other incompatibilities. Possible Errors while flashing: If it says "FAILED" do not immediately reboot the device. If you reboot with a FAIL it could brick your device! Listed below error are safe to reboot: If you encounter one of them, you can just reboot. Nothing changes. - 12 signature fail (means a signed firmware package is required. This would only happen with S-ON phones though. but safe to reboot) - 23 parsing image fail (means something wrong with the image in the zip) - 32 header error (means the zip couldn’t be read and unzipped properly) - 41 Wrong Model ID (means the MODEL ID in the android-info.txt does not match with your device. you can reboot the device. You may change the MID manually in the android-info.txt at your own risk.) - 42 Wrong Customer ID (means you need to include the CID of your device in the android-info.txt or change the CID to superCID.) - 99 UNKOWN (is not yet clear but safe to reboot) DON'T reboot until you get a success message if you get an error bellow: - 90 hboot pre-update (means it only flashed hboot and you have to run the process again immediately to flash all other partitions. Don’t reboot before repeating the command. If the command window stuck in the middle for a long time, wait for a few minutes and please unplug the USB and replug it again. Repeat the command again. DON'T reboot until you get a success message.) Editing android-info.txt - Use an Editor that doesn't doesn't alter the linebreaks. Don't use Windows Notepad. Use Notepad++ - Only one MID can be in the file. - CID's can easily be added or removed- one per line To Get SUPERCID Code: fastboot oem writecid 11111111 RUUmode: RUU Mode is the mode used for RUU flashes by HTC. It is different from the normal fastboot. You must flash the firmware only in RUU Mode. The RUU mode can be identified by the black background with only a silver HTC logo and if a command is being active a green progress bar will show the progress of any command being excecuted. For Further ReadingSome more useful threads that might be helpful to you: - Mike1986’s Firmware thread - Vomer’s ultimate guide thread - hes_theone64’s radio flash guide for recovery - chrisch1974's HOW-TO Flash a custom splash screen - Sneakyghost's Firmware Flashing & Hboots red warning gone thread - HTC ONE Partition List: - Mike1986 Partition explanation: You must be aware that writing to the bootloader -partition increases your risk to lose the device exponentially. You understand and agree that i cannot be held responsible for such or any other damages. The flash process is theoretically safe and tested. I will not accept any responsibility. The method itself is developed by Google and HTC, i have only adapted it and you execute it. You understand that you should not do it if you are not willing to accept this risk. For More info, about Super CID, S-OFF and Firmware update process, check this thread: [Guide] Vomer's Ultimate AIO - S-OFF, SuperCID, Firmware Upgrade & Custom Recovery Thanks @vomer and @Sneakyghost
placeholder
'Please note that it is for the HTC One M7 UL Only.' is this a typo or true :silly:
Is this for the wrong device? or am i just being special?
its a placeholder although, really not needed, since the devs who will be responsible for s-off will likely make their own thread
Thread closed as its only a placeholder. When the OP has something to share he can ask one of the forum mods to reopen it or report the thread and ask that it is reopened.