• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [how to] manually achieve s-off,simunlock,supercid for Inspire 4g/DHD

scotty85

scotty85

Extreme Android User
the Advanved Ace Hack KIT(AAHK) has been the root standard for quite some time for ACE modles. the original creator has pull the links,it is no longer supported. (read about his reasons here)

fortunately,htcdev unlock has made it possible to manually apply the original exploit,without having to downgrade your entire rom. unfortunately,the htcdev unlock process will wipe your data. but,at any rate, it is my opinion that this method,while does use some adb/fastboot commands,is conceptually simpler,and easier to implicate since over time different variant of ACE changed so many variables and made the program extremely complex.

i take no credit for ATTN1's work. i only wish to help folks who have a desire for s off achieve the knowledge and tools to do the process. if all you need is to have root access to run a couple of root requiring apps,i sugest you simply unlock via htcdev(use the linked guide) and leave it at that.

the new manual guide is here:
A high-level DHD/Inspire manual S-OFF hack concept for advanced users | TAU – It's All About The Negative

first,use this thread to unlock your bootloader,install a recovery,and flash superuser zip files:
http://androidforums.com/desire-hd-...-how-unlock-install-recovery-root-htcdev.html
 
at this point,your stock rom has superuser access. if all you need is superuser access to run root,apps,you techncially can stop here. everything is stock,and s on is protecting the vital parts of your device.

if you have a desire to flash roms and diferent regional RUUs,and modify other partitions of your phone,then carry on :)

first download the "ace-tools.zip" file from the bottom of ATTN1's directions,at A high-level DHD/Inspire manual S-OFF hack concept for advanced users | TAU – It's All About The Negative

extract it,and move everything from that extracted folder,to your "miniadb" folder. if you have to,you can use a utility such as 7-zip to extract. you can drag and drop,or copy/paste or any other means your comfortable moving files.

*note: if you need to make a gold card,you may want to use a new,small,spare sd card for this. theres a chance it could be damaged,or reformatted,causing data loss.

start by making sure superSU is in your app drawer. from this point onward,adb and fastboot commands are in bold face,and can be simply copied from here,and pasted in your cmd window. open a cmd window,change to your miniadb directory(mine is miniadb_inspire):

cd c:\miniadb_inspire

check that you have root access:
adb shell should return $

su have your phone awake,and watch for a superuser prompt. touch grant. this should return #

exit

exit

you are now ready to start entering commands from the high-level guide.

the first comands are copying your stock boot image for later use. i am on the ATT inspire build and could not get the commands provided to work there seems to be some issue writing .img files to /data/local/tmp/. if you get cant open or permission denied errors,then you can use the following commands:
adb shell

su

dd if=/dev/block/mmcblk0p22 of=/sdcard/boot.img

exit

exit

adb pull /sdcard/boot.img



the next set of commands are making your sd card into a gold card.

adb push goldcard /data/local/tmp

adb shell

su

chmod 775 /data/local/tmp/goldcard

cat /sys/class/mmc_host/mmc2/mmc2:*/cid

/data/local/tmp/goldcard -c <sd card cid above> -o /data/local/goldcard.img
here you will have to plug in the number that the prior command spits out. space back to <sd card cid above>,and backspace it out. right click. click "mark" highlight the sd card number in white. hit enter or right click. paste the number in the spot where <sd card cid above> used to reside.

dd if=/data/local/goldcard.img of=/dev/block/mmcblk1

exit

exit

*note: after this,my sd card showed as damaged to the phone and was unaccessable. it still funtioned just fine to flash the downgrade firmware. it can be reformatted later for use in the phone.


these next commands are changing the misc version to allow instalation of the downgrade firmware:

adb push misc_version /data/local/tmp

adb shell

su

chmod 775 /data/local/tmp/misc_version

/data/local/tmp/misc_version -s 1.11.111.1

exit

exit

at this point you need to relock the bootloader. boot back to fastboot:

adb reboot bootloader

fastboot devices

fastboot getvar all *take note of this information. it lists your stock CID,and it MUST list main version as 1.11.111.1. if main version is something else,something has gone wrong,the donwngrade will not flash. if main version is correct,then procede.

fastboot oem lock you will get a FAILED (status read failed (Too many links)) error. this is normal. this will also cause the phone to reboot. after it does go back to bootloader:

adb reboot bootloader

and back to the directions to flash the downgrade firmware:

fastboot oem rebootRUU

fastboot flash zip firmware.zip
if you get an "error 41 or 42" FAILED! you do not have a correctly made gold card. if the zip starts flashing,wait of an OKAY in the cmd window. dont pay attention to the green bar on the phone screen,it will never reach the far right side ;)

fastboot reboot-bootloader

fastboot flash unlocktoken Unlock_code.bin to re-unlock with your original token,wich should still be in your miniadb_folder.

your phone will now try and reboot,but be unable to due to the old boot image. youll need to unplug from the pc,pull the battery for a few seconds,and then boot to hboot,select fastboot from the hboot menu. plug the phone back in. if your phone hangs in hboot,remove the sd card. then back to the directions. in the cmd window:

fastboot flash boot boot.img

fastboot flash recovery recovery.img

fastboot reboot

the phone should reboot. when its fully booted,youll need to skip the start up stuff,re-enable usb debugging,and turn off fastboot again. now boot to recovery:

adb reboot recovery this will boot your phone to a freaky,black screen :eek: give it a few seconds,then:

adb devices if the response is "offline" unplug for a few seconds and replug. try the comand again. when you get HTxxxxxxx recovery then procede

adb push gfree /tmp/

adb shell chmod 775 /tmp/gfree

adb shell /tmp/gfree -f

adb reboot bootloader

