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

Root Help!! Stuck in bootloop!

K

keegankhaos

Newbie
Hello, first off, let me say that im completely new to the whole rooting scene. So i will probably be asking a bunch of nooby questions..

I just rooted my HTC Evo V 4G by Virgin Mobile last night, and the rooting process went great. I rebooted and had superuser access. I then decided i wanted to flash a custom rom to my phone, and followed a tutorial on how to do so. However, once i wiped the cache and delvik cache, Installed the new rom, Its said the new rom was flashed correctly. So, i rebooted the phone, and it showed the htc logo screen, then went to the custom boot screen for that rom. However. It just sits there, doing the same boot screen over and over. I dont know what i did wrong nor how to fix it. Any Help would be VERY much appreciated. Thanks!
 
What Rom did you flash

If its not sense ics you most likely need s off to change hboot

If it is a sense ics, make sure you wipe system and boot as well as cache and dalvik.
 
adamhos1234 said:
What Rom did you flash

If its not sense ics you most likely need s off to change hboot

If it is a sense ics, make sure you wipe system and boot as well as cache and dalvik.
Click to expand...

This is the most common issue for newcomers. The HBOOT version is very important. As requested by adamhos, please confirm:

1. Which ROM did you flash?
2. Are you S-OFF?
3. What HBOOT version are you running?
4. Which Recovery are you using?
5. How did you go about wiping (formatting) the phone before you flashed the ROM
6. Did you make a NANDROID backup before you flashed the new ROM?

EDIT:

To check your HBOOT, shut the phone down, remove the battery and put it back in. Then hold down the vol - button and the power button until the screen turns on. If you failed to hold the vol- button down properly, it will boot normally rather than the bootloader. Pull the battery and try again. Press hard on the vol - if you can't seem to get it to work, and hold them both down until it turns on. Once on the bootloader screen, tell us what you see.
 
Palmetto Fellow said:
This is the most common issue for newcomers. The HBOOT version is very important. As requested by adamhos, please confirm:

1. Which ROM did you flash?
2. Are you S-OFF?
3. What HBOOT version are you running?
4. Which Recovery are you using?
5. How did you go about wiping (formatting) the phone before you flashed the ROM
6. Did you make a NANDROID backup before you flashed the new ROM?
Click to expand...

