HTC evo 4g LTE can't load system again - Sprint HTC EVO 4G LTE

Hi people facing a problem with my Phone. The problem is it won't reboot to system anymore even when i select system after going into reboot menu in Team Win Recovery Project v2.2.1 ...What happens is when i select system in the reboot menu, it boots to my Teamwin recovery instead of system but when i select power off or recovery or bootloader it goes into those fine. I even tried factory reset from bootloader and from Teamwin recovery but it still reboots to Teamwin recovery. I just want it to be able to get to my system again so i can have everything working..
This is what i did before it became like this. I was on HTCevohacks on the HTC evo 4g lte roms page trying to install CM10 ROM for Rooted HTC Evo 4G LTE! [Android 4.1.2][STABLE]. i downloaded CM10 Rom zip file and Gapps 4.1.2 zip file. i put both on my external storage then tried to install them and fail but before that i made a backup of my System, Data and Boot on my external storage. When it failed i factory reset from recovery without restoring backups and it started up perfectly, i even set up my phone interface again linking my google mail and wifi connections. next i went back to recovery and restore my backups from my external storage and that's when i couldn't get back to system. I still have my backup files. They are boot.emmc.win, boot.emmc.win.md5, data.ext4.win.md5, system.ext4.win and system.ext4.win.md5...
this is my HTC evo 4g lte specs..
Flashed to boostmobile
unlocked
Jewel put ship s-on RL
Hboot-1.15.0000
Radio-1.05.11.0606
OpenDSP-v25.1.0.32.0405
eMMc-boot
PLEASE HELP ANYWAY HOW!!just want to go back into system again

You'll need to flash the boot.img through fastboot if you have s-on

xHausx said:
You'll need to flash the boot.img through fastboot if you have s-on
Click to expand...
Click to collapse
I don't have a boot.img to flash that i know off so where do i get my boot.img so i can flash it and have my system running again?

Pull the boot img from the rom your flashing. You should probably read the "don't panic " thread stickied in q&a. All your answers are there
Sent from my EVO using xda premium

If booting system is loading twrp then you have flashed twrp as a kernel, flash a Rom with kernel installer or fastboot kernel

om4 said:
If booting system is loading twrp then you have flashed twrp as a kernel, flash a Rom with kernel installer or fastboot kernel
Click to expand...
Click to collapse
Yes, that makes a lot more sense, i think i flashed twrp as a kernel without knowing it that's why booting system boots to twrp..bout bro i'm still new to this whole thing so please explain step by step how i can flash a Rom with kernel installer or fastboot kernel or provide a link to a guide..please my phone is off nd i'm missing out on calls, i really need to put it back to normal nd not miss with it anymore..i appreciate your first help..

You need to find a ROM that is son friendly, like meanrom. It will flash the whole ROM including the boot.IMG just like you would if you were s-off. It doesnt need anything extra done on your part. Or you need to extract the boot.img from your cm zip and fastboot flash that. In order to fastboot flash the kernel you need to set up adb. Google how to set up adb on windows or Mac or Linux or whatever os your computer is.

thedecider said:
Yes, that makes a lot more sense, i think i flashed twrp as a kernel without knowing it that's why booting system boots to twrp..bout bro i'm still new to this whole thing so please explain step by step how i can flash a Rom with kernel installer or fastboot kernel or provide a link to a guide..please my phone is off nd i'm missing out on calls, i really need to put it back to normal nd not miss with it anymore..i appreciate your first help..
Click to expand...
Click to collapse
Meanrom has a kernel installer, just leave it alone for 5-10 minutes to install. Or to flash kernel manually, when you are ready to flash a Rom extract the boot.img from the Rom zip and use uniflash, bootimg flasher, or fastboot to flash it. ADB Tools and HTC drivers are all you need to flash the kernel through fastboot. Just extract folder and place boot image inside. In windows you can hold shift and right click, select open command window here for the terminal. Then connect phone I'm fastboot (bootloader/fastboot) and type fastboot devices to make sure the pc sees it. Type fastboot flash boot boot.img and then boot recovery and flash rom