from start to finish,the cmd window should look something like this(red are entered inputs,blue are additional comments):

Code: 
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Scott>[COLOR="Red"]cd c:\miniadb_inspire[/COLOR]

c:\miniadb_inspire>[COLOR="red"]adb devices[/COLOR]
List of devices attached
HTxxxxxxxxxx    device


c:\miniadb_inspire>[COLOR="red"]adb reboot bootloader[/COLOR]

c:\miniadb_inspire>[COLOR="red"]fastboot devices[/COLOR]
HTxxxxxxxxxx    fastboot

c:\miniadb_inspire>[COLOR="red"][COLOR="red"]fastboot oem get_identifier_token[/COLOR][/COLOR]
                              ... INFO
INFO< Please cut following message >
INFO<<<< Identifier Token Start >>>>
INFO34194E39EDEA619C838476594B1A449F
INFOE45191AAC44BAF6D3D8A45623F70D1A1
INFO2A7152FB7965D38DB9D1C31A4B6DB151
INFO6C4B6681FE6FBED89E76F6E898B5987D
INFO78E4CB185180742E536B5A3907F38FC0
INFO5A057876958B1B39F4B1C2DCDBE217FF
INFODAAEDC0FB65531C9D9E799EA3819ACFA
INFOC1BBECD525D1F3C061C62EDA3E64E675
INFOE1FB77AFF515610368A7DF9AC52FE124
INFO210EE60E6A74F0872F6417AA4F590D1D
INFO69B233C7FE3EA54E4C61D1EDAE44A0A3
INFO5031FC8E5CD2C2714357B4BCA240F6D1
INFO796312B19F58DDA959CE314DCED660EC
INFO073A5D7354DE0EE492F6DA51C563638D
INFO442CA56D3990C78383DCEBE300C3AEED
INFO9822DBA596C23C8663D737A3CB34DB49
INFO<<<<< Identifier Token End >>>>>
OKAY [  0.066s]
finished. total time: 0.067s

c:\miniadb_inspire>[COLOR="red"]fastboot flash unlocktoken Unlock_code.bin[/COLOR]
  sending 'unlocktoken' (0 KB)... OKAY [  0.014s]
         writing 'unlocktoken'... INFOunlock token check successfully
OKAY [  0.009s]
finished. total time: 0.024s

c:\miniadb_inspire>[COLOR="red"]adb devices[/COLOR]
List of devices attached
HTxxxxxxxxx    device

c:\miniadb_inspire> [COLOR="red"]md5sums ace_recovery_ext_4.img[/COLOR]

MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help

[Path] / filename                              MD5 sum
-------------------------------------------------------------------------------
[c:\miniadb_inspire\]
ace_recovery_ext_4.img                         042e9fa838521592ec9224bfb27df52a

c:\miniadb_inspire>[COLOR="red"]adb reboot bootloader[/COLOR]

c:\miniadb_inspire>[COLOR="red"]fastboot boot ace_recovery_ext_4.img[/COLOR]
        downloading 'boot.img'... OKAY [  1.033s]
                       booting... OKAY [  0.003s]
finished. total time: 1.037s

c:\miniadb_inspire>[COLOR="Red"]adb shell[/COLOR]
$ [COLOR="red"]su[/COLOR]
su
# [COLOR="red"]dd if=/dev/block/mmcblk0p22 of=/sdcard/boot.im[/COLOR]g
dd if=/dev/block/mmcblk0p22 of=/sdcard/boot.img
8192+0 records in
8192+0 records out
4194304 bytes transferred in 1.652 secs (2538924 bytes/sec)
# [COLOR="red"]exit[/COLOR]
exit
$ [COLOR="red"]exit[/COLOR]
exit

c:\miniadb_inspire>[COLOR="red"]adb pull /sdcard/boot.img[/COLOR]
1904 KB/s (4194304 bytes in 2.151s)

c:\miniadb_inspire>[COLOR="red"][COLOR="red"]adb push goldcard /data/local/tmp[/COLOR][/COLOR]
671 KB/s (19240 bytes in 0.028s)

c:\miniadb_inspire>[COLOR="red"]adb shell[/COLOR]
$ [COLOR="red"]su[/COLOR]
su
# [COLOR="red"]chmod 775 /data/local/tmp/goldcard[/COLOR]
chmod 775 /data/local/tmp/goldcard
# [COLOR="red"]cat /sys/class/mmc_host/mmc2/mmc2:*/cid[/COLOR]
cat /sys/class/mmc_host/mmc2/mmc2:*/cid
02544d534130324705235a270400b2c6
# [COLOR="red"]/data/local/tmp/goldcard -c 02544d534130324705235a270400b2c6 -o /data/local/go
ldcard.img[/COLOR]
/data/local/tmp/goldcard -c 02544d534130324705235a270400b2c6 -o /data/local/gold
card.img
HTC android goldcard tool Copyright (C) 2011, Wayne D. Hoxsie Jr.
Original code by B. Kerler. Special thanks to ATTN1 and the XDA team.
Donations can be made to the Electronic Frontier Foundation:
http://www.eff.org/
or to B. Kerler:
http://psas.revskills.de/
# [COLOR="red"][COLOR="red"]dd if=/data/local/goldcard.img of=/dev/block/mmcblk1[/COLOR][/COLOR]
dd if=/data/local/goldcard.img of=/dev/block/mmcblk1
0+1 records in
0+1 records out
384 bytes transferred in 0.004 secs (96000 bytes/sec)
# [COLOR="red"]exit[/COLOR]
exit
$[COLOR="red"] exit[/COLOR]
exit

c:\miniadb_inspire>[COLOR="red"]adb push misc_version /data/local/tmp[/COLOR]
1434 KB/s (572752 bytes in 0.390s)

