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

Root Boot loop after rooting DHD 2.3.3

Hi Scotty,
Had something good to hear about. The phone is up and running with software number 1.32.405.6 (Hence hoping it to be downgraded).
Can I proceed with step 6??

Is still the goldcard required for the further procedure??

Thanks & Regards,
Sagar.
 
Hi Scotty,

I have completed the step 6 and downloaded the cwm and superuser zipfiles, how do I install them.. ?
Also please let me know, how I need to install the required ROM (eg: Jellytime)

Thanks and regards,
Sagar.
 
Excellent! I'm very glad to.hear it. Especially since it was not booting this morning. Have you allready upgraded your firmware? I can give more details on the recovery and Rom install later this evening
 
Nope .. I haven't upgraded the firmware yet. It is still running the build number - 1.32.405.6.
Can you please guide me regarding the upgradation of firmware and clockworkmod (ROM as well).

Thanks and regards,
Sagar.
 
ksagar04 said:
Nope .. I haven't upgraded the firmware yet. It is still running the build number - 1.32.405.6.
Can you please guide me regarding the upgradation of firmware and clockworkmod (ROM as well).

Thanks and regards,
Sagar.
Click to expand...

first... what did you do and the phone started working?


second,just to confirm,you had no errors from running gfree,and the getvar all confirmed you to have s-off,and superCID?

if thats the case,then you dont need your gold cards any more! :smokingsomb:

since this is old firmware,you will want to upgrade to something newer,to have stronger and more stable phone aNd data signals. you technically could install new radio and hboot,but i personally prefer to run whole ruus just to make sure everything matches.

if the phone is still to be used on att,what i would recomend is this:
1)re-run the ruu for att 2.47.605.7. those radios are prolly best suited for that network. do not fear,radio s-off remains no matter what you do,so you wont have to do all this complicated stuff again. after it flashes,let it boot and settle a few minutes.

2)install the recovery. you can install as a PD98IMG in hboot,or you can install from the cmd window,just as you did the other firmware. its up to you,wichever you find easier.

you might consider using ext4 recovery instead,most of us somewhat prefer it. it has a nice touch screen ui and is easy to use.

http://www.mediafire.com/?titr0gqhvb38p8m
md5: PD98IMG_ace_recovery_ext_4.zip fc0f377f7d91ce5dc1f415f7bc72284d

3) boot to recovery and make a backup of the stock,unrooted rom. never know when you may need it. :)

4)if you wish to root the stock software,you can flash the superuser file you downloaded. if you want to immediately falsh a rom,that ok too.

if you want to falsh a rom,download it,place it on the root of your sd. boot to recovery.
-wipe data/factory reset
-wipe cache
-wipe dalvik cache

then flash the rom. jellytime is an AOSP rom,so you will need to flash gapps as well,simply flash the rom,flash gapps right after.

reboot. enjoy :D

these are generalized steps,so just holler if you have questions on any part of that. :)
 
Hi Scotty,

1. I just kept the powered ON for a few minutes (approx 10min). It got started up slowly and then booted in.

2. I hope there were no errors thrown from running gfree,and the getvar all. I am posting the executed steps, to have a better idea.

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


C:\>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT19NT213520 device


C:\>adb devices
List of devices attached
HT19NT213520 device


C:\>cd c:\mini-adb_inspire


c:\mini-adb_inspire>adb push psneuter /data/local/
1776 KB/s (585731 bytes in 0.322s)

c:\mini-adb_inspire>adb push busybox /data/local/
1587 KB/s (1062992 bytes in 0.654s)

c:\mini-adb_inspire>adb push wpthis /data/local/
1451 KB/s (679475 bytes in 0.457s)

c:\mini-adb_inspire>adb push gfree /data/local/
1339 KB/s (134401 bytes in 0.098s)

c:\mini-adb_inspire>adb shell
$ chmod 0755 /data/local/psneuter
chmod 0755 /data/local/psneuter
$ chmod 0755 /data/local/wpthis
chmod 0755 /data/local/wpthis
$ chmod 0755 /data/local/gfree
chmod 0755 /data/local/gfree
$ /data/local/psneuter
/data/local/psneuter
property service neutered.
killing adbd. (should restart in a second or two)

