Related
I want to flash userdata.img, system.img, recovery.img, boot.img files via ADB to my Desire in order to unroot my 2.1, then make it able to upgrade to 2.2 via OTA.
I am using rooted HK 2.1 ROM, have downloaded Asia WWE 2.1 RUU and extracted those .img files.
How can I disable the signature checking? I've got below errors when I tried to flash the img file to my Desire.
C:\r5>fastboot flash userdata userdata.img
sending 'userdata' (2 KB)... OKAY
writing 'userdata'... INFOsignature che
FAILED (remote: signature verify fail)
If you are using a custom recovery like clockwork mod or Amon ra. There is an option called "Toggle Signature".
txitxi2004 said:
If you are using a custom recovery like clockwork mod or Amon ra. There is an option called "Toggle Signature".
Click to expand...
Click to collapse
thanks, but ADB is unable to connect to the device if it is in recovery mode, can only be in fastboot mode. So that I need to disable signature checking in fastboot mode.
scott4 said:
thanks, but ADB is unable to connect to the device if it is in recovery mode, can only be in fastboot mode. So that I need to disable signature checking in fastboot mode.
Click to expand...
Click to collapse
I'm looking the answer for the same problem. I get "signature verification failed" when using fastboot flash method. Any instructions got how to disable signature check?
kekojan said:
I'm looking the answer for the same problem. I get "signature verification failed" when using fastboot flash method. Any instructions got how to disable signature check?
Click to expand...
Click to collapse
i've tried flashing the original recovery.img to Desire, still can't solve the signature check problem. I also have tried doing below:
push flash_image and mtd0.img (what should be the CID of HK 2.1 official rom?) to Desire through ADB, the execute like: flash_image misc mtd0.img
however the upgrade still couldn't pass the signature check... sigh..
kekojan said:
I'm looking the answer for the same problem. I get "signature verification failed" when using fastboot flash method. Any instructions got how to disable signature check?
Click to expand...
Click to collapse
You can't do that with the bootloader on the desire. Our version of fastboot is "S-ON" (security enabled). You need an engineering bootloader (S-OFF) to flash images using fastboot. Hopefully we will get this one day.
st0kes said:
You can't do that with the bootloader on the desire. Our version of fastboot is "S-ON" (security enabled). You need an engineering bootloader (S-OFF) to flash images using fastboot. Hopefully we will get this one day.
Click to expand...
Click to collapse
So, is there any way I can flash the images I build for Desire? (I have rebuild the froyo platform for desire)
Can I flash them via sdcard using for e.g clockwork or similar recovery method?
kekojan said:
So, is there any way I can flash the images I build for Desire? (I have rebuild the froyo platform for desire)
Can I flash them via sdcard using for e.g clockwork or similar recovery method?
Click to expand...
Click to collapse
Pack the contents of out/product/target/bravo/system into a zip fille (just the system directory) along with the boot.img, and flash it using clockwork recovery. Toggle signed files to off to allow this or sign the file using testsign.jar (you can find it on the board here somewhere).
You will have to remove the symlinks in out/product/target/bravo/system/bin and symlink them again during the flashing process using an update-script or you will have a lot of broken stuff (like dhcp), check inside an existing rom like CyanogenMod to see how the update-script is constructed and how get the syntax right.
st0kes said:
Pack the contents of out/product/target/bravo/system into a zip fille (just the system directory) along with the boot.img, and flash it using clockwork recovery. Toggle signed files to off to allow this or sign the file using testsign.jar (you can find it on the board here somewhere).
You will have to remove the symlinks in out/product/target/bravo/system/bin and symlink them again during the flashing process using an update-script or you will have a lot of broken stuff (like dhcp), check inside an existing rom like CyanogenMod to see how the update-script is constructed and how get the syntax right.
Click to expand...
Click to collapse
Currently in order to unroot Desire, is to push flash_image and mtd0.img to Desire through ADB, and then execute like: flash_image misc mtd0.img, then is able to run any RUU to unroot Desire. Since we still do not have RUU 2.1 or 2.2 for official HK rom (not test rom), we have no way to unroot our HK Desire.
I am thinking if there is any trick can mimic a RUU .exe file which is able to change back the CID or signature file to an official Hong Kong one. Then OTA can be done as it check signature during OTA upgrade. Do you think it is workable?
st0kes said:
Pack the contents of out/product/target/bravo/system into a zip fille (just the system directory) along with the boot.img, and flash it using clockwork recovery. Toggle signed files to off to allow this or sign the file using testsign.jar (you can find it on the board here somewhere).
You will have to remove the symlinks in out/product/target/bravo/system/bin and symlink them again during the flashing process using an update-script or you will have a lot of broken stuff (like dhcp), check inside an existing rom like CyanogenMod to see how the update-script is constructed and how get the syntax right.
Click to expand...
Click to collapse
I zipped system.img and boot.img and toggled off the signed files in clockwork and flashed the zipped (50Mb) package. All were installed really way too fast and without errors. After reboot nothing was updated. Next steps? Any ideas?
eh.. delete me
Update to previous post. I did zip the system directory + boot.img. Actually, in a second try I also zipped system.img to same package. And I also removed the symlinks from ../bin directory. And then flashed. I got no errors but again installing (clockwork) was really quick and after reboot nothing changed. The weird thing is that I do not get any errors no matter what I'm zipping.
What can I try next?
kekojan said:
I zipped system.img and boot.img and toggled off the signed files in clockwork and flashed the zipped (50Mb) package. All were installed really way too fast and without errors. After reboot nothing was updated. Next steps? Any ideas?
Click to expand...
Click to collapse
st0kes said:
Pack the contents of out/product/target/bravo/system into a zip fille (just the system directory) along with the boot.img, and flash it using clockwork recovery. Toggle signed files to off to allow this or sign the file using testsign.jar (you can find it on the board here somewhere).
You will have to remove the symlinks in out/product/target/bravo/system/bin and symlink them again during the flashing process using an update-script or you will have a lot of broken stuff (like dhcp), check inside an existing rom like CyanogenMod to see how the update-script is constructed and how get the syntax right.
Click to expand...
Click to collapse
Now I did as per the instructions except the update-script part.
I did zip the system directory + boot.img. Actually, in a second try I also zipped system.img to same package. And I also removed the symlinks from ../bin directory. And then flashed. I got no errors but again installing was really quick and after reboot nothing changed. The weird thing is that I do not get any errors no matter what I'm zipping.
What can I try next?
kekojan said:
Now I did as per the instructions except the update-script part.
I did zip the system directory + boot.img. Actually, in a second try I also zipped system.img to same package. And I also removed the symlinks from ../bin directory. And then flashed. I got no errors but again installing was really quick and after reboot nothing changed. The weird thing is that I do not get any errors no matter what I'm zipping.
What can I try next?
Click to expand...
Click to collapse
The corresponding part of the recovery log below.
- Installing: SDCARD:images_new.zip
I:Set boot command "boot-recovery"
Finding update package...
I:Update location: SDCARD:images_new.zip
Opening update package...
I:Update file path: /sdcard/images_new.zip
Installing update...
I:Trying update-binary.
I:Trying update-script.
Starting recovery on Fri Sep 3 13:03:42 2010
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (480 x 800)
ClockworkMod Recovery v2.5.0.1
I:Boot command: boot-recovery
I:Got arguments from boot message
I:Set boot command "boot-recovery"
Command: "recovery"
What do you think what is wrong?
st0kes said:
You can't do that with the bootloader on the desire. Our version of fastboot is "S-ON" (security enabled). You need an engineering bootloader (S-OFF) to flash images using fastboot. Hopefully we will get this one day.
Click to expand...
Click to collapse
technically, that is incorrect.
S-ON or S-OFF is a flag that's being interpreted by fastboot/hboot.
The engineering bootloader you talk about, ignores this flag and exposes developer options like flashing through the fastboot protocol directly, without a signature.
scott4 said:
Currently in order to unroot Desire, is to push flash_image and mtd0.img to Desire through ADB, and then execute like: flash_image misc mtd0.img, then is able to run any RUU to unroot Desire. Since we still do not have RUU 2.1 or 2.2 for official HK rom (not test rom), we have no way to unroot our HK Desire.
I am thinking if there is any trick can mimic a RUU .exe file which is able to change back the CID or signature file to an official Hong Kong one. Then OTA can be done as it check signature during OTA upgrade. Do you think it is workable?
Click to expand...
Click to collapse
I like the theory, but you would probably have to fool the RRU so that it thinks your img files have the same checksums as the original img files. I've never heard of anyone being able to repack and flash an RRU file.
kekojan said:
Starting recovery on Fri Sep 3 13:03:42 2010
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (480 x 800)
ClockworkMod Recovery v2.5.0.1
I:Boot command: boot-recovery
I:Got arguments from boot message
I:Set boot command "boot-recovery"
Command: "recovery"
What do you think what is wrong?
Click to expand...
Click to collapse
I think something is wrong with your update-script.
Btw, forget about your system.img, you can't use it .. you have to work with the contents of the system directory instead
ieftm said:
technically, that is incorrect.
S-ON or S-OFF is a flag that's being interpreted by fastboot/hboot.
The engineering bootloader you talk about, ignores this flag and exposes developer options like flashing through the fastboot protocol directly, without a signature.
Click to expand...
Click to collapse
Are you sure about that? I had always thought that S-OFF meant it was an engineering bootloader.
I didn't think you could get an engineering bootloader that was also S-ON.
st0kes said:
Are you sure about that? I had always thought that S-OFF meant it was an engineering bootloader.
I didn't think you could get an engineering bootloader that was also S-ON.
Click to expand...
Click to collapse
unrevoked 3.2 seems to be able to set to S-OFF!! but waiting it release
st0kes said:
Are you sure about that? I had always thought that S-OFF meant it was an engineering bootloader.
I didn't think you could get an engineering bootloader that was also S-ON.
Click to expand...
Click to collapse
Bootloaders are either ship or eng.
The latter ignores secuflag and allows extended fastboot commands.
So bootloader or s-off are two separate things.
S-off is mainly for unsigned flashing and nand writelocks.
scott4 said:
unrevoked 3.2 seems to be able to set to S-OFF!! but waiting it release
Click to expand...
Click to collapse
only on cdma desire.
For gsm desire you will need to wait for our s-off/eng hboot 0.93 release.
This is a patched hboot to ignore security, and allow extended fastboot commands.
So essentially S-OFF and eng.
scott4 said:
Currently in order to unroot Desire, is to push flash_image and mtd0.img to Desire through ADB, and then execute like: flash_image misc mtd0.img, then is able to run any RUU to unroot Desire. Since we still do not have RUU 2.1 or 2.2 for official HK rom (not test rom), we have no way to unroot our HK Desire.
I am thinking if there is any trick can mimic a RUU .exe file which is able to change back the CID or signature file to an official Hong Kong one. Then OTA can be done as it check signature during OTA upgrade. Do you think it is workable?
Click to expand...
Click to collapse
Flashing the misc partition allows you to bypass (fake, really) version checks with an RUU flash, nothing more. It doesn't affect root nor does it have anything to do with signature checking (which is currently impossible to disable on the GSM Desire).
Hi.
Seems I bricked my Desire, but before I give up and send it to repairs I’m trying to get help from this forum.
To explain what happened:
First and most important thing: “’I’m an idiot”
Second – I had working InsertCoin 1.9.5 ROM installed (rooted phone with S-OFF. )
Occasionally I’m trying other Roms and this time I wanted to try 2.3 rom. During install process I checked some additional information and I run into topic regarding AlphaRev 1.8. –there was a recommendation to upgrade HBoot. So I did. Same time I upgraded Clockworkmod from 2.5.0.7 to 3.0.0.5
When Installed “PB99IMG_bravo_stock.zip” from Alpharev site this is when my problems started. (probably it was corrupted file. I dint check MD5Sum so this is probably why I’m an idiot.
When I found out that something is wrong I tried to restore backup but seems I’t worked partially. Actually when backup was restored I couldn’t switch off the phone – exit the screen. So I had to remove battery. Then I got stuck in AlhpaRev screen and only way to continue was to remove battery again and redo restore. I got everything work but started to disconnect few seconds after call was connected and phone did not connect with windows any more (when usb connected) it doesn’t show anything on the phone.
Now When tried to make advanced restore via Fastboot, I had problems to restore Boot. So I messed around with different options to restore boot without success and in the end only solution I could think of is to restore the phone to its original state. Backed up SD card and installed PB99IMG_Bravo_Froyo_HTC_WWE_2.29.405.2_Radio_32.49.00.32U_5.11.05.27_release_151783_signed file that I found (can be installed without windows). It installed correctly and my phone switched on (unrooted), can send emails and messages but still problems with connection (drops calls) and phone not recognizing usb connection still remained.
In bootloader my phone data is this:
BRAVO PVT3 SHIP S-ON
HBOOT-0.93.0001
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27
… long story.
But now is the question how I can root and or downgrade my phone if it’s not recognized by windows? When connecting via usb if in HBOOT mode everything ok (HBOOT USB PLUG).
I think that complete reinstall would fix connection problem, but how to reinstall + root without connection to pc, this is mystery for me.
So under windows 7
.. unrevoked doesn’t recognize a phone
… ruu installer doesn’t recognize a phone
…HTC sync doesn’t recognize a phone
…Phone doesn’t recognize usb connection in normal mode.
When picking “fastboot” in bootloader, phone will go to black screen with red triangle. Nothing happens.
Is there a way to root via bootloader or fastboot or anything… ?
Appreciate any help here.
Thanks.
First of all.. Why oh why did you flash a stock s-on bootloader... It makes everything so much more complicated.
Second are you sure the black screen with the red triangle comes up when you choose fastboot and not when you choose recovery, because it is the recovery.
Third it sounds exactly like your problem is similar to those with usb-brick. This means your misc partition is corrupted, so you will need to flash a new one(this would have been a piece of cake if you hadn't flashed the ruu with stock hboot).
thanks for the quick reply,
well... at this point i have understood this is going to be complicated... Im actually not home but on a business trip without a phone connection - so if not anything else, this will be good lesson for the future to read all the instructions carefully... '
but anyway... regarding red triangle... you are right as this is recovery and I have found how to enter android system recovery menu: "volume up +power"
so as I understand from your post I need to flash new partition... any directions?
Well year i'll try to find some instructions for you, and i might be able to help you do it on pm, but it involves editing a std. misc.img file with your cid and flash it.
The tough part is the flashing, as this is not possible without root. Had you not run the "PB99IMG_Bravo_Froyo_HTC_WWE_2.29.405.2_Radio_32.49 .00.32U_5.11.05.27_release_151783_signed" it would have taken 30 seconds, but now you are unrootet, so you will need to use an exploit to gain temporary root in order to flash the misc.img from a terminal emulator. You will also need access to putting files on the sd-card(sd-card reader or dropbox as you dont have usb-connection)
Edit: First boot into fastboot and connect it to your pc. From here you need fastboot.exe from the android sdk. Then you run "fastboot oem boot" and take note of the CID you get in the console.
edit 2: here is the full guide:
http://forum.xda-developers.com/showthread.php?t=691639&highlight=usbbrick
You will need to do somethings different, as you don't have root, but i might be able to guide you thrugh it.
...ran fastboot oem boot , this is what I got:
C:\android\tools>fastboot oem boot
... INFOsetup_tag addr=0xA0000100 cmdline add=0x8E
07F9F0
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 0
INFOTAG:hwid 0x0
INFOTAG:skuid 0x26A0D
INFOTAG:hero panel = 0x3
INFOTAG:engineerid = 0x0
INFOMCP dual-die
INFOMCP dual-die
INFOTAG:mono-die = 0x0
INFODevice CID is not super CID
INFOCID is HTC__032
INFOsetting->cid::HTC__032
INFOserial number: HT09HPL05298
INFOcommandline from head: no_console_suspend=1
INFOcommand line length =428
INFOactive commandline: board_bravo.disable_uart3=1 board_bravo.
INFOusb_h2w_sw=1 board_bravo.disable_sdcard=0 diag.enabled=0 boa
INFOrd_bravo.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e
INFOmmc=false androidboot.baseband=5.11.05.27 androidboot.cid=H
INFOTC__032 androidboot.carrier=HTC-EastEurope androidboot.mid=P
INFOB9920000 androidboot.keycaps=qwerty androidboot.mode=normal
INFOandroidboot.serialno=HT09HPL05298 androidboot.bootloader=0.9
INFO3.0001 no_console_suspend=1
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
INFOmpu_nand_acpu_rw A1E 1000
INFOjump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker
INFOnel_addr(0x20008000)
INFO-------------------hboot boot time:36923 msec
FAILED (status read failed (Too many links))
finished. total time: 5.339s
Ok what you need is "HTC__032" Now you need to download the img file from the thread i linked and install a hex-editor. Then you can use the hex-editor to insert "HTC__032" into the img file instead of the one it came with.
After that you just need to flash it I can't help you on that until tomorrow though it's past midnight here.
To get temporary root try to get visionary+ app (not available from market) then look at USB brick thread in development section. I had a similar issue
Sent from my HTC Desire using XDA Premium App
mortenmhp said:
Ok what you need is "HTC__032" Now you need to download the img file from the thread i linked and install a hex-editor. Then you can use the hex-editor to insert "HTC__032" into the img file instead of the one it came with.
After that you just need to flash it I can't help you on that until tomorrow though it's past midnight here.
Click to expand...
Click to collapse
... stuck.
downloaded img file.
downloaded hex editor
changed img file line to HTC__032
now this guide you mentioned says:
3. Get flash_image from the attached files below
Move this to /data/ , and flash the modified image using:
"/data/flash_image misc /data/mtd0.img"
You can move both mtd0.img and flash_image by putting it on your sdcard, and issueing the following command in a terminal emulator:
'cat /sdcard/flash_image > /data/flash_image'
'cat /sdcard/mtd0.img > /data/mtd0.img'
question is where is this "data" folder?
there is no this kind of folder on the SD card (should I create it?) , also there is no Data folder on Android sdk folder. I must missing something.
P.S. before flashing I probably need to run "fastboot oem enableqxdm 0" to enable SD card?
anyway... thanks now. Im going to sleep as well. tomorrow is a busy day, so I might not be able to watch this thread until later in the evening. lets keep fingers crossed that Ill fix this.
... good night.
abz54 said:
To get temporary root try to get visionary+ app (not available from market) then look at USB brick thread in development section. I had a similar issue
Sent from my HTC Desire using XDA Premium App
Click to expand...
Click to collapse
... got up now. Good morning
I have downloaded Visionary+ and tried temporary root. It seems it worked as superuser has created after reboot. However I will not proceed until next step is clear. Thanks a lot at the moment.
manager2a said:
'cat /sdcard/flash_image > /data/flash_image'
'cat /sdcard/mtd0.img > /data/mtd0.img'[/I]
question is where is this "data" folder?
Click to expand...
Click to collapse
The data folder is present on the phone's filesystem.
You should put the two files on the sdcard (not inside any folder) and then issue the commands in a terminal emulator on your phone.
Hi,
I had the same problem when my Misc partition got corrupted and I also flashed a RUU update which broke my SLCD screen as well (not to mention unrooting my phone).
So in the end I had a stock rom, unrooted phone which wasn't recognized by my laptop, unrevoked, adb etc.
Quanchi's guide : http://forum.xda-developers.com/showpost.php?p=9056719 helped solve my problem.
The rageagainstthecage exploit gives you temp root after which you can flash the correct mtd0.img for your phone from your SD card. All steps are outlined in that guide
This will solve your problems!
thanks a lot for the information.
I have downloaded this Rageagainstthecage and already modified mtd0.img earlier.
Ill try this later when I will have time and let you guys know if succeed.
manager2a said:
thanks a lot for the information.
I have downloaded this Rageagainstthecage and already modified mtd0.img earlier.
Ill try this later when I will have time and let you guys know if succeed.
Click to expand...
Click to collapse
You dont need to follow the rageinthecage method as that is another way of getting root, you should already have root through visionary+, so you only need to follow the methods on the usb-brick thread
just entered this command from emulator:
'cat /sdcard/flash_image > /data/flash_image'
got response : cannot create /data/flash_image: permission denied .
...damn need to run... back after few hours
manager2a said:
... got up now. Good morning
I have downloaded Visionary+ and tried temporary root. It seems it worked as superuser has created after reboot. However I will not proceed until next step is clear. Thanks a lot at the moment.
Click to expand...
Click to collapse
Downloaded the visionary+ APK??? Where did you place it? How and where did u execute it?
How do we get this terminal access? I understand that we need to move the image & mstd0 files to /data from /sdcard. But the problem is, I do not have any access to the file system on the phone of on the SD Card at this moment. The only access we have is the bootloader interface.
How did you manage to execute visionary+ (or any other terminal emulator or file manager) apk on your bricked phone?
Can you pl elaborate?
well bricked is not fully "bricked" as you read from the thread I have most of the functionality but problem is with dropping calls and no connections with PC. so everything can be instaled via market at the moment as I have no problem with internet connection.
for now I got USB connection back. wohoooo ...!!! Thanks to everybody who helpe me so far.
So one problem solved.
next plan would be to :
root again,
reinstall InsertCoin rom,
restore data from old nand backup.
... boarding plane right now, continuing after few hours...
Now I can say its done!
everything is back to normal like it was before.
In the end I
USB-Unbricked the phone
Rooted with Unrevoked3
Restored old rom and data.
only thing is Im currently S-ON. so I need to proceed with this issue as well.
Last remaining question: should I still retry to install new updated HBoot withAlpharev 1.8?
Hi All.
Not my phone, but a friends:
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
If you go into recovery, the phone just vibrates a few times and turns off. If you go Factory Reset, the phone just freezes.
I've tried:
RUU with no luck (get's stuck on Rebooting into Bootloader)
tried putting the .ZIP onto the SD but got "ModelID Incorrect" (can't create a GoldCard as phone won't boot, therefor no ADB)
flashing a recovery through fastboot but got "FAILED (remote: signature verify fail)"
booting into recovery using fastboot boot (FAILED (remote: signature verify fail))
I assume all my issues have been due to S-ON.
I'm stumped - any ideas?
There have been a few folks on here with the same issue in the last few weeks. Not that the phone is terribly old, but I wonder if it can be that some hardware component (eMMC or other) is failing over time?
expza said:
Hi All.
*snip*
RUU with no luck (get's stuck on Rebooting into Bootloader)
tried putting the .ZIP onto the SD but got "ModelID Incorrect" (can't create a GoldCard as phone won't boot, therefor no ADB)
flashing a recovery through fastboot but got "FAILED (remote: signature verify fail)"
booting into recovery using fastboot boot (FAILED (remote: signature verify fail))
?
Click to expand...
Click to collapse
IIRC there is a way to create a GoldCard manually without the phone ... but i'm highly unsure :-s
The last two sounds like an error due to s-on
oelly said:
IIRC there is a way to create a GoldCard manually without the phone ... but i'm highly unsure :-s
The last two sounds like an error due to s-on
Click to expand...
Click to collapse
I was able to create a working GoldCard using my phone, it no longer gives Model-ID Incorrect. HOWEVER, new problem. It's now moaning about Main Version being older, update failed.
I see android-info.txt in the ZIP is:
modelid: PC1010000
cidnum: T-MOB010
mainver: 2.15.531.3
hbootpreupdate:12
However, this phones info is:
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
I assume it's the Radio Version number that is not matching up - however, the one RUU's in Shipped-Roms with that Radio Number are EXE's and not ZIPs.
Does anyone know how I can get a ZIP RUU that would work with this phones current versions?
edit: p.s. ZIP I'm currently using is PC10IMG_Vision_TMOUS_2.15.531.3_Radio_12.52.60.25U_26.08.04.30_M3.zip (renamed when on SDcard to PC10IMG.zip)
double edit: Have found a way to extract zip from EXE. Loaded it to Gold Card and update is currently flashing via HBOOT. Still on Bootloader. Assume this takes a while (10 - 15 minutes), so I'll be patient.
combo edit: should state the the RUU ZIP I extracted was RUU_Vision_Gingerbread_S_HTC_WWE_2.42.405.2_Radio_12.56.60.25_26.10.04.03_M_release_199043_signed.exe
Phone honors the PC10IMG.zip, but gets stuck on BOOTLOADER - Updating.
Any suggestions? Is it safe to delete items out of the RUU .zip? Want to try flash recovery.img only.
edit: looks the the rom.zip I extract is always corrupt (when trying to edit it using WinRAR or something)
You can't edit the zips, they are signed, so anything you do to them will cause them to not flash.
Winrar might be complaining because of the signing.
-Nipqer
Given up on trying to flash the RUU via HBOOT - it just freezes on "Bootloader - Updating" - pulling battery causes no issues so I assume it doesn't even attempt to flash anything.
Next step, using HTCDev to unlock the bootloader? Safe? I worry that the Bootloader not flashing via RUU means that HTCDev Bootloader Unlock won't work, or could possibly break it.
same problem
hi mate, im having the exact same problem as you...did you manage to fix it?
i have found the same ruu for my radio version but it gets stuck on the bootloader as the bar moves but the fone stays on the same screen.
do u think i need to make that goldchip card? how do i make one please?
i had that same problem just 2 days ago so in order to get the ruu to flash right it has to be a radio thats higher than the one you already have ... but if that dosnt work you will have to change it manualy using adb in recovery mode so wat you do is power offf the phone comptley and plug it in your computer via usb then open up adb and type adb devices the phone has to be off and it should show your device id then the word recvery next to it then your gunna wanna pull the misc.img from the phone and edit it with a hex editor i did this method to downgrade my g2 kus my sdcard dosnt read but after you change the misc the ruu shuld flash fine 1.power off phone Connect phone to computer,
2.Open adb cmd and type : adb shell
3.Type su
4. if you get # symbol continue
5.Type : dd if=/dev/block/mmcblk0p24 of=/sdcard/misc.img (YOU CAN COPY THE IMG TO EITHER sdcard, which is internal memory, or sdcard2, which is removal card)
6. Switch to USB mode
7.copy misc.img from the root of the sdcard to your computer
8.Open misc.img with HeX Editor XVI32
9.Find the version and change it. it will be the first area in the the upper right in the screen of the app
10.change the number in whatever you want. (has to be in the form of.. 1.00.000.0
11.Save it and upload it to the root of the sdcard with miscnew.img name
12. Switch to charge mode
13.Type adb shell, su dd if=/sdcard/misc.img of=/dev/block/mmcblk0p24
14.Reboot to fastboot then fastboot reboot to RUU then fastboot flash PC10IMG.zip and it shuld flash fine
---------- Post added at 11:42 PM ---------- Previous post was at 11:37 PM ----------
or yu can try this http://forum.xda-developers.com/showthread.php?t=1526316 and should work its alot easier than the adb method
Never managed to fix this (tried the exact same thing ari3z suggested, but ages ago) - just kept freezing when trying to write anything to flash.
Phone was eventually swapped out in warranty.
I've searched the forum and Google high and low to solve this and have come up with the following:
1. Running the RUU. Result: "Wrong customer" error.
2. Grabbing rom.zip from RUU temp files, renaming PK76IMG.zip, flashing from bootloader. Result: No dice.
3. Repeat step 2 on a Goldcard. Tried MMC0 and MMC2 (GoldCard generator got errors with MMC1). Result: "CID incorrect! Update Fail!"
4. Flashing zip from command line as follows:
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip rom.zip
Result: "CID error"
5. Relocking bootloader and repeating #4. Result: same.
6. Change CID as follows: fastboot oem writecid HTC__001. Result: COMMAND ERROR!
7. Downloaded various other fastboot.exe and re-run step 6. Result: COMMAND ERROR!
8. Flashing with fastboot: fastboot flash system system.img. Result: "FAILED (remote: data length is too large)." This one boggles me because the extracted system.img for the HTC UE ROM (what I'm trying to flash) is identical to the HTC Asia ROM (what I have).
9. What's your idea???????
BTW, can I replace the android-info.txt in the HTC EU ROM with the one from the HTC Asia ROM without negative ramifications?
Bump.
So using Goldcard and flash RUU also not working ?
I used to use Goldcard to flash RUU which is not meant for my Desire before.
Thread moved to Q&A.
Sent from my Galaxy Note (i717), using XDA Permium.
•••••••••••••••••••••••••••••••••••••••••••••••••
XDA Rules:
http://forum.xda-developers.com/announcement.php?a=81
Ten post rule:
http://www.xda-developers.com/android/10-post-rule-explained/
Marketplace Rules (updated):
http://forum.xda-developers.com/announcement.php?f=476
ckpv5 said:
So using Goldcard and flash RUU also not working ?
I used to use Goldcard to flash RUU which is not meant for my Desire before.
Click to expand...
Click to collapse
Yes. The same works for Wildfire S. But to change my Wildfire S from Asian to European I ultimately had to flash from fastboot.
I only tried MMC0 so I'm going to try MMC1 and MMC2 next.
I tried MMC1 and MMC2 tonight.
MMC1 didn't work. SimpleGoldCard.exe reported errors and couldn't produce the GoldCard.
MMC2 produced a different CID and successfully generated a GoldCard, but the install failed again: "CID incorrect! Update Fail!"
Any ideas? It can't be impossible to do this!
When we connect our phone as usb drive, with sdcard inserted, there are two removable storage, so patch the sdcard alone with the goldcard won't work as the other is not patched. Anyway this is my guess only.
Delete.
My next approach to changing to CID to the Super CID comes from the AT&T One X forum:
[UNLOCK] AT&T Bootloader Unlock Through HTC-Dev
Thoughts???
CafeKampuchia said:
My next approach to changing to CID to the Super CID comes from the AT&T One X forum:
[UNLOCK] AT&T Bootloader Unlock Through HTC-Dev
Thoughts???
Click to expand...
Click to collapse
Any idea what is mmcblk0p4 referring to ? As we know for one v, our dev/block is numbered differently.
Actually, I don't. I don't think retrieving this block is going to work on the One V, but the method he used will. He found the block containing the CID by searching a dump. I don't (yet) know how to do that.
CafeKampuchia said:
Actually, I don't. I don't think retrieving this block is going to work on the One V, but the method he used will. He found the block containing the CID by searching a dump. I don't (yet) know how to do that.
Click to expand...
Click to collapse
Hi,
I'm trying to figure out how to do the same thing. I can't revert to stock because I have a One V on Three, and the radio is a later version than the RUU online. I found a similar guide to changing the CID on a One S that you did:
http://forum.xda-developers.com/showthread.php?t=1674202
This thread shows how to look at the contents of those blocks:
http://forum.xda-developers.com/showthread.php?t=1694700
And this one gives the purpose of each partition, at least for the primoc, probably same for primou:
http://forum.xda-developers.com/showthread.php?t=2156415
I wrote a BASH script to search through the blocks for a given bit of text, which you can use if you're on Linux by making sure it has execute permission, and running it with the search string (change .txt to .sh if you like). For my CID (H3G__001), I used ./findinblock H3G__001. It is case sensitive. I found my CID in partitions 7, 18, 23, 25 & 26.
Maybe 7 is the one to change. I'm not sure I'm quite ready to just blindly experiment, even if it may be possible to revert. I wonder if someone more experienced can weigh in?
I tried overwriting the CID in mmcblk0p7 but it didn't "take":
Code:
C:\adt-bundle-windows-x86\sdk\platform-tools>adb shell
[email protected]:/ # strings -n 8 /sdcard/mmcblk0p7MOD
strings -n 8 /sdcard/mmcblk0p7MOD
HTC__001
<snip>
[email protected]:/ # strings -n 8 /dev/block/mmcblk0p7
strings -n 8 /dev/block/mmcblk0p7
H3G__001
<snip>
[email protected]:/ # dd if=/sdcard/mmcblk0p7MOD of=/dev/block/mmcblk0p7
dd if=/sdcard/mmcblk0p7MOD of=/dev/block/mmcblk0p7
4096+0 records in
4096+0 records out
2097152 bytes transferred in 0.393 secs (5336264 bytes/sec)
[email protected]:/ # strings -n 8 /dev/block/mmcblk0p7
strings -n 8 /dev/block/mmcblk0p7
H3G__001
<snip>
Perhaps using a goldcard would help. I've only ever done this putting the goldcard directly in the phone. In this case we'd need to use a Y cable to allow a working sdcard in the phone (unless you can store the modded CID partition somewhere else) and I don't have the hardware to hand.
Can anyone else help?
Ok, I tried this with a gold card, sorting this modified block in internal storage instead of SD card. Still no joy.
Sent from my Nexus 7 using XDA Premium HD app
>_<''
Hey everyone
I got the same Problem.
I've found my CID, which is O2___102, on partition 7, 18, 23, 29 and 32.
I made some screenshots of it.
Maybe anyone can help.
P.S.:
Does anyone now the filesize of the mmcblk0p4 partition of the AT&T One X??
Maybe this information can be helpful
- greetings, animeryumyu
EDIT:
I just find out, that the needed partition for modding is the bootloader itself.
At least I read it in the "how to SuperCID" for the HTC One SV (K2_U / K2_UL)
For the One SV it is the same partition as for the AT&T One X.
And before the CID and IMEI of both, the X and the SV is a little text that reads "HTC-BOARD-INFO!".
Maybe this is important to.
Does anyone now any other indicators to find out, which partition is the bootloader??
Maybe, when we get SuperCID, we are one step closer to S-OFF our device
Im trying to flash RUU-HTC_One_M8_GPE_4.4.4-2.12.1700.1.zip on my GSM HTC One M8.
I have root, S-off. when putting in command i get the following error...
C:\>fastboot flash zip Desktop/RUU-HTC_One_M8_GPE_4.4.4-2.12.1700.1.zip
error: cannot open 'RUU-HTC_One_M8_GPE_4.4.4-2.12.1700.1.zip'
any help would be great!
Thanks
Hi,
Have you checked the md5 checksum of the file you want to flash? Probably the file is broken..
Probably have a look into this thread here : http://forum.xda-developers.com/showthread.php?t=2708589