c:\miniadb_inspire>[COLOR="red"]adb shell[/COLOR]
$ [COLOR="red"]su[/COLOR]
su
# [COLOR="red"]chmod 775 /data/local/tmp/misc_version[/COLOR]
chmod 775 /data/local/tmp/misc_version
# [COLOR="red"]/data/local/tmp/misc_version -s 1.11.111.1[/COLOR]
/data/local/tmp/misc_version -s 1.11.111.1
--set_version set. VERSION will be changed to: 1.11.111.1
Misc partition is "/dev/block/mmcblk0p17"
Patching and backing up misc partition...
# [COLOR="red"]exit[/COLOR]
exit
$ [COLOR="red"]exit[/COLOR]
exit

c:\miniadb_inspire>[COLOR="red"]adb reboot bootloader[/COLOR]

c:\miniadb_inspire>[COLOR="red"]fastboot devices[/COLOR]
HTxxxxxxxxxx    fastboot

c:\miniadb_inspire>[COLOR="red"]fastboot getvar all[/COLOR]
INFOversion: 0.5
INFOversion-bootloader: 2.00.0030
INFOversion-baseband: 26.17.14.11_M
INFOversion-cpld: None
INFOversion-microp: 0438
INFOversion-main: 1.11.111.1  [COLOR="Blue"]<-this must read 1.11.111.1[/COLOR]
INFOserialno: HTxxxxxxxxxx
INFOimei: xxxxxxxxxxxxxxx
INFOproduct: ace
INFOplatform: HBOOT-7230
INFOmodelid: PD9812000
INFOcidnum: CWS__001  [COLOR="blue"]<-make note of your stock CID[/COLOR]
INFObattery-status: good
INFObattery-voltage: 4201mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 62d2f26e
INFOhbootpreupdate: 11
INFOgencheckpt: 0
INFOregion-id: 0
all: Done!
finished. total time: 0.028s

c:\miniadb_inspire>[COLOR="Red"]fastboot oem lock[/COLOR]
                              ... INFOLock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.154s

[COLOR="Blue"](phone will reboot)[/COLOR]

c:\miniadb_inspire>[COLOR="Red"]adb reboot bootloader[/COLOR]

c:\miniadb_inspire>[COLOR="red"]fastboot oem rebootRUU[/COLOR]
                              ... OKAY [  0.220s]
finished. total time: 0.220s

c:\miniadb_inspire>[COLOR="red"]fastboot flash zip firmware.zip[/COLOR]
      sending 'zip' (18223 KB)... OKAY [  3.049s]
                 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,31
INFO[RUU]UZ,boot,68
INFO[RUU]UZ,boot,99
INFO[RUU]UZ,boot,100
INFO[RUU]WP,boot,0
INFO[RUU]WP,boot,100
INFOstart image[recovery] unzipping & flushing...
INFO[RUU]UZ,recovery,0
INFO[RUU]UZ,recovery,20
INFO[RUU]UZ,recovery,44
INFO[RUU]UZ,recovery,66
INFO[RUU]UZ,recovery,89
INFO[RUU]UZ,recovery,100
INFO[RUU]WP,recovery,0
INFO[RUU]WP,recovery,100
INFOstart image[radio] unzipping & flushing...
INFO[RUU]UZ,radio,0
INFO[RUU]UZ,radio,8
INFO[RUU]UZ,radio,13
INFO[RUU]UZ,radio,20
INFO[RUU]UZ,radio,25
INFO[RUU]UZ,radio,33
INFO[RUU]UZ,radio,41
INFO[RUU]UZ,radio,49
INFO[RUU]UZ,radio,57
INFO[RUU]UZ,radio,62
INFO[RUU]UZ,radio,70
INFO[RUU]UZ,radio,79
INFO[RUU]UZ,radio,86
INFO[RUU]UZ,radio,94
INFO[RUU]UZ,radio,99
INFO[RUU]UZ,radio,100
INFO[RUU]WP,radio,0
INFO[RUU]WP,radio,6
INFO[RUU]WP,radio,14
INFO[RUU]WP,radio,19
INFO[RUU]WP,radio,27
INFO[RUU]WP,radio,36
INFO[RUU]WP,radio,44
INFO[RUU]WP,radio,51
INFO[RUU]WP,radio,59
INFO[RUU]WP,radio,68
INFO[RUU]WP,radio,76
INFO[RUU]WP,radio,85
INFO[RUU]WP,radio,95
INFO[RUU]WP,radio,100
OKAY [ 81.765s]
finished. total time: 84.815s

c:\miniadb_inspire>[COLOR="red"]fastboot reboot-bootloader[/COLOR]
     rebooting into bootloader... OKAY [  0.156s]
finished. total time: 0.157s

c:\miniadb_inspire>[COLOR="red"]fastboot flash unlocktoken Unlock_code.bin[/COLOR]
  sending 'unlocktoken' (0 KB)... OKAY [  0.013s]
         writing 'unlocktoken'... INFOunlock token check successfully
OKAY [  0.009s]
finished. total time: 0.023s

[COLOR="Blue"](phone will try and reboot. unplug,pull battery,enter fastboot via hboot. replug)[/COLOR]

c:\miniadb_inspire>[COLOR="Red"]fastboot flash boot boot.img[/COLOR]
      sending 'boot' (4096 KB)... OKAY [  0.682s]
                writing 'boot'... OKAY [  0.416s]
finished. total time: 1.098s

c:\miniadb_inspire>[COLOR="red"]fastboot flash recovery recovery.img[/COLOR]
  sending 'recovery' (4458 KB)... OKAY [  0.732s]
            writing 'recovery'... OKAY [  0.552s]
finished. total time: 1.285s