Related

3d wont boot

hey fam i was running virus rom Eternity 3.0 with stock kernel then i flashed the cm7 rom by joelz yesterday but had to change kerenls to get it to work. i used the apk to do that i think its gui i think, but anyway i tried to restore back from nadroid and my phone wont boot. im on 1.5 with s-on
thanks if any one can help.
evoguy404 said:
hey fam i was running virus rom Eternity 3.0 with stock kernel then i flashed the cm7 rom by joelz yesterday but had to change kerenls to get it to work. i used the apk to do that i think its gui i think, but anyway i tried to restore back from nadroid and my phone wont boot. im on 1.5 with s-on
thanks if any one can help.
Click to expand...
Click to collapse
I guess you have flashed a 2.3.3 kernel so you are experiencing issues.........so now just boot your phone in bootloader then select fastboot > connect your phone to pc (it should say fastboot usb on phone)> now open cmd > head to your fastboot folder in cmd> then type fastboot boot xxxxx.img (xxxx = your recovery img (cwm/twrp) ) > Now your phone will boot into recovery > then restore your Nandroid backup .......
Hope this helps
If the above didnt work try to flash boot.img from your nandroid backup using fastboot (not recovery) with command "fastboot flash boot boot.img"
press thanks if i helped you
is there a way i can do it without my computer im at work,so i don't have all my files on hand...thanks this has got me stomped......
I m sorry you cannot do it without a pc .....you know the limitations of htc unlock method...you can only flash kernels made for 2.3.4 from flash image gui......you can always download those fastboot/adb files from here or google for it.They are just a few kb's
evoguy404 said:
is there a way i can do it without my computer im at work,so i don't have all my files on hand...thanks this has got me stomped......
Click to expand...
Click to collapse
Yes, as long as all the nandroid backup files are on your sdcard. Steps below.
mnomaanw said:
I m sorry you cannot do it without a pc .....you know the limitations of htc unlock method...you can only flash kernels made for 2.3.4 from flash image gui......you can always download those fastboot/adb files from here or google for it.They are just a few kb's
Click to expand...
Click to collapse
This isn't true. Flash Image GUI will flash the kernel for any version, but if your system OS is not also updated at the same time, the device will not boot.
If you're looking to do a nandroid restore w/o using fastboot (or being attached to a computer), here are the steps I would suggest:
1) From Flash Image GUI, select the boot.img from inside of the custom recovery backup directory on the /sdcard. Flash this kernel.
2) Reboot directly into recovery mode. Run the nandroid restore for that SAME backup as the boot.img was pulled from and flashed via Flash Image GUI.
3) After nandroid restore finishes, reboot and the device should be back to the previous state found in the backup.
Remember, this is a work around for the HTC unlock and might not always be the best solution.
Keep us updated and let us know. Hope that helps!
joeykrim said:
Yes, as long as all the nandroid backup files are on your sdcard. Steps below.
This isn't true. Flash Image GUI will flash the kernel for any version, but if your system OS is not also updated at the same time, the device will not boot.
If you're looking to do a nandroid restore w/o using fastboot (or being attached to a computer), here are the steps I would suggest:
1) From Flash Image GUI, select the boot.img from inside of the custom recovery backup directory on the /sdcard. Flash this kernel.
2) Reboot directly into recovery mode. Run the nandroid restore for that SAME backup as the boot.img was pulled from and flashed via Flash Image GUI.
3) After nandroid restore finishes, reboot and the device should be back to the previous state found in the backup.
Remember, this is a work around for the HTC unlock and might not always be the best solution.
Keep us updated and let us know. Hope that helps!
Click to expand...
Click to collapse
hey joey i know we can use flash image gui to flash boot.img from a rom.zip but evoguy cannot boot his phone at all.So how will he be able to use Flash image GUI? I m only telling him what he can do now........
mnomaanw said:
hey joey i know we can use flash image gui to flash boot.img from a rom.zip but evoguy cannot boot his phone at all.So how will he be able to use Flash image GUI? I m only telling him what he can do now........
Click to expand...
Click to collapse
If the device won't boot past the splash screen, chances are the issue is kernel related. For kernel related issues, the ONLY method provided by HTC via their unlock is to use fastboot to boot the recovery. This is the only accessible mode HTC grants write access to the kernel partition.
This is the only way HTC provides write access to the kernel for a device that is not booting properly. The command using fastboot is as follows: fastboot boot c:\recovery.img .
This command will temporarily load the custom recovery with kernel write access allowing a proper recovery to take place.
One reason the device is not booting could be the android OS version mismatches with the kernel, therefore the kernel's ramdisk is looking for files which are not present and cause the device to either freeze or reboot.
There are other reasons too, probably too many worth detailing out as the easiest route to solving the issue is to restore back to a known good working nandroid or cleanly load another known working ROM/kernel combination.
Hope that helps clarify! Best of luck!
Thanks to all you guys. Got it back running XDA is the best.
sent from my Rooted & Boosted 3VO.