c:\mini-adb_inspire>adb shell
# /data/local/wpthis
/data/local/wpthis
Build: 25
Section header entry size: 40
Number of section headers: 45
Total section header table size: 1800
Section header file offset: 0x00014e90 (85648)
Section index for section name string table: 42
String table offset: 0x00014cc7 (85191)
Searching for .modinfo section...
- Section[16]: .modinfo
-- offset: 0x00000f80 (3968)
-- size: 0x000000c4 (196)
Kernel release: 2.6.32.21-gf3f553d
New .modinfo section size: 204
Loading module... OK.
Write protect disabled.
Searching for mmc_blk_issue_rq symbol...
- Address: c02a9e00, type: t, name: mmc_blk_issue_rq, module: N/A
Kernel map base: 0xc02a9000
Kernel memory mapped to 0x40001000
Searching for brq filter...
- Address: 0xc02a9e00 + 0x34c
- 0x2a000012 -> 0xea000012
Done.
# /data/local/gfree -f
/data/local/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: 0x000138b4 (80052)
Section index for section name string table: 41
String table offset: 0x000136fb (79611)
Searching for .modinfo section...
- Section[16]: .modinfo
-- offset: 0x00000a14 (2580)
-- size: 0x000000cc (204)
Kernel release: 2.6.32.21-gf3f553d
New .modinfo section size: 204
Attempting to power cycle eMMC... OK.
Searching for mmc_blk_issue_rq symbol...
- Address: c02a9e00, type: t, name: mmc_blk_issue_rq, module: N/A
Kernel map base: 0xc02a9000
Kernel memory mapped to 0x40000000
Searching for brq filter...
- Address: 0xc02a9e00 + 0x34c
- ***WARNING***: Found fuzzy match for brq filter, but conditional branch isn't
. (0xea000012)
Patching and backing up partition 7...
patching secu_flag: 0
Done.
# exit
exit

c:\mini-adb_inspire>adb reboot bootloader

c:\mini-adb_inspire>fastboot getvar all
< waiting for device >
INFOversion: 0.5
INFOversion-bootloader: 0.85.0007
INFOversion-baseband: 26.03.02.26_M
INFOversion-cpld: None
INFOversion-microp: 0438
INFOversion-main: 1.32.405.6
INFOserialno: HT19NT213520
INFOimei: 358920043212536
INFOproduct: ace
INFOplatform: HBOOT-7230
INFOmodelid: PD9812000
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 4182mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-7eafc656
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.158s

c:\mini-adb_inspire>fastboot reboot
rebooting...
finished. total time: 0.550s

c:\mini-adb_inspire>
--------------------------------------------


3. The phone will no longer be running on AT&T. so should I do this step any ways.. ?

( if the phone is still to be used on att,what i would recomend is this:
1)re-run the ruu for att 2.47.605.7. those radios are prolly best suited for that network. do not fear,radio s-off remains no matter what you do,so you wont have to do all this complicated stuff again. after it flashes,let it boot and settle a few minutes.)

Thanks and regards,
Sagar
 
Hi Scotty,
Also the boot loader is not opening when volume down+power keys are pressed.
(Through cmd I am unable to enter it, but it is taking around 5 min)
So can you please list me a set of commands in cmd, hence I can execute the
1.Superuser-3.0.7-efgh-signed
2.cwm-5.0.2.7-ace
3.PD98IMG_ace_recovery_ext 4
4.cm-JellyTime_R4
5.gapps-jb-20120726-signed.

Thanks and regards,
Sagar.
 
Hope, If I can first install the 4EXT, for rest of them I shall be able use the phone instead of proceeding through cmd window prompt.

Thanks and regards,
Sagar.
 
ksagar04 said:
Hi Scotty,

1. I just kept the powered ON for a few minutes (approx 10min). It got started up slowly and then booted in.

2. I hope there were no errors thrown from running gfree,and the getvar all. I am posting the executed steps, to have a better idea.

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


C:\>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT19NT213520 device


C:\>adb devices
List of devices attached
HT19NT213520 device


C:\>cd c:\mini-adb_inspire


c:\mini-adb_inspire>adb push psneuter /data/local/
1776 KB/s (585731 bytes in 0.322s)

c:\mini-adb_inspire>adb push busybox /data/local/
1587 KB/s (1062992 bytes in 0.654s)

c:\mini-adb_inspire>adb push wpthis /data/local/
1451 KB/s (679475 bytes in 0.457s)