c:\miniadb_inspire>[COLOR="red"]fastboot reboot[/COLOR]
                     rebooting...
finished. total time: 0.156s

[COLOR="Blue"](phone will reboot)[/COLOR]

c:\miniadb_inspire>[COLOR="red"]adb reboot recovery[/COLOR]

c:\miniadb_inspire>[COLOR="Red"]adb devices[/COLOR]
List of devices attached
HTxxxxxxxxxx    offline

[COLOR="Blue"]unplug from PC. replug)[/COLOR]

c:\miniadb_inspire>[COLOR="red"]adb devices[/COLOR]
List of devices attached
HTxxxxxxxxxx    recovery


c:\miniadb_inspire>[COLOR="Red"]adb push gfree /tmp/[/COLOR]
2693 KB/s (722728 bytes in 0.262s)

c:\miniadb_inspire>[COLOR="red"]adb shell chmod 775 /tmp/gfree[/COLOR]

c:\miniadb_inspire>[COLOR="red"]adb shell /tmp/gfree -f[/COLOR]
--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: 0x00015398 (86936)
Section index for section name string table: 41
String table offset: 0x000151df (86495)
Searching for .modinfo section...
 - Section[16]: .modinfo
 -- offset: 0x000011cc (4556)
 -- size: 0x000000c4 (196)
Kernel release: 2.6.32.21
New .modinfo section size: 196
Attempting to power cycle eMMC... OK.
Write protect was successfully disabled.
Searching for mmc_blk_issue_rq symbol...
 - Address: c02db21c, type: t, name: mmc_blk_issue_rq, module: N/A
Kernel map base: 0xc02db000
Kernel memory mapped to 0x40002000
Searching for brq filter...
 - Address: 0xc02db21c + 0x34c
 - 0x2a000012 -> 0xea000012
Backing up current partition 7 and patching it...
patching secu_flag: 0
Done.

c:\miniadb_inspire>[COLOR="red"]adb reboot bootloader[/COLOR]

c:\miniadb_inspire>[COLOR="red"]fastboot getvar all[/COLOR]
INFOversion: 0.5
INFOversion-bootloader: 2.00.0030
INFOversion-baseband: 26.03.02.26_M
INFOversion-cpld: None
INFOversion-microp: 0438
INFOversion-main: 1.32.405.6
INFOserialno: HTxxxxxxxxxx
INFOimei: xxxxxxxxxxxxxxx
INFOproduct: ace
INFOplatform: HBOOT-7230
INFOmodelid: PD9812000
INFOcidnum: 11111111  [COLOR="Blue"]<- superCID[/COLOR]
INFObattery-status: good
INFObattery-voltage: 4199mV
INFOpartition-layout: Generic
INFOsecurity: off  [COLOR="blue"]<- s off![/COLOR]
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 62d2f26e
INFOhbootpreupdate: 11
INFOgencheckpt: 0
INFOregion-id: 0
all: Done!
finished. total time: 0.028s

c:\miniadb_inspire>
 
1)download a recovery of choice:
-ext 4: PD98IMG_ace_recovery_ext_4.zip

-twrp: PD98IMG-twrp-ace.zip

-clockwork: cwm-5.0.2.7-ace.zip

2)download radio of choice:
-european wwe unbranded radio(for build 3.12.405.1)
PD98IMG-12.65.60.29_26.14.04.28_M.zip
(the wwe radio is used by ARHD,a popular inspire/DHD rom,and a good all-around choice)

-at&t stock radio(for build 3.20.502.52):
http://www.mediafire.com/?7imx292s8bxrg07



*if you wish to use a different radio,just ask,we can help you :)
____________________________________________________________________________________

these files can be installed as RUUs from fastboot as above,or via hboot by renaming "PD98IMG"

to install as an RUU,place the zip files(do not extract!) into iniadb_inspire folder. open cmd window,change to miniadb_inspire directory. place the phone in fastboot via adb reboot bootloader

files are flashed as downgrade firmware above:
fastboot erase cache

fastboot oem rebootRUU

fastboot flash zip zipname.zip

*reboot RUU mode between each zip file

installing recovery and radio as RUU(red are my inputs):
Code: 
c:\miniadb_inspire>[COLOR="Red"]fastboot erase cache[/COLOR]
               erasing 'cache'... OKAY [  0.377s]
finished. total time: 0.377s

c:\miniadb_inspire>[COLOR="red"]fastboot oem rebootRUU[/COLOR]
                              ... OKAY [  0.151s]
finished. total time: 0.151s

c:\miniadb_inspire>[COLOR="red"]fastboot flash zip PD98IMG_ace_recovery_ext_4.zip[/COLOR]
       sending 'zip' (6071 KB)... OKAY [  1.017s]
                 writing 'zip'... INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOstart image[recovery] unzipping & flushing...
INFO[RUU]UZ,recovery,0
INFO[RUU]UZ,recovery,14
INFO[RUU]UZ,recovery,25
INFO[RUU]UZ,recovery,38
INFO[RUU]UZ,recovery,64
INFO[RUU]UZ,recovery,76
INFO[RUU]UZ,recovery,91
INFO[RUU]UZ,recovery,100
INFO[RUU]WP,recovery,0
INFO[RUU]WP,recovery,100
OKAY [ 11.201s]
finished. total time: 12.219s

c:\miniadb_inspire>[COLOR="red"]fastboot oem rebootRUU[/COLOR]
                              ... OKAY [  0.151s]
finished. total time: 0.152s

c:\miniadb_inspire>fastboot flash zip PD98IMG-12.65.60.29_26.14.04.28_M.zip
      sending 'zip' (11428 KB)... OKAY [  1.942s]
                 writing 'zip'... INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOstart image[radio] unzipping & flushing...