I might have messed up

Guys,
I followed this guide to unlock my phone and gain superuser access step by step:
http://forum.xda-developers.com/showthread.php?t=1239821
I then installed Rom Manager, and restarted in Recovery.
I placed this zip: http://forum.xda-developers.com/showthread.php?t=1421065 onto my SD Card, and did not rename it. Once in recovery I installed that ROM. It installed with no errors however now the phone gets stuck at the htc logo screen.
Any thoughts?
What was contained that .zip file you flashed, and did you make a backup of your system before you flashed?
Sent from my Droid Razr Maxx
Did you wipe data cache and dalvik? If not wipe again. If it bootloops again try pushing the kernel with fastboot.
Sent from my PG86100 using Tapatalk
The .zip contains the following files:
data
devices
kernel
META-INF
sdcard
system
CHANGELOG
check_data_app
mike, can you tell me how to push the update with fastboot, I'm kind of new to all of this telephone wizardry
I can get into FASTBOOT/HBOOT/RECOVERY, however nothing I do seems to help me get past the HTC Logo. Any thoughts? Maybe I'm not waiting long enough? Can someone please tell me exactly what I need to do (if I can even do something). I might just be approaching this whole process the wrong way.
Do I install a ROM from ZIP from Recovery? Do I need to fastboot an .img file first?
Sounds like your hboot 1.5 and your phone is hanging due to you need to place a copy of your recovery in your adb folder...
The while in Hboot
Using adb with phone plugged in and debug turned on
fastboot boot recovery.img
Then wipe and flash the rom you were trying to flash...
You can't just flash a rom with recovery since your s-on
Two methods
One is fastboot boot recovery.img which is easy
Other is boot.img pain in the ass
I tried booting directly into recovery like you just said. I am using TWRP recovery.img file.
Can this be caused by the type of ROM that I am trying to install?
Everything works fine, the .zip gets applied and seems to install correctly, but it still hangs at the htc logo.
I also forgot to mention that originally I used Clockwork Recovery Mod, which i got from the market, and selected the option to boot into recovery. I don't know if that makes any difference.
You should Google shooter ruu. Get back to stock. Retry this with another shot at reading the instructions.
You must plug your phone into pc while in fastboot and give it a command to boot recovery recovery.img .
Then reflash a rom.
Read more I'm hboot 1.4 and I can still flash a 1.5 hboot correctly cause I've read how to.
Sent from my PG86100 using Tapatalk
If u haven't figured it out yet, see if this helps:
[Guide] My Hboot 1.50 HTC Unlock/recovery/rom/kernel flashing notes http://forum.xda-developers.com/show....php?t=1495358
If u have updated your phone to the newest radio in the 2.17.651.5 update you may have problems if the Rom is based on an earlier kernel/radio like I think Warm is, but I could be wrong.
You may have flashed the Rom incorrectly & not had the kernel get flashed causing the boot loop.
Sent from my "Up all night, sleep all day" Evo3D via Tapatalk.

