Hi guys, sorry if there's some solution already available on the forum, but I didn't find it and am really afraid of what the fu** is happenning with my Desire S One day I have entered Android Market and clicked "Update All" in "My Applications" tab (there were about 14-15 updates available) and lied down my phone on the desk. After few minutes I looked at it and it was dead (blac screen with backlight on) - it was not responding at all, so I pull the battery out and in again. This time it was still able to turn on, but every time it got stuck in few minutes (when updates have resumed) - the only way to get it works was to canlcel every update. I was able to cancel one per reboot (before HTC got stuck), but after few reboots I have finally canceled all updates, and... my phone seemd to work properly again Yeah... 'seemd to' ;/ I have updated few apps manually (only one at a time) and then tried to download and install some new app (about 25MB) - then my phone has finally broke down;/ At the beginig I was able to enter a bootloader, but after trying to enter recovery (it has failed because there were no backup in sd/recovery dir) it has died at all - not reacting for any key pressed After plugging it to PC it has started to blink with it's LED, but that's all And later it didn't even want to blink with this diode
Has anybody any idea, what the hell is going on?? I have never flashed that phone etc. so what could happen? Please help me, because I want to avoid hard resteing my phone to save some data on it if it'll be still possible...
Oh, and sorry for my english
This has been mentioned before and the 'update all' option seems to have been a contributing factor to fried eMMC along with pulling the battery and putting it back in again to quickly
Read the posts in the end of the index thread, eMMC issue section (see last link in my sig)
Swyped from my Desire S using XDA Premium
Thanks for replies, now I see that it truly can be an eMMC issue :/ I have read littlebit about it now, but unfortunatelly I can't even check if my eMMc is fired, cause I haven't got debugging mode on And now ADB works correctly on my PC, but it doesn't see my device
BTW. Can you tell me how to execute instructions given by amidabuddha (about checking eMMC)? He writes to execute "dmesg | grep mmc0" comand, but this command is not recognized by my command prompt (paths are set correctly and so on) so I'm not able to try it even on a working phone (Wildfire connected and recognized by ADB correctly)... :/
EDIT:
I have read somewhere, that if my bootloader is unlocked, than I can flash a new recovery image and do a nandroid backup. Does it mean "if my phone is S-OFF"? Is there any way to retrieve some data from my phone if it's not? I'm still able to get into bootloader, so it should be easy to reset to factory defaults (if my eMMC isn't fried, which I can't check ), but I still got hope to save some data... Can anybody help?
mrkaczor said:
Thanks for replies, now I see that it truly can be an eMMC issue :/ I have read littlebit about it now, but unfortunatelly I can't even check if my eMMc is fired, cause I haven't got debugging mode on And now ADB works correctly on my PC, but it doesn't see my device
BTW. Can you tell me how to execute instructions given by amidabuddha (about checking eMMC)? He writes to execute "dmesg | grep mmc0" comand, but this command is not recognized by my command prompt (paths are set correctly and so on) so I'm not able to try it even on a working phone (Wildfire connected and recognized by ADB correctly)... :/
EDIT:
I have read somewhere, that if my bootloader is unlocked, than I can flash a new recovery image and do a nandroid backup. Does it mean "if my phone is S-OFF"? Is there any way to retrieve some data from my phone if it's not? I'm still able to get into bootloader, so it should be easy to reset to factory defaults (if my eMMC isn't fried, which I can't check ), but I still got hope to save some data... Can anybody help?
Click to expand...
Click to collapse
What is your bootloader version? If you are S-OFF then you can install a Recovery and in the better case formatting cache will do the trick. If your bootloader is locked (Stock) just give your device for a repair. This is a well known problem to the HTC guys and it will be covered by your warranty.
All the data on your SDcard is still there (pictures, etc). The contacts and calendar items can be restored via your Google account later if you had a sync previously. Probably you will lose your SMS.
Unfortunatelly my phone is S-ON, the informations given in bootloader are as follows:
SAGA PVT SHIP S-ON RL
HBOOT-0.98.0002
RADIO-3805.06.02.03_M
eMMC-boot
Mar 30 2011,17:29:31
So it seems that the only solution is to send my phone for eMMC replacement And to say 'goodbye' to all my data... Anyway thanks for help guys...
Related
Hi guys.
After two weeks without wifi, yesterday, my phone decide to update about 20 apps from market. When Beautiful Widgets were downloading, phone suddenly froze and I had to remove my battery after 10 minutes. When it booted again, Angry Birds started to update and phone froze again. So I removed my battery once again and when it booted up, I turned my net connection offline to prevent downloading. As soon as I did so, I canceled all market downloads and turned connection online again. Market started updating on its own and phone froze during night.
So I decided to removed battery once again this morning and when I put it back in, put it back in, phone froze after "Quietly Brilliant" logo with black screen.
It was suitable for factory reset from bootloader. So I did factory reset and same story repeated, except for this, it was a loading loop, HTC Quietly Brilliant and sound which comes with it over and over again.
So in the end, I tried to do the "recovery" option which did no good and again factory reset, but this time, bootloader froze and nothing happened. This is final state of my phone.
So after boring story, there is a question. Is there any way I can do software flash / reset without phone (via USB etc?) before I send it back to HTC for repair?
Device is S ON and never been rooted. I also removed SIM and memory card with no effect.
Thanks a lot!
You should take hope from the fact that you are able to still enter bootloader and perform full reset
Also the fact that you are still s-on means that you should still be covered under warranty
I believe that you should be able to re flash your original rom via your pc using RUU, check to see if your original is in the rom sticky thread within the dev section and if so start downloading
Sent from my HTC Desire S using XDA Premium App
You may well have a hardware problem, in which case I would advise you send it for repair rather than trying to root and invalidating your warranty.
Hey, thx for reply.
I have no experiences in this but I guess I only need to know this things:
RUU - Stands for ROM Upgrade Utility. What soft should I use?
Also, all I can see in bootloader is following:
SAGA PVT SHIP S-ON RL
HBOOT-0.98.0000
RADIO-38.03.02.11_M
eMMC-boot
Mar 10 2011,14:58:38 (<wtf?)
and then just classic boot menu with options like FASTBOOT etc.
Therefore I cant figure out, which ROM is mine in that thread. Also, is there any option to flash ROM from memory card? Does it have to be signed?
Only limitation is warranty which I dont wanna lose. Thx.
InfernalByte said:
You may well have a hardware problem, in which case I would advise you send it for repair rather than trying to root and invalidating your warranty.
Click to expand...
Click to collapse
See the statement above, I will not do anything to invalidate the warranty.
Yesterday, after attempting the "Update all" for the first time (well, not exactly) the phone froze just as yours did & started encountering the same issues. After coming here to seek assistance, this thread was the first I laid eyes upon.
My case in somewhat more detail, after freezing during the "Update all", I performed a soft reset by removing the battery as well, booted up fine, but as soon as everything was loaded the market tried to continue where it left off (which is updating Opera Mobile @ 98%) and the result was another freeze. I was quickly able to deduct that the update were to be the issue & turned off connectivity. Now, at the present state, Opera Mobile update is still under notifications (at 98% complete but "paused"), as soon as I re-enable either WiFi or 3G it continues & crashes. I cleared all caches & reset all Market applications & rebooted to no avail.
Hard reset was next on my list, but see-ing how the situation got worse for your device hereafter, I am holding it off for now. Is it possible to have market updates, that are ongoing, canceled? Bear in mind that I cant enter Market since it requires connectivity.
Weird stuff.
Yes, when your phone is turned on (connection on), open your Market app, press menu button and select "My apps". You should see all downloading apps now. Hold your finger on each and wait until menu pops up. Select cancel download. You have to be quick tho.
If I were you, I would not do any software reset, my phone is pretty much bricked now, as it freezes on nearly every bootloader option.
Numline1 said:
Yes, when your phone is turned on (connection on), open your Market app, press menu button and select "My apps". You should see all downloading apps now. Hold your finger on each and wait until menu pops up. Select cancel download. You have to be quick tho.
If I were you, I would not do any software reset, my phone is pretty much bricked now, as it freezes on nearly every bootloader option.
Click to expand...
Click to collapse
Thanks! That did the trick, was able to remove everything due to be updated.
Strangely, though, I wasn't able to finish loading the market before it resumed the Opera update. This time, however, instead of crashing it was able to complete it (contrary to the last 10+ attempts yesterday), thus there is a chance it wouldn't have crashed at all. In any case, keeping distance from the Market seems like a valid idea for now.
Reading your thread might've helped to avoid my device turning into a brick, I appreciate it.
Well, update to my current status:
Im still in hboot. Device was recognized as "Android 1.0" in my Windows, so I had to install ADB driver. It is now connected as Android Composite ADB Interface".
I can't get any further, since RUU says my phone is not connected to PC.
Any advices please?
PS: When I choose "Recovery" in hboot, it shows HTC logo for a while, then icon of mobile phone with green sign shows and after few secs, screen turns off and phone vibrate for a few times and disconnects from PC.
//When I connect it in Fastboot, it shows as "MyHTC" in Windows.
Numline1 said:
PS: When I choose "Recovery" in hboot, it shows HTC logo for a while, then icon of mobile phone with green sign shows and after few secs, screen turns off and phone vibrate for a few times and disconnects from PC.
Click to expand...
Click to collapse
Afraid, that I'm well out of my depth with all that, hopefully someone else with more knowledge will post...or else it's warranty return. best of luck
Np, thx for trying, maybe someone else will know
//Update: In Fastboot mode, my device is recognized by RUU!!! Trying to update right now!!!
As you've never been rooted or S-off, and the phone has developed its own fault. I'd return it!
Well, so far, no luck. RUU stuck at "Rebooting to bootloader" and phone is frozen.
InfernalByte said:
As you've never been rooted or S-off, and the phone has developed its own fault. I'd return it!
Click to expand...
Click to collapse
Im willing to do that first thing tommorow, but Im trying to fix it today, as it is sunday and I have day off.
Numline1 said:
Well, so far, no luck. RUU stuck at "Rebooting to bootloader" and phone is frozen.
Im willing to do that first thing tommorow, but Im trying to fix it today, as it is sunday and I have day off.
Click to expand...
Click to collapse
Good luck
(....10 Chars...)
Ok, update about my phone so far:
RUU was not sucessful, for some reason there's still freeze in certain HBOOT actions, like when I select "Factory reset" or when RUU is trying to get phone from fastboot to bootloader.
So I extracted rom.zip from my RUU and now I'm backing up my memory card using my old phone. I'm willing to rename it to update.zip and try to flash it.
Any advices about this?
Numline1 said:
Ok, update about my phone so far:
RUU was not sucessful, for some reason there's still freeze in certain HBOOT actions, like when I select "Factory reset" or when RUU is trying to get phone from fastboot to bootloader.
So I extracted rom.zip from my RUU and now I'm backing up my memory card using my old phone. I'm willing to rename it to update.zip and try to flash it.
Any advices about this?
Click to expand...
Click to collapse
Update.zip will not work, if your determined to try something push a new SPL via fastboot commander, even thought your not S-off if things aren't working maybe the CID check wont check either.
Below will only work if your phone is not branded or you have a goldcard.
Alternatively unzip your RUU on your PC in one of the files called {squigly brackets and a lot of numbers673652435364849483763} you'll find a .zip called rom.zip rename this PB99IMG and put the file into the root directory of your SD card, and boot into Hboot. Just answer yes to any questions. This is the way HTC Tech folk themselves serve an RUU.
Yea, I actually extracted it using advanced system monitor from microsoft, this file was in temp folder. That's where my rom.zip was. Anyway, isn't it PB88IMG.zip? I think DS is checking for this one. Thx.
//Edit: I mean PB88IMG.img
//Edit2: It's PG88IMG.zip It's now updating, don't know if it works yet, still at BOOTLOADER update with status "Updating".
Ok, I think this is my last post, since I no longer know what else to do. When Im trying to flash PG88IMG, it stops at [1]BOOTLOADER - Updating.
For more than one hour. There's something wrong with it and I will claim my warranty, which will be funny, since Im in Slovakia, phone was bought from Amazon with 3 year warranty from SquareTrade and they claim, they may just return money in some cases, which will result in buying a new phone = more than 2 weeks...
Numline1 said:
they may just return money in some cases, which will result in buying a new phone = more than 2 weeks...
Click to expand...
Click to collapse
O, bugger!
question is if they do give you the money, will you buy another DS? and if not what would you consider instead? Sensation?
Yea, can't say yet, since I don't know. I just discovered, there may be a chance they will cover my repair costs when I email them all the service documentation from service center.
But if they do, I'd like to stay with HTC, I paid something about 377L for the phone, so I may buy something better now.
Anyway, thanks a lot for help guys, if you come with some new ideas about how to fix it, do not hesitate to tell me I'll be sending it to them first thing tommorow.
Hey guys,
Got a bit of a weird situation here and have spent 3 days pondering this and surfing the web with no success -
I noticed my friends HTC Desire S had a crack in the screen so offered to repair it for her, free of charge - say for my cost. I didn't get a chance to do it before holiday so went to pick it up when I got back and she explained that since then the phone has developed a fault and now won't turn on past the boot logo. I have no idea if this is related to her dropping it - I'm assuming it was a bad app download or something?
I followed various guides on YouTube, XDA forums and other external sources but am getting stuck at a particular stage which is what I think I need help with - I may just be chasing my tail but don't have the background to know otherwise. I have download Fastboot drivers, Revolutionary etc. with the intention of S-OFFing the phone and re-flashing the software - doesn't technically need to be custom but it seems easier to get hold of. I do not know if Fastboot or debugging mode are turned on/off due to the inability to turn the phone on.
Revolution sticks 'Waiting for Device...' - Here's what I've tried:
- Factory resetting the device from the bootloader menu but it freezes. (It also freezes if I select 'reboot bootloader')
- I have tried multiple USB cables in 3 laptops (with the drivers installed) but have had no success.
- Using Fastboot.exe to test if the laptops can see the device - which they can.
Eventually I got frustrated with this so moved on to the screen - no problems replacing that. No internal damage that I can see.
All the buttons work, it still vibrates etc. I can't test the sound - I'm running out of troubleshooting ideas and trying not to be too invasive where I'm unsure of what I'm doing to save bricking the phone.
Here is the Bootloader Info:
""SAGA PVT SHIP S-ON RL
HBOOT-0.98.0002
RADIO-3805.06.02.03_M
eMMC-boot
Mar 30 2011,17:29:31""
Does anyone have any suggestions of a path to follow or any step by steps to eradicate my problem?
I will post back my triumph (if possible) so others can hopefully overcome it!
Also, any advice on which RUU to use? I don't know the network the phone is on but can find it out.
Thanks alot for reading!
Josh
If it is not a hardware fault using a RUU should make the phone running again.
You do not need additional modification, just start the RUU while connected to a PC is FASTBOOT USB mode.
How to know the proper RUU version see here
P.S.: this will work only if you have not tried any other RUU so far.
Revolutionary uses adb not fastboot, this is the reason it cannot find the device. It will work only when fully booted in the OS or in a custom recovery.
Sent from my HTC Desire S
Thanks for the quick reply mate, I started downloading a Vodaphone RUU straightaway.
I am now having an issue with this - the phone is plugged in and sat waiting in Fastboot USB (on the bootloader,) I run the RUU on the computer, run through all the menu's and when it attempts to apply the Radio Update it sticks at 'Rebooting the Bootloader' and seemingly freezes the phone. As mentioned above, if I try this manually it does the same thing.
Any Ideas?
If it is the right RUU then most probably it is some kind of hardware problem. Sorry but this was the only software fix that I can suggest.
You can try to revive it with JTAG if you have such service in your area.
Sent from my HTC Desire S
I have followed all of the procedures to reload my phone stuch on the splash screen, but have had no luck. Before I dispose of the phone, as it is in mint condition, I want to be sure there is no other options to update / reformat the bootloader
1. I have loaded the image for 2.2.1 AND 2.3.4 MULTIPLE TIMES
2. I have cleared the Cache's and no change
3. status on bootloader shows
GLACIAER PVT SHIP S-ON
HBOOT-09.0006
MICROP-0429
RADIO-26.13.04.19_M
eMMC-BOOT
Jul 15 2011, 16:45:17
I guess the last hope since th reloading the original images did not work is to reload / format the bootloader using ADB, but I believe that I have the wrong HBoot.
Is the phone eMMC bad and the phone bricked or is there something else to try?
johnmbailey said:
I have followed all of the procedures to reload my phone stuch on the splash screen, but have had no luck. Before I dispose of the phone, as it is in mint condition, I want to be sure there is no other options to update / reformat the bootloader
1. I have loaded the image for 2.2.1 AND 2.3.4 MULTIPLE TIMES
2. I have cleared the Cache's and no change
3. status on bootloader shows
GLACIAER PVT SHIP S-ON
HBOOT-09.0006
MICROP-0429
RADIO-26.13.04.19_M
eMMC-BOOT
Jul 15 2011, 16:45:17
I guess the last hope since th reloading the original images did not work is to reload / format the bootloader using ADB, but I believe that I have the wrong HBoot.
Is the phone eMMC bad and the phone bricked or is there something else to try?
Click to expand...
Click to collapse
When you try to flash PDwhatever.IMG, what does it tell you?
Glacier locked at Mytouch logo, without image load errors
THEindian said:
When you try to flash PDwhatever.IMG, what does it tell you?
Click to expand...
Click to collapse
It does not give any errors after flashing to 2.3.4, as it loads, verifies, then asks to load. It then successfully loads all pieces of the image, only to reboot to the same Mytouch logo screen.
When I use recovery, it can't mount anything, and when I wipe the Cache, it give arror that Ext3 is not compatible.
I reboot and factory restore in recovery, and gives the Ext3 compatibility message and can't mount anything.
I never receive any image loading errors, but I cannot load the 2.2.1 image, as it never give me a chance to say 'yes' to loading it.
If it doesn't work, care to sell it? I need a back and home button for mine lol
I also think my volume buttons will be gone soon, their starting to stick
Sent from my Dark Unicorn Resurrected v.2.5 using xda premium
siloner said:
If it doesn't work, care to sell it? I need a back and home button for mine lol
I also think my volume buttons will be gone soon, their starting to stick
Sent from my Dark Unicorn Resurrected v.2.5 using xda premium
Click to expand...
Click to collapse
The phone is in Mint Condition, so I hoped to resurrect it if at all possible, but if it is not possible I definitely will be selling it whole or in part.
johnmbailey said:
It does not give any errors after flashing to 2.3.4, as it loads, verifies, then asks to load. It then successfully loads all pieces of the image, only to reboot to the same Mytouch logo screen.
When I use recovery, it can't mount anything, and when I wipe the Cache, it give arror that Ext3 is not compatible.
I reboot and factory restore in recovery, and gives the Ext3 compatibility message and can't mount anything.
I never receive any image loading errors, but I cannot load the 2.2.1 image, as it never give me a chance to say 'yes' to loading it.
Click to expand...
Click to collapse
Thats really weird because usually if the emmc is dead, the image doesn't load completely in the bootloader. Have you tried calling tmo and telling them about your predicament? I know you are over warrenty but they might still help.
Glacier Stuck on Splash, now on StraightTalk service
THEindian said:
Thats really weird because usually if the emmc is dead, the image doesn't load completely in the bootloader. Have you tried calling tmo and telling them about your predicament? I know you are over warrenty but they might still help.
Click to expand...
Click to collapse
I am now on Straight Talk, so I no longer have a TMobile account to call about. My PAygo ended on Sunday with them.
Can I load anything from ADB with this version of the HBoot / Bootloader? Does the Ext3 mean it had a newer Rom, so I need to change to a supported type using ADB? IT almost looked like the Ext3 format was causing the problem. This also might be a red flag to support if it was not on a factory format. I inherited the phone, so I do not know the history.
Since it never finished booting, is there any way to use the original HTC.exe programs that install the RUU image?
Why are you s-on? Shouldn't you be s-off if you want to install a rom??
Have you tried rooting method again? As far as i know using the gfree method should not give you this issue,
Sent from my Arrows Z using xda app-developers app
Mytouuch 4g - stuck at splash screee
I bought phone from CL. As I suspected previous owner tried to mod the phone. It loads to splash screen. I can get into bootloader but can not select RECOVERY or FACTORY RESET. I tried the PD15IMG.ZIP but when i extracted hboot is 0.89 (and the following happens):
***LOCKED***
GLACIER PVT SHIP S-ON
HBOOT-0.90.0000
MICROP-0429
RADIO-26.13.04.19_M
eMMC-boot
PD15DIAG.ZIP
no image
PD15DIAG.nbh
no image
Main Version is older!
Update Fail!
Press<power> to reboot
I think i need the IMG that pertains to the HBOOT.
HELP PLEASE
Thank you all
Glacier is Stuch at Splash, so what are options after reloading img?
NeuroticallyYou said:
Why are you s-on? Shouldn't you be s-off if you want to install a rom??
Have you tried rooting method again? As far as i know using the gfree method should not give you this issue,
Sent from my Arrows Z using xda app-developers app
Click to expand...
Click to collapse
The phone is stuck at the splash, so what options do I have that load from SD or USB at the 'Stuck' splash or 'Bootloader'? Can I use the HTC EXE programs to reload the phone or do they require a 'fully booted' phone? Is there any way to load the engineered hboot / bootloader so that I can have ADB options?
johnmbailey said:
The phone is stuck at the splash, so what options do I have that load from SD or USB at the 'Stuck' splash or 'Bootloader'? Can I use the HTC EXE programs to reload the phone or do they require a 'fully booted' phone? Is there any way to load the engineered hboot / bootloader so that I can have ADB options?
Click to expand...
Click to collapse
ok let's calm down and not panic, something similar happened to me when i started rooting my first MT4G, did you try to root the phone? if not i will suggest you to do that with the cyanogenmod guide HERE but before you follow the guide try to boot into bootloader by shutting the phone down, leave it off for like 10 seconds then turn it on by pressing the power button+volume down key, you will enter into bootloader usually you will see 3 androis at the bottom of the screen on skateboards if you don't see that but instead the phone keeps booting into splash screen then try again until you enter bootloader, wihle in bootloader you need to tell me what options you get and what options are enabled, since you can't mount the SD card you will have to get an adapter to download all software needed on the SD card(remember you have to remove the sd card from the phone since you can't mount it). Proceed with the guide until you install a custom rom like CyanogenMod 7.
this type of errors can be reproduced easily for example on a rooted phone wipe the phone completely and reboot, the phone will do exactly the same your phone is doing another thing is i don't know what is this HTC.exe program you are talking about everything is done with the android SDK so before doing everything in the guide you need to download and isntall the android SDK.
it seems like the previous person tried to root but instead messed up the phone system, probably corrupted? like i said i have reproduced the same behaviour on my MT4G many times and by now i don't freak out like it was the first time, the thing that have saved me is the rooting guide, i know by experience that you CAN'T install a rom or anything if you are S-ON.
Bootloader options on Glacier Stuck at bootloader
NeuroticallyYou said:
ok let's calm down and not panic, something similar happened to me when i started rooting my first MT4G, did you try to root the phone? if not i will suggest you to do that with the cyanogenmod guide HERE but before you follow the guide try to boot into bootloader by shutting the phone down, leave it off for like 10 seconds then turn it on by pressing the power button+volume down key, you will enter into bootloader usually you will see 3 androis at the bottom of the screen on skateboards if you don't see that but instead the phone keeps booting into splash screen then try again until you enter bootloader, wihle in bootloader you need to tell me what options you get and what options are enabled, since you can't mount the SD card you will have to get an adapter to download all software needed on the SD card(remember you have to remove the sd card from the phone since you can't mount it). Proceed with the guide until you install a custom rom like CyanogenMod 7.
this type of errors can be reproduced easily for example on a rooted phone wipe the phone completely and reboot, the phone will do exactly the same your phone is doing another thing is i don't know what is this HTC.exe program you are talking about everything is done with the android SDK so before doing everything in the guide you need to download and isntall the android SDK.
it seems like the previous person tried to root but instead messed up the phone system, probably corrupted? like i said i have reproduced the same behaviour on my MT4G many times and by now i don't freak out like it was the first time, the thing that have saved me is the rooting guide, i know by experience that you CAN'T install a rom or anything if you are S-ON.
Click to expand...
Click to collapse
The 2.2.1 image does not load due to 'older version' error in the bootloader, so I renamed it so that it would stop at bootloader to test working options.
Glacier pvt ship s-on
HBOOT-0.89.0006
MICROCROP-0429
RADIO-26.13.04.19_M
cMMC-boot
Jul 15 2011, 16:45:17
HBOOT
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
Fastboot of course works, as I am able to run the image load from SD card
REcovery works, but give the various mounting errors mentioned earlier
factory reset can be selected but does not change anything and it returns to the splash screen
I did not try simlock, as it looks irrelevant
image crc works and seems to check an image somewhere
When I select RECOVERY, Press UP Volume and Power to get past Triangle, it enters the recovery with all of the mount errors, and then the menu pops up
Androic System Recovery <3e>
Use volume .....
Select w Power....
Reboot System Now
Apply Update from SD card
Wipe data / Factory Reset
Wipe Cache Partition
Wiping DAta completes with Ext3 error, unable to mount anything, and unable to open errors, and returns to Recovery menu
Wiping Cache completes wipe with Ext3 error, unable to mount, unable to open and then reboots
Apply Update from SD Card also appears to fail
Rebooting by reason OEM
Cant mount
Count open
then it reboots
From what screens can you mount the 'drive' to use with ADB? When trying to run the ADB commands, I get the error device not found, so I either am not in the correct mode on the phone or I do not have the correct drivers. When coinnectd at the splash screen, my device manafer shows a Portable Device with Drive f:\ and the details show an Android Phone, but the drive is not visible or accessible by ADB.
When I start bootloader with Hboot at USB PLUG mode, the device manage on my computer changes to Android Bootloader device, but I still get 'Device Not Found' after executing the first ADB command. I then followed the info (I think) at http://forum.xda-developers.com/showthread.php?t=881324 with no success for ADB to work, so I something must be wrong.
It seems the S-ON option is not letting you go further, if it gave you a ext3 format error most likely is because the phone can't erase or rewrite the partition needed. Now I'm no expert on the hardware part but I put my small knowledge on that it have to do with the S-ON part of the phone.
Was the phone booting up properly before? If the phone can't boot to android then you can't use adb commands(for what I know) also the fact you don't have a custom recovery image will make it hard for you reinstall android.
I can probably make some time to help you but nothing is better than having the phone so I can troubleshoot. If you want we can chat on gmail to set up a remote session? Other than that I don't see how I can help you.
Sent from my Arrrows Z using xda app-developers app
FINAL Questions on Recovering Glacier MyTouch 4g stuck at Splash
NeuroticallyYou said:
It seems the S-ON option is not letting you go further, if it gave you a ext3 format error most likely is because the phone can't erase or rewrite the partition needed. Now I'm no expert on the hardware part but I put my small knowledge on that it have to do with the S-ON part of the phone.
Was the phone booting up properly before? If the phone can't boot to android then you can't use adb commands(for what I know) also the fact you don't have a custom recovery image will make it hard for you reinstall android.
I can probably make some time to help you but nothing is better than having the phone so I can troubleshoot. If you want we can chat on gmail to set up a remote session? Other than that I don't see how I can help you.
Sent from my Arrrows Z using xda app-developers app
Click to expand...
Click to collapse
Since the phone will not go pase the splash or bootloader / hboot.....
Questions:
1. Can the original manufacturer RUU - Rom Update Utility be downloaded somewhere and if so wouldn't it just need the phone in Bootloader mode?
2. For the ADB method, will it work with thge phone at the Bootloader screen, and if so what drivers arfe needed as the Android Bootloader ones do not work that are showing. Is these another setting beyond just the driver that needs to be set to use ADB?
3. Will a program like Odin that I used to recover my samsung image from bootloader work for these phones?
4. Does anyone have any ideas or should I just part out this Mint phone?
Please refer to previous posts for the details on what has already been tried....and what it is still doing.
johnmbailey said:
Since the phone will not go pase the splash or bootloader / hboot.....
Questions:
1. Can the original manufacturer RUU - Rom Update Utility be downloaded somewhere and if so wouldn't it just need the phone in Bootloader mode?
2. For the ADB method, will it work with thge phone at the Bootloader screen, and if so what drivers arfe needed as the Android Bootloader ones do not work that are showing. Is these another setting beyond just the driver that needs to be set to use ADB?
3. Will a program like Odin that I used to recover my samsung image from bootloader work for these phones?
4. Does anyone have any ideas or should I just part out this Mint phone?
Please refer to previous posts for the details on what has already been tried....and what it is still doing.
Click to expand...
Click to collapse
I don't know of an external app like odin that works for our phone. Also, there are no RUU's for the Glacier, only PD15IMG.zip files.
Since Mint MyTouch 4g Phone is Bricked, how much will work for Slide Version?
I saw an old post with a broken link for an RUU that was supposed to work on the Glacier called the panache. I finally found a working link and downloaded the RUU for Gingerbread, but when I ran it it gave and error that the battery was below 30%, even though fully charged and verified with my wall charger, and 2 usb chargers and 2 different batteries. I might try a powered USB hub, but this data on battery condition might have been stored on the phone somehow? If it could get the phone to work again, then a I could always reflash with a different ROM later.
If there is no hope of recovering this Mint MyTouch 4g Stuck on the splash screen, so can parts be used on the shift / slide version such as LCD / Digitizer, push buttons, or ????
It makes me sick to tear it apart.....
Any other thoughts?
Ran into similar problem
I ran into a similar problem with a message about the version number of the recovery image being wrong. This was a few weeks ago and I didn't keep a log of exactly how I fixed it but this is what I remember:
It turned out that during an attempt to root before I knew what I was doing I had changed the version number using the guide at the link below.
http://www.androidauthority.com/mytouch-4g-t-mobile-root-custom-recovery-74465/
That error message was misleading and the problem was instead due to the fact the phone was unlocked (although mine did say so on the bootloader screen.) HTC images have apparently been created to require a locked phone to successfully load. I relocked it in Fastboot USB mode with the command "fastboot oem relock" and was able to successfully load any version number after that.
Good luck.
Hello, have you tried using a different SD card?
Sent from my HTC Sensation 4G using xda app-developers app
Hi,
I have my HTC Desire S for about 6 month and it worked fine. About three weeks ago I installed the official ICS upgrade for this phone. The phone was rooted (by me) so I re-locked it in order to apply the update (sorry if I'm not using the right terms, I a bit new for this..).
A week ago, while in visiting in Rome, I tried to open my phone after the flight and it started a reboot loop. After a while it somehow recovered, and from the HTC recovery log I saw there was some "radio failure".
During the last week it would reboot from time to time, and I thought I would check it out when coming back home.
Now, trying to open it after the flight home - it won't even get beyond the HTC logo, just stuck in endless reboot loop.
I read some posts on this problem, but because my phone is re-locked I don't know what I can do: any thread about this problem requires the phone to be rooted. And I'm not sure how to root it because any thread about performing a root requires to open the phone and set up some settings, like 'enable debugging' for the USB connection (which I cannot do because phone keeps rebooting..).
Here is what I see at the HBOOT screen, hope it helps:
*** RELOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT-2.02.0002
RADIO-3831. 19.00.110
eMMC-boot
Jul 31 2012, 15:41:32
Trying to select FACTORY RESET will not help.
Trying to select RECOVERY ends with an error (I get a screen with a nice picture of the phone and red exclamation mark near it).
PLZ HELP!!
Thanks
Update: I've unlocked my phone again using the HTC site, so now the HBOOT screen shows *** UNLOCKED *** as the first line, other lines are the same (if this helps...)
UPDATE: I've used some very good guide (unfortunately I cannot post the link because I'm a new user..) for rooting and flashing a new ROM to my phone (downgraded to Gingerbread ROM), BUT the phone keeps rebooting..
Help plz....
As it did work until you opened the phone, either you made a physical problem, and now need a new board because it is defective, torn, cracked or something...
Or you made a mistake by removing the battery while the phone was still (partially) powered. This may cause some partition damage like on a pc. As there is no chkdsk available, the easiest solution is to repartition and reformat.
I read you already have reformatted the data partition by factory reset, and tried to repartition by installing that old update.
That would not work, as a normal flashing of a (custom or original) rom will / can not repartition the emmc chip. The only way to do that is to execute the RUU again what made phone get the ICS Update.
If that doesn't solve your problem, your phone seems to be defective.
The last option that remains then is to replace the emmc chip.
Verstuurd van mijn Nexus 7 met Tapatalk
Thanks for the reply.
Can you explain how should I reformat and repartition? I have now the ClockworkMod Recovery (V5.8.1.5)
I cannot run RUU because the exe file tries to connect to the phone and gets an connection error. It only worked when the phone completed its upload and now (because of the reboot-loop) I can't get to this state.
Ok, It took me some time to understand that when in fastboot the PC has communication with the phone and I can install RUU..
So I re-install the HTC official ICS RUU for my device and it seems PROBLEM SOLVED!
Phone has started, I could play with it a bit... and no reboots yet.
Let's see if it keeps like that for several hours / days... I hope it is not an hardware problem and only software...
Thanks!
Good day ,
I've been looking around for solution in this forum for two days now and none has helped me solving the problem I'm having. Hopefully by posting more specific details on this thread, you guys could help me pinpoint what to do. My main goal is to backup all data from the internal storage if possible (the data in the SD cards are backed up fine) then proceed to possibly make the phone usable again.
The phone was initially somehow soft-brick (loop on bootloader - tampered, locked, security warning and S-ON). Tried all possible actions/options on the bootloader but none has worked out, it would just prompt me back to bootloader. I am really not sure, as to how it ended up soft-brick. The phone was bought through Vodafone Australia carrier and has never been rooted etc.
So following guide on from (forums.androidcentral.com/htc-one-m8/398427-htc-one-tampered-locked-security-warning-2.html), So from the guide I've done as followed:
- I understand I have to firstly unlocked the bootloader, which was done just fine. So after Unlocked, I could still boot to hboot and getting tampered, unlocked and S-ON (no security warning).
- Then I connect my phone to fastboot, flash twrp-2.8.5.0-k2_ul.img and clear the cache
- I then tried to access the recover mode
- The phone restarted and stuck on the HTC logo with "Starting recovery..." message at the top but nothing really loaded for a long while
- So then I tried to restart it but it just won't work, I then pulled out the battery and re-inserted it
- After that, the phone was just stuck on the battery symbol with solid orange light on (this occurs if the USB cable is connected to power or computer), I tried all button, buttons up/down power hold etc (I even tried that covering middle battery part and let the outer ones connected) but none helped
-- If I unplugged the USB cable, the battery symbol and the solid orange light would still persist until it runs out of battery
-- If I removed the battery then re-insert the battery without connecting to USB cable, it's not displaying anything regardless how long I pressed the buttons (I tried holding them for more than 3 minutes which I assumed enough?)
That's pretty much everything, I really hope someone could shed some light for me - the thing is the data is fairly crucial that it may even help me prove a legal case, where some physical threats were sent out to me. :crying:
Thanks for the assistance in advance!
Help anyone?
i guess that if you didn't break your phone as i did the datas are still there and so, have you a recovery installed like twrp ? if not do it with bootloader, all you have to do is access fastboot and recovery to use adb commands and copy datas, if you can't do that i'm afraid there is no much to do without erasing all..
colton49 said:
i guess that if you didn't break your phone as i did the datas are still there and so, have you a recovery installed like twrp ? if not do it with bootloader, all you have to do is access fastboot and recovery to use adb commands and copy datas, if you can't do that i'm afraid there is no much to do without erasing all..
Click to expand...
Click to collapse
Hi there,
Thanks for your response, so I could access fastboot before and installed TWRP, the phone became 'totally' unresponsive after I installed TWRP and restart the phone.
At first it's stuck on recovery screen loading screen, then it just won't show anything. At the moment, I am wondering if there is any way to recover the internal storage data. I have contacted local HTC service center about the issue and they recommended me to go back to Australia (where I bought the phone) since they don't sell this model here in Indonesia (nearest country selling this model would be Singapore or Malaysia) - so yeah not much help from them as well.
Any other thought?
One SV does not respond
sorry wrong topic...