INFO[RUU]UZ,radio,0
INFO[RUU]UZ,radio,8
INFO[RUU]UZ,radio,13
INFO[RUU]UZ,radio,20
INFO[RUU]UZ,radio,25
INFO[RUU]UZ,radio,32
INFO[RUU]UZ,radio,37
INFO[RUU]UZ,radio,45
INFO[RUU]UZ,radio,53
INFO[RUU]UZ,radio,61
INFO[RUU]UZ,radio,69
INFO[RUU]UZ,radio,80
INFO[RUU]UZ,radio,86
INFO[RUU]UZ,radio,94
INFO[RUU]UZ,radio,100
INFO[RUU]WP,radio,0
INFO[RUU]WP,radio,6
INFO[RUU]WP,radio,14
INFO[RUU]WP,radio,19
INFO[RUU]WP,radio,27
INFO[RUU]WP,radio,36
INFO[RUU]WP,radio,44
INFO[RUU]WP,radio,100
OKAY [ 34.397s]
finished. total time: 36.340s

c:\miniadb_inspire>[COLOR="red"]fastboot reboot-bootloader[/COLOR]
     rebooting into bootloader... OKAY [  0.149s]
finished. total time: 0.150s

c:\miniadb_inspire>[COLOR="red"]fastboot reboot[/COLOR]
                     rebooting...
finished. total time: 0.151s

c:\miniadb_inspire>
 
this post can be used to return to s on,and stock CID. in all honesty there is really not much reason to do this. the ACE model is old enuff that there are not likely any left carrying factory warranty. if youre carrying a third party insurance,they could care less if your phone is rooted,rommed,or s off,as long as youve paid your premium ;)

i do know folks like the safety net of being able to get back to stock,so if there is a need,here you go :)

prerequisates:
1)that you know your stock CID,and have an RUU for the build you want to return to
2)that you have adb/fastboot installed and a basic knowledge of entering commands in the cmd window
3)that you are currently rooted,s off,and superCID

failing the second part of #1,i would simply return to unbranded build 3.12.405.1 and a CID of HTC__001

ATT folks can use inspire sense 3.0 build 3.20.502.52 and a CID of CWS__001

other ruus are available here: Shipped ROMs and here: Directory listing of http://androidfiles.org/ruu/Ace and via internet searching


download these files:
-main version low zip from this post place it on your sd card
-back to stock firmware here DO NOT EXTRACT. move to adb/fastboot folder
-ace-tools.zip from here.. extract and move contents to adb/fastboot folder

1)lower your main version
-boot to recovery and flash the main version low zip
-boot to bootloader using a recovery menu option,or power off then on to hboot,select fastboot

2)flash exploitable firmware
-in fastboot:
fastboot erase cache

fastboot oem rebootRUU

fastboot flash zip backtostock-firmware.zip

*when it finishes:

fastboot reboot

*wait for phone to boot and settle.

3)return to stock
adb devices

adb reboot recovery
phone will boot to a black screen

adb devices
(if you get HTxxxxx offline unplug,and replug. repeat )

adb push gfree /tmp/

adb shell chmod 775 /tmp/gfree

adb shell /tmp/gfree -c xxxxxxxx
(where xxxxxxxx is the CID you want to return to)

adb shell /tmp/gfree -s on

adb reboot bootloader

fastboot getvar all
(will confirm s on,and correct CID)

4)run RUU

i personally like to run them from fastboot,as above. but you can run a .exe,or let hboot install from the sd card if you wish.

*note: your bootloader will need to be relocked to run an RUU. if you are still unlocked,relock with this command:
fastboot oem lock

heres what your comd window will look like(red are my inputs,blue are additional notes):
Code: 
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Scott>[COLOR="Red"]cd c:\miniadb_inspire[/COLOR]

c:\miniadb_inspire>[COLOR="red"]adb devices[/COLOR]
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HTxxxxxxxxxx    device


c:\miniadb_inspire>[COLOR="red"]adb reboot bootloader[/COLOR]

c:\miniadb_inspire>[COLOR="red"]fastboot erase cache[/COLOR]
               erasing 'cache'... OKAY [  0.148s]
finished. total time: 0.148s

c:\miniadb_inspire>[COLOR="red"]fastboot oem rebootRUU[/COLOR]
                              ... OKAY [  0.226s]
finished. total time: 0.227s

c:\miniadb_inspire>[COLOR="red"]fastboot flash zip backtostock-firmware.zip[/COLOR]
      sending 'zip' (15830 KB)... OKAY [  2.606s]
                 writing 'zip'... INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOstart image[recovery] unzipping & flushing...
INFO[RUU]UZ,recovery,0
INFO[RUU]UZ,recovery,23
INFO[RUU]UZ,recovery,47
INFO[RUU]UZ,recovery,69
INFO[RUU]UZ,recovery,96
INFO[RUU]UZ,recovery,100
INFO[RUU]WP,recovery,0
INFO[RUU]WP,recovery,100
INFOstart image[radio] unzipping & flushing...
INFO[RUU]UZ,radio,0
INFO[RUU]UZ,radio,8
INFO[RUU]UZ,radio,13
INFO[RUU]UZ,radio,20
INFO[RUU]UZ,radio,25
INFO[RUU]UZ,radio,33
INFO[RUU]UZ,radio,41
INFO[RUU]UZ,radio,49
INFO[RUU]UZ,radio,57
INFO[RUU]UZ,radio,66
INFO[RUU]UZ,radio,74
INFO[RUU]UZ,radio,80
INFO[RUU]UZ,radio,86
INFO[RUU]UZ,radio,94
INFO[RUU]UZ,radio,99
INFO[RUU]UZ,radio,100
INFO[RUU]WP,radio,0
INFO[RUU]WP,radio,6
INFO[RUU]WP,radio,14
INFO[RUU]WP,radio,19
INFO[RUU]WP,radio,27
INFO[RUU]WP,radio,36
INFO[RUU]WP,radio,44
INFO[RUU]WP,radio,100
OKAY [ 35.514s]
finished. total time: 38.121s

