*Droid Htc Eris
HBOOT: 1. 49. 0000
RADIO: 2. 42. 01. 04. 27
-After doing a hard reset (volume down +send+End button)] i can NO LONGER boot into the hboot menu (shouldn't have done that) :-(
*Boot status after pressing the power button:
-phone comes to the white start screen with the 3 skateboard droids along the center of the screen, then goes straight into recovery:
----------------------------
ClockworkMod Recovery v 2.5.0.1
*reboot system now
*apply sdcard:update.zip
*wipe data/factort reset
*wipe cache partition
*install zip from sdcard
*nandroid
*partitions menu
*advanced
ClockworkMod Recovery v 2.5.0.1
E: Can't read MISC:
(No space left on device)
E: Can't read MISC:
(No space left on device)
E: Can't read MISC:
(No space left on device)
---------------------------
-Im able to put stuff on my sdcard via the -mount USB storage sub- menu under the *partitions menu. I did a status report using one of the zips i found on a thread (cant remember which one).
----------------------------------------------------------------------------
Eris MTD Partition Status Report Generated
PARTITION DEVICE_NAME SIZE(Bytes) BAD_BLOCKS #_E-BLKS ECC_FAIL ECC_CORR BBT_BLOCKS
misc /dev/mtd/mtd0 655360 5 5 30 0 0
recovery /dev/mtd/mtd1 5242880 0 40 0 0 0
boot /dev/mtd/mtd2 2621440 20 20 0 0 0
system /dev/mtd/mtd3 178257920 1354 1360 0 0 0
cache /dev/mtd/mtd4 136314880 37 1040 74 0 0
userdata /dev/mtd/mtd5 167247872 745 1276 172 0 0
----------------------------------------------------------------------------
-Has anyone figured out how to fix this error?
ClockworkMod Recovery (as the default recovery image) and the Eris are a disaster waiting to happen. Almost every stuck Eris like this happens from Clockwork, while you never read it happening from Amon_RA recovery.
If you can flash something, I guess you may as well flash ErisMTDNuke_v0.9.zip and hope that clears the errors in the partitions.
See this post: http://forum.xda-developers.com/showpost.php?p=23034380&postcount=3
While this gives an overview of how to use the new unlockable 1.51.0000 bootloader to get the 1.49.2000 S-OFF bootloader on, it shows the steps as well to flash ErisMTDNuke. After you flash that, hopefully it will leave the phone in a state where you can get a working HBOOT and - more importantly - Amon_RA recovery.
I just walked somebody through the process in a bit more detailed steps a few days ago (including adding the flash of Flashback21_v2 in order to get the radio flashed back to the current version; flashing the old root PB00IMG.zip flashes an old radio). It starts with this post: http://androidforums.com/htc-droid-eris/556826-stuck-boot-up-screen.html#post4475687
But, in your case, since you cannot start in HBOOT, you'll have to try starting with ErisMTDNuke. Then flash ErisMiscReset_v0.9.zip (and hope that works) and then try flashing the root PB00IMG.zip file (renamed as PB00IMG.zip). From there you should be able to start HBOOT, put the phone in fastboot, flash Amon_RA recovery, and then you should be able to get the phone back in order.
(By the way, you start in HBOOT by holding only VolDn - you don't need to hold send as well.)
hi doogald, Thank you for replying. I will read and try this on the phone as soon as i get home from work.
Okay so i was able to flash both ErisMTDNuke and ErisMiscReset_v0.9.zip and both flashed without error, but for some reason when i went to flash the PB00IMG.zip, it was not showing up in my storage card even though i could see it every time i mounted back to my laptop. I'm not sure why it wouldn't come up in my sd card? Anyway i think i screwed up.... i was being distracted and pulled out the battery, so when i tried to turn the phone back on, it went straight to the 3 droid skateboarders. No more clockword mod recovery. I tried the vol down + Send + end and this brought up fastboot USB in the top left corner of the 3 droid scateborders screen. I figured i'd try to use an RUU to see if i could flash using that, but there was a bootloader driver problem. I searched around and found drivers for it. I then tried the RUU but it gave me the 170 error about the USB not being connected. So i did another battery pull cos i read its not good to leave the phone on in fastboot because it kills the battery. I put the battery back in and put the phone in the charger. I didnt get the orange charge light, so i tried turning it back on, no use... it wouldnt turn on Now im stuck.. have no idea what to do?
PB00IMG.zip does not get flashed from recovery - it is processed by HBOOT. As I said, you get into HBOOT by holding VolDn while starting the phone, not holding VolDn and Send.
Erisuser1 posted an illustrated guide to PB00IMG.zip updating here: http://androidforums.com/eris-all-things-root/75384-visual-example-pb00img-zip-update-method.html
You can try to leave the phone plugged in to a charger overnight (not to a PC but to a wall charger) and see if it will charge. Don't try to turn it on while charging - just let it sit for several hours. There is an external charger that Seidio Online makes and Amazon sells, so you can charge the battery outside the phone.
http://www.amazon.com/Seidio-Multi-Function-Battery-Charger-Incredible/dp/B003N1915S
Ressurection: Phone has come back to life, it has power again!!!
doogald said:
PB00IMG.zip does not get flashed from recovery - it is processed by HBOOT. As I said, you get into HBOOT by holding VolDn while starting the phone, not holding VolDn and Send.
Click to expand...
Click to collapse
I did a battery pull, and pressed the power button for about 5 sec to discharge the motherboard of the phone. I replaced the battery and pushed the power button again. The phone vibrated and went straight to the skateboard droids screen. I was semi relieved in a way
Doogald, i tried the volume down and End button to get into HBOOT, but it doesn't work. It just goes to the blank screen with the 3 droid skateboarders.
I can't really use the link you gave me because i'm not able to get into HBOOT. Is there another way to do this? BTW..Thank you for helping me!
I think that the only thing that you can try is to get the RUU for the new 1.51.0000 unlockable bootloader and try installing that.
You get it from here: http://www.htcdev.com/bootloader
Register for an address at the top, select "Droid Eris" from the dropdown, click "Begin unlock bootloader", answer the questions in the popup, and then you can download an RUU that will hopefully get you the 1.51.0000 unlockable bootloader.
I downloaded the RUU, i also downloaded HTC sync but my device is not being picked up. Is there any way to fix this, i think if i can just get my phone recognized by my computer, i should be able to run the RUU.
Try a different cable. However, it's quite possible that if the phone cannot get into HBOOT, it cannot be accessed by the PC. If that's the case, sorry to say that I think the phone is a brick.
Do you think this is a driver issue? is there some way i can connect to the phone using the fastboot command in sdk ? It does show the "fastboot USB" in the top left corner, though it shows that even when i disconnect the cable from the computer.
Is there anyone out there with this problem? Im not ready to give up.
If anyone is still stuck with an Eris that is bricked, i suggest you look into "JTAG" check out ebay for people that offer the service. They will do it for you for about $30 -$40. It fixes the fastboot and Hboot. You can load whatever firmware you want to after.
MY HTC ERIS LIVES ON !!! WOOOOHOOOOO
Related
Hey guys,
It looks like I've finally screwed up my phone. It was bound to happen.
Here's what happened:
I was running an unchanged, rooted rom. I installed RyanA's lagfix, which worked, but didn't make a huge difference.
So I unapplied it, and then applied the voodoo lagfix. This worked great until I tried to install a backup. I forgot to disable voodoo, and now I'm stuck.
Problems:
The phone boots up, I can use it and everything, but I have 0.00 application space. I cannot install anything!
I cannot enter USB mode in any way. I installed the drivers, uninstalled them, re-installed... nothing. I am running Windows 7, but I tried it on an XP machine, still nothing.
If I go into Clockwork to try to factory reset, or install my backup stock rom, I get this error:
E: Can't mount /dev/block/mmcblk0p2
(File exists)
Error mounting /data/!
Skipping format...
Copying files...
E: Can't mount /dev/block/mmcblk0p2
(File exists)
E: Can't mount DATA:
E: Failure at line 372:
copy_dir PACKAGE:data DATA:
Installation aborted.
Lastly, I can't enter download mode at all. I may have a hardware locked Vibrant, because I've never been able to get into it. This is a problem, because I can't flash Odin to fix this whole mess.
I now come to you people who have been super helpful in the past! What can I do aside from cry?
You are getting that error becuase you still have a ext4 partition in place. If you can still acess your sd card,then download "disable-lagfix" zip,or create a file by that name in the "voodoo" folder (reboot), or flash zip through clockwork. Then run your nandroid backup. I always keep that zip on my sdcard for this very situation.
If you can boot up, and get into the Android OS, you can almost assuredly fix it.
What have you tried to get into Download mode? Try to follow these instructions exactly.
1- Install Samsung Kies. (This will install the drivers needed for your phone onto your computer).
2- Power down your phone.
3- Remove the battery.
4- Plug a usb cable into your phone.
5- Plug the usb cable into your computer.
6- While holding your phone with one hand, press and hold the Volume Up AND Volume Down button AND the power button.
7- While holding down all three buttons, put your battery into the phone.
8- As soon as you put the battery back in you will see a small icon in the center of the screen, as soon as it goes away, (it will be a solid black screen) release ONLY the power button. Continue to hold the Volume keys. Timing is important here, you must release the button as soon as you see a black screen after the initial animation.
This should get you into Download mode where you can flash with Odin and fix it right up.
Hope this helps.
Thanks for the speedy response guys. I'll give it a shot now and see what happens!
y2jon said:
If I go into Clockwork to try to factory reset, or install my backup stock rom, I get this error:
E: Can't mount /dev/block/mmcblk0p2
(File exists)
Error mounting /data/!
Skipping format...
Copying files...
E: Can't mount /dev/block/mmcblk0p2
(File exists)
E: Can't mount DATA:
E: Failure at line 372:
copy_dir PACKAGE:data DATA:
Installation aborted.
Lastly, I can't enter download mode at all. I may have a hardware locked Vibrant, because I've never been able to get into it. This is a problem, because I can't flash Odin to fix this whole mess.
I now come to you people who have been super helpful in the past! What can I do aside from cry?
Click to expand...
Click to collapse
I ended up making this very same mistake a few days ago. This might be silly, but have you tried disabling Voodoo yet? When this happened to me, I was able to put the "disable lagfix" file in the Voodoo folder and it fixed it. It copied the ext4 back to rfs and I was then able to restore a backup and my /data was recognized once again with no errors.
Dragoth12 said:
If you can boot up, and get into the Android OS, you can almost assuredly fix it.
What have you tried to get into Download mode? Try to follow these instructions exactly.
1- Install Samsung Kies. (This will install the drivers needed for your phone onto your computer).
2- Power down your phone.
3- Remove the battery.
4- Plug a usb cable into your phone.
5- Plug the usb cable into your computer.
6- While holding your phone with one hand, press and hold the Volume Up AND Volume Down button AND the power button.
7- While holding down all three buttons, put your battery into the phone.
8- As soon as you put the battery back in you will see a small icon in the center of the screen, as soon as it goes away, (it will be a solid black screen) release ONLY the power button. Continue to hold the Volume keys. Timing is important here, you must release the button as soon as you see a black screen after the initial animation.
This should get you into Download mode where you can flash with Odin and fix it right up.
Hope this helps.
Click to expand...
Click to collapse
You are an absolute genius! I just got in on the first try following those instructions!
It looks like everything is on the way to working again, thanks so much!!
And thanks everyone else for the help!
I didn't personally come up with that procedure, I found it in other threads here on XDA after a couple hours of searching since I soft bricked my phone yesterday. Glad I could relay the info and help you out.
I used Rom Manager to apply an update to my DasBamf 2.0-beta5, and the phone reset but did not into Clockwork. Instead it got stuck in a boot loop.
I thought nothing of it, held down the volume button and went into the bootloader. Turns out I left a radio update on the root of my SD Card, so no biggie, I plugged the SD Card into my pc, removed the radio update file. I put the card back into my phone and now I cannot get into Clockwork!
Every time I get to bootloader, click recovery, then it goes into clockwork for a second, says:
E: Can't Mount /cache/recovery/command
E: Can't Mount /cache/recovery/log
E: Can't Open /cache/recovery/log
E: Can't Mount /cache/recovery/last_log
E: Can't Open /cache/recovery/last_log
What should I do? I do not have any idea what the issue is here!
Uhhhh flash a new rom... It appears clockworkmod is still partially useable
Sent from my ADR6400L using XDA Premium App
I wish it were that simple. Clockwork is unusable. After the error message appears, the phone reboots into a boot loop with the White HTC Logo.
Load the stock rooted ruu through the bootloader than reflash can in the stock ruu than reupdate to gb
Sent from my ADR6400L using XDA App
Can you boot into your ROM?
If so, the just reflash CWR via Rom Manager.
If not, grab a root stock RUU and flash that via HBOOT. Then download Rom Manager from the market, then reflash CWR.
Only bad thing about the second option is that you will loose /data.
I *think* there is a way to flash CWR via adb, but I'd have to look it up.
I feel really stupid because I thought I had a grasp on this whole thing...I got rooted without any trouble!!!
BUt I am not sure what is up at this point. I took the advice of those above, and loaded the stock rooted RUU through HBOOT (http://forum.androidcentral.com/thu...8597-ruu-return-rooted-stock-leaked-ruus.html).
- Put zip on SD-root folder
- Rename to PG05IMG.zip
- Boot into HBOOT
- Press Vol Up To start update
- Reboot phone
- Boot loop (never goes past the white HTC screen before resetting)
But afterwards I still am stuck in a boot loop! When I boot to recovery I get into CWR, and can move through the menus, but the phone reboots after a second or two (not enough to restore a backup).
Am I doing something wrong?
Sounds to me like the RUU didn't take when flashed via HBOOT. Is S-ON?
Try reflashing that RUU again.
If that doesn't work, try downloading and flashing another RUU. If all else fails, get the unrooted stock RUU. You might have to reroot but you will have a function device.
Damn. I really only trust stuff posted by Jcase, but all of his links are broken!!!
http://forum.xda-developers.com/showthread.php?p=13921164
http://forum.xda-developers.com/showthread.php?t=1082114
I have an idea what it is, my phone did this before after I walked in and out of a walk in freezer... Blah blah
Go into hboot and find the selection that says system info.or something along those lines and if it says touch panel - fail or something along those lines then it will.never boot up
Sent from my ADR6400L using XDA Premium App
I think thats ok!
TOUCH PANEL-ATMELC12_20aaT
OS Ver.-1.12.605.6
Dang well we know it's not a hardware failure
I would just try to.boot it.up after flashing a ruu and don't touch it for awhile and see if its just taking forever to boot
Sent from my ADR6400L using XDA Premium App
Well multiupload is back up! I will try some other RUUs
Any tips to charge the battery again though? I am fearful that I may have depleted it too far at this point, and plugging it in sends it into a boot loop!
The best thing is to do a battery pull and plug it in right after you put the battery in
It shouldn't boot up... But who knows I could be wrong
>--The Game--<
I have loaded multiple RUUs in an attempt to fix this...no luck
I followed the Jcase to return to stock for rooted users - I am now stuck with S-ON, but it does not boot still. Just the same old White HTC Screen.
It could be that it wasn't a CWR problem to begin with since you have loaded the stock RUU, replacing CWR with the stock recovery, and it still won't boot.
Try taking the battery out and pressing the power button for about 10 seconds. Then put the battery back in. Do not press the power button. Now plug in the wall (AC) charger. Let the battery fully charge, no bump charging required. then unplug the charger. Now press Vol - and the Power button. The phone should boot into the bootloader (If it doesn't, then its bricked). Select RECOVERY. Now let the stock recovery program run and reboot.
I hope that fixes it, but if it doesn't...
Well, it comes down to a question that you need to ask your self...
Do you continue down the path of trying to fix this device?
Or
Do you take it in to a vzw store (or call warranty dept.) since its still under warranty and get a replacement?
If you want to press on with trying to fix it (keep in mind that all your data is already gone) in the hope that this process will help someone later who might run into the same problem and is out of warranty, I can try to help. But outside of flashing the unroot stock RUU, there isn't a bunch more that I can think of.
Let us know what you want to do.
barcodelinux said:
It could be that it wasn't a CWR problem to begin with since you have loaded the stock RUU, replacing CWR with the stock recovery, and it still won't boot.
Click to expand...
Click to collapse
I agree. I kind of think that Rom Manager corrupted the file that it tried to install.
Try taking the battery out and pressing the power button for about 10 seconds. Then put the battery back in. Do not press the power button. Now plug in the wall (AC) charger. Let the battery fully charge, no bump charging required. then unplug the charger. Now press Vol - and the Power button. The phone should boot into the bootloader (If it doesn't, then its bricked). Select RECOVERY. Now let the stock recovery program run and reboot.
Click to expand...
Click to collapse
I will try this tonight. I think that my battery is dead at this point. I can get it to reset to HBOOT (S-ON). I can click recovery. The stock recovery opens, and then within 5 seconds the phone resets. From this point (until I pull the battery), it will boot loop to factory recovery. Is this due to a dead battery? Every time I plug in my phone to my wall AC Adapter, the phone actually turns on and boot loops. Because of this I have not been able recharge it.
I hope that fixes it, but if it doesn't...
Well, it comes down to a question that you need to ask your self...
Do you continue down the path of trying to fix this device?
Or
Do you take it in to a vzw store (or call warranty dept.) since its still under warranty and get a replacement?
If you want to press on with trying to fix it (keep in mind that all your data is already gone) in the hope that this process will help someone later who might run into the same problem and is out of warranty, I can try to help. But outside of flashing the unroot stock RUU, there isn't a bunch more that I can think of.
Let us know what you want to do.
Click to expand...
Click to collapse
I have a replacement in the mail at this point, but I am willing to experiment in the meantime so that anyone in the future can avoid my problems!
vypurr said:
I agree. I kind of think that Rom Manager corrupted the file that it tried to install.
Click to expand...
Click to collapse
You are not the first one to say that. While using a GUI front end to CWR is handy, it doesn't have a great track record.
I have gotten away from using Rom Manager for anything except flashing CWR.
But then again, I make it a habit to wipe /system, /data, and /cache before flashing a new ROM. You can't do that from Rom Manager.
Anyways, back to the topic...
The battery being in a low charge state wouldn't make the phone reboot (I wouldn't think). In the past when my battery has died, the phone never rebooted...it just turned off. However, I have never had the phone boot when I plugged up my wall charger either. (My old OG Droid used to do that and it pissed me off)
Has anyone else had this happen? If not, that might suggest a hardware malfunction of some sort too.
Was this phone dropped or does it have any kind of water damage?
At this point, I think it is a hardware failure of some sort. And chasing a hardware failure with a software fix is kind of a fruitless endeavor.
I know the phone has been babied its entire life (except for many many roms).
I remember that the phone used to turn on when CWR was first put onto the TB, but it should not do that stock, and it was cleared up with recent CWR updates.
I am just going to cut my losses and get the replacement that Verizon has offered me. Maybe I can have a couple more break and just get the Galaxy S2 when it lands!
Well I am not alone!!!
http://www.droid-life.com/2011/05/2...ght-want-to-consider-reverting-back-to-froyo/
Hello all. I'm a brand-noob (my phrase, thank you) here.
I have received a Verizon HTC Eris phone that boots to the red triangle with exclamation point (three droids on skateboards prior to the triangle screen). I have no information on what was done on this phone prior to my receiving it. I have read here that the three droids means that it has been rooted, and that the red triangle means a stock recovery is on it.
I can only "Up Volume + Power" to get this - "E:Can't open /cache/recovery/command". Other than that, I can't seem to get to anything else on the phone.
Now, upon connecting via usb to my computer (Windows 7), I can get Windows to recognize the "Android Phone", but not specifically an HTC Eris. I do not have HTC Sync installed. I have used ADB to root another phone (MyTouch), but this phone does not show up when I check for devices via "adb devices".
I am hoping someone can offer some simple steps that I can do to work towards fixing the phone. Thanks everyone for your time. !
This may help you:
http://forum.xda-developers.com/showthread.php?t=992916
Good luck.
Thanks for the reply phone_cell. I had already read/seen that post.
I cannot see any boot information at all, it shows the skateboarders, then the red triangle. The phone shows up on my computer, but only as an "android storage device". I'm not sure how I can check anything via my computer. I have installed PDAnet prior, and read that it should have installed the phone drivers. ? I installed HTCSync on a different computer and it doesn't see the phone.
If there is no way to fix this phone, then I understand. I would like to think that there are ways (standard methods ?) to check and/or re-install a phone (any phone) back from something like this. ? ...Thanks again for your time and expertise!
I was happy to try to help you. I recommend you send a PM to bftb0. If your Eris can be brought back to life, bftb0 will know what to do.
Bummer. bftb0 does not receive private messages, or at least not from me. Maybe someone could relay the forum post.
I am still digging and digging to try and figure something out. If I could get my computer to communicate properly with the phone, I'm sure I could re-install/fix the boot problem.
Anyone have ideas on how to install a usb device that's stuck in recovery?
As always, thanks thanks thanks. And thanks.
I made a post asking bftb0 to lend you a hand.
http://forum.xda-developers.com/showpost.php?p=15386610&postcount=33
Are you able to get it into fastboot mode? To do so, the phone needs to be completely off first...pulling the battery if needed. From there, first hold down the green send/call button then press and hold the red power/end button at the same time. Holding both should bring you to the fastboot screen which has three small skateboard andy's at the bottom and the word FASTBOOT highlighted in red. If you get there, post what the top two green lines say. Post #4 in the thread phone_cell gave shows an example of what you'll see. I would also try and follow bftb0's directions in post #5 about using the "Official" RUU utility to install usb drivers but make sure to stop before actually flashing anything to the phone. After that, download the fastboot tool and then with the phone connected through usb, see if the command "fastboot devices" lists your device ID.
Getting that far is promising and you can proceed with bftb0's directions in that thread to flash with HBOOT, load a recovery, hopefully eventually get a custom ROM flashed.
Hey MongooseHelix (great nick). Thanks for your reply.
No, the phone does not boot into fastboot, or anything else. There's plenty of resources here for all the different methods for booting and such. I've read hundreds of threads and pages. I've tried them all (and to success on other phones). It only gives me the recovery-stuck-ness.
The more I think about it, the more I think it has something to do with me not having this certain phone installed on my computer prior to receiving it. ? What would other people do to remedy something like that..? Find a working model to get the drivers working? Hmmm. Thanks and thanks again folks.
If you haven't already, how about installing the android-sdk(try the exe if on windows):
http://developer.android.com/sdk/index.html
Then run the SDK Manager.exe from the SDK directory. I'd download the latest SDK tools, SDK platform-tools, and the USB driver for Windows. Make sure to add the tools and platform-tools directories to your path...instructions at the end of Step 5:
http://developer.android.com/sdk/installing.html#sdkContents
With the phone on and connected through usb, see if running "adb devices" from the command prompt recognizes the Eris.
Yes, I had the android-sdk installed prior to receiving this phone. I did run it and update everything within it (per everything I researched online). But, the phone still doesn't show up via "adb devices". I feel like because the phone is stuck in recovery, it's not letting the computer do anything hardware-wise with it. ? Not sure.
Not sure what else to suggest. Without access to recovery, fastboot, or hboot along with not being able to connect through a comp, it unfortunately sounds like it might be hard-bricked. I'm certainly no expert at reviving an Eris so someone may know a way to to fix things...maybe bftb0 will come work his magic. Good luck and if I find or think of anything else I'll let you know.
The red triangle screen is indeed a splash screen for the stock recovery.
The next question is whether you are able to proceed beyond the "splash screen" and attempt to perform a "factory reset" procedure using the stock recovery menus.
There are two ways you get past the stock recovery splash screen, and it depends on which version of the stock recovery is installed on your phone have.
(1) press & hold Vol-Up+End simultaneously (with the "red triangle" splash screen showing)
or
(2) press the Home(soft-key)+End simultaneously (with the "red triangle" splash screen showing)
Do either of those cause the <2e> recovery menu to appear on the screen? If so, perform a "factory reset" using that menu, and THEN see if you can get alternate startup modes to occur (after powering off the phone before each trial):
End (only) => Does anything boot now?
VolDown+End => HBOOT
Send+End => FASTBOOT
VolUp+End => Recovery boot (red triangle screen again) **only works if HBOOT > 1.49.xxxx
Please do not say "I tried everything" in your reply. It is extremely non-specific, and conveys no information about what you actually attempted.
bftb0
Many thanks for the reply. !
With the recovery splash screen showing, upon holding "Volume Up + End (power)" I get = E:Can't open /cache/recovery/command Now, I am able to clear that message by pressing "Volume Up + End" again, however it just goes back to the recovery splash screen.
I held down Home (on the glass) + End (power) and nothing happened.
?? Any suggestions ?
Also... my reference to "tried them all" in my earlier post meant that I have tried just about every combination of simultaneous key pressing upon powering up (booting from no power) the phone. I am also familiar with the recovery menus on other phones - I have not seen it show up on this one (per my most recent post as well).
cjslugbug said:
I get = E:Can't open /cache/recovery/command
Click to expand...
Click to collapse
That message is quite normal. However, what usually happens is that the (stock) recovery <2e> menus appear immediately after that message.
I guess this suggests that there is something wrong with the phone (hardware) or the recovery.
I'll give it some thought (check this thread every so often), but I don't see an immediate way out of your situation.
bftb0
Well, I certainly appreciate the replies. Thanks!
Does
VolDown+Send+End
do anything interesting - either from a phone off condition, or when the "can't open /cache/recovery/command" message is on the screen?
Was there a (properly formatted) SD card in the phone when you performed all the prior button-pressing experiments?
Booted with "Volume Down + Send + End" = same, straight to recovery splash screen.
I then "Volume Up + End" to get "e:can't open /cache...." and tried "Volume Down + Send + End" = no changes.
I have an sd card in it that I used to root a MyTouchSlide recently. It has ClockworkMod recovery on it (update.zip). I have done every procedure I've mentioned in this thread with and without the sd card in the phone.
I just reread the whole thread.
I understand that you tried all the standard button-press-startup methods, and the only thing you can get to work (partially) is the first part of the standard recovery boot. What you didn't say explicitly is, what exactly happens when the standard button-press operations fail:
- nothing at all (screen stays black, not a single LED blips, etc)? or,
- every start sequence results in the recovery splash screen? or,
- the three skating droids appear but the screen freezes that way? or,
- other?
Here is what you are up against:
The standard recovery does not start up an "adbd" daemon, so worrying about drivers is not likely to get you anywhere: under normal circumstances, "adb" simply doesn't work with a standard recovery.
There are two exceptions to this:
(1) The (leaked) HTC "Root ROM" does start an adbd daemon (but "adb shell" won't work)
(2) The Leak-V2 recovery had a race condition that allowed less than 20% of the folks who tried it to get an adbd daemon to persist. (Search for "tereg" root). It's a huge long shot.
Whether either of these apply to you is indeterminate, as we know neither the bootloader version that is on your phone, nor the version ofthe (damaged?) recovery on the phone.
One more question, and then some straws to grasp at:
- when you plug the phone into the charger, do you see the amber/green LED light up?
- repeat every one of the "standard-button-press" sequences, but make sure that before each start sequence, you pull the battery, press all buttons, wait 10 secs, and then reinsert the battery. Long shot, but what have you got to lose?
bftb0
- what exactly happens when the standard button-press operations fail:
The three skating droids appear (for a few seconds, as per a normal-type boot is beginning) but then the screen freezes to the recovery splash screen.
- when you plug the phone into the charger, do you see the amber/green LED light up?
Yes, I see the amber/green light. The light seems to operate as if it is charging normally.
I will try your 10 + second-battery-pull-button-combinations method here in a while.
Really appreciate the thoughts/help on the matter. !!!
Hey guys,
So I properly powered down my phone and went to go into the bootloader by holding vol down + power button. As soon as it opened up the bootloader the phone turned off. I went to turn it on and it flashes the white sprint screen for less than 1 sec and turns off. When I plug it into a charger the light turns on for a few secs then goes away.
I have s-off + cwm.
I have read that if your battery dies in the bootloader after installing cwm your battery won't charge and the phone won't boot. I am not sure if this is the case but was hoping to get some input.
I am not sure what percentage my battery was at when this happened.
Thanks!
Go to bootloader (cwm) and reinstall your back up rom that outta do it. And after download the rom you currently have but replace your old one and flash it over usin cwm
Supa Dupa Troopah
My phone only stays on for 1 second tops. I cannot go to my bootloader. My computer sees the phone even when it won't turn on witch is weird. I also cannot communicate with the phone with adb / fastboot etc. The only thing I have not tried is hacking a usb cable to communicate. Any advice would be great. I will try a battery tomorrow.
ADB
Wow hey ok so I can see the phone in ADB after all... List of devices attached
HT167HX05101 recovery
Is there a way to flash the old recovery?
Or can someone point me to the RUU.exe? Not the ZIP
Thanks!
EDIT:
Well never mind... I had adb and booted into bootloader and flashed team win recovery from fastboot and it failed - sending 'recovery' (5016 KB)... OKAY
writing 'recovery'... FAILED (status read failed (Cannot send after transport endpoint shutdown))
Now the light stays on when I plug in but no longer flashes when I power button and no more adb. I'm screwed
Idk what your problem is since i do not have your phone in front of me, either you deleted an import file and are now screwed no offense and cant boot your phone my suggestion is to either call or take it to the store by gettin a new one. I would tell them your phone got hot all the sudden and just crashed that way its under warentee
Supa Dupa Troopah
can you use fastboot? Also, leave the phone alone and charge it, while off, for a bit. If you come back to a full charge phone and hold vol down and then power, it should boot into fastboot, try running a fastboot command from the PC. Also, you could download twrp 1.0.2 zip and put it on your SD card as PG86IMG.zip, same vol down/power and it *might* install the recovery from hboot. Don't give up yet. In theory if your charging light turns on, you're not bricked.
hopefully this works for me !!
Thanks
il Duce said:
can you use fastboot? Also, leave the phone alone and charge it, while off, for a bit. If you come back to a full charge phone and hold vol down and then power, it should boot into fastboot, try running a fastboot command from the PC. Also, you could download twrp 1.0.2 zip and put it on your SD card as PG86IMG.zip, same vol down/power and it *might* install the recovery from hboot. Don't give up yet. In theory if your charging light turns on, you're not bricked.
Click to expand...
Click to collapse
Thanks for the help.
I last time I had adb I got into the bootloader by using an adb command once in there I flashed teamwin rec. It failed during install and ever since I am locked out. I can't get any commands. I wonder if it damaged my boot loader. Ill keep trying otherwise I should be able to get it swapped since it does not boot at all
SpyFi said:
Thanks for the help.
I last time I had adb I got into the bootloader by using an adb command once in there I flashed teamwin rec. It failed during install and ever since I am locked out. I can't get any commands. I wonder if it damaged my boot loader. Ill keep trying otherwise I should be able to get it swapped since it does not boot at all
Click to expand...
Click to collapse
yeah if you can't get into the bootloader/adb/recovery/rom then sprint can't either
Sorry to be a bother.. but can someone check out my problem? I really need help. I know, i am such a troll coming to another post to look for help.
-Mike
Check out this threath i hope it helps..
http://androidforums.com/evo-3d-all-things-root/385959-error-16-sprint.html
Supa Dupa Troopah
Long story short, I messed up my phone while changing the partitions to EXT4.
EDIT: accidently clicked enter, let me finish the rest before posting!
My phone is more or less a brick now. When I boot up, it doesn't take me to the moto logo, instead I get a blank screen that looks something like this
Unlocked
PwrReason: SW_AP_RESET
OS will boot up in 5 seconds
Press a key to stop countdown
Available modes are:
1 RSD
2 Fastboot
3 NvFlash
yadada all you would find while normally booting while holding vol down.
-----------------------------------------------------------------------------
Volume up to select, volume down for next choice
Current choice mode is: (the mode I pick)
If I wait it out, it boots
Powering on BP
Cold-booting Linux
Reading ODM Fuse: 1
Then boots up normally - EXCEPT. my touch orientation is all off. It is lower then where I tap, For example I have to tap the menu button area to access the space bar while typing, and since the orientation is off, I cannot select the menu buttons.
I cannot flash a backup or a new rom because I cannot access my recovery, when I vol up on the android reocvery option it just scrolls down and resets the whole menu..
Help would be greatly appreciated, I am on a Bell Atrix, rooted/unlocked.
Another (possibly stupid) question, will factory resetting through setting->privacy brick my phone? I vaguely remember reading something stating that but I am not 100% sure if I read it wrong or something of the sort.
Update:
I have successfully flashed a sbf file but touch screen orientation is still off.. Any solutions?
Killer0Kevin said:
Update:
I have successfully flashed a sbf file but touch screen orientation is still off.. Any solutions?
Click to expand...
Click to collapse
This will fix your problem:
http://forum.xda-developers.com/showthread.php?t=1131649
+1 Beeboobop
I had the same problem yesterday and solved it that way ! http://forum.xda-developers.com/showthread.php?t=1427038
http://db.tt/mRStSurc { this is the pdsfix.img }
place it in the root of your sdcard
turn off phone turn it on
then choose early usb enumeration
now here is the hard part
open terminal emulator on your phone
if its not installed use this---+
http://db.tt/OKuCxXLt
on your pc go to android market
and get the free android terminal emulator download it to pc rename it
to app place in app folder of apk tool and follow the directions in the. exe
once it pushes terminal emulator to
your phone it will install it too
so just go into it and type /copy and paste this--//
su
dd if=/sdcard/pdsfix.img of=/dev/block/mmcblk0p3
if ya see an output like
49091-in
44027-out
2410436 transfered
then exit and reboot
choose early usb enumeration
boot up and the screen will be good as new
then just flash a boot.img in recovery
i have them too mske sure you use ext4
if your on ext4(like a cm7 or any of them
or use ext3 stock boot.img
Thanks guys, got it working