Develop Bugs

[Q] Can't root Desire, HBOOT 0.93.0001

I've tried to root it in many ways.
My only reason of rooting is installing Georgian glyphs,
as I would like to have georgian alphabet support.
It's a very big issue for us:
code.google.com/p/android/issues/detail?id=5925
code.google.com/p/android/issues/detail?id=8394&q=georgian&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars
#########################
unrevoked.com
with unrevoked 3.21 and even 3.22 version. no way.
it tells me: Internal error: couldn't find misc.
Afterwords I've tried r6-desire-root-alt, no success in this front too:
Code:
ladbook:r6-desire-root-alt alinux$ ./step1-mac.sh
Desire Root Step 1
Erasing cache and rebooting in RUU mode...
Password:
erasing 'cache'... OKAY
... OKAY
About to start flash...
< waiting for device >
sending 'zip' (138708 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
FAILED (remote: 43 main version check fail)
sending 'zip' (138708 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
FAILED (remote: 43 main version check fail)
Rebooting to bootloader...
rebooting into bootloader... OKAY
Step 1 complete - now use the bootloader menu to enter recovery mode.
To do this, press the power button, wait a few seconds, then use the volume keys and power button to select the RECOVERY option.
ladbook:r6-desire-root-alt alinux$
My phone details:
BRAVO PVT1 SHIP S-ON
HBOOT-0.93.0001
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.09.05.30_2
with OTA updated Froyo 2.2
Any help is very appreciated! Thank you in advance!

unrEVOked works with no issues on that HBOOT - sounds like you've not made sure the right drivers are installed

EddyOS said:
unrEVOked works with no issues on that HBOOT - sounds like you've not made sure the right drivers are installed
Click to expand...
Click to collapse
First of all thank you for your reply.
Primary I've done it in MacOSX.
Afterwards I repeated it on Win 7, I was following this guide:
http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
for driver installation.
But, same result.
Is there way to make a TOTAL HARD reset, and maybe redo rooting with the latest unrevoked?

Download the Slax iso and the create a bootable cd, then download unrevoked 3.2.1(for linux) and save it onto the flash.
Boot from slax cd, copy files from flash to desktop, install and follow the onscreen instructions with unrevoked.

I had no issues in Windows 7 x64 Ultimate using unrEVOked so can't really comment, sorry

RaymondErasmus said:
Download the Slax iso and the create a bootable cd, then download unrevoked 3.2.1(for linux) and save it onto the flash.
Boot from slax cd, copy files from flash to desktop, install and follow the onscreen instructions with unrevoked.
Click to expand...
Click to collapse
Hello,
I've tried it with Linux too now...
I have a Ubuntu partition. With "sudo ./reflash" in the same way like win or mac gives me:
Internal error: couldn't find misc.

i have the same problem. after i installed this rom RUU_Bravo_Froyo_HTC_ARA_2.32.415.3_Radio_32.49.00. 32U_5.11.05.27_release with bootloader 0.93.0001 i cannot root. any solution yet? thanks in advance

People! I've done a downgrade from 0.93.0001 to HBOOT-0.83.0001
I've used this downgrade tool:
http://www.brutzelstube.de/wp-content/uploads/2010/09/downgrade23a.zip
My stuff at the moment:
2.1-update1 firmware.
32.41.00.32U_4.08.00.09 radio.
1.21.405.2 software version.
build number: 1.21.405.2
Should I root now?

i have tested this too but it did not work for me. what did u exactly do?

gonjeshk said:
i have tested this too but it did not work for me. what did u exactly do?
Click to expand...
Click to collapse
boot in linux.
use terminal for:
unzip donwgrade23a.zip
move into:
desire_downgrade
and launch with sudo:
sudo ./donwgrade.sh
and wait

i did exactly that but i get error messages:
./adb: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory
Your phone is now ready to be downgraded - rebooting to bootloader.
Starting in 10 seconds (ctrl-c to quit)
./adb: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory
what can i do now?

alinuxos said:
boot in linux.
use terminal for:
unzip donwgrade23a.zip
move into:
desire_downgrade
and launch with sudo:
sudo ./donwgrade.sh
and wait
Click to expand...
Click to collapse
Worked like a charm! Thanks.

That is this thread:
http://forum.xda-developers.com/showthread.php?t=768256
It also works in Windows

gonjeshk said:
i did exactly that but i get error messages:
./adb: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory
Your phone is now ready to be downgraded - rebooting to bootloader.
Starting in 10 seconds (ctrl-c to quit)
./adb: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory
what can i do now?
Click to expand...
Click to collapse
It's ubuntu dependencies, you should have libstdc++ installed.
try sudo apt-get install libstdc
or if not,... try to find a right package with command apt-cache search libstdc

alinuxos said:
People! I've done a downgrade from 0.93.0001 to HBOOT-0.83.0001
I've used this downgrade tool:
http://www.brutzelstube.de/wp-content/uploads/2010/09/downgrade23a.zip
My stuff at the moment:
2.1-update1 firmware.
32.41.00.32U_4.08.00.09 radio.
1.21.405.2 software version.
build number: 1.21.405.2
Should I root now?
Click to expand...
Click to collapse
Go for it ... i see no reason why you shouldnt be able to root and then let us know how it went.
Its strange that some people running HBOOT 0.93 have issues rooting, were any of your phones branded? I read somewhere that vodafone or something with this hboot gives issues when trying to root

I have HBOOT 0.93.0001 and I could root fine.

now i get this error message with using ubuntu live cd:
no device found and in phone bootloader tells me the version would be older....
maybe it depends on the new rom i am havin now?

I have 0.93.0001 and rooted fine with unrevoked3

That hboot 0.93000001, was released as an OTA. This also updated my Desire to that new hboot version. Maybe a try to prevent rooting?
My desire was rooted before but I unrooted it because it needs sending to htc. It's suffering from random reboots when it gets hot. It reboots, then vibrates 7 times. Google it, a lot of people have this problem.
I'm hoping I'll be able to root again when I get it back, because I just neeeeeed to run MIUI..
Ah the above comment comforts me I'll just try unrevoked again.

i tried Unrevoked and all downgrade tools , but always have problem some where , but main problem that after the phone reboot it's always can not find the phone and give me error , i recheck the adb many times and used Linux and windows 7 64 bit .
please help

[Q] Can't change CID

My desire HD was branded from VIRGIN.
I've downgraded to 1.32.405.3.
Unrooted, SHIP S-OFF
The only problem i have is that i can't change the CID from VIRGI001 to unbranded.
# ./gfree -f
./gfree -f
--secu_flag off set
--cid set. CID will be changed to: 11111111
--sim_unlock. SIMLOCK will be removed
Section header entry size: 40
Number of section headers: 44
Total section header table size: 1760
Section header file offset: 0x00015384 (86916)
Section index for section name string table: 41
String table offset: 0x000151cb (86475)
Searching for .modinfo section...
- Section[16]: .modinfo
-- offset: 0x000011cc (4556)
-- size: 0x000000cc (204)
Kernel release: 2.6.32.21-gbe90714
New .modinfo section size: 204
Attempting to power cycle eMMC... OK.
Write protect was successfully disabled.
Searching for mmc_blk_issue_rq symbol...
- Address: c02a8e48, type: t, name: mmc_blk_issue_rq, module: N/A
Kernel map base: 0xc02a8000
Kernel memory mapped to 0x40002000
Searching for brq filter...
- Address: 0xc02a8e48 + 0x34c
- 0x2a000012 -> 0xea000012
Backing up current partition 7 and patching it...
patching secu_flag: 0
Done.
# sync
sync
<Reboot>
but after reboot the CID is still the same with CID Getter
tried other methodes, but they all use gfree....

Are you following this thread?
http://forum.xda-developers.com/showthread.php?t=857444
If not, do so.

I've tried that already, still the CID keeps the branded one.

massivekid said:
I've tried that already, still the CID keeps the branded one.
Click to expand...
Click to collapse
If you have ENG S-OFF boot into bootloader (HBOOT) and check the CID via System Info.

My HBOOT lists:
ACE PVT SHIP S-OFF
HBOOT-0.85.0007
MICROP-0438
eMMC-boot
oct 11 2010, 12:47:02
HBOOT
<VOL UP> to previous item
<VOL Down> to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
and i don't see any system info

As I said, "If you have ENG S-off".
Do that first, get ENG S-Off. Page 3 ish of development forum last time I checked.
[EDIT] http://forum.xda-developers.com/showthread.php?t=855403
Aren't I nice??

Very nice, you even made me smile, and I never smile.
MR_JMM is correct once you have ENG S-OFF look in "System Info", I'm pretty sure your CID will read CID: 11111111. There is a know bug/glitch that incorrectly reports your CID if you view it from elsewhere.

andyharney said:
Very nice, you even made me smile, and I never smile.
Click to expand...
Click to collapse
Glad it did as you're the only reason I said it!! *rasp*

Thanks nice guy ;-)
You are absolutely right. CID displays CID-11111111
So it was already unlocked and i didn't know that the applications are displaing the wrong (original) CID.
As for OTA updates, are they not checking the CID also to present updates?
And if they get the old value, only displaying updates from the brand?

[Q] Problem Flashing Radio Help Please

Hi as the title suggests im experiencing some problems flashing my radio to the latest verion, first of all im trying to flash via Clockwork Recovery v5.0.2.0 by selecting install zip from SDcard then pointing to the new radio, the error im getting is:
Installing /sdcard/bravo.5.17.05.23.zip
finding update package........
opening update package.......
Installing update.........
Amend scripting (update-script) is no longer supported.
Amend scripting was depreceated by google in andriod 1.5
It was necessary to remove it when upgrading to the clockworkmod 3.0 gingerbread based recovery.
Please switch to Edify scripting (updater-script & update-binary) to create working update zip packages.
Installation aborted.
Whatever all that lot means ????????????
Now my system details are as follows
Revolutionary
BRAVO PVT4 SHIP S-OFF
HBOOT 6.93.1002
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.14 (ive read this is a bad batch and I have lots of signal issues this is why I want to change it)
I am using the latest Runny ROM v5.5, sense version 3.5, Andriod 2.3.5
Any help would be greatly appreciated
TIA

I think you need to flash through fastboot.. Android flasher makes it easy.
I may be wrong though!

This flashing of the Radio is causing me all sorts of headaches, ive just tried the fastboot way of flashing and been met with the following error:
What am I doing wrong here ?

Seems to me, that Windows does not know, in which directory it should search for this library.
Did you install the Android SDK? This will be necessary because it contains the library.
Maybe, this post will help you:
http://forum.xda-developers.com/showpost.php?p=11139522&postcount=5

Thanks, just finished flashing the latest radio, after following those instructions you posted, all went well, thanks again.

Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A

Error trying to flash radio
Hello,
I just tried to flash via Fastboot, and got the following error returned:
H:\>fastboot.exe flash radio D:bravo.5.17.05.23.zip
sending 'radio' (11561 KB)...
OKAY [ 1.906s]
writing 'radio'...
FAILED (remote: image update error)
finished. total time: 1.969s
OK - so after reading much more carefully - I realised you don't flash the .zip like you would a ROM, you just need to flash the .img file.
So having extracted the radio.img from the .zip ..... it all went fine (my first ever fastboot)
H:\>fastboot.exe flash radio D:radio.img
sending 'radio' (26112 KB)...
OKAY [ 4.281s]
writing 'radio'...
OKAY [ 31.172s]
finished. total time: 35.453s
H:\>

[?] Can't flash the HTC EU ROM because of CID

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

FAILED (remote: 12 signature verify fail) during fastboot downgrading.

I'm (or I was) about to root my desire Z. Using strawmetal pdf as instructions first two steps went smooth. Everything as written with no errors.
Problems start with downgrading to stock froyo. Frist I've tried manual downgrade, but the phone did nothing after finding PC10IMG.zip (well it checked it and werify, but then just went back to bootloader with no message). So I reboot the phone and it loaded normaly to my system.
Then I tried second method Fastboot downgrade, but when I enter into a black screen with white/silver htc logo and type:
Code:
fastboot flash zip StockRom.zip
it gives me:
Code:
c:\platform-tools>fastboot flash zip StockRom.zip
sending 'zip' <288060 KB>... OKAY
writing 'zip' ... INFOsignature checking...
FAILED <remote: 12 signature verify fail>
I've tried rerun the fastboot flash zip StockRom.zip command multiple times, everytime the same output.
What I should do now?
update: I've found in #G2ROOT irc logs someone had similar problem to mine but with his G2, Nipqer aptly suggested pulling the sd card out of the phone, it's not working in my case
update2: I checked md5 sum of the stock rom linked in strawmetal.pdf and it was different from the one in [GUIDE] Downgrade G2 (2.3.X) & DZ (2.3.X) & mT4g (2.3.4) & DHD w/ S-ON to Stock Froyo
strawmetal's pdf: 621f7c807cde340f1353fc43f34a4ea4 dz_pc10img.zip 288 061 KB
guide stock rom: 2ff42897cd27e0db425a2cf36c8bd078 vision_dz_1.34.405.5_pc10img.zip 291 448 KB
After flashing the rom from xda forum guide I'm on stock froyo and advancing to obtain pernament root :victory:
update3: I'm rooted! It took me 2 hours but thankfully to xda community and all the helpfull articles I've done it!