Related
Hello All,
I believe my phone is either semi-bricked or completely bricked? How do I know if it is, it feels like it.
I was in the process of wiping my system to load a custom ROM when I accidentally pressed the trackball and selected 'Reboot Recovery' in Recovery mode, I was doing the following:
1. Wipe Data/Factory Rest
2. Format Cache
3. Format Boot
4. Format System
5. Format Cache
6. Format Data
7. Format Recovery
8. Wipe Dalvik
9. Reboot Recovery [WHOOPS!!!!!!]
Now my system is stuck when it boots up and stays on the HTC screen. Attempting to go to Recovery by holding down the DOWN VOLUME provides me the menu:
- Vol Up - FastBoot Mode
- Back - Simlock
- Home - Recovery
With the following information displayed:
HERC XC SHIP S-ON
HBOOT-1.47.0000 (HERO200000)
MICROP-0110
TOUCHE PANEL-SYN0104
RADIO-2.42.02.10.29
Mar 1 2010, 16:02:39
HBOOT
Selecting Recovery sends me to the HTC screen with the FastBoot USB text displayed and it just sits there. I am not able to recognize the device via the ADB console nor HTC Sync.
Any ideas how to get thru this? The recovery.img is on the SDCard and all, I just can't get the phone access and load it into the system memory?
Thanks in advance,
GP
Did you notice that you're S-On? This means you're not rooted.
Then I must have accidentally gotten by all the requirements for SuperUser, etc to install FreshRom, AOSP Roms, etc previously. Odd...but all is fine now.
I was able to restore the system to a 2.1 RUU by grabbing it from HTC's webiste and continued from there. Thanks though.
plainjane said:
Did you notice that you're S-On? This means you're not rooted.
Click to expand...
Click to collapse
It could've been that you were rooted before, but maybe the lack of a recovery somehow translates into s-on? I don't know. Glad you got it fixed, though.
hi friends,
My Device: Desire S
My ROM: [ROM][Jun 27][SAGA] Virtuous Unity 1.27.0 Sense 3.0 based on Pyramid
My Radio ROM: 38.03.02.11_M
SPL/hboot version: 0.98.2000.
security: off via XTC Clip
build-mode: eng. ENGHboot is installed
Recovery: 4EXTRecovery v2.0.3 RC1 | STAY @EXT4 |
eMMC: eMMC-boot
every time i boot into recovery i get the following lines:
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
whats working:
fastboot and fastboot - USB: is OK
Hboot and HBOOT USB: is ok
i can connect my desire S with ADB: OK
i can flash any recovery with success! OK!!!!
MY PROBLEM:
> Device is not boot anymore just STOCK on Bootlogo
> I cant wipe, I cant istall an other ROM -> Error (Status1) - via recovery
> RUU not working it stocks on rebooting bootloader ......
> Rom.zip from RUU --> on SDCard as PG88IMG.zip -> stock on updating Bootloader
> install rom via fastboot -> not working (fastboot flash zip Rom.zip) - nothing happens
> install backuped ROM via recovery -> not working
> factory reset in HBOOT mode: just freezes my device --> nothing happens
> no differenc: with SC-Card and SIM inserted or NOT in device
fastboot erase cache --> just hangs all time
fastboot oem rebootRUU --> nothing happens
fastboot flash zip Rom.zip
> FastbootCommander: i can connect my desie S -> cant flash rom, radio, hboot,
pls help me this is my secound desire S i bricked in 2 weeks.
this problem came to days ago, without to do anything on my device!!!
the phone rebooted and just cant boot anymore!
r_benamin said:
hi friends,
My Device: Desire S
My ROM: [ROM][Jun 27][SAGA] Virtuous Unity 1.27.0 Sense 3.0 based on Pyramid
My Radio ROM: 38.03.02.11_M
SPL/hboot version: 0.98.2000.
security: off via XTC Clip
build-mode: eng. ENGHboot is installed
Recovery: 4EXTRecovery v2.0.3 RC1 | STAY @EXT4 |
every time i boot into recovery i get the following lines:
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
whats working:
fastboot and fastboot - USB: is OK
Hboot and HBOOT USB: is ok
i can connect my desire S with ADB: OK
MY PROBLEM:
> Device is not boot anymore just STOCK on Bootlogo
> I cant wipe, I cant istall an other ROM -> Error (Status1) - via recovery
> RUU not working it stocks on rebooting bootloader ......
> Rom.zip from RUU --> on SDCard as PG88IMG.zip -> stock on updating Bootloader
> install rom via fastboot -> not working (fastboot flash zip Rom.zip) - nothing happens
> install backuped ROM via recovery -> not working
pls help me this is my secound desire S i bricked in 2 weeks.
this problem came to days ago, without to do anything on my device!!!
the phone rebooted and just cant boot anymore!
Click to expand...
Click to collapse
Hi pull out the battery press power and volume down buttons together when u put the battery back in so you have hboot now try factory reset. Then try to flash again.
Sent from my HTC Pyramid using XDA Premium App
mastersjef said:
Hi pull out the battery press power and volume down buttons together when u put the battery back in so you have hboot now try factory reset. Then try to flash again.
Sent from my HTC Pyramid using XDA Premium App
Click to expand...
Click to collapse
just done that, im in HBOOT
> pressed FACTORY Reset: ---> nothings happens (i tried that yesterday after 10 min. no RESULT)
phone is just like freezed -> VOL UP , DOWN is not working, i have to pull out battery again!
r_benamin said:
just done that, im in HBOOT
> pressed FACTORY Reset: ---> nothings happens (i tried that yesterday after 10 min. no RESULT)
phone is just like freezed -> VOL UP , DOWN is not working, i have to pull out battery again!
Click to expand...
Click to collapse
Try it again without your sdcard maybe that helps.
mastersjef said:
Try it again without your sdcard maybe that helps.
Click to expand...
Click to collapse
no SD-Card, no SIM is in my device!
There has been a similiar/identical problem with the Desire Z/HD devices, its a hardware issue, faulty emmc chip.
there's a thread about it here http://forum.xda-developers.com/showthread.php?t=1039504
You could pop into the #G2ROOT irc channel on freenode for potential help, but if its the same error we had, you'll have to get a warranty replacement.
-Nipqer
Same thing happened to me and other guy (check ds general). He had to replace eMMC chip, I sent mine to HTC and they gave me new device. Good luck with this, with every topic it appears to be more general issue.
Sent from my HTC Desire S using Tapatalk
@ all thx for advicing me
i gonna try to get it repleced by HTC / T-Mobile
thx
PS..: why to f*ck this happens to me, thy it happens when you need you smartphone most - pissing me off --> maybe i gonna buy i iphone 5 when it comes out!
r_benamin said:
no SD-Card, no SIM is in my device!
Click to expand...
Click to collapse
recently many friends came up with the same confusiom like yours。
this seems to be a bug with a small chip，named eMMC（GOOGLE it，pls）
this happens mostly to the owners of DS，that pull out the battery when the phone is being used. In this way the fragile chip for story is burned.
this is my own opinion，maybe right or maybe not.
oh,right.changing a new eMMC chip，cost300 rmb.as $40 more or less~\
wish you&your device a good luck
what's kind of interesting:
i had the same problem, but somehow i have not knowingly managed to get it to work again. back then i had those log-errors when making a backup via clockwork. now when i do that i don't have the errors anymore. basically i didn't do anything else but formatting the cache-partition multiple times via clockwork when the phone didn't want to boot...
szallah said:
what's kind of interesting:
i had the same problem, but somehow i have not knowingly managed to get it to work again. back then i had those log-errors when making a backup via clockwork. now when i do that i don't have the errors anymore. basically i didn't do anything else but formatting the cache-partition multiple times via clockwork when the phone didn't want to boot...
Click to expand...
Click to collapse
You can get the same error messages if your partitioning table gets corrupted, which can be fixed by wiping and flashing a few times.
But if you have the eMMC error, writing fails, so the phone is completely bricked and cannot be fixed.
You can double check if you have the broken chip when you get the error messages by running some adb commands, can't remember them off the top of my head, but if you follow the link in my previous reply, there's plenty of instructions there.
Also, r_benamin, did you get the name of your eMMC chip? I'd like to check if my gf has the potentially faulty one.
-Nipqer
Ive got the "faulty" samsung one...so far so good - i hope it will be okay forever
Anyway, the eMMC can be replaced, so you can repair your first bricked device
Sent from my HTC Desire S using XDA App
Nipqer said:
You can get the same error messages if your partitioning table gets corrupted, which can be fixed by wiping and flashing a few times.
But if you have the eMMC error, writing fails, so the phone is completely bricked and cannot be fixed.
You can double check if you have the broken chip when you get the error messages by running some adb commands, can't remember them off the top of my head, but if you follow the link in my previous reply, there's plenty of instructions there.
Also, r_benamin, did you get the name of your eMMC chip? I'd like to check if my gf has the potentially faulty one.
-Nipqer
Click to expand...
Click to collapse
i send bouth desire S to HTC. and i am using now my old desire HD.
so i have to wait for at least 4 weeks
r_benamin said:
hi friends,
this problem came to days ago, without to do anything on my device!!!
the phone rebooted and just cant boot anymore!
Click to expand...
Click to collapse
my man, u got shot! see this:
[solved]BRICKed: inside eMMC's dead, with E:Can't open /cache/recovery/log
http://forum.xda-developers.com/showthread.php?t=1150917
my phone with the same mistake installs the new rom installs su but it cannot open
after installing su on recovery i can format system wipe everything and install roms but it cannot opens is there a different or strange thin with my desire s
I have the exact problem with a Desire S
The problem is that I S-OFF with Revolutionary, and so my warranty is void.
Any idea in how could I put back the original boot so I can send it HTC for repair?
I encountered this problem in the morning while flashing my GF's Desire S.
Thank god i managed to format it through recovery and after flashing LBC Rom everything was fine again. Got me scared there for a minute.
I didn't manage to do nothing with it.... just the recovery works and cant do nothing from it
Its nice that I have phone insurance from my provider, so I will prob get it repaired through insurance.
ok i just managed to resolve this issue with ordinary Desire.
I rerooted it with custom unrevoked by using custom recovery.
I putted RA 2.0.0 and everything worked smoothly.
(i thought it is wasted)
Any updates on this?
Isn'n possible to mount some fake cache and do what you need to?
What is your logcat saying while in boot loop?
Sent from my HTC Desire S using XDA App
At my sister's today, and she asked me to root her EVO as mine is. In trying to boot into recovery, when I attempt to do so, I get to the white screen, select recovery, but then the red triangle with red exclamation point within it shows on the screen. The only way out of this is to do a battery pull and try again, but the same problem recurs every time.
Is there something I'm not doing correctly?
Just an update...
In playing around with this a little more, I got this message:
E: Can't open /cache/recovery/command
Click to expand...
Click to collapse
At the top of the screen the options are:
Reboot system now
Apply update from SD card
Wipe data/factory reset
Wipe cache partition
http://forum.xda-developers.com/showthread.php?t=865204
That thread will answer your question. Post #3 has an explanation of the image. You need to flash a recovery (.IMG) file from the bootloader. Hope that helps.
Good luck
db56319 said:
http://forum.xda-developers.com/showthread.php?t=865204
That thread will answer your question. Post #3 has an explanation of the image. You need to flash a recovery (.IMG) file from the bootloader. Hope that helps.
Good luck
Click to expand...
Click to collapse
^^Exactly^^
Simple issue. You just havent loaded clockwork or Amen Ra properly. If its a brand new evo hit unrevoked.com up. Download the program. Hit the button and wait. It roots and flashes clockwork for you.
Easy..
Hey Everyone,
Im sorry in advance if I'm about to ask the dumbest questions of the day/week, but I'm brand new to this, and I haven't found any answers in any of these threads, so go easy...
Up until now I customized the heck out of my mt4g. Tonight however, I followed HTC's instructions and unlock the boot loader -- as I thought based on what their site said, that I'd be able to flash custom roms to the phone once unlocked.
I was successful in unlocking the Bootloader, but (S=on) still exists. I'm kinda stuck now because I don't know what to do next? Is it possible to go from here to Root, if so, how? I've tried the HTC Super Tool for over an hour and it's not working... not giving me perm S=off. Maybe I'm doing something wrong?
If the phone isn't rooted, then how am I supposed to be able to flash a rom??... Do I do it from the HBOOT menu? Because I can't seem to do that either. If I opt for "recovery" while in HBOOT, I come to a red triangle, and have to do a battery pull.
The stock rom that's loaded now has GB 2.3.4 running.
My goal is simply to get CyanogenMod running on this phone. I just don't know what the next step is. I've already factory reset the phone so all my customizations and apps are gone therefore I don't really care what I have to do to get where I want to go. If it's possible to root from here, what's the next step? If root isn't possible, then how do I flash a new rom, like HTC claims I can do now that the BL is unlocked??
If someone could offer some help, I would be super appreciative!!
T40
Follow this link . Very well written guideit worked for me http://forum.xda-developers.com/showthread.php?t=1178912
headcreepz said:
Follow this link . Very well written guideit worked for me http://forum.xda-developers.com/showthread.php?t=1178912
Click to expand...
Click to collapse
Follow that guide and get off the official HTC unlock. You should have read the thread on this forum about it.
Sent from my mytouch 4g using xda premium
okay... I followed the guide and I achieved "perm-root", I believe.
If I go into terminal emulator, and type SU, I get a # returned. I do notice however that when I boot into HBOOT, it still says s=on. Not sure what the difference is between 'perm root' and 's=on' but...
I have rom manager downloaded. I also have titanium backup downloaded and did a full backup.
PROBLEM:
In rom manager, I Flashed ClockworkMod Recovery, and then downloaded the nightly CyanogenMod, no problem, but every time the phone reboots (into recovery mode), I stop at the red triangle?!?!?!
What's going wrong?
Open rom manager and art the top is an option to install recovery-install it, then you should be good to go
I did install recovery. Everytime it reboots into recovery i get the red triangle.
After I get the red triangle, and I hold the Vol Up button and hit power, I come to a BLUE recovery menu (3e) with 4 options:
- Reboot system now
- Apply update from sdcard
- Wipe data/factory reset
- Wipe cache partition
in the middle of the screen, in yellow text it says "E:Can't open /cache/recovery/command"
track40 said:
I did install recovery. Everytime it reboots into recovery i get the red triangle.
After I get the red triangle, and I hold the Vol Up button and hit power, I come to a BLUE recovery menu (3e) with 4 options:
- Reboot system now
- Apply update from sdcard
- Wipe data/factory reset
- Wipe cache partition
in the middle of the screen, in yellow text it says "E:Can't open /cache/recovery/command"
Click to expand...
Click to collapse
That's the stock android recovery.
Sent from my Infernalized Glacier!
-Team Inferno
If you had your device s-off and rooted, why HTC unlock? You just went backwards.
i started with HTC Unlock, then achieved perm-root, but (s=on)
Recovery
Hello,
I had the same issue, I had to flash the recovery with adb
1) If you dont already have it download flash_image and place it in your adb tools folder
2) Download the recovery you need and unzip, then rename to recovery.img and place in the root of your sdcard
3) open terminal and use the following commands
adb push flash_image /system/bin
adb shell
su
cd /system/bin
chmod 777 flash_image*
flash_image recovery /sdcard/recovery.img
4)wait for it to finish
5) type exit
adb reboot recovery
this should solve the issue
You can find the recovery here...including the new touchscreen version
http://clockworkmod.com/rommanager
You can download flash_image here
http://forum.xda-developers.com/showthread.php?t=902493
Thanks to Raichison for all the above
okay #furydude39, im all ready to run through your steps... when i issued the first command "adb push flash_image /system/bin", the handset responded with
"failed to copy 'flash_image' to '/system/bin/flash_image': Read-only file system"
Any idea where to go now? This is obviously why every time i boot into recovery that the processes initiated by RomManager isn't sticking.
an hour later...
I was able to execute the commands correctly that 'furydude39' recommended, and still nothing.
Here's a video I shot of the phone [still] giving me a headache
http://youtu.be/2Hr-7CosDQc
Someone's gotta have an idea on how to get past this?
Have you turned off fastboot?
Sent from my HTC Glacier using xda premium
yes, just checked... fastboot is off
We need to find out why it is not flashing the cw recovery. Are you able to to mount /system partition and copy files to it? I'm thinking a downgrade might be necessary so you can do gfree and eng bootloader.
Sent from my HTC Glacier using xda premium
okay guys...
I got past the last problem, of getting clockwork mod recovery to work. So, that's all set.
NOW, I use rom manager and i downloaded cyanogenmod 7.1 (stable) + google apps. Once the downloads were complete, I checked all three boxes... backup, clear caches, clear dalvik cache. The phone reboots, goes right into clockwork mod recovery.
the backup goes fine... the cyanogen flash goes without error, and then the google apps flashes without error.
NOW, the phone reboots, and the thing just hangs on the White t-mobile boot screen. Is this supposed to take a while before it goes into Cyanogen's screen? It's been sitting on this white screen for at least 5 minutes.
track40 said:
okay guys...
I got past the last problem, of getting clockwork mod recovery to work. So, that's all set.
NOW, I use rom manager and i downloaded cyanogenmod 7.1 (stable) + google apps. Once the downloads were complete, I checked all three boxes... backup, clear caches, clear dalvik cache. The phone reboots, goes right into clockwork mod recovery.
the backup goes fine... the cyanogen flash goes without error, and then the google apps flashes without error.
NOW, the phone reboots, and the thing just hangs on the White t-mobile boot screen. Is this supposed to take a while before it goes into Cyanogen's screen? It's been sitting on this white screen for at least 5 minutes.
Click to expand...
Click to collapse
You should manually wipe and flash. Doing it from the app seems to screw up some of the time. Make sure you wipe system data cache and dalvik before flash. It even helps to reboot recovery after doing wipe before you flash a rom.
Sent from my HTC Glacier using xda premium
i hate to ask another [stupid] question... but how do i manually do that?
track40 said:
i hate to ask another [stupid] question... but how do i manually do that?
Click to expand...
Click to collapse
In recovery, using the volume rockers, look for factory data reset/wipe. I'm not to positive on the exact names, since I have touch recovery. When you find it select wipe data an wipe cache. after those are wiped, go back then find advance, wipe dalvik cache. When that finished, go back. Select install from sdcard, find your files an install them. Everything should work then.
If I helped, give thanks, if you please.
........Death before dishonor........
Team inferno
Leader
Thanks all for your suggestions. I finally was able to get Cyanogen to stick. Had to wind up flashing the boot.img manually using fastboot via Windows while in HBOOT screen.
Hello, I've recently completed the Bootloader unlocking method with Easy Ace Root Tool. Bootloader is unlocked and SHIP S-ON, I need to flash a rom. These roms require S-OFF and have no method to flash them with only an unlocked bootloader and S-ON.
So let me get this straight, us 'low level' and unexperienced users are left without any method to gain S-OFF privileges without following the vague guide provided at tau(dot)shadowchild(dot)nl/attn1/?p=411 Yeah... I can't.
Trying to find alternate methods I have only gone in circles and keep running into old how-to guides. The more I read the more confused I become. I hope someone can point me in the right direction, I would really appreciate it!
Thanks,
Ninjewbag
You don't need S-Off. Flash a ROM in recovery, then flash the ROM zip's boot.img in fastboot.
bananagranola said:
You don't need S-Off. Flash a ROM in recovery, then flash the ROM zip's boot.img in fastboot.
Click to expand...
Click to collapse
Good deal, thanks for the reply!
I put the ROM Android Revolution HD 9.0 on the root of my SD card, booted in recovery mode and chose the recovery option, I got the red exclamation mark icon so I pressed VOL up + power button which didn't work so I pulled the battery. I tried all above steps again but this time I was able to successfully get into "Android system recovery <3e> with VOL up + power button. With 4 options:
Reboot system now
Apply update from sdcard
wipe data/factory reset
wipe cache partition
I chose the option to wipe all data, said it could not find Efolder name)'s and "data wipe completed successfully".
Then I wiped cache, then chose the option to apply update from sdcard, it said "Invalid operation" then "success rebooting by reason 00" and proceeded to reboot by itself.
Phone factory reset, I rebooted into recovery again with the same red exclamation mark error. Pressed Vol up + power and back into "Android system recovery". At the bottom in yellow text it says "E: Can't open /cache/recovery/command". I tried another "update from SD card" and recieved error: "success rebooting by reason 00" and reboots.
I don't have a nandroid backup as I read I needed Root to make one, but the phone still works fine as far as I can tell. I don't have a working simcard in it though.
Also from what I've read my eMMC chip may be fried so it looks like I'm retiring early. I'll keep an eye on this thread among others with the same problems.
Cheers,
Ninjewbag
Volume + and power brings you to the factory recovery; you need to use vol - have you flashed a different recovery? If not, flash 4ext recovery through fast boot and try again
RadRacer said:
Volume + and power brings you to the factory recovery; you need to use vol - have you flashed a different recovery? If not, flash 4ext recovery through fast boot and try again
Click to expand...
Click to collapse
Thank you for the info! No luck finding the 4ext .IMG file anywhere yet, they're all dead links. I have the 4ext recovery.APK but that doesn't do me any good since I don't have root. Still looking and thanks again.
http://forum.xda-developers.com/showthread.php?p=31211732
ninjewbag said:
Thank you for the info! No luck finding the 4ext .IMG file anywhere yet, they're all dead links. I have the 4ext recovery.APK but that doesn't do me any good since I don't have root. Still looking and thanks again.
Click to expand...
Click to collapse
You can install the app and then open the app and use it to manually download the recovery zip which you can flash or copy it to your pc and extract the recovery.img file and flash with fastboot. It's a good idea to familiarize yourself wiht the adb and fastboot utils as they come in handy.
turboyoshi said:
You can install the app and then open the app and use it to manually download the recovery zip which you can flash or copy it to your pc and extract the recovery.img file and flash with fastboot. It's a good idea to familiarize yourself wiht the adb and fastboot utils as they come in handy.
Click to expand...
Click to collapse
Thanks for the reply but as for installing the 4ext free updater version, it wasn't on the market so I used android injector to place and install that APK. None of the options worked as they all give the same error "it seems your phone is not rooted, this option will not function" etc.
RadRacer said:
http://forum.xda-developers.com/showthread.php?p=31211732
Click to expand...
Click to collapse
Nice! Wasn't expecting to find the 4ext recovery within the adbfastboot.zip. With that I was able to move on, create a nandroid and successfully install a custom rom, thanks! Was a little scared after rebooting, it took around 5 minutes to load past the "quietly brilliant" screen but is working fine now nonetheless.
ninjewbag said:
Nice! Wasn't expecting to find the 4ext recovery within the adbfastboot.zip. With that I was able to move on, create a nandroid and successfully install a custom rom, thanks! Was a little scared after rebooting, it took around 5 minutes to load past the "quietly brilliant" screen but is working fine now nonetheless.
Click to expand...
Click to collapse
Glad to help. Wanna hit thanks?