Hi guys, a little background :
I S-Off'd my Desire S a few weeks ago and installed/clicked gingerbread which i gather roots it?
One day my screen went blank randomly with just the notification bar showing up top. No buttons worked, couldn't turn it off etc.. so I did a battery pull. It then got stuck on the HTC screen, so I googled, tried clicking recovery/factory reset etc.. all while not really knowing what i was doing, but in the end it randomly loaded after a long wait.
Phew, or so I thought.
Now it constantly crashes, turns itself off, the camera doesn't work, force closes galore.. it's a mess. Figured the battery pull messed something up.
Searched a bit more and figured i should try and flash a ROM which might fix it and get it stable again.
Tried installing using 'download ROM' in Rommanager, it did all the installing and whatnot, but when it rebooted nothing had changed. Tried three times, same deal. Figure I should install a ROM via the SD card instead.
Found this forum and a relatively simple/safe guide :
I'm using the guide here : How to flash a perfect ROM.
http://forum.xda-developers.com/showthread.php?t=1257731
The Rom is MIUI.
However, I'm only on step 2 : Format data. (Formatting /system was fine)
Clockworkmod says Formatting /data for about 5 minutes, then : Error formatting /data.
Help!
A big thanks in advance.
Spare yourself a lot of troubles - use RUU and start fresh...
Sent from my HTC Desire S using XDA App
Could be a faulty eMMC chip on the phones motherboard, these tend to break after a few bad battery pulls?
If installing a new ROM on the phone wont work and you get data format problems I would do as posted above. If this doesnt work I would suggest a faulty eMMC chip.
amidabuddha said:
Spare yourself a lot of troubles - use RUU and start fresh...
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
Is there a fairly easy to follow guide that includes every step on here?
According to the FAQ I might have a fried chip.. the e:Unable to mount errors.
Can I still save it with the RUU?
I'm clueless, and a fair few of the guides are not too noob friendly tbh, could you please point me in the direction of an easy to follow guide?
I wish I knew how deadly the battery pulls would be before hand, but when your phone is frozen and you can't power it off, it seems logical. Arrrghg.
Much appreciated.
wax_addict said:
Is there a fairly easy to follow guide that includes every step on here?
According to the FAQ I might have a fried chip.. the e:Unable to mount errors.
Can I still save it with the RUU?
I'm clueless, and a fair few of the guides are not too noob friendly tbh, could you please point me in the direction of an easy to follow guide?
I wish I knew how deadly the battery pulls would be before hand, but when your phone is frozen and you can't power it off, it seems logical. Arrrghg.
Much appreciated.
Click to expand...
Click to collapse
Since you still can boot into your system you are good.
Download the RUU that is right for you from here. Connect your phone to the PC and run the RUU.exe. It will hadle everything automatically. Then you will be back to Stock. To go back to custom ROM:
1) use Revolutionary
2) no need of Gingerbreak since you will flash a rooted ROM
3) flash custom ROM from recovery
amidabuddha said:
Since you still can boot into your system you are good.
Download the RUU that is right for you from here. Connect your phone to the PC and run the RUU.exe. It will hadle everything automatically. Then you will be back to Stock. To go back to custom ROM:
1) use Revolutionary
2) no need of Gingerbreak since you will flash a rooted ROM
3) flash custom ROM from recovery
Click to expand...
Click to collapse
Ok, I have the RUU downloaded.
Should I just connect the USB cable to the phone while it's in ClockworkMod, HBOOT, or does it not matter?
Soooo.. plug in USB cable, run the RUU file in Windows.. should work?
Cheers again.
wax_addict said:
Ok, I have the RUU downloaded.
Should I just connect the USB cable to the phone while it's in ClockworkMod, HBOOT, or does it not matter?
Soooo.. plug in USB cable, run the RUU file in Windows.. should work?
Cheers again.
Click to expand...
Click to collapse
Yep. If by any chance the RUU installer says that it cannot detect your device go to Settings -> Development - > enable USB Debugging on your phone
amidabuddha said:
Yep. If by any chance the RUU installer says that it cannot detect your device go to Settings -> Development - > enable USB Debugging on your phone
Click to expand...
Click to collapse
Cheers. Yep, I got no phone detected, check your USB cable etc.. / ERROR [170] USB CONNECTION ERROR
I can't get into the phone to go into settings and turn USB debugging on though As soon as I get it functioning to that degree I'm not using it for anything other than calls in case I break it again. sadly, I could have earlier before I tried flashing a new ROM. Hindsight eh?
All I can get is HBOOT/ClockworkMod.
Tried RUU with the HTC white screen on and also while in Clockwork Mod.
Anything else I could try?
Thanks.
Are you using windows?
If yes download HTC sync and instal it, could be a missing driver.
Swyped from my Desire S
wax_addict said:
Cheers. Yep, I got no phone detected, check your USB cable etc.. / ERROR [170] USB CONNECTION ERROR
I can't get into the phone to go into settings and turn USB debugging on though As soon as I get it functioning to that degree I'm not using it for anything other than calls in case I break it again. sadly, I could have earlier before I tried flashing a new ROM. Hindsight eh?
All I can get is HBOOT/ClockworkMod.
Tried RUU with the HTC white screen on and also while in Clockwork Mod.
Anything else I could try?
Thanks.
Click to expand...
Click to collapse
From the power menu in ClockworkMod reboot to bootloader (hboot) and with the volume key go to FASBOOT (then you should see "FASTBOOT USB"). Then run the RUU again. Let me know is it working please because I will leave my PC soon
amidabuddha said:
From the power menu in ClockworkMod reboot to bootloader (hboot) and with the volume key go to FASBOOT (then you should see "FASTBOOT USB"). Then run the RUU again. Let me know is it working please because I will leave my PC soon
Click to expand...
Click to collapse
It worked, can't thank you enough!!
Cheers all.
wax_addict said:
It worked, can't thank you enough!!
Cheers all.
Click to expand...
Click to collapse
Good to know
Congratulations!
great to read another XDA forum rescue complete successfully!
Please update post#1 (using Go advanced edit) and prefix the post title with [SOLVED] to indicate that the problem is resolved.
Tectas said:
Are you using windows?
If yes download HTC sync and instal it, could be a missing driver.
Swyped from my Desire S
Click to expand...
Click to collapse
Limited to 5 thanks a day but I'll come back, this definitely helped I'm sure, fairly certain the drivers were needed.
wax_addict said:
Limited to 5 thanks a day but I'll come back, this definitely helped I'm sure, fairly certain the drivers were needed.
Click to expand...
Click to collapse
If your intending on re-running revolutionary to S-OFF your device again then you must first de-install the program HTC SYNC from your PC, don't worry the drivers are left behind and there are all that you need.
This is already the 4th case that the "E: cannot open...." error is successfully solved. I am keeping track on all such posts constantly and in my opinion if we have some more evidences for solved errors of this kind it will be good to remove the "[solved]BRICKed: inside eMMC's dead..." thread to avoid stressing the users...
I think this is a mistake of a service technician that was too lazy to diagnose and just replaced the chip...and started a great panic in this forum
Could be true.
I personally think there where a few devices out there with an chip failure, but most of the reported faults where wrong classified and could have been solved other ways.
Maybe it would be good to write the conclusion at the overall section down, cause our device isn't the only affected.
Swyped from my Desire S
Tectas said:
Could be true.
I personally think there where a few devices out there with an chip failure, but most of the reported faults where wrong classified and could have been solved other ways.
Maybe it would be good to write the conclusion at the overall section down, cause our device isn't the only affected.
Swyped from my Desire S
Click to expand...
Click to collapse
I will write a "calming" thread besides the Guide that is in my signature or as a part of it, just waiting for more confirmations that generally the chip is not affected when there is an error. But it seems not much people are reading the guides they prefer to start a new thread...Anyway I have a friend that is working at a centre of a Mobile Operator for my country and according to him among the hundreds (!) Nokia's, Samsung's, etc., he got only one faulty HTC for repair for the last 2 years (and there is a practice to replace rather than repair as well)
amidabuddha said:
This is already the 4th case that the "E: cannot open...." error is successfully solved. I am keeping track on all such posts constantly and in my opinion if we have some more evidences for solved errors of this kind it will be good to remove the "[solved]BRICKed: inside eMMC's dead..." thread to avoid stressing the users...
I think this is a mistake of a service technician that was too lazy to diagnose and just replaced the chip...and started a great panic in this forum
Click to expand...
Click to collapse
Good point although hopefully any new user experiencing this problem for the first time will create a post in this forum and can get pointed in the right direction, or better still there's always the hope that they will look at the INDEX/GUIDES themselves and read some of the resources that have been made available for them to use.
Possibly create a list of most likely resolution strategies in a new thread so that they can be tried in order and I'll refer users to that in the section on eMMC issues at the bottom of the INDEX thread, where I've tried not to scare users into thinking that its all too late and its game over in the textual intro bit!
ben_pyett said:
...
Possibly create a list of most likely resolution strategies in a new thread ...
Click to expand...
Click to collapse
Yep. My "[GUIDE] Read this before going for eMMC replacement" is updated with the solutions that worked so far..
Related
Tried this but I have this error after Fastboot :
HBOOT > FASTBOOT > no image or wrong image
also, tried factory reset but it just freeze or nothing happens after I chose FACTORY RESET.
Please help.
MarlX said:
Tried this but I have this error after Fastboot :
HBOOT > FASTBOOT > no image or wrong image
also, tried factory reset but it just freeze or nothing happens after I chose FACTORY RESET.
Please help.
Click to expand...
Click to collapse
Some questions, is your phone a standard DESIRE S, S-ON, with standard HBOOT etc?
I'd wait for someone with more Android experience than myself to confirm this, but, I believe that you should attempt to re-flash your original ROM (RUU). Which you should hopefully find somewhere in this post http://forum.xda-developers.com/showthread.php?t=1002506
ben_pyett said:
Some questions, is your phone a standard DESIRE S, S-ON, with standard HBOOT etc?
I'd wait for someone with more Android experience than myself to confirm this, but, I believe that you should attempt to re-flash your original ROM (RUU). Which you should hopefully find somewhere in this post http://forum.xda-developers.com/showthread.php?t=1002506
Click to expand...
Click to collapse
Thanks for the reply.
It's S-ON, this is untouched so I guess standard HBOOT?
Is flash(ing) ROM can be done even phone is not rooted?
Also, been searching around and found this (almost) same problem encountered, regarding "No image...", but I'm hesitant coz now I have to start from scratch again after that(?). :/
http://forum.xda-developers.com/showthread.php?t=648864
MarlX said:
Thanks for the reply.
It's S-ON, this is untouched so I guess standard HBOOT?
Is flash(ing) ROM can be done even phone is not rooted?
Also, been searching around and found this (almost) same problem encountered, regarding "No image...", but I'm hesitant coz now I have to start from scratch again after that(?). :/
http://forum.xda-developers.com/showthread.php?t=648864
Click to expand...
Click to collapse
You should be able to flash an official HTC ROM, without ROOT. Although if you are operator locked ie T-Mobile/Vodafone etc you may have to install one of their ROMS. Although I'm a little out of my depth/comfort zone with all this...
I may be well off the mark here, but, have you tried it, without your SD card inserted? give it a go?
What you found is related to something different. and related to image files stored on your SD card used for updating....which is what made me make the above suggestion.
After a factory reset you will have to start a fresh anyway.
Ohh. So it's not related.
My phone looks like this :
SAGA PVT SHIP S-ON RL
HBOOT-0. 98. 0000
RADIO-38. 03. 02. 15_M
e-MMC-boot
Mar 10 2011, 14:58: 38
HBOOT
vol <up>......
vol <down>......
POWER
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
Click to expand...
Click to collapse
FASTBOOT goes to BOOTLOADER menu which shows me the "No image..."
RECOVERY works but then after the process it turns off, and vibrate several times.
FACTORY RESET if selected, nothing happens, like it froze or something.
Did you try it without an SD as suggested?
The IMAGE errors I think (but could be wrong) are as a result of FASTBOOT auto checking for the existence of update files on your SD and simply not finding any!
Does it say Checking.....
If you select FASTBOOT then REBOOT what happens? Phone hangs? with what screen?
Hopefully someone else will add some advice soon?
ben_pyett said:
Did you try it without an SD as suggested?
The IMAGE errors I think (but could be wrong) are as a result of FASTBOOT auto checking for the existence of update files on your SD and simply not finding any!
Does it say Checking.....
If you select FASTBOOT then REBOOT what happens? Phone hangs? with what screen?
Hopefully someone else will add some advice soon?
Click to expand...
Click to collapse
Yes, I did. It's same.
If I put the SD in it, when chosing FASTBOOT the errors looks like the attachment in this topic : http://forum.xda-developers.com/showthread.php?t=703761
Yes it say Checking...
Doing FASTBOOT then REBOOT shuts down the phone then restarts it and hangs at the green HTC logo.
I really wish someone can help me.
BTW, regarding the ROM's you provided above, what do you suggest is the one for me? I really don;t have any idea. I'm from Asia (Philippines) and phone is not locked by a mobile carrier.
MarlX said:
Regarding the ROM's you provided above, what do you suggest is the one for me? I really don;t have any idea. I'm from Asia (Philippines) and phone is not locked by a mobile carrier.
Click to expand...
Click to collapse
I've found a very similar sounding problem experienced by another user in this thread
I'm afraid that I don't know which of those ROMS would be best for you, I imagine one of the HTC ones, sorry....
Ensure that you continue to keep charging your device. Now, I'm grasping at straws now, but have you tried the above without a SIM inserted?
Same problem
I had the same problem much times!
I had to Factory Reset my phone every time it freezes!
When i did a factory reset, it was all ok until it appeared again
The only solution i found was to factory reset the phone..
ben_pyett said:
I've found a very similar sounding problem experienced by another user in this thread
I'm afraid that I don't know which of those ROMS would be best for you, I imagine one of the HTC ones, sorry....
Ensure that you continue to keep charging your device. Now, I'm grasping at straws now, but have you tried the above without a SIM inserted?
Click to expand...
Click to collapse
Yes, I also did that. Unfortunate, nothing happens, if it does not froze it boots to that green HTC logo and stops there.
I guess the only solution is to bring this to the store where I purchased it.
ben_pyett said:
I've found a very similar sounding problem experienced by another user in this thread
I'm afraid that I don't know which of those ROMS would be best for you, I imagine one of the HTC ones, sorry....
Ensure that you continue to keep charging your device. Now, I'm grasping at straws now, but have you tried the above without a SIM inserted?
Click to expand...
Click to collapse
Yes, I also did that. Unfortunate, nothing happens, if it does not froze it boots to that green HTC logo and stops there.
I guess the only solution is to bring this to the store where I purchased it.
MarlX said:
I guess the only solution is to bring this to the store where I purchased it.
Click to expand...
Click to collapse
Did you read the very similar sounding thread that I found http://forum.xda-developers.com/showthread.php?t=1107016&highlight=boot? unfortunately this is what that person ended up doing
If someone can advise which ROM would be the best for you to select then I'd possibly try that before returning it?
Good luck...
I've seen another user @Skanob also from the Phillipines, if you look at the details within his signature in the following post http://forum.xda-developers.com/showpost.php?p=14748687&postcount=4 you should see details of the RUU ROM that you can/should try to flash.
I am actually downloading it now.
Hope this will fix it.
This will not void the warranty, right? Coz I'm gonna bring the phone to the service center later (it's 12.30AM here atm).
MarlX said:
I am actually downloading it now.
Hope this will fix it.
This will not void the warranty, right? Coz I'm gonna bring the phone to the service center later (it's 12.30AM here atm).
Click to expand...
Click to collapse
I'll be perfectly honest, I don't know if this voids warranty....sorry..
Ultimately, you're only putting back the same ROM as the phone has on it originally, but, bear in mind that in the other thread I posted above, re-flashing the original ROM didn't resolve the issue, so if there's any doubt that this might void the warranty - don't do it!
MarlX said:
I am actually downloading it now.
Hope this will fix it.
This will not void the warranty, right? Coz I'm gonna bring the phone to the service center later (it's 12.30AM here atm).
Click to expand...
Click to collapse
Flashing RUU won't void the warranty. How long are you waiting on the htc logo screen? It can take a while after factory reset...
It might be that some files were corrupted so flashing RUU should help. If not, connect your device to computer and see what logcat is showing
Sent from my HTC Desire S using XDA App
The longest was 25 minutes, then had it reboot again coz nothing happened. Also, when doing the Factory Reset it just hangs/do nothing, can't choose any option from the menu, have to remove the battery to turn the device off.
I'm gonna bring the phone to the service center in a while.
I think I put myself in a bad situation here...
I spent all day trying to figure out how to root my 5 week old Nexus as it's tethering ability is my only access to the web.
So - step one, I did the one-click method, as the instructions I was finding for "the long way" were written by people who know what they're doing FOR people who know what they're doing.
Once that was accomplished, I downloaded Rom Manager. Unfortunately Rom Manager didn't seem to want to work with One-Click's style of rooting, locking me on the boot screen every time I tried using it.
So, I finally worked out how to root my phone the "normal" way and Rom Manager was working.
Here's where my mistake came in... I was one part frustrated from how long it took me to figure it all out, one part elated that I finally DID figure it out, so I immediately put Cyanogenmod on my phone... without backing it up. I played with it a bit, but realized my mistake, so downloaded the 2.3.3 Stock Rom.
That totally futzed things up for me... First, my USB connection isn't working anymore. The USB cable still powers my phone, and the USB ports on my PC still work, but I can't get a phone to pc connection through USB anymore.
Second, my cell radio isn't working anymore, I can only get anything over wifi. The OTA 2.3.4 update was pushed and installed to me that way (The current version my phone is on now...)
Third, apparently my phone was no longer rooted, so Rom Manager wouldn't work anymore for me. When I go to the bootloader menu and try to Recover, it brings me to an android with a triangle and exclamation point symbol.
Once there, some trial and error brought up a menu that I'd hoped would have let me reroot or reinstall a working Rom, but every one I try gives me a Signature Verification error and aborts the install...
So, I'm stuck... Without my USB connection working, I can reroot my phone, and without rerooting, I can't get a working ROM back in place. If ANYBODY can help me with this, it will be greatly appreciated. If any additional information is needed, I'll do my best to give it. Thank you...
Who is your carrier? Need to know which phone you have.
Also I assume that since you said you rooted the hard way eventually, that means you successfully used Fastboot to unlock your bootloader, yes?
The Android with exclamation point is just the stock Android recovery partition.
The key to fixing your problem will be to get USB connection between phone and PC.
Please plug in your phone to USB connected to your computer, then put your phone into Bootloader mode (Power on while holding Volume Up). On your computer, open a command prompt window and type "fastboot devices" and post what it says.
Can you see the phone in fast boot by usb also have you course factory reset and then try to flash
Sent from my Nexus S 4G using Tapatalk
The big problem is that I'm unable to make a USB connection anymore. My phone is not reading any kind of connection to allow for file transfers or debugging, but it still powers the phone.
TBoarder said:
The big problem is that I'm unable to make a USB connection anymore. My phone is not reading any kind of connection to allow for file transfers or debugging, but it still powers the phone.
Click to expand...
Click to collapse
Can you answer my question about fastboot? I want to help you.
matt2053 said:
Who is your carrier? Need to know which phone you have.
Also I assume that since you said you rooted the hard way eventually, that means you successfully used Fastboot to unlock your bootloader, yes?
The Android with exclamation point is just the stock Android recovery partition.
The key to fixing your problem will be to get USB connection between phone and PC.
Please plug in your phone to USB connected to your computer, then put your phone into Bootloader mode (Power on while holding Volume Up). On your computer, open a command prompt window and type "fastboot devices" and post what it says.
Click to expand...
Click to collapse
I did that and nothing came up.
TBoarder said:
I did that and nothing came up.
Click to expand...
Click to collapse
ok can you please install PDAnet on your computer?
http://junefabrics.com/android/download.php
This will ensure the proper must up to date drivers are installed for you. This is the best and most reliable way to get the correct drivers.
EDIT: Then try fastboot again and tell me the output for "fastboot devices"
matt2053 said:
ok can you please install PDAnet on your computer?
This will ensure the proper must up to date drivers are installed for you. This is the best and most reliable way to get the correct drivers.
EDIT: Then try fastboot again and tell me the output for "fastboot devices"
Click to expand...
Click to collapse
It was already installed, but I reinstalled it. I got to the end of the process where it asked me to go into USB Debugging mode and won't finish the install because it's not reading the USB connection.
(Sorry for any delays here... Being a newbie, I have a 5 minute delay between when I can post)
No worries, thanks for trying. If you have hardware failure you might be out of luck. USB connection is pretty crucial for this stuff.
Maybe you can try Odin. See here: http://forum.xda-developers.com/showthread.php?t=947950
matt2053 said:
No worries, thanks for trying. If you have hardware failure you might be out of luck. USB connection is pretty crucial for this stuff.
Maybe you can try Odin. See here:
Click to expand...
Click to collapse
I've been looking into Odin, to see if there's a way I can do it just by pushing the files I need to my phone's sdcard and going into recovery mode. Not looking likely, but I'll read through the thread you linked me and maybe something will pop up. Thank you...
On the plus side, I just contacted Sprint and I *might* be able to get my phone replaced... Much as I'd like to troubleshoot this myself, it's looking like my only option. Too bad getting a phone replaced this early in a contract, just out of the warranty period is a total pain in the neck...
TBoarder said:
I've been looking into Odin, to see if there's a way I can do it just by pushing the files I need to my phone's sdcard and going into recovery mode. Not looking likely, but I'll read through the thread you linked me and maybe something will pop up. Thank you...
On the plus side, I just contacted Sprint and I *might* be able to get my phone replaced... Much as I'd like to troubleshoot this myself, it's looking like my only option. Too bad getting a phone replaced this early in a contract, just out of the warranty period is a total pain in the neck...
Click to expand...
Click to collapse
Can you post a link to the stock image you installed?
Was there ever a 2.3.3 for the nexus s 4g? Seems like it shipped with 2.3.4
Sent from my SPH-P100 using XDA App
matt2053 said:
Can you post a link to the stock image you installed?
Click to expand...
Click to collapse
It was downloaded through ROM Manager.
And yes, if I could get back into ROM Manager, I'd warn people NOT to flash their ROM to that. Bad mojo there.
My suggestion is to try and use Odin to flash it back to stock, I don't think Odin needs any drivers to see the phone...
Sent from my Nexus S 4G using XDA Premium App
TBoarder said:
It was downloaded through ROM Manager.
And yes, if I could get back into ROM Manager, I'd warn people NOT to flash their ROM to that. Bad mojo there.
Click to expand...
Click to collapse
Yeah see the thing is there is no 2.3.3 for NS4G. If you flashed 2.3.3 that means you flashed a GSM Rom on your CDMA phone. Oops! not the first time it has happened I'm sure.
Sent from my Nexus S using XDA App
Which totally explains what went wrong... Wow. ROM Manager, I though, was supposed to only bring up ROMs that are compatible with your phone model. Any way somebody can either let the developer know about this, or at the very least put a comment in the 2.3.3 ROM that specifically says it won't work with Sprint's network? That way nobody else will go through the hell I put myself through...
I'm wondering, could the USB connection issue be connected, like the "program" that controls that is integrated with the radio? Just curious, is all. Thanks again for your help!
How did you find astock 233 rom in rom manager, I only see cyanogen nighties oxygen, peter alphonso, extras etc everything is for the nexus a 4g
Sent from my Nexus S 4G using Tapatalk
TBoarder said:
Which totally explains what went wrong... Wow. ROM Manager, I though, was supposed to only bring up ROMs that are compatible with your phone model. Any way somebody can either let the developer know about this, or at the very least put a comment in the 2.3.3 ROM that specifically says it won't work with Sprint's network? That way nobody else will go through the hell I put myself through...
I'm wondering, could the USB connection issue be connected, like the "program" that controls that is integrated with the radio? Just curious, is all. Thanks again for your help!
Click to expand...
Click to collapse
Yeah. I have the T-Mobile version. When I download through Rom Manager I get a popup that says "select your phone model" or something similar and then two choices: "Nexus S" or "Nexus S 4G". It would be really easy to mess that up.
The good news is that I believe your phone can still be recovered, you're definitely not the first person with this exact issue, and at worst, it sounds like you have a Sprint rep who is willing to work with you. I think Odin is your only chance for a software solution. I can't walk you through Odin though, because I've never used it myself.
Let me know what happens.
Sent from my Nexus S using XDA App
matt2053 said:
Let me know what happens.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I just got my warranty replacement phone due to an abnormally long backorder. Thank you very much for your help (And well, I would've more appreciated it if you hadn't shown me that the problem was all my fault... ). Being my only phone and being poor, I won't be trying to root again, no matter what I learned from this problem. Anyway, thanks again, the help was, in all seriousness, greatly appreciated.
I was one of the unlucky testers before Steve0007 closed the thread. Did anyone figure out how to save our Sensation after the bad flash? My phone does not light up or respond to any button presses but when plugged into the computer it is recognized as an "unrecognized device."
I guess this is the risk we run being early testers. Hopefully someone figures it out otherwise I've got myself very expensive paper weight.
I assume no two button rescue? And this should be in q/a or general
Can you get to the bootloader?
Sent from my Sensation using xda premium
what did he brick people's phones with what was it supposed to be?
Wrong section. And that happened to me when i got an hd2 and i bricked it. Luckily it was 2 days after i bought it so tmobile gave me another because they thought something was wrong with it. But next time please post in the right section. Thanks.
nba1341 said:
what did he brick people's phones with what was it supposed to be?
Click to expand...
Click to collapse
Its probably only a soft brick
Sent from my Sensation using xda premium
Thank god I didn't flash it, I just finished downloading it when people started reporting issues.
Anyway, I'm sure he didn't mean for it to happen. If you have a spare battery, have you tried putting that one in?
These things are usually flash at your own risk.
I would never flash a ruu, unless it's official it could cause problems.
Sent from my Sensation using Tapatalk
Also, if it doesnt work and if you have tmo. Tell them bs and they will get you one. Just some advice and please dont flame me.
tried spare battery. same result. And i'm sure he didn't do it maliciously I've flashed many of his things before with no problem. Just hoping to get some help. Phone doesn't respond. Can't get to bootloader. Only sign of life is windows recognizing that i plugged something into the usb slot.
Yes as I said, this happened to me exactly when i had a tmo HD2 and flashed a european ruu and it was dead. I tried everything. You will have better luck to talk to your insurance company.
Have you got ADB installed on your pc? If not start downloading and installing it. I will find some links, in just a sec.
Edit:
New to ADB CLICK HER
More to set up path CLICK HERE
http://www.mediafire.com/?rrwi4f258lie1r7
Extract to system 32 or sysWOW64 (64bit)
Try 3 finger salute (VOL UP,VOL DOWN + POWER) with your phone plugged into pc and pc volume up see if it makes a sound like a device has connected.
Whats was this RUU anyway?
if you just need ADB you dont need all of the stuff above or to set up a path if its extracted to those folders
duychau said:
tried spare battery. same result. And i'm sure he didn't do it maliciously I've flashed many of his things before with no problem. Just hoping to get some help. Phone doesn't respond. Can't get to bootloader. Only sign of life is windows recognizing that i plugged something into the usb slot.
Click to expand...
Click to collapse
This is excatly what happened to me.Computer wont see the phone though,so no adb fix can be applied.Mnn i'm so pissed as i dont have insurance.
usually blagging HTC will do the trick for a repair,dont mention XDA, ROOT, ICS or basically anything except your phone said update was available and the battery died
Click to expand...
Click to collapse
roflcopter is 10chars
duychau said:
tried spare battery. same result. And i'm sure he didn't do it maliciously I've flashed many of his things before with no problem. Just hoping to get some help. Phone doesn't respond. Can't get to bootloader. Only sign of life is windows recognizing that i plugged something into the usb slot.
Click to expand...
Click to collapse
What does it recognize it as?
unrecognized usb device
Ok guys, it looks like the firmware that I posted to another thread from 3.06 bricked few devices. I have flashed it and it worked fine, so i tried again with the package i posted and indeed it is corrupted as it bricked also mine
My device does not respond, so I would think it is dead
I feel sorry for those who have bricked also theirs based on the package i posted.
I am closing my Rom thread and starting now my Rom developments will be for my own use. I will not publish anymore my work.
Again I feel sorry for those who have lost their devices.
Steve
ok so now his rom thread is closed. Why not keep it open and work together to help those with bricked devices attempt to restore them to a working state?
That way you keep your reputation rather than running away after bricking devices?
Arrrggghhhh,This could not have come at a worse time
nba1341 said:
ok so now his rom thread is closed. Why not keep it open and work together to help those with bricked devices attempt to restore them to a working state?
That way you keep your reputation rather than running away after bricking devices?
Click to expand...
Click to collapse
Because as far as I know no way to get them back
Ive been rooted and have been flashing different mods to tests them out to find whats best for me... Now Im stuck without a working phone. The only thing that I have done different since I last flashed a Rom was Do a factory reset with the PG58diag file to SIM Unlock. Phone worked fine when I restated and restored my backup... Thats when I decided to try the ARHD 667xe Rom. it Installed complete but never rebooted after that. Battery was at about 38% when I flashed. PLEASE HELP
Elrickg80 said:
Ive been rooted and have been flashing different mods to tests them out to find whats best for me... Now Im stuck without a working phone. The only thing that I have done different since I last flashed a Rom was Do a factory reset with the PG58diag file to SIM Unlock. Phone worked fine when I restated and restored my backup... Thats when I decided to try the ARHD 667xe Rom. it Installed complete but never rebooted after that. Battery was at about 38% when I flashed. PLEASE HELP
Click to expand...
Click to collapse
Do you have access to the bootloader or the recovery?
Do you see the LED when charging the phone?
That is a Negative to both Q's!...
I notice my computer locates it but will not load drivers nor charge,... device manager shows it as "QHSUSB_DLOAD" device.
Thats all I got so far!
Thx for REplying
Elrickg80 said:
That is a Negative to both Q's!...
I notice my computer locates it but will not load drivers nor charge,... device manager shows it as "QHSUSB_DLOAD" device.
Thats all I got so far!
Thx for REplying
Click to expand...
Click to collapse
Hi,
Try posting HERE
Happen to have finally found that post searching all dayand looking thru it now, but thank you for being there. let you know how it works out for me. thx again
Ive been trying the unbrick method all day with diff linux systems, on 1st script I get..."The bricked device is on" ...Use the above node to perform operations using the emmc_recover tool". with NO feedback....
1.Would flashing the ARHD6 XE on my Tmobile Sensation 4g be the cause of the brick?
2. Would I have to us the Sensation XE package to unbrick instead of Sensation 4g if that were the case.
unbrick guide is Great, just need to know where I may be going wrong!
thx
One possible reason is your battery you mention that youre battery was 38% charged when you flashed. It may haved dropped during flashing and you might didnt notice the flash method did not finish properly.
Lesson here is do not flash rom if youre battery is lower than 50% coz you wouldnt know what will happen. For safe flashing make sure you are fully charged.
Hope you recover phone coz it looks like it will be recovered using the method posted by malybru.
Elrickg80 said:
Ive been trying the unbrick method all day with diff linux systems, on 1st script I get..."The bricked device is on" ...Use the above node to perform operations using the emmc_recover tool". with NO feedback....
1.Would flashing the ARHD6 XE on my Tmobile Sensation 4g be the cause of the brick?
2. Would I have to us the Sensation XE package to unbrick instead of Sensation 4g if that were the case.
unbrick guide is Great, just need to know where I may be going wrong!
thx
Click to expand...
Click to collapse
Hi,
I do not know enough about this to comment.
Are you unable to post in that thread?
@darkmantra, Thx for the advice Ill keep that in mind from now on. But I did get to see the flash come to a complete finish and hit restart on 4ext, during the reboot is when things went dark. hope I do get it going tho, thx!
@Malybru, I found that thread hours after posting this thread, I can C&P to that thread if that's whats best... But the issue I have is as partially described here.
I have Tmobile Sensation 4G
1. Did factory reset with PG58DIAG file to SIM UNLOCK .1111111
2. Backup Recovery
3. decided to try new Rom, ARHD6 XE with beats (not sure if meant for TMO Sen 4G)
4.flash completed, went black on reboot
5. Computer now see it as QHSUSB_DLOAD
6.Used Ubunto8 & Knoppix to run script ./brickdetect.sh.... "No return" script reply
7. now the PHtoolz live CD, but "file not in Directory" when clearly in Home/Ubuntu folder
ANY ADVICE!!?
Elrickg80 said:
@darkmantra, Thx for the advice Ill keep that in mind from now on. But I did get to see the flash come to a complete finish and hit restart on 4ext, during the reboot is when things went dark. hope I do get it going tho, thx!
@Malybru, I found that thread hours after posting this thread, I can C&P to that thread if that's whats best... But the issue I have is as partially described here.
I have Tmobile Sensation 4G
1. Did factory reset with PG58DIAG file to SIM UNLOCK .1111111
2. Backup Recovery
3. decided to try new Rom, ARHD6 XE with beats (not sure if meant for TMO Sen 4G)
4.flash completed, went black on reboot
5. Computer now see it as QHSUSB_DLOAD
6.Used Ubunto8 & Knoppix to run script ./brickdetect.sh.... "No return" script reply
7. now the PHtoolz live CD, but "file not in Directory" when clearly in Home/Ubuntu folder
ANY ADVICE!!?
Click to expand...
Click to collapse
Hi,
If you copy/paste your problem into that thread,you will increase your chances of someone being able to help you.
I tried, But since I dont have enough membership rating or comments its not letting me post to that threat.
Think I may be going for A TMOBILE warranty replacement...... Any doubts i may be out of warranty once they get it??
Elrickg80 said:
I tried, But since I dont have enough membership rating or comments its not letting me post to that threat.
Think I may be going for A TMOBILE warranty replacement...... Any doubts i may be out of warranty once they get it??
Click to expand...
Click to collapse
Make 4 more posts and youll be able yo post in that thread
Sent from my sensational sensation 4g
You have lost your boot.IMG that's why it won't boot and as for it not charging take look at your recovery if your not using 4ext as the recovery then you should be this will solve your charging problem
sent from xda premium:sensation4g Insertcoin Ics Evolution v2.0 Sense 4.0 kernel version Bricked-3.0-v1.1
Hi All!
Recently i flashed TWRP and Cynogenmod 10.2.1 stable to my HTC Telestra One XL (evita)
I unlocked boot-loader
I successfully rooted
But I shut down once, and when i tried to boot, it got stuck in a boot-loop
Upon many retries, it suddenly wont turn on
when I charge it it only has a flashing red light but it wont even turn on, no screen not buttons; nothing!
And if I plug it in to my PC, the pc keeps sounding the USB Connected sound multiple times over a short period of 30 seconds to 2 minutes and then it gives off multiple shaky beeps
I hope this is enough info to let anyone help out!
Thank You in Advance
EDIT:
when connected to a pc it shows drivers is ready to use but tries to install QHUSB_DLOAD but fails and latest RUU does not detect
Thx again
What is the exact full filename of the ROM zip that you flashed? When a device is showing up as QHSUSB_DLOAD in Windows it usually means it's bricked.
Sent from my Evita
timmaaa said:
What is the exact full filename of the ROM zip that you flashed? When a device is showing up as QHSUSB_DLOAD in Windows it usually means it's bricked.
Sent from my Evita
Click to expand...
Click to collapse
Just found out:
a friend of mine tried to flash a file named "cm-10.0.0-evita" and it gave off a message saying that this phone is not rooted or missing supersu/ something along those lines
before that he wiped sd card (whole thing)...
and then it went off from there
NOTE: its a phone with mess with, but still want to fix even though its just a side phone we barely use....help appreciated
So does it power on at all?
Sent from my Evita
timmaaa said:
So does it power on at all?
Sent from my Evita
Click to expand...
Click to collapse
nope
when plugged in it only has a red LED that flashes once every once in a while and thats it
pc recognises it but wants to install qhusb_dload (as mentioned) and it just sais no driver found
i am researching and i found something called a "RIFF Box" but unsure if its worth it, plus i dont know where to jtag it (if its possible at all)
PS: hi from sydney!
Al-Dazzlez said:
Just found out:
a friend of mine tried to flash a file named "cm-10.0.0-evita" and it gave off a message saying that this phone is not rooted or missing supersu/ something along those lines
before that he wiped sd card (whole thing)...
and then it went off from there
NOTE: its a phone with mess with, but still want to fix even though its just a side phone we barely use....help appreciated
Click to expand...
Click to collapse
How did he try to flash it -_- these vague responses make it very hard to help. Bottom line is you can try pressing and holding power until the light goes off and then power and volume down to get the bootloader up, if that doesn't work you can try the evita jet tool to try to unbrick it. Bricks such as yours are not recoverable 9 times out of 10.
It looks like your only option is to get a jtag repair done. I wouldn't bother trying to do it yourself unless you're a fully experienced electronic engineer or the like. I'm not sure how many jtag repairers there are in Australia but I'm guessing Google should be able to reveal that information. Howdy from Melbourne.
Sent from my Evita
Hi from Canada!... I just wanted to be part of the greetings.. :laugh:
exad said:
How did he try to flash it -_- these vague responses make it very hard to help. Bottom line is you can try pressing and holding power until the light goes off and then power and volume down to get the bootloader up, if that doesn't work you can try the evita jet tool to try to unbrick it. Bricks such as yours are not recoverable 9 times out of 10.
Click to expand...
Click to collapse
he placed the cyanogen mod on the phones sd card, then he wiped sd card, after that he used the install function on twrp it gave him a message that his phone is not rooted and if he would like to root it, he accepted, then it rebooted into twrp, and he tried again to install, same message appeared and then he gave up and shut it down...(sorry for vague terms, please bear with me, still trying to learn the ropes of talking on this forum)
I gotta say, this is all very odd :/ How did he install anything if he wiped the SD card after copying it over? :/ hmmmm In any case, you CAN try he jet tool as per my last post before getting a jtag. You'll need a linux install or Bootable USB stick/CD/DVD though.
My guess is that the only thing he installed was SuperSU. That'd be why it booted straight back into TWRP.
Sent from my Evita
timmaaa said:
It looks like your only option is to get a jtag repair done. I wouldn't bother trying to do it yourself unless you're a fully experienced electronic engineer or the like. I'm not sure how many jtag repairers there are in Australia but I'm guessing Google should be able to reveal that information. Howdy from Melbourne.
Sent from my Evita
Click to expand...
Click to collapse
i researched..nothing..just some videos of people who do it (jtag)in the US and US only......
but still asking 'round the shops wont hurt i guess:laugh:
ill keep ya posted about using that tool you mentioned!
and exad; SUP!
and yeah.. it sounds weird to me too but i mainly play around with stuff like the galaxy series samsung's so the htc stuff is still new...and i have to admit...i am hating it so far.... but still experience cant hurt :laugh:
Hi guys!
im back
I JTAG'd the phone overseas, and it came back, surely enough, working, but now another problem arises,
the guy apparently unlocked the bootloader, S-Off, and installed CM with android 4.3.1. the phone boots, everything is well, but for times from 10 seconds to minutes of usage it just turns off, the Hboot shows
***tampered***
***relocked***
any idea wth is wrong with it now?
it does not reboot from power menu, and does not do anything really since I cant keep it on for more than a few minutes at most. I cannot keep it on long enough to unlock the bootlaoder anymore, and I cannot boot into TWRP (as the guy told me he put it on)
da hell do I Do now? any help appreciated
Try an RUU, any Evita RUU is fine if you have s-off.
Sent from my Evita
timmaaa said:
Try an RUU, any Evita RUU is fine if you have s-off.
Sent from my Evita
Click to expand...
Click to collapse
Thank you, tried but it did not pick up, but:
UPDATE:
I booted into teamwin, and flashed a CM11snapshot (latest one) everything seems fine so far (after 20 million dalvik and cache and factory restores) but now i am waiting for the problem to arise again, if not, ill have one problem left to fix....the back button does not work....
and now how the hell do i use an RUU on a custom frimware, ? (used it once on this phone but using a stock rom)
thanks again for your time timmaaa, seriously appreciated
Al-Dazzlez said:
Thank you, tried but it did not pick up, but:
UPDATE:
I booted into teamwin, and flashed a CM11snapshot (latest one) everything seems fine so far (after 20 million dalvik and cache and factory restores) but now i am waiting for the problem to arise again, if not, ill have one problem left to fix....the back button does not work....
and now how the hell do i use an RUU on a custom frimware, ? (used it once on this phone but using a stock rom)
thanks again for your time timmaaa, seriously appreciated
Click to expand...
Click to collapse
There's only one way to run an RUU, and that's to connect your phone and initiate the program in Windows. You're s-off so all security checks are disabled.
Sent from my Evita
timmaaa said:
There's only one way to run an RUU, and that's to connect your phone and initiate the program in Windows. You're s-off so all security checks are disabled.
Sent from my Evita
Click to expand...
Click to collapse
I Just ran one, Unlocked bootloader, on Cm11 snapshot after re-root and all that crap done, should be alright now