as stated, I was using the Team Nocturnal Venom Rom, Im not sure if im s-off. I dont even really know what that is.
I am running HBOOT-1.58.0000
I am using the custom recovery that i made when i rooted my device.
As for the wipig(formatting) I just wiped the cache and delvik cache. should i have done more..?
And sadly no, i did not make a nandroid backup, i didnt know that i could untill after the process. :(
 
keegankhaos said:
as stated, I was using the Team Nocturnal Venom Rom, Im not sure if im s-off. I dont even really know what that is.
I am running HBOOT-1.58.0000
I am using the custom recovery that i made when i rooted my device.
As for the wipig(formatting) I just wiped the cache and delvik cache. should i have done more..?
And sadly no, i did not make a nandroid backup, i didnt know that i could untill after the process. :(
Click to expand...

If you aren't sure about S-OFF, it probably means you aren't. The HBOOT screen I asked you to look at would show either S-ON or S-OFF.

Also, if you're on 1.58, I assume you took some of the OTA (over the air) updates on the phone? If so, you can still S-OFF, but you can't run the RUU. The RUU is sort of a last resort which restores the phone to stock, but Virgin Mobile users on 1.58 can't run the RUU until HTC releases an updated RUU.

Yes, you should have wiped EVERYTHING. This is why I asked which recovery you're using. 4EXT makes wiping everything fool proof.

EDIT:

What do you mean by "I am using the custom recovery that i made when i rooted my device"? You didn't "make" a recovery...you flashed one right? Which one? TWRP?
 
I am S-on, I just checked that.
Yea, i did do the OTA updates. How would i go about getting it to s-off? and would that help the situation?

Yes, i didnt make a custom recovery, that was my understanding error. It was the TWRP recovery that i flashed.
 
keegankhaos said:
I am S-on, I just checked that.
Yea, i did do the OTA updates. How would i go about getting it to s-off? and would that help the situation?

Yes, i didnt make a custom recovery, that was my understanding error. It was the TWRP recovery that i flashed.
Click to expand...

I would start here:

http://androidforums.com/evo-v-4g-all-things-root/695161-s-off-root-fix-everything-all-in-one.html

But at your current state, you're not bone-stock, so some of your steps need to be modified. Remanifest can help you as can Brian or Ramjet.

Guides, or others who know...

Can he perform S-OFF at this point, or does he need a stock, working ROM? Since he's on 1.58, he can't RUU. What does he do now? Would the JMZ ROM work, or should he go with Negamann's latest release with the 2.95 firmware? He's taken the latest OTAs and is on 1.58.

I have an instinct that he should install Negamann's stock ROM UNROOTED, then proceed with Remanifest's all in one thread. I'd rather someone else confirm this as a course of action though.
 
Your best option is to wait on a Guide to show up and help you out. I've PM'ed one for you with a link to this thread. He'll show up when he gets a chance.

If you just want a working phone again, flash a stock ROM. I'm not really sure how to advise you though. I was going to send you to Negamann's stock ROM as it's been updated to the OTA revision you've updated to. JMZ used to be the go to stock ROM as an initial flash to get SuperUser.

How did you get SUperUser? Did you flash the SuperUser zip, or did you flash a ROM that was already unlocked with SuperUser? If you used a ROM, then wipe all, and flash that same ROM, and you'll have a working phone.

MAKE A BACKUP next time around :p
 
Palmetto Fellow said:
Your best option is to wait on a Guide to show up and help you out. I've PM'ed one for you with a link to this thread. He'll show up when he gets a chance.

If you just want a working phone again, flash a stock ROM. I'm not really sure how to advise you though. I was going to send you to Negamann's stock ROM as it's been updated to the OTA revision you've updated to. JMZ used to be the go to stock ROM as an initial flash to get SuperUser.

How did you get SUperUser? Did you flash the SuperUser zip, or did you flash a ROM that was already unlocked with SuperUser? If you used a ROM, then wipe all, and flash that same ROM, and you'll have a working phone.

MAKE A BACKUP next time around :p
Click to expand...

Thank you so much for your help. At the moment, im going to try a RUU tool, even though i doubt it iwll work. If it doesnt, i can try and flash the Negamann's rom. I had flashed the Superuser zip to get it. Could i possibly just wipe all, then flash another rom? Sorry for all the noob-ish questions.. :)
 
Palmetto Fellow said:
MAKE A BACKUP next time around :p
Click to expand...

Yes! Always make a backup before flashing a new rom or changing anything major. Then if something goes wrong, it's easy to come back from ;)


Here's the deal. You rooted, and are still s-on. The recovery you are using (TWRP I assume) does not allow you to flash the kernel with the rom, if you are s-on.

What to do now?
Browse the rom.zip on your sd card with a card reader or spare device. Copy the boot.img from the rom you flashed into the folder that contains fastboot/adb on your PC. (Same place you put the recovery.img when rooting). Then get your phone back into fastboot usb mode with adb reboot bootlader or by doing a battery pull, then holding volume down+power to access the bootloader. From there select fastboot and then when you plug the phone in, you should see fastboot usb in red letters.

From there use this command: fastboot flash boot boot.img

Your rom should boot up after that.

After you are booted, I would suggest installing 4ext recovery.
Go to their site and get the free recovery updater. Put that .apk file on your sd card and tap on it and choose install. Then you can open the app and go to "online|install" and choose a recovery version. It will automatically install it for you. When it asks if you are s-on say YES!

That will enable a feature called smart flash that will allow you to flash roms without flashing the boot.img separately. As long as you flash a rom that is compatible with your hboot version, this shouldn't happen again if you are using 4ext recovery.

The other way to flash the boot.img with the rom is to do like you did when you first rooted. use fastboot boot recovery.img to boot the recovery into the phones memory. You can even use TWRP for this. Then after using that fastboot command to boot recovery, it will flash the boot.img just fine along with the rom.
 
keegankhaos said:
Thank you so much for your help. At the moment, im going to try a RUU tool, even though i doubt it iwll work. If it doesnt, i can try and flash the Negamann's rom. I had flashed the Superuser zip to get it. Could i possibly just wipe all, then flash another rom? Sorry for all the noob-ish questions.. :)
Click to expand...

Unfortunately since you took the March OTA update and got on hboot 1.58, there is no RUU available for you. Until you get s-off, you have no RUU :eek:

It's unnecessary at this point though. Even if there was an RUU you could use, it's way more effort than you need. That would require you to lock the bootloader, run RUU (which takes away root and recovery), then you'd have to unlock again, flash recovery, and then flash super user.

All you really need at this point is to flash the boot.img per above, and you should be good ;)
 
keegankhaos said:
Thank you so much for your help. At the moment, im going to try a RUU tool, even though i doubt it iwll work. If it doesnt, i can try and flash the Negamann's rom. I had flashed the Superuser zip to get it. Could i possibly just wipe all, then flash another rom? Sorry for all the noob-ish questions.. :)
Click to expand...

Don't try the RUU tool yet. Follow Brian's instructions for now.

Also, yes, you can flash another ROM, just be sure it's very close to stock or it won't work with that HBOOT. Also, flashing the kernel can be tricky as Brian mentioned unless your recovery is setup to do this. I strongly suggest getting on 4EXT recovery at some point.

I was S-OFF before I flashed any ROMs, so I am not really sure which ones you can flash and which ones you can't being S-ON. JMZ is usually the safest, and I think Harmonia will flash as well no issues...but I don't know if either of those has been updated to the latest OTA, and I don't know if there are incompatibility issues as a result since you're on the newest firmware.

I'll let Brian take over from here.
 
Brian706 said:
What to do now?
Browse the rom.zip on your sd card with a card reader or spare device. Copy the boot.img from the rom you flashed into the folder that contains fastboot/adb on your PC.

After you are booted, I would suggest installing 4ext recovery.
Click to expand...

Brian,

Will that ROM boot on 1.58? Does he need to wipe all? He didn't wipe all before he flashed, so maybe he has some funky file system on his paritions.

Also, he'll need busybox to install 4EXT. You can get it from the Google Play store, but the app for BusyBox is just the installer. You have to launch the installer, and then afterwards, you will have BusyBox.

EDIT:

Off to lunch...good luck :)
 
