Related
[SOLVED]
okay so i have a working goldcard. my adb is working
i have a 32b
but heres the weird part. i loaded the sappimg.zip on my goldcard and did fastboot. that was loaded just fine. yet im still on 1.6 , but i thought im suppose to be on 1.5. im going by the directions on the (how to) for rooting made by RA.
then when i fastboot usb to load the recovery img. it says failed. i really have no idea what im doing wrong.
i have done all this for my g1. cuz i hand changed the boot screen. so im not new to this.
i have checked to see if my drivers are all working. when im on the home screen , i made sure my mytouch was connected to adb with *adb devices* but when i go to fastboot usb it says theres nothing there. also i have the recovery.img in both places. one on my normal mem card and one in ANDROIDSDK/tools/
so im not even sure what the problem is. once i get the recovery.img on there then ill be good to go.
if anyone knows what this may be. then thank you in advanced for the help
posted in wrong section... And try unlocker to get yourself a video you can't seem to read. B/c you don't need a gold card or fastboot... REALLY over thinking it.. get a newer updated guide really/
wow dbag. i am using unlocker also. forgot to put that in there.
okay all great master of phones. why not help then
Sent from my T-Mobile G1 using the XDA mobile application powered by Tapatalk
Downgrade to DC83 (1.5). Just drag and drop Sapp onto the root of your card, unmount, turn the phone off, volume down and power, hit END key to start update, wait awhile (make sure your phone has full power), once its done hit the trackball to restart and you should be good to go. Reboot phone and check system settings for 1.5 firm.
ok first off we need your phone info... not all mt3g need a goldcard to root.. basically i found if you mt3g came with 1.6 preloaded then you do need a goldcard.. you wont be able to just downgrade using the mt3g sappimg from theunlockr how to..
ceas909 said:
ok first off we need your phone info... not all mt3g need a goldcard to root.. basically i found if you mt3g came with 1.6 preloaded then you do need a goldcard.. you wont be able to just downgrade using the mt3g sappimg from theunlockr how to..
Click to expand...
Click to collapse
yeah this was a replacement MT3g that came with 1.6
to the guy above. i tried those steps already. it stops at sig. and says failed something.
i made a goldcard and tried with the Sapp zip file
it loads and all. but then its still on 1.6
G-Fetus6 said:
to the guy above. i tried those steps already. it stops at sig. and says failed something.
i made a goldcard and tried with the Sapp zip file
it loads and all. but then its still on 1.6
Click to expand...
Click to collapse
Downgrade to DC83 (1.5). Just drag and drop Sapp onto the root of your card, unmount, turn the phone off, volume down and power, hit END key to start update, wait awhile (make sure your phone has full power), once its done hit the trackball to restart and you should be good to go. Reboot phone and check system settings for 1.5 firm.
Click to expand...
Click to collapse
Well. Those are right steps. If it says signature fail - that's your problem that you need to fix.
r3s-rt said:
Well. Those are right steps. If it says signature fail - that's your problem that you need to fix.
Click to expand...
Click to collapse
hmm ive tried everything. just doesnt wanna seem to downgrade. i redownloaded the files from other places to make sure it wasnt my files.
still nothing . hmmm i guess more reason to sell this phone and upgrade to a better one... maybe a N1
G-Fetus6 said:
hmm ive tried everything. just doesnt wanna seem to downgrade. i redownloaded the files from other places to make sure it wasnt my files.
still nothing . hmmm i guess more reason to sell this phone and upgrade to a better one... maybe a N1
Click to expand...
Click to collapse
no no no.. you cant downgrade your device with the regular mt3g 1.5 sappimg... if your phone came with 1.6 already loaded you need to find a sappimg that has a higher hboot then your phone... im betting your current hboot is 1.33.0007 ... and the mt3g sappimg used to downgrade to 1.5 is for hboot 1.33.0006.. you can use a hboot lower then what you have to down grade try this how to.. http://forum.xda-developers.com/showthread.php?t=674003
turtleiscool said:
posted in wrong section... And try unlocker to get yourself a video you can't seem to read. B/c you don't need a gold card or fastboot... REALLY over thinking it.. get a newer updated guide really/
Click to expand...
Click to collapse
o and its funny how noobs try to step in and give their 2 cents when they have no idea of what their talking about....
ceas909 said:
no no no.. you cant downgrade your device with the regular mt3g 1.5 sappimg... if your phone came with 1.6 already loaded you need to find a sappimg that has a higher hboot then your phone... im betting your current hboot is 1.33.0007 ... and the mt3g sappimg used to downgrade to 1.5 is for hboot 1.33.0006.. you can use a hboot lower then what you have to down grade try this how to.. http://forum.xda-developers.com/showthread.php?t=674003
Click to expand...
Click to collapse
Never knew that. Ty.
i solved it . went and looked threw the magic wiki more. and found my problem hinding. the spl was perfected an such.
turtleiscool said:
posted in wrong section... And try unlocker to get yourself a video you can't seem to read. B/c you don't need a gold card or fastboot... REALLY over thinking it.. get a newer updated guide really/
Click to expand...
Click to collapse
and yeah i posted in the wrong section. but thats cuz i though i was in the general section on my phone <not a noob lol
I ran into a few problems getting back to stock until I remembered a minor detail from my HTC Hero days.
You need to download and install HTC Sync get it here install it.
Reboot your computer
make sure the phone is NOT in USB debug mode and is in charge only mode.
the proper drivers will install. you'll know it's done right if you see ADB pop up as one of the drivers installed. You'll see a warning that HTC sync isn't detecting your phone and that's ok.
Then run the RUU exe all should work fine.
Get the RUU exe from this thread http://forum.xda-developers.com/showthread.php?t=952224 This is FROYO
http://forum.xda-developers.com/showthread.php?t=1191959 This one is Gingerbread
Didn't realize debugging had to be disabled.
Sent from my Inspire 4G or Desire HD or whatever this thing is called via XDA app.
gunnyman said:
I ran into a few problems getting back to stock until I remembered a minor detail from my HTC Hero days.
You need to download and install HTC Sync get it here install it.
Reboot your computer
make sure the phone is NOT in USB debug mode and is in charge only mode.
the proper drivers will install. you'll know it's done right if you see ADB pop up as one of the drivers installed. You'll see a warning that HTC sync isn't detecting your phone and that's ok.
Then run the RUU exe all should work fine.
Click to expand...
Click to collapse
RUU? Where do I find that?
http://forum.xda-developers.com/showthread.php?t=952224
So even if I've tried going through the rooting process and it didn't work, this will basically put the phone back the way it was before I started that process?
Yes
Sent from my Desire HD using XDA App
Good sir I can not thank you enough for helping me get my phone back. i don't even mind all the bloatware now. Too bad I can't use the thanks button more than once. I really appreciate it.
Happy to be of service. I can't dev my way out of a paper bag, well I've never tried, but I can share what I do know.
I tried to run the RUU but it failed twice. Both times it would get about 70% finished and it would stop with an Error 110 which says that a file is either open or corrupted. Then it tells you to download the RUU again and run it again, which I did but got the same results. I downloaded it with the anti virus and firewall turned off. Is there another site to download the file from?
capman231
capman231 said:
I tried to run the RUU but it failed twice. Both times it would get about 70% finished and it would stop with an Error 110 which says that a file is either open or corrupted. Then it tells you to download the RUU again and run it again, which I did but got the same results. I downloaded it with the anti virus and firewall turned off. Is there another site to download the file from?
capman231
Click to expand...
Click to collapse
have no idea. Sorry
Need to put my htc inspire to out of box state
I tried rooting my phone today and everything seemed fine but i didnt like it. so i went back to stock menu. and everything is okay but the sound isnt working can anyone please tell me how to fix this?
mohaamadq said:
I tried rooting my phone today and everything seemed fine but i didnt like it. so i went back to stock menu. and everything is okay but the sound isnt working can anyone please tell me how to fix this?
Click to expand...
Click to collapse
Either flash a different rom via Clockwork Mod or run the RUU. If you choose the RUU, be sure HTC Sync is installed, USB Debugging is checked and Fastboot is unchecked.
Thank you! It works!
Just used this thread to get my Inspire back to stock before taking it back for a refund and cancelling service. Decided to go with the HTC Evo3d from Sprint. This method worked returning the phone back to the latest (Gingerbread) and unrooted it from Cyanogen (CM7) ROM. Thanks a ton for sharing your wisdom!
Baffling Issues.
Hey, I have a question. When running this RUU update (downgrade) it gives me this: Error 140: Bootloader version error. Its agravating. I'd love to go back to froyo... I really can't use GB because it blocks tethering. Any help is appreciated. Thanks.
corvettezo7sp said:
Hey, I have a question. When running this RUU update (downgrade) it gives me this: Error 140: Bootloader version error. Its agravating. I'd love to go back to froyo... I really can't use GB because it blocks tethering. Any help is appreciated. Thanks.
Click to expand...
Click to collapse
I take it you're not S-OFF? HTC (and probably others) decided they didn't want users reverting to older versions. You'll have to root, get S-OFF, before you can revert, but if you're rooted, you might as well just use the new andTether from google code:
http://code.google.com/p/android-wifi-tether/
http://forum.xda-developers.com/showthread.php?t=1233141
Just found out at Best Buy that my phone is crap. The memory is out and I have no apps installed, my HD card is empty except for the standard stuff, and I get error that I need to free up memory or something like that. Guy told me to UNroot my phone and call AT&T.
So, this thread is all I need to do that???? Can it really be this easy????
thanks so much,
Patti
Gene Poole said:
I take it you're not S-OFF? HTC (and probably others) decided they didn't want users reverting to older versions. You'll have to root, get S-OFF, before you can revert, but if you're rooted, you might as well just use the new andTether from google code:
http://code.google.com/p/android-wifi-tether/
http://forum.xda-developers.com/showthread.php?t=1233141
Click to expand...
Click to collapse
Ok, thanks for the info! And this phone has no root, its my Moms phone and she needs the tethering. Eh, maybe we can exchange the phone. Other than that I don't know what to do. I'll browse a few more forums. Actually, one more question: is it possible to root with the latest update from HTC? As you can tell I'm really not that up to date on things around here. Haha.
Sent from my HTC Inspire 4G using XDA Premium App (MIUI FTW!)
corvettezo7sp said:
Ok, thanks for the info! And this phone has no root, its my Moms phone and she needs the tethering. Eh, maybe we can exchange the phone. Other than that I don't know what to do. I'll browse a few more forums. Actually, one more question: is it possible to root with the latest update from HTC? As you can tell I'm really not that up to date on things around here. Haha.
Sent from my HTC Inspire 4G using XDA Premium App (MIUI FTW!)
Click to expand...
Click to collapse
Yes. Ace Hack Kit v12:
http://forum.xda-developers.com/showthread.php?t=952352
corvettezo7sp said:
Ok, thanks for the info! And this phone has no root, its my Moms phone and she needs the tethering. Eh, maybe we can exchange the phone. Other than that I don't know what to do. I'll browse a few more forums. Actually, one more question: is it possible to root with the latest update from HTC? As you can tell I'm really not that up to date on things around here. Haha.
Sent from my HTC Inspire 4G using XDA Premium App (MIUI FTW!)
Click to expand...
Click to collapse
You could try this:
http://forum.xda-developers.com/showthread.php?t=1208507
gunnyman said:
have no idea. Sorry
Click to expand...
Click to collapse
Nice to see you around again gunny
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 have literally tried EVERYTHING. I have spent countless hours and actually did not go to sleep last night trying to figure this damn thing out.
I have a HTC One X running Android Version 4.0.4, HTC Sense 4.0, and Software 2.20.
I cannot figure this **** out. Right now when I run the X-Factor exploit, it gets stuck at "daemon started succesfully". When I run the HTC Drivers.exe that come with Hasoon2000's All in one kit, it doesn't even run. It does nothing.
I have restarted my computer numerous times, and I am stuck. So I'm offering this:
Anyone who helps me/leads me in the correct direction to rooting and bootunlocking my ATT One X so I can install Cyanogenmod 10,
I will give you $25 [PayPal]
I am desperate, and just want this to work.
Try my guide.
How to Unlock Bootloader and Root AT&T One X 2.20
http://www.youtube.com/watch?v=FML0Y2ovZ_Q
And here is the full guide i wrote up.
http://forums.team-nocturnal.com/showthread.php/1147
itsjakez said:
I have literally tried EVERYTHING. I have spent countless hours and actually did not go to sleep last night trying to figure this damn thing out.
I have a HTC One X running Android Version 4.0.4, HTC Sense 4.0, and Software 2.20.
I cannot figure this **** out. Right now when I run the X-Factor exploit, it gets stuck at "daemon started succesfully". When I run the HTC Drivers.exe that come with Hasoon2000's All in one kit, it doesn't even run. It does nothing.
I have restarted my computer numerous times, and I am stuck. So I'm offering this:
Anyone who helps me/leads me in the correct direction to rooting and bootunlocking my ATT One X so I can install Cyanogenmod 10,
I will give you $25 [PayPal]
I am desperate, and just want this to work.
Click to expand...
Click to collapse
Now I'm able to make it this far:
Press any key to continue...
398 KB/s (64526 bytes in 0.158s)
[-] Failed
[+] Rebooting into bootloader mode...
[+] Press enter once the device has finished booting into bootloader mode.
Press any key to continue.
So it says it fails...why?
If I hit continue it says
[+] Getting CID:
... INFOcid: CWS___001
So It doesn't get to 111111111 Like It should.
XsMagical said:
Try my guide.
How to Unlock Bootloader and Root AT&T One X 2.20
And here is the full guide i wrote up.
I'm currently following your guide. I downloaded your drivers. Do I just drag and drop all of these driver files into my drivers folder in system32?
I tried doing that earlier with I think the same drivers and It didnt work.
When I plug up my HTC One X, it doesn't show up as a adb device, it shows up as My HTC.
Click to expand...
Click to collapse
It would be more helpful to list the things you tried, instead of just saying "literally everything".
Does adb see the phone?
Did you try different USB ports or cables? Tried a different computer (if possible)?
redpoint73 said:
It would be more helpful to list the things you tried, instead of just saying "literally everything".
Does adb see the phone?
Did you try different USB ports or cables? Tried a different computer (if possible)?
Click to expand...
Click to collapse
I'm not sure by what you mean of "does adb see the phone?
If you mean if I open up device manager and it says "adb device", then no, adb does not see it.
I did try different USB cables, I'll try a different port now.
I do not have any access to any other computer at the moment, so no.
Thanks for your time, by the way.
Install HTC sync. It will install the drivers.
Sent from my Nocturnal'd ONE X
itsjakez said:
I cannot figure this **** out. Right now when I run the X-Factor exploit, it gets stuck at "daemon started succesfully". When I run the HTC Drivers.exe that come with Hasoon2000's All in one kit, it doesn't even run. It does nothing.
Click to expand...
Click to collapse
Have you tried updating drivers manually? His toolkit did thesame to me but I just went to:
Right click Computer -> Manage -> driver manager
and updated my drivers from there.
EDIT: Try the post above mine, before this. I didn't even think of that, HTC Sync will install that latest drivers.
Aldo, this is technically a question so it shouldn't be here. It should be in Q&A
The problem is almost certainly the HTC drivers. Otherwise your computer won't see the phone.
You have to do this with just about every new device you root, unless you're staying with the same manufacturer.
iElvis said:
The problem is almost certainly the HTC drivers. Otherwise your computer won't see the phone.
You have to do this with just about every new device you root, unless you're staying with the same manufacturer.
Click to expand...
Click to collapse
I installed HTC Sync and used their drivers, and Im still met with the failed CID thing.
Ughhh I'm so frustrated.
Where it says failed before where it says authorize backup, are you hitting the restore option on your phone when it shows up and prompted?
Sent from my One X using xda app-developers app
Kole_Ackerson said:
Where it says failed before where it says authorize backup, are you hitting the restore option on your phone when it shows up and prompted?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Yes, I am.
I'm following a video tutorial step by step and I still get these errors.
itsjakez said:
I installed HTC Sync and used their drivers, and Im still met with the failed CID thing.
Ughhh I'm so frustrated.
Click to expand...
Click to collapse
Do you have the international version of the phone, or the US version?
it WILL work using the X-factor exploit.
Three main steps:
1.) Download SYNC to ensure latest drivers here
2.) make sure to RIGHT CLICK and RUN AS ADMINISTRATOR (that took me f'in 27 minutes to realize)
3.) follow all on screen instructions.
---------- Post added at 06:18 PM ---------- Previous post was at 06:17 PM ----------
Myrder said:
Do you have the international version of the phone, or the US version?
Click to expand...
Click to collapse
+1
Strange.... the only other option is to try a different USB port or another windows machine I guess.. sorry bro
Sent from my One X using xda app-developers app
Myrder said:
Do you have the international version of the phone, or the US version?
Click to expand...
Click to collapse
US Version.
I am now trying while running as administrator (I think I've tried this already)
Yep. Same error. Failed on CID thing.
itsjakez said:
US Version.
I am now trying while running as administrator (I think I've tried this already)
Yep. Same error. Failed on CID thing.
Click to expand...
Click to collapse
Hmm... I'm assuming you're on the 2.20 right?
Edit: We'll get down to the bottom of this and get him rooted.
---------- Post added at 11:27 AM ---------- Previous post was at 11:24 AM ----------
Also, ensure your usb debugging is ON.
Myrder said:
Hmm... I'm assuming you're on the 2.20 right?
Edit: We'll get down to the bottom of this and get him rooted.
Click to expand...
Click to collapse
Thank you for your diligence.
Yes, I'm on 2.20
I don't understand why this wont work for me!!!
itsjakez said:
Thank you for your diligence.
Yes, I'm on 2.20
I don't understand why this wont work for me!!!
Click to expand...
Click to collapse
Check to make sure your use debugging is on, try it. If that doesn't work... I would like to see the prompt. May have to do this through teamviewer.
Drivers may be the problem. I didn't have quite the same problem he is having( fastboot and adb didn't wont to see my device.) Spent 3 days trying to fiqure it out. Finally I gave up and installed Mac Os X on vmware and ran the mac version of x-factor and then I had no problems. You might want to try that. It was the only thing that worked for me. Htc sync, pda net, and reinstalling the driver never helped me. No matter what I did I never could get windows to see my device.