Related
I just acquired a Droid Eris from my buddy of mine, when you turn it on it just stays at the screen with the 3 androids on skateboard(if I turn it on with it plugged into usb It makes the connection noise though). I can Also get into hboot and recovery but no matter what I do it will not install anything, everything just fails. Also its say its S-ON. Any help would be great, thanks.
glitch666 said:
I just acquired a Droid Eris from my buddy of mine, when you turn it on it just stays at the screen with the 3 androids on skateboard(if I turn it on with it plugged into usb It makes the connection noise though). I can Also get into hboot and recovery but no matter what I do it will not install anything, everything just fails. Also its say its S-ON. Any help would be great, thanks.
Click to expand...
Click to collapse
Well, you didn't really say what "everything just fails" means. How about giving us an error message?
While you are at it, what version of recovery is on the phone - Amon_RA v1.6.2, or some version of Clockwork?.
Same deal for the bootloader - how about an exact version number - 1.49.0000, 1.47.0000, or other?
Because your phone is already "soft-bricked", and you got it for free, and because your recovery boots up, you can try flashing "ErisMTDNuke_v0.9.zip". You can find it at this post:
http://forum.xda-developers.com/showpost.php?p=11651122&postcount=21
It has an an assert() in it that tries to block it from running on ClockworkMod, but depending on what version of recovery you have, that may not matter. Let me know if you get any errors running it. If it runs, you should be back in business; it leaves the /system, /data, and "boot" partitions of the ROM blank, so you will need to flash a ROM afterwards. Also, if you have ClockworkMod recovery on the phone, you should consider getting it off of there, and putting one of the two Amon_RA recovery variants on there.
You might find the entire thread that contains the above post very useful, as it describes a method for installing the S-OFF bootloader using the "SoSickWiTiT" rooting method, as well as other tricks such as using fastboot to soft-load recoveries without writing them to flash; that full thread is here:
http://forum.xda-developers.com/showthread.php?p=11652502
Please provide full details on what works / doesn't work, particularly with "ErisMTDNuke_v0.9.zip" - it has only been used on 3 phones so far (worked on all three, though).
cheers
bftb0
I dont think the phones been rooted(my friend has no idea what that even is). It has hboot 1.49.0000, and the recovery is not a custom one, its Android recovery 2e. If I try to Install an update through recovery its says installation aborted. Also if I use pb00img.zip it loads in hboot but says previous version is older and to reboot.
glitch666 said:
I dont think the phones been rooted(my friend has no idea what that even is). It has hboot 1.49.0000, and the recovery is not a custom one, its Android recovery 2e. If I try to Install an update through recovery its says installation aborted. Also if I use pb00img.zip it loads in hboot but says previous version is older and to reboot.
Click to expand...
Click to collapse
OK, that is completely different. It is impossible to load a dev ROM using the stock recovery <2e>
Did you try the "wipe data/factory reset procedure" of the recovery menu, or have you already done that and then the phone hangs at the three droids?
bftb0
If the stock ( <2e> ) recovery factory reset does not work, then the method of last resort is going to be to try and get the S-OFF bootloader onto the phone using the "SoSickWiTiT" rooting method.
Generally what happens - if you have corrupted flash memory partitions - is that parts of this install will fail, but getting the engineering bootloader (1.49.2000 S-OFF) onto the phone will succeed - and from there you can leverage the behaviors of the S-OFF bootloader to get a custom recovery running (by using fastboot). Once that happens, you can run the ErisMTDNuke_v0.9.zip flash to erase the /system, /data, and "boot" partitions, so that a subsequent ROM flashing operation will succeed (probably, no guarantees).
The way the "SoSicWiTiT" rooting method works, you run the "Official 2.1 RUU" Utility on the PC - but just before it is ready to start writing to the phone (after it has unpacked all it's temporary files and installed drivers for you), you take the "Root PB00IMG.ZIP" file, rename it to "rom.zip", and replace the "rom.zip" file unpacked in the temporary file area of the RUU. This gets the S-OFF bootloader installed (at a minimum, possibly the whole rom if your problem is not flash memory page corruption).
The thread I mentioned above has more details; ask questions if you don't understand something.
bftb0
PS You should be doing all of these operations with a well charged battery - 100% is a good place to start. Don't let the phone sit in HBOOT or FASTBOOT mode for extended periods of time - the battery will discharge rapidly, even if the phone is plugged in to the charger.
Thank you for the quick and to the point replies, I will try this later tonight and will post and let you know if it works out. I have tried the factory reset and it doesn't work, but hey it was free if I screw it up Its no big issue lol. Im not new to rooting its just I have no experience with this particular phone, so thank you =].
glitch666 said:
Thank you for the quick and to the point replies, I will try this later tonight and will post and let you know if it works out. I have tried the factory reset and it doesn't work, but hey it was free if I screw it up Its no big issue lol. Im not new to rooting its just I have no experience with this particular phone, so thank you =].
Click to expand...
Click to collapse
OK. Good luck.
The Root PB00IMG.ZIP and the "Official 2.1 RUU" can be found here:
Consolidated HTC RUU, Leak, and OTA Downloads
Amon_RA's original (v1.6.2) recovery is located here
If you don't have a version of fastboot on your PC/workstation already, you can find different platform versions of it a short distance down the HTC's developer page for the ADP.
If you can get the S-OFF bootloader onto the phone, then you can flash Amon_RA's recovery from the PC with a single command:
Code:
fastboot flash recovery recovery-RA-eris-v1.6.2.img
If you don't already have USB drivers installed on your PC, the RUU utility should be able to do it for you automatically (although ymmv depending on your Xp/Vista/Win7/x32/x64 variety).
Let me know how things go.
bftb0
PS It is worth repeating - make sure your phone is well charged when you are doing any flashing.
Yeah I know fastboot like the back of my hand(g1 and other phones that I love dearly but no longer have), im giving this a shot right now, thank bud.
glitch666 said:
Yeah I know fastboot like the back of my hand(g1 and other phones that I love dearly but no longer have), im giving this a shot right now, thank bud.
Click to expand...
Click to collapse
Standing by.
No matter what the official 2.1 RUU gives me a bootloader mismatch error 140 with either the actual rom.zip or the root rom renamed to rom.zip and placed in the temp folder, let me try some more things. Edit RUU says Im going from 2.37.605.4 to 2.36.605.1. Ok so this leads me to believe it has the 4th OTA on it right?
PS -
I might have mentioned it in that other thread, but anyway: the RUU utility will get the phone to cooperate if the phone is put into fastboot mode (or RUU mode). Normally it is expected that the phone will be booted normally when you start up the RUU... but that (obviously) isn't an option for a soft-bricked phone.
cheers
glitch666 said:
No matter what the official 2.1 ruu gives me a bootloader mismatch error 140 with either the actual rom.zip or the root rom renamed to rom.zip and placed in the temp folder, let me try some more things.
Click to expand...
Click to collapse
Rats. Does that happen immediately after the RUU starts up, or only when you tell it to begin the flashing operation?
Here's another wild straw to grasp at.
If you plug the phone into your PC, and then cold-start it (normal boot), do you hear 2 USB sequences at about 5 and 9 seconds, respectively? If the kernel is alive, but looping on something.... and the prior user had USB debugging enabled, and it's a 2.1 ROM, we can probably still root it by hand across ADB.
does "adb devices" give you anything 15 or more seconds after boot-up, or does your (Windows) device manager indicate a "Composite Interface"?
bftb0
Edit RUU says Im going from 2.37.605.4 to 2.36.605.1. Ok so this leads me to believe it has the 4th OTA on it right?
Click to expand...
Click to collapse
Sure sounds that way. Normally that info (the "Main Version") is stored in the misc partition, and it rather surprises me that an OTA install would cause that to happen; but I can't argue with what you are seeing.
That might mean that neither RUU nor PB00IMG.ZIP installs will work without being able to modify the RUU program to ignore version checks.
How about the adb angle - does anything come up on the USB when the 3 skating droids are showing?
No it goes all the way to the flashing processes after the phone goes into bootloader mode. then stops and gives me the error, now with adb when I turn the phone on I hear one chime and then get a device not recognized and no output from adb. Did you see my last post on the other page I edited it about the bootloaders, its says its going from 2.37.605.4 to 2.36.605.1. Sorry you posted before me so ignore this last tid bit.
Long shot, but check your HBOOT screen again - is it still S-ON (1.49.0000) ?
BTW, when you say "bootloader mode" - do you mean FASTBOOT or RUU mode? (The RUU mode is just a graphic with the HTC logo in the middle of the screen, sometimes with small arrows in each of the 4 corners of the screen. FASTBOOT mode says either "FASTBOOT" or "FASTBOOT USB" right on the screen).
I would think that you are starting the process with the phone in FASTBOOT mode, right?
bftb0 said:
Sure sounds that way. Normally that info (the "Main Version") is stored in the misc partition, and it rather surprises me that an OTA install would cause that to happen; but I can't argue with what you are seeing.
That might mean that neither RUU nor PB00IMG.ZIP installs will work without being able to modify the RUU program to ignore version checks.
How about the adb angle - does anything come up on the USB when the 3 skating droids are showing?
Click to expand...
Click to collapse
I am not getting anything from adb.
bftb0 said:
Long shot, but check your HBOOT screen again - is it still S-ON (1.49.0000) ?
Click to expand...
Click to collapse
Yup it stayed the same.
bftb0 said:
Long shot, but check your HBOOT screen again - is it still S-ON (1.49.0000) ?
BTW, when you say "bootloader mode" - do you mean FASTBOOT or RUU mode? (The RUU mode is just a graphic with the HTC logo in the middle of the screen, sometimes with small arrows in each of the 4 corners of the screen. FASTBOOT mode says either "FASTBOOT" or "FASTBOOT USB" right on the screen).
Click to expand...
Click to collapse
First I put the phone into fastboot mode, then fire up RUU and it kicks the phone to a black screen with an htc logo in the middle and trys to flash it(the RUU says its putting the phone into bootloader mode so I guess thats what its in when it restarts to the htc logo).
Don't Quote me but I know the Eris is Almost like my Hero, and with the Hero there's a way to Get it into the Fastboot I Think by Holding Volume Up and Powering on the Phone! Then you Should be Able to Run the Latest RUU for the Eris... Hopefully that will get you back Right!!
Good Luck!
Sent from my Hero using XDA App
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!!
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
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
I've been trying to install Maximus HD 10. I've turn s-off, but now I'm not sure the s turned off. As you can see on the photo, s is now on - not sure why
Every time I'm installing the soft, the device - after done it - is rebooting, and then turning off. I've done it with Maximus and CWM, and it changes nothing.
Phone is unlocked and tempered
wkornas96 said:
I've been trying to install Maximus HD 10. I've turn s-off, but now I'm not sure the s turned off. As you can see on the photo, s is now on - not sure why
Every time I'm installing the soft, the device - after done it - is rebooting, and then turning off. I've done it with Maximus and CWM, and it changes nothing.
Phone is unlocked and tempered
Click to expand...
Click to collapse
so the phone is unlocked and tampered, that means you can write a recovery image
so download twrp or cwm for your device
boot to hboot and open cmd prompt on your computer and do:
fastboot flash recovery (recovery).img
for (recovery) put in whatever the file name is for the .img you download
once that is flashed, boot into recovery and flash the rom you want to use.
if the rom isn't a stock rom then open it's zip and pull out the boot.img and put it in the folder where you did the recovery.img
then go back to hboot and open cmd prompt again and do:
fastboot flash boot boot.img
that should allow your phone to boot if nothing else.
all else fails find an RUU for your device and use it to restore the factory software
But the phone is S-ON and i can't do S-OFF. I try to do it on the HTCdev but it's not working
wkornas96 said:
But the phone is S-ON and i can't do S-OFF. I try to do it on the HTCdev but it's not working
Click to expand...
Click to collapse
Right HTC dev doesn't s-off it only puts you in the unlocked s-on state, that's why to get software or anything on it you have to do what I suggested
Sent from my LG-D800 using Tapatalk 4
thoughtlesskyle, just wanted to say thanks. Thought I'd bricked my phone. I too 'assumed' the HTC Dev option S-Off'd my phone. Followed your instructions and got my phone to boot into cyanogen 9.1. Now, I assume if I do a restart everything will reboot as normal?
It will boot back to cm but yes it will reboot no problem, if you update the rom you might need to reflash the boot.img depending if there was a kernel change, but otherwise you are good
Sent from my LG-D800 using Tapatalk 4
Also glad I could help, I had an evo 3D that was the same way, luckily they fixed it for the One
Sent from my LG-D800 using Tapatalk 4
So will MaxiumsHD work for those of us that are still S-On, if we use something like FlashImageGUI to flash the boot.img?
Yes, flash image gui does the same as doing the fastboot flash
Sent from my LG-D800 using Tapatalk 4