Palmetto Fellow said:
Brian,

Will that ROM boot on 1.58? Does he need to wipe all? He didn't wipe all before he flashed, so maybe he has some funky file system on his paritions.

Also, he'll need busybox to install 4EXT. You can get it from the Google Play store, but the app for BusyBox is just the installer. You have to launch the installer, and then afterwards, you will have BusyBox.

EDIT:

Off to lunch...good luck :)
Click to expand...

I think that rom will be fine. It's a stock based Evo 3d ICS rom, which is hboot 1.58. The new Evo V hboot is exactly the same. May run into MMS issues though since it's a 3vo rom :/

Someone around here with an Evo V can probably help with that though.

Yes, before flashing any rom, you should wipe all partitions (except sd card)
 
Brian706 said:
Yes! Always make a backup before flashing a new rom or changing anything major. Then if something goes wrong, it's easy to come back from ;)


Here's the deal. You rooted, and are still s-on. The recovery you are using (TWRP I assume) does not allow you to flash the kernel with the rom, if you are s-on.

What to do now?
Browse the rom.zip on your sd card with a card reader or spare device. Copy the boot.img from the rom you flashed into the folder that contains fastboot/adb on your PC. (Same place you put the recovery.img when rooting). Then get your phone back into fastboot usb mode with adb reboot bootlader or by doing a battery pull, then holding volume down+power to access the bootloader. From there select fastboot and then when you plug the phone in, you should see fastboot usb in red letters.

From there use this command: fastboot flash boot boot.img

Your rom should boot up after that.

After you are booted, I would suggest installing 4ext recovery.
Go to their site and get the free recovery updater. Put that .apk file on your sd card and tap on it and choose install. Then you can open the app and go to "online|install" and choose a recovery version. It will automatically install it for you. When it asks if you are s-on say YES!

That will enable a feature called smart flash that will allow you to flash roms without flashing the boot.img separately. As long as you flash a rom that is compatible with your hboot version, this shouldn't happen again if you are using 4ext recovery.

The other way to flash the boot.img with the rom is to do like you did when you first rooted. use fastboot boot recovery.img to boot the recovery into the phones memory. You can even use TWRP for this. Then after using that fastboot command to boot recovery, it will flash the boot.img just fine along with the rom.
Click to expand...

Ok, So i followed your direction, and completely farmatted every partition except the sdcard, and flashed the Venom ROM. I then rebooted into fastboot USB and flashed the boot.img. I rebooted, and the rom did boot to the lock screen, but then just restarted the phone. it did this twice, but i think i missed one of the partition when i was formatting them Im going through and doing everything again... *crossing fingers*
 
Update: After wiping all partitions and caches, flashing new rom, then flashing boot img, the rom boots up to lock screen like before, but then restarts before i can do anything. could i possibly flash a boot.img from another rom? like negamanns stock rom? Also, where can i find Negamann's rom, i tried searching for it but couldnt find it.
 