c:\mini-adb_inspire>adb push gfree /data/local/
1339 KB/s (134401 bytes in 0.098s)

c:\mini-adb_inspire>adb shell
$ chmod 0755 /data/local/psneuter
chmod 0755 /data/local/psneuter
$ chmod 0755 /data/local/wpthis
chmod 0755 /data/local/wpthis
$ chmod 0755 /data/local/gfree
chmod 0755 /data/local/gfree
$ /data/local/psneuter
/data/local/psneuter
property service neutered.
killing adbd. (should restart in a second or two)

c:\mini-adb_inspire>adb shell
# /data/local/wpthis
/data/local/wpthis
Build: 25
Section header entry size: 40
Number of section headers: 45
Total section header table size: 1800
Section header file offset: 0x00014e90 (85648)
Section index for section name string table: 42
String table offset: 0x00014cc7 (85191)
Searching for .modinfo section...
- Section[16]: .modinfo
-- offset: 0x00000f80 (3968)
-- size: 0x000000c4 (196)
Kernel release: 2.6.32.21-gf3f553d
New .modinfo section size: 204
Loading module... OK.
Write protect disabled.
Searching for mmc_blk_issue_rq symbol...
- Address: c02a9e00, type: t, name: mmc_blk_issue_rq, module: N/A
Kernel map base: 0xc02a9000
Kernel memory mapped to 0x40001000
Searching for brq filter...
- Address: 0xc02a9e00 + 0x34c
- 0x2a000012 -> 0xea000012
Done.
# /data/local/gfree -f
/data/local/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: 0x000138b4 (80052)
Section index for section name string table: 41
String table offset: 0x000136fb (79611)
Searching for .modinfo section...
- Section[16]: .modinfo
-- offset: 0x00000a14 (2580)
-- size: 0x000000cc (204)
Kernel release: 2.6.32.21-gf3f553d
New .modinfo section size: 204
Attempting to power cycle eMMC... OK.
Searching for mmc_blk_issue_rq symbol...
- Address: c02a9e00, type: t, name: mmc_blk_issue_rq, module: N/A
Kernel map base: 0xc02a9000
Kernel memory mapped to 0x40000000
Searching for brq filter...
- Address: 0xc02a9e00 + 0x34c
- ***WARNING***: Found fuzzy match for brq filter, but conditional branch isn't
. (0xea000012)
Patching and backing up partition 7...
patching secu_flag: 0
Done.
# exit
exit

c:\mini-adb_inspire>adb reboot bootloader

c:\mini-adb_inspire>fastboot getvar all
< waiting for device >
INFOversion: 0.5
INFOversion-bootloader: 0.85.0007
INFOversion-baseband: 26.03.02.26_M
INFOversion-cpld: None
INFOversion-microp: 0438
INFOversion-main: 1.32.405.6
INFOserialno: HT19NT213520
INFOimei: 358920043212536
INFOproduct: ace
INFOplatform: HBOOT-7230
INFOmodelid: PD9812000
INFOcidnum: 11111111 <-superCID
INFObattery-status: good
INFObattery-voltage: 4182mV
INFOpartition-layout: Generic
INFOsecurity: off <- s-off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-7eafc656
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.158s

c:\mini-adb_inspire>fastboot reboot
rebooting...
finished. total time: 0.550s

c:\mini-adb_inspire>
--------------------------------------------


3. The phone will no longer be running on AT&T. so should I do this step any ways.. ?

( if the phone is still to be used on att,what i would recomend is this:
1)re-run the ruu for att 2.47.605.7. those radios are prolly best suited for that network. do not fear,radio s-off remains no matter what you do,so you wont have to do all this complicated stuff again. after it flashes,let it boot and settle a few minutes.)

Thanks and regards,
Sagar
Click to expand...

yup,that all looks good. you are supercided and s-offed :cool:

if youre not going to use it on att,then making the att backup would be optional. you still should run a newer RUU to get an updated radio and hboot. if you do not want to use the att radio,you may want to run this ruu:

Shipped ROMs

that is an .exe file that you will run,either withthe phone in the booted OS,or in fastboot mode. im in the process of uploading a PD98IMG if the ruu doesnt execute

ksagar04 said:
Hi Scotty,
Also the boot loader is not opening when volume down+power keys are pressed.
(Through cmd I am unable to enter it, but it is taking around 5 min)
So can you please list me a set of commands in cmd, hence I can execute the
1.Superuser-3.0.7-efgh-signed
2.cwm-5.0.2.7-ace
3.PD98IMG_ace_recovery_ext 4
4.cm-JellyTime_R4
5.gapps-jb-20120726-signed.