c:\miniadb_inspire>[COLOR="red"]fastboot reboot[/COLOR]
                     rebooting...
finished. total time: 0.154s

c:\miniadb_inspire>[COLOR="red"]adb devices[/COLOR]
List of devices attached
HTxxxxxxxxxx    device


c:\miniadb_inspire>[COLOR="red"]adb reboot recovery[/COLOR]

c:\miniadb_inspire>[COLOR="red"]adb devices[/COLOR]
List of devices attached
HTxxxxxxxxxx    offline

[COLOR="Blue"](unplug from PC,replug)[/COLOR]

c:\miniadb_inspire>[COLOR="red"]adb devices[/COLOR]
List of devices attached
HTxxxxxxxxxx    recovery


c:\miniadb_inspire>[COLOR="Red"]adb push gfree /tmp/[/COLOR]
2683 KB/s (722728 bytes in 0.263s)

c:\miniadb_inspire>[COLOR="red"]adb shell chmod 775 /tmp/gfree[/COLOR]

c:\miniadb_inspire>[COLOR="red"]adb shell /tmp/gfree -c CWS__001[/COLOR]
--cid set. CID will be changed to: CWS__001
Section header entry size: 40
Number of section headers: 44
Total section header table size: 1760
Section header file offset: 0x00015398 (86936)
Section index for section name string table: 41
String table offset: 0x000151df (86495)
Searching for .modinfo section...
 - Section[16]: .modinfo
 -- offset: 0x000011cc (4556)
 -- size: 0x000000c4 (196)
Kernel release: 2.6.32.21
New .modinfo section size: 196
Attempting to power cycle eMMC... OK.
Write protect was successfully disabled.
Searching for mmc_blk_issue_rq symbol...
 - Address: c02db21c, type: t, name: mmc_blk_issue_rq, module: N/A
Kernel map base: 0xc02db000
Kernel memory mapped to 0x40002000
Searching for brq filter...
 - Address: 0xc02db21c + 0x34c
 - 0x2a000012 -> 0xea000012
Backing up current partition 7 and patching it...
Done.

c:\miniadb_inspire>[COLOR="red"]adb shell /tmp/gfree -s on[/COLOR]
--secu_flag on set
Section header entry size: 40
Number of section headers: 44
Total section header table size: 1760
Section header file offset: 0x00015398 (86936)
Section index for section name string table: 41
String table offset: 0x000151df (86495)
Searching for .modinfo section...
 - Section[16]: .modinfo
 -- offset: 0x000011cc (4556)
 -- size: 0x000000c4 (196)
Kernel release: 2.6.32.21
New .modinfo section size: 196
Attempting to power cycle eMMC... OK.
Module did not power-cycle eMMC, write-protect already off.
Searching for mmc_blk_issue_rq symbol...
 - Address: c02db21c, type: t, name: mmc_blk_issue_rq, module: N/A
Kernel map base: 0xc02db000
Kernel memory mapped to 0x40002000
Searching for brq filter...
 - Address: 0xc02db21c + 0x34c
 - ***WARNING***: Found fuzzy match for brq filter, but conditional branch isn't
. (0xea000012)
Backing up current partition 7 and patching it...
patching secu_flag: 1
Done.

c:\miniadb_inspire>[COLOR="red"]adb reboot bootloader[/COLOR]

c:\miniadb_inspire>[COLOR="red"]fastboot getvar all[/COLOR]
INFOversion: 0.5
INFOversion-bootloader: 2.00.0030
INFOversion-baseband: 26.03.02.26_M
INFOversion-cpld: None
INFOversion-microp: 0438
INFOversion-main: 1.32.405.6
INFOserialno: HTxxxxxxxxxx
INFOimei: xxxxxxxxxxxxxxx
INFOproduct: ace
INFOplatform: HBOOT-7230
INFOmodelid: PD9812000
INFOcidnum: CWS__001 [COLOR="Blue"]<- stock CID[/COLOR]
INFObattery-status: good
INFObattery-voltage: 4199mV
INFOpartition-layout: Generic
INFOsecurity: on  [COLOR="blue"]<- s on[/COLOR]
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 62d2f26e
INFOhbootpreupdate: 11
INFOgencheckpt: 0
INFOregion-id: 0
all: Done!
finished. total time: 0.025s

c:\miniadb_inspire>[COLOR="Red"]fastboot oem lock[/COLOR]
                              ... INFOLock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.223s

[COLOR="Blue"](phone will reboot)[/COLOR]

c:\miniadb_inspire>[COLOR="Red"]adb reboot bootloader[/COLOR]

c:\miniadb_inspire>[COLOR="red"]fastboot erase cache[/COLOR]
               erasing 'cache'... OKAY [  0.165s]
finished. total time: 0.165s

c:\miniadb_inspire>[COLOR="red"]fastboot oem rebootRUU[/COLOR]
                              ... OKAY [  0.151s]
finished. total time: 0.151s

