first off, I'm an idiot with this whole thing and shouldn't be doing it probably. i just don't know enough about it to be playing with expensive phones like this so i understand I deserve whatever i get.
i was running a custom rom on an S-ON phone. i forgot the name of the rom (was made by TEAM COOL or something). But I wanted to unroot and go back to normal stock ROM and download the JB update. First, in the SU app, I did a complete unroot. that did nothing except not let me use the app anymore.
then I tried doing the RUU way of going back, but when it would go to the loading bootloader portion, the usb would disconnect and it would fail with error 171.
so then, and i don't know how i got here, but i went into recovery and did a factory reset and now i have no rom. I have tried installing meanrom but it fails after some line regarding a kernal. my phone won't do anything except boot to the white HTC screen or into the bootloader.
i have no idea what to do, I just want it working at this point.
i've been searching forums like crazy but all the solutions are things I already have done or things that won't work for me.
If you haven't done so yet, you need to relock the bootloader before running ruu. Put your phone in fastboot and using SDK or ADB Tools, type fastboot oem lock
om4 said:
If you haven't done so yet, you need to relock the bootloader before running ruu. Put your phone in fastboot and using SDK or ADB Tools, type fastboot oem lock
Click to expand...
Click to collapse
thank you for your help! however, whenever i do this, it just says < waiting for device >
so i finally got a rom to install--clean rom. that is the one i used to have. but when i reboot, it gets stuck on a black screen and won't go any further.
I had the same thing happen. Had to run a boot.img flash utility i found on another thread elsewhere on xda. The flash utility was updated for jb. If i can locate where i found it then i will get back to you.
Sent from my EVO using Tapatalk 2
I was curious if you ever found that rom or if anybody can help me? The phone is still out of commission. It's been tough to make it through the holidays especially since my laptop was stolen the very next day that all this happened
bump again. I'm assuming the phone is bricked for good if the brightest minds on the subject don't even know
i'm using my dad's old evo 4g for now.
unclefarkus said:
bump again. I'm assuming the phone is bricked for good if the brightest minds on the subject don't even know
i'm using my dad's old evo 4g for now.
Click to expand...
Click to collapse
Have you tried meanbean? It has the boot.img flash tool baked in for s-on, just follow the instructions to the tee in the OP... It's in the Android development thread... Good luck
Sent from my EVO using xda app-developers app
Sounds like you need to flash a Rom that has the s-on installer or fastboot flash the kernel for the Rom you have installed
Most roms come with the kernel installer built in now days. just keep trying to flash em. fyi if your phone turns on , even a little bit , you are not bricked
I am trying to flash meanbean. I wiped the cahes and did factory reset, then flashed the ROM. It's been on "Installing /system..." for about 30 minutes now. Something seems wrong. I'm scared to interrupt it in case that's normal or if interrupting it will break it for good.
Well, I think that might be because my twrp version is really old...2.1.8. I tried updating but had no luck.
Now nothing flashes. It gets to 'verifying partition sizes' then fails. Tried this on several roms that would previously flash, just not work.
unclefarkus said:
Well, I think that might be because my twrp version is really old...2.1.8. I tried updating but had no luck.
Now nothing flashes. It gets to 'verifying partition sizes' then fails. Tried this on several roms that would previously flash, just not work.
Click to expand...
Click to collapse
Update twrp through goomanager, its in the market, then try again.
Sent from my EVO using xda premium
mrlakadaddy said:
Update twrp through goomanager, its in the market, then try again.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
lol how could he do that if he dont have any rom installed...dafuq?
You need to FASTBOOT install it:
Turn off your device. Turn on the device and keep holding volume down until a menu shows up. Select fastboot from the menu list. Plug the device into your computer. If you have the right drivers installed, your screen should now say FASTBOOT USB. Run the following command via the command line:
fastboot flash recovery TWRP.img
Boatiy said:
lol how could he do that if he dont have any rom installed...dafuq?
You need to FASTBOOT install it:
Turn off your device. Turn on the device and keep holding volume down until a menu shows up. Select fastboot from the menu list. Plug the device into your computer. If you have the right drivers installed, your screen should now say FASTBOOT USB. Run the following command via the command line:
fastboot flash recovery TWRP.img
Click to expand...
Click to collapse
Don't forget the clear cache commands
Sent from my EVO using xda app-developers app
I have given this a go, however, as I should expect by now, nothing happens.
It says "waiting for device" and that's it
Upon typing "adb devices" nothing shows up.
Furthermore, when I go to Fastboot, Fastbook usb does show up, but I get a message on the computer saying the usb device has malfunctioned.
unclefarkus said:
I have given this a go, however, as I should expect by now, nothing happens.
It says "waiting for device" and that's it
Upon typing "adb devices" nothing shows up.
Furthermore, when I go to Fastboot, Fastbook usb does show up, but I get a message on the computer saying the usb device has malfunctioned.
Click to expand...
Click to collapse
Can you get into bootloader? If so go to the TWRP website and download the hboot zip. Put on external sd card and enter bootloader.
Sent from my EVO using Tapatalk 2
Perhaps what is happening when you try oem lock and get that error is that adb is still running from a prior attempt or because of some other program. Try opening your task manager and ending all processes of adb and other programs that connect to the phone. Then try oem locking again and go from there.
Sent from my EVO using xda premium
I made a little bit of progress!
I determined that Windows 8 was the reason I get the usb malfunctioning message. I obtained a Windows 7 computer and it worked like a charm.
That said, I'm not out of the woods yet.
I relocked the phone using fastboot and then have been attempting to flash a stock RUU now that the usb issue is sorted out.
That seems to work but it gets stuck at "sending....." for as long as 35 minutes. I've tried about 4 times, giving between 20-35 minutes and it won't go beyond sending.
I can at least fastboot now; but the phone is locked. Which is fine; I just want back to stock anyways.
Tampered
Re-locked
S-On
Hboot-1.19.0000
Radio-1.12.11.0809
OpenDSP-v29-1.0.45.0622
eMMC-boot
Aug 9 2012
I flashed the 2.13.651.1 RUU by the way.
Any new advice haha?
I loaded a PJ img via sd card and it's alive and updating to JB OTA right now! Thanks for all the help over the past month folks
Related
I'm S-on. I was GB, rooted on ViperRom. Flashed .10 following Nils instructions. Everything was fine. Unlocked and tried to flash Amon Ra. The PC would not detect the phone. I deleted the PH98IMG and booted into recovery hoping the phone would be detected for adb. Now the phone is stuck at HBoot. It cannot find a PH98 since I stupidly deleted it and now I cannot get back to a working phone. Any sugestions are greatly appreciated. Thanks.
was your PC detecting the phone earlier?
Did you let the ruu make its second pass of the install? Did it boot normally before you went back to bootloader to flash a recovery? Also you have to be in fastboot menu to connect to usb
Sent from my ADR6425LVW using xda app-developers app
kancherlapraneeth said:
was your PC detecting the phone earlier?
Click to expand...
Click to collapse
Yes. I am positive it did before flashing the .10 RUU and i'm fairly sure it did in order for me to unlock, I just do not remember completely.
Squirrel1620 said:
Did you let the ruu make its second pass of the install? Did it boot normally before you went back to bootloader to flash a recovery? Also you have to be in fastboot menu to connect to usb
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
OH man, I forgot about going back into the fastboot menu. That seems to have solved it. I know have my phone back. Now I have to try and figure out why the pc is not detecting my phone. In the command prompt when I change directories to where fastbot and ADB are. I type adb devices, it does not detect the phone.
Thanks for the help on theHBoot issue. Phone is back but after booting up it flashes that it needs a SIMcard. Then loads up fine. I was able to connect thru the pc. I forgot to enable usb debugging and uncheck fastboot, but even after detected it will not let me flash amon ra. it gives me an error. I am bone tired and will try any suggestions tomorrow.
If you flashed a good ROM and your stuck in hboot, use fastboot and use the following command 'fastboot oem boot' that will force your phone to boot.
Alright so everything was great i was using viper rom on my evo lte, i had been having trouble flashing kernels. I tried some app that would do it, flashed one and now im ****ed. this thing just won't boot up at all it goes in between the (htc quietly stupid) splash screen and the one that you see as you load recovery. (with like the little red writing crap) just back and fourth thats it.... i can access my boot loader and recovery, so far ive wiped the hell out of it, formated the internal card, and tried installing countless different rom. all do the same loop thingy.
PLEASE HELP, ILL TRY ANYTHING!!
Im unlocked with s-on
and hboot-1.15.0000
if u can get into bootloader then wipe and restore your backup.. if u can get into booloader then u should be able to get into recovery from there go into recovery wipe and restore ya backup and u should be good to go.. wipe data.. wipe system.. wipe cash.. wipe dalvik cash
I'm in the same boat except it had nothing to do with kernels... Just all of a sudden everything stopped working... Nothing flashes correctly... Md5 sums never match for restores... If I mess with it long enough twrp stops recognizing my internal SD... I've had to ruu like 3 times because of it... I've tried different recoveries... Countless different wipe methods... Nothing works... I'm lazy panda s-off... Tried both twrp 2.2.1 and even tried clockwork for awhile... After running ruu I re-root and flash either recovery and as soon as I wipe and flash a Rom I'm stuck at the splash no matter what Rom... So with that said I'm stuck with stock for now... No fun stuff anymore...
Sent from my EVO using Tapatalk 2
thats why!! clockwork recovery is no good for this phone!! your not supposed to use it..
But as I said I was getting the same problems with twrp... And the internal SD problem happened using twrp... It doesn't matter what recovery I use... I've used both superwipe zips or just plane system wipe within twrp and every time something screws up and I get stuck at the splash screen having to run the ruu bootloader zip just to have a working phone...
Sent from my EVO using Tapatalk 2
jrmusante said:
Alright so everything was great i was using viper rom on my evo lte, i had been having trouble flashing kernels. I tried some app that would do it, flashed one and now im ****ed. this thing just won't boot up at all it goes in between the (htc quietly stupid) splash screen and the one that you see as you load recovery. (with like the little red writing crap) just back and fourth thats it.... i can access my boot loader and recovery, so far ive wiped the hell out of it, formated the internal card, and tried installing countless different rom. all do the same loop thingy.
PLEASE HELP, ILL TRY ANYTHING!!
Im unlocked with s-on
and hboot-1.15.0000
Click to expand...
Click to collapse
The OP in this thread was having the same problem:
http://forum.xda-developers.com/showthread.php?t=1842238
They were able to fix it by fastboot flashing the kernels boot image.
Sent from my EVO LTE
Thought you couldn't flash kernals while s-on? Did I make that up?
Sent from my EVO using xda app-developers app
still screwed
Ive just got no idea where my backup went, its just simply GONE. ive been messing around with android sdk so that i could relock my stupid bootloader so i can flash a ruu or whatever.
im normaly very good with this stuff, ive installed android sdk, watched like 4 videos on how to get this stupid adb shell working but its just not happening. im about to throw my emo lte and my macbook pro into my lake, and get an iphone.
Did you mount the correct sd card in twrp?
Sent from my EVO using xda app-developers app
jrmusante said:
Ive just got no idea where my backup went, its just simply GONE. ive been messing around with android sdk so that i could relock my stupid bootloader so i can flash a ruu or whatever.
im normaly very good with this stuff, ive installed android sdk, watched like 4 videos on how to get this stupid adb shell working but its just not happening. im about to throw my emo lte and my macbook pro into my lake, and get an iphone.
Click to expand...
Click to collapse
Lol don't do that, I'm sure you would regret it. The important thing is that your problem is completely solvable so don't lose hope. Did you take a look at the thread I linked you? If you have the sdk installed you should be able to flash a new boot image, which would be much better than going the RUU route in my opinion.
Sent from my EVO LTE
jrmusante said:
Ive just got no idea where my backup went, its just simply GONE. ive been messing around with android sdk so that i could relock my stupid bootloader so i can flash a ruu or whatever.
im normaly very good with this stuff, ive installed android sdk, watched like 4 videos on how to get this stupid adb shell working but its just not happening. im about to throw my emo lte and my macbook pro into my lake, and get an iphone.
Click to expand...
Click to collapse
bro your backup is prob on your internel sd card..
device wont show up..
ive got my emo lte plugged in, go into fastboot and plug it in, then it says fastboot usb. i go to the directry where my adb and stuff is in my terninal but when try ./adb devices it just shows no devices at all...
im on a mac btw
heres whats going on:
http://www.youtube.com/watch?v=pOCX-43eaUI
let me know if i an do anything else to make this crap work...
jrmusante said:
ive got my emo lte plugged in, go into fastboot and plug it in, then it says fastboot usb. i go to the directry where my adb and stuff is in my terninal but when try ./adb devices it just shows no devices at all...
im on a mac btw
heres whats going on:
http://www.youtube.com/watch?v=pOCX-43eaUI
let me know if i an do anything else to make this crap work...
Click to expand...
Click to collapse
Try going into recovery from the bootloader and then try the "adb devices" command. I've noticed that I can't issue adb commands while in fastboot also...not sure why. If you can get it to display your device while in recovery, then you know your communication is good. Go back into fastboot and you should be able to do the "fastboot flash boot" command, but rebooting with the adb command will not work for some reason. After you flash the boot image, there should be an option to reboot on your phone that you can select with the volume keys.
Sent from my EVO LTE
just wont show in boot loader
premo15 said:
Try going into recovery from the bootloader and then try the "adb devices" command. I've noticed that I can't issue adb commands while in fastboot also...not sure why. If you can get it to display your device while in recovery, then you know your communication is good. Go back into fastboot and you should be able to do the "fastboot flash boot" command, but rebooting with the adb command will not work for some reason. After you flash the boot image, there should be an option to reboot on your phone that you can select with the volume keys.
Sent from my EVO LTE
Click to expand...
Click to collapse
i wiped and reflashed the rom in recovery, also while i was there i kept trying to flash the boot.img and at one point kept getting some (ERROR: could not get pipe properties) and no matter what i do, it just wont show up in boot loader.
run the ruu
Fixed it!!
hey i just kept wiping everything and finally got the boot.img flashed through boot loader in adb or whatever. thank you everyone for your quick help!!
I'm trying to help a buddy of mine. He has a Thunderbolt, issued through work. It is stock, unrooted, locked, never modded. He recently got the ICS OTA update. Phone was functional, but laggy and a bit unstable. He did a factory reset, and initially the phone was fine for a few hours, then it was acting buggy. After a reboot it was fine for a bit, then froze. Usable time kept diminishing with subsequent reboots. He tried another factory reset, and the phone won't boot now. If you power it up, you get the white screen with the HTC logo, then a black screen, and nothing ever happens. I can get to Hboot. I can get to fastboot. Not sure if recovery does anything. I get the recovery screen, then a reboot, and then nothing.
I've been trying to read up on how to fix this, and I'm not sure how to go about it since the phone is currently locked, and won't boot. I looked at the Thunderbolt All In One tool, but it looks like it needs the phone to be booted to start the process.
My end goal is to get back to stock, unrooted, (Gingerbread, then OTA update I suppose), and S-on. But to do that, I need to obtain s-off first. Any info would be greatly appreciated.
I've attached a couple of pics.
Thank you.
a little side note
from what I've read verison has been replacing some phones that the ota has killed or broken something..
worth checking out...
I believe even out of warrenty..
cujo6801 said:
a little side note
from what I've read verison has been replacing some phones that the ota has killed or broken something..
worth checking out...
I believe even out of warrenty..
Click to expand...
Click to collapse
Good to know. Thank you. I think because it was employer issued, he's going to try to get a newer device if we can't get it running. But I just had to make some attempt to get it running.
Pm disconnecktie as you should be able to flash via abd beings you can get in to fastboot. He knows a lot about the workings of these phones.
Sent from my ADR6425LVW using Tapatalk 2
It could possibly be fixed by fastboot flashing the official release but I think a package would need to be put together for that to work correctly. Since the phone doesn't boot it limits the ways to fix it especially since we don't have an Ruu for the ics ota. Also because it doesn't boot adb commands are useless. Fastboot commands are unlikely to work either but I guess you could try by connecting the usb cable. Open a command prompt and type fastboot devices. If it shows the serial number then fastboot commands will work.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
It could possibly be fixed by fastboot flashing the official release but I think a package would need to be put together for that to work correctly. Since the phone doesn't boot it limits the ways to fix it especially since we don't have an Ruu for the ics ota. Also because it doesn't boot adb commands are useless. Fastboot commands are unlikely to work either but I guess you could try by connecting the usb cable. Open a command prompt and type fastboot devices. If it shows the serial number then fastboot commands will work.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Fastboot does work. I was able to do the "fastboot devices" command before, and saw the phone. I was also able to "fastboot flash zip" the file from post 12 from this tread (link below), BUT even though the file transferred from the computer to the phone, the actual flash failed... I'm assuming because the phone is locked.
http://forum.xda-developers.com/showthread.php?t=2120985&page=2
Try downloading the official ota zip over at the developer section. Put it on the root of your sd card and rename it to PG05IMG. Then run the update through fastboot. I seriously doubt this will solve the problem long term but it may work. I have doubts. I am beginning to think htc released the ota purely for development purposes. More and more people are popping in here with problems similar to this.
Sent from my ADR6400L using Tapatalk 2
I downloaded santod040's full ODEXED ICS ROM. That's the only thing I noticed that said "Official". Hopefully I didn't miss something obvious. I put it on the SD card and renamed it. Booted Hboot, and the file loaded, checked, then stopped and went back to the Hboot menu. No option to flash or install. Then, I tried doing fastboot flash zip from the command line while the phone was in Fastboot. It sent the file, and loaded it, then failed booloader signature checking. I'm not sure if there is another method to try. I have SOME working knowledge on how to do this stuff, but not as much as many of the members here, I'm sure.
SoundTech said:
I downloaded santod040's full ODEXED ICS ROM. That's the only thing I noticed that said "Official". Hopefully I didn't miss something obvious. I put it on the SD card and renamed it. Booted Hboot, and the file loaded, checked, then stopped and went back to the Hboot menu. No option to flash or install. Then, I tried doing fastboot flash zip from the command line while the phone was in Fastboot. It sent the file, and loaded it, then failed booloader signature checking. I'm not sure if there is another method to try. I have SOME working knowledge on how to do this stuff, but not as much as many of the members here, I'm sure.
Click to expand...
Click to collapse
You need to be rooted to use a rom
Sent from my Nexus 7 using Tapatalk 2
Yeah, that wasn't too swift of me, was it now?
I grabbed the zip from this thread:
http://forum.xda-developers.com/showthread.php?t=2144326
Tried Hboot with the file renamed, same results as previous post. Tried fastboot flash zip, same results as above. No joy.
Going to try to see if HTCDev will get the bootloader unlocked in the current phone state.
Well since the ota isn't a downgrade I thought it may work. If HTC dev is able to unlock his bootloader maybe he can get further.
Sent from my personally built from source CM10.1 N7.
Bootloader is unlocked now, since it was all through fastboot. Still S-on. Tried with the OTA zip still on the SD card as "PG05IMG.zip." It loaded, started to check, started to parse for a moment, then went back to the Hboot screen, reboot got me nowhere. I need to go deal with the rest of life now. I'll try again tomorrow. I appreciate everyone's help today. Thank you.
At this point just s off and install a recovery then you can flash that ROM.
Sent from my Nexus 7 using Tapatalk 2
Use this guide here. Make sure you have plenty of time before hand and FOLLOW THE DIRECTIONS IN ORDER TO A T. It is very important that you don't skip over stuff. This is the only current method to get s off with ics.
Sent from my ADR6400L using Tapatalk 2
Long day at work, but back to it. Making sure the battery is charged up, and downloading files.
I'm looking at a post on ThunderboltForums. Making absolutely sure here: Is THAT the one I should be following?
Follow-up: At the end of step 28, after flashing the .19 ROM, is says to use the All-In-One tool. IF I plan to be stock, unrooted, locked, S-on, it seems I'm there at this point, and I can let the OTA update run. Is that correct?
Thanks again.
Looks like I'm on stock Gingerbread, S-off, re-locked, stock recovery. Heck, it finally boots! I'll see about trying OTA update tomorrow.
Thanks again.
S off and relocked? You need to run the allinonetool first and unlock the bootloader before you flash anything.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
S off and relocked? You need to run the allinonetool first and unlock the bootloader before you flash anything.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Huh. I never did use the tool. I went through the steps on the ThunderboltForums post all the way through flashing the .19 ROM. Unless I missed something or did something wrong, before the flash it said I would be re-locked and S-on. After the flash it said the phone should be "back to normal". The next step was the All-In-One tool. But the device actually booted into android with the .19 ROM. That was the first time I saw it boot since I got my hands on it. Perhaps the process in that thread helped repair whatever part of the system was buggered up to begin with?
Regardless, I tried the OTA update, and the phone took the ICS update through Verizon. It seems to be running better now than it did before. It's back in my buddy's possession, and he's in the process of getting his apps and data reinstalled.
He thanked me profusely for getting it running again. So I, in turn, pass his thanks on to everyone here that helped me out, the people that worked to get the Thunderbolt resources to where they are now, and to the forum in general for existing and doing what it does. Thank you all.
Ok first off my phone just started a boot loop but only with the first htc quietly brilliant screen, noting more. It then restarts and does it all over again. I tried the factory reset a few times and got nothing. So i decided now would be a good time to root so I unlocked with htvdev. Then, using the twrp stuff, i did the fastboot devices cmd and it recognizes the phone. So i did the rest the jewel stuff and it said okay. Then did the cache erase. After getting back to hboot screen i select recovery and it starts with the htc quietly brilliant screen with the red writing under it. After a few seconds the phone restarts and the htc quietly brilliant screen is back but without the red writing under it and it starts the boot cycle all over again. I have no access the the twrp recovery, just the fastboot and bootloader stuff. I am fairly new to this stuff and have searched all over the place but cant find what im looking for. Maybe not looking for the right stuff. Any direction would be great. Thanks
Ok So now I got it to loop the splash screen but with the writing under it. I forced a couple roms and found one that did brick it. Got it back through ubuntu but thats about it, still looping.
Sounds like you're S-on & you need to install the kernel separately from the ROM for your phone to boot. Click the link in my sig for more info.
Also, your phone isn't bricked
Sent from my EVO using xda premium
I cant get into twrp. Its installed but I cant access it and i cant seem to figure out how to flash a kernal or rom or anything. Im running hboot 2.09 unfortunately. I dont know what rom or kernal to flash anyway. The dirtyracun stuff says to boot into recovery for part of it and I cant get into recovery.
Can you access your bootloader screen?
Sent from my EVO using xda premium
FinZ28 said:
Can you access your bootloader screen?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Yes
enolive said:
Yes
Click to expand...
Click to collapse
What happens when you try to access recovery from the bootloader screen?
Sent from my EVO using xda premium
FinZ28 said:
What happens when you try to access recovery from the bootloader screen?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
It shows the splash screen with the htc writing, sits there for 30 secs or so then the screen goes black and then the splash screen comes back up. I keeps doing that over and over. I should clarify that the twrp install was the next step that I was trying to get to. After typing "fastboot flash recovery openrecovery-twrp-2.5.0.0-jewel.img" then selecting recovery. Mind you that the boot cycle was already happening in the very beginning and thats what prompted the root. Kind of a "nothing to lose" deal.
I also just tried to see if adb is still reading my phone and now its showing the "list of devices attached" with nothing listed. Im not sure if the developer options could have been reset to off or something, dont even know if that matters at this point.
You need to get into the bootloader and plug your phone up to it. Make sure it's connected via Fastboot USB highlighted in red, then try fastboot flashing the recovery again. Make sure the recovery file is in your ADB tools folder or it won't work. Once you get recovery working I suggest using the mount option, then you can transfer files to your phone from your computer. I suggest using a ROM that has an S-on kernel installer, like MeanBean. Just follow the instructions for flashing the ROM.
Sent from my EVO using xda premium
FinZ28 said:
You need to get into the bootloader and plug your phone up to it. Make sure it's connected via Fastboot USB highlighted in red, then try fastboot flashing the recovery again. Make sure the recovery file is in your ADB tools folder or it won't work. Once you get recovery working I suggest using the mount option, then you can transfer files to your phone from your computer. I suggest using a ROM that has an S-on kernel installer, like MeanBean. Just follow the instructions for flashing the ROM.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
The phone is plugged into the computer and connected via fastboot usb in red like you said. The recovery file is in the adb folder. It says
C:\Users\Adam\Desktop\Root_HTC_EVO_LTE>fastboot flash recovery openrecovery-twrp
-2.5.0.0-jewel.img
sending 'recovery' (8196 KB)...
OKAY [ 1.010s]
writing 'recovery'...
OKAY [ 2.000s]
finished. total time: 3.020s
Thats the problem, when i select recovery, in the bootloader menu, it just keeps rebooting. I let it go for awhile, like 2 hrs, and thats all it did.
Would a messed up sdcard cause this? Should I try mounting file the the sdcard and then putting it back in the phone? I'm not against going with the s-off but I cant get that to work till i get into the recovery, right?
That's weird. You should be able to get to recovery now. Try and install an older version of TWRP, like version 2.41. It's on their site.
Sent from my EVO using xda premium
FinZ28 said:
Did you try to fastboot flash the recovery to your phone from your computer like I said to do in my previous post? Or are you just trying to boot straight into recovery from the bootloader?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Fastboot flash from the computer? Isnt that what I was doing or am i doing it wrong? I type it all in on the cmd prompt. If thats not right I dont know how else to do it. Is there another way to boot the recovery other then from the bootloader?
Try "fastboot reboot recovery " from the command window.
I'm not 100% positive about that command but it should be good
SENT FROM MY LTEVO
corcgaigh said:
Try "fastboot reboot recovery " from the command window.
I'm not 100% positive about that command but it should be good
SENT FROM MY LTEVO
Click to expand...
Click to collapse
Just tried it and it gave me a list of commands to try. I just copied the twrp file "pj75img.zip" to the sdcard via another phone. Problem is that the battery is to low right now so its gonna wait till tomorrow.
enolive said:
Just tried it and it gave me a list of commands to try. I just copied the twrp file "pj75img.zip" to the sdcard via another phone. Problem is that the battery is to low right now so its gonna wait till tomorrow.
Click to expand...
Click to collapse
You won't be able to flash a PJ75IMG.zip file unless you are S-OFF
Open a cmd window from android-sdk/platform-tools folder and type adb reboot recovery and press enter
that should take you to twrp
bigdaddy619 said:
You won't be able to flash a PJ75IMG.zip file unless you are S-OFF
Open a cmd window from android-sdk/platform-tools folder and type adb reboot recovery and press enter
that should take you to twrp
Click to expand...
Click to collapse
Well now it says "error:device not found". When I type "adb devices" i get the blank list of devices but if i type "fastboot devices" it gives me the number. I think at some point I tried fastbooting a rom didn't work and actually bricked the phone, blank screen that wont turn on. Then fixed that via ubuntu and got it back to the bootloop. As I stated in the beginning it wasnt booting with the red writing at the bottom of the splash screen to start but then went away on the second reboot and kept rebooting without it. After fastbooted twrp again it now shows the red writing on every reboot. Also I cant get the battery to charge because i cant shut it off so it says battery low when i try the flash recovery command. The battery charge led is blinking slowly for about a minute after a simulated battery pull but thats it.
I guess its not fixable.
enolive said:
I guess its not fixable.
Click to expand...
Click to collapse
It's fixable, bro. Check your PM
Sent from my EVO using xda premium
Hello,
I was recently given a bootlooping Evo 4G Lte. I have been trying to figure out how to get this thing out of a bootloop and havent been able to do it. I, unfortunately, have no history on what happened to this device. Currently, it bootloops on the "Mean Bean" loading screen but will go no further. I can get into the bootloader, which says it is Unlocked, S-On, but I am unable to boot it into a recovery, it just returns back to bootloader. I have tried fastbooting twrp, but it fails (remote: image update error), and I have tried fastbooting the Mean Bean kernel thinking maybe thats all it needs, but that failed as well. Anybody have an insight? Much appreciated! Thanks.
Mike
I would run the 3.17 RUU. Hit the top link in my sig and look at the last post in the thread. You can run it from the bootloader. You'll need to re-root afterwards but it should get your phone back in working condition.
Sent from my HTC EVO 4G LTE
FinZ28 said:
I would run the 3.17 RUU. Hit the top link in my sig and look at the last post in the thread. You can run it from the bootloader. You'll need to re-root afterwards but it should get your phone back in working condition.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
Thanks for the quick reply. I downloaded the RUU and ran it. However it sits and says "Waiting for bootloader" then errors out with "USB connection issue". The usb is working. The reason I never ran the RUU in teh first place was because i thought i read that you cant RUU with and unlocked bootloader. Is that not true? or is that my problem?
Mike
Not 100% sure but I will check with someone who used this tool recently and see if they were still unlocked at the time. Were you connected via Fastboot USB? Sounds more like a driver issue.
Sent from my HTC EVO 4G LTE
FinZ28 said:
Shouldn't matter. I know of a couple of users who were having phone issues and had unlocked bootloaders when they ran this tool. Were you connected via Fastboot USB? Sounds more like a driver issue.
Click to expand...
Click to collapse
Yeah I was connected and it said fastboot USB. It said rebooting to bootloader and rebooted, still said fastboot USB. Then it sat at a screen that said "waiting for bootloader" and after a while error ed out.
You can try relocking. You just need to run the command "fastboot oem relock" from a command line while connected via fastboot USB mode.
Sent from my HTC EVO 4G LTE
FinZ28 said:
You can try relocking. You just need to run the command "fastboot oem relock" from a command line while connected via fastboot USB mode.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
I have since tried relocking to see if that was it, and it did the same thing.
Mike
Hopefully @YoFayce can shed some light on the matter since he recently used this on his phone.
Sent from my HTC EVO 4G LTE
FinZ28 said:
Hopefully @YoFayce can shed some light on the matter since he recently used this on his phone.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
crazymike1234 said:
I have since tried relocking to see if that was it, and it did the same thing.
Mike
Click to expand...
Click to collapse
you can use the stock RUU and you can leave the bootloader unlocked as it will not affect anything.. it will fix your looping problem (Amongst others) as in gps not working ect.. once your done you will need to fastboot over your TWRP and from there mod as normal Good Luck! and ill be watching if you need any help!
YoFayce said:
you can use the stock RUU and you can leave the bootloader unlocked as it will not affect anything.. it will fix your looping problem (Amongst others) as in gps not working ect.. once your done you will need to fastboot over your TWRP and from there mod as normal Good Luck! and ill be watching if you need any help!
Click to expand...
Click to collapse
Problem is the ruu keeps error in out. I am beginning to think it may still be a driver problem. Someday I will get this done!
Mike
crazymike1234 said:
Problem is the ruu keeps error in out. I am beginning to think it may still be a driver problem. Someday I will get this done!
Mike
Click to expand...
Click to collapse
When in doubt update your android SDK remove the htc drivers reboot install drivers reboot and you should be good to go! Check the integrity of your USB cable and if possible use a rear USB port (More Power) Painful process yes but well worth it.. HTC drivers act strange till you reboot OOOh and make sure your using the proper HTC drivers for windows 32 bit or 64 bit!
YoFayce said:
When in doubt update your android SDK remove the htc drivers reboot install drivers reboot and you should be good to go! Check the integrity of your USB cable and if possible use a rear USB port (More Power) Painful process yes but well worth it.. HTC drivers act strange till you reboot OOOh and make sure your using the proper HTC drivers for windows 32 bit or 64 bit!
Click to expand...
Click to collapse
The drivers seem to be ok, but I am still not able to get any further. The RUU finds my phone, then reboots again to bootloader, but it just sits there saying "Waiting for bootloader" until it errors out due to "USB Connection error". I have tried a few different cables, and different USB ports. Not sure what the problem is but it just wont go any further. I re-unlocked my bootloader with htcdev. I have tried fastbooting a recovery to the phone but it errors out. I just cant get anything to work so I can boot anything. I really just want to get something working...anything! Any other ideas? Thanks.
Mike
use an sd card put a recovery image on the root of the sd boot into bootloader apply the recovery you should then have a recovery if you did it right, go into twrp mount device add a rom flash in recovery viola.
Sinistertensai said:
use an sd card put a recovery image on the root of the sd boot into bootloader apply the recovery you should then have a recovery if you did it right, go into twrp mount device add a rom flash in recovery viola.
Click to expand...
Click to collapse
Sinister,
Thanks for the reply. I put TWRP on the sdcard (named PJ75IMG, right?) and tried to apply that when I rebooted to recovery last night and it failed. It tries to load it but gives a few errors quick (No Image) Did I do it wrong?
Mike
crazymike1234 said:
Sinister,
Thanks for the reply. I put TWRP on the sdcard (named PJ75IMG, right?) and tried to apply that when I rebooted to recovery last night and it failed. It tries to load it but gives a few errors quick (No Image) Did I do it wrong?
Mike
Click to expand...
Click to collapse
make sure the file is just the PJ75IMG no additional text and it should be .zip If I recall correctly. make sure its on the root of the sdcard not internal but sd or external and it should be at the top level e.g. sdcard/ make sure its not in any other folders after you do that hold power and vol down get to hboot screen itll scan and then just follow the instructions.
Sinistertensai said:
make sure the file is just the PJ75IMG no additional text and it should be .zip If I recall correctly. make sure its on the root of the sdcard not internal but sd or external and it should be at the top level e.g. sdcard/ make sure its not in any other folders after you do that hold power and vol down get to hboot screen itll scan and then just follow the instructions.
Click to expand...
Click to collapse
Thats exactly what I did. It is the only thing on the sdcard. It says no gift file, Loading, no image for 4 different things. Then returns to the bootloader.
Mike
crazymike1234 said:
Thats exactly what I did. It is the only thing on the sdcard. It says no gift file, Loading, no image for 4 different things. Then returns to the bootloader.
Mike
Click to expand...
Click to collapse
zip files probably corrupt then. download another do the same process make sure you've got a good file use md5 checks
Sinistertensai said:
zip files probably corrupt then. download another do the same process make sure you've got a good file use md5 checks
Click to expand...
Click to collapse
Hmmm, Ill try download again. I got it from the main TWRP site.
crazymike1234 said:
Hmmm, Ill try download again. I got it from the main TWRP site.
Click to expand...
Click to collapse
careful on the vol down press you might be holding it too long and its canceling the update.
Sinistertensai said:
careful on the vol down press you might be holding it too long and its canceling the update.
Click to expand...
Click to collapse
Well, which recovery file should I be using? When I use the main TWRP ones (ie openrecovery-twrp-2.6.0.0-jewel.img) it gives me the errors like I said above. I now see they have a few labeled like this PJ75IMG-twrp-2.3.1.0-jewel.zip. When I use these, it tries to continue but says "Main Version Is Older. FAILED"