Thanks and regards,
Sagar.
Click to expand...
there is a setting in applications called "fastboot" make sure you uncheck that,and you will be able to get to hboot via vol down/power.

you can also entere hboot by:
adb reboot bootloader in the booted OS
then push power to select bootloader

1 and 2 you do not need if youre going to install ext 4 recovery and jelly bean rom.

3 you do by rename PD98IMG and install in hboot,or via the cmd as you did the other RUUs:
-place inside mini-adb_inspire folder

use thses commands:
fastboot erase cache

fastboot oem rebootRUU

fsatboot flash zip zipname.zip

fastboot reboot-bootloader

fastboot reboot


4 and 5 you will do using the recoverys menu options on the phone itself

ksagar04 said:
Hope, If I can first install the 4EXT, for rest of them I shall be able use the phone instead of proceeding through cmd window prompt.

Thanks and regards,
Sagar.
Click to expand...

correct. once you update to newer firmware,and install ext 4 recovery,you will not need the cmd prompt
 
Some really amazing work you and scotty85 have been doing here. Let me catch up on this thread after I get home from work and see if I can contribute anything.

scotty85 is one of the heavy hitters here, but sometimes the lesser mortals can provide some help too.
 
Thanks for sending the 4EXT link Scotty
I have tried flashing the RUU you sent:

C:\rooting>fastboot oem rebootRUU
... OKAY [ 0.206s]
finished. total time: 0.206s
C:\rooting>fastboot flash zip RUU_Ace_sense30.zip
< waiting for device >
sending 'zip' (342262 KB)... OKAY [ 61.488s]
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 4104.003s


The link you sent for the RUU isn't probably working. Can you please upload the PD98IMG for that.

Also I have small query here. Do I need to flash this RUU first before I would flash the jellytime or else can I directly flash the Jellytime and googleapps (after I install the 4EXT)
Thanks and regards,
Sagar
 
Hi Scotty,

The Bootloader is very very slow, don't know the reason behind it. Its taking a lot of time to execute even a small file (4EXT).
Can you help me regarding this. Even it is taking a lot of time to boot up as well, inactive volume and power buttons.(can only communicate via cmd, but even that it is taking a lot much time).In setting -> applications -> "fastboot" was made uncheck, still I am facing the issue .This was the same problem from the moment I have downgraded it to 1.32.405.6. Hope something went wrong during the downgrade.

Thanks and regards,
Sagar.
 
Sagar - I am sure that Scotty will reply once he's up and about (he is in the USA though, so may not be straight away)... I will also have a proper look and see if I can give more help when I get home (in work at the moment and can't really check on here so much) :)
 
ksagar04 said:
Thanks for sending the 4EXT link Scotty
I have tried flashing the RUU you sent:

C:\rooting>fastboot oem rebootRUU
... OKAY [ 0.206s]
finished. total time: 0.206s
C:\rooting>fastboot flash zip RUU_Ace_sense30.zip
< waiting for device >
sending 'zip' (342262 KB)... OKAY [ 61.488s]
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 4104.003s


The link you sent for the RUU isn't probably working. Can you please upload the PD98IMG for that.

Also I have small query here. Do I need to flash this RUU first before I would flash the jellytime or else can I directly flash the Jellytime and googleapps (after I install the 4EXT)
Thanks and regards,
Sagar
Click to expand...

you had trouble flashing the ruu because you cant flash it that way ;) as i said above that link was a .exe file that you run on the PC from fastbot,or the booted OS

i would pretty strogly recomend to falsh the ruu prior to installing a recovery and rom,mainly becasue the ruu will overwrite them. once youve installed the rom and recovery,you wont want to run the ruu,and its defiantely to your advantage to install something newer

ksagar04 said:
Hi Scotty,

The Bootloader is very very slow, don't know the reason behind it. Its taking a lot of time to execute even a small file (4EXT).
Can you help me regarding this. Even it is taking a lot of time to boot up as well, inactive volume and power buttons.(can only communicate via cmd, but even that it is taking a lot much time).In setting -> applications -> "fastboot" was made uncheck, still I am facing the issue .This was the same problem from the moment I have downgraded it to 1.32.405.6. Hope something went wrong during the downgrade.