plz help

after install rom ,the device is rebooting always like that
hboot-1.94.0012 s-on gsm
RUU_Shooter_U_HTC_ARA_1.24.415.6_Radio_10.59.9020.00_10.15.9020.06_M_release_220917_signed
We need a lot more info. What hboot? What rom? Cdma or gsm evo? What recovery? Did you do a full wipe?
We're comin from a pure power source.
From and educated guess I would say you are S-On and failed to flash the kernel via "fastboot flash boot boot.img" in fastboot mode.
as-mol said:
after install rom ,the device is rebooting always like that
Click to expand...
Click to collapse
I guess you are htc unlocked and havent flashed the kernel seperately via fastboot.........or you havent wiped the previous rom.
bootloop
and also need to know what custom recovery you installed sounds like you lost your Boot.IMG if so you will need to exract it from the zip folder of the rom that you have install and then go to that folder and scrool down until you come to the Boot.IMG and copy and past it in same floder that you used to install your su file using command promts and typ fastboot flash boot boot.img

[Q] (BIG Problem/Question) Error after ROM Install. Please help.

i have been running Synergy Rom and causing a lot of problems so I have been tryin to install a numerous amount of roms and after wiping the phone back to factory and the dalvik then when its time to reboot the system i reboot the phone it just stays in the HTC boot up screen. so after a wait 10 or so min i just reload the Synergy rom which is the only one that works.
i am also running Revolutionary CWM v4.0.1.4 if that helps
i would really appreciate it if someone could point me into the right the direction thank you.
Are you on hboot 1.5? Are you flashing the correct kernel?
We're comin from a pure power source.
Yes it is and to be honest I haven't flashed them with any kernels cuz I never have before
Hmmmm, and you're doing a full complete wipe right? Which recovery are you using
We're comin from a pure power source.
Revolutionary CWM v4.0.1.4 and yes full wipe and dalvik.
Have you tried a different recovery?
We're comin from a pure power source.
nspyr05 said:
i have been running Synergy Rom and causing a lot of problems so I have been tryin to install a numerous amount of roms and after wiping the phone back to factory and the dalvik then when its time to reboot the system i reboot the phone it just stays in the HTC boot up screen. so after a wait 10 or so min i just reload the Synergy rom which is the only one that works.
i am also running Revolutionary CWM v4.0.1.4 if that helps
i would really appreciate it if someone could point me into the right the direction thank you.
Click to expand...
Click to collapse
ok as you know the roms come as .zips and we apply them through recovery.... some times that recovery doesnt writ the boot img correctly.... try installing ANY rom....then try to boot up... if it hangs at htc then pull the battery out then put it right back in and hold vol down and press power..then connect the phone to your computer so on your phone you see "fastboot usb"now the rom you tried installing that was the zip have a copy of that on your computer and open up with any program you use to open zips...extract that boot.img file to your fast boot file and where adb is too ,once extracted go back to your terminal window and type in
fastboot flash boot boot.img
it should say that its sending the data then writing it and then from there wait about 30 seconds and then select reboot and the rom should boot up
nspyr05 said:
Yes it is and to be honest I haven't flashed them with any kernels cuz I never have before
Click to expand...
Click to collapse
You cannot directly install ROMs with custom kernels on hboot 1.5 .
You always have to use "fastboot boot <your recovery>.img" or "fastboot flash boot boot.img" like the above post says..... If you dont use PC to flash ROMs with custom kernels , you will always get stuck on the HTC screen.
If you want to be able to flash ROMs / kernels / radios etc without PC, downgrade your hboot from 1.5 to 1.4.
Get flash image GUI from market to bypass fast boot and install custom kernels, or downgrade using unbeknownforce method and closeones live cd
Sent from my PG86100 using xda premium
Are you s off and if your knott you may need to use the GUI app from the market
Sent from my HTC EVO 3D X515m using xda premium
Idk if someone already said this but for 1.5 boot you need to go into fasboot usb . Fastboot boot recovery.img
Replace "recovery" with recovery file name. If your using 4.0.1.0 it might be. Cwm-4.0.1.4-shooter.img something like that
Second option is use 4EXT and you won't need to use your computer to flash rooms or kernels
Sent from my PG86100 using Tapatalk
First I assume you have the adb drivers.
place new rom on sd card
boot phone in bootloader, select fastboot
Access the adb folder via CMD
type in fastboot boot recovery.img
it should say waiting for device then connect..
you'll see the recovery screen
this will let you wipe and install new rom on hboot 1.5

