Related
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 hope I am not posting where I am not supposed to, but I desperately need help. I am a noob and have managed to brick my inspire, or at least that's my guess. I can still get in to hboot, but when I select recovery, nothing happens. This all started after trying to use the htc boot unlocker. My screen shows the following when in hboot
*** UNLOCKED ***
ACE PVT SHIP S-ON RL
HBOOT-2.00.0029
MIROP-0438
RADIO-26.10.04.03_M
eMMC-boot
Dec 22 2011,14:28:19
I have tried loading the stock images using the PD98IMG.zip files that I have found throughout the site, but nothing seems to be working. Please help, or if you can point me to someone that can I would greatly appreciate it. I hate to be a pain, but I don't know what else to do.
dalton42503 said:
I hope I am not posting where I am not supposed to, but I desperately need help. I am a noob and have managed to brick my inspire, or at least that's my guess. I can still get in to hboot, but when I select recovery, nothing happens. This all started after trying to use the htc boot unlocker. My screen shows the following when in hboot
*** UNLOCKED ***
ACE PVT SHIP S-ON RL
HBOOT-2.00.0029
MIROP-0438
RADIO-26.10.04.03_M
eMMC-boot
Dec 22 2011,14:28:19
I have tried loading the stock images using the PD98IMG.zip files that I have found throughout the site, but nothing seems to be working. Please help, or if you can point me to someone that can I would greatly appreciate it. I hate to be a pain, but I don't know what else to do.
Click to expand...
Click to collapse
YOUR PHONE IS NOT BRICKED. The term bricked means that your phone is a useful as a brick, i.e. if you can get into HBOOT, it's not bricked.
Gotta ask though, why did you not use the Hack Kit as its the only reliable method to root, my advice to you sir is when this gets cleared up READ AND EDUCATE YOURSELF before you really do brick your phone.
If you have a SDcard reader, pop out the SDcard and place one of the PD98IMG stock ROMs on your SDcard. From here you can reboot into HBOOT with the sdcard in your phone and HBOOT should pick up the PD98IMG and flash a working stock ROM. From here, you can root with the Hack Kit...
This will help you, read it and do what the stock ROM option...if you can get into HBOOT
I have tried doing that, it says loading image, then parsing, then goes back to the hboot screen, it doesn't say press volume up to update or anything else as I have read in many other posts. Am I doing something wrong? As far as not using the hack kit, I didn't really stumble on that until after it was to late, sure wish I had found it in the first place. Guess if I could just get it back to factory, I would accept that doing this isn't for me and not mess with it again. I am good at following directions, but nothing I have tried seems to work.
dalton42503 said:
I have tried doing that, it says loading image, then parsing, then goes back to the hboot screen, it doesn't say press volume up to update or anything else as I have read in many other posts. Am I doing something wrong? As far as not using the hack kit, I didn't really stumble on that until after it was to late, sure wish I had found it in the first place. Guess if I could just get it back to factory, I would accept that doing this isn't for me and not mess with it again. I am good at following directions, but nothing I have tried seems to work.
Click to expand...
Click to collapse
is the file named exactly "PD98IMG.zip"..you may also want to check the hide extension option to be sure its not hiding the .zip because if it is and you renamed it to "PD98IMG.zip" with the hide extension on, the phone will read it as "PD98IMG.zip.zip" and you would get that error.
haha and yeah man, we've all been there...I don't want to discourage you man, rooting is such an awesome experience and the hack kit is a pretty straight forward process, if you do the research and take the time to understand what you're doing, but lets see if we can help you out here first. I had the same issue you're having when I tried to flash a radio (same PD98IMG method you're trying to use) and it turned out to be the hide extension issue.
I had also verified that as well, I went under tools, folder options, view tab, scrolled down to hide extensions for known file types and unchecked... And, everything was correct, just verified to be on the safe side.
dalton42503 said:
I had also verified that as well, I went under tools, folder options, view tab, scrolled down to hide extensions for known file types and unchecked... And, everything was correct, just verified to be on the safe side.
Click to expand...
Click to collapse
hmm, so its named PD98IMG.zip caps and everything? If its not working you m ay have to get a stock RUU and run it through fastboot..
This is why you should educate yourself first. You do not need to unlock the bootloader from the HTC dev site. Now you could flash the the stock ruu from the PC and then use the hack kit. Check the stickies in the Inspire general section for more help.
Sent from my HTC Inspire 4G using Tapatalk
I understand that I should have been a little more educated first now, but I thought I had everything in order, thats what thinking gets me... I have tried running the stock ruu, but it gives the following error.
ERROR[155]: UNKNOWN ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
I did notice the Image version the program shows is on the phone is 3.13.0.0, and it is trying to put 2.47.502.7 on the phone... Is this the problem? If so, whats the solution, I am so lost now its not even funny.... I apologize everyone.
dalton42503 said:
I understand that I should have been a little more educated first now, but I thought I had everything in order, thats what thinking gets me... I have tried running the stock ruu, but it gives the following error.
ERROR[155]: UNKNOWN ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
I did notice the Image version the program shows is on the phone is 3.13.0.0, and it is trying to put 2.47.502.7 on the phone... Is this the problem? If so, whats the solution, I am so lost now its not even funny.... I apologize everyone.
Click to expand...
Click to collapse
Dalton, lock your bootloader again. Boot into fastboot and plug the phone. You will see fastboot usb at the top. Then plug your phone and open cmd session. Once there type fastboot oem relock. Once that is done, try flashing the .exe file in the HTC site (original GB update), making sure that you have HTC Sync installed.
If that fails, then I would try using the HACK Kit to gain S-OFF and root. You will then be able to revert to stock or flash a custom rom...
Had a similar problem when using aahk my own fault and I took care of it. Long winded, so short of it, are you trying to install through
1. hboot or 2. on the computer using HTC rom update?
I ended up trying 2. But ended up using aahk to finish.
HTC update errored out and the recovery portion would not work, just in a boot loop on HTC logo
This was good news as aahk could take over on USB during that HTC green letters white background.
I'd suggest reading the effen manual run the tool to get it up and going, figure out what you want to do. I've used it to return to stock with s off before go back into roms.
So look at those options know what you want and then power on the phone USB connected and during HTC screen enter your number the kit should take over and give you what you asked it.
That should give you a working rom image.
--will'm
Sent from my Inspire 4G using XDA Premium HD app
willm98G97B said:
Had a similar problem when using aahk my own fault and I took care of it. Long winded, so short of it, are you trying to install through
1. hboot or 2. on the computer using HTC rom update?
I ended up trying 2. But ended up using aahk to finish.
HTC update errored out and the recovery portion would not work, just in a boot loop on HTC logo
This was good news as aahk could take over on USB during that HTC green letters white background.
I'd suggest reading the effen manual run the tool to get it up and going, figure out what you want to do. I've used it to return to stock with s off before go back into roms.
So look at those options know what you want and then power on the phone USB connected and during HTC screen enter your number the kit should take over and give you what you asked it.
That should give you a working rom image.
--will'm
Sent from my Inspire 4G using XDA Premium HD app
Click to expand...
Click to collapse
He won´t be able to use the Kit if the bootloader is unlocked. HE MUST RELOCK Bootloader...then run the Kit...It´s worth mentioning that...
True, never ran htc s unlock option.
Sent from my Inspire 4G using XDA Premium HD app
Thanks A MILLION!!!
Thank you all for your time, finally got it working again, with stock firmware. Think I may wait a while before messing with this again. I really do appreciate the help, without you all, I would have a nice expensive paper weight....
dalton42503 said:
Thank you all for your time, finally got it working again, with stock firmware. Think I may wait a while before messing with this again. I really do appreciate the help, without you all, I would have a nice expensive paper weight....
Click to expand...
Click to collapse
Glad you have it back....yeah you'd better read and make sure what are about to do it and of course what risks are involved before making a move....
Dalton,
I would suggest following glevitan's and willm's assertion of getting s-off and root to use custom roms. Custom roms are WAY better than anything HTC has to offer, and much easier to install, if you have an issue warranty wise, you can always return to stock. Just make sure you know how to flash correctly, search for it and you will find easy instructions, and if memory serves, a youtube video which helped me greatly.
dalton42503 said:
Thank you all for your time, finally got it working again, with stock firmware. Think I may wait a while before messing with this again. I really do appreciate the help, without you all, I would have a nice expensive paper weight....
Click to expand...
Click to collapse
Can you tell me the which firmware or send me a link.I have a same problem
If you are using AT&T branded cell then go to the htc.com site and in the support section of the inspire you will find it. Otherwise, you will find stock roms in the general section of this forum
Sent from my Inspire 4G using XDA
glevitan said:
If you are using AT&T branded cell then go to the htc.com site and in the support section of the inspire you will find it. Otherwise, you will find stock roms in the general section of this forum
Sent from my Inspire 4G using XDA
Click to expand...
Click to collapse
I am having a bootloader error with stock ro.(error 140)
How can i fix it
ydnbngl said:
I am having a bootloader error with stock ro.(error 140)
How can i fix it
Click to expand...
Click to collapse
if you have unlocked the bootloader then relock it...then run it again.
glevitan said:
if you have unlocked the bootloader then relock it...then run it again.
Click to expand...
Click to collapse
It is relocked and ship s-on
Well Im going to quickly explain my way I rooted the new hboot (NOT S-OFF)
In all my time trying all methods I found a couple that did things for me.
First was the all in one kit http://www.xda-developers.com/andro...-mytouch-4g-slide-amaze-4g-rezound-and-vivid/
this I used to unlock boot loader and have a recovery img
but it didnt want to root my phone. So i tried other things like the bear wire method which i wouldnt rec. and came across a thread http://forum.xda-developers.com/showthread.php?t=1508556&page=3 that said "how to flash ics with s-on" and it was pretty simple so i tried it and it flashed a ics rom and when I went into the it was rooted! Su granted and all.
With that said I hope this can help people who want a little change until a s-off method comes about but this is a whole lot to work with for now.
Thanks to everyone and I hope this helps.
I have :
Doubleshot pvt ship s-on rl
hboot- 1.45.0013
microp-0353
emmc-boot
now running PYROS ics rooted
homeboy773 said:
Well Im going to quickly explain my way I rooted the new hboot (NOT S-OFF)
In all my time trying all methods I found a couple that did things for me.
First was the all in one kit http://www.xda-developers.com/andro...-mytouch-4g-slide-amaze-4g-rezound-and-vivid/
this I used to unlock boot loader and have a recovery img
but it didnt want to root my phone. So i tried other things like the bear wire method which i wouldnt rec. and came across a thread http://forum.xda-developers.com/showthread.php?t=1508556&page=3 that said "how to flash ics with s-on" and it was pretty simple so i tried it and it flashed a ics rom and when I went into the it was rooted! Su granted and all.
With that said I hope this can help people who want a little change until a s-off method comes about but this is a whole lot to work with for now.
Thanks to everyone and I hope this helps.
I have :
Doubleshot pvt ship s-on rl
hboot- 1.45.0013
microp-0353
emmc-boot
now running PYROS ics rooted
Click to expand...
Click to collapse
That is fantastic news!
Can you post any pics / screens?
Anyone else can confirm it?
I see a thank you from yellowjacket1981 - have you follow these steps and now you indeed have rooted Pyros ICS too on a locked MT4Gs with s-on and hboot-1.45.0013 ???
MT4GS said:
That is fantastic news!
Can you post any pics / screens?
Anyone else can confirm it?
I see a thank you from yellowjacket1981 - have you follow these steps and now you indeed have rooted Pyros ICS too on a locked MT4Gs with s-on and hboot-1.45.0013 ???
Click to expand...
Click to collapse
I rooted my boyfriend's phone and put bulletproof on his phone. He has that hotboot. I will post screenshots when he gets here later today.
yellowjacket1981 said:
I rooted my boyfriend's phone and put bulletproof on his phone. He has that hotboot. I will post screenshots when he gets here later today.
Click to expand...
Click to collapse
Cool, thanks!
Unlocking through htcdev and then installing recovery and superuser.apk will give you root permissions....not hard to root anymore. If you want s-off it is a bit more tricky but even with s-on you can flash roms just have to do kernel seperately
beezie916 said:
Unlocking through htcdev and then installing recovery and superuser.apk will give you root permissions....not hard to root anymore. If you want s-off it is a bit more tricky but even with s-on you can flash roms just have to do kernel seperately
Click to expand...
Click to collapse
What about "wire trick" to get s-off on top of this procedure?
MT4GS said:
What about "wire trick" to get s-off on top of this procedure?
Click to expand...
Click to collapse
I did the trick and worked first time for me but others have had more issues...like I said a bit more complicated to et s-off but root is very easy thanks to htcdev now
MT4GS said:
What about "wire trick" to get s-off on top of this procedure?
Click to expand...
Click to collapse
I did the wire trick also. It took me about 10-15 times for it to actually work though. The 0.4 version of the program worked with me. Just takes patience and truly following instructions. Now I don't have to flash ONLY at my computer anymore. So glad of that!
manimmal said:
I did the wire trick also. It took me about 10-15 times for it to actually work though. The 0.4 version of the program worked with me. Just takes patience and truly following instructions. Now I don't have to flash ONLY at my computer anymore. So glad of that!
Click to expand...
Click to collapse
Hey what did it show for you? When u did the trick did it go fastboot then to the loading screen again? And what happened to your sd card? Mine is basically garbo now.
Also can u quick link for the 0.4 version for me.
Thanks.
Sent from my HTC Vision using XDA
homeboy773 said:
Hey what did it show for you? When u did the trick did it go fastboot then to the loading screen again? And what happened to your sd card? Mine is basically garbo now.
Also can u quick link for the 0.4 version for me.
Click to expand...
Click to collapse
For me, the first couple times I tried it the response was always something different (from it saying things like "couldn't find bar" to "connect device" even though it was connected). I asked around a little but since it was still kind of experimental there was no definite answer for much of anything. When I got ver 0.4 a few of the same errors happened but not as much. For some reason I found that restarting my computer and then running the program worked. Every time I did it went further in the ControlBear program, then finally when I did the wire trick the phone rebooted but not into fastboot, it just stayed at the boot animation logo while the program finished its work. I think the results vary for everyone...My SD card did crash but I was able to restore it with the info Indirect posted. It was an extra card tho, I keep them laying around.
Ok so heres the link. I still have it ---> Ver 0.4
help please
i bought a mytouch 4g slide on amazon and ive been trying to root my phone it says in fastboot LOCKED s-off. i tried to load clock work mod and it wont let me can anyone please give me information on my situation. and what to do or where to go from here. on my computer it wont recognize my device for me to be able to complete the process in the command prompt it just says waiting for device and my computer says device not working. ive searched and search and search and i cant find anything on my situation. please help
kingkyle14 said:
i bought a mytouch 4g slide on amazon and ive been trying to root my phone it says in fastboot LOCKED s-off. i tried to load clock work mod and it wont let me can anyone please give me information on my situation. and what to do or where to go from here. on my computer it wont recognize my device for me to be able to complete the process in the command prompt it just says waiting for device and my computer says device not working. ive searched and search and search and i cant find anything on my situation. please help
Click to expand...
Click to collapse
Good day, and welcome to XDA!
What is the OS on your PC? Windows, Mac, Linux, or something else? Which drivers have you tried? I had good luck in the past with the adbsetup package, but your mileage may vary.
Hope this provides a good start.
HI guys,
Had a quick search on my phone and couldn't find anything in this section, do forgive me if there's already a thread that explains this.
Basically, my phone keeps randomly rebooting, and sometimes only boots to them shut itself down again, no matter what rom, radio or hboot it's on, so I decided that I'm going to have to take it back to o2 as it's still under warranty.
The only problem is, I'm rooted and want to return to s-on. I've Google'd how to do this on the Sensation and found that you can do it via the ruu, but this can sometimes brick your device, is there any easy way to do this with clockwork installed etc?
If it helps, I'm running 4.03, latest radio and latest hboot, the baseband version states this: 11.76A_3504.00P.11.24A.3504.11_M
Thanks in advanced,
Dan
DanielF50 said:
HI guys,
Had a quick search on my phone and couldn't find anything in this section, do forgive me if there's already a thread that explains this.
Basically, my phone keeps randomly rebooting, and sometimes only boots to them shut itself down again, no matter what rom, radio or hboot it's on, so I decided that I'm going to have to take it back to o2 as it's still under warranty.
The only problem is, I'm rooted and want to return to s-on. I've Google'd how to do this on the Sensation and found that you can do it via the ruu, but this can sometimes brick your device, is there any easy way to do this with clockwork installed etc?
If it helps, I'm running 4.03, latest radio and latest hboot, the baseband version states this: 11.76A_3504.00P.11.24A.3504.11_M
Thanks in advanced,
Dan
Click to expand...
Click to collapse
Follow these steps:
1. Flash an RUU - It doesnt matter which one but I would recommend the latest 3.33.401.6 RUU - WARNING: THIS STEP MUST BE DONE, FAILURE TO DO THIS STEP WILL RESULT IN A BRICKED DEVICE!
2. Once the RUU has done its thing, boot into bootloader, connect to pc, go to fastboot usb mode and type the following command:
fastboot oem writesecureflag 3
All done
To add on the post above me, if the RUU.exe is unable to find your device, install the "Universal_Naked_Driver_0.7" drivers. Worked for me.
Jonny said:
Follow these steps:
1. Flash an RUU - It doesnt matter which one but I would recommend the latest 3.33.401.6 RUU - WARNING: THIS STEP MUST BE DONE, FAILURE TO DO THIS STEP WILL RESULT IN A BRICKED DEVICE!
2. Once the RUU has done its thing, boot into bootloader, connect to pc, go to fastboot usb mode and type the following command:
fastboot oem writesecureflag 3
All done
Click to expand...
Click to collapse
1.RUU corresponding to his device must be chosen for rma purposes.. Otherwise they won't accept it.. They will check the main-version too which varies for each RUU
Also running RUU as a exe ( not manually flashing) will never result in a brick.. In case something is failed.. It's completely reverted
DanielF50 find the exact RUU as per your Cid and mid
The below guide is the best one.. Which will help you in finding the right RUU and flashing instructions
http://forum.xda-developers.com/showthread.php?p=26541170
Sent from my pyramid.. Through blazing fast sonic waves
ganeshp said:
1.RUU corresponding to his device must be chosen for rma purposes.. Otherwise they won't accept it.. They will check the main-version too which varies for each RUU
Also running RUU as a exe ( not manually flashing) will never result in a brick.. In case something is failed.. It's completely reverted
DanielF50 find the exact RUU as per your Cid and mid
The below guide is the best one.. Which will help you in finding the right RUU and flashing instructions
http://forum.xda-developers.com/showthread.php?p=26541170
Sent from my pyramid.. Through blazing fast sonic waves
Click to expand...
Click to collapse
I have the same problem, my phone keeps on rebooting every time. Where did you find the original HTC rom?
anielk77 said:
I have the same problem, my phone keeps on rebooting every time. Where did you find the original HTC rom?
Click to expand...
Click to collapse
where??
ive given a link already ..which will help you in finding the right RUU ..just read read read the guide
Hi guys, thanks for all the replies!
I flashed the RRU but flashed one of the latests ones, and now I can't root to restore my settings etc with Titanium Backup
Anyone know of a temporary root on 1.27, without having to use HTC dev, so that I don't void my warranty?
DanielF50 said:
Hi guys, thanks for all the replies!
I flashed the RRU but flashed one of the latests ones, and now I can't root to restore my settings etc with Titanium Backup
Anyone know of a temporary root on 1.27, without having to use HTC dev, so that I don't void my warranty?
Click to expand...
Click to collapse
arent you going to RMA it?
anyways if you are already SOFF ..you can use my one click root tool from my soff guide (link in my signature)
ganeshp said:
arent you going to RMA it?
anyways if you are already SOFF ..you can use my one click root tool from my soff guide (link in my signature)
Click to expand...
Click to collapse
I am, but I wanted to restore my settings so I can use it for a few days before I take it in, as work has got in the way lol.
I S-On'd after restoring the RUU as I didn't know revolutionary didn't work n 1.27, obviously not up to speed with this stuff anymore :silly:
DanielF50 said:
I am, but I wanted to restore my settings so I can use it for a few days before I take it in, as work has got in the way lol.
I S-On'd after restoring the RUU as I didn't know revolutionary didn't work n 1.27, obviously not up to speed with this stuff anymore :silly:
Click to expand...
Click to collapse
If SON Then rooting process is difficult. If you want to avoid htc-dev. As you need to soff again.. That too juopunutbear (wire trick)... You should have done SON just when you return the device..
Sent from my pyramid.. Through blazing fast sonic waves
ganeshp said:
If SON Then rooting process is difficult. If you want to avoid htc-dev. As you need to soff again.. That too juopunutbear (wire trick)... You should have done SON just when you return the device..
Sent from my pyramid.. Through blazing fast sonic waves
Click to expand...
Click to collapse
I've tried the wire trick too, can't seem to get it to work, so completely given up, whenever the wire trick supposedly works my phone actually turns itself off
DanielF50 said:
I've tried the wire trick too, can't seem to get it to work, so completely given up, whenever the wire trick supposedly works my phone actually turns itself off
Click to expand...
Click to collapse
Wire trick for soff without htc-dev is but hard.. Check the troubleshoot point #3 for tips, tricks
Also the phone switching off means.. The pause you gave is too high..
Try this
0.5 sec tap - 1.5 sec pause - 0.5 sec tap
Sent from my pyramid.. Through blazing fast sonic waves
Thanks mate, got it rooted and s-off'd now
Any way to S-ON and Unroot again without wiping now!? lol.
Was thinking, flashing certain images through fastboot should do that shouldn't they?
Hi guys!
First of all thank you for reading.
I'm probably in my 3rd day lurking around every possible forum and thread looking for an answer to my similar problem but have yet to find one.
I used to have a sensation xe but I kinda smashed the digitizer to bits. before that the was battery swollen and the back case pretty damaged (it survived a 120 kph gps reading of an rc car before going end over end across a parking lot). Meanwhile I got an Htc One, which is superb and I kinda forgot about the old gal.
A few days back I found a guy selling a sensation for spares (the mobo was fried on his) so I just bought that (for 20 euros) and figured all I needed to to was a mobo transplant and then have a nice almost new sensation.
But obviously the digitizer is not calibrated. I found the forum with the tutorial on that but it requires super CID and Soff. Cannot do either of them.
Since the mobo has been replaced the devunlock didn't work. Cannot, for the love of me succeed with the junopunutbear soff with the wire trick. Tried it on a ubuntu live cd, all goes well up until the wire trick. On a side note, I design and build 3d printers for a living, I might be a noob in the android department but that's about it. Even tried an automatic timed relay to do the two wire taps and still nothing. Obviously, it's not working on windows, I found the kgs1992 tool which requires a version of controlbear for windows which I cannot find (found one but it doesn't recognise it when I put it in the tools folder).
tl;dr
Cannot devunlock, cannot soff, nothing. Could I possibly try changing the IMEI so that i can maybe just maybe devunlock it first? I tried putting the mobo back in the old phone, still powered up but didn't recognize the token. I'm pretty much stuck right now.
Any help would be highly appreciated and if you read the whole thing, kudos to you for standing my chatter !
i sent you a pm
also you can follow this guide which avoids wire trick
http://forum.xda-developers.com/showthread.php?t=2751187
rzr86 said:
i sent you a pm
also you can follow this guide which avoids wire trick
http://forum.xda-developers.com/showthread.php?t=2751187
Click to expand...
Click to collapse
Hi mate!
Thank you so much for your reply!
Unfortunately, rumrunnes told me to f myself lol, an error about not finding an unsecure kernel I guess, too frustrated to remember what the error was after finally finding a piece of software which seemed to do something.
Will try with the link you sent me and will come back with results!
elktw said:
Hi mate!
Thank you so much for your reply!
Unfortunately, rumrunnes told me to f myself lol, an error about not finding an unsecure kernel I guess, too frustrated to remember what the error was after finally finding a piece of software which seemed to do something.
Will try with the link you sent me and will come back with results!
Click to expand...
Click to collapse
did it tell you to be rooted first?
rzr86 said:
did it tell you to be rooted first?
Click to expand...
Click to collapse
That it did, but I was under the assumption (well all the guides I read) that you need to be devunlocked in order to root it. which I can't do. Am I missing something or is this a vicious circle ?
elktw said:
That it did, but I was under the assumption (well all the guides I read) that you need to be devunlocked in order to root it. which I can't do. Am I missing something or is this a vicious circle ?
Click to expand...
Click to collapse
just use the temproot.bat file from juopunutbear thread
then run rumrunner again
it is mentioning also in rumrunner thread
Stuck on confirm Unlock bootloader
Ok, my phone got really messed up with TWRP format bug.
Since then, I have tried RUU, different recoveries and finally got stuck with Relocked, S-ON, no ROM, no ADB on my Sensation.
When i try to unlock via Unlock_code.bit i used earlier i am able to send it via fastboot to phone where it prompts me for a choice Yes/No.
And here is funny part.
I can select No with my power button which reboots my phone and shows white screen with bootloader after it since there is nothing on it.
But, when i press Volume up and select Yes option and Power button to confirm it, nothing happens. Actually it freezes phone and i have nothing else left to do except pulling out battery and booting to bootloader.
Since it is some kind of alive, I'm sure there is some way to revive it but I guess I'm kinda not seeing right steps to unlock it, s-off again, and custom recovery and wait for twrp team or shantur to find a sollution to fix corrupted partitions.
Can you help me with unlocking?
What logs do you need?
culler said:
Ok, my phone got really messed up with TWRP format bug.
Since then, I have tried RUU, different recoveries and finally got stuck with Relocked, S-ON, no ROM, no ADB on my Sensation.
When i try to unlock via Unlock_code.bit i used earlier i am able to send it via fastboot to phone where it prompts me for a choice Yes/No.
And here is funny part.
I can select No with my power button which reboots my phone and shows white screen with bootloader after it since there is nothing on it.
But, when i press Volume up and select Yes option and Power button to confirm it, nothing happens. Actually it freezes phone and i have nothing else left to do except pulling out battery and booting to bootloader.
Since it is some kind of alive, I'm sure there is some way to revive it but I guess I'm kinda not seeing right steps to unlock it, s-off again, and custom recovery and wait for twrp team or shantur to find a sollution to fix corrupted partitions.
Can you help me with unlocking?
What logs do you need?
Click to expand...
Click to collapse
Well, i can certainly try and tell you what I did. Basically listen to the wonderful advice of @rzr86. Assuming you have tried many tools, you probably have the temproot utility. I just used that and Rumrunners, no wire trick no nothing, those were pretty straightforward and I finally managed to soff and supercid it. Afterwards I just installed 4ext recovery and was finally able to install whatever custom rom I wanted.
My problem however is now a different one. Cannot calibrate the touchscreen using the 58diag file. I'm using cgmod11 and if I run the calibration file, it gets stuck in bootloader. Standard RUU and it does nothing at all for the touchscreen. I'm pretty much stuck and out of ideas.
Aaaanyway, try rumrunners with temproot and get back to me with the results !
elktw said:
Well, i can certainly try and tell you what I did. Basically listen to the wonderful advice of @rzr86. Assuming you have tried many tools, you probably have the temproot utility. I just used that and Rumrunners, no wire trick no nothing, those were pretty straightforward and I finally managed to soff and supercid it. Afterwards I just installed 4ext recovery and was finally able to install whatever custom rom I wanted.
My problem however is now a different one. Cannot calibrate the touchscreen using the 58diag file. I'm using cgmod11 and if I run the calibration file, it gets stuck in bootloader. Standard RUU and it does nothing at all for the touchscreen. I'm pretty much stuck and out of ideas.
Aaaanyway, try rumrunners with temproot and get back to me with the results !
Click to expand...
Click to collapse
Did you had access to rom and adb to run Rumrunners utility? I have only access to bootloader and when i try to run it it hangs waiting for ADB.
Also, I'm stuck on unlock bootloader screen so probably have corrupted memory because I can't unlock it. :/
culler said:
Did you had access to rom and adb to run Rumrunners utility? I have only access to bootloader and when i try to run it it hangs waiting for ADB.
Also, I'm stuck on unlock bootloader screen so probably have corrupted memory because I can't unlock it. :/
Click to expand...
Click to collapse
do you have adb/fastboot installed?
did you enable usb debugging mode from settings?
use usb 2.0 ports not 3.0
also what windows OS do you have?
rzr86 said:
do you have adb/fastboot installed?
did you enable usb debugging mode from settings?
use usb 2.0 ports not 3.0
also what windows OS do you have?
Click to expand...
Click to collapse
I'm on Windows 8.1 64-bit, but also tried Windows 7 32-bit and Ubuntu 13.04 both 32 and 64bit.
I also tried both USB2.0 and USB3.0 ports.
Like i said, I cant enable USB debugging mode in settings since i don't have ROM now, device is empty, except bootloader without recovery and I can't find way to install since I'm Relocked and S-on.
culler said:
I'm on Windows 8.1 64-bit, but also tried Windows 7 32-bit and Ubuntu 13.04 both 32 and 64bit.
I also tried both USB2.0 and USB3.0 ports.
Like i said, I cant enable USB debugging mode in settings since i don't have ROM now, device is empty, except bootloader without recovery and I can't find way to install since I'm Relocked and S-on.
Click to expand...
Click to collapse
S-OFF requires a working rom so you can't use S-OFF method
with windows 8.1 you will face connectivity issues
type in search box how to set up adb/fastboot in windows 8 but the point is that you don't have enabled usb debugging mode
so i am not sure if you will have any success
by the way what version of TWRP did you flash?
the latest? (2.7.0)
I was using TWRP 2.7.0.0 which corrupted my partitions so i tried various recoveries to fix the situation without success.
So I tried to RUU and it also failed.
Somewhere along the way of trying to revive my phone, i used fastboot oem lock and now i somehow have S-ON device which is RELOCKED and I have no custom recovery. I can't even access HTC recovery now.
When i try fastboot flash unlocktoken Unlock_code.bin from HTCDev it prompts me with screen to choose YES to unlock or NO to unlock.
When i choose YES with Volume button and press Power button to confirm, device freezes and stays like that forever, or until I remove battery.
Selecting no reboots device and brings me back to bootloader.
*** RELOCKED ***
*** Security Warning ***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.29.0000
RADIO-11.24A.3504.31_M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
Mar 2 2012,18:14:34
culler said:
I was using TWRP 2.7.0.0 which corrupted my partitions so i tried various recoveries to fix the situation without success.
So I tried to RUU and it also failed.
Somewhere along the way of trying to revive my phone, i used fastboot oem lock and now i somehow have S-ON device which is RELOCKED and I have no custom recovery. I can't even access HTC recovery now.
When i try fastboot flash unlocktoken Unlock_code.bin from HTCDev it prompts me with screen to choose YES to unlock or NO to unlock.
When i choose YES with Volume button and press Power button to confirm, device freezes and stays like that forever, or until I remove battery.
Selecting no reboots device and brings me back to bootloader.
*** RELOCKED ***
*** Security Warning ***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.29.0000
RADIO-11.24A.3504.31_M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
Mar 2 2012,18:14:34
Click to expand...
Click to collapse
i thibk you are stuck mate unfortunately
did you try unbricking project or jtag method?
rzr86 said:
i thibk you are stuck mate unfortunately
did you try unbricking project or jtag method?
Click to expand...
Click to collapse
I tried unbricking project but it hangs on start with connecting to device or waiting for device.
As I understood, it needs to access ADB which i cant succeed.
I dont have JTAG equipment so it goes to some service to see if they could repair it.
It's such a great device, i don't want to lose it so soon