Thanks and regards,
Sagar.
Click to expand...

since you uncheck the "fastboot" setting,that should have let you get to hboot via power/vol down. hold vol down slightly first,then power,then keep holding both until hboot comes up. since it takes awhile to get there even thru cmd,maybe you just have to hold the buttons for a long time.

since youre having prollems with the WWE rom,maybe it is best that you install the ATT ruu instead of the one i recomended a couple posts up. maybe the phone will be happier with the firmware that came on it.

if you need the att links again,here is the .zip:
Shipped ROMs
(run in hboot from sd,or from cmd window)

here is the .exe:
Shipped ROMs
(run on pc with phone in fastboot or booted OS)

once you get that flashed,let the phone boot and settle for a few minutes. then do a "factory data reset" in settings/SD & phone storage. hopefully that will clear some things out of the dark corners of the phones file system and speed things up a lil :)

after its done wth the reset,you can install the recovery and rom :)
 
@ksagar04

Just got back home (long day) Awaiting update on your status. Will be online for a hour or so, and will be back online in 5-6 hours (sleep).

Catching up on the thread. Amazed at what you guys have covered. This is the most amazing piece of tech support I have ever seen. Whether from in-house IT, online, from a customer service center, in a forum. I am speechless.

@scotty85

What can I say? Awesome does not cover it.
 
Hi Guys,

First of all, a lot many thanks to all you guys, especially a hats-off to Scotty, without whom I wouldn't have moved further. And not to forget DURX,EL-PRESIDENTE, RAL, you guys do a great work here. I am really thankful for your help and I am really satisfied with your approach and very grateful to this forum.
I got a lot to learn. And thanks for your patience Scotty :) :)

After a lot from your help, I have flashed the ATT RUU and the phone too got faster in booting than previously when it was quite slow after the downgrade. Now I have to flash the jellytime.
I will still be updating further steps :) :)

Thanks and regards,
Sagar.
 
Well I really did not do anything. Do you need a step-by-step on how to flash?

@scotty85

Congratulations.
 
Yep, Ral
U may have not contributed yet in this thread, but I have gone through your few forums. Keep up the good energy in you :) :)
U are doing a good work in this thread :) :)

Regards,
Sagar :)
 
  • Like
Reactions: ral
Okay. First, lets back-up your current ROM. Go into recovery, select back-up/restore and than select back-up. Your phone should create a back-up. In case something goes wrong with the flash, you can reinstall the backed-up ROM and get a functional phone back.

Download ROM. Check the md5sum.
Download Google Apps for Jelly Bean. Check the md5sum.

Link to thread with link to files.

Transfer both files to your SD card (not in a folder) and check the md5sums again.

Make sure your phone has enough power to complete the procedure (most guides say at least 70%).

After that go back into recovery and select Wipe/Format and than do the following:

--- wipe data/factory reset
--- wipe cache/dalvik
--- format all partitions other (except sdcard) === Some may say this step is not necessary.

Click back and select ---> install from SD card ---> choose zip from sdcard ---> find the zip file of the ROM you downloaded and select.

Follow any on screen instructions (sorry never flashed Jellytime).

Repeat the procedure and flash the zip file for Google apps.

When done.. reboot.

Before starting all this wait for someone else to confirm I covered everything.
 
--- format all partitions other (except sdcard) === Some may say this step is not necessary.
Click to expand...

Since I caught you online. Is this step necessary?

Added: Found an older post where you and CDPlant where helping me out:

If you are doing a full wipe to install a new ROM, I do the following -

-Backup current ROM
-Factory reset/wipe data
-Wipe Dalvik Cache
-Wipe Cache
-Choose zip from SD Card
-Install
-Reboot
-New ROM

Despite what people will tell you, there is no need to wipe battery stats. Some people say you need to do it every time you flash a new ROM, however it really doesn't do anything useful (and in fact every time you charge your phone to 100% and remove the charger it wipes it for you anyway.) It is solely there to show you your usage on a given charge and has no effect on battery life.
Click to expand...

I am not sure where I picked up the habit of "format all partitions other (except sdcard) "
 
Most Rom install scripts will format the system and bot partitions,so invmost cases ,its not rsally needed. It's definagely not
A bad idea,I can elaborate more a lil later.
 
You must log in or register to reply here.
Back
Top Bottom