c:\miniadb_inspire>[COLOR="red"]fastboot flash zip htc_inspire4g_att_RUU_3.20.502.52_US.zip[/COLOR]
     sending 'zip' (350966 KB)... OKAY [ 58.166s]
                 writing 'zip'... INFOadopting the signature contained in this
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] unzipping & flushing...
INFO[RUU]UZ,hboot,0
INFO[RUU]UZ,hboot,100
INFO[RUU]WP,hboot,0
INFO[RUU]WP,hboot,100
INFOstart image[boot] unzipping & flushing...
INFO[RUU]UZ,boot,0
INFO[RUU]UZ,boot,33
INFO[RUU]UZ,boot,72
INFO[RUU]UZ,boot,100
INFO[RUU]WP,boot,0
INFO[RUU]WP,boot,100
INFOstart image[recovery] unzipping & flushing...
INFO[RUU]UZ,recovery,0
INFO[RUU]UZ,recovery,23
INFO[RUU]UZ,recovery,44
INFO[RUU]UZ,recovery,78
INFO[RUU]UZ,recovery,100
INFO[RUU]WP,recovery,0
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,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,37
INFO[RUU]UZ,system,43
INFO[RUU]UZ,system,48
INFO[RUU]UZ,system,50
INFO[RUU]UZ,system,54
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,30
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,50
INFO[RUU]WP,system,54
INFO[RUU]UZ,system,54
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,77
INFO[RUU]UZ,system,79
INFO[RUU]UZ,system,82
INFO[RUU]UZ,system,86
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,54
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,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,5
INFO[RUU]UZ,lib,10
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,69
INFO[RUU]UZ,lib,78
INFO[RUU]UZ,lib,85
INFO[RUU]UZ,lib,93
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[sp2] unzipping & flushing...
INFO[RUU]UZ,sp2,0
INFO[RUU]UZ,sp2,100
INFO[RUU]WP,sp2,0
INFO[RUU]WP,sp2,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[tp] unzipping & flushing...
INFO[RUU]UZ,tp,0
INFO[RUU]UZ,tp,100
INFOstart image[tp] unzipping & flushing...
INFO[RUU]UZ,tp,0
INFO[RUU]UZ,tp,100
INFOstart image[tp] unzipping & flushing...
INFO[RUU]UZ,tp,0
INFO[RUU]UZ,tp,100
INFOstart image[tp] unzipping & flushing...
INFO[RUU]UZ,tp,0
INFO[RUU]UZ,tp,100
INFO[RUU]WP,tp,0
INFOstart image[radio] unzipping & flushing...
INFO[RUU]UZ,radio,0
INFO[RUU]UZ,radio,8
INFO[RUU]UZ,radio,14
INFO[RUU]UZ,radio,20
INFO[RUU]UZ,radio,25
INFO[RUU]UZ,radio,32
INFO[RUU]UZ,radio,37
INFO[RUU]UZ,radio,45
INFO[RUU]UZ,radio,53
INFO[RUU]UZ,radio,61
INFO[RUU]UZ,radio,69
INFO[RUU]UZ,radio,79
INFO[RUU]UZ,radio,86
INFO[RUU]UZ,radio,94
INFO[RUU]UZ,radio,100
INFO[RUU]WP,radio,0
INFO[RUU]WP,radio,6
INFO[RUU]WP,radio,14
INFO[RUU]WP,radio,19
INFO[RUU]WP,radio,27
INFO[RUU]WP,radio,36
INFO[RUU]WP,radio,44
INFO[RUU]WP,radio,51
INFO[RUU]WP,radio,59
INFO[RUU]WP,radio,68
INFO[RUU]WP,radio,76
INFO[RUU]WP,radio,85
INFO[RUU]WP,radio,95
INFO[RUU]WP,radio,100
INFOstart image[rcdata] unzipping & flushing...
INFO[RUU]UZ,rcdata,0
INFO[RUU]WP,rcdata,0
INFO[RUU]WP,rcdata,100
OKAY [226.301s]
finished. total time: 284.467s

c:\miniadb_inspire>[COLOR="red"]fastboot reboot-bootloader[/COLOR]
     rebooting into bootloader... OKAY [  0.155s]
finished. total time: 0.155s

c:\miniadb_inspire>[COLOR="red"]fastboot reboot[/COLOR]
                     rebooting...
finished. total time: 0.152s

c:\miniadb_inspire>
 
Worked! Thank you Scotty

I kept on getting an error message when I was trying to re-unlock my bootloader after the DUU step, but i fixed it by re-generating my identifier token, sending it off to HTC again, then using the new Unlock_code.bin file they sent me. I can't see how it would be different to the original one they sent, but it worked!
 
awsome! glad it worked for you. not sure either why you needed a new identifier token and unlock code. ive run thru this 4 or 5 times now(or more :eek:) and used the same token every time. glad the issue you encountered had a pretty easy fix :)
 
agree with everyone else, very easy to follow one of the simplest guide out there. Props to you!

is flashing the radio required? i did not



totally unrelated but also after flashing a rom (cm10.1 nightlies)noticing significant battery drain and lag in the system when i try to navigate around

are there htc sense for JB now?
 
flashing the radio is not really required,but id pretty strongly recomend it. the one that the downgrade firmware installs is many versions of android old,and while it may not casue obvious issues,newer is better,and will most likely give you better performance in stronger signal,more stable data,etc. :)

as for JB sense,not sure on that one. last time i looked at DHD roms,there was sense ICS,but not sure about JB. ral is the resident rom expert,might put up a post in the main forum,and he will undoubtedly answer you :)
 
thanks SCotty, should i go ahead and follow the above steps to flash the radio now that im running JB rom? pretty sure it's ok but just wanted to double check before i do it so i dont mess anything up
 
623baller said:
thanks SCotty, should i go ahead and follow the above steps to flash the radio now that im running JB rom? pretty sure it's ok but just wanted to double check before i do it so i dont mess anything up
Click to expand...
Yup! Changing the radio while on a custom Rom won't hurt a thing :)
 
just to contribute to the threads a bit

i was running stock radio, but custom rom (Cm10.1 nightlies 2013-03-30)

