- This is a guide on how to Flash radio nothing else you will find the other items required to do the flash have been provided in the links and the zip file attached it is known that using this method you can flash radio on any rom base fully tried and tested
Can be used on Windows/now for mac aswell
This guide is for window users only
Mac users follow this guide to flash radio [Mac OS X] Flashing Radio.img on Mac (Easy!) All credit to Thekn
Also can be used to for splash screens download splash screen follow guide instead of radio use splash img and in command prompt type
Fastboot flash splash1 " name of splash".img
WARNING FLASHING RADIO.IMG IS RISKY
PLEASE READ FULLY ALL OF POST 1 BEFORE ATTEMPTING THE FLASH AND MAKE SURE YOU HAVE GOT EVERYTHING REQUIRED ASWELL AS HAVING A ROOTED RADIO S-OFF AND ENG S-OFF THEN CAREFULLY FOLLOW GUIDE AND DO STEP BY STEP DO NOT RUSH YOU DO NOT WANT AN EXPENSIVE PAPER WEIGHT
i take no responsibility for anything that happens to your phone
PHONE MUST BE ROOTED WITH RADIO S-OFF AND ENG S-OFF
Links to do this
Eng s-off with guide and links to root
[TOOL] One click S-OFF by jkoljo
Radio s-off and simunlock
[TOOL][VIDEO] One click Radio S-OFF, SimUnlock (Easy Root Guide) By jkoljo
CHECK YOU HAVE THE ABOVE DONE BEFORE TRYING TO FLASH RADIO
MUST HAVE HTC SYNC Pre installed
Link to radios
radio link From xmoo
Another radio link from mousey_
latest radio for 1.72 in 1st post By leedroid
MAKE SURE YOUR PHONE IS FULLY CHARGED BEFORE FLASHING RADIO
use zip file attached provided by Jkoljo to use follow the below instructions
HAVE YOUR PHONE PLUGGED IN AND SET AT CHARGE ONLY
USB DEBUGGING ON DO THIS BY PRESSING MENU>SETTINGS>APPLICATIONS>DEVELOPMENT>TOP OF MENU GREEN TICK IN BOX ON
Youtube Video Here
1. Read the whole of the post first
2. Download attached Radio flash.zip
3. Extract the folder to anywhere of your choice (MINE IS ON THE DESKTOP)
4. Open the flash folder
5.Download the radio you want to use from the links above .Then Drag and drop radio.img you have downloaded in to radio flash folder
6.In the folder double left click the START HERE a command prompt window will open
7. Type: "adb reboot bootloader"
The adb reboot bootloader will take the device directly to fastboot And I can confirm that this method works also with non Sense roms.
8. Once your phone has rebooted in to bootloader screen Type fastboot flash radio radio.img
9. Once its done type fastboot reboot
All done
If a flash fails error signs and fixs below
FAILED REMOTE NOT ALLOWED --- you do not have ENG S-Off go back to the start of the post and click the link for eng s-off
credits
jkoljo for tools
I do this as I enjoy it if you like my work hit the thanks button or rate my thread or buy me a beer or all three or none at all up to you.
[/B]
Donators List
*****************
leith51 said:
PHONE MUST BE ROOTED WITH RADIO S-OFF AND ENG S-OFF LINK TO DO THIS http://forum.xda-developers.com/showthread.php?t=857537
Click to expand...
Click to collapse
Nice guide! Actually with the tool you linked you will get Radio S-OFF, but as you mentioned, the phone must also have ENG S-OFF (second link in my sig)
And one should really just add the C:\androidsdk\tools after everything in path, otherwise something really important might stop working.
jkoljo said:
Nice guide! Actually with the tool you linked you will get Radio S-OFF, but as you mentioned, the phone must also have ENG S-OFF (second link in my sig)
And one should really just add the C:\androidsdk\tools after everything in path, otherwise something really important might stop working.
Click to expand...
Click to collapse
Modified guide cheers for that one will put eng-off link in tonight when I finished work
Sent with 1 hand tied behind my back
sorry to ask, can i use cwm recovery to flash radio?
No, not yet at least. Don't know why really, I just remember reading it wasn't possible. Once you've got your SDK setup and got your radio s-off and eng hboot, there really is nothing to doing it this way though.
Guide updated with link to tool for eng off
Sent with 1 hand tied behind my back
napoli26 said:
sorry to ask, can i use cwm recovery to flash radio?
Click to expand...
Click to collapse
It would be easier to flash a radio through cw but as tmh says not possible as of yet that's why I created this guide to make it that little bit easier with links to downloads and tools that's needed than having to scour the forums for the info
So till we can flash via cw the guide is here to help
Sent with 1 hand tied behind my back
Still just hangs on <Waiting For Device>
ADB picks up my device though "/
Evostance said:
Still just hangs on <Waiting For Device>
ADB picks up my device though "/
Click to expand...
Click to collapse
ok, waiting for device is cause its waiting for your device to be in 'fastboot'.
when you first checked your device being connected, its when its on, and in 'charge only mode'. you type "adb devices" to check if your device has any driver problems.
next you turn your device off, take out batt (some may need like me), and boot into recovery with pressing the on button and the volume down button. go into fast boot. (Note: now, when you type adb devices, nothing will come up, but no worries, the computer has the tools necessary and is able to connect to it via fastboot."
now you do your fastboot commands and it should detect. cheers!
Nice with this guide, to help out others, thumbs up man
Sent from my Desire HD using XDA App
agentxq49 said:
ok, waiting for device is cause its waiting for your device to be in 'fastboot'.
when you first checked your device being connected, its when its on, and in 'charge only mode'. you type "adb devices" to check if your device has any driver problems.
next you turn your device off, take out batt (some may need like me), and boot into recovery with pressing the on button and the volume down button. go into fast boot. (Note: now, when you type adb devices, nothing will come up, but no worries, the computer has the tools necessary and is able to connect to it via fastboot."
now you do your fastboot commands and it should detect. cheers!
Click to expand...
Click to collapse
Cheers for answering this is in step 12 and 13
Sent with 1 hand tied behind my back
capychimp said:
Nice with this guide, to help out others, thumbs up man
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
No problem every little helps the world of flashing
Sent with 1 hand tied behind my back
agentxq49 said:
ok, waiting for device is cause its waiting for your device to be in 'fastboot'.
when you first checked your device being connected, its when its on, and in 'charge only mode'. you type "adb devices" to check if your device has any driver problems.
next you turn your device off, take out batt (some may need like me), and boot into recovery with pressing the on button and the volume down button. go into fast boot. (Note: now, when you type adb devices, nothing will come up, but no worries, the computer has the tools necessary and is able to connect to it via fastboot."
now you do your fastboot commands and it should detect. cheers!
Click to expand...
Click to collapse
Still "Waiting for Device"
Evostance said:
Still "Waiting for Device"
Click to expand...
Click to collapse
Does your phone show white screen with fastboot usb highlighted in red ?
Sent with 1 hand tied behind my back
leith51 said:
Does your phone show white screen with fastboot usb highlighted in red ?
Sent with 1 hand tied behind my back
Click to expand...
Click to collapse
Yes, however I fixed the problem.
I opened up Device Manager on my PC
Went to Android USB Devices and updated the Driver.
Went from Android 1.0 to My HTC.
Not sure why it was like this, everything was up to date
Just booted it. My signal has gone from GPRS to HSDPA woop
Evostance said:
Yes, however I fixed the problem.
I opened up Device Manager on my PC
Went to Android USB Devices and updated the Driver.
Went from Android 1.0 to My HTC.
Not sure why it was like this, everything was up to date
Just booted it. My signal has gone from GPRS to HSDPA woop
Click to expand...
Click to collapse
So it worked then lol
Sent with 1 hand tied behind my back
leith51 said:
So it worked then lol
Sent with 1 hand tied behind my back
Click to expand...
Click to collapse
Eventually, been trying to do it for days. Just thought i'd have a look in device manager and randomly did an update and it worked
Evostance said:
Eventually, been trying to do it for days. Just thought i'd have a look in device manager and randomly did an update and it worked
Click to expand...
Click to collapse
Well I only set this guide in the last 24 hour but did it help at all
Also did you start from the top with nothing installed like sdk ???
Sent with 1 hand tied behind my back
leith51 said:
Well I only set this guide in the last 24 hour but did it help at all
Also did you start from the top with nothing installed like sdk ???
Sent with 1 hand tied behind my back
Click to expand...
Click to collapse
Yeah.
Might be worth adding what I said to the guide
Evostance said:
Yeah.
Might be worth adding what I said to the guide
Click to expand...
Click to collapse
I was going to ask if that was ok with you if a added it in the guide
At which number did you get to so I can revamp it to include it
Sent with 1 hand tied behind my back
Related
**VIDEO AT THE BOTTOM!!**
Requirements
ADB: Click here for windows or Linux or download from) Sensation S-off guide
You Will Need HTC Drivers http://forum.xda-developers.com/atta...7&d=1312092669
*DO NOT ADD "" TO COMMANDS!!!
1. On your pc click on your local disk C: Drive (or D: drive for some) (WINDOWS users: Start > My computer > Local Disk (C)
2. Create a new folder called "adb" and extract the files from adb.zip (link above) into it. Make sure it doesn't create another folder in the adb folder when extracting
3. Install HTC USB Driver 3.0.0.007.
4. Press Windows + R, it will open Run. (linux users ignore this)
5. Type "cmd". (or open terminal on linux)
6. Ensure your phone is switched on (regular home screen) and connect it by USB in charging mode
7. On your phone, Go to Settings > Applications > Development > Enable USB Debugging
8. enter the command "adb devices". This is to confirm your phone is connected. (It should come back with list of devices attached and your serial number)
9. If it is recognized, then download your official RUU, please get the same/similar version that came with your phone. If you fail then you might Brick your Device!
10. Start RUU.exe and follow on screen commands.
11. After reboot, turn phone off without fastboot on, or, take out battery and then Hold Volume down button and power on.
12. Bootloader should now read Pyramid PVT Ship S-OFF RL.
13. Remove and reinsert the battery. Press power on as normal
Optional To change to stock S-ON
PROCEED WITH CAUTION. ONLY DO THIS IF YOU ABSOLUTELY HAVE TO. BEWARE THERE IS A SMALL RISK OF BRICKING
15. Boot up into the new ROM and On your phone, Follow steps 4-8 above then continue here
16. enter the command "fastboot oem writesecureflag 3" (Thanks Dazweeja who came up with this)
17. Reboot into bootloader using "fastboot reboot-bootloader" or remove & reinsert the battery and press power on while keeping hold of volume down.
18. Bootloader should now read Pyramid PVT Ship S-ON RL.
19. Remove and reinsert the battery. Press power on as normal
USE IF SEMI BRICKED
20. IF IT DOESN'T REBOOT and bootloader says ***Security Warning**
Remove and re-insert the battery and go back into bootloader and holding Volume Down +power button select fastboot
21. Run RUU.exe to reflash stock rom. (the one u just downloaded in step 1) and then reboot. It should work now
*NOTE*
This removes ROOT and custom recovery!!
I take No Credit for the Idea!
I am in no way responsible if YOU brick your phone!
If you want to add stock SuperCID AFTER you installed RUU.exe, Then Go Here For CID's, They Must Be Your Mobile Carriers... Ex: T-Mobile USA = (Carrier"TMUS") (CID"T-MOB010")
CID CANNOT BE CHANGED AFTER S-ON, it must be done while S-off
I added a video to download! you may need to re-record
http://www.mediafire.com/?ibn7168nd2ywr5d
Good Day to You and Good Luck!
Feel free to Comment for Help
If you need any help feel free to post comments
well thanks for this guide, but we're all hoping to never send our beloved Sensation in warranty return
Yeah, I would hate to send it in.
Read Me!
Everyone should do this and then reinstall custom recovery and root. Only because if sent to warranty and they see Revolution, you are screwed.
plocri said:
well thanks for this guide, but we're all hoping to never send our beloved Sensation in warranty return
Click to expand...
Click to collapse
Nice write up and VERY Noob friendly! I was reading through and in my head, half the time, going well duh. Then it clicked, you said Noob friendly. I think it will help almost all Noobs but there will be at least ONE that F's it up!
Again, nice write up!
setzer715 said:
Nice write up and VERY Noob friendly! I was reading through and in my head, half the time, going well duh. Then it clicked, you said Noob friendly. I think it will help almost all Noobs but there will be at least ONE that F's it up!
Again, nice write up!
Click to expand...
Click to collapse
Thanks, Its funny cause im a junior member and im writing NOOB friendly threads
Well was a junior member when i wrote this lol
Just to let you know if you stay with S-OFF HTC will now...
Hboot is a different version from HTC, it ends in 10xx rather than 00xx
So even if it doesnt say revolution, they still can tell
Best to restore to S-ON which is a bit risky if you dont follow instructions to the t..
Cheers
P.S. Also why are you giving SuperCid since everyone will need to flash their Stock RUU anyway?
broncogr said:
Just to let you know if you stay with S-OFF HTC will now...
Hboot is a different version from HTC, it ends in 10xx rather than 00xx
So even if it doesnt say revolution, they still can tell
Best to restore to S-ON which is a bit risky if you dont follow instructions to the t..
Cheers
P.S. Also why are you giving SuperCid since everyone will need to flash their Stock RUU anyway?
Click to expand...
Click to collapse
nope my hboot is 1.17.0008, which is stock T-Mobile HBoot. And the SuperCID is because people are going to mess up and pick the wrong RUU.exe,
alphadog32 said:
nope my hboot is 1.17.0008, which is stock T-Mobile HBoot. And the SuperCID is because people are going to mess up and pick the wrong RUU.exe,
Click to expand...
Click to collapse
If it is stock hboot then you have missed all fastboot flash functionality that alpharev has put in their hboot.
Can you flash radio, splash and so on with this hboot you have now?
broncogr said:
If it is stock hboot then you have missed all fastboot flash functionality that alpharev has put in their hboot.
Can you flash radio, splash and so on with this hboot you have now?
Click to expand...
Click to collapse
Yes I can flash.
alphadog32 said:
And the SuperCID is because people are going to mess up and pick the wrong RUU.exe,
Click to expand...
Click to collapse
By encouraging people to install SuperCID, all you are doing is making their phone more traceable for tampering if it goes back for warranty, and allowing them to install the wrong RUU. If they don't have SuperCID, they'll get 'ERROR[131]: CUSTOMER ID ERROR' if they try to flash the wrong RUU and it will stop without flashing anything to the phone.
I know you're just trying to help, but all they have to do is run the latest released RUU for their region. Nothing more.
alphadog32 said:
Yes I can flash.
Click to expand...
Click to collapse
He means use 'fastboot flash' commands which you can't with the stock hboot.
Oh. I thought he meant ROM installing and installing root. Thank You.
Sent from my HTC Sensation 4G using XDA App
How do i know if CWM is removed?
Hi,
i did all the steps and get s-on back with stock rom.
my question is how do i know whether i have removed CWM as well? when i vol down + power, it went into bootloader. it's the same screen as when i have CWM installed. the only difference is the S-on, at least the ones i can recognize is different.
thx
here is what i need to know... i am actually getting and exchange and have to send this back in because the vibration stopped working. It as TMOUSA Sensation. So far here is what i have gathered about my phone:
Baseband/radio version: 10.42.9007.00u_10.11.9007.15_m
Build number: 1.35.401.1 cl84734
hboot: 1.17.1011
CID: T-MOB010
I looked at the http://forum.xda-developers.com/showthread.php?t=1074559 page and they listed two RUU for TMOUSA:
RUU_Pyramid_TMOUS_1.29.531.2_Radio_10.42.9007.00P_ 10.11.9007.15_M_release_193714_signed
and
RUU_Pyramid_TMOUS_1.27.531.2_Radio_10.42.9007.00P_ 10.11.9007.15_M_release_192098_signed
which one of these am i suppose to use? Will my baseband/radio be updated to a different band/radio?
radiikal said:
Hi,
i did all the steps and get s-on back with stock rom.
my question is how do i know whether i have removed CWM as well? when i vol down + power
thx
Click to expand...
Click to collapse
i will try to answer ur question.. after u went thru all the process to get s-off with the idea of installing custom roms using CWM, u will get into recovery with the steps power+vol down them u scroll down and pick recovery taking u to CWM..try now and it should take u to stock recovey, after u finally figure it this out by ur self..im pretty sure u will feel like u can conquer the android world..
Pick 1.29.xxx.x for TMOBILEUSA
HTC Sensation
RESTORED TO S-ON
STOCK HBOOT
STOCK ROM
ROOTED
Is this safe?? im planning to remove my superuser,root,CWM but keep S-OFF because im tired of worrying that my phone will die when i'm out and i won't be able to charge it
If you mess up, you may brick your device!
AFTER i DL the RUU, where do i paste it at?
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..
Finally Hyuh and Fuses released their next version of JB SOFF which now doesn't require HTCdev UNLOCK and ROOT
(after a lot of pestering from me of-course want proof?? here and here)
THIS VERSION NOW DOESN'T NEED HTC-DEV UNLOCKED BOOTLOADER
UPDATE: it is assumed that you have stock ROM and stock recovery and/or HTC unlock is failing..otherwise follow SOFF JB guide by auggie2k
UPDATE 2: it is strongly recommended to follow the SOFF JB guide by auggie2k if you already did HTCdev unlock and got unlocked bootloader . for guide click here
So for people where HTCDEV UNLOCK is Failing because of new motherboards after replacement ..THIS IS THE DOOR TO HEAVEN...ERRR I MEAN SOFF
Also for people who wants to prevent HTCDEV unlock...this is the tool for you (but it's always recommended to follow HTCDEV unlock way as the wire trick there is easier)
the new version of JB SOFF...NOW JUST requires temporary root---but worry not i have created a simple scripts(windows/linux only) to gain temp root...and by just double clicking them...you can RUN THE JB SOFF TOOL
Right now this tool supports windows/linux only
DISCLAIMER: i wont be responsible if this process bricks your device (which i highly doubt it) ..so run this tool at your own risk
PREREQUISITES:
make sure "usb debugging" is checked in settings->develop option
This tool requires HTC drivers to be installed on your pc so
1.If you people have adb/fastboot setup already then just copy the scripts
"temp_root" and "temp_root_remove" to the adb folder that you already have and run these scripts when asked(steps below)
2.If you don't have adb/fastboot setup get these HTC drivers
click here for htc drivers
install the drivers ,reboot your pc/notebook and follow the steps below to the letter
3. Uninstall HTC sync and any other device syncing softwares.. They interfere with the soff tool we are going to use (also when connecting the phone just keep it in charging mode)
Make sure you met all the step 1: Pre-requisites from the official Juopunutbear website ..i.e from here http://unlimited.io/juopunutbear.htm
(you can ignore prerequisites #1 and #2 from the site as this process is an exception)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
NOTE: both the "temp_root" and "temp_root_remove" files need to be run..when device is connected to pc normally (i.e from lock screen or home screen)
STEPS TO RUN THIS TOOL:
IMP:
1. Make sure you removed the back cover of the phone before starting the below process
2. Also you need the controlbear files ..if you dont have them ..refer point #6 below first
3. Also Sdcard mostly will be wiped ..so use a spare unsed sdcard or do a backup of your current sdcard
1.get this temproot-sensation-windows zip file
TEMPROOT ZIP
2.Extract temproot-sensation-windows.zip into a directory on your computer.
3.Plug your HTC SENSATION/XE/4G into your computer via USB. (keep the connection in "charging" mode)
Recommended: Plug your device’s USB cable into the back of your computer if you’re using a desktop PC.
4.Enable USB Debugging on your HTC sensation. Settings >> Develop Options >>USB debugging (checked)
5.Double click temp_root.bat to run the script and wait until it completes. Don't touch the device during the entire process.
Note: if you didn't get the controlbear tools within some time.. To get back the phone in working condition again do the step #9 after this step #5. That would take the phone to normal working condition again
6.get the latest control bear from http://unlimited.io/jb_pyramidlocked.htm
download the "windows Ice cream sandwich" one ("windows Gingerbread" one if on gingerbread ) from the downloads section of the above page
NOTE: you should download the right tool.. The tool will have NOHTCDEV in the name of the downloaded zip file.
NOTE2: links have been removed from the official site....download the tool from below link
ControlBearRelease_pyramid_ICS_WIN_NOHTCDEV.zip
(for OTHERS searching for Windows variant of SOFF tool which involves HTCDEV unlock ..download them from here
7.RUN THE JB TOOL or control-bear now
Follow the Complete set of Instructions(Step 2 | ControlBear: and Step 3 | Wire Trick: ) on running the controlbear from the official Juopunutbear website ...i.e from here http://unlimited.io/juopunutbear.htm
(optional)
excellent guide on how to run juopunutbear SOFF is here (by auggie2k)
JB SOFF GUIDE ---START FROM STEP 5---I INSIST YOU PEOPLE TO "START FROM STEP 5"
8.once control Bear is over..don't do anything to the device and let it be connected--and if the device is left in bootloader---reboot manually using power and vol up/down
9.now you guys need to remove the temp root which you have created first
to do that Double click temp_root_remove.bat to run the script and wait until it completes. Don't touch the device during the entire process
10.congratulations you guys now have a proper SOFF
Click to expand...
Click to collapse
NJOY YOUR NEW SOFF ...HUGE THANKS TO HYUH AND FUSES FOR THIS NEW TOOL
Click to expand...
Click to collapse
NEW
ONE CLICK ROOT TOOL
ADDING A NEW TOOL WHICH JUST ROOTS YOUR DEVICE (no recovery required )
this is a replicated work (with minor changes of this post)
this tool only works with SOFF devices, Also with devices having HTCdev unlocked bootloader while being SON.
STEPS:
1.get the new root tool from root-sensation-zip
2.extract the zip
3.remove the files adb.exe, AdbWinApi.dll , AdbWinUsbApi.dll
(if you dont have any adb/fastboot setup don't delete these and skip step 4 )
4.copy the rest of files to the your adb/fastboot folder
-> if you did SOFF using this guide then copy the reset of files to the temproot-sensation-windows folder which you
have downloaded during SOFF procedure
5.connect your device normally (from lock screen or home screen) to pc
(NOTE: avoid usb hubs and usb 3.0 ports while connecting ..just connect the device directly to pc/laptop)
6.double click on root.bat file
-> when the message "PRESS ANY KEY WHEN THE PHONE BOOTED PROPERLY/COMPLETELY" pops up in the command window
press any key once the phone is completely booted
-> wait until root is success and once success message "EVERYTHING DONE..ROOT SUCCESS...ONE FINAL REBOOT NOW" pops out
without any errors...you are rooted completely
Click to expand...
Click to collapse
Click to expand...
Click to collapse
CHANGELOG:
EDIT:
1.Did some modification to original scripts(no need of manual reboot now )
2.Adding the linux tar files thanks to "TheSh4wn"
for linux scripts click here
3.Also adding a copy of these scripts as attachments (in case DB link fails )
4. Adding Dev-Host mirrors
temp-root-linux
temp-root-windows
EDIT2: corrected a small typo in linux scripts ..thanks to "splattersxda"
EDIT3:
AUTOMATED UTILITY FOR SOFF AND OTHER FLASHES
also for soff there is a great tool made by "kgs1992"
here is the link to the tool KGS SUPER UTILITY
it not only has automated SOFF feature ..but tons of others which will make your life pretty easy
for more details please check the above link
Click to expand...
Click to collapse
TROUBLESHOOT:
1.temporray root is failing or errors in the temporary root command window
Solution:
Make sure you connected your device properly.. No usb hubs, no usb 3.0 ports and connect the phone to back of pc.. If using pc..(un install htcsync and see too)
Click to expand...
Click to collapse
2 . controlbear is failing by saying no root
Solution:
Temp root failed.. So run temp root again.. Also see troubleshoot 1 for running temp root properly
Click to expand...
Click to collapse
3. wire trick problems ? want some tips ?
Solution:
look here
and thanks to "kgs1992" for his informative post
Click to expand...
Click to collapse
4. tired of doing doing wire trick.. So Want to revert back to normal Working condition
Solution:
If you are stuck at Juopunutbear screen
CORRECTION: THE OPTION a) ONLY WORKS WITH controlbear version which involves HTCDEV unlocked, also needs unlocked bootloader
a) if you can go to bootloader.. Then connect the phone to pc.. From fastboot (device should read fastboot usb)
Go to controlbear folder (from where you ran controlbear until now) in pc..
Open command window there
(hold shift + right click->open command window here)
Once you got the window.. Type this
"ControlBear.exe -f" without quotes
This will revert back the phone to proper working condition
b) if you can't go to bootloader.. But stuck at Juopunutbear/black/normal screen... Connect the phone with this screen only to pc
And repeat the above process.. But type "ControlBear.exe -r" without quotes in the command window
During this process.. You are getting cannot detect device errors?
Then try the solution for troubleshoot 1
c) still cant recover the things ? then you need to unlock your bootloader and then try step 3 and 4 from "ROM/Data Recovery" sub section from the below troubleshoot page
FOR MORE TROUBLESHOOT CHK THIS JUOPUNUTBEAR TROUBLESHOOT
This will bring your phone out from Juopunutbear/blank screen
once restoring sdcrad, recovery and boot ..using the above commands was done ..you need to run the
remove_temp_root.bat too ..that will give you proper working phone again (i.e. step 9 )
Click to expand...
Click to collapse
Click to expand...
Click to collapse
wow, that is fantastic...you guys are doing some amazing work!
Can't wait to give this a go, thought it be ages until I would be able to root and s-off, so thanks for your work!
Sent from my HTC Sensation XE with Beats Audio Z715e using XDA
Once the above process is complete do we need to go through the normal procedure to add permanent root?
Sent from my HTC Sensation XE with Beats Audio Z715e using XDA
work for me! ICS T-mobile hboot 1.27, new motherboard
ceulem said:
work for me! ICS T-mobile hboot 1.27, new motherboard
Click to expand...
Click to collapse
gratz bro
Wow!
Thanks a lot bro!
unfortunately, i'm not able even to get temproot:-( but i'll try it later using my personal nbook, maybe some company apps(fwall....)are messing it.
S-Off S-OFF S-OFF Thank you very much
This is really good! Well done to all the devs for supporting our device
Sent from my HTC Sensation XE with Beats Audio using xda premium
will the wire trick be need for this?
spidey88 said:
will the wire trick be need for this?
Click to expand...
Click to collapse
Yes you need the temp root first, then do the JP s off procedure.
Sent from my HTC Sensation XE with Beats Audio Z715e using XDA
thanks ganesh for ur work... ill give it a try later.
gsmyth said:
Yes you need the temp root first, then do the JP s off procedure.
Sent from my HTC Sensation XE with Beats Audio Z715e using XDA
Click to expand...
Click to collapse
wondering where to get the wire..*looking for unused cable*
spidey88 said:
wondering where to get the wire..*looking for unused cable*
Click to expand...
Click to collapse
Someone recommended a wire from an Ethernet cable (there's a several strands inside it and its easy to split), that's what I am going to try, have u got a patch lead lying about that u don't need?
Sent from my HTC Sensation XE with Beats Audio Z715e using XDA
i did the htc dev method two weeks ago and now don't have warranty
for me it did not work... i tried 4 times
hboot1.29
Do not remove sdcard from phone
Do wire-trick now!! Check the instructions at http://unlimited.io
=== Waiting device....
(11/45)
Found device... Please wait...
Getting into bar.....
Raising Glass
SUCCESS - Taking a sip.
SUCCESS - Beer is tasty.
SUCCESS - Beer is tasty.
SUCCESS - Beer is tasty.
SUCCESS - Beer is tasty.
SUCCESS - Buddies and Beer
Checking alcohol level......
Let's take one more......
S-OFF Failed
Errorcode: 66732337
ErrorMsg: Still sober
Quit....
Press ENTER to exit.....
Click to expand...
Click to collapse
still the same error
purebeatz said:
for me it did not work... i tried 4 times
hboot1.29
still the same error
Click to expand...
Click to collapse
Pb try it again.. That error corresponds to wrong timing of wire trick... Some people even tried 20-30 times.. The wire trick is fun... Do it do it again
Sent from my pyramid.. Through blazing fast sonic waves
Hmmm, it's S-OFF'ed, but the bootloader doen't allow to flash recovery / splash / whatever...
What's to do now?
ToM
ganeshp said:
Pb try it again.. That error corresponds to wrong timing of wire trick... Some people even tried 20-30 times.. The wire trick is fun... Do it do it again
Sent from my pyramid.. Through blazing fast sonic waves
Click to expand...
Click to collapse
ok ill try!
is it possibl to restore the data from the sdcard.img? in my dumpness i forgot to backup all datas!
This thread is just to direct all the noobs into the right direction, related to root and flash new roms in the Inspire 4G.
[*]Rooting and reverting to stock
Due to the retirement of the Hack Kit, rooting methods have been reduced to:
http://forum.xda-developers.com/showthread.php?t=2168500
or if you are skilled in using adb and fastboot commands:
http://tau.shadowchild.nl/attn1/?cat=6
If you are still stuck and want to revert your phone back to out of the box, then use Marsdta's Guide:
http://forum.xda-developers.com/showthread.php?t=1396229
or Gene Poole's Tool (that will revert also S-OFF):
http://forum.xda-developers.com/showthread.php?t=1208507
[*]Flashing a Custom Rom
To flash a custom rom you need to be rooted and S-OFF (if u used the Hack Kit) or have and unlocked bootloader using HTCDEV tool (wich I don't suggest)
Once u are S-OFF and have CWM or some other custom recovery installed (I personally prefer 4ext) you have to follow these steps (read the dev's thread about particularities. This is just a general guide on how to do it):
Download the custom rom .zip file and put it in your sdcard. Make sure that u check md5sum first just to avoid bootloops.
Reboot phone in recovery. There are many ways to do that, the first can be using Rom Manager (I don't suggest using it for anything else but that) and choosing reboot in recovery option. The second way is to boot in bootloader (press power down and reboot choosing hboot) or just turn phone off and power it up pressing power and volume down. And the last is to use adb commands. Plug the phone as charge only with usb debugging on, open a cmd as admin or terminal as root in your PC and then type adb reboot recovery.
Once in recovery, you need to do a full wipe (wipe data / factory reset and wipe cache + dalvik cache). You can also format some other partitions such as data and system, but the full wipe will work.
When full wipe is finished, go to flash zip from sdcard option, choose zip file and then flash that file.
Reboot the phone once it has finished flashing and wait for the device to fully reboot. The first boot will take a while (probably longer than usual) so don't get scared.
If you flashed a CM based rom, you need to flash google apps separately as well, so find the gapps file corresponding to your rom and flash it in the same manner as above described.
Trouble Shooting
Bootloops: If your phone repeats over and over the bootanimation, don't panic, you are not bricked. Something must have gotten wrong but you can reboot in recovery and re flash the rom as previously described. If bootloop is still there, then try downloading the zip again or choose a diffrent rom.
Factory Reset: If you factory reset the phone and you are not stock, then the phone won't have a rom...you will get stuck in the splash screen (white screen with the green HTC). Just do as described above, get a rom to the sdcard and then flash it. You are not bricked, you are just stuck
Well, this was just to try to point you in the right direction. If you think that I missed something, feel free to tell me and will add it to the OP.....Salud! :good:
Reserved just in case
Well done glevitan. On a side note, I finally understood how to use adb. Thanks.
Sent from a dream.
Teichopsia said:
Reserved just in case
Well done glevitan. On a side note, I finally understood how to use adb. Thanks.
Sent from a dream.
Click to expand...
Click to collapse
Thanks, let's hope that people find it usefull...
To help your thread going however 'slightly' off topic it may be, but since you did mention adb, I finally managed to get apk multi tool and sdk manager installed, and with a slight hiccup getting the adb to recognize my device (I started all of this last night), I believe I have everything I need?
Now I need to learn what I can do with those.
All of this would have taken me half the time if I were 15 again
Sent from a dream.
Teichopsia said:
To help your thread going however 'slightly' off topic it may be, but since you did mention adb, I finally managed to get apk multi tool and sdk manager installed, and with a slight hiccup getting the adb to recognize my device (I started all of this last night), I believe I have everything I need?
Now I need to learn what I can do with those.
All of this would have taken me half the time if I were 15 again
Sent from a dream.
Click to expand...
Click to collapse
hahaha...ummmm you shouldn't have problems. Just install SDK and apk multi tool in the SDK>tools folder or somewhere else. Then from command prompt you should be able to run the commands for the apk multi tool. I use the apktool and I have no problem at all. The main thing is to have adb installed...but there's no need to have the phone plugged to use the apk tool.
In the case of your device, make sure that u have the HTC drivers installed, if you have HTC Sync, you should have them...to try that just plug the phone as charge only, make sure that usb debugging is on and then open a cmd as admin and type adb devices...you should see your HTCserialnumber....
I didn't know I didn't need to have the cell plugged in, nice to know.
I had done all of that and it was working.... IT WAS WORKING , I decided to move a few folders around, something got messed up, tried placing them where they were, still no go, it's not recognizing my device anymore.
Don't worry, I'll figure it out eventually, but the problem is my head is going to start hurting any minute now. I'll be back shortly to ask you something you mentioned and I've read which I simply don't get - well, maybe not as shortly as I would like.
Edit: whenever I run the adb devices command it has to be done withing the folder where the adb.exe is located, right?
2nd edit: found it and it's working.
To run the adb devices command, which means going to that specific folder, would be seperate from using the apk tool? Would have moving the folders around somehow messed up the way apk tool would work? Im not even sure if im asking the right question
3rd edit: when you said to install the apk tool and sdk in the same folder, well, I already installed both of them to the default location.... what do you mean by that? Should I move them if they are not there? And if I may ask why?
Sent from a dream.
Teichopsia said:
I didn't know I didn't need to have the cell plugged in, nice to know.
I had done all of that and it was working.... IT WAS WORKING , I decided to move a few folders around, something got messed up, tried placing them where they were, still no go, it's not recognizing my device anymore.
Don't worry, I'll figure it out eventually, but the problem is my head is going to start hurting any minute now. I'll be back shortly to ask you something you mentioned and I've read which I simply don't get - well, maybe not as shortly as I would like.
Edit: whenever I run the adb devices command it has to be done withing the folder where the adb.exe is located, right?
2nd edit: found it and it's working.
To run the adb devices command, which means going to that specific folder, would be seperate from using the apk tool? Would have moving the folders around somehow messed up the way apk tool would work? Im not even sure if im asking the right question
3rd edit: when you said to install the apk tool and sdk in the same folder, well, I already installed both of them to the default location.... what do you mean by that? Should I move them if they are not there? And if I may ask why?
Sent from a dream.
Click to expand...
Click to collapse
What I did, that doesn't mean that is the correct way.... I installed SDK and in the tools folder I installed the apktool. You don't need to be in that folder to run the adb command...I don't do it that way...I just run the command from where I am...
glevitan said:
What I did, that doesn't mean that is the correct way.... I installed SDK and in the tools folder I installed the apktool. You don't need to be in that folder to run the adb command...I don't do it that way...I just run the command from where I am...
Click to expand...
Click to collapse
Right now I feel I'm way over my head. And that includes my choice of using eclipse. I'm not even sure what I can do with all these tools...
My hat off to you guys.
Sent from a dream.
Teichopsia said:
Right now I feel I'm way over my head. And that includes my choice of using eclipse. I'm not even sure what I can do with all these tools...
My hat off to you guys.
Sent from a dream.
Click to expand...
Click to collapse
I don't know either....but it is worth trying....see Adam's tutorials...are awesome. Maybe some day I will learn what to do with all this as well!! lol
glevitan said:
I don't know either....but it is worth trying....see Adam's tutorials...are awesome. Maybe some day I will learn what to do with all this as well!! lol
Click to expand...
Click to collapse
Back and forth
I don't believe that was the link you gave me on the other side. Perhaps posting over here will refresh your memory...?
Sent from a dream.
Teichopsia said:
Back and forth
I don't believe that was the link you gave me on the other side. Perhaps posting over here will refresh your memory...?
Sent from a dream.
Click to expand...
Click to collapse
AHH I was talking about Adamsoutler´s tutorial in XDA TV. He explains how to set SDK and develop APKs....it is awesome!..look at the XDA TV thread.
Bump.
Sent from a dream.
not able to go back to stock
I unlocked my htc inspire and tried to root it. Now i ended up with a ccwm recovery and S on unlocked bootloader .
I tried to go back to stock rom and have tried this guide and other guides also but was unsuccessful . My phone is running gizroot v2 but with taht the wifi mac address is unavailable . So i canniot access wifi .
If i put PD98IMG .zip in the root directory then it does not prompt me to any installation in the bootloader .
Please help
krjkinan said:
I unlocked my htc inspire and tried to root it. Now i ended up with a ccwm recovery and S on unlocked bootloader .
I tried to go back to stock rom and have tried this guide and other guides also but was unsuccessful . My phone is running gizroot v2 but with taht the wifi mac address is unavailable . So i canniot access wifi .
If i put PD98IMG .zip in the root directory then it does not prompt me to any installation in the bootloader .
Please help
Click to expand...
Click to collapse
RUUs can not be flashed with an unlocked bootloader. Relock it first, then run the RUU.
Can some one help me. I want to riot my htc inspire 4g
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
romanvaldezo said:
Can some one help me. I want to riot my htc inspire 4g
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
This post is no longer timely. The tool it refers to has been retired. You can no longer get S-Off, but you can unlock the bootloader: http://forum.xda-developers.com/showthread.php?t=2169515.
hey
hey not being mean but you guys dont actually help ive been on this site looking for a tutorial for weeks and cant find one i need to root my htc inspire plzz help
rty123456 said:
hey not being mean but you guys dont actually help ive been on this site looking for a tutorial for weeks and cant find one i need to root my htc inspire plzz help
Click to expand...
Click to collapse
Hey, not being mean, but did you read the post right above yours...? Or anything in the Desire HD forums, which is the same phone and is more populated?
rty123456 said:
hey not being mean but you guys dont actually help ive been on this site looking for a tutorial for weeks and cant find one i need to root my htc inspire plzz help
Click to expand...
Click to collapse
Then are not reading the OP. You have all the information neeeded in there...if your first post in here Is to whine, then you have not Read the rules or understand the spirit of xda.
Follow the instructions And You will be fine, if You don't Get them take time To learn. Nobody Is going To do your homework.
I just recently rooted my inspire it took some time reading and a few attempts to get it down. But after my homework and grasping the concept it was fairly easy.
Sent from my Desire HD using xda app-developers app
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