-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root [HELP]Stuck in bootloop..
- Thread starter golfrguy
- Start date
-
- Tags
- htc evo v 4g
If you're not concerned about losing your data, just wipe from recovery and re-flash Mobz rom. If you are concerned about your data, you might be able to wipe just the cache and dalvik cache in recovery, and then re-flash the Power kernel that came with Mobster Rom (It's in the second post in the Rom's thread). Hope this helps.
kagevazquez
Well-Known Member
I recommend the second option
Well if you're going to wipe everything, then there's no need to flash power kernel because that's what Mobz V comes with. So just wipe everything again and only flash the rom. Also, are you S-off?
nsciucco
Android Expert
No fret. I had this excact problem before... I dont know what caused it.. but its a easy fix.. You should still have the boot.img from the almost stock rom on your computer. ( You used it during the root process.) Just use CMD and flash the boot.img and reboot your phone.. Problem solved
golfrguy
Newbie
No fret. I had this excact problem before... I dont know what caused it.. but its a easy fix.. You should still have the boot.img from the almost stock rom on your computer. ( You used it during the root process.) Just use CMD and flash the boot.img and reboot your phone.. Problem solved
I will try that as soon as I'm back on my computer. Thanks! I now just want to find out why flashing that kernel broke my phone..
Edit: So whats the code to flash the boot.img through cmd? I see the boot.img but can't figure cmd out...
Edit2: I figured it out thanks to the all root commands so thanks for all the help!
nsciucco
Android Expert
I will try that as soon as I'm back on my computer. Thanks! I now just want to find out why flashing that kernel broke my phone..
Edit: So whats the code to flash the boot.img through cmd? I see the boot.img but can't figure cmd out...
Edit2: I figured it out thanks to the all root commands so thanks for all the help!
So you are all set? It worked?... I had the same problem one day. That worked for me.. I hope it helped:smokingsomb:
nsciucco
Android Expert
I am s-on. I flashed the kernel using CMD
OverByter
Resident Slide Rule Guru
Using fastboot? What command did you use? I'm just trying to see if there is any commonalities to the people who have been having this issue. Right now it seems random but I'm sure that there has to be a common thread involved. Thanks for the info.
golfrguy
Newbie
Recovery-4ext
HBoot-1.57000(whatever stock is)
S-On
I just flashed the .zip with smartflash and tried to reboot and got the bootloop.
Flashing the original boot.img through cmd worked like a charm. Not sure why it didn't work though.
Sidenote- The kernel may have been installed but needed the original boot.img because I was able to OC up to 2.0GHz with more governors then Mobz Rom has. Mobz Rom with clean install can't OC with it's kernel. I may have to go through those steps because the custom kernel did work well.
HBoot-1.57000(whatever stock is)
S-On
I just flashed the .zip with smartflash and tried to reboot and got the bootloop.
Flashing the original boot.img through cmd worked like a charm. Not sure why it didn't work though.
Sidenote- The kernel may have been installed but needed the original boot.img because I was able to OC up to 2.0GHz with more governors then Mobz Rom has. Mobz Rom with clean install can't OC with it's kernel. I may have to go through those steps because the custom kernel did work well.
nsciucco
Android Expert
the command I used was fastboot flash boot boot.img
nsciucco
Android Expert
The stock boot.img that was used for rooting purpouses
nsciucco
Android Expert
You are all set to flash whatever kernel you want now. it will work fine. like i said i dont know what caused the bootloop... i just know the stock boot.img fixed it !