after i flashed the radios on the top, it stuck on boot screen forever without progressing

after digging through some threads and google, many suggested to wipe cache before loading the radio.

i wiped cache and upon reboot , the phone started updating applications to adapt to the new radios without having to reflash

it does seem im getting better reception but time will tell
 
AWESOME!!! Worked like a charm, just took my time and stayed patient... i forgot to flash the recovery.img at first and almost had a mental melt down =P but i just slowed down and went step by step SLOWLY!!! reading all the outputs, and BAM s-off achieved and phone working on Cellular One network now. THANK YOU SO MUCH GUYS!!!! Great guide very simple once i slowed down and actually read every word =D
 
Worked great thanks...first time applying root and s-off to anything. Did lots of reading and took my time.

So now i have radio s-off and was wondering about the two pseudo eng s-off hboots that are included in the toolkit. My phone was shipped with Froyo long time ago but it took the OTA Telus update to Gingerbread 2.3.5 (with the new lib partition) and was hboot 2.00.0027 and rom 3.13.661.4 before i started messing with it.

Now I am hboot 2.00.0029 (required to do the HTCdev unlock) and running Unofficial Cyanogen 10.1 rom by Mustaavalkosta. I am interested in flashing one of the Hyuh hboots from the toolkit but don't know which one to use (I am guessing the later 2.00.2728 one for sense 3 roms). I don't want to screw anything up so I thought I would check here first.

Thanks,
stnky1
 
glad it went well for you. your instincts are correct,if you had a 2.00.00xx hboot prior to htcdev,then youll want to use the 2.00.2728 hboot.

i flashed it awhile back,i didnt test too many things,but it should allow you to fastboot boot and fastboot flash all partitions,so be careful.

the htcdev unlocked hboot is allowing fastboot boot/flash of boot/system/recovery,wich is prolly adequate for most folks. radios,splash image,and other hboots are easily flashed without the eng hboot as PD98IMG files in hboot or from fastboot,so you can get along fine without it... its really a matter of personal preference.

visually,it will say **AAHK** where your current one says **unlocked** :cool:

just holler if you have further questions :)
 
Thanks Scotty for the super fast response.

Reason I am interested is because I saved a nandroid of my original rom before I flashed anything but that was with an old version of 4ext (before I or it knew about the lib.img and the separate partition). Now when I try to restore it I am getting stuck in a boot loop.

I soon figured out it was due to the missing partition and lib.img. I can add the partition easily enough now with the latest version of 4ext. So I found a copy of the original complete rom and was able to extract the lib.img file from it and now I want to apply it to see if I can get my old backup working again. When I try to do "fastboot flash lib lib.img" it won't let me of course with just radio s-off.

The other option might be to save the lib.img along with the andriod-info.txt into a PD98IMG.zip file and install it directly through hboot but I have seached high and low on the net and have never heard of anyone trying it so I don't want to use my phone as a guinea pig (but that would save me having to replace the hboot).

Any thoughts on the better/safer approach?
stnky1
 
What was your original Rom? If you were on hboot 2.00.0027 when this nandroid was made,I would think it should restore just fine with hboot 2.00.0029 as well,but maybe not... With radio s off it would definately be easy enuff to install your original hboot,or hyuhs newer patched hboot. I didn't really mean to discourage you from trying hyuhs hboot,especially since you seem to have a good grasp on what you're doing. Just make sure to verify md5 sum and changing hboots can easily be done safely.

I can't think of any reason that pcking up the lib image with a text document would be a bad idea,but I've not done that,so I couldn't say for sure... Did you pull this image from an ruu? If so,running that ruu would be a good option. That would restore matching hboot,radio,lib,etc. Then you'd just need to install recovery,restore nandroid :)

Have you perchance tried restoring the backup,then wiping cache and dalvik again prior to rebooting?
 
Hi Scotty:

Original rom was as stated in post #18 above, Telus Gingerbread 2.3.5 v3.13.661.4. Sorry I failed to mention that it was the rooted rom that I took the nandroid of (with all my apps and settings of course). I don't care about returning to original (I never will) so I am not interested in going back to a completely stock RUU but I wouldn't mind getting into my backup if I need to to find something I missed.

The rom I found is a stock but rooted Telus RUU that matches my old one. I found it in the Inspire 4G section of another site (make a guess...) as a .zip file. I don't know if attaching links is against the rules here so I won't do it.

I know the Telus Gingerbread roms did use the system/lib partition and lib.img so I am guessing that is what is holding me back, especially since I was using 4ext version 1.0.0.5 RC5 which is before that extra partition was supported (I am on the latest v1.0.0.5 RC8 now). This is from the 4ext site changelog:

"Desire S, Incredible S, Incredible 2, Desire HD: depending on which hboot 2.x was installed, detection of the new "lib" partition could fail. You need at least 4EXT Recovery v1.0.0.5 RC7!"

I always do wipe data/factory reset and wipe cache + dalvik before I restore the rom but never after. So I just tried it and unfortunately it is still giving me boot loop.

Maybe I will be brave and try the lib.img as a PD98IMG.zip in hboot. What's the worst that could happen? :)

stnky1
 
Well,your phone could melt Into a smoldering pile of goo? :eek:

Prolly not tho... That partition should be pretty harmless. I think the worse case is the phone won't let you flash it. Or maybe it flashes,but nothing changes.

Have you allready tried installing your stock or the patched hboot to see if it will install that partition and let your nandroid restore? May take a reboot between the hboot and nand restore for it to work.
 
Another option may be this,since the nandroid was taken with an old version of ext 4:
-install proper hboot
-flash the .zip file you found
-restore the data portion of your nandroid
 
You must log in or register to reply here.
Back
Top Bottom