[Q] Phone freezes on HTC boot screen after restore

Hey guys
I've only just got into this stuff so please forgive my ignorance, but I need a hand understanding what might have gone wrong. I've got a GSM Evo 3D which I've unlocked through htcdev, phone is still S-ON, hboot 1.53.007. I flashed CWM recovery but have since switched to 4ext.
I downloaded Viper3D, ran a backup using 4ext recovery so I could go back to stock when I feel like it, then flashed the new ROM to test it out (mainly just testing the process). The phone booted fine - no problem. On that success, I went to restore the backup I made before flashing Viper3D. The restore completed successfully from 4ext recovery, but on trying to boot my phone it just hangs on the first HTC boot screen.
Tried rebooting a few times, tried restoring a second time, did wipe/factory reset first, tried clearing cache and dalvik cache, still just hangs on that HTC boot screen. I probably left it for about 20 minutes on that screen but it didn't go anywhere.
I flashed Viper3D again, and it worked again and my phone boots up fine. So the question is, what's going wrong when I try to restore my original backup? I haven't upgraded hboot or changed the kernel.
Would appreciate if someone could shed some light on this, cheers.
Ok so I think I've figured it out but could still do with a little clarification from someone.
I've read around and found that people have fixed the HTC screen hang by flashing the boot.img with fastboot from the PC, so I decided to give it a go. I copied the boot.img from my original backup to my PC, then booted the phone up into 4ext recovery and restored the backup. After restoring had completed, I rebooted into fastboot and hooked up to my PC, then flashed the boot.img from there. Once that was done, disconnected the phone from the PC and rebooted and the phone booted up fine into my stock ROM.
One thing I noticed when flashing Viper3D is that immediately after flashing, the phone would boot to the HTC screen, then reboot a second time by itself. I now understand this is where 4ext is flashing the boot.img with Smartflash, and it didn't reboot this second time when I was trying to restore my backup so I'm guessing that's where the problem lies.
So it looks to me like 4ext/Smartflash is not doing the whole process for some reason, perhaps a bug? Smartflash is enabled permanently on my phone, so I can't think of another reason why it didn't work except that it's bugged.
Can anyone confirm this issue or have any other comments? Cheers.
zaphodalive said:
So it looks to me like 4ext/Smartflash is not doing the whole process for some reason, perhaps a bug? Smartflash is enabled permanently on my phone, so I can't think of another reason why it didn't work except that it's bugged.
Can anyone confirm this issue or have any other comments? Cheers.
Click to expand...
Click to collapse
Read the requirements for the SmartFlash feature to work on the OP of the 4EXT Recovery thread, and in particular the limitations section. My guess is that you didn't have a bootable kernel when trying to use the SmartFlash option.
An easier way to re-flash the ROM in that situation is to start recovery with this fastboot command:
fastboot boot recovery.img (where recovery.img is the name of your 4EXT recovery file)
Click to expand...
Click to collapse
That command will boot any custom recovery in a mode that will let it flash the entire ROM from recovery, but for 4EXT you have to make sure that the SmartFlash/S-ON option is disabled in the tools menu and then flash the ROM zip file.
ramjet73
Ok thanks, just to clarify - by doing fastboot boot recovery.img, that would reboot the phone into 4ext recovery and allow it to flash both boot.img and recovery.img when flashing the ZIP? What exactly is the fastboot command doing that allows this?
Cheers
zaphodalive said:
Ok thanks, just to clarify - by doing fastboot boot recovery.img, that would reboot the phone into 4ext recovery and allow it to flash both boot.img and recovery.img when flashing the ZIP? What exactly is the fastboot command doing that allows this?
Cheers
Click to expand...
Click to collapse
The "fastboot boot" command starts the recovery as an OS image and just like Android it has the ability to flash the boot partition (kernel) when loaded that way. When started in the "recovery" mode it is not able to flash the boot partition when the phone is S-ON.
SmartFlash uses the same principle to flash the boot partition after the existing kernel is booted, but if the current kernel is not bootable SmartFlash doesn't work.
ramjet73
Ok, I kinda understand (without quite understanding)... can the same command be used for flashing ROMs in a ZIP? e.g. fastboot boot yourromhere.zip
Thanks
zaphodalive said:
Ok, I kinda understand (without quite understanding)... can the same command be used for flashing ROMs in a ZIP? e.g. fastboot boot yourromhere.zip
Thanks
Click to expand...
Click to collapse
No. The "fastboot boot" command only works with bootable images and not zip files.
ramjet73
Thanks very much for your help. A couple of final questions...
How can you flash a custom ROM in a ZIP with fastboot? e.g. the Viper3D ZIP didn't have a recovery.img, only a boot.img
Also, I'm downloading Cool ICS and CoolZ kernel, and this is my first time flashing a kernel. Checked the CoolZ ZIP file and there's no boot.img which I was expecting, so I'm hoping that 4ext won't have any problems flashing it..? Also not sure whether to flash CoolZ or Cool ICS first.
Cheers
The fastboot commands are part of the bootloader (hboot) and custom ROM's are flashed by recovery.
There are guides in the general forum that cover ROM flashing procedures including this one by mpgrimm2.
ramjet73
Thanks, getting stuck installing the CoolZ kernel. I rebooted into 4ext with fastboot boot recovery.img, disabled Smartflash, tried flashing the ZIP, and after extracting files I got the error message:
assert failed: write_raw_image(" /tmp/newboot.img", "boot")
I assume this means it failed writing to the boot partition... any thoughts why?
zaphodalive said:
assert failed: write_raw_image(" /tmp/newboot.img", "boot")
I assume this means it failed writing to the boot partition... any thoughts why?
Click to expand...
Click to collapse
If the assert fails that usually means you are trying to flash something that's not intended for your device. Make sure you are flashing the correct version since there are CoolZ kernels for both the CDMA and GSM Evo 3D models.
Edit: I just checked and it looks like the CoolZ v4.5 kernel has one installation file for both Evo 3D models.
Make sure you can boot into the ROM you flashed before you try to flash the kernel.
ramjet73
Ok, a little weird...
I tried installing the CoolZ kernel, that failed (as mentioned before), then I installed the v14 ROM and v14b update. Booted up the phone, had no WIFI (just said error). So I flashed the boot.img from the v14b ZIP after that to see if I'd get WIFI back, got a couple of bootloops on the splash screen, and it then booted up with WIFI working and the CoolZ kernel installed.
I originally downloaded the CoolZ kernel separately from the Cool ICS ROM, but it appears that the kernel is part of the ROM package so I didn't need to do that.
Anywho, seems to be working now so I'll have a fiddle around. Thanks very much for your help.

Categories

Resources