Root Can't get out of Hboot FastBoot

jivenene

Member
So I had my EVO 4G running

Amon Ra 2.3
MikG 3.11
Anthrax Kernel

then I tried changing recovery to the smelkus team Dirt recovery, but had a brain fart and did a "flash from zip" via recovery mode, instead of "fastboot flash recovery recovery.img". It did not complete (don't remember the exact error verbage).

Now the phone goes into Hboot every time i turn it on. Weird thing is that it goes directly to Fastboot, unlike before when it went to the main Hboot menu.

Next day i realized what i did and ran the proper command,
"fastboot flash recovery recovery.img". I can go into the Team Dirt recovery now, so I know it worked.

tried reloading ROMs, Kernels, "Clear Data", wiping all the caches multiple times. Still boots up into hBoot and can't get the phone to boot.

Anyone got wisdom for me?
 

Mikestony

~30% Carbon Black ±
So I had my EVO 4G running

Amon Ra 2.3
MikG 3.11
Anthrax Kernel

then I tried changing recovery to the smelkus team Dirt recovery, but had a brain fart and did a "flash from zip" via recovery mode, instead of "fastboot flash recovery recovery.img". It did not complete (don't remember the exact error verbage).

Now the phone goes into Hboot every time i turn it on. Weird thing is that it goes directly to Fastboot, unlike before when it went to the main Hboot menu.

Next day i realized what i did and ran the proper command,
"fastboot flash recovery recovery.img". I can go into the Team Dirt recovery now, so I know it worked.

tried reloading ROMs, Kernels, "Clear Data", wiping all the caches multiple times. Still boots up into hBoot and can't get the phone to boot.

Anyone got wisdom for me?
So, you can get into recovery? (smelkus)?
What are you wiping besides caches before rom flash?
You should wipe all but sd card before a rom flash...I usually wipe 3 times but thats just me.
 

jivenene

Member
Thread starter
So, you can get into recovery? (smelkus)?
What are you wiping besides caches before rom flash?
You should wipe all but sd card before a rom flash...I usually wipe 3 times but thats just me.

Yep, can get into smelkus recovery. Before, the phone went to the Hboot screen (volume down + pwr), and you could select "recovery". Now just when I hit pwr (no volume down), it goes right to FASTBOOT screen, and I have to hit BOOTLOADER to get to the main Hboot screen in order to get to RECOVERY. But it goes into recovery no prob.

did the Superwipe via smelkus recover. then installed ROM and Kernel. I do the ROM first, then reboot, then wipe again and flash the Kernel. Should I do both before rebooting?

Again, this all started when I tried to install the smelkus recovery via "flash a zip" in the recovery menu in Amon Ra 2.3
 

ocnbrze

DON'T PANIC!!!!!!!!!
Yep, can get into smelkus recovery. Before, the phone went to the Hboot screen (volume down + pwr), and you could select "recovery". Now just when I hit pwr (no volume down), it goes right to FASTBOOT screen, and I have to hit BOOTLOADER to get to the main Hboot screen in order to get to RECOVERY. But it goes into recovery no prob.

did the Superwipe via smelkus recover. then installed ROM and Kernel. I do the ROM first, then reboot, then wipe again and flash the Kernel. Should I do both before rebooting?

Again, this all started when I tried to install the smelkus recovery via "flash a zip" in the recovery menu in Amon Ra 2.3

ok your order of flashing is all wrong. you need to wipe everything but the sd card first then flash the superwipe then flash the rom. when you wipe after flashing the rom you are wiping the rom clean. so when you try to reboot all you have is the bootloader and recovery.
 

ocnbrze

DON'T PANIC!!!!!!!!!
and as far as kernels goes it is:
1.nandroid backup
2.full wipe
3.flash superwipe
4.flash rom
5.reboot and sign in making sure that the rom flashed ok
6.wipe only dalvik cache and cache
7.flash kernel.
8.reboot
9.make another nandroid backup if you like the combo(rom/kernel)
 

Mikestony

~30% Carbon Black ±
and as far as kernels goes it is:
1.nandroid backup
2.full wipe
3.flash superwipe
4.flash rom
5.reboot and sign in making sure that the rom flashed ok
6.wipe only dalvik cache and cache
7.flash kernel.
8.reboot
9.make another nandroid backup if you like the combo(rom/kernel)

If flashing a rom, I would start at step 1 and go thru step 5.
If changing a kernel, I would start at step 6 in recovery thru step 9:)
 

dustwun77

Endeavor to Persevere :)
A nice distinction, like to add though, if you want to be a bit more safe when flashing a kernel, you can nand just before it, as well..

It can be a lifesaver to have that nand. Some roms, you can just flash the rom back over itself to restore the original kernel and maintain your setup, other than themes, if you don't like the kernel. The MikG 3.1 rom, for example, is not like that though, it will wipe if you flash it over itself.

Rx modified a version of it here though, that did not wipe itself upon reflashing.
 

jivenene

Member
Thread starter
and as far as kernels goes it is:
1.nandroid backup
2.full wipe
3.flash superwipe
4.flash rom
5.reboot and sign in making sure that the rom flashed ok
6.wipe only dalvik cache and cache
7.flash kernel.
8.reboot
9.make another nandroid backup if you like the combo(rom/kernel)

Well I'll be damned. I didn't know you had to reboot between the ROM and Kernel flash.

I can't believe it but it worked! thanks all! You guys have some patience answering questions from dunces like me all day, wow.

Now lets see if the new ROM/Kernel fix my radio and battery issues. Still think it's hardware related, but thought I would try another ROM/Kernel anyway.
 

ocnbrze

DON'T PANIC!!!!!!!!!
Well I'll be damned. I didn't know you had to reboot between the ROM and Kernel flash.

I can't believe it but it worked! thanks all! You guys have some patience answering questions from dunces like me all day, wow.

Now lets see if the new ROM/Kernel fix my radio and battery issues. Still think it's hardware related, but thought I would try another ROM/Kernel anyway.

it is not necessary. you can flash both rom and kernel in the same recovery session. but doing so makes it harder to trouble shoot if things go wrong. if they do you will not know if it is from the rom or the kernel. it is better to take things slow rather then rush into things.
 
Top