Related
OK so I have the Sprint EVO 4G LTE with 1.22.651.3 on it, rooted, S-ON. I have the Team Win Recovery Project v.2.1.8 on it as well with hboot 1.15. I tried loading the newest rooted software 2.13.651.1 710RD and voila.... paperweight. I tried reloading 1.22.651.3 and nothing. I can still boot to the bootloader and TWRP recovery, but nothing seems to work and now because sprint screwed up and removed my total equipment protection service from my plan, I don't have insurance on the phone. PLEASE HELP!!!
You just need to flash the kernel, extract it from the Rom (boot.img) and place it in adb folder, connect phone I'm bootloader and type fastboot flash boot boot.img
You can also flash meanrom, it has a working kernel installer, just let it sit because the kernel installer does take awhile 5-10 minutes
om4 said:
You just need to flash the kernel, extract it from the Rom (boot.img) and place it in adb folder, connect phone I'm bootloader and type fastboot flash boot boot.img
You can also flash meanrom, it has a working kernel installer, just let it sit because the kernel installer does take awhile 5-10 minutes
Click to expand...
Click to collapse
Can you explain how to do this in greater detail? I'm experienced only enough to be dangerous to myself lol
This program should install the kernel that you need. If not you are supposed to be able to swap boot.img files that it will install.
http://forum.xda-developers.com/showthread.php?t=1917106
http://forum.xda-developers.com/showthread.php?t=1752270
This is for the One S but it's the same process for our phones also.
Sorry I've been in a low coverage area and just got home. Open the Rom, extract the boot.img, open adb folder or SDK, hold shift and right click, select open command window here, connect phone in fastboot and type fastboot flash boot boot.img
So I tried to use that program to flash the boot.img from the fastboot screen but the computer wouldnt connect to the phone... now what?
Boot from system into hboot and fast boot while plugged in via USB. Helps your PC determine drivers.
Also, if you need a guide for setting up adb/fastboot, Google a YouTube vid by qbking77 on how to unlock galaxy nexus bootloader, it links to a great tutorial.
from my flying AOKP'd Evo LTE and xda premium
do you have SDK installed on your computer? If not install it. Go through the setup (set up your your environment variables) for fastboot.
Make a copy of the boot.img from a ROM of your choice. Place it in a folder on your desktop name the folder (android) leave the folder open.
Open cmd
Type cd Desktop press enter
Type cd android press enter
Type fastboot flash boot boot.img
After that it should say sending then OK
After that go into recovery then flash the ROM
you should be good to go then...
Sent from my EVO using xda app-developers app
The full SDK is not necessary, just the debug tools
ADB Tools
Also you can directly open the command prompt from within the folder by holding shift and opening the context menu (shift+right click) then select open command window here
i keep getting a message in windows "usb device not recognized" so i switched usb cables and finally got that program to load the boot.img file, then flashed a rom in bootloader but its still not booting... any ideas?
Did you make sure to wipe the phone first? What rom are you trying to flash?
wiped phone first and now trying to flash 2.13.651.1 after loading boot.img thru that program
you have to find a way to update your twrp to version 2.2.0 cause this is the culprit that gave you the issues. did you make a backup try doing a restore to get back up and running then download goomanager from the google play store and install the latest twrp here is a video to update to the latest twrp through goomanager.
twrp downloads I dont know if you have to be s-off to install in bootloader or not. maybe someone could clarify that
ok so i tried flashing twrp 2.2.2.0 and got a message saying "main verison is older" then it said "update failed!" which is weird since i had version 2.1.8.0 to begin with i think.
anyone? any ideas? I feel like my only resort is to have it replaced
You could fastboot flash the recovery image. Thats how I usually do it
So download the recovery image from twrp website and place it in your a dB folder. I don't have my PC but I think the command is fastboot flash recovery "recovery image"
Sent from my EVO using xda premium
corcgaigh said:
You could fastboot flash the recovery image. Thats how I usually do it
So download the recovery image from twrp website and place it in your a dB folder. I don't have my PC but I think the command is fastboot flash recovery "recovery image"
Sent from my EVO using xda premium
Click to expand...
Click to collapse
this should be the correct code to type
fastboot flash recovery openrecovery-twrp-2.1.8-jewel.img
Or
fastboot flash recovery openrecovery-twrp-2.2.2-jewel.img
Depending on how twrp names their recovery image
Sent from my EVO using xda app-developers app
Ok so i updated the twrp by changing the txt file to the proper software number.... then i flashed the lastest software version and NOW IT STARTS!!! WOOOHOOO!!!! Thanks everyone!!
I rooted my htc evo 4g lte and have twrp installed, and tried to flash a rom, when i rebooted it always takes me back to hboot screen and is stuck there, won't actually boot up. I am able to go to recovery and use twrp including usb mount (maybe a zip i could flash to help). I have searched for awhile but haven't found any real solution for my phone yet.
I have S-on, no external sd card.
If you need any more info just ask.
Thanks in advance for the help!
Extract the boot.img from the rom, place it in adb folder and put phone in fastboot
Type fastboot flash boot boot.img and restart the phone
solved!!!!!!!
om4 said:
Extract the boot.img from the rom, place it in adb folder and put phone in fastboot
Type fastboot flash boot boot.img and restart the phone
Click to expand...
Click to collapse
Thankyou so much for the fast reply, and fix!! I did what you said and it worked! The funny thing is that it was my first flash, is there something i did or should avoid to have this happen to me again? Any way I am so grateful and now am going to try out team venoms viper4g 2.0.2 new rom!
If others have the same problem and want more detailed info about what I did:
1. downloaded sdk manager developer.android.com/sdk/index. html opened the program and installed platform tools
2. Since I have twrp I put into recovery and mounted usb found the zip of the rom i wanted to flash opened it found the boot.img and copied it to the folder where platform tools where installed (C:\Users\yourname\AppData\Local\Android\android-sdk\platform-tools)
3. got back to hboot screen
4. opened cmd to the folder by typing: cd then file path like mine above
5. then in cmd typed fastboot flash boot boot.img it will do its thing
6. restart phone and hopefully work for you too!
vipomorge said:
Thankyou so much for the fast reply, and fix!! I did what you said and it worked! The funny thing is that it was my first flash, is there something i did or should avoid to have this happen to me again? Any way I am so grateful and now am going to try out team venoms viper4g 2.0.2 new rom!
If others have the same problem and want more detailed info about what I did:
1. downloaded sdk manager developer.android.com/sdk/index. html opened the program and installed platform tools
2. Since I have twrp I put into recovery and mounted usb found the zip of the rom i wanted to flash opened it found the boot.img and copied it to the folder where platform tools where installed (C:\Users\yourname\AppData\Local\Android\android-sdk\platform-tools)
3. got back to hboot screen
4. opened cmd to the folder by typing: cd then file path like mine above
5. then in cmd typed fastboot flash boot boot.img it will do its thing
6. restart phone and hopefully work for you too!
Click to expand...
Click to collapse
If you are s-on, the kernel won't flash with the rom so you have to flash it separately like om4 showed you. Some roms, like MeanRom have modified their install script to automatically load the kernel to avoid this extra step.
The latest Mean installer failed for me, as did the latest Viper, something to keep in mind if you try those and they don't boot
if you haven't read my last thread here is my issue.
my pc won't read my phone because it say "failed to open usb master mode"
i can access bootloader and twrp but i cant usb anything.
my pc will say mtp driver install failed
so my question is what do i need to download for adb fastboot? programs, drivers, all i need since the auto install from my phone isn't working. and if all possible link me to it. ive been up 14 hours straight trying to search every where on what to do but im coming up with nothing. just people saying install and reinstall......so far only clonz tried to help me. i tried sideloading but i didnt know i needed to abd fastboot....tried installing adt from a google search android sdk but eclipse is saying im missing a java file. what the hell am i suppose to do? where does all the adb files/sdk stuff go? im lost already.
Are you trying to copy something to the phone while it's booted up? If yes, you dont need adb/fastboot, only the correct drivers. If you are trying to flash a Kernel, you have to use fastboot. To do this, download the sdk, install it and all the necessary things from the SDK Manager. Then open the command prompt (as admin) and navigate to the folder where fastboot.exe is (probably smth like C:\Program Files\android-sdk\platform-tools). Make sure your boot.img (the kernel) is also there. Boot the phone into the bootloader, then connect it per usb and type
"Fastboot erase cache (optional)
Fastboot flash boot boot.img"
And reboot
Sent from my HTC One X+ using xda app-developers app
s3nsation said:
Are you trying to copy something to the phone while it's booted up? If yes, you dont need adb/fastboot, only the correct drivers. If you are trying to flash a Kernel, you have to use fastboot. To do this, download the sdk, install it and all the necessary things from the SDK Manager. Then open the command prompt (as admin) and navigate to the folder where fastboot.exe is (probably smth like C:\Program Files\android-sdk\platform-tools). Make sure your boot.img (the kernel) is also there. Boot the phone into the bootloader, then connect it per usb and type
"Fastboot erase cache (optional)
Fastboot flash boot boot.img"
And reboot
Sent from my HTC One X+ using xda app-developers app
Click to expand...
Click to collapse
some odd reason when i wiped to to a new rom it like wiped everything and keep saying no os installed. so i never use adb so i dont know what to download and my mtp driver isnt installing properly
I guess you wiped data and it wiped the internal storage too. And now you cant install a rom. I'm not an expert but I guess you could try extracting a rom zip and flash every partition since sideload doesn't seem to work. Better ask a dev about that one, though..
P.s. dont wonder about the "thank", I accidentally pressed it
Sent from my HTC One X+ using xda app-developers app
EDIT: Do you have TWRP recovery? If yes, boot into recovery, select "advanced", then "sideload". Now open cmd again, navigate to adb and type:
"adb sideload rom.zip" (replace rom.zip with the name of your rom file)
Note that the rom.zip must be in the same folder as adb.
Wont be able to write anymore 2day, gotta go sleeping, sry (europe ). I hope this works though..
sideloading as we speak!!!!! hope it works!!!!! taking a long time though
Flipnfr3ak said:
sideloading as we speak!!!!! hope it works!!!!! taking a long time though
Click to expand...
Click to collapse
Not sure if you have fixed your problem but this http://forum.xda-developers.com/showthread.php?t=2051032 might help...even if you don't know what you are doing
Cheers!
Clonz said:
Not sure if you have fixed your problem but this http://forum.xda-developers.com/showthread.php?t=2051032 might help...even if you don't know what you are doing
Cheers!
Click to expand...
Click to collapse
found my problem......i didnt have android sdk installed properly....once i reinstalled everything( java, sdk, htc sync, some other things) i was able to follow your TUT no problem!!!! thanks clonz!!! sideloading is awesome
Flipnfr3ak said:
found my problem......i didnt have android sdk installed properly....once i reinstalled everything( java, sdk, htc sync, some other things) i was able to follow your TUT no problem!!!! thanks clonz!!! sideloading is awesome
Click to expand...
Click to collapse
Glad to help man
Cheers!
Alright, so i have an EVO 4g lte and i attempted to root it today. It didnt turn out very well to say the least... I unlocked bootloader and flashed TWRP recovery.I then flashed superSU, and at the same time i flashed a custom rom and gapps zip. Then hit reboot. It has not booted up since.. It will just sit at the white HTC screen. i tried clearing cache and Dalvik cache, also did a factory reset. tried flashing cm10 rom onto the device as well as a rooted stock rom. nothing works! the farthest i have gotten was with the cm10 rom and it went to the cyanogenmod boot logo but was in bootloop still. I downloaded the ADT tool bundle but the phone wont show up on the device list. Can anyone help? im completely stumped.. Im fairly new to rooting and custom roms, but i have rooted multiple tablets and samsung galaxy phones and havent had any issues. this is my only phone also, i just gave my backup to my mother because her phone broke... please if anyone knows how to fix this let me know. when i boot into recovery mode it says Tampered and Unlocked at the top as well as S-On. I can also go into TWRP recovery with no problems. just cant use fastboot with my computer (windows 7 PC).
I am pretty sure i know what i did wrong, I flashed SuperSU to gain root at the same time i flashed the custom rom and gapps.. on all the other devices i would reboot after root and then flash the custom rom seperately.. but is there a way to correct my mistake?
Since you are s-on you have to fastboot flash the boot.img/kernel first and then flash CM and gapps
Any questions PM me
OK sorry to be a noob but how do I do that? I used cmd.exe while rooting but now it won't recognize my device. Much thanks for any help!!
Sent from my GT-P5110 using xda app
If in bootloader type fastboot devices
In recovery type adb devices
See if you get a reply
In fast boot USB menu on the phone, I typed fastboot devices on cmd and it came up blank.
Sent from my GT-P5110 using xda app
Sounds like a driver issue
1.Uninstall everything HTC from your PC
2.Reboot your PC
3.Plug your phone in and it will load a bunch of drivers
4.Try the command again
If that does not work get the latest drivers from HERE use the ones dated 6/6/13
and don't forget the BMP drivers towards the bottom of post 1
bigdaddy619 said:
Sounds like a driver issue
1.Uninstall everything HTC from your PC
2.Reboot your PC
3.Plug your phone in and it will load a bunch of drivers
4.Try the command again
If that does not work get the latest drivers from HERE use the ones dated 6/6/13
and don't forget the BMP drivers towards the bottom of post 1
Click to expand...
Click to collapse
ok ill uninstall all that and give it a try. is pm a better contact method for you?
AUSRA15 said:
ok ill uninstall all that and give it a try. is pm a better contact method for you?
Click to expand...
Click to collapse
Here is fine
bigdaddy619 said:
Here is fine
Click to expand...
Click to collapse
OK rebooting now I'll see if it uninstalled everything.
:fingerscrossed:
OK were connected now, now what? :good:
PC and phone are talking ?
fastboot devices
yes they are talking now. fastboot devices and my phone shows up.
i tried fastboot flash boot.img but it wont recognize the command, i placed the boot.img file into the platform-tools folder inside my C drive. what am i doing wrong? its late at night and im frustrated so i know im screwing something up...
ok good BTW which version of twrp are you using? Let me know before you continue.
pull the boot.img from the rom zip and copy it to the folder you opened your cmd window from
then type fastboot boot boot.img
once it says successful press the power button to return to HBOOT and use the vol keys to navigate to recovery
Once there choose wipe and wipe cache/dalvik cahce/system/data or factory reset depending which version of twrp you are using
then flash CM and gapps
C:\Users\Corey>fastboot boot boot.img
cannot load 'boot.img': No error
thats what i typed in and thats what it said back to me. not quite sure what the problem is.
the boot.img is placed in the same folder as the fastboot application
AUSRA15 said:
C:\Users\Corey>fastboot boot boot.img
cannot load 'boot.img': No error
thats what i typed in and thats what it said back to me. not quite sure what the problem is.
the boot.img is placed in the same folder as the fastboot application
Click to expand...
Click to collapse
try fastboot flash boot boot.img
My bad I was looking at a buddies thread for the commands
bigdaddy619 said:
try fastboot flash boot boot.img
My bad I was looking at a buddies thread for the commands
Click to expand...
Click to collapse
same thing, cannot load unknown error. also i am using twrp 2.6.0.0
Ok lets try something different at least it will get you up and running
Get twrp v2.4.1.0 from http://techerrata.com/browse/twrp2/jewel
put it in the same folder you are using and we will downgrade your twrp for now
copy and paste this in the cmd window
fastboot flash recovery openrecovery-twrp-2.4.1.0-jewel.img
then fastboot erase cache
ok got the twrp done succesfully as well as the wipe cache. whats next? i think i figured out what i was doing wrong, i hadnt opened the file directory. cd downloads, cd android files, etc.
should i try going into recovery now on the phone and flash a rom, or should we stay on fastboot and push the boot.img?
Easiest way to open a cmd window is to press shift and right click inside the folder and choose open cdm window here
That way you know you are in the correct folder.
Yeah go ahead and try to flash the boot.img again
I'm pretty inexperienced with rooting.. I think I may have messed my brother's phone up. I rooted his rezound and got cwm recovery working. I tried to flash a "TACHYON-1.2.zip" rom I found here and now it won't boot past the white background with green htc screen when I try to boot the phone. Please help me try to fix this! I can still boot into cwm recovery.
[EDIT] When I wipe data/factory rest it says error mounting /sdcard/.android_secure!
This was probably a mistake but I'm freaking out. I put CleanROM Standard 4.5.zip from here https://www.copy.com/s/uYOSaNCntCvx/CleanROM on another sd card and installed it after tying to wipe again. Now it boots past the htc screen and the CleanROM screen boots for a minute, then sticks..
Cap'n Jazz said:
I'm pretty inexperienced with rooting.. I think I may have messed my brother's phone up. I rooted his rezound and got cwm recovery working. I tried to flash a "TACHYON-1.2.zip" rom I found here and now it won't boot past the white background with green htc screen when I try to boot the phone. Please help me try to fix this! I can still boot into cwm recovery.
[EDIT] When I wipe data/factory rest it says error mounting /sdcard/.android_secure!
This was probably a mistake but I'm freaking out. I put CleanROM Standard 4.5.zip from here https://www.copy.com/s/uYOSaNCntCvx/CleanROM on another sd card and installed it after tying to wipe again. Now it boots past the htc screen and the CleanROM screen boots for a minute, then sticks..
Click to expand...
Click to collapse
You need to extract and flash the boot.img file from the ROM zip separately via fastboot. Extract the file and place it in an easy to access place on the drive (like same place as fastboot/adb) , then after flashing the ROM reboot into hboot and start fastboot, and use:
fastboot flash boot boot.img
Then reboot and be patient, sometimes the first boot seems to take forever.
Sent from my Nexus 4 using Tapatalk
acejavelin said:
You need to extract and flash the boot.img file from the ROM zip separately via fastboot. Extract the file and place it in an easy to access place on the drive (like same place as fastboot/adb) , then after flashing the ROM reboot into hboot and start fastboot, and use:
fastboot flash boot boot.img
Then reboot and be patient, sometimes the first boot seems to take forever.
Click to expand...
Click to collapse
Thank you for the reply, and sorry if I ask too many questions, but how exactly do I flash the boot.img file? In CMD? There isn't a flash option in my fastboot section of the phone, just BOOTLOADER, REBOOT, REBOOT BOOTLOADER and POWER DOWN.
http://img854.imageshack.us/img854/6248/ismh.png
This is how far I got in cmd if I'm headed in the right direction at all..
Cap'n Jazz said:
Thank you for the reply, and sorry if I ask too many questions, but how exactly do I flash the boot.img file? In CMD? There isn't a flash option in my fastboot section of the phone, just BOOTLOADER, REBOOT, REBOOT BOOTLOADER and POWER DOWN.
This is how far I got in cmd if I'm headed in the right direction at all..
Click to expand...
Click to collapse
You start fastboot in the phone, that puts it in a mode to enter fastboot commands from a PC... You Don't do anything in the phone in fastboot, you use the fastboot command that is part of the ADB package. The same way you would have unlocked the phone on HTCdev.com to allow root or CWM to be installed.
Sent from my Nexus 4 using Tapatalk
To borrow from the CM11 thread.
- Place the boot.img into the platform-tools folder of the Android SDK's install directory.
- Boot to the bootloader.
- Ensure your device is connected to your computer and that your device is now in fastboot mode. This is a white screen and it says fastboot on it.
- Open a Terminal (OSX or Linux) or CMD window (Windows) and cd to the platform-tools directory of the Android SDK's install directory.
- Issue this command to flash the boot.img we placed in the platform-tools folder earlier:
Code:
fastboot flash boot boot.img
- Watch the output of the terminal, it should say something like "sent successfully".
- Finally send this command:
Code:
fastboot reboot
Since you're s-on, you'll need to do this whenever you install a new rom.
mjones73 said:
To borrow from the CM11 thread.
- Place the boot.img into the platform-tools folder of the Android SDK's install directory.
- Boot to the bootloader.
- Ensure your device is connected to your computer and that your device is now in fastboot mode. This is a white screen and it says fastboot on it.
- Open a Terminal (OSX or Linux) or CMD window (Windows) and cd to the platform-tools directory of the Android SDK's install directory.
- Issue this command to flash the boot.img we placed in the platform-tools folder earlier:
Code:
fastboot flash boot boot.img
- Watch the output of the terminal, it should say something like "sent successfully".
- Finally send this command:
Code:
fastboot reboot
Since you're s-on, you'll need to do this whenever you install a new rom.
Click to expand...
Click to collapse
Thank both of you so much! I'm sorry I had to have you completely spell it out for me, but I appreciate the help and this forum in general so much!
I hate to bring this thread back, but it's the best place to ask about my problem. I'm trying to switch from Clean Rom on an HTC Rezound to Venasaur Rom v3.2.0 because I read that it will work with a Straight Talk sim. I tried installing with ClockWork and I get the new rom's boot screen, but it won't boot past that. I don't know what I'm doing wrong. I would really appreciate it if somebody could help me out again!
Did you flash the boot.img this time? I would suggest after you get booted, trying rumrunner to go S-off... It saves sooo much time... I'm always switching between multiple ROMs because I'm s-off....
Sent from my HTC EVO 4G Running AOKP 4.2.2
Cap'n Jazz said:
I hate to bring this thread back, but it's the best place to ask about my problem. I'm trying to switch from Clean Rom on an HTC Rezound to Venasaur Rom v3.2.0 because I read that it will work with a Straight Talk sim. I tried installing with ClockWork and I get the new rom's boot screen, but it won't boot past that. I don't know what I'm doing wrong. I would really appreciate it if somebody could help me out again!
Click to expand...
Click to collapse
... you should remember one thing for sure. Because you are s-on whenever you flash any custom rom, you have to flash its corresponding boot.img file in fastboot separately otherwise you are gonna get bootloop ...
---------- Post added at 11:50 AM ---------- Previous post was at 11:49 AM ----------
... and yeah. you should try to get s-off as you are already been suggested above ...