Hmmm... I don't think it would be wise to flash the boot.img from another rom. The boot.img contains the kernel, and generally you want to stick with the kernel that the rom uses.

It is an Evo 3d rom, so it's possible that it just isn't playing nice with your phone. I know that they are the same phone but there are some differences, which is why a lot of devs make a Sprint version and a VM version of the rom. I would say, to try some stock based VM roms to start. I'll let someone else suggest them as I have the sprint version and haven't used any of the VM roms.
 
Brian706 said:
Hmmm... I don't think it would be wise to flash the boot.img from another rom. The boot.img contains the kernel, and generally you want to stick with the kernel that the rom uses.

It is an Evo 3d rom, so it's possible that it just isn't playing nice with your phone. I know that they are the same phone but there are some differences, which is why a lot of devs make a Sprint version and a VM version of the rom. I would say, to try some stock based VM roms to start. I'll let someone else suggest them as I have the sprint version and haven't used any of the VM roms.
Click to expand...

Alright, I didnt try with another boot img, so we are good there.

what rom would i use though? Is there a defference between cm9 and cm 10? Because im pretty sure ive seen both for the vm version..
 
Brian,

That whole boot.img stuff is totally foreign to me. Why is this step required for s-on users? I mentioned that I never flashed a rom until I was s-off so this sort of thing makes me feel noobish :o
Is the kernel part of boot.img?

Also, what do you think about getting him a working phone as close to stock by flashing a rom that won't need the boot.img step? He could then follow remanifest's guide.
Is there any chance the rom he picked doesn't like the fact that he took the latest ota? Is there anything in his updated firmware that could conflict

Edit:

Lol, I type so slow on my phone that there have been two replies since I started this reply. I see that brian answered my question about the kernel being part of the boot.img.
 
keegankhaos said:
Alright, I didnt try with another boot img, so we are good there.

what rom would i use though? Is there a defference between cm9 and cm 10? Because im pretty sure ive seen both for the vm version..
Click to expand...

Stay away from all cm roms. You can't run them yet. Stick with ics.

Edit:

I would suggest some vm roms but I don't know what you can flash. My lack of s-on knowledge makes me hesitant to suggest one.
At this point since he's wiped his boot partition, will he ways have to take that extra boot.img step?
 
Ill remember to avoid them. I cant find just a stock ICS one though. All the ones that are plain stock that i have found were the cm roms.
 
Palmetto Fellow said:
Brian,

That whole boot.img stuff is totally foreign to me. Why is this step required for s-on users?
Because twrp recovery alone will not flash the boot.img with the rom. It's part of s-on security checks.

I mentioned that I never flashed a rom until I was s-off so this sort of thing makes me feel noobish :o
Is the kernel part of boot.img?
Yes

Also, what do you think about getting him a working phone as close to stock by flashing a rom that won't need the boot.img step?
Any working rom would be great to start with. Including stock.
But they all would require a separate boot.img flash, unless you flash the rom one of the two ways I've specified in the previous posts.
1. Use 4ext recovery with smart flash enabled.
2. fastboot boot recovery.img to boot the recovery into phones memory. Then flash the rom through recovery. Booting the recovery this way allows you to flash the boot.img together with the rom.

He could then follow remanifest's guide.
Is there any chance the rom he picked doesn't like the fact that he took the latest ota?
I don't see why not. He is on the required hboot. It is an evo 3d rom though, and maybe something in it doesn't play nice with VM? I'm not a dev so I don't really have those kinds of answers.

 Is there anything in his updated firmware that could conflict
Again, not that I know of??
Edit:

Lol, I type so slow on my phone that there have been two replies since I started this reply. I see that brian answered my question about the kernel being part of the boot.img.
Click to expand...
Oops, I didn't read your last paragraph before starting my reply :p
 
Based on what brian last write to me, I suggest using option 2 to flash the rom and boot.img together.
Here is a link to negamann's stock rom.

http://androidforums.com/evo-v-4g-all-things-root/699063-rom-stock-vm-ota-2-95-652-5-un-rooted-odexed-deodexed-everything-should-work-now.html

Nega says to use smart flash with 4ext but it sounds like brian's method should work. I can't screw up your phone worse than it is now, so the only thing you'll lose is your time if it fails.
A for which of the 3 versions to choose, I dunno. Ask brian if you should take the rooted or not. I don't understand odex or deodex myself. If you take the non rooted one, there is only one option.

If you get up and running, make a backup, then follow the remanifest guide I linked to in order to obtain s-off. Also, switch to 4ext when you can.
 
You must log in or register to reply here.
Back
Top Bottom