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

Root [CDMA] Help! Stuck at boot loop evo 3d

Hello All,
I recently rooted my EVO3D using the HTCDEV method because the bootloader was version 1.5.
Here are the steps I followed to root (sorry for the copy and past but I want to be as detailed as possible)

Files Used
su 2.3.6.3
TWRP Recovery

Steps Taken:
1)Take both the su.zip and recovery.img files and put them in your sdk tools folder.
2)Now do the following in ur command prompt, hitting enter after each command.
3)Code:adb push recovery.img /sdcard/And,
4)Code:adb push su-2.3.6.3.zip /sdcard/Then,
5)Code:adb reboot bootloaderUr phone will go to fastboot and should look like the after picture above. Now you can flash the twrp recovery, so do,
6)Code:fastboot flash recovery recovery.imgIt will ouput something like this,
7)Code:sending 'recovery' <5068 KB>... OKAY////writing 'recovery'... OKAY///finished. total time: 11.355sNow you have twrp recovery, so you can navigate to it. On ur phone, use the power button to pick bootloader, then scroll down to recovery and pick that. You will then be booted into recovery.
8)Here you can pick "install zip" and then pick the "su-2.3.6.3.zip"
It will flash, the you can pick "back to main menu", then "reboot system now"
9)You will boot back up and have working Superuser. I have had no trouble with Titanium Backup, Root Explorer, Quick Boot or any other app that requires root. Before you do too much, it would be good to go back to recovery and do a Nandroid backup. Always best to get one ready before you start modding anything.

All of this worked fine, and the phone was "unlocked."
Then, I flashed the most recent version of CleanRom (2.7)
Again, the phone worked fine, battery life was a little crappy.
I decided to flash Ziggy's kernel.I flashed the kernel simply by putting on the SD card, and then rebooting into recovery. This worked fine as well, but I noticed some of the buttons for example the menu popups displayed volume where it should have said more, or bluetooth options where it should have said preferences. so this is where the trouble started, I downloaded kernel manager, and flashed silverneedle through that program. Now, I am stuck at the White HTC Splash screen bootloop. The phone turns on and after 15 seconds reboots, and reboots, and reboots.

What Ive attempted:
I have done countless wipes and clears of the dalvik cache and cache
ive formatted the system and the date sections (advanced menu in twrp)
ive reflashed the rom after wiping countless times
ive tried flashing different kernels in recovery to no avail
factory reset and wipe havent helped
im not concerned losing the contents of the SD card
I need help because I already had two phone claims in the past 11 months, and if I claim another lost phone I will lose insurance for life with Asurion (sprint)

anytips or help would be greatly appreciated
i can provide any additional info
 
I did, and I attempted to restore it but it still keeps loading the splash screen and then restarting. I am really out of ideas.......
 
Your best bet is to post this in the rooted section, you will get the proper response there.


I did, and I attempted to restore it but it still keeps loading the splash screen and then restarting. I am really out of ideas.......
 
Put a rom on the root of your sdcard, boot to bootloader
Open cmd and cd to the folder with fastboot
Issue command fastboot boot recovery recovery.img
Then once you get to recovery do a full wipe and flash again. This will allow you to write to /boot partition which you can not do by just booting into recovery
 
And it seems like there are quite a few issues with ziggy kernel now so I would recommend that you wait until his next release before flashing
 
sorry to be a pest, could you be more specific, if i put cleanrom on the sd card
boot to recovery using those commands then do a factory reset , then flash the rom?
 
everyone give wake69 a bump for helping me out........it worked!

thank you wake69!
here you go wake69
29005553.jpg
 
I've noticed too and guess I should've asked earlier....A lot of people aren't catching the step of using the command prompt to enter recovery. They're rebooting into recovery via volume+power.
 
you can boot into recovery that vol + power and flash fine if s-off via recovery but not htc unlock
 
I don't post much but I just wanted to post a possible fix for a problem that has been asked before if you search the web. I wanted to post my fix here just so that it's out there.

DISCLAIMER:

1. YOU NEED A HEAT GUN.
2. IT'S NOT AN EASY FIX AND REQUIRES A FULL TEAR DOWN

The Problem:
My rooted launch Evo was stuck in an odd boot loop. I thought it could be software but it wouldn't reboot at a specific moment rather different times. Sometimes it wouldn't reboot for a minute, other times it would reboot after a couple of seconds after hitting the power button. This led me to believe that it was hardware related.

A couple of weeks back my wife dropped it in the dog bowl for a second but it booted up normally and worked well for several weeks.

I also have it overclocked and it tends to heat up a wee bit more compared to when it was stock. Maybe the problem is similar to what the PS3 and Xbox experience with the immense heat and the subsequent fracturing of the GPA connection.

I had this problem with my PS3 and after researching I decided that since it was already broken to tear it down to the board and heat up the GPU. What happens is that the thermal compound is crap and dries out after a while. mine lasted 4 year until this happened. Anyways, the compound dries up and the chip overheats causing the connections to the board to fracture. Heating up the GPU liquefies the connections a bit and the fractures fill in.

I decided that since the phone was busted, I would apply the same logic. It was a crap shoot basically but it ended up working. So for those that give up and are willing to try this over buying a new phone just tear your Evo down to the board and heat the sucker up a bit. I used the low setting on my heat gun. I didn't bother to remove the ribbons and instead avoided blasting them with heat and focused on the rest of the board. You might want to remove them completely if you don't want to burn them.
 
Could the answer really be as simple as booting into fastboot instead of holding the button to get into recovery? I have also been struggling with the same problem. hboot 1.5 Htc unlock. with the black boot screen of death. I'm following your instructions now. i'll let you know if it works.
 
Eureka! Thank you so much. Weeks of head aches solved. SO Does this mean that every zip that needs to be flashed must be done so through fastboot recovery, is rom manager recover acceptable? you said the ziggy kernel is unstable? is there one that you recommend?
 
Eureka! Thank you so much. Weeks of head aches solved. SO Does this mean that every zip that needs to be flashed must be done so through fastboot recovery, is rom manager recover acceptable? you said the ziggy kernel is unstable? is there one that you recommend?
there are no kernels i have found to be stable but a lot of people have had luck with the anthrax kernels
 
ok. I will stick with the ziggy kernel for now. I've had to fast boot my phone all last month and that was the only kernel that worked. on synergy nightly. mostly stable may require reboot when temp memory gets low.
 
You just have to find what works for your device. My device doesn't get along with any ROM other than CleanROM (it doesn't even like any of the other ROMs Scott produced) and, oddly enough, it the ICS alphas.

Synergy, Infected, Viper, Senseless, etc just do a random reboot whenever they feel like. Regardless of the kernel used (stock, tiamat, anthrax, etc). But, if I'm running CleanROM, I can run any kernel I want without issue.

It's just weird.
 
Xplod does the same for you also ??



You just have to find what works for your device. My device doesn't get along with any ROM other than CleanROM (it doesn't even like any of the other ROMs Scott produced) and, oddly enough, it the ICS alphas.

Synergy, Infected, Viper, Senseless, etc just do a random reboot whenever they feel like. Regardless of the kernel used (stock, tiamat, anthrax, etc). But, if I'm running CleanROM, I can run any kernel I want without issue.

It's just weird.
 
Back
Top Bottom