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
Related
[07oct2010] resolved
I have searched extensively through the forums and have attempted dozens of different solutions and permutations of my own. My Eris will not advance past the splash screen, I can access recovery and bootloader. I've tried many different versions of update.zip through recovery, fails for various reasons, usually signature. Every attempt for PB00IMG.zip in HBOOT yields Main Version is Older. Fast boot gives me (remote: not allow). I've created a gold card, and it's not done me any good, the phone doesn't even acknowledge it, I used the Kingston 2gb and tried GoldCardTool.exe 0.5 and hex editor separately, it appears to have been successful. Ruu doesn't recognize my phone in any of the modes I can access, splash, HBOOT, FastBoot, recovery triangle, recovery.
PB00100 XC SHIP S-ON
HBOOT-1.49.0000 (PB0010000)
MICROP-0111
TOUCH PANEL-SYN0104
RADIO-2.32.40.11.09
Feb 8 2010,00:08:56
Thanks
USSENTERNCC1701E said:
I have searched extensively through the forums and have attempted dozens of different solutions and permutations of my own. My Eris will not advance past the splash screen, I can access recovery and bootloader. I've tried many different versions of update.zip through recovery, fails for various reasons, usually signature. Every attempt for PB00IMG.zip in HBOOT yields Main Version is Older. Fast boot gives me (remote: not allow). I've created a gold card, and it's not done me any good, the phone doesn't even acknowledge it, I used the Kingston 2gb and tried GoldCardTool.exe 0.5 and hex editor separately, it appears to have been successful. Ruu doesn't recognize my phone in any of the modes I can access, splash, HBOOT, FastBoot, recovery triangle, recovery.
PB00100 XC SHIP S-ON
HBOOT-1.49.0000 (PB0010000)
MICROP-0111
TOUCH PANEL-SYN0104
RADIO-2.32.40.11.09
Feb 8 2010,00:08:56
Thanks
Click to expand...
Click to collapse
I am assuming that this is a completely stock phone with the July 2010 OTA on it?
(I assume this because you mentioned "recovery triangle" - which seems to indicate that you have the stock recovery on the phone.)
I think you are "almost" SOL - but there are a few remote possibilities. I hope you don't mind answering a few questions. But first, some assertions:
- fastboot will not do anything useful for you with an S-ON bootloader; that is the way it works. S-ON means (among other things) that "fastboot is crippled".
- the only "update.zip" files which will work with the stock recovery are signed with HTC's key; furthermore, they are locked to specific versions of the recovery boot. These are the "OTA" zip files. Moreover, they perform binary patching, so they are extremely tightly bound to the exact version of software which pre-exists on the phone.
So, here's my questions:
1) Completely stock phone or not? (Please Elaborate, esp. if you have any root tools on the phone.)
2) Did you try the HBOOT+PB00IMG.zip method with the "Leak-V3" HTC ROM, and also get a "Main Version is Older" error?
3) Before your phone got into this state, did you have USB debugging turned on?
4) Does "adb devices" indicate that adbd is running on the phone when it is in the "Stuck at boot splash screen" state?
5) If it is a stock phone, did you try cold-booting into "Safe Mode" (press and hold trackball down and then press and hold End/Power, and continue to hold down the trackball until the verizon splash screen shows up - about 40 seconds, iirc). If that works - do a factory reset.
Finally - if the phone is (in fact) completely stock - why not take it back to Big Red and ask them to exchange it? (Or upgrade it; lately it seems from reports as if all the Eris refurbs that are left all have problems).
bftb0
bftb0 said:
1) Completely stock phone or not? (Please Elaborate, esp. if you have any root tools on the phone.)
Click to expand...
Click to collapse
Not stock. I rooted my phone with Easy Root, then used 1-Click root and got Amon's Recovery Image. I think I was running Cyanogen. I was trying to get back to stock and no method was working, I was unable to flash with using adb or fastboot, I was able to flash using the recovery image and the way I got the recovery image led me to believe I was able to flash from within the phone, so I got a terminal emulator on the phone and flashed the recovery and boot partitions to an images I extracted from an update.zip that I found, I can't remember where it came from though.
bftb0 said:
2) Did you try the HBOOT+PB00IMG.zip method with the "Leak-V3" HTC ROM, and also get a "Main Version is Older" error?
Click to expand...
Click to collapse
Yes I tried an image i found on androidforums, same error.
bftb0 said:
3) Before your phone got into this state, did you have USB debugging turned on?
Click to expand...
Click to collapse
I believe I did, but it's been a while, it may have been off, I know I was attempting to use adb before hand, and that it did register the device, I don't think I would have disable it, but I can't be sure.
bftb0 said:
4) Does "adb devices" indicate that adbd is running on the phone when it is in the "Stuck at boot splash screen" state?
Click to expand...
Click to collapse
No, adb devices says "List of attached devices" and lists nothing.
bftb0 said:
5) If it is a stock phone, did you try cold-booting into "Safe Mode" (press and hold trackball down and then press and hold End/Power, and continue to hold down the trackball until the verizon splash screen shows up - about 40 seconds, iirc). If that works - do a factory reset.
bftb0
Click to expand...
Click to collapse
I tried, and after a couple minutes it was still on the skateboarding androids. I suppose I should have specified, I don't ever get to the verizon screen.
Thank you
Well, you might just be SOL.
But, I have to say, I still notice a fair bit of ambiguity in the way you describe certain things. For instance, I asked about the "Leak-V3" PB00IMG.zip file, and you replied "an image from Androidforums". (There have been 6 different PB00IMG.zip files from HTC for the Eris.)
Also, you said,
"flashed the recovery and boot partitions to an images I extracted from an update.zip that I found, I can't remember where it came from though"
Click to expand...
Click to collapse
.
As you have discovered, sloppiness gets you into trouble. Almost all of the methods that you are attempting are highly sensitive to versions of software already on the phone, and also past history.
To summarize, it sounds like the current state of your phone is:
(1) 1.49.0000 S-ON Bootloader ( = Leak-V3 )
(2) recovery boot from "an update.zip", origin and version unknown.[SIZE=+1]**[/SIZE]
(3) boot partition from "an update.zip", origin and version unknown.[SIZE=+1]**[/SIZE]
(4) /system, /data, and /cache partitions from a version of "I think I was running Cyanogen."
That's pretty much a disaster - you don't have an engineering bootloader, you don't have a custom recovery, your boot image is mis-matched to the loaded OS, and your OS (obviously) will not boot far enough to gain any access from adb.
As near as I can tell, you really have only one chance at recovery; the RUU method certainly will not work as it requires the OS to be booted at the very beginning so that the phone can be restarted in OEM-78 (aka "RUU") mode, and you can't do that correctly without an HTC-derived 2.1 ROM anyway. (Or manually installing the correct "reboot" binary and supporting shared libs).
Here is what I recommend you try: go back and find the Leak-V3 PB00IMG.zip; it has a MD5 checksum of 1c0b0182356242a9d673a661e7458587. Try to apply it to your phone with the HBOOT method. If you get a "Main Version is Older" message, you are screwed - that is your only hope at the moment.
bftb0
[SIZE=+1]**[/SIZE]If you are able to locate the "update.zip" file that you used (on your PC, I suppose), you might be able to identify the HTC version from the MD5 checksums of the "boot.img" and "recovery.img" files in that "update.zip" file. This listing of checksums for HTC ROMs provides those values. (Note the same post can be used to identify PB00IMG.zip files as well - just compute their "MD5" checksums and look up the value)
PS I don't know when you started on your journey of trying to restore back to factory, but there is this method which uses the normal (Amon_RA) flashing method. It works.
Sorry for all my impercison, I entered into all this without an understanding of how specific everything is, this was my first endeavor into tinkering with any sort of EEPROM OS, I didn't recognize by necessity everything is distinct.
The link listed in the same one I downloaded the PB00IMG.zip from.
Thanks for your time, I guess I'll just find one on eBay with a broken screen and a good ESN.
USSENTERNCC1701E said:
Sorry for all my impercison, I entered into all this without an understanding of how specific everything is, this was my first endeavor into tinkering with any sort of EEPROM OS, I didn't recognize by necessity everything is distinct.
The link listed in the same one I downloaded the PB00IMG.zip from.
Thanks for your time, I guess I'll just find one on eBay with a broken screen and a good ESN.
Click to expand...
Click to collapse
Ouch. Sorry that your phone ended up that way. Sort of a "live brick".
I have flashed, rooted, unrooted, installed Eris ROMs via adb, fastboot, manually with unyaffs, rolled back bootloaders (8 ways to Sunday) - and I don't think there is anything more I could do with your phone even if I had it in my hands.
It's not very ethical, because it is (in fact) your fault that the phone ended up that way it did - but have you considered having VZW replace it?
bftb0
bftb0 said:
It's not very ethical, because it is (in fact) your fault that the phone ended up that way it did - but have you considered having VZW replace it?
bftb0
Click to expand...
Click to collapse
I've thought about it, I can justify the morality to myself by asserting that their is really nothing wrong with the hardware and assuming they have some means of reprogramming it that I don't have access to. The other side to that is, they may have some way of seeing what's been done to it that I don't know about, and then do I get charged?
Well, I took it in store and they just swapped it out, hoping they don't come back at me if they find anything when it gets back to factory. Thanks again for your help.
USSENTERNCC1701E said:
Well, I took it in store and they just swapped it out, hoping they don't come back at me if they find anything when it gets back to factory. Thanks again for your help.
Click to expand...
Click to collapse
Good luck with the new phone. If you plan on rooting, take your time and read as much as you can in the dev forum.
bftb0
if you are rooted and have a recovery and need to return to stock OTA do this:
http://forum.xda-developers.com/showthread.php?t=792026&highlight=cupcake
edit, I see you resolved it already, thats what I get for not reading the thread.
The flash down to cupcake method works in all cases because it overwrites everything on the phone when the 2.1 OTA comes. The only safe stuff is on your SD Card
All I can see is the HTC logo with 4 ! inside of a triangle on each corner. This is a been bricked for a long time and I cant remember how it happened but just wonder is there is anyway to fix it
Thanks,
The state your phone is in sounds similar to this
http://forum.xda-developers.com/showthread.php?t=824290
but there is no way to be sure of that, based on the zero details you provided.
Read the ENTIRE POST, not just part of it (it is quite long).
WOW, exactly the same problem this phone has!
If I remember right it was a mix up with ClockworkMod recovery.
That was a very nice recovery, I will have to read and learn all that. That's a lot of info and stuff that I will have to learn to try to fix this phone.
I think all that is AWAY over my head... lol
OMG my head hurts now... lol
stick2e said:
I think all that is AWAY over my head... lol
OMG my head hurts now... lol
Click to expand...
Click to collapse
You don't need to understand the bit where sosicwitit was repartitioning.
If you can only get into that one mode ("RUU mode"), and not HBOOT, nor FASTBOOT, nor recovery, then the only avenue available is to first try his "trick" of flashing the RUU, but dropping the Root PB00IMG.ZIP file into the "rom.zip" file location of the RUU. If you are lucky, that will get you a working S-OFF bootloader. Try that first and report your results.
bftb0
bftb0 said:
You don't need to understand the bit where sosicwitit was repartitioning.
If you can only get into that one mode ("RUU mode"), and not HBOOT, nor FASTBOOT, nor recovery, then the only avenue available is to first try his "trick" of flashing the RUU, but dropping the Root PB00IMG.ZIP file into the "rom.zip" file location of the RUU. If you are lucky, that will get you a working S-OFF bootloader. Try that first and report your results.
bftb0
Click to expand...
Click to collapse
I have the leak v3 PB00IMG.ZIP, however did you have any idea where is the temp file that is created where I can change rom.zip? I'm running windows 7 32bit.
I can get into FASTBOOT and RUU mode but that all I can do with this unit.
Thanks again!
stick2e said:
I have the leak v3 PB00IMG.ZIP, however did you have any idea where is the temp file that is created where I can change rom.zip? I'm running windows 7 32bit.
I can get into FASTBOOT and RUU mode but that all I can do with this unit.
Thanks again!
Click to expand...
Click to collapse
Well, first off - you should say what version of the boot loader you have. It is shown on the fastboot screen. If you already have the 1.49.2000 S-OFF bootloader this current step can be skipped, And you can proceed directly to flashing a recovery using fastboot from the pc. If you do not have the S-OFF bootloader the whole point of this current step is to get it on the phone - in which case you should be using the ROOT PB00IMG.ZIP file, not the Leak-V3 PB00IMG.ZIP file.
All Eris RUU and PB00IMG.ZIP files can be found at:
http://forum.xda-developers.com/showthread.php?t=909921
When the RUU program is running, just prior to the moment when you would begin flashing to the phone, you use the search function on your PC in the folder
C:\Documents and Settings\<your_user_name>
(Edit - in Win7, C:\Users\<your_user_name> )
to look for the file named "rom.zip". (You will probably need to twiddle the dumbass Microsoft setting which prevents searching for hidden files and folders.)
Then, you delete the rom.zip file, rename the ROOT PB00IMG.ZIP file to rom.zip, and drop it into the same location.
Before starting this step, make sure your phone is completely charged and also be sure to verify the file size and md5 checksum of the ROOT PB00IMG.ZIP file you downloaded.
As I mentioned above if you already have the S-OFF bootloader present on your phone, this operation is not necessary and we can proceed to flashing a recovery using the fastboot program on the PC.
Lemme know how it goes.
PS - It would be helpful for you to answer a few questions about your current skill set and computer setup:
- have you used either the "fastboot" or "adb" programs in the past on your pc?
- if not, do you know how to verify communication with the phone in fastboot mode?
(Note that running the RUU utility will install drivers on your PC)
The original Amon_RA recovery for the Eris can be found here:
http://forum.xda-developers.com/showthread.php?t=648025
I have sdk setup and FASTBOOT can see the phone however ADB dont see the phone. If I do adb devices, nothing get listed.
stick2e said:
I have sdk setup and FASTBOOT can see the phone however ADB dont see the phone. If I do adb devices, nothing get listed.
Click to expand...
Click to collapse
"fastboot devices" when the phone is in fastboot mode.
adb only applies when the normal OS is running with USB debugging turned on, or if the Amon_RA recovery is booted.
What bootloader version do you have?
This is where the phone is right now.
1.49.0000 S-ON bootloader
When I get home today I will look for the proper img file and try the RUU option to see if I can get the S-OFF in there. We will see.
If you can get the S-OFF bootloader to "take" with the RUU+rom.zip replacement trick, and you can communicate with fastboot, then
fastboot flash recovery recovery-RA-eris-v1.6.2.img
is the next step.
Please report any errors that the RUU utility reports - we want to figure out which partitions got corrupted by ClockworkMod.
PS - don't let the phone sit in fastboot mode for extended periods of time - it will discharge rapidly even if it is plugged into the charger
This thread honestly scares me and I hope this never happens to me lol
willwgp said:
This thread honestly scares me and I hope this never happens to me lol
Click to expand...
Click to collapse
All you need to remember is this:
newb + Eris + ClockworkMod = disaster waiting to happen
In almost every bricking that has been reported here on the (XDA) Eris forums, ClockworkMod (or running the battery down to very low charge levels) was involved.
What is also notable is that in almost every case, the folks that got into trouble:
- got their rooting instructions from non-XDA sites (e.g. unrevoked, z4root, unlockr)
- could not clearly explain what they had been doing immediately prior to the event - even after repeatedly being asked to do so,
- were unaware what ROM signing is about (or that ClockworkMod doesn't perform it)
The second observation seems to imply a behavioral trait of innattention or sloppiness.
In the hands of people that are experienced, ClockworkMod seems to behave correctly.
For the moment though, let's stay on topic and see if we can revive stick2e's phone. At the moment, I am guessing that there is about a 30% chance of that. We'll find out more when we hear the result of his/her flashing attempt.
bftb0
I think this is going to work!!!! Thinks are looking better.
I try to flash the RUU but replace the rom.zip (what a pain to find it!!!) with the root rom (PB00IMG.ZIP: Eris_RootROM_v2.19.605.1_PB00IMG.zip) and now I have to load a rom in the sdcard to flash the phone. Fingers crossed we will see.
I'm downloading a ROM now.
RUU Error is 110 but I'm on HBOOT-1.49.2000 and S-OFF
Now?
Ok, I need help on what file to select. I dont think that I grab the right file :-(
In the mind time... charging the battery again!
stick2e said:
RUU Error is 110 but I'm on HBOOT-1.49.2000 and S-OFF
Now?
Ok, I need help on what file to select. I dont think that I grab the right file :-(
In the mind time... charging the battery again!
Click to expand...
Click to collapse
DId you rename the new PB00IMG.zip file to rom.zip?
bftb0 said:
If you can get the S-OFF bootloader to "take" with the RUU+rom.zip replacement trick, and you can communicate with fastboot,
Click to expand...
Click to collapse
Ok, HBOOT-1.49.2000 and S-OFF
bftb0 said:
then
fastboot flash recovery recovery-RA-eris-v1.6.2.img
is the next step.
Click to expand...
Click to collapse
C:\sdk\tools>fastboot flash recovery recovery-RA-eris-v1.6.2.img
sending 'recovery' (3834 KB)... OKAY [ 0.826s]
writing 'recovery'... OKAY [ 1.357s]
finished. total time: 2.183s
bftb0 said:
Please report any errors that the RUU utility reports - we want to figure out which partitions got corrupted by ClockworkMod.
Click to expand...
Click to collapse
RUU Utility report ERROR [110]: FILE OPEN ERROR
Parsing... [download ZIP]
[1] User Data - OK
[2] System - Fail-PU
[3] Recovery - OK
[4] Radio_V2 - OK
[5] Boot - Fail-PU
Partition update fail!
Update Fail!
Gimme a minute to fire up a real computer instead of this stupid phone browser.
Well, I fastboot recover revery-RA-eris-v1.6.2.img but nothing happen now :-(
Before used to take me to RA Recovery but now is not.
So in my efforts to update my phone, I downloaded the July 2010 OTA radio. I also tried flashing the sprint radio 2.42.02.10.29
To my surprise, neither of them worked. It's like I am permanently unable to flash a radio. I can flash roms, themes, boot animations and everything else, just not radios. If anyone has any suggestions for this I greatly appreciate it. Here are the radios I've tried to flash and where I got them from.
2.42.01.04.27 from http://forum.xda-developers.com/showthread.php?t=728529
2.42.02.10.29 from http://forum.xda-developers.com/showthread.php?t=853868
Haven't seen anyone else on here ever have this issue except for 1 person and when I checked his post, no one had replied to it and it was almost a year old lol. Any help with this at all ?
spc_hicks09 said:
2.42.02.10.29 from http://forum.xda-developers.com/showthread.php?t=853868
Haven't seen anyone else on here ever have this issue except for 1 person and when I checked his post, no one had replied to it and it was almost a year old lol. Any help with this at all ?
Click to expand...
Click to collapse
So you are saying that you followed those instructions exactly and it did not flash?
In other words, you:
- copied that 2.42.02.10.29.zip file to the root of your SD card;
- you checked the MD5 of that file to make sure that it was fully downloaded;
- restarted in recovery and flashed that .zip file;
- you rebooted the phone and a very different screen appeared;
- it went back to Recovery with a message at the bottom saying "formatting cache..."
- you waited about a minute (it says 5 seconds, but I waited longer) and then rebooted the phone
And your radio baseband version did not update?
That's exactly what I'm saying. I flashed both radios and waited 10-15 on both of them and neither one of them did anything !?! So confused
Sent from my Ginger Tazz using XDA App
Well, if it's any consolation I haven't noticed anything different about that radio. People report that they get more "bars", but that's just a display thing - it doesn't mean that they get better performance or signal from the radio version.
You can try unrooting with btfb0's Flashback21 ROM - there is a version that flashes the current Verizon radio - and then re-root after that and see if it updates the radio for you.
http://forum.xda-developers.com/showthread.php?t=792026
Take the version of that with the radio, obviously.
What bootloader (version) and recovery (version) are on the phone when you perform the flashing operation?
What is the version # of the radio firmware which doesn't get removed/overflashed?
When you complete the flashing operation, are you using the reboot menu item? (I'm presuming you are not pulling the battery or something unusual like that, but thought I would ask for completeness sake)
bftb0
PS If you have the engineering bootloader on your phone (1.49.2000 S-OFF), you can just flash the radio with fastboot from the PC:
Code:
fastboot flash radio radio.img
bftb0 said:
What bootloader (version) and recovery (version) are on the phone when you perform the flashing operation?
What is the version # of the radio firmware which doesn't get removed/overflashed?
When you complete the flashing operation, are you using the reboot menu item? (I'm presuming you are not pulling the battery or something unusual like that, but thought I would ask for completeness sake)
bftb0
PS If you have the engineering bootloader on your phone (1.49.2000 S-OFF), you can just flash the radio with fastboot from the PC:
Code:
fastboot flash radio radio.img
Click to expand...
Click to collapse
At work now but I will check it out when I get home. Im not sure how to check some of the stuff you're talking about so I will need your guidance later if possible.
Sent from my Ginger Tazz using XDA App
bftb0 said:
What bootloader (version) and recovery (version) are on the phone when you perform the flashing operation?
What is the version # of the radio firmware which doesn't get removed/overflashed?
When you complete the flashing operation, are you using the reboot menu item? (I'm presuming you are not pulling the battery or something unusual like that, but thought I would ask for completeness sake)
bftb0
PS If you have the engineering bootloader on your phone (1.49.2000 S-OFF), you can just flash the radio with fastboot from the PC:
Code:
fastboot flash radio radio.img
Click to expand...
Click to collapse
Recovery Version
RA-eris-v1.6.2
On HBOOT screen I see this:
PB00100 XC SHIP S-ON
HBOOT-1.49.0000 (PB0010000)
MICROP-0111
TOUCH PANEL-MELFAS_45_17
RADIO-2.42.00.04.12
FEB 8 2010, 00:08:56
Radio that will not change or anything is:
2.42.00.04.12 which is the pre July 2010 OTA update Radio
Yes you presumed right, I am "rebooting" through the recovery menu as opposed to pulling the battery or anything else.
Executive summary: just get the engineering bootloader (1.49.2000 S-OFF) installed on your phone, and flash radios using fastboot (being very very careful to verify MD5 signatures). If you are going to be flashing stuff to your phone frequently, you really want the S-OFF bootloader on your phone for disaster recovery reasons anyway.
OK, I ran a fairly long experiment on your behalf, and it went like this:
- flash 2.42.02.10.29.zip from Amon_RA (succeeded; bootloader was 1.49.2000 S-OFF)
- flashed older radio (2.42.00.04.12) image file back into place using fastboot (not Amon_RA)
- Downgraded my bootloader to 1.49.000 S-ON using fastboot
- flash 2.42.02.10.29.zip from Amon_RA (failed; bootloader was 1.49.0000 S-ON)
- Upgraded my bootloader using "erisengspl.zip" + Amon_RA **** back to 1.49.2000 S-OFF
- flash 2.42.02.10.29.zip from Amon_RA (failed; bootloader was 1.49.2000 S-OFF)
- rebooted once (into OS) and then booted into recovery
- flash 2.42.02.10.29.zip from Amon_RA (succeeded; bootloader was 1.49.2000 S-OFF)
So, I was expecting to see that your trouble had something to do with your bootloader version - especially after seeing the first failure that I observed ... but then I was able to get it to both succeed and fail using the same S-OFF (1.49.2000) bootloader - and the only thing which changed was that I rebooted once between the trial that succeeded, and the trial which failed.
At that point, I did not go back and re-run any trials with the 1.49.0000 S-ON bootloader to see if I could get it to suceed - because it was evident that something else was going on.
Some of this is not entirely unexpected. When you flash either of the firmware images (either the radio or the bootloader image files), it is actually the bootloader that does the flashing, not the recovery boot: that's why the recovery tells you to "reboot .... to complete the installation". What the recovery does is to "stage" the image file (in /cache, I suspect), and then write some instructions into the "misc" partition that tell the bootloader what to do the next time the phone resets.
That's why - when things work correctly - the phone momentarily goes dark, you see a graphic image on the screen (that suggests that flashing is taking place), and then the phone reboots again ... and ends up back in the recovery boot !! (You will have to take my word for it, if you don't remember what it looks like). That "flashing" graphic image is put up on the screen by the bootloader; when it finishes up, it chains back to the recovery boot ... and communicates to the recovery (via the either the misc partition or the cache partition), "hey, wipe the /cache partition as soon as you start up". (Note the implications - the next OS reboot will need to rebuild the dalvik-cache(s))
The thing is, "misc" gets written to every time the phone shuts down or boots up - whether we are talking about starting from the OS, from the recovery boot, from fastboot mode, or from RUU mode - and how many different ways are there to reboot?
- battery pull
- fastboot reboot-recovery
- fastboot reboot
- adb shell reboot bootloader
- adb shell reboot recovery
- reboot Amon_RA from menu
- (cold start) -> fastboot mode -> hboot mode -> recovery
- (cold start) -> hboot mode -> recovery
- (cold start) -> recovery
In any event, if you want to tease this all out, with some experimenting around with the way that you get into the recovery boot, you can probably get the flashing method to work. ( For instance, you could probably use an adb shell session with Amon_RA running to "flash_image misc misc.img", where "misc.img" is the image file from jcase's "Flash Any RUU post" - and then use the flashable radio .zip file from within Amon_RA. )
But, as I mentioned above, it is a lot easier to just punt and install radios using fastboot and the S-OFF bootloader. Just be sure you have triple-checked everything before you hit the Enter key.
bftb0
**** EXTREMELY DANGEROUS UNLESS THE EXISTING BOOTLOADER IS 1.49.0000 - "erisengspl.zip" has hard-bricked phones that had 1.46.0000 bootloaders!
I really appreciate all the work man ! I did a search in the forums though and can't find the S-OFF bootloader. As soon as I read your question about the bootloader I was seriously wondering if it was because I have the S-ON bootloader. However, since you got both a success and a fail with the S-ON i'm not sure now what to think. I would like to get the S-OFF bootloader though so if you got a link to that, it would be greatly appreciated. Also again, thank you for the hard work and the time you put into all this man. Your knowledge never ceases to amaze me !
This would be what I want correct ?
http://forum.xda-developers.com/showthread.php?t=725047
Seems like a lot of work to get 1.49.2000 S-OFF
Also, do I have to go back to stock to do this ?
spc_hicks09 said:
I really appreciate all the work man ! I did a search in the forums though and can't find the S-OFF bootloader. As soon as I read your question about the bootloader I was seriously wondering if it was because I have the S-ON bootloader. However, since you got both a success and a fail with the S-ON i'm not sure now what to think. I would like to get the S-OFF bootloader though so if you got a link to that, it would be greatly appreciated. Also again, thank you for the hard work and the time you put into all this man. Your knowledge never ceases to amaze me !
This would be what I want correct ?
http://forum.xda-developers.com/showthread.php?t=725047
Seems like a lot of work to get 1.49.2000 S-OFF
Also, do I have to go back to stock to do this ?
Click to expand...
Click to collapse
You don't need to go back to stock to do that. That post will work. Slightly more effort than necessary, though.
You probably ought to familiarize yourself with the "old-fashioned" method of flashing a PB00IMG.ZIP file (see this post on AF (lots of pictures) for some background). All Eris RUUs, OTAs, and PB00IMG.ZIP files can be found at this XDA post
Because you have the 1.49.0000 S-ON bootloader, your phone would previously have been referred to as a "Leaker" phone. The only thing which stood in the way of "Leakers" applying any PB00IMG.ZIP file is that the "misc" partition contains a version number in it which blocks that from happening. jcase's method in that post you provided a link to is to "patch" the misc image with an older version number, and then you can proceed with any PB00IMG.ZIP file installation after you have patched the "misc" partition.
There is another option available to you, though, but I am reluctant to suggest it to you: because you have the 1.49.0000 bootloader, the "erisengspl.zip" flash method of installing the bootloader should work for you. (IT HAS BRICKED A 1.46.0000 PHONE, and there have been only a few people that have used it - I did it one hour ago, but hey, that's my phone, and there's a huge difference between doing something to your own phone and telling other people to do it).
If you want to try an alternative method, which should be:
- less effort than the URL link you provided
- safer than using "erisengspl.zip"
I could whip up a flashable version of "misc.img" - that way you don't need to fool around with adb commands - you would just flash a zip file that patches misc.img (instead of doing that manually with adb), and then after that just install the Root PB00IMG.ZIP ROM by putting it on the root folder of your SD card and powering up your phone (after you have made Nandroid backups and fully charged your phone, of course).
Say the word and I'll cobble that together.
bftb0
Here you go...
Introducing...
ErisMiscReset_v0.9.zip :
Size: 53,784 bytes
MD5: aeb8f3d9b2ab39379b8ee563c76efee0
Credits: jcase (for the misc.img file); Amon_RA (for the flash_image binary - from his v1.6.2 Eris recovery)
This doesn't do anything special - it just flashes the embedded "misc.img" file (jcase) to the "misc" partition. It could be done the hard way (with adb and the command line), but this makes life a little easier.
bftb0
bftb0 said:
You don't need to go back to stock to do that. That post will work. Slightly more effort than necessary, though.
You probably ought to familiarize yourself with the "old-fashioned" method of flashing a PB00IMG.ZIP file (see this post on AF (lots of pictures) for some background). All Eris RUUs, OTAs, and PB00IMG.ZIP files can be found at this XDA post
Because you have the 1.49.0000 S-ON bootloader, your phone would previously have been referred to as a "Leaker" phone. The only thing which stood in the way of "Leakers" applying any PB00IMG.ZIP file is that the "misc" partition contains a version number in it which blocks that from happening. jcase's method in that post you provided a link to is to "patch" the misc image with an older version number, and then you can proceed with any PB00IMG.ZIP file installation after you have patched the "misc" partition.
There is another option available to you, though, but I am reluctant to suggest it to you: because you have the 1.49.0000 bootloader, the "erisengspl.zip" flash method of installing the bootloader should work for you. (IT HAS BRICKED A 1.47.0000 PHONE, and there have been only a few people that have used it - I did it one hour ago, but hey, that's my phone, and there's a huge difference between doing something to your own phone and telling other people to do it).
If you want to try an alternative method, which should be:
- less effort than the URL link you provided
- safer than using "erisengspl.zip"
I could whip up a flashable version of "misc.img" - that way you don't need to fool around with adb commands - you would just flash a zip file that patches misc.img (instead of doing that manually with adb), and then after that just install the Root PB00IMG.ZIP ROM by putting it on the root folder of your SD card and powering up your phone (after you have made Nandroid backups and fully charged your phone, of course).
Say the word and I'll cobble that together.
bftb0
Click to expand...
Click to collapse
Ok quick question. After doing some digging, I found a post where jcase was working on a flashable zip that would give 1.49.2000 S-OFF. Someone noted that he no longer had an Eris and abandoned the project after pulling it. Well someone else "drewrobinso" picked up where jcase left off and finished the zip and in the post, starting at post 32 he posted that he fixed jcase's file and people after that say it "works perfectly." So I was wondering what your opinion is on this method. It can be found here.
http://forum.xda-developers.com/showthread.php?t=742735&highlight=engineering+bootloader&page=4
Here are the instructions they give for the hboot1492.zip
1) Download hbootupdate.zip
2) Placed it on root of sdcard
3) booted Recovery
4) nand backup
5) flashed hbootupdate.zip
6) rebooted (with menu) after the install of the hboot.zip
7) waited untill it came back to the recovery screen with " formatting cache..." at the bottom.
8) Waited for a few min then pressed reboot from the menu again.
9) waited for it to boot up and rebooted in to hboot as S-OFF was there
10) enjoyed it
spc_hicks09 said:
So I was wondering what your opinion is on this method. It can be found here.
Click to expand...
Click to collapse
Probably equivalent to the "erisengspl.zip" file (I haven't used it or looked at it) - you can find both, unpack them, and compare the differences. They should be extremely similar. I think the reason that jcase pulled his effort is because someone ended up with a brick - but I can't be 100% certain of that.
The thing you should be aware of is the lack of testing that goes into stuff on XDA. That "erisengspl.zip" floated around on XDA for months, and a few people in fact used it successfully. Those few people happened to be "Leakers" (with 1.49.0000 S-ON) on their phones.
The first person to try it with the 1.46.0000 S-ON bootloader on his phone hard-bricked his phone.
I suppose that it will work for you - but, flashing the bootloader is the most dangerous thing you can do to your phone. I prefer to be conservative about it.
LOL, I just realized that I said that after flashing it three times today.
PS we posted 60 seconds apart - look up above your post for a "misc" flasher .zip
bftb0 said:
PS we posted 60 seconds apart - look up above your post for a "misc" flasher .zip
Click to expand...
Click to collapse
Oh lol, sorry about that. Ok so if I use the misc flashable zip, which PB00IMG.ZIP would I want for the S-OFF, Leak 3 or the Root one ? I'll just use the method you're suggesting but I have no idea which PB00IMG.ZIP to use.
Nevermind lol obviously it would be the Root one since it's the only one with the Engineering Bootloader. Ok so if I downloaded the misc reset file and the PB00IMG.ZIP, do I flash the misc reset zip then the PB00IMG or what ?
bftb0 said:
If you want to try an alternative method, which should be:
- less effort than the URL link you provided
- safer than using "erisengspl.zip"
I could whip up a flashable version of "misc.img" - that way you don't need to fool around with adb commands - you would just flash a zip file that patches misc.img (instead of doing that manually with adb), and then after that just install the Root PB00IMG.ZIP ROM by putting it on the root folder of your SD card and powering up your phone (after you have made Nandroid backups and fully charged your phone, of course).
Say the word and I'll cobble that together.
bftb0
Click to expand...
Click to collapse
Nevermind LOL ! I swear as I get older I forget more and more stuff ! You gave me the directions right in your other post hahahaha. Ok so i'm going to charge my phone up then follow the instructions in this post and hopefully a couple hours from now I'll have the S-OFF bootloader. I'll definitely keep you updated once I start the process and hopefully we can get this resolved !!!
Flashed the zip and got the PB00IMG loading now. So far so good !
Now saying 1.49.2000 S-OFF !!!! Now it's going through and loading the system, recovery, radio_v2. Everything says -OK so far !
Rebooting now.......on the Verizon splash screen.............now it's not going anywhere just stuck on the Verizon logo !
Nevermind it booted ! Just took a while to load up !!!! Soon as everything is done loading I will check and see what the HBOOT screen says now.
Software Info:
Firmware - 2.1
Baseband - 2.40.00.01.22
Kernel - 2.6.29-5898f66b [email protected] #1
Build Number - 2.19.605.1 CL123435 test keys
Software Number - 2.19.605.1
Browser Version - WebKit 3.1
PRI Version - 2.11_002
PRL Version - 52219
ERI Version - 5
Rooting now with Eris 1 Click and will post HBOOT info in a few minutes.
spc_hicks09 said:
Nevermind LOL ! I swear as I get older I forget more and more stuff ! You gave me the directions right in your other post hahahaha. Ok so i'm going to charge my phone up then follow the instructions in this post and hopefully a couple hours from now I'll have the S-OFF bootloader. I'll definitely keep you updated once I start the process and hopefully we can get this resolved !!!
Click to expand...
Click to collapse
- Get the Root PB00IMG.ZIP file from this XDA post
- Verify it's size and MD5 signature on the copy you transferred to the root folder on your SD card.
- Put your phone on a charger.
- While it is charging, read through this post on AF (lots of pictures)
- Wait until fully charged, and
- Boot into recovery and make a Nandroid backup.
- (Optional: wipe data/factory reset)
- Flash the ErisMiscReset_v0.9.zip
- Power the phone off
- Boot the phone into HBOOT mode (Vol-Down+End)
- Follow the instructions in that Android Forums thread (PB00IMG.ZIP install)
Note that if you do not do the battery-pull trick, you will be overwriting everything on the phone. (That's OK because you have a backup, right?). If you did the "battery pull trick", you are done.
You can re-root the "root ROM" at that point, or, just skip that and use fastboot on your PC to directly flash the recovery to your phone. Put the phone in fastboot mode (cold-start with Send+End), and then test connectivity to the PC with:
Code:
fastboot devices
You should see your phone ID number if you are communicating correctly. Then,
Code:
fastboot flash recovery recovery-RA-eris-v1.6.2.img
Then, boot into Amon_RA directly by cold-starting the phone with Vol-Up+End, and "wipe data/factory reset" and restore your Nandroid backup.
Finally, you can flash a radio image directly at this point. (Note that we are not talking about a zip file, but the individual "radio.img" file that you would dig out of the 2.42.blahblahblah.zip file). Restart the phone in Fastboot Mode (Send+End) and
Code:
fastboot flash radio radio.img
Don't forget to remove the PB00IMG.ZIP file from the root folder of your SD card - otherwise you will forget about it and the next time you boot into HBOOT mode, the bootloader will start loading it up again.
HTH
bftb0
This explains a lot... Thanks.
I've not been able to figure out why my radio won't update until now.
And it allllllllll WORKED !!!!
HBOOT Info:
PB00100 XC ENG S-OFF
HBOOT-1.49.2000 (PB0010000)
MICROP-0111
TOUCH PANEL-MELFAS_45_17
RADIO-2.40.00.01.22
Jan 24 2010, 22:35:57
Dude you are a frickin genius !!!!! LOL
So now I should be able to update my Radio with either fastboot or adb or just by flashing right ?
You should make a main topic in Developement about your new method to get S-OFF. That was so much more simple than ANYTHING else I found !
Where do I need to have the Radio.img file because I have it in the ADB folder right now, trying to flash through fastboot but it keeps saying "error cannot load radio.img"
spc_hicks09 said:
And it allllllllll WORKED !!!!
Click to expand...
Click to collapse
You've now experienced "old school Eris root".
spc_hicks09 said:
So now I should be able to update my Radio with either fastboot or adb or just by flashing right ?
Click to expand...
Click to collapse
You certainly should be able to do it with fastboot. As I said before, I'm not precisely sure what was causing your Amon_RA installs to fail.
Just make sure you always, always, always verify file MD5 sigs of image files before flashing them with fastboot.
bftb0
Hello,
This is an odd request, but I'm in need of some help with this HTC Rezound. A bit of background first. It's not mine. I'm a G2 user (rooted and I know my way around Android hacking). This phone belongs to a friend and despite having it rooted he knows nothing about how he got there or how to fix a problem. Currently it's stuck in a bootloop. He mailed the phone to me (we live 750 miles apart) and he's hoping I might be able to assist. I can get into recovery (I'm assuming it's a custom recovery - looks like ClockworkMod) and my hope was to flash a new ROM but he stupidly neglected to send the phone to me with an SD Card. I'm wondering if there's a way to get a ROM/gapps onto the phone (internal storage) and flash from there. I see there's an option for USB-MS toggle and I've tried playing around in the internal_sd area, and I can get a G: drive to appear when choosing this and connected via USB to my computer, but when I put the ROM/gapps on there I cannot seem to access it for flashing purposes.
Sorry for the long-winded description. But is this a simple solution? Do I just need to get a hold of an SD card and put the files needed on there for flashing? Or is there a way to flash the ROM directly from internal storage?
Thanks in advance for any help you might provide.
Could you post a "fastboot getvar all" ? Without the commas.
Also one thing I would do. Flash twrp 2.6.3.0 Then mount the phone. Push the ROM using a adb push. But first could you post a fastboot getvar all ?
Sent from my Rezound running Sense 5. S-OFF
pball52998 said:
Could you post a "fastboot getvar all" ? Without the commas.
Also one thing I would do. Flash twrp 2.6.3.0 Then mount the phone. Push the ROM using a adb push. But first could you post a fastboot getvar all ?
Sent from my Rezound running Sense 5. S-OFF
Click to expand...
Click to collapse
Sorry for my noobness, but I have no idea how to do that with this phone. I know nothing about HTC devices - never owned one before.
No problem at all man, we all start somewhere for every phone company.
Okay, pull the battery out. Put it back in, volume down, power button. It should show up a white screen. With I think like 5 options, I know the first two are: fastboot and recovery. When highlighted over fastboot, press power. Then will bring you to fastboot. It'll say in red letters "FASTBOOT USB" at the top. Plug it into the computer open a cmd prompt where you fastboot/adb also known as platform-tools is. Type fastboot getvar all
Sent from my Rezound running Sense 5. S-OFF
pball52998 said:
No problem at all man, we all start somewhere for every phone company.
Okay, pull the battery out. Put it back in, volume down, power button. It should show up a white screen. With I think like 5 options, I know the first two are: fastboot and recovery. When highlighted over fastboot, press power. Then will bring you to fastboot. It'll say in red letters "FASTBOOT USB" at the top. Plug it into the computer open a cmd prompt where you fastboot/adb also known as platform-tools is. Type fastboot getvar all
Sent from my Rezound running Sense 5. S-OFF
Click to expand...
Click to collapse
Thanks for the reply. My time messing with the phone is done for the night, but I'll give that a try tomorrow.
Okay sounds good
Sent from my crappy Jailbroken apple iPad.....
Freedoms just another word for nothing left to do... Nothin' ain't worth nothing but it's free.....
It should say something in the bootloader at the top like below:
***unlocked***
Pvt ship s-off (or s-on)
Hboot version # stuff here
Radio version # stuff here
Is it s-off or s-on?
If it's secure flag is still on, you would need to extract the boot.IMG from your ROM zip and do the following command after pushing and flashing the ROM in recovery. After you do flash the ROM, boot back into bootloader and into fastboot and type the following command in PC terminal
Fastboot flash boot boot.img
Sent from my Rezound
Uzephi said:
It should say something in the bootloader at the top like below:
***unlocked***
Pvt ship s-off (or s-on)
Hboot version # stuff here
Radio version # stuff here
Is it s-off or s-on?
If it's secure flag is still on, you would need to extract the boot.IMG from your ROM zip and do the following command after pushing and flashing the ROM in recovery. After you do flash the ROM, boot back into bootloader and into fastboot and type the following command in PC terminal
Fastboot flash boot boot.img
Sent from my Rezound
Click to expand...
Click to collapse
Yep, pretty much, what I was trying to get him through first was actually pushing a ROM to the phone, also the fastboot getvar all gives almost all info. But true with that, that's probably the MOST important part of rooting and ROMing HTC lol. Although he never stated what rom he has. Trying to get him through some basics of HTC too.
Sent from my Rezound running Sense 5. S-OFF
Yeah, just wanted to put that out there in case he found it how to flash a ROM without us, he will see that post to fix his boot loop (if s-on)
Sent from my Rezound
Thanks again for the replies everyone. Very helpful. As stated before, this is an odd situation because I know nothing about rooting/ROMs for HTC and this isn't my phone.
Anyway, a bit of where I'm at and some better info regarding the phone's situation. The phone, upon attempting to boot, would just bootloop. I don't remember exactly which ROM was on there as I've since done a factory reset, but needless to say it wasn't working. Also, I happened to track down an SD card from an old phone of mine and I used the USB-MS feature in recovery to put a ROM on there for flashing. Wiped everything as I would any other phone, flashed the ROM (which stated was successful) and upon a reboot the phone just hangs on the white HTC screen. Did a bit of digging and decided to try returning to stock (he doesn't care if this phone is still rooted, just wants it working). Found this link http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/ and followed the instructions exactly. Update seemed to take just fine, but again a reboot just got me stuck on the white HTC screen.
I've yet to hook this up to try the fastboot getvar thing as the computer I'm using didn't have ADB installed and I didn't have the time to do so. In the meantime any additional suggestions?
I'm attaching a pic of the phone in hboot so you can see some info that might be helpful.
The reason the phone froze at the HTC screen is because that phone is s-on...
In HTC world, there is the bootloader lock (the purple thing at the top saying unlocked) and the secure flag.
With the bootloader unlocked, you can flash on virtually any partition (only signed firmware and other technical stuff that is irrelevant in your situation) but when booted in recovery, you cannot flash to the boot partition. (Can only do that when s-off)
To flash the boot partition when unlocked s-on (secure flag on) you need to extract the boot.IMG from the ROM and flash it while in fastboot mode from the hboot.
To RUU (return to complete stock) you also need to flash upwards or same version firmware officially signed by HTC when s-on. If you are s-off then you can downgrade. Also, bootloader needs to be locked again.
TL/DR: flash the boot image following my post above and that ROM you flashed will work.
Sent from my Rezound
Uzephi said:
The reason the phone froze at the HTC screen is because that phone is s-on...
In HTC world, there is the bootloader lock (the purple thing at the top saying unlocked) and the secure flag.
With the bootloader unlocked, you can flash on virtually any partition (only signed firmware and other technical stuff that is irrelevant in your situation) but when booted in recovery, you cannot flash to the boot partition. (Can only do that when s-off)
To flash the boot partition when unlocked s-on (secure flag on) you need to extract the boot.IMG from the ROM and flash it while in fastboot mode from the hboot.
To RUU (return to complete stock) you also need to flash upwards or same version firmware officially signed by HTC when s-on. If you are s-off then you can downgrade. Also, bootloader needs to be locked again.
TL/DR: flash the boot image following my post above and that ROM you flashed will work.
Sent from my Rezound
Click to expand...
Click to collapse
Thanks for this. I think I get what you're saying, but just for the sake of clarification, one more question regarding this process.
I extract the boot.IMG from my ROM of choice, flash the ROM/gapps as I would on any other device, then go back to fastboot and run the adb commands posted earlier? Correct?
Rodeojones said:
Thanks for this. I think I get what you're saying, but just for the sake of clarification, one more question regarding this process.
I extract the boot.IMG from my ROM of choice, flash the ROM/gapps as I would on any other device, then go back to fastboot and run the adb commands posted earlier? Correct?
Click to expand...
Click to collapse
Exactly. Be sure to do exactly that command not
Fastboot boot boot.img
If you forget to say flash boot, it will just temporarily boot that kernel/boot image and not flash it to the device. Then upon reboot you will be back at step one.
Sent from my Rezound
Uzephi said:
Exactly. Be sure to do exactly that command not
Fastboot boot boot.img
If you forget to say flash boot, it will just temporarily boot that kernel/boot image and not flash it to the device. Then upon reboot you will be back at step one.
Sent from my Rezound
Click to expand...
Click to collapse
Again, thank you. Going to give this a go after my son's t-ball game. I feel like more of a noob than when I rooted my OG Droid years ago.
@Uzephi, @pball52998, thank you to for your assistance. I felt like a total noob working on a phone that wasn't mine. But I've got it up and running again. My friend Jake will be very happy (I've also told him that this is the last ROM he will ever put on here unless he learns how to do everything I just did - he didn't even know what ADB was when I told him).
Rodeojones said:
@Uzephi, @pball52998, thank you to for your assistance. I felt like a total noob working on a phone that wasn't mine. But I've got it up and running again. My friend Jake will be very happy (I've also told him that this is the last ROM he will ever put on here unless he learns how to do everything I just did - he didn't even know what ADB was when I told him).
Click to expand...
Click to collapse
Wait! He has old HBOOT and Radios, the newest radio is 1.28 he has 1.21 I think I saw.... I would suggest s-off then RUU and doing a RUU.... Or if anyone has em, the HBOOT and Radios you can flash in recovery.
pball52998 said:
Wait! He has old HBOOT and Radios, the newest radio is 1.28 he has 1.21 I think I saw.... I would suggest s-off then RUU and doing a RUU.... Or if anyone has em, the HBOOT and Radios you can flash in recovery.
Click to expand...
Click to collapse
Flashing them in recovery would be great, if there's a link to download the files. But just to be clear, despite this phone finally booking up there's more I need to do to make it 100% usable?
It is 100% usable, but you will experience less overheats and better battery life with the new firmware. I know the hboot ph98img zip is somewhere in this forum for the updated hboot and radio (for that zip you would just put in root of external SD card and in hboot it will automatically flash)
Sent from my Rezound
Uzephi said:
The reason the phone froze at the HTC screen is because that phone is s-on...
In HTC world, there is the bootloader lock (the purple thing at the top saying unlocked) and the secure flag.
With the bootloader unlocked, you can flash on virtually any partition (only signed firmware and other technical stuff that is irrelevant in your situation) but when booted in recovery, you cannot flash to the boot partition. (Can only do that when s-off)
To flash the boot partition when unlocked s-on (secure flag on) you need to extract the boot.IMG from the ROM and flash it while in fastboot mode from the hboot.
To RUU (return to complete stock) you also need to flash upwards or same version firmware officially signed by HTC when s-on. If you are s-off then you can downgrade. Also, bootloader needs to be locked again.
TL/DR: flash the boot image following my post above and that ROM you flashed will work.
Sent from my Rezound
Click to expand...
Click to collapse
Hello, I have been preparing to RUU back to 4.03.605.2 and want to be sure of process. I read REV3NT3CH's post on downgrading, so I downloaded the latest 2 PH89IMGs via his instructions and here's where I stand:
S Off
Hboot 2.28
Radio 2.23.10.0123r/1.23.10.0124r
also running CleanRom 4.5
Can I just place PH89IMG on sdcard to RUU or am I missing a step? Thank you in advance
Just place it in the root of SD card and reboot to your boot loader
Sent from my Rezound
Hey all,
I have this HTC EVO 3D that just, refuses to co-operate with me.
Story goes -
Got it on ICS and everything was working fine on it. I looked for updates available and it found a 28MB update that I installed and once the phone rebooted with the update, the camera fails to start and the touch screen just starts going crazy and opening everything, whereas before it fine.
So, I attempted to try and get it back to Gingerbread.
And googled and googled and googled.
Reason why I have opened a new thread is cause it's sort of everything going weird with it.
Of course, trying RUU files and trying to flash RUU in zip failed so on so forth.
I had unlocked the Bootloader and S-ON is on at this point. Also had CWM recovery installed and was able to boot into that.
With this in place, I read up on the wire trick and thought, yeah it seems a bit hard, I'll take it to a phone repair shop, where they had the phone for 2 weeks and told me that it was S-OFF and back to stock.
Since they had it and I got it back, it's now stuck in a boot loop and I can not get into any recovery etc (With the original SD Card in it). Can get to Bootloader and fastboot though.
Spent the last 3 hours with about 20 tabs in Chrome opened on how to exactly go from here and I am stuck.
Got a Linux Laptop here and tried to ControlBear and it comes up with ADB and Fastboot not found (Directory points to it being in tmp..no idea)
TL;DR
HTC Evo 3D (Australian Variant, was running ICS Telstra OEM)
Unlocked Bootloader
SHOOTER_U PVT SHIP S-ON RL
HBOOT-1.53.0007
eMMC-boot
Radio - 11.25.3504.16 M
Boot Loops, No Recovery, Fastboot commands work on windows.
So just wondering, where do I go from here. I don't know if the device is completely bricked now or if it can be saved.
(I tried a number of zip files on the SD Card (PG86IMG.zip) and nothing due to having S-ON.
Hoping someone can provide a procedure or point me in the right direction.
As reference, I used this thread mostly before it was taken to the Repair Shop and got stuffed.
Any help is appreciated.
Thanks so much.
skylirizm said:
Hey all,
I have this HTC EVO 3D that just, refuses to co-operate with me.
Story goes -
Got it on ICS and everything was working fine on it. I looked for updates available and it found a 28MB update that I installed and once the phone rebooted with the update, the camera fails to start and the touch screen just starts going crazy and opening everything, whereas before it fine.
So, I attempted to try and get it back to Gingerbread.
And googled and googled and googled.
Reason why I have opened a new thread is cause it's sort of everything going weird with it.
Of course, trying RUU files and trying to flash RUU in zip failed so on so forth.
I had unlocked the Bootloader and S-ON is on at this point. Also had CWM recovery installed and was able to boot into that.
With this in place, I read up on the wire trick and thought, yeah it seems a bit hard, I'll take it to a phone repair shop, where they had the phone for 2 weeks and told me that it was S-OFF and back to stock.
Since they had it and I got it back, it's now stuck in a boot loop and I can not get into any recovery etc (With the original SD Card in it). Can get to Bootloader and fastboot though.
Spent the last 3 hours with about 20 tabs in Chrome opened on how to exactly go from here and I am stuck.
Got a Linux Laptop here and tried to ControlBear and it comes up with ADB and Fastboot not found (Directory points to it being in tmp..no idea)
TL;DR
HTC Evo 3D (Australian Variant, was running ICS Telstra OEM)
Unlocked Bootloader
SHOOTER_U PVT SHIP S-ON RL
HBOOT-1.53.0007
eMMC-boot
Radio - 11.25.3504.16 M
Boot Loops, No Recovery, Fastboot commands work on windows.
So just wondering, where do I go from here. I don't know if the device is completely bricked now or if it can be saved.
(I tried a number of zip files on the SD Card (PG86IMG.zip) and nothing due to having S-ON.
Hoping someone can provide a procedure or point me in the right direction.
As reference, I used this thread mostly before it was taken to the Repair Shop and got stuffed.
Any help is appreciated.
Thanks so much.
Click to expand...
Click to collapse
Hello my friend, the reason you can't load the pg86img is because you have unlocked bootloader. The fastboot commands could help us a lot, did you follow the controlbear instructions in the correct order? I think there is a way through windows with exe files I don't remember well because I did S-OFF 3years+ before. If you want we can try together some time. If you want for start we can flash 4ext recovery and a custom rom so your phone can boot.
mhnx said:
Hello my friend, the reason you can't load the pg86img is because you have unlocked bootloader. The fastboot commands could help us a lot, did you follow the controlbear instructions in the correct order? I think there is a way through windows with exe files I don't remember well because I did S-OFF 3years+ before. If you want we can try together some time. If you want for start we can flash 4ext recovery and a custom rom so your phone can boot.
Click to expand...
Click to collapse
Hi there, I didn't know with having the bootloader unlocked that it would cause any issues, but there you go!
Yeah, if there's a guide to flashing the 4EXT Recovery and a custom rom that would be great!
I have a fair idea of how to do it, but don't want to try anything without having someone of greater knowledge point me in the right direction
Thanks!
Just an update, I did come across a thread to flash 4EXT Recovery onto my Evo 3D.
Put Recovery.img into my platform-tools folder, used the fastboot command, it said sending and OK.
Selected recovery and still boot loops. No idea where to go from here now
skylirizm said:
Just an update, I did come across a thread to flash 4EXT Recovery onto my Evo 3D.
Put Recovery.img into my platform-tools folder, used the fastboot command, it said sending and OK.
Selected recovery and still boot loops. No idea where to go from here now
Click to expand...
Click to collapse
Sorry for being late, I had some problems with my internet connection. Can you boot into recovery? Power button + Vol- and choose recovery, if you can boot tell me first which version you have and second what type of rom you want to have.
mhnx said:
Sorry for being late, I had some problems with my internet connection. Can you boot into recovery? Power button + Vol- and choose recovery, if you can boot tell me first which version you have and second what type of rom you want to have.
Click to expand...
Click to collapse
Hey there,
That's OK, I don't mind the wait, it's all good!
I can boot into Fastboot, but when I choose recovery/factory reset etc, it shows the HTC Logo and then goes into a bootloop.
As for the ROM, I want to get the original GB ROM for it because when I updated it to the latest ICS that's when the camera and touch started to get weird, whereas beforehand it was fine.
So thinking, if I go back down to GB Stock, that it should be all fine again, but I am not too sure on that one.
Thanks!
skylirizm said:
Hey there,
That's OK, I don't mind the wait, it's all good!
I can boot into Fastboot, but when I choose recovery/factory reset etc, it shows the HTC Logo and then goes into a bootloop.
As for the ROM, I want to get the original GB ROM for it because when I updated it to the latest ICS that's when the camera and touch started to get weird, whereas beforehand it was fine.
So thinking, if I go back down to GB Stock, that it should be all fine again, but I am not too sure on that one.
Thanks!
Click to expand...
Click to collapse
Well, we have to downgrade the hboot version first. Did you do the wire trick procedure right? You can download a pg86img and flash it first to fix the bootloops. First lock the bootloader. When you finish this report here. I have to sleep it's late here and I work early. I'll send you tomorrow. See you.
mhnx said:
Well, we have to downgrade the hboot version first. Did you do the wire trick procedure right? You can download a pg86img and flash it first to fix the bootloops. First lock the bootloader. When you finish this report here. I have to sleep it's late here and I work early. I'll send you tomorrow. See you.
Click to expand...
Click to collapse
Ok, the technician I took the phone to supposedly did the wire trick for S-OFF, but, it's still S-ON.
I have downloaded a lot of stock PG86IMG files before posting on here and none work, they scan when in bootloader and then nothing after that.
But that would be because I haven't locked the bootloader. So in saying this, I lock the bootloader following steps on many forum posts on here, then flash a .zip file that's correct and then it should all work?
I'll wait for your response, thanks!
skylirizm said:
Ok, the technician I took the phone to supposedly did the wire trick for S-OFF, but, it's still S-ON.
I have downloaded a lot of stock PG86IMG files before posting on here and none work, they scan when in bootloader and then nothing after that.
But that would be because I haven't locked the bootloader. So in saying this, I lock the bootloader following steps on many forum posts on here, then flash a .zip file that's correct and then it should all work?
I'll wait for your response, thanks!
Click to expand...
Click to collapse
I do not think that the wire trick procedure was correct because you are still s on. Lock the bootloader and try to load the zip.
mhnx said:
I do not think that the wire trick procedure was correct because you are still s on. Lock the bootloader and try to load the zip.
Click to expand...
Click to collapse
Hey, so I tried a P86IMG.zip from this thread here - http://forum.xda-developers.com/showthread.php?t=2274635
I couldn't find another one and with that I get an error "Main Version Fail" or "Main Version Check Fail".
I then tried RUU and RUU in zip format.
RUU comes back with wrong bootloader error. (I couldn't find an RUU that matched my radio version so I went with the nearest one)
RUU Zip comes back through fastboot with "remote 43 main version check fail"
Also I tried to do the Wire Trick and got stuck at the "ADB and Fastboot not found" even though the files are there and the phone is connected.
So still a little bit...stuck :\
Also relocked bootloader it just says relocked now.
If you need any other additional info I can send screenshots of what it's at.
Thanks!
skylirizm said:
Hey, so I tried a P86IMG.zip from this thread here - http://forum.xda-developers.com/showthread.php?t=2274635
I couldn't find another one and with that I get an error "Main Version Fail" or "Main Version Check Fail".
I then tried RUU and RUU in zip format.
RUU comes back with wrong bootloader error. (I couldn't find an RUU that matched my radio version so I went with the nearest one)
RUU Zip comes back through fastboot with "remote 43 main version check fail"
Also I tried to do the Wire Trick and got stuck at the "ADB and Fastboot not found" even though the files are there and the phone is connected.
So still a little bit...stuck :\
Also relocked bootloader it just says relocked now.
If you need any other additional info I can send screenshots of what it's at.
Thanks!
Click to expand...
Click to collapse
Did you try flashing the zip after the locking? You are doing the wire trick procedure on live linux cd?
mhnx said:
Did you try flashing the zip after the locking? You are doing the wire trick procedure on live linux cd?
Click to expand...
Click to collapse
Yes, tried flashing the zip after locking. Live CD is being used also. I will try again later. Thanks!
skylirizm said:
Yes, tried flashing the zip after locking. Live CD is being used also. I will try again later. Thanks!
Click to expand...
Click to collapse
If you want we can do the procedure together some time. Keep in mind that you have to unlock again. We can search for the windows version too.
mhnx said:
If you want we can do the procedure together some time. Keep in mind that you have to unlock again. We can search for the windows version too.
Click to expand...
Click to collapse
I have windows version of wire trick procedure. If you need it, I'll gladly share it via PM
donkeykong1 said:
I have windows version of wire trick procedure. If you need it, I'll gladly share it via PM
Click to expand...
Click to collapse
Oh that would be extremely helpful, I can use Linux, but prefer my Windows PC as it has all the files and it's just easier.
Thanks so much!
mhnx said:
If you want we can do the procedure together some time. Keep in mind that you have to unlock again. We can search for the windows version too.
Click to expand...
Click to collapse
donkeykong1 said:
I have windows version of wire trick procedure. If you need it, I'll gladly share it via PM
Click to expand...
Click to collapse
So update -
DK sent me the windows version of ControlBear via PM - thank you.
Have an unlocked bootloader.
I tried ControlBear, and because I can not boot into the OS, I start it at Fastboot USB, it reboots, then says "Connecting to Device", then "Testing ADB connection" then "Press Enter To Exit" and that's it, can't do anything else from there, and it gets stuck in the boot loop that it still has.
Tried again to google for methods for HBOOT 1.53, and am trying some of those methods, but it's not looking good at all.
I haven't even got to the stage where it asks me to do any sort of wire trick.
Also my battery in the EVO 3D has died so am using a battery out of a HTC MyTouch 4G with help from electrical tape :\
So now, any suggestions? I am trying to flash another RUU that's stock for my Radio (Well, it's close enough - RUUs are both 11.25.3504.06, mine is 11.25.3504.16)
EDIT: Tried all RUUs with relocked bootloader and comes back with bootloader error (ERROR 140). So, no idea.
Also it's scanning for PG86DIAG.img files on the SD Card - that's not normal is it.
Do you think we should give up on it, it's probably hard bricked and dead now
I think it's literally hard bricked and no way to bring it back from the dead.
As per my original post, all the details for the phone are there. And it sucks that I can't find a correct RUU for my phone (As it was Telstra AU - latest update of ICS)
AHH I don't know.
skylirizm said:
So update -
DK sent me the windows version of ControlBear via PM - thank you.
Have an unlocked bootloader.
I tried ControlBear, and because I can not boot into the OS, I start it at Fastboot USB, it reboots, then says "Connecting to Device", then "Testing ADB connection" then "Press Enter To Exit" and that's it, can't do anything else from there, and it gets stuck in the boot loop that it still has.
Tried again to google for methods for HBOOT 1.53, and am trying some of those methods, but it's not looking good at all.
I haven't even got to the stage where it asks me to do any sort of wire trick.
Also my battery in the EVO 3D has died so am using a battery out of a HTC MyTouch 4G with help from electrical tape :\
So now, any suggestions? I am trying to flash another RUU that's stock for my Radio (Well, it's close enough - RUUs are both 11.25.3504.06, mine is 11.25.3504.16)
EDIT: Tried all RUUs with relocked bootloader and comes back with bootloader error (ERROR 140). So, no idea.
Also it's scanning for PG86DIAG.img files on the SD Card - that's not normal is it.
Do you think we should give up on it, it's probably hard bricked and dead now
I think it's literally hard bricked and no way to bring it back from the dead.
As per my original post, all the details for the phone are there. And it sucks that I can't find a correct RUU for my phone (As it was Telstra AU - latest update of ICS)
AHH I don't know.
Click to expand...
Click to collapse
First of all you should be unlocked now with 1.53 hboot. Download from here the latest 4ext recovery (4EXT_Recovery_Touch_v1.0.0.6_RC3)
It's in my mega account don't worry about malicious software I downloaded it 5 minutes before doing this post. If you don't have unlocked your bootloader do it with the tokens HTC sent you in your email. Flash this recovery from fastboot (fastboot flash recovery "recoveryname".img). After that remove the battery and re-enter fastboot mode (Vol down+power button) and choose recovery. If you manage to boot into recovery from there tell me to send you a link for a rom to flash. I don't believe its a hard brick.
mhnx said:
First of all you should be unlocked now with 1.53 hboot. Download from here the latest 4ext recovery (4EXT_Recovery_Touch_v1.0.0.6_RC3)
It's in my mega account don't worry about malicious software I downloaded it 5 minutes before doing this post. If you don't have unlocked your bootloader do it with the tokens HTC sent you in your email. Flash this recovery from fastboot (fastboot flash recovery "recoveryname".img). After that remove the battery and re-enter fastboot mode (Vol down+power button) and choose recovery. If you manage to boot into recovery from there tell me to send you a link for a rom to flash. I don't believe its a hard brick.
Click to expand...
Click to collapse
Hey there, thanks for the help again, unfortunately, still didn't work.
I unlocked the bootloader again. Then tried to flash what you said, it said "writing" then "successful". I pulled the battery and tried to boot into recovery and just loops
skylirizm said:
Hey there, thanks for the help again, unfortunately, still didn't work.
I unlocked the bootloader again. Then tried to flash what you said, it said "writing" then "successful". I pulled the battery and tried to boot into recovery and just loops
Click to expand...
Click to collapse
Try doing:
fastboot erase recovery
fastboot flash recovery "recovery".img
fastboot format system
fastboot format boot
And if it still doesn't let me send you a boot.img in some minutes to try flashing it.
EDIT: And something last, you can still do the controlbear trick while not in OS, its easy if you wanna try let me know.
skylirizm said:
Hey all,
I have this HTC EVO 3D that just, refuses to co-operate with me.
Story goes -
Got it on ICS and everything was working fine on it. I looked for updates available and it found a 28MB update that I installed and once the phone rebooted with the update, the camera fails to start and the touch screen just starts going crazy and opening everything, whereas before it fine.
So, I attempted to try and get it back to Gingerbread.
And googled and googled and googled.
Reason why I have opened a new thread is cause it's sort of everything going weird with it.
Of course, trying RUU files and trying to flash RUU in zip failed so on so forth.
I had unlocked the Bootloader and S-ON is on at this point. Also had CWM recovery installed and was able to boot into that.
With this in place, I read up on the wire trick and thought, yeah it seems a bit hard, I'll take it to a phone repair shop, where they had the phone for 2 weeks and told me that it was S-OFF and back to stock.
Since they had it and I got it back, it's now stuck in a boot loop and I can not get into any recovery etc (With the original SD Card in it). Can get to Bootloader and fastboot though.
Spent the last 3 hours with about 20 tabs in Chrome opened on how to exactly go from here and I am stuck.
Got a Linux Laptop here and tried to ControlBear and it comes up with ADB and Fastboot not found (Directory points to it being in tmp..no idea)
TL;DR
HTC Evo 3D (Australian Variant, was running ICS Telstra OEM)
Unlocked Bootloader
SHOOTER_U PVT SHIP S-ON RL
HBOOT-1.53.0007
eMMC-boot
Radio - 11.25.3504.16 M
Boot Loops, No Recovery, Fastboot commands work on windows.
So just wondering, where do I go from here. I don't know if the device is completely bricked now or if it can be saved.
(I tried a number of zip files on the SD Card (PG86IMG.zip) and nothing due to having S-ON.
Hoping someone can provide a procedure or point me in the right direction.
As reference, I used this thread mostly before it was taken to the Repair Shop and got stuffed.
Any help is appreciated.
Thanks so much.
Click to expand...
Click to collapse
i have same problem plz give me GB rom link and flash method
---------- Post added at 07:56 AM ---------- Previous post was at 07:42 AM ----------
mhnx said:
First of all you should be unlocked now with 1.53 hboot. Download from here the latest 4ext recovery (4EXT_Recovery_Touch_v1.0.0.6_RC3)
It's in my mega account don't worry about malicious software I downloaded it 5 minutes before doing this post. If you don't have unlocked your bootloader do it with the tokens HTC sent you in your email. Flash this recovery from fastboot (fastboot flash recovery "recoveryname".img). After that remove the battery and re-enter fastboot mode (Vol down+power button) and choose recovery. If you manage to boot into recovery from there tell me to send you a link for a rom to flash. I don't believe its a hard brick.
Click to expand...
Click to collapse
plz help my htc evo 3d is bootloop no go to any recovery mode i flash all recovery
BOOTLOADER-UNLOCK
HBOOT-1.53.0007
RADIO-11.25.3504.06.M
i flash many ruu.exe but this
RUU_SHOOTER_U_ICS_35_S_hTC_Asia_WWE_3.28.707.1_Radio_11.77.3504.00U_11.25.3
flash seccussfully without any error but no booting only htc logo plz help