Jump to content

root for 1.22.771.1


Recommended Posts

Guest tangyiyong
Posted (edited)

PLEASE deleted this thread!

thx

Edited by tangyiyong
Guest RalphM
Posted
I flash my Desire to xxxx-H3G-UK-1.22.771.1-xxxxx,and i found I can not root with the 'r5-desire-root-alt', please help me~how to root the xxxx-H3G-UK-1.22.771.1-xxxxx?

thanks.

Your current build on a UK version should be 1.15. Where you you getting the 1.22? Settings, About Phone, Software.

Guest geek78
Posted
Your current build on a UK version should be 1.15. Where you you getting the 1.22? Settings, About Phone, Software.

You can find it on xda-dev forum

Guest potter97
Posted
I flash my Desire to xxxx-H3G-UK-1.22.771.1-xxxxx,and i found I can not root with the 'r5-desire-root-alt', please help me~how to root the xxxx-H3G-UK-1.22.771.1-xxxxx?

thanks.

As descirbed in the post over at XDA you need to have root FIRST before you can flash!

Please read threads fully !!

Guest tangyiyong
Posted
As descirbed in the post over at XDA you need to have root FIRST before you can flash!

Please read threads fully !!

I just make the gold card,the run the RUU_xxxxxxx,then it flash my desire~~~

the build number:1.22.771.1 CL175326 release keys

Guest tangyiyong
Posted
I just make the gold card,the run the RUU_xxxxxxx,then it flash my desire~~~

the build number:1.22.771.1 CL175326 release keys

My hboot is 0.80,and the build is 1.22.771.1

please help me~~~

Guest mrshark
Posted
My hboot is 0.80,and the build is 1.22.771.1

please help me~~~

why the hell do you update your phone as soon as an update arrives, without anybody tells you to do it, KNOWING that it is rootable? You could have waited until paul release...

Guest craigcrawford1988
Posted
why the hell do you update your phone as soon as an update arrives, without anybody tells you to do it, KNOWING that it is rootable? You could have waited until paul release...

My thoughts exactly. As soon as people see a release, they flash it and if something breaks they cry. Why don't they just WAIT?

Guest dreamdealer
Posted
My thoughts exactly. As soon as people see a release, they flash it and if something breaks they cry. Why don't they just WAIT?

probably the only good thing the USB bricking has brought to the community most people don't rush into flashing.

Guest tangyiyong
Posted
My thoughts exactly. As soon as people see a release, they flash it and if something breaks they cry. Why don't they just WAIT?

I will never flash and root again,until the 2.2 for desire is released.And now,I lock my Desire, use My Hero back.

wait for Paul and the HTC.........

Guest tangyiyong
Posted
I will never flash and root again,until the 2.2 for desire is released.And now,I lock my Desire, use My Hero back.

wait for Paul and the HTC.........

yesterday,I buy a Adfree account,and custom a madaco rom,and prepare to flash my desire, and found,I cann't root my Desire again,because I flash the 1.22 ruu.........My god,who can save me?

Guest xTc is loVe
Posted
yesterday,I buy a Adfree account,and custom a madaco rom,and prepare to flash my desire, and found,I cann't root my Desire again,because I flash the 1.22 ruu.........My god,who can save me?

Nobody! :( Think in a few days 2.2 Roms are rooted, too. But the best thing that the bricks are over!

Guest n8schicht
Posted
Why don't they just WAIT?

Because patience is a virtue :(

And it's the hunger (or greed?) for new stuff that drives people to do so.

Guest tangyiyong
Posted
Because patience is a virtue :(

And it's the hunger (or greed?) for new stuff that drives people to do so.

the output:

=========================================================

D:\desk\Desire\RUU\r5-desire-root-alt>step1-windows.bat

Desire Root Step 1

Erasing cache and rebooting in RUU mode...

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.

D:\desk\Desire\RUU\r5-desire-root-alt>

===================================================================

It seems ''flashing the testimage'' is fail!

"fastboot-windows.exe flash zip testimage.zip"

Guest tangyiyong
Posted
the output:

=========================================================

D:\desk\Desire\RUU\r5-desire-root-alt>step1-windows.bat

Desire Root Step 1

Erasing cache and rebooting in RUU mode...

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.

D:\desk\Desire\RUU\r5-desire-root-alt>

===================================================================

It seems ''flashing the testimage'' is fail!

"fastboot-windows.exe flash zip testimage.zip"

the method I think that can let me flash ruu_1.22.

1:run the ruu_1.22.771.1_xxxx,get the rom.zip.

2:unyaffs the system.img,get the system packages.

3:add the su,superusr.apk and others apk to the fold.

4:repack the changed fold to system.img again.

5:replace the system.img in the file - rom.zip.

6:rename the rom.zip->testimage.zip,and replace the file in the r5-desire-root-alt.

7:root again:return+power->step1->step2.

Is there any error or fault?

Is it probably right?

Is there a superman, a clark kent, tell me~

Guest craigcrawford1988
Posted

Are you using a goldcard?

Guest Namtaffy
Posted

that stock rom is quite nice, good battery life (better than MCR), though I still love custom roms, running stock with this. Very stable, quick and v good battery

Guest tangyiyong
Posted
Are you using a goldcard?

yes,I make a goldcard.

Guest tangyiyong
Posted

I'm waiting for you~~~~

who can root the 1.22.771.1 stock rom?

Guest SgtDavePwnage
Posted
I'm waiting for you~~~~

who can root the 1.22.771.1 stock rom?

I assume you are using the .80 root method?

If that wont work it is because you have a later software version than the one contained in the test rom, and it wont allow you to flash

Guest tangyiyong
Posted
I assume you are using the .80 root method?

If that wont work it is because you have a later software version than the one contained in the test rom, and it wont allow you to flash

yes,I have a 0.80 hboot.

yes,I think it is failed because the test rom's version.

And when and who will update the test rom~~~~~~~~~~~~~~~~~~~~~~?

Guest tangyiyong
Posted
yes,I have a 0.80 hboot.

yes,I think it is failed because the test rom's version.

And when and who will update the test rom~~~~~~~~~~~~~~~~~~~~~~?

木有人帮忙……

Guest newbe5
Posted
木有人帮忙……

Did you work out how to do this? I am in the same situation and need to either root or remove 1.22!

Guest wookoouk
Posted

Sadly I am in the same position, ment

there is very litte (nothing) that can be done to fix this without root.

  • 2 weeks later...
Guest tangyiyong
Posted
Sadly I am in the same position, ment

there is very litte (nothing) that can be done to fix this without root.

One question to the Admin of this forum,And Paul:

where did you get the testimage.zip for 1.21.405.2?

or how do you sign it?

Can I use the same method for the 1.22.771.1 or later rom?

waiting for your help~

thanks a lot!

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.