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

Root stuck in cyanogenmod splash

Thanks for the reply. I'm sure I didn't interpret your answer properly. Where is boot.img located?

Going to fastboot, there isn't a boot.img option in hboot, and I don't have a file called boot.img to flash from on cmd line (except for where I hacked my old hp touchpad :). Where would I find a boot.img and should I flash from cmd line, or is it somewhere in twrp that I missed.

Again, thanks for your help.
 
Fast boot is the program you use to push commands from your computer to your phone. So from the command line on your computer, running fast boot, you would run flash boot boot.img

Boot.img is located in the zip you used to flash cyanogen mod. Unzip a copy of what you flashed on your computer and take the boot.img and put it in the same folder as fast boot so you can flash it over onto your phone. You may have to do this one or two or five times before it flashes properly.

You have to flash the boot image separately because of the way HTC phones work: since you are s-on you have to separately replace the kernel, with the process Brian and I are describing.
 
Sorry for being so vague. I only had a few seconds to reply. Was hoping you'd know what I meant!

As guitar said, the boot.img is in the cyanogenmod rom zip that you flashed. You need to put that boot.img in on your pc in the same directory as fastboot.exe.


Then with the phone in fastboot mode selected in the bootloader and plugged into the pc, you will use the command

fastboot flash boot boot.img
 
I absolutely appreciate the responses. I did flash from cmd the boot image that I had loaded it with, but still in endless cyanogenmod. Should I have erased the cache? I did not initially, but tried as a second shot and still in endless cyanogenmod...
 
I absolutely appreciate the responses. I did flash from cmd the boot image that I had loaded it with, but still in endless cyanogenmod. Should I have erased the cache? I did not initially, but tried as a second shot and still in endless cyanogenmod...

Not sure exactly what the problem is. Possibly occurred from some of the other stuff you tried while stuck.

Really the easiest way around this, since you are using a pc to flash the boot.img separately is to just boot the recovery instead.

This will allow you to flash the boot.img at the same time as the rom.


All you need is a copy of your recovery.img kept in your fastboot folder.

You put the phone in fastboot USB mode and use command:
fastboot boot recovery.img

Then once in recovery, wipe system data cache and dalvik and then just flash the rom normally.

You should really consider S-off if it's available for you because it will save you from this s-on rom flashing hassle.
 
I again appreciate the quick response. I flashed the stock_evo4glte_recovery.img using the fastboot boot stock_evo4glte_recovery.img I received a message booting.... Failed <remote: reproduce boot image with on-flash ramdisk error>

No joy, and would love to get to s-off, but honestly right now, I've been without a phone since Thursday, and I'd take a working dumb phone :)
 
Use your custom recovery to boot. You won't be able to wipe and flash with the stock recovery.

Things are hectic here right now, so apologies if I get a little short
 
You'll need to re-lock the bootloader to run the RUU. Boot to the bootloader and select "Fastboot"
Plug the phone in.
Open the command prompt from your ADB folder (find the folder, shift + right click, select "Open Command Window Here")
From there type this "fastboot oem relock" without the quotes.
Press enter

Once this is complete, type in "Fastboot reboot bootloader"

Now your Hboot screen should say "Relocked" at the top.

At this point, try and run this RUU:
http://dl3.htc.com/application/RUU_...V_3.02_003_PRL25007_release_334470_signed.exe

If that doesn't work, we'll try another avenue. :)
 
so from the cmd prompt, I'm in the folder that contains adb.exe and fastboot.exe... from there, I typed fastboot oem relock, but received an error message - (bootloader) [ERR] Command error !!!
OKAY [ 0.122s]
finished. total time: 0.122s.

I then tried the fastboot reboot bootloader in case the error was some trickery the system was trying to pull, and received a list of commands. apparently the fastboot version I'm working with needs the reboot bootloader to have a dash such as follows - reboot-bootloader.

It did end up providing a list of commands available for this fastboot that I have, and oem relock wasn't on the list.

Again, I appreciate the assistance, and I'm sure I'm missing tons!
 
Use your custom recovery to boot. You won't be able to wipe and flash with the stock recovery.

Things are hectic here right now, so apologies if I get a little short


Sorry, I'm not not following quick enough. By custom recovery help me out for the guy still at 3rd grade level. I didn't see a recovery.img in the zip files I downloaded.

Thank you all for your patience and help. I've temporarily ported my number to my old evo 3d that I had gave my daughter to use. She can do without until I get this figured out!
 
so from the cmd prompt, I'm in the folder that contains adb.exe and fastboot.exe... from there, I typed fastboot oem relock, but received an error message - (bootloader) [ERR] Command error !!!
OKAY [ 0.122s]
finished. total time: 0.122s.
I believe the command is actually fastboot oem lock as opposed to "relock"


Sorry, I'm not not following quick enough. By custom recovery help me out for the guy still at 3rd grade level. I didn't see a recovery.img in the zip files I downloaded.

Thank you all for your patience and help. I've temporarily ported my number to my old evo 3d that I had gave my daughter to use. She can do without until I get this figured out!
No worries :p

The custom recovery is what you use to flash the root binaries or to flash a custom rom. Also make full image backups, etc...

If you are running the RUU first, you will not worry about recovery right now. Running the RUU will return you to a fully stock state.

Once you are stock again you will be starting from scratch.

Flashing a recovery is part of the standard rooting process (which I assume you did at some point). Twrp recovery offers a download here: Techerrata Downloads - Browsing jewel

that you can flash via the command prompt/fastboot.

You would want the latest which I believe is named "openrecovery-twrp-2.7.0.0-jewel.img".


Anyway, I don't want to get ahead of ourselves. Let's attempt the RUU first and then we can worry about getting the phone back to where you want it!!
 
Thank you all!! back to stock!!! I'm taking recommendations for first steps. I'd like to be unlocked, preferrably s-off and be able to load ROM's Since I don't know for sure where I went wrong last time, I'll take advice from this group as to next steps.

Thank you again!
 
Excellent!! :D

We're always available if you have any questions. :)

Big Edit: If you would like to take the last update from HTC for this device, it will update you to Sense 5 and 4.3, there is an RUU for it. I recommend getting S-off first as it makes everything a little easier to do. This remaps the phones partitions just as a heads up, so you'll need to backup even the internal memory prior. If you're interested just let us know!! :)

@ Brian: Thanks Brother! I know that command like the back of my hand but still screwed it up. :p
 
Thank you all!! back to stock!!! I'm taking recommendations for first steps.

For first steps check out this guide: http://androidforums.com/evo-4g-lte-all-things-root/605567-ltevo-rooting-dummies-complete-guide.html

That will get you root, but if you want s-off you will want to check out the link in my last post.

You will have to make a live Ubuntu cd/dvd for S-off.

For help with that check here: http://www.ubuntu.com/download/desktop/burn-a-dvd-on-ubuntu


It's really just a matter of going step by step. Other than that, just let us know if you get stuck or have any specific questions about a step and we can help you out!
 
Back
Top Bottom