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

Root In a boot loop, need help

R

romanlynch

Member
I haven't used my Evo 4g LTE for a while, just blew off the dust and found there was a new version of CM (11). I followed the normal routine for flashing but it failed. I think because I have HBoot 1.19, the error message said something about boot 2.10. Anywho, being the brilliant guy I am, I already deleted the CM10 zip off my phone. I tried restoring an old backup that was on the phone, still boot loops. I got into bootloader and tried fast boot flashing the CM10 .img file but that did not work either.

Anyone have any ideas?
 
How about remove the sdcard, use a card reader to place a known, working rom onto it, replace card and flash working rom from recovery?

Or adb push a working rom, then flash.
 
adb and fastboot are utilities within the android sdk. If you don't already have it on your PC, you can also look at our forum's mini sdk which is an extremely lean package that contains just adb and fastboot.

Depending on which recovery you have, it may have an adb sideload option. You can try that but I always have better luck with good old fashioned adb push as mentioned. For that you don't have to select any menu option in recovery. Adb works the moment you enter recovery, so with the menu showing, select nothing and issue adb push command and you're good.

If you don't have the sdk set up yet, physically placing a rom on an sdcard via card reader is probably sounding a whole lot easier right about now. :D

Actually, it's not that bad to set up our mini sdk. Ask if you have any questions. If you go that route, I'd recommend unzipping it to the root of your computer's "C" drive if using windows. That makes changing directory much easier down the road.
 
You sir freakin rock. I was able to push the cm10.zip and get that loaded... However CM is stuck in the load screen.

Would you be able to tell me what I might need to do to upgrade to CM11+ or another kitkat rom? I think I'll need hboot 2.10 and twrp 2.8 to start but not sure.
 
romanlynch said:
You sir freakin rock. I was able to push the cm10.zip and get that loaded... However CM is stuck in the load screen.

Would you be able to tell me what I might need to do to upgrade to CM11+ or another kitkat rom? I think I'll need hboot 2.10 and twrp 2.8 to start but not sure.
Click to expand...

I'm sorry I have no knowledge of prerequisites for this device as I don't own one. But from here out, you can push any rom to the sdcard and flash like you just did this one. So if this one doesn't work, try one that's known to be stable. The process is identical.

And don't forget if you're using an AOSP based rom, you'll also need to push the gapps too. So push rom, push gapps. Then flash rom and flash gapps both in the same recovery session. Then reboot to system and cross fingers. :D
 
Okay, going through rumrunner, I set debugging, can not find where to disable fastboot (I'm on cm10.2 but apparently not a problem) disabled the anti-virus. I run soju and I get this far

Must sanitize, skunky rum is nasty
hold please.......
**********************

then the *'s start turning into T's then it says press enter to exit.

What am I doing wrong?
 
Rumrunner wont work with EVERY custom rom :) Maybe all you've to do is flash a different rom and try it again...try a sense based rom.
 
romanlynch said:
Okay, going through rumrunner, I set debugging, can not find where to disable fastboot (I'm on cm10.2 but apparently not a problem) disabled the anti-virus. I run soju and I get this far

Must sanitize, skunky rum is nasty
hold please.......
**********************

then the *'s start turning into T's then it says press enter to exit.

What am I doing wrong?
Click to expand...
If you look back at the post where I mentioned Rumrunner, I said to run it after you RUU, install TWRP and SuperSU. I'm confused as to how you're running it on CM10.2?
 
I don't follow directions well lol. I had 10.2 and twrp 2.6.3 on there already, installed SU and gave it a shot. Flashing those files now.
 
Okay, I did miss that part.

Okay so now I have:
Locked the phone flashing the code through fastboot
Ran the RUU file
Unlocked the phone with HTCDev and the unlock.bin thing
Flashed TWRP 2.8.x (the file you linked)
Installed SuperSU.zip through recovery
Ran soju

Now I only get the the

Must sanitize, skunky rum is nasty
hold please.......
**********************
then the *'s start turning into T's then it says press enter to exit.
 
romanlynch said:
Okay, I did miss that part.

Okay so now I have:
Locked the phone flashing the code through fastboot
Ran the RUU file
Unlocked the phone with HTCDev and the unlock.bin thing
Flashed TWRP 2.8.x (the file you linked)
Installed SuperSU.zip through recovery
Ran soju

Now I only get the the

Must sanitize, skunky rum is nasty
hold please.......
**********************
then the *'s start turning into T's then it says press enter to exit.
Click to expand...
How many times did you try running it? Your problem might be having a secure boot image. If I can find an unsecured one for you to fastboot flash I'll link it here.
In the meantime, you might want to try running it again. Try disabling the screen timeout on the device and making sure you watch the device screen for any prompts for root access. You might also want to just allow all by default for the duration of the process.
 
ADB did request SU access but when I went into SU to allow it it said that was a Pro option only. Could that be it?

Edit - I just ran it again and when it rebooted for the adb access I made sure to unlock the screen and SU did ask for permission, I allowed but same thing happened.

edit the edit - just ran it again and SU automatically granted permission to ADB so that went through fine but it gave me another Fatal error - Fatal: Download updated package at www.rumrunner.us
 
romanlynch said:
ADB did request SU access but when I went into SU to allow it it said that was a Pro option only. Could that be it?

Edit - I just ran it again and when it rebooted for the adb access I made sure to unlock the screen and SU did ask for permission, I allowed but same thing happened.

edit the edit - just ran it again and SU automatically granted permission to ADB so that went through fine but it gave me another Fatal error - Fatal: Download updated package at www.rumrunner.us
Click to expand...
Sometimes that last error means your Internet connection went stale.

At any rate, try flashing this unsecured boot.img via fastboot: https://s.basketbuild.com/filedl/devs?dev=Captain_Throwback&dl=Captain_Throwback/EVO 4G LTE/boot.img

And then run it again. If it doesn't work then, you'll need to try contacting the devs on IRC.
 
Sweet, I forgot to disable the anti virus stuff that last time. I turned that off and it finished. Sorry for being such a PITA, thanks for all your help.
 
Well spent most of the day trying to figure this out so I have to ask now. Is there a way to use the dialer codes, ## in CM11 or is there a sense rom I can flash? I'm on Ting and since this phone wasn't working for a while I switched to another phone and need to use the ## code to get this one back on to Ting.
 
You must log in or register to reply here.
Back
Top Bottom