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
*UNLOCKED*
SHOOTER_U PVT SHIP S-ON RL
HBOOT-1.53.0007
eMMC-boot
Originally Vodafone branded, in the UK
Hello all, Ive lost several days to this now and have finally signed up to ask you all for help on "unbricking" my Evo3d.
Ive done so much i cant quite remember a full list, but alas my problem is essentialy i have deleted the OS on the phone and now every time i try to flash a .zip to the phone (i am using TWRP which seems to be working fine) it says FAILED and gives me an error whilst trying to find /cache.
So it appears my /cache folder has dissapeared aswell? The cure for this (from what i have read online) is to boot into your rom and then restart to bootloader, however there is no rom to boot into on the phone.
ALL I WANT IS STOCK.
Just to be able to use the phone again, before it was on 4.0.2 i think and even though i have S-ON i still tried to load a custom kernal and rom, this then obviousely put me into a bootloop which was ok, except i have no idea how to go back to stock.
I have tried several RUU files (at 400mb a pop) ALL of which fail and give me the error 155 unknown error during the installing on my computer.
I believe the image that the RUU.exe says my phone is was 3.*** (i cant remember exactly but if anyone needs to know i can boot it up again)
I have tried the RUU to return it to 1.21 or something similar but that also failed.
Seemingly i cant do anything with the phone and hours apon hours of googling is getting me no where.
Please help somebody it would be greatly appreciated.
EDIT- I can now no longer boot into recovery for an unknown reason, i tried another RUU it failed in exactly the same fashion, now i boot the phone and it loads a small picture of a phone with a green circle icon next to it, this then turns into a red triangle with a "!" inside of it, then i have to remove the battery.
Crap.
I think I have found why the RUU were not working, its because my bootloader was unlocked.
I have relocked my bootloader, ran the RUU and it has errored again except this time it says Customer ID number.
I presume this means the CID number on my phone is incorrect? Which would sort of make sense because i think i may have changed it at the very beginning whilst i was following a guide.
How on earth do i find out what to change it back to? I have no idea what the original was
EDIT-
************FIXED**************
Use the fastboot commands to change your CID to what is required (HTC or Vodafone) This must be done with unlocked bootloader.
LOCK YOUR BOOTLOADER
Run the RUU file that you wish to apply and voila.
Thanks xda!
Hello everyone. This is my first post with my first problem from my first android phone. Please exercise some patience with me. When kitkat was pushed to the HTC One (T-Mobile) the install failed miserably. When I thought it was done it booted into recovery and just stayed there. I did a hard reboot and the splash screen was all crazy and the HTC boot screen was off colored and it was stuck at the boot screen. Obviously something was corrupted. I ran RUU for 4.3 to get back and flashed twrp and restored from my back up. All is well. I downloaded the OTA (I forget where but I believe somewhere on here) in an attempt to flash it from the stock recovery. Those were the instructions on that post. I ran RUU for 4.3 again to be completely fresh. I get to stock recovery and when I select to "apply from phone storage" I get an "invalid CID" error and the phone reboots. I ran "fastboot getvar all" and my cidnum= T-MOB010. What is the deal? That cid is correct, isn't it? I am also S-On with a "relocked" bootloader. I had to relock in order to run RUU because I was getting error 155. What am I missing? Why is it doing this?
Okay. I really need help guys. My phone is completely wiped and I have NO OS!! I side loaded Android Revolution kitkat and I'm getting errors with that. I can't unzip it!! I'm screwed guys. Please. Any help at this moment!! I'm desperate.
I was able to get out of this hell hole. I was able to run "adb push" and move my nandroid backup from my pc to the phone and restore.
What do I have to do to update to kitkat??? Why did check cid fail? I never changed that. What else could change it?? I had a stock recovery installed but the OTA failed still. Do I have to have the "right" stock recovery? I'm unlocked, rooted and S-off. Do I need to fix something else? Do I need to "relock" first? Is updating to kitkat even possible?? (sarcasim) The information seems to be scattered all over the place. I can not be the only one unlocked, rooted w/ S-off and trying to update my OS.
Hi everyone, I am having a problem with HTC Desire 601, specific details (from bootloader) as follows:
Code:
ZARA_UL PVT SHIP S-ON RL
HBOOT-2.22.0000
RADIO-1.27.40e.00.11
OpenDSP-v18.2.9268.0925
OS-2.14.401.6
eMMC-boot 1024
Mar 27 2014,22:38:07.0
So, I needed to root this phone (its a company phone, we needed to root it for work purposes, long story). Now, I don't really know much about rooting phones specifically, but I am a programmer and I work in software development, so I have good knowledge of computers in general and I'm usually very good at following instructions. So I followed instructions from one guide (cant post link, but it was one of the more prominent search results for 601 specifically, both CL and UL. What happened was that after installing a SuperSU update in the a (PhilZ) recovery, the phone still didn't register as rooted for neither SuperSU (which I had to install manually) nor a RootChecker app. So I thought I'll go back to start and I did a factory reset in the bootloader. After that, the phone is basically soft bricked. It can load bootloader, it can load recovery from bootloader, but it doesn't load system at all, it just stops on HTC screen and does nothing until I turn it off (and then tries to boot again, if I don't start bootloader or remove battery).
I think that a) recovery is somehow corrupted (PhilZ says that it: E:Can't mount /cache/recovery/log .../last_log .../last_install) and b) the system is therefore gone, since I tried to factory reset it, but that is just my layman evaluation, if you need more info about behavior, I can obviously provide it.
I have searched the internet for the past ~6 hours and found mutlitudes of solutions, neither of which unfortunately helped.
I tried using RUU (RUU_ZARA_UL_JB422_SENSE50_TELUS_WWE_1.10.661.8_Radio_1.21.40e.00.27_10.z08.40.4411L_release_336830_signed_2.exe) , which seems to be the correct one for me, but the install just halts on sending data for hour+ and I have to stop it myself).
I tried installing a couple of custom/stock roms from recovery, but it doesn't load them and just says either again that it failed to mount last_install or that there was an error "failed to stat "/system/build.prop": No such file or directory. Also tried a different recovery (TWRP), still nothing.
I tried flashing some system images through fastboot but I guess the S-ON version of bootloader doesn't allow that? (says FAILED (remote: not allowed) on erasing 'system')
It is quite possible that for any of these, I've used a wrong file or something, I tried to check everything and choose the closest file to what is my device, but it wasn't always possible, so I sometimes used a file that seemed applicable to my case. If anyone has an image they think I should use, please let me know. If anyone knows what is the problem exactly, please let me know also. Any help is appreciated, I spent my whole work day trying to fix it but to no avail.
Was your phone previously updated to KitKat? If so, the recovery version you've used isn't directly compatible, try [ http://forum.xda-developers.com/desire-601/orig-development/recovery-twrp-2-7-1-0-touch-recovery-t2804520 The "can't mount" messages point me in that direction.
Good luck.
gorocz said:
Hi everyone, I am having a problem with HTC Desire 601, specific details (from bootloader) as follows:
Code:
ZARA_UL PVT SHIP S-ON RL
HBOOT-2.22.0000
RADIO-1.27.40e.00.11
OpenDSP-v18.2.9268.0925
OS-2.14.401.6
eMMC-boot 1024
Mar 27 2014,22:38:07.0
So, I needed to root this phone (its a company phone, we needed to root it for work purposes, long story). Now, I don't really know much about rooting phones specifically, but I am a programmer and I work in software development, so I have good knowledge of computers in general and I'm usually very good at following instructions. So I followed instructions from one guide (cant post link, but it was one of the more prominent search results for 601 specifically, both CL and UL. What happened was that after installing a SuperSU update in the a (PhilZ) recovery, the phone still didn't register as rooted for neither SuperSU (which I had to install manually) nor a RootChecker app. So I thought I'll go back to start and I did a factory reset in the bootloader. After that, the phone is basically soft bricked. It can load bootloader, it can load recovery from bootloader, but it doesn't load system at all, it just stops on HTC screen and does nothing until I turn it off (and then tries to boot again, if I don't start bootloader or remove battery).
I think that a) recovery is somehow corrupted (PhilZ says that it: E:Can't mount /cache/recovery/log .../last_log .../last_install) and b) the system is therefore gone, since I tried to factory reset it, but that is just my layman evaluation, if you need more info about behavior, I can obviously provide it.
I have searched the internet for the past ~6 hours and found mutlitudes of solutions, neither of which unfortunately helped.
I tried using RUU (RUU_ZARA_UL_JB422_SENSE50_TELUS_WWE_1.10.661.8_Radio_1.21.40e.00.27_10.z08.40.4411L_release_336830_signed_2.exe) , which seems to be the correct one for me, but the install just halts on sending data for hour+ and I have to stop it myself).
I tried installing a couple of custom/stock roms from recovery, but it doesn't load them and just says either again that it failed to mount last_install or that there was an error "failed to stat "/system/build.prop": No such file or directory. Also tried a different recovery (TWRP), still nothing.
I tried flashing some system images through fastboot but I guess the S-ON version of bootloader doesn't allow that? (says FAILED (remote: not allowed) on erasing 'system')
It is quite possible that for any of these, I've used a wrong file or something, I tried to check everything and choose the closest file to what is my device, but it wasn't always possible, so I sometimes used a file that seemed applicable to my case. If anyone has an image they think I should use, please let me know. If anyone knows what is the problem exactly, please let me know also. Any help is appreciated, I spent my whole work day trying to fix it but to no avail.
Click to expand...
Click to collapse
Same thing happened to me..
well.. i swapped my recovery to team win, and Still sits at the HTC screen..
any solutions.?
Okay, So here goes. I updated my phone with an OTA and the system file kept crashing making the phone unusable. It was still on stock at that point in time. I had trouble finding any help as the online help did not solve the problem.
So I went and decided to install a new OS. I unlocked the phone, rooted it, installed TWRP and MaximusHD 44.00. Now with the call issue, my phone became useless. My phone also was not receiving any OTA from the Devs of that OS.
This is all a big headache so I just want to go back to stock. I have tried using some TMO US RUU's, both zips and .exe to no avail. I keep getting not allowed: remote errors or signature errors.
Also, because of using the executives, my TWRP was removed. So now, the phone has nothing on it except the bootloader (whatever the operation is that I can get to fastboot.)
The diagnostics on top say ***tampered*** ***relocked*** ***security warning!***
I can provide radio numbers as well, but really I just need some one to tell me exactly which RUU I need and how to install it and get my phone back to how it was before this big headache. Any help is really appreciated. I need this phone for work and right now, it is a glorified paper weight. Getting desperate.
knightsmarian said:
Okay, So here goes. I updated my phone with an OTA and the system file kept crashing making the phone unusable. It was still on stock at that point in time. I had trouble finding any help as the online help did not solve the problem.
So I went and decided to install a new OS. I unlocked the phone, rooted it, installed TWRP and MaximusHD 44.00. Now with the call issue, my phone became useless. My phone also was not receiving any OTA from the Devs of that OS.
This is all a big headache so I just want to go back to stock. I have tried using some TMO US RUU's, both zips and .exe to no avail. I keep getting not allowed: remote errors or signature errors.
Also, because of using the executives, my TWRP was removed. So now, the phone has nothing on it except the bootloader (whatever the operation is that I can get to fastboot.)
The diagnostics on top say ***tampered*** ***relocked*** ***security warning!***
I can provide radio numbers as well, but really I just need some one to tell me exactly which RUU I need and how to install it and get my phone back to how it was before this big headache. Any help is really appreciated. I need this phone for work and right now, it is a glorified paper weight. Getting desperate.
Click to expand...
Click to collapse
Post a fastboot getvar all except for imei and serialno. We can not recommend anything unless we know what your current set up.