Hi guys,
I have my 32B Vodafone Spain USB Bricked, and now there may be a chance of de-bricking it, by flashing a good known misc.img flash image. You can see more info over here, although this is for the HTC Desire, I know a case of an HTC Magic that worked: http://forum.xda-developers.com/showthread.php?t=691639.
The problem is that I don't have a good known misc.img file from a 32B Vodafone Spain...
Is there anyone that can get me a dump of the misc.img from a 32B Vodafone Spain with working usb? Its quite easy to get a dump of the misc partition, just open a terminal and do the following:
Code:
su
cat /dev/mtd/mtd0 > /sdcard/misc.img
Cheers
skhell said:
Hi guys,
I have my 32B Vodafone Spain USB Bricked, and now there may be a chance of de-bricking it, by flashing a good known misc.img flash image. You can see more info over here, although this is for the HTC Desire, I know a case of an HTC Magic that worked: http://forum.xda-developers.com/showthread.php?t=691639.
The problem is that I don't have a good known misc.img file from a 32B Vodafone Spain...
Is there anyone that can get me a dump of the misc.img from a 32B Vodafone Spain with working usb? Its quite easy to get a dump of the misc partition, just open a terminal and do the following:
Code:
su
cat /dev/mtd/mtd0 > /sdcard/misc.img
Cheers
Click to expand...
Click to collapse
So let's get this straight... a "brick" is a device that cannot get to bootloader and cannot get to recovery. The phone will not boot and you cannot get the device to show up on your computer. Right?
So how do you flash a misc.img without a computer or recovery?
My bad, I explained bad. It's "USB bricked", the phone is working correctly, but can't use the USB, only can use it in fastboot mode...
No one? There's no one here with a rooted Vodafone Spain HTC Magic?
Looks like none, I found this thread later yesterday and tried the cmd above. I opened the img dump in a hex editor and it looked like a blank 256kb img. Half the file were 0s and the last half were Fs.
Fly1nP4nda said:
Looks like none, I found this thread later yesterday and tried the cmd above. I opened the img dump in a hex editor and it looked like a blank 256kb img. Half the file were 0s and the last half were Fs.
Click to expand...
Click to collapse
That is weird, it really should be a 256kb file, with the beginning of the file with some info(not much) and then the 0s and the Fs
In attachment there is a misc.img from a Vodafone Germany 32B, in the first bytes there is the CID: VODAP102, then some more bytes ahead(not much) there is something which some say is the "rom version" 1.89.162.1... I tried to flash this file in my phone, and it kept the same ...
Yeah I tried to do the same with images I found on the htc desire thread, except I replaced the CID with my t-mobile cid and compared them via a hex editor. I didn't mess with the rom version as they mentioned the difference in rom versions didn't seem to matter.
However I did regain sdcard functionality when I flashed using the image from the htc desire thread.
Fly1nP4nda said:
Yeah I tried to do the same with images I found on the htc desire thread, except I replaced the CID with my t-mobile cid and compared them via a hex editor. I didn't mess with the rom version as they mentioned the difference in rom versions didn't seem to matter.
However I did regain sdcard functionality when I flashed using the image from the htc desire thread.
Click to expand...
Click to collapse
How about usb functionality, did you regained that too? Also, how did you managed to flash the desire image, its bigger than 256kb. Did you get any error while flashing the image?
No usb functionality, it gave me an error with no space left ... but somehow my sdcard regained functionality. Each time I switch roms I lose my sdcard, I flash with that image I regain sdcard functionality.
I also tried the germany image as well since it is 256kb, changed the CID to match mine. USB still doesn't work but when I dump the image now ( cat /dev/mtd/mtd0 > /sdcard/misc.img ) I get the exact image I put in so no errors in flashing. I'm going to study this some more a bit later.
Fly1nP4nda said:
Each time I switch roms I lose my sdcard, I flash with that image I regain sdcard functionality.
Click to expand...
Click to collapse
That's really weird , never happened to me.
using cat /proc/cmdline
I get
board_sapphire.disable_uart3=0
board_sapphire.usb_h2w_sw=0
which I believe should be correct? I read somewhere else thats what it should be I think http://forum.xda-developers.com/showthread.php?t=691639
If that is what it should be... I still don't have USB function and the phone only charges when off or my cable is just busted.
Fly1nP4nda said:
using cat /proc/cmdline
I get
board_sapphire.disable_uart3=0
board_sapphire.usb_h2w_sw=0
which I believe should be correct? I read somewhere else thats what it should be I think http://forum.xda-developers.com/showthread.php?t=691639
Click to expand...
Click to collapse
I have the same. I have looked at a friends HTC Magic and its the same, so I guess it is correct.
Fly1nP4nda said:
If that is what it should be... I still don't have USB function and the phone only charges when off or my cable is just busted.
Click to expand...
Click to collapse
Actually I can charge my phone when its on, but I also have a curious situation. While charging, if I go to Settings->About Phone->Status, the Battery Status always says "Charging (AC)", even if I am charging it using a USB port of a computer. I have a friend with a HTC Magic with proper working usb, and it says something like "Charging(usb)"... I guess this could also be related the problem...
Hmm, so your usb brick is just not be able to mount your phone onto your computer?
The details on my brick, although I'm starting to think it could be a borked port or something now.
I stopped by the T-mobile store and asked for a cable to test and see if it was the cable and nothing happened.
My phone does not charge when on, or at least does not appear to be charging. The battery indicator does not change and the status in the settings is not connected always. The phone only charges when off, I found this out when my usb just randomly went out and my phone died and I just turned it back on hrs later while on the charger.
I'm unable to use fastboot/adb via usb which was frustrating because while attempting to fix the usb I lost my sdcard functionality. However I have that back now and all I am left is with the broken usb.
I'm currently using the MISC img that was attached to your post with my modified CID, however I don't know how to get my ROM version. Do you or someone know how to get that info? I've been searching up and down the forums for the right info, although it was mentioned that it didn't seem to matter if it was different.
Fly1nP4nda said:
Hmm, so your usb brick is just not be able to mount your phone onto your computer?
Click to expand...
Click to collapse
Yeah, that's right, I am able to charge it and use it with fastboot, Just can't mount it or use it with adb.
Fly1nP4nda said:
The details on my brick, although I'm starting to think it could be a borked port or something now.
I stopped by the T-mobile store and asked for a cable to test and see if it was the cable and nothing happened.
My phone does not charge when on, or at least does not appear to be charging. The battery indicator does not change and the status in the settings is not connected always. The phone only charges when off, I found this out when my usb just randomly went out and my phone died and I just turned it back on hrs later while on the charger.
I'm unable to use fastboot/adb via usb which was frustrating because while attempting to fix the usb I lost my sdcard functionality. However I have that back now and all I am left is with the broken usb.
I'm currently using the MISC img that was attached to your post with my modified CID, however I don't know how to get my ROM version. Do you or someone know how to get that info? I've been searching up and down the forums for the right info, although it was mentioned that it didn't seem to matter if it was different.
Click to expand...
Click to collapse
I have the same questions about the ROM version, have no idea how to get it or if it can be anything else
up
hopping someone with good news see this
Here is the link to my mtd0 image. It's from a Vodafone 32A Magic from Greece. I don't know if this will help, but it doesn't hurt to try.
Thanks, will try it and see what happens
bump from the dead, any luck on this?
Nope, still USB dead, except in fastboot
skhell said:
Nope, still USB dead, except in fastboot
Click to expand...
Click to collapse
You can repair this phone but will a different kay mapping ...
Related
Anyone know how to change the ugly vodafone screen on the 32B Board? Im talking about the one before splash when you first turn it on?
"Change splash screen on HTC Magic" - http://ostebaronen.dk/?p=124
Tried that and all it says is failed all the time, Once it went through but didnt change feck all lol
EDIT: Done it god knows why it wouldnt work
Really?
I got a UK Vodafone Magic G2, i did this http://ostebaronen.dk/?p=124 and then i used these pictures http://ostebaronen.dk/android/splash/
Works like a charm on my phone, me 2 got pissed at the Red Vodafone screen.
so you have to have the phone rooted for this
I'm actually not sure whether you have to have a rooted phone for this. My guess is yes. You should try it with an unrooted phone though. And I am happy you could use my guide It is also in XDA's Wiki here: http://wiki.xda-developers.com/index.php?pagename=HTC_Sapphire_Hacking#sec08
my phones no rooted am to scared lol
ok ive got waiting for device now its doing nothing
make sure its loaded in fast boot.The easiet way i found to do it all was..windows key then search cmd,when it finds it copy.
Put all the neccessary files in one folder (android sdk fastboot etc) and paste the cmd window. When you run the cmd inside your folder full of stuff it starts tyhere so no need to change directories. I then followed the flashing procedure and voila new boot screen
Turn off you phone. Then when it is turned of hold the back button and then hold the end/power button along with it until it boots again. It will boot into fastboot mode.
in fast bootmode i notice i don't have the usb driver installed right cusae am using vista x64 so downloading the new andriod sdk with the signed vista 64 driver. ive never messed around with andriod before so wish me luck
comes up with remote sig failed
I'm actually not sure whether you have to have a rooted phone for this. My guess is yes. You should try it with an unrooted phone though.
Click to expand...
Click to collapse
OK, It definitely needs to be rooted as I've just tried without being rooted.
Incidentally
comes up with remote sig failed
Click to expand...
Click to collapse
this is the error you get when not rooted
so is it worth doing as far as a see i only need a engineer spl or hard spl what ever they are lol
scoobyturbo said:
so is it worth doing as far as a see i only need a engineer spl or hard spl what ever they are lol
Click to expand...
Click to collapse
If you follow the instructions provided here you can flash it in a manner that will root it.
Code:
http://forum.xda-developers.com/showthread.php?t=530492
thanks i will have a look
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.
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..
I've researched and researched, now I need help. I have an HTC Inspire 4G that crashed. Never rooted, never unlocked, I think something just went wrong and a critical OS file or two got corrupted. So I brought out my old Aria and am using that :crying: while I try to figure out how to restore my Inspire 4G.
I'm a programmer but never felt the need to root my phone. It was fine as is. Now I am willing to do what it takes to get this back. I scoured the internet and found out a lot, piecemeal and by accident. Here's what I have learned, found and done so far:
I know how to boot into the Bootloader. I tried Factory Reset to no avail. It simply boots to the HTC screen and sits there.
I've installed the Android SDK and have researched the ADB and FASTBOOT commands.
I have installed the Windows 7 64-bit drivers onto my Win8 64-bit PC. They seem to be installed correctly - the device shows up in the Device Manager when I connect the phone via USB - although I have to connect it first, then Reboot Bootloader, at which point it appears in Device Manager as INSPIRONWIN8\Android USB Devices\My HTC.
I've unlocked my phone using instructions from HTCDev.com. I have the Unlock_code.bin file for my phone.
I have the actual AT&T ROM for this phone in EXE form. I've run it successfully twice with the phone attached(I relocked first), but each time when I reboot the phone just freezes on the HTC screen or cycles between that and the AT&T startup animation.
I've also mounted the SD card into my computer, formatted it with FAT32 and put PD98IMG.zip on it. There's another DIAG file the phone complains about not finding -I've searched the net and I can't find it either. I go into recovery and try to reload the ROM from that (Apply update from SD Card) but that has not succeeded either. Formatting the cached, etc.... none of that has worked.
I am trying to run the ADB command on the phone but it cannot find the device. I was thinking I'd try to push the ROM to the phone that way, but so far no luck. The USB Universal Driver does not work at all, so I'm back to the Win7 64-bit driver.
Does anyone have any other suggestions? Maybe I have all the steps but haven't done them in the right order?
Any help, guidance or suggestions would be appreciated, thanks.
Barry
bimplebean said:
I've researched and researched, now I need help. I have an HTC Inspire 4G that crashed. Never rooted, never unlocked, I think something just went wrong and a critical OS file or two got corrupted. So I brought out my old Aria and am using that :crying: while I try to figure out how to restore my Inspire 4G.
I'm a programmer but never felt the need to root my phone. It was fine as is. Now I am willing to do what it takes to get this back. I scoured the internet and found out a lot, piecemeal and by accident. Here's what I have learned, found and done so far:
I know how to boot into the Bootloader. I tried Factory Reset to no avail. It simply boots to the HTC screen and sits there.
I've installed the Android SDK and have researched the ADB and FASTBOOT commands.
I have installed the Windows 7 64-bit drivers onto my Win8 64-bit PC. They seem to be installed correctly - the device shows up in the Device Manager when I connect the phone via USB - although I have to connect it first, then Reboot Bootloader, at which point it appears in Device Manager as INSPIRONWIN8\Android USB Devices\My HTC.
I've unlocked my phone using instructions from HTCDev.com. I have the Unlock_code.bin file for my phone.
I have the actual AT&T ROM for this phone in EXE form. I've run it successfully twice with the phone attached(I relocked first), but each time when I reboot the phone just freezes on the HTC screen or cycles between that and the AT&T startup animation.
I've also mounted the SD card into my computer, formatted it with FAT32 and put PD98IMG.zip on it. There's another DIAG file the phone complains about not finding -I've searched the net and I can't find it either. I go into recovery and try to reload the ROM from that (Apply update from SD Card) but that has not succeeded either. Formatting the cached, etc.... none of that has worked.
I am trying to run the ADB command on the phone but it cannot find the device. I was thinking I'd try to push the ROM to the phone that way, but so far no luck. The USB Universal Driver does not work at all, so I'm back to the Win7 64-bit driver.
Does anyone have any other suggestions? Maybe I have all the steps but haven't done them in the right order?
Any help, guidance or suggestions would be appreciated, thanks.
Barry
Click to expand...
Click to collapse
Barry, if you ran the RUU successfully and the phone got stuck in the splash screen (white one), that seems to be a fried emmc chip. That is quite usual in Ace devices (DHD / Inspire 4G).
glevitan said:
Barry, if you ran the RUU successfully and the phone got stuck in the splash screen (white one), that seems to be a fried emmc chip. That is quite usual in Ace devices (DHD / Inspire 4G).
Click to expand...
Click to collapse
Actually, I was able to flash the original 2.3.3 ROM last night using Fastboot. It took me a while to realize that since the OS was fried, ADB was useless - there was no 'android' to 'debug.' Consequently I used fastboot.exe to re-apply the PD98IMG.zip and it worked!
The old ROM is real smooth, so I may just keep it, but if I can figure out how to apply a newer build I will.
Thanks!
bimplebean said:
Actually, I was able to flash the original 2.3.3 ROM last night using Fastboot. It took me a while to realize that since the OS was fried, ADB was useless - there was no 'android' to 'debug.' Consequently I used fastboot.exe to re-apply the PD98IMG.zip and it worked!
The old ROM is real smooth, so I may just keep it, but if I can figure out how to apply a newer build I will.
Thanks!
Click to expand...
Click to collapse
you can run the RUU exe file from fastboot usb
glevitan said:
you can run the RUU exe file from fastboot usb
Click to expand...
Click to collapse
It's an EXE. How do I run that from fastboot?
bimplebean said:
It's an EXE. How do I run that from fastboot?
Click to expand...
Click to collapse
Just run the exe file with the phone plugged and in fastboot usb. That is how RUU's work
glevitan said:
Just run the exe file with the phone plugged and in fastboot usb. That is how RUU's work
Click to expand...
Click to collapse
Ah. Yes, I already did that, no luck. See above.
But never mind, as I said above I was able to flash the original 2.3.3. ROM using fastboot and it's working now. Everything else from here on out is just gravy.:laugh:
bimplebean said:
Ah. Yes, I already did that, no luck. See above.
But never mind, as I said above I was able to flash the original 2.3.3. ROM using fastboot and it's working now. Everything else from here on out is just gravy.:laugh:
Click to expand...
Click to collapse
That is weird...RUU should be working if your phones works fine. Anyway, if you are cool in this state, just let it be. :good:
glevitan said:
That is weird...RUU should be working if your phones works fine. Anyway, if you are cool in this state, just let it be. :good:
Click to expand...
Click to collapse
I REALLY should have taken your advice, but I fiddle around a bit and hosed the recovery loader.
I restored the phone again but it runs very slow and processes fail all the time. I can't run the RUU because it won't boot into the bootloader.
How do i restore the stock bootloader?
bimplebean said:
I REALLY should have taken your advice, but I fiddle around a bit and hosed the recovery loader.
I restored the phone again but it runs very slow and processes fail all the time. I can't run the RUU because it won't boot into the bootloader.
How do i restore the stock bootloader?
Click to expand...
Click to collapse
There is no "recovery loader," just "recovery" and "bootloader." Which doesn't work? What did you do exactly when you "fiddled" with it?
bananagranola said:
There is no "recovery loader," just "recovery" and "bootloader." Which doesn't work? What did you do exactly when you "fiddled" with it?
Click to expand...
Click to collapse
I apologize, this is not my strong suit. I've been through so many things I'm not sure I remember all the things I've tried. I think I tried flash the recovery with Ace Hack Kit.
Let me describe what I DO know.
I can boot in to Fastboot (Vol Down + Power)
Here's what it says:
ACE PVT SHIP S-ON RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.10.04.03_M
eMMC-boot
Apr 12 2011, 00:55:45
There is no LOCKED or UNLOCKED indicator at all.
I'd he happy with an RUU stock ROM, but when I try to re-run the RUU from my computer, the system tries to reboot the phone into the bootloader. This is when I get the HTC screen and it just sits there. The RUU program reports a connection error.
I have several ZIP files, one for the Froyo image, one for the Gingerbread one, they're supposed to be for this phone.
I tried to reload the Gingerbread one from the SD card (I renamed it update.zip) but it failed. I booted into fastboot, then selected Recovery. While I had the green symbol I waited...after a bit it went to HTC screen and froze.
Tried again - this time when I had the green symbol I pressed vol up + power and got to the recovery options.Here's what I see
formatting / data
can't open /data/cwpkg.zip
can't open /data/cw.prop
can't open /cache/cwpkg.zip
can't open /cache/cw.prop
formatting /cache.....
Then I get the blue list of options. I select apply update from SDCard...
-- Invalid Operation ---
Then it reboots into the HTC screen and stays there.
Suggestions?
would love a copy of your file...
bimplebean said:
Actually, I was able to flash the original 2.3.3 ROM last night using Fastboot. It took me a while to realize that since the OS was fried, ADB was useless - there was no 'android' to 'debug.' Consequently I used fastboot.exe to re-apply the PD98IMG.zip and it worked!
The old ROM is real smooth, so I may just keep it, but if I can figure out how to apply a newer build I will.
Thanks!
Click to expand...
Click to collapse
Any chance I could get you to get me a copy of your original 2.3.3 ROM? I would like to try this. My phone Inspire 4G is bricked.....
pharoah1974 said:
Any chance I could get you to get me a copy of your original 2.3.3 ROM? I would like to try this. My phone Inspire 4G is bricked.....
Click to expand...
Click to collapse
The original Stock rom can be found in www.shipped-roms.com or you can get the lastest 2.3.5 AT&T rom at the HTC support Site.
glevitan said:
The original Stock rom can be found in www.shipped-roms.com or you can get the lastest 2.3.5 AT&T rom at the HTC support Site.
Click to expand...
Click to collapse
Thanks. I will try that.
Hi all,
My Sensation XE was recently dropped from a fair height, and now it is demonstrating multiple issues:
- Screen has a small buldge in upper left corner,
- Wifi does not turn on,
- Bluetooth does not turn on,
- The memory card cant be read,
- The casing got damaged.
I replaced the battery back cover with a used one from eBay this week, so that was a quick fix.
My wifi and bluetooth were still not turning on. So I thought I may as well restore the firmware to fix it.
After booting up in 4EXT Recovery Touch (ver1.0.0.3 beta 8), I formatted the system and data folder and then tried to restore it.
But now it wont boot into anything. I believe I have formatted my ROM by mistake and now it wont boot.
I can go to Recovery mode, but nothing from there.
Please guide me diagnose and restore my phone...
bym007 said:
Hi all,
My Sensation XE was recently dropped from a fair height, and now it is demonstrating multiple issues:
- Screen has a small buldge in upper left corner,
- Wifi does not turn on,
- Bluetooth does not turn on,
- The memory card cant be read,
- The casing got damaged.
I replaced the battery back cover with a used one from eBay this week, so that was a quick fix.
My wifi and bluetooth were still not turning on. So I thought I may as well restore the firmware to fix it.
After booting up in 4EXT Recovery Touch (ver1.0.0.3 beta 8), I formatted the system and data folder and then tried to restore it.
But now it wont boot into anything. I believe I have formatted my ROM by mistake and now it wont boot.
I can go to Recovery mode, but nothing from there.
Please guide me diagnose and restore my phone...
Click to expand...
Click to collapse
did you make a nandroid backup from recovery before formatted system and data folder?
if not you should
now flash again the rom
rzr86 said:
did you make a nandroid backup from recovery before formatted system and data folder?
if not you should
now flash again the rom
Click to expand...
Click to collapse
No, I did not make a backup.
How can I make a backup now that my phone is not booting up and stuck on Sensation splash screen.
I can go into Bootloader/recovery screens though.
Secondly I cant mount or read from the SD card either.
Kindly suggest alternatives.. Cheers.
bym007 said:
No, I did not make a backup.
How can I make a backup now that my phone is not booting up and stuck on Sensation splash screen.
I can go into Bootloader/recovery screens though.
Secondly I cant mount or read from the SD card either.
Kindly suggest alternatives.. Cheers.
Click to expand...
Click to collapse
use a ruu.exe
http://forum.xda-developers.com/showthread.php?t=1672425
use the one which corresponds with your region(firmware) and cid
edit:can you mount the sdcard from recovery?
rzr86 said:
did you make a nandroid backup from recovery before formatted system and data folder?
if not you should
now flash again the rom
Click to expand...
Click to collapse
rzr86 said:
use a ruu.exe
http://forum.xda-developers.com/showthread.php?t=1672425
use the one which corresponds with your region(firmware) and cid
edit:can you mount the sdcard from recovery?
Click to expand...
Click to collapse
I am downloading all the files required for RUU from my laptop.
regarding the SD Card, I cant mount it in the Recovery Mode, however, when I connect it to the laptop in Recovery Mode and toggle USB connection menu, the SD card mounts in the laptop, as USB drive. I confirmed by copying and removing stuff on it.
bym007 said:
I am downloading all the files required for RUU from my laptop.
regarding the SD Card, I cant mount it in the Recovery Mode, however, when I connect it to the laptop in Recovery Mode and toggle USB connection menu, the SD card mounts in the laptop, as USB drive. I confirmed by copying and removing stuff on it.
Click to expand...
Click to collapse
since you can't mount the sdcard from recovery then the nandroid is useless
your only option is the ruu.exe
does your sdcard fits correctly in its case?
maybe that's why you can't mount it after dropping
rzr86 said:
since you can't mount the sdcard from recovery then the nandroid is useless
your only option is the ruu.exe
does your sdcard fits correctly in its case?
maybe that's why you can't mount it after dropping
Click to expand...
Click to collapse
So, I am trying to run RUU.exe and update the phoneset.
Here is an error message I get after following the steps as mentioned.
C:\AndroidSDK\sdk\tools>fastboot flash zip PG58IMG.zip
sending 'zip' (347576 KB)...
FAILED (remote: 02 data length is too large)
finished. total time: 0.030s
Click to expand...
Click to collapse
Please see attached snapshot.
I have tried this with a couple of ROMs, but still no success.
Kindly suggest what is going wrong here?
bym007 said:
So, I am trying to run RUU.exe and update the phoneset.
Here is an error message I get after following the steps as mentioned.
Please see attached snapshot.
I have tried this with a couple of ROMs, but still no success.
Kindly suggest what is going wrong here?
Click to expand...
Click to collapse
actually don't do it in that way
connect the device in fastboot mode to pc and run the ruu.exe directly
see also step 3 from the ruu thread
rzr86 said:
actually don't do it in that way
connect the device in fastboot mode to pc and run the ruu.exe directly
see also step 3 from the ruu thread
Click to expand...
Click to collapse
How do I run RUU directly ? Is there a separate tool or command line app for that ?
bym007 said:
How do I run RUU directly ? Is there a separate tool or command line app for that ?
Click to expand...
Click to collapse
connect the device in fastboot mode to pc
double click to the ruu.exe
rzr86 said:
connect the device in fastboot mode to pc
double click to the ruu.exe
Click to expand...
Click to collapse
I cannt find RUU in my Android SDK folder. Can I download it from somewhere separately ?
bym007 said:
I cannt find RUU in my Android SDK folder. Can I download it from somewhere separately ?
Click to expand...
Click to collapse
from here
http://forum.xda-developers.com/showthread.php?t=1672425
rzr86 said:
connect the device in fastboot mode to pc
double click to the ruu.exe
Click to expand...
Click to collapse
rzr86 said:
from here
http://forum.xda-developers.com/showthread.php?t=1672425
Click to expand...
Click to collapse
Thanks, downloading it now.
I check my CID, and it was HTC__001, which is HTC WWE handset.
Now, I downloaded and ran the RUU from the link, which is corresponding to my handset. After running for a long time, it gave me an error. I am attaching screenshots below.
Please assist.
bym007 said:
I check my CID, and it was HTC__001, which is HTC WWE handset.
Now, I downloaded and ran the RUU from the link, which is corresponding to my handset. After running for a long time, it gave me an error. I am attaching screenshots below.
Please assist.
Click to expand...
Click to collapse
Which one you downloaded?
Probably you tried a one for a different model
You said you have a sensation xe device so use the one for xe
Sent from my HTC Sensation Z710e using xda premium
rzr86 said:
Which one you downloaded?
Probably you tried a one for a different model
You said you have a sensation xe device so use the one for xe
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
I downloaded another RUU for my model Sensation XE, and thankfully, my phone is up again.
Now, about my Wifi, Bluetooth and SD card, they are still not working.
I know its a long shot, but could something be done about it ?
bym007 said:
I downloaded another RUU for my model Sensation XE, and thankfully, my phone is up again.
Now, about my Wifi, Bluetooth and SD card, they are still not working.
I know its a long shot, but could something be done about it ?
Click to expand...
Click to collapse
probably mate it's a hardware issue
check your back cover if antennas are fine(the one which is responsible for wifi)or try to lift them up a little bit
also check again the card reader if something is wrong
i am out of ideas mate
rzr86 said:
probably mate it's a hardware issue
check your back cover if antennas are fine(the one which is responsible for wifi)or try to lift them up a little bit
also check again the card reader if something is wrong
i am out of ideas mate
Click to expand...
Click to collapse
Thanks, I changed my back case, so its either hatdware issue or antenna pins being bent. I will try to ease them out gently.
Out of interest, does bluetooth also have an antenna?
Sent from my HTC One using xda premium
bym007 said:
Thanks, I changed my back case, so its either hatdware issue or antenna pins being bent. I will try to ease them out gently.
Out of interest, does bluetooth also have an antenna?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
i am not sure but i think it is the same for the wifi