Related
How to Root CDMA Desire! HOOT 0.98
Original post can be found HERE/
As many of us have researched, the Hoot on the desire is 0.98 and is hard to find any other instructions to root. Im a DROID user on the Cell South network and Last night got my hands on a Desire. The root was tricky but my friends desire is running Cyanogenmod no problem
Note: I take no resposability if you brick your phone an/or any other devices. This is just how i did it.
Instructions:
1: Download unReVoked Rooting tool. Click Here
(This tool works best if you are on linux ubuntu, windows users must install HTC Sync for the ADB Drivers)
2:Linux:
>Extract reflash, Open Terminal, Place your desire in Charge Only Mode with Debugging enabled.
> Plug in the phone and give it a few seconds to be reconized fully.
> In terminal type: cd /path/to/unrevoked then chmod +x reflash then sudo ./reflash and finally
> If it asks you for a password, use your root/user password. Unrevoked should start working and detect the phone.
Windows:
>Again Phone must be in Charge Only Mode with Debugging Enabled.
>Download the unrevoked package, Run the EXE. If you have HTC Sync installed it should detect the phone.
>Works same as Linux, Patience is a virtue.
(DO NOT CLOSE THE PROGRAM UNTIL IT SAYS ITS DONE!!. YOU WILL BRICK YOUR ****)
3. Unrevoked will begin working its magic, Your phone will reboot about 2-3 times. Be Patient!
> When its all over you will be brought to the recovery menu. (Green writing)
> Ours spit out some error code, but i restarted the phone and re entered recovery mode by holding down (Vol Down + Power)\
>You will be brought to a white screen HTC Labeled, Wait for hoot then do volume down to recovery, Push power.
4. After you have re-entered, Go down to manage and backup to Backup your stock ROM.
>Push back after the process has completed.
> Wipe the Device, then press back
> Go to mount and unmount storage.
> Mount your storage card to the computer.
5: After you have your phone plugged in make a folder on the memory card called Roms and Kernels (Whatever you prefer really).
> Go download the latest nightly/stable rom from the BravoC thread.
Click here for BravoC Roms
6:After download, Place the zip into the memory card in the Roms and Kernels folder i asked to make.
> On the android, when the file is done copying, unmount the memory card from the pc.
> Then in recovery menu, install zip file.
> Choose from SD Card
> Go to Roms and Kernels Folder.
> Select the file you downloaded.
> Click yes and enjoy!
7. You can download the Google Addon for your desire Here
YOU HAVE SUCCESSFULLY ROOTED and flashed YOUR DESIRE, This works on Cellular South, US Cellular, and other BravoC Desires with the 0.98 Hoot.
Don't forget to say thanks!
I have been looking to do this for a long time. And it worked great, the only problem is I don't understand the rom.
in the second step when it says:
> If it asks you for a password, use your root password. Unrevoked should start working and detect the phone.
you should use your user password, not the root password.
(of course your user must be a member of the sudoers group)
No need for passwords. But wish I had my HTC Clock and Calendar back.
You lose some you gain some buddy. there is a clock, look up fancy widget 1. 3 apk in your google box. and you can get it free.. Not gnna post a link cause of the rules. but its the ported HTC clock.
Thanks, but didn't care for that clock, saw one for $2 but couldn't get it to display so I uninstalled it. I know about "Win some, loose some" After all I have had a WinMobile phone for a couple years. And started flashing ROM's since the Touch Pro. My problem is, by the time I find a perfect ROM, I upgrade to a different phone. Did that with the TP1, and again with the TP2. Now the search begins again with the Desire. Actually the only problem I had with the stock 2.1 rom was that I kept running out of room. But thanks for the help and I am off again to find the perfect CDMA ROM!!!
awesome! just got my desire last night. to be sure after i root i will lose clock and calender? also (sorry, maybe a noob question) i like the sence, wasnt a big fanof AOSP and i notice all the Rom's here seem to be for GSM not CDMA. if i was to root and run the stock 2.1 and get rid of all the junk apps in it would that be possible? and lastly, does anybody know if there is a RUU for Csouth's desire incase i need to go back to original like we could with the hero?
leadfoot9281 said:
awesome! just got my desire last night. to be sure after i root i will lose clock and calender? also (sorry, maybe a noob question) i like the sence, wasnt a big fanof AOSP and i notice all the Rom's here seem to be for GSM not CDMA. if i was to root and run the stock 2.1 and get rid of all the junk apps in it would that be possible? and lastly, does anybody know if there is a RUU for Csouth's desire incase i need to go back to original like we could with the hero?
Click to expand...
Click to collapse
1. You shouldn't lose clock and calender.
2. After you root, install Titanium Backup. It will allow you to uninstall those apps you don't want.
3. No RUU's available for CDMA at this time. Make sure you do a nandroid backup immediately after rooting
uhh buddy there is a RUU out for it. Thats what the recovery menu basically is, the installer for the zip file. Cyanogen Mod is the ROM. To keep your Cellular South ROM you just backup like the instructions say, if you ever want to go back you Wipe the device and restore the image from your SD Card. Theres a link to Cyan in the main post. RC1 Came out yesterday!
[SP]JESTER said:
uhh buddy there is a RUU out for it. Thats what the recovery menu basically is, the installer for the zip file. Cyanogen Mod is the ROM. To keep your Cellular South ROM you just backup like the instructions say, if you ever want to go back you Wipe the device and restore the image from your SD Card. Theres a link to Cyan in the main post. RC1 Came out yesterday!
Click to expand...
Click to collapse
when i said RUU i meant a stock RUU put out by Csouth just like they gave us for the hero. it would put your phone back exactly like it was when you took it out of the box so if you needed to take it back to the store for whatever reason you could simply use it to go back to original.
ok guys one more question, i got root just fine. gonna keep running my stock rom but when i installed titanium backup (never used it before) it said busybox not installed and i dont have root access. i do have root cuz shoot me is working. i searched busybox in market and it says wont work for the desire yet.. any ideas? i ran into this problem with SU on my hero and had to change to the chainsDD version of SU. could this be the same thing?
ALSO: trying to use ADB and it says permission denied.
EDIT . Spoke to soon and did unrevoked forever and seems to all be working now.
Hi,
I am new to this sort of thing. I just got my phone and I am following this guide and I am thinking about trying it on my phone. Here's what I've got:
HTC Desire
Running Android 2.1
Alltel is my service provider
This is the information I get when I boot up my phone while holding the "back" button:
Bravoc DVT2 Ship S-ON
HBOOT-0.98.0000
MicroP-051e
Touch Panel-SYNT0101
Radio-2.05.10.08.11
Jul. 5, 2010, 19:14:11
Will this guide work with my phone?
The sole reason I'm wanting to do this is because I want to use a Wii remote with emulators on my phone. I am aware that there is an Android app that will do so, but that app doesn't work with phones that use HTC's "sense". I'm also aware that there are certain third-party wireless bluetooth controllers, but don't want to use them. So, I've been told that my only option is to root the phone so that I can have a custom ROM on it. If there is another way to do this without rooting, I'd love to know what that is.
Any information pertaining to any of this would be very helpful. Thanks in advance.
hovage said:
Hi,
I am new to this sort of thing. I just got my phone and I am following this guide and I am thinking about trying it on my phone. Here's what I've got:
HTC Desire
Running Android 2.1
Alltel is my service provider
This is the information I get when I boot up my phone while holding the "back" button:
Bravoc DVT2 Ship S-ON
HBOOT-0.98.0000
MicroP-051e
Touch Panel-SYNT0101
Radio-2.05.10.08.11
Jul. 5, 2010, 19:14:11
Will this guide work with my phone?
The sole reason I'm wanting to do this is because I want to use a Wii remote with emulators on my phone. I am aware that there is an Android app that will do so, but that app doesn't work with phones that use HTC's "sense". I'm also aware that there are certain third-party wireless bluetooth controllers, but don't want to use them. So, I've been told that my only option is to root the phone so that I can have a custom ROM on it. If there is another way to do this without rooting, I'd love to know what that is.
Any information pertaining to any of this would be very helpful. Thanks in advance.
Click to expand...
Click to collapse
Rooting is the only way to flash a custom Rom and yes unrevoked will work with your hboot. Not sure about any of the wii stuff your talking about tho.
Sent from my HTC Desire CDMA using XDA App
Thanks. And one other question I forgot to ask: Suppose I do this and an update to android 2.2 comes out for my phone. What should I do then?
If they give you a ruu just do it like normal, but as soon as they do cone out with a ruu for it whether its uscc or cellular south, there will be a custom Rom made from it.
Sent from my HTC Desire CDMA using XDA App
Fail
unrevoked "fails to push recovery image"
any advice?
blind_fury6342 said:
unrevoked "fails to push recovery image"
any advice?
Click to expand...
Click to collapse
Check the MD5 checksum for the Reflash_Package.exe
Most likely a corrupted installation.
I have the same phone/hboot/ etc...
I was able to root with unrevoked, no problem. I did get an error in the recovery at the end but per this guide, that seems to be normal.
I was able to run a backup in nandroid, which also worked, but I noticed S-on didn't change to S-off. Is this normal for this phone? Should I try rerunning unrevoked?
dills2214 said:
I have the same phone/hboot/ etc...
I was able to root with unrevoked, no problem. I did get an error in the recovery at the end but per this guide, that seems to be normal.
I was able to run a backup in nandroid, which also worked, but I noticed S-on didn't change to S-off. Is this normal for this phone? Should I try rerunning unrevoked?
Click to expand...
Click to collapse
I had this same issue. I did some research and there is a thread on unrevoked wiki that has an updated unrevoked-forever.zip to flash that gives us successful S-off. There seems to be a problem with S-off ing this route though. After it was complete, the APN info was gone and MMS settings were blank. I used APN backup/restore to put APN info back in, but still would not send/receive. I had to restore MMS via Goldcard, which changed back to S-on. Any ideas?
Since this seems to be the only generic CDMA Desire thread, I have some questions for other CDMA Desire owners. First, the only rom I can find with everything working is CM, but not sure I like the way it looks. I'm looking for a Sense rom. Anyone running a stable one? Second, I have found a rom called Ultimate Droid 2.3 and 2.4 for CDMA desire that looks worth trying. Anybody running it or tried it yet? 3rd, is there any other good forums specifically for CDMA desire? I am sick of having to weed through the billions of GSM threads to find a CDMA one...
link to Ultimate Droid roms: http://theultimatedroid.com/forum/index.php?/forum/33-htc-desire-releases-cdma/
I am having some bizarre problems after running the ace hack kit to root my Inspire HD. Basically after running step 3 3 S-OFF, SuperCID and More
I cant get access to internet, ie browser, google network etc.
Phone works, sound is ok.
I tried to restore to stock and redo. but I've gone through this loop a few times. and now I'm stuck in no-mans land. cant get completely back to stock and cant get to a full root.
problem originated the first time through when I did not uninstall the HTC sync - I didnt realize it was running as I only installed for the driver.
Then when repeating, I got an incoming call during the process. I think this disrupted the script.
Any ideas
Tonyeff said:
I am having some bizarre problems after running the ace hack kit to root my Inspire HD. Basically after running step 3 3 S-OFF, SuperCID and More
I cant get access to internet, ie browser, google network etc.
Phone works, sound is ok.
I tried to restore to stock and redo. but I've gone through this loop a few times. and now I'm stuck in no-mans land. cant get completely back to stock and cant get to a full root.
problem originated the first time through when I did not uninstall the HTC sync - I didnt realize it was running as I only installed for the driver.
Then when repeating, I got an incoming call during the process. I think this disrupted the script.
Any ideas
Click to expand...
Click to collapse
It might be because you are still on the downgraded rom and radio...which if you stopped after step 3, then you probably are
Try flashing this
http://forum.xda-developers.com/showthread.php?t=1058042
It's a rooted stock rom with all the updates, should get everything up and running...then from there you can flash a custom rom if you prefer....
I'm actually kinda stuck between the two. not rooted so I cant run clockwork to flash, but not stock so the root script doesnt run clean.
Tonyeff said:
I'm actually kinda stuck between the two. not rooted so I cant run clockwork to flash, but not stock so the root script doesnt run clean.
Click to expand...
Click to collapse
Well that rom can't be flashed using clockwork.....you have to flash that one through hboot....
So if you boot into hboot at the very top it should say whether you are s-off or s-on...if your s-off you are good to go...
If you dont know how to get to hboot...its easy...
-turn off fast boot
-shut down phone
-turn on phone by holding down the power button and volume minus button at the same time, and hold it till the hboot screen loads..then release.
thanks
I have S-off, and I know how to get into Hboot, but I've never used it before.
I've been doing the trial and error thing and its not working too well....
so let me ask a few questions.
I take it that the rom.zip has to be on the sd card. doest the SD card need to be formatted in a specific way?
does the rom file need to be named anything specific?
once I get into Hboot, I believe the optin would be to select recovery.
Will that give me a prompt to select the rom file?
Tonyeff said:
thanks
I have S-off, and I know how to get into Hboot, but I've never used it before.
I've been doing the trial and error thing and its not working too well....
so let me ask a few questions.
I take it that the rom.zip has to be on the sd card. doest the SD card need to be formatted in a specific way?
does the rom file need to be named anything specific?
once I get into Hboot, I believe the optin would be to select recovery.
Will that give me a prompt to select the rom file?
Click to expand...
Click to collapse
Instead of answering each specific question..I'll just post the steps, which should answer all your questions....
-Download the rom, (I would suggest the one that allows for side loading, but either is fine)
-rename the zip to....PD98IMG.zip (it has to be named exactly that)
-place it on the root of your SD card (meaning not inside of any folders)
-unplug you phone from your computer
-boot into Hboot....when you get there, dont press anything, just wait...it will automatically locate the zip....the first 2 attempts will fail, then the 3rd one will work....it will then ask you if you would like to update
-push volume up to update
EDIT: no need to format the sd card and when flashing a PD98IMG.zip, you never go into recovery....
EDIT2: once you get this flashed, you can then then download rom manager from the market, and flash clockwork recovery....which will allow you to flash any of the other custom roms using recovery....
If you're S-OFF, then you don't need anything special with teh SDCard (gold card not needed with S-OFF). Just rename the file PD98IMG.ZIP and be sure it is in the root of the SDCard. Don't worry too much; this method is more foolproof than others as the HBOOT does sanity checks on the image files in the zip and won't flash anything but the correct image to the correct partition.
Thanks guys, this worked. I'm back in business... trying not to screw thinkgs up
-my previous experience was rooting a nookcolor, which was a whole different process, since the SD has boot priority.
I recently "unlocked" my HTC Sensation 4g through HTC's official method. However, after successfully unlocking it, my phone is still set on S-On. Because of this, I am not recognized as a superuser, and so I cant boot into Clockwork Mod Recovery. Can anyone who knows more than me about this please give me a hand? This is my first time attempting any of this.
to make sure i understand this correctly- your phone now says "unlocked" at the top,but is still s-on?
what have you done to root?
once you have a truly unlocked bootloader,you can install a recovery thru that bootloader,and then flash superuser in that recovery.
having superuser permissions within a rom and being able to boot to a recovery shouldnt have anything to do with the bootloader.
if you are unable to install clockwork,or some other custom bootloader thru htcs "unlocked" bootloader,then they have lied to us... its not truly unlocked. that or something happened during the unlock process,possibly.
sorry im not of more help,its been awhile since i looked at the developer website. are there support forums there?
if everything is functioning correctly and you cant load whatever you want thru hboot,this unlock program is a joke. you could have gotten s-off with revolutionary or an xtc clip and not alerted them to the fact that you were messing with software and potentially "voided all or parts" of your warranty.
please keep us updated on this- im very interested to know how it turns out.
Thats exactly what it says. The method I used is on the front page of the htc dev site.
(the forum wont let me post outside urls yet)
The top of my H-boot screen says
"*** UNLOCKED ***
PYRAMID PUT SHIP S-ON RL
HBOOT-1.80.0000
eMMC-BOOT"
So this is a problem. I think...
I just figured the official method through HTC would be the easiest and safest
Oh and when I try and flash Clockwork Mod Recovery through ROM manager this is the message I get
"You must root your phone for ROM Manager to function. Superusuer was not found at /system/bin/su or /system/xbin/su. Use Google Search on your computer to find instructions to root your phone."
or
"An error occurred while attempting to run privileged commands."
So what have you done to root besides unlocking the bootloader? Just tried to install rom manager and clockwork?
Unless you have done something else,you are not rooted,you are just unlocked. Search the sensation forum for a PxxxIMG file that is clockwork recovery. When named that,and placed on root of your SD,hopefully your hboot will find and flash it.
Once you have done that,delete the PxxxIMG From your SD card,and place the superuser.zip file on it. Enter recovery thru hboot,and flash superuser.zip.it will install the root files.
After that you should be rooted.
Later I can try and find some links if you can't find them. PxxxIMG will be specific to the pyramid,I'm not sure what it is. For example,this type of file for the thunderbolt is PG05IMG.
Hope that helps.
edit:
here are some links for you:
download clockwork from here or multiupload (found the download in this thread)
download from one of those 2 places. rename the download "PG58IMG" and place on the root of your sd card. boot to hboot(power+vol down). when asked to update chose yes.
download superuser from here (this is the one i always use. found it here)
after deleting or renaming PG58IMG from your sd card,put the superuser.zip,boot to hboot,select recovery,then flash the superuser.zip.
hope it helps
Sent from my ADR6400L using XDA Premium App
Well I tried what you recommended and it did not work. But then I tried revolutionary and I managed to get s-off. However HBOOT doesnt recognize the P58IMG file. It just keeps saying P58IMG.*** NO IMAGE. (*** being different file types).
Im not sure if I need to try the recovery now that Im s-off but I cant flash the superuser file either.
gah! i wish you hadnt run revolutionary yet,as now we wont really know if your "unlocked" s-on hboot would have allowed the flash like a truly s-off one will.
one thing i know for certain,is that the troubles youre having werent because you were s-on. being able to place the superuser app,aND matching binary within the OS is not dependent on the hboot being s-off. s-off is handy,as it allows another method of flashing partitions like the radio and recovery. in the old days,before all the exploits were patched,alot of devices were rooted and a custom recovery installed from within the OS without ever bothering with the bootloader. the eris is a good example- prolly 95% of the eris community is still s-on and they change roms and such all the time.
-so i guess you downloaded the PG58IMG from multiupload? when i tried the first link,there was no valid attachement.
-you did name PG58IMG,correct? if you did name the file "P58IMG" maybe thats the prollem?
-make sure your SD card is formatted FAT32( not just plain FAT) and make sure you put the file on the root(not inside another folder)
*assuming you named the file correctly,have a FAT32 sd card,and placed the file onto the root of the SD,what happend when you went to hboot?
heres what should happen: the green writing flashes,hboot finds a PG58IMG file,then youll see a blue status bar on the far left as the phone unpacks it,then gold as it checks it. since the recovery file is small youll see that very fast. then you should get the "vol up to update" prompt.
if you have named the file correctly,FAT32 card,etc. maybe you just got a bad download. try downloading it again.
i downloaded and checked it- it contains a recovery image and an android info file,so it should be good to go. if you want to verify the integrity,the md5 i got is: 940fa14af3dcd055132adf292f668ad3
last and not least,if you ran revoltuinary it should have installed clockwork for you. if you dont want to keep messing with PG58IMG files,just run revoltionary again. it should detect your s-off,then ask if you want to install clockwork.
im sure youre getting a lil fustrated,but the method for rooting new phones is what im reccomending you to do:
1)unlock bootloader(revolutionary or htc unlock)
2)install recovery thru bootloader
3)install superuser files from recovery
it does work,i promise... ive done it many times on my thunderbolt.
Awesome, everything worked great. I had a few hitches but I figured them out. Thank you so much for all the help, I really appreciate it.
Until just now... I installed cm7 and now when i boot up my phone all I see is about 6 seconds of the cm7 start up animation (the one with the blue android guy on a skateboard). Then the phone starts up that same animation again. Its been doing this for about an hour now.
barnodian said:
Awesome, everything worked great. I had a few hitches but I figured them out. Thank you so much for all the help, I really appreciate it.
Click to expand...
Click to collapse
please list the hitches and what you did to make it work,so others will benefit that find this in future searches.
barnodian said:
Until just now... I installed cm7 and now when i boot up my phone all I see is about 6 seconds of the cm7 start up animation (the one with the blue android guy on a skateboard). Then the phone starts up that same animation again. Its been doing this for about an hour now.
Click to expand...
Click to collapse
sounds like you didnt do a full wipe. pull the pattery,go back to recovery thru hboot,and wipe data/factory reset,wipe cache,wipe dalvik chache,and format /system. i dont usually format /system,but when youre stuck in a bootloop it cant hurt
well it was my own dumb fault... like extracting the .zip files instead of leaving them compressed.
And yeah now i totally have cm7 running! thanks for all the help man. I really appreciate it
No prollem.glad you got it figured out.
Sent from my ADR6325 using XDA App
Well they were my own fault. Like forgetting to leave the .zip files compressed. Otherwise everything is working great and I'm running cyanogen perfectly. Thanks for all the help
Oh thats why I didnt see the response I thought i sent... it was on the second page. my bad. well now you get thanked twice.
I examined most if not all Boot Loop related items in XDA-Developers, as well as other sources. Although there are lots of suggestions, I cannot find one that relates to my specific situation. The last thing I want to do is make it worse. So, here's my story. I'll keep it brief, but concise.
I've had my Sensation 4G for a little over two years. Soon after purchase, I rooted it via the Revolutionary mechanism. Unfortunately (I think), I also opted for the Clockwork Mod. Unfortunately, I have not been able to do OTA updates, and find I'm still running 2.3.4.
I recently desired to purchase the HTC One for T-Mobile, and did so. I wanted to pass on my Sensation 4G to my sister. Therefore I needed to unroot it. I did weeks of reading about all the ways to do this. Early last week I attempted doing so by following the directions found here (http://kgs1992.com/ruu-guide/). I used the PG58IMG file found here (http://forum.xda-developers.com/showthread.php?t=1459767#2). The file selected was Firmware 3.33 Universal: (http://d-h.st/SuC). I followed the directions precisely. All appeared to run properly, and appeared to end with successful messages. At the end of the instructions it states "If you experience a boot loop, repeat 4.4.2 again." I did that several times. I still have the boot loop.
I started the process with this...
-Revolutionary-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.17.1111
RADIO-10.14.9035.01_M
eMCC-boot
Jun 2 2011.22:31:39
HBOOT
(VOL UP) to previous item
(VOL DOWN to next item
(POWER) to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
Following afore-mentioned process it says...
-Firmware-3.33-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
RADIO-11.24a. 3504.31-M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
Jan 13 2012,17:33:34
That brings me to my big question. What do I do now? I had hoped to retain my contacts and applications. I'd like to first attempt ways to fix it and still salvage what's on the phone, but ultimately I just need the phone to work. I should also mention that I've downloaded the following two files. My next attempt was going to execute the top one, but I don't know the status of the phone after doing so. Can anyone help me? Are there other things I should try first?
RUU_PYRAMID_ICS_TMOUS_3.32.531.14_Radio_11.69A.3504.00U_11.23.3504.07_M2_release_256085_signed.exe
RUU_Pyramid_TMOUS_1.50.531.1_Radio_10.56.9035.00U_10.14.9035.01_M_release_223976_signed.exe
Micalee said:
I examined most if not all Boot Loop related items in XDA-Developers, as well as other sources. Although there are lots of suggestions, I cannot find one that relates to my specific situation. The last thing I want to do is make it worse. So, here's my story. I'll keep it brief, but concise.
I've had my Sensation 4G for a little over two years. Soon after purchase, I rooted it via the Revolutionary mechanism. Unfortunately (I think), I also opted for the Clockwork Mod. Unfortunately, I have not been able to do OTA updates, and find I'm still running 2.3.4.
I recently desired to purchase the HTC One for T-Mobile, and did so. I wanted to pass on my Sensation 4G to my sister. Therefore I needed to unroot it. I did weeks of reading about all the ways to do this. Early last week I attempted doing so by following the directions found here (http://kgs1992.com/ruu-guide/). I used the PG58IMG file found here (http://forum.xda-developers.com/showthread.php?t=1459767#2). The file selected was Firmware 3.33 Universal: (http://d-h.st/SuC). I followed the directions precisely. All appeared to run properly, and appeared to end with successful messages. At the end of the instructions it states "If you experience a boot loop, repeat 4.4.2 again." I did that several times. I still have the boot loop.
I started the process with this...
-Revolutionary-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.17.1111
RADIO-10.14.9035.01_M
eMCC-boot
Jun 2 2011.22:31:39
HBOOT
(VOL UP) to previous item
(VOL DOWN to next item
(POWER) to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
Following afore-mentioned process it says...
-Firmware-3.33-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
RADIO-11.24a. 3504.31-M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
Jan 13 2012,17:33:34
That brings me to my big question. What do I do now? I had hoped to retain my contacts and applications. I'd like to first attempt ways to fix it and still salvage what's on the phone, but ultimately I just need the phone to work. I should also mention that I've downloaded the following two files. My next attempt was going to execute the top one, but I don't know the status of the phone after doing so. Can anyone help me? Are there other things I should try first?
RUU_PYRAMID_ICS_TMOUS_3.32.531.14_Radio_11.69A.3504.00U_11.23.3504.07_M2_release_256085_signed.exe
RUU_Pyramid_TMOUS_1.50.531.1_Radio_10.56.9035.00U_10.14.9035.01_M_release_223976_signed.exe
Click to expand...
Click to collapse
You will probably have to wipe the data partition, and therefore delete your contacts and apps (but if your contacts are saved on your google account they will be restored).
:
Do you have access to the recovery? from there you can flash a ROM and do a fresh install. I got that problem when I upgraded to the newer firmware, and I just flashed the ROM, and then everything worked fine.
astar26 said:
You will probably have to wipe the data partition, and therefore delete your contacts and apps (but if your contacts are saved on your google account they will be restored).
:
Do you have access to the recovery? from there you can flash a ROM and do a fresh install. I got that problem when I upgraded to the newer firmware, and I just flashed the ROM, and then everything worked fine.
Click to expand...
Click to collapse
I'm not sure I know what the data partition is. I can get to all my apps via play.google.com. I took full Titanium Backups, so maybe that'll be an option. Those backups were copied to my laptop.
As to Recovery, I can access it, but cannot put anything on the sd card as I do not have access to it. Apparently I can only do things via ADB.
I was just reading "A must read for those noobs who want to enjoy ICS". Perhaps there is a solution. There are apparently conflicts with Hboot versions and ICS or something. I just found that, so I'm still looking into that. I don't know how to deal with only Hboot.
Micalee said:
I'm not sure I know what the data partition is. I can get to all my apps via play.google.com. I took full Titanium Backups, so maybe that'll be an option. Those backups were copied to my laptop.
As to Recovery, I can access it, but cannot put anything on the sd card as I do not have access to it. Apparently I can only do things via ADB.
I was just reading "A must read for those noobs who want to enjoy ICS". Perhaps there is a solution. There are apparently conflicts with Hboot versions and ICS or something. I just found that, so I'm still looking into that. I don't know how to deal with only Hboot.
Click to expand...
Click to collapse
You can connect your MicroSD card via another phone to the PC, and also use the "adb push" command to push the ROM files to the root of the microSD card. Also, some recoveries allow mounting the SD card to the PC like doing it when the phone is booted, as an external drive, check for it in the recovery.
To move the ROM files to the SD card:
put the files in the folder where ADB is located
On command line type: "adb push rom.zip /sdcard/rom.zip"
Where rom.zip is the name of the rom file you are going to flash. this should work, here is a full guide to help you pushing the file via ADB: http://forum.xda-developers.com/showthread.php?t=1667929
Good luck
astar26 said:
You can connect your MicroSD card via another phone to the PC, and also use the "adb push" command to push the ROM files to the root of the microSD card. Also, some recoveries allow mounting the SD card to the PC like doing it when the phone is booted, as an external drive, check for it in the recovery.
To move the ROM files to the SD card:
put the files in the folder where ADB is located
On command line type: "adb push rom.zip /sdcard/rom.zip"
Where rom.zip is the name of the rom file you are going to flash. this should work, here is a full guide to help you pushing the file via ADB: http://forum.xda-developers.com/showthread.php?t=1667929
Good luck
Click to expand...
Click to collapse
That certainly sounds doable. I went to the link you provided. I'm not sure how pushing the rom.zip to the sdcard and doing the recovery via the phone's recovery is different than via the adb command as done earlier. The adb command process seemed to work correctly, except for the resulting boot loop. Apparently I still need to determine which rom.zip will leave me with a function phone. The only other difference in what I read at the link you provided was to do the various ["Factory Reset", "Wipe Cache Partition", and "Wipe Dalvik Cache]" commands, which I have not done. I need to determine whether those commands are necessary in my case. Thank you for your contribution.
What's happens here is that you have placed ice cream sandwich firmware with a gingerbread Rom. Gingerbread doesn't support it and as such won't boot. If you want to regain access to everything again the reflash 1.17 firmware from the thread. Then your Rom should boot up. Then jump to recovery and make a full nandroid back up. Then re-flash the ics 3.33 universal firmware and then run one of the ics ruu's you downloaded. That will make the phone have a fresh install of ics and stock HTC sense unrooted
don't try to s-on again as their is no real point to it. It's not going back for warrenty so what's the concern eh?
Good luck pal
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
Micalee said:
That certainly sounds doable. I went to the link you provided. I'm not sure how pushing the rom.zip to the sdcard and doing the recovery via the phone's recovery is different than via the adb command as done earlier. The adb command process seemed to work correctly, except for the resulting boot loop. Apparently I still need to determine which rom.zip will leave me with a function phone. The only other difference in what I read at the link you provided was to do the various ["Factory Reset", "Wipe Cache Partition", and "Wipe Dalvik Cache]" commands, which I have not done. I need to determine whether those commands are necessary in my case. Thank you for your contribution.
Click to expand...
Click to collapse
If you want you should backup via recovery, but wiping the phone after is necessary. if you managed to push the ROM to the SD-card, you can normally flash. but use a ICS (or newer) ROM, that supports the firmware.
In contrast to what heavy_metal_man said, you can do a nandroid backup as it is, as the files are still there. but you don't have much to do with it.
Edit - If you need any help doing it step by step - I'm here to help, just say where you are stuck on the guide (or just explain)
heavy_metal_man said:
What's happens here is that you have placed ice cream sandwich firmware with a gingerbread Rom. Gingerbread doesn't support it and as such won't boot. If you want to regain access to everything again the reflash 1.17 firmware from the thread. Then your Rom should boot up. Then jump to recovery and make a full nandroid back up. Then re-flash the ics 3.33 universal firmware and then run one of the ics ruu's you downloaded. That will make the phone have a fresh install of ics and stock HTC sense unrooted
don't try to s-on again as their is no real point to it. It's not going back for warrenty so what's the concern eh?
Good luck pal
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
Click to expand...
Click to collapse
Thanks heavy_metal_man for that information. In the mean time, while waiting for another suggestion, I decided to try a different rom. That was due to the comments I'd seen about conflicts between Hboot and ICS. So, just for the heck of it I went through whole routine, using ROM V3.12. After doing so (twice), the phone booted! Amazingly, other than thinking it's 1970, it appears to be identical to what it was before I ever did anything. It's still running V2.3.4 of Android, and Sense V3.0. I don't recall which version of Sense was there before. After it booted, I shut it down again and put it in Recovery mode. There have been a number of changes there. Now it says...
*** LOCKED ***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.23.0000
RADIO-11.19.3504.29.2
OpenADSP-v01.6.0.2226.00.1227
eMMC-boot
Dec 26 2011.12:14:25
Does any of this information affect or change your suggestion in any way? I'd still like to get ICS on this thing so the latest is available for when I give it to my sister. I wonder what will happen if I attempt OTA? By the way, it still has Revolutionary CWM V4.0.1.4 on it.
Micalee said:
Thanks heavy_metal_man for that information. In the mean time, while waiting for another suggestion, I decided to try a different rom. That was due to the comments I'd seen about conflicts between Hboot and ICS. So, just for the heck of it I went through whole routine, using ROM V3.12. After doing so (twice), the phone booted! Amazingly, other than thinking it's 1970, it appears to be identical to what it was before I ever did anything. It's still running V2.3.4 of Android, and Sense V3.0. I don't recall which version of Sense was there before. After it booted, I shut it down again and put it in Recovery mode. There have been a number of changes there. Now it says...
*** LOCKED ***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.23.0000
RADIO-11.19.3504.29.2
OpenADSP-v01.6.0.2226.00.1227
eMMC-boot
Dec 26 2011.12:14:25
Does any of this information affect or change your suggestion in any way? I'd still like to get ICS on this thing so the latest is available for when I give it to my sister. I wonder what will happen if I attempt OTA? By the way, it still has Revolutionary CWM V4.0.1.4 on it.
Click to expand...
Click to collapse
you just used a ruu.exe from pc and restored everything to stock condition
but how you were able to keep custom recovery(cwm V4.0.1.4)
when you flashed the 3.33 firmware you could just install a custom ics rom
because with 3.33 firmware the gb rom you had it would never booted
about OTA i assume nothing will happen as long as you have cwm recovery installed
you must have the stock recovery
Well, since you flashed a new rom you can disregard my first suggestion and go straight for running the ics ruu you have. Ota updates will not work if you dont have the stock recovery. But the ruu will give you it so ota will work, but the updates will be for the cid of the rom you flashed. So flash a WWE rom to make sure you get any updates, but at this point their will be few if any.
Aside from that you will be all sorted pal
Sent from my Nexus 7 using Tapatalk 4
Thanks again heavy_metal_man. It wasn't that I ignored your suggestion, I tried the second (V3.12) Rom before I had seen it. As for your last entry, I was following it until you hit me with the WWE reference. As for the V3.12 Rom I used, there was a direct MIB match, and the CID used was cid******, so a direct match was not necessary as far as I can determine. I could have edited the txt file and inserted my actual CID however. Also, was your comment about "the ics ruu I have", in reference to the two RUU_PYRAMID_ICS_TMOUS...etc. files I mentioned that I had already downloaded? Running one of those will be a new experience. I'll run the latest. If that works, I'll be a happy camper. I've learned a lot, but I have a long way to go.
Micalee said:
Thanks again heavy_metal_man. It wasn't that I ignored your suggestion, I tried the second (V3.12) Rom before I had seen it. As for your last entry, I was following it until you hit me with the WWE reference. As for the V3.12 Rom I used, there was a direct MIB match, and the CID used was cid******, so a direct match was not necessary as far as I can determine. I could have edited the txt file and inserted my actual CID however. Also, was your comment about "the ics ruu I have", in reference to the two RUU_PYRAMID_ICS_TMOUS...etc. files I mentioned that I had already downloaded? Running one of those will be a new experience. I'll run the latest. If that works, I'll be a happy camper. I've learned a lot, but I have a long way to go.
Click to expand...
Click to collapse
ah sorry, getting ahead of myself with terminology here WWE stand for world wide English. most unbranded phones run on world wide English roms, and if people are downgrading/upgrading they tend to want unbranded as they will get official htc updates faster
as far as cid`s are concerned they dont really matter as you are s-off and the phone will accept any ruu (rom update utility) you give it. one note of caution though is you have select a t-mobileus ruu and they are ment to be for the tmobile sensation 4g. if you dont have the tmobus 4g it may give you some issues with the radio, meaning you may lose phone signal. ( im not 100% sure but caution is advised )
if you dont have a sensation 4g then download and run this one here. im pretty confident that its a stock ice cream sandwich unbranded rom
Running the RUU is simple enough, just boot the phone into your stock 2.3.4 rom and turn on usb debugging from settings for good measure. Then connect the phone to the pc via the usb cable and then run the RUU. it will connnect to the phone and confirm the phone is the correct model i believe, then it will confirm this is what you want to do. select yes and let it work its magic. its pretty straight forward they phone may reboot several times, this is normal. just dont disconnect the battery or the usb cable and you will be fine. should be done in ten minutes tops
good luck pal
I made it through the RUU process, but not without some difficulty. When I ran the RUU_PYRAMID_ICS_TMOUS_3.32.531.14 version, it died with an Error 155. Fortunately it left everything intact. Then I ran the older RUU_Pyramid_TMOUS_1.50.531.1 non-ICS version. It got the same error. I think these errors must somehow be due to the peculiar results from flashing the PG58IMG file earlier. Once again, it left everything intact. I tried the RUU ICS 3.32 version one more time, except this time I put the phone in flashboot mode first. Curiously, the RUU screen that came up thought it was updating a later version than what was actually on the phone, but IT RAN... all the way through to a successful finish. I was stunned. Now the phone reports...
-Firmware-3.33-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
RADIO-11.24a. 3504.31-M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
Jan 13 2012,17:33:34
The entire process left my SD card intact as well. Amazing. It still says S-OFF as you expected. I may or may not attempt turning S-On again.
One comment I'd like to make about xda-developers. There is an amazing amount of information here. The biggest problem I've encountered is trying to figure out if I'm looking at, or have found, the latest information. Some times I'll find something that looks pertinent, only to find that I'm on page 2 of a 114 page thread, and the information I'm looking at is completely obsolete. It's tough for a noob to decipher it all. Anyway, thanks again for everyone's assistance. I think this is a proper place to terminate this particular thread. Now I'll start looking for the latest information on rooting my new HTC ONE. At least I have a fall back phone in my newly restored Sensation 4G. I'm not sure I'm in love the ONE yet, so perhaps I'll take it back. I'm within my 14 day return window.
I'm glad your sorted pal the threads can be a bit out of date, maintenance of information is not really regulated but as always if people are unsure just ask, quoting the info you have and what you think is the case
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
Micalee said:
I made it through the RUU process, but not without some difficulty. When I ran the RUU_PYRAMID_ICS_TMOUS_3.32.531.14 version, it died with an Error 155. Fortunately it left everything intact. Then I ran the older RUU_Pyramid_TMOUS_1.50.531.1 non-ICS version. It got the same error. I think these errors must somehow be due to the peculiar results from flashing the PG58IMG file earlier. Once again, it left everything intact. I tried the RUU ICS 3.32 version one more time, except this time I put the phone in flashboot mode first. Curiously, the RUU screen that came up thought it was updating a later version than what was actually on the phone, but IT RAN... all the way through to a successful finish. I was stunned. Now the phone reports...
-Firmware-3.33-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
RADIO-11.24a. 3504.31-M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
Jan 13 2012,17:33:34
The entire process left my SD card intact as well. Amazing. It still says S-OFF as you expected. I may or may not attempt turning S-On again.
One comment I'd like to make about xda-developers. There is an amazing amount of information here. The biggest problem I've encountered is trying to figure out if I'm looking at, or have found, the latest information. Some times I'll find something that looks pertinent, only to find that I'm on page 2 of a 114 page thread, and the information I'm looking at is completely obsolete. It's tough for a noob to decipher it all. Anyway, thanks again for everyone's assistance. I think this is a proper place to terminate this particular thread. Now I'll start looking for the latest information on rooting my new HTC ONE. At least I have a fall back phone in my newly restored Sensation 4G. I'm not sure I'm in love the ONE yet, so perhaps I'll take it back. I'm within my 14 day return window.
Click to expand...
Click to collapse
actually are you sure that you flashed the ruu.exe correctly?
you still have the patched hboot and on top of the screen it still says firmware 3.33 which is the patched one
don't attempt to S-ON.probably you will brick the device
after ruu installation your bootloader should say relocked or locked on top of the screen
edit:if i remember well error 155 means a connection issue
rzr86 said:
actually are you sure that you flashed the ruu.exe correctly?
you still have the patched hboot and on top of the screen it still says firmware 3.33 which is the patched one
don't attempt to S-ON.probably you will brick the device
after ruu installation your bootloader should say relocked or locked on top of the screen
edit:if i remember well error 155 means a connection issue
Click to expand...
Click to collapse
Flashed? All I did was run the program. It did whatever it did. I think the 3.33 was somehow left over from flashing a PG58IMG I'd gotten from here>http://forum.xda-developers.com/showthread.php?t=1459767#2. That failed as explained earlier in this thread. I figured that running the RUU would overwrite that failure, and I'm surprised it didn't. All I care is that I'm now getting OTA updates correctly. Yeah, I won't be trying to S-ON. I've thought about rerunning the RUU (3.32) again, but for now I'm going to just leave well enough alone.
I forgot to mention. This information was in the documentation for the RUU
ERROR [155~159]: IMAGE ERROR
One of these error messages will appear when you use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version and try again.
One last note. I returned the HTC ONE, and have reactivated the Sensation 4g which this thread is about. The HTC ONE hardware is wonderful, but I didn't like all the HTC ONE software "features" you can't turn off. Maybe I'll jump ship and go with the Samsung Galaxy S4. In the mean time, this Sensation 4G is okay.
Micalee said:
Flashed? All I did was run the program. It did whatever it did. I think the 3.33 was somehow left over from flashing a PG58IMG I'd gotten from here>http://forum.xda-developers.com/showthread.php?t=1459767#2. That failed as explained earlier in this thread. I figured that running the RUU would overwrite that failure, and I'm surprised it didn't. All I care is that I'm now getting OTA updates correctly. Yeah, I won't be trying to S-ON. I've thought about rerunning the RUU (3.32) again, but for now I'm going to just leave well enough alone.
I forgot to mention. This information was in the documentation for the RUU
ERROR [155~159]: IMAGE ERROR
One of these error messages will appear when you use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version and try again.
One last note. I returned the HTC ONE, and have reactivated the Sensation 4g which this thread is about. The HTC ONE hardware is wonderful, but I didn't like all the HTC ONE software "features" you can't turn off. Maybe I'll jump ship and go with the Samsung Galaxy S4. In the mean time, this Sensation 4G is okay.
Click to expand...
Click to collapse
exactly the firmware 3.33 and the 1.27.1100 hboot version are from 3.33 universal firmware zip(from the thread you mentioned)
but as long as you are on S-OFF you can use any ruu.exe if you are also supercid
When the PG58IMG flash failed, I assumed at that time that it failed completely, and that no part of it actually worked. I'm too much of a noob to understand the pieces, or elements of the phone's software vs. firmware. I know the difference of course, but not as they relate to this phone, and certainly not as they relate to all the various flashes or other 'fixes' or other such mechanisms I see here on xda-developers.
If I get the nerve to attempt it, is there a way to get everything to a fully legitimate 'stock' situation? That is, just in case I upgrade to another phone again and want to sell this Sensation 4G? For example, I wonder what would be the result of a factory reset at this point? I realize it'll wipe everything out of course, but I wouldn't care.
Micalee said:
When the PG58IMG flash failed, I assumed at that time that it failed completely, and that no part of it actually worked. I'm too much of a noob to understand the pieces, or elements of the phone's software vs. firmware. I know the difference of course, but not as they relate to this phone, and certainly not as they relate to all the various flashes or other 'fixes' or other such mechanisms I see here on xda-developers.
If I get the nerve to attempt it, is there a way to get everything to a fully legitimate 'stock' situation? That is, just in case I upgrade to another phone again and want to sell this Sensation 4G? For example, I wonder what would be the result of a factory reset at this point? I realize it'll wipe everything out of course, but I wouldn't care.
Click to expand...
Click to collapse
A factory reset only deletes the data partition and cache, not any other partition. There are ROMs that are based on stock (and even stock). By fully legitimate 'stock' situation I believe you mean S-On and every thing stock. There are guies for that in the general and development forums.
I have a AT&T One X rooted
HBOOT-1.09.0000
RADIO-0.17.32.09.12
I am attempting to do the OTA's or RUU to bring it up to current because I realized since I had not touched it since first purchased and rooted so none of the OTA's went through. I never gave myself time allowed to figure out how to send them.
Well now I'm trying and I have gotten myself in to a hot mess.
I first tried using the FUU Upgrades provided by Flashalot but it said "wrong update" and I could not find a reason. I backed up a couple and tried 2.14. Well eventually it just stayed at the fastboot "HTC" screen for nearly an hour and appeared locked up. So I pulled it and rebooted. It would not let me get past the boot up screen until I cleared cache's and went back to my stock rom (cmod 10).
Now it will not mount "SD Card" when connected USB and in TWRP. I am also unable to download any files to it via browser or launched phone because it says no SD Card installed.
I attempted to send any of the OTA's via fastboot and it hangs (giving it hours...overnight even). I did writecid 11111111 before sending some with same results.
Any suggestions?
Thanks
stampy101 said:
I have a AT&T One X rooted
HBOOT-1.09.0000
RADIO-0.17.32.09.12
I am attempting to do the OTA's or RUU to bring it up to current because I realized since I had not touched it since first purchased and rooted so none of the OTA's went through. I never gave myself time allowed to figure out how to send them.
Well now I'm trying and I have gotten myself in to a hot mess.
I first tried using the FUU Upgrades provided by Flashalot but it said "wrong update" and I could not find a reason. I backed up a couple and tried 2.14. Well eventually it just stayed at the fastboot "HTC" screen for nearly an hour and appeared locked up. So I pulled it and rebooted. It would not let me get past the boot up screen until I cleared cache's and went back to my stock rom (cmod 10).
Now it will not mount "SD Card" when connected USB and in TWRP. I am also unable to download any files to it via browser or launched phone because it says no SD Card installed.
I attempted to send any of the OTA's via fastboot and it hangs (giving it hours...overnight even). I did writecid 11111111 before sending some with same results.
Any suggestions?
Thanks
Click to expand...
Click to collapse
First question is do you have s-off?
Second question is did you perform a factory reset from the bootloader at some point? I ask this because it looks like your sd card is corrupt, and that's what happens when you perform a factory reset from the bootloader on a modified Evita. Either way I believe you need to wipe your sd card with TWRP before it'll become usable again. If it still isn't usable after a wipe, try mounting it to your PC again so you can format it with Windows.
My last question is what is your end goal? Are you wanting to run a stock ROM and that's why you're wanting to install OTA updates? The rule of thumb for modified phones is to never install OTA updates on them. If you're just looking to update to the latest/latest needed firmware, you can just flash a firmware package or run an RUU. You must have s-off to do this though.
Another thing I should mention is that you don't use fastboot to install OTA updates. It seems like you're not exactly sure about what you're doing, which can be a very dangerous thing when messing with a modified device. I think you need to do a bit more research before continuing ahead. Tell me exactly what your end goal is though and I'll provide as much information as I can.
Sent from my Evita
FUBAR?
timmaaa said:
First question is do you have s-off?
Second question is did you perform a factory reset from the bootloader at some point? I ask this because it looks like your sd card is corrupt, and that's what happens when you perform a factory reset from the bootloader on a modified Evita. Either way I believe you need to wipe your sd card with TWRP before it'll become usable again. If it still isn't usable after a wipe, try mounting it to your PC again so you can format it with Windows.
My last question is what is your end goal? Are you wanting to run a stock ROM and that's why you're wanting to install OTA updates? The rule of thumb for modified phones is to never install OTA updates on them. If you're just looking to update to the latest/latest needed firmware, you can just flash a firmware package or run an RUU. You must have s-off to do this though.
Another thing I should mention is that you don't use fastboot to install OTA updates. It seems like you're not exactly sure about what you're doing, which can be a very dangerous thing when messing with a modified device. I think you need to do a bit more research before continuing ahead. Tell me exactly what your end goal is though and I'll provide as much information as I can.
Sent from my Evita
Click to expand...
Click to collapse
OK So it sounds like I've probably corrupted my memory from what you are saying. Any going back?
1. S-Off. I'm going with no. It was 2 years ago when I rooted it and installed CM10. I do not recall doing this but just flashing CM.
1a. Attempting to do it now just shows error 99 unknown error...
2. Yes. I do believe that I had hit the factory reset. Attempting to do the wipe in TWRP shows "success" but it also shows it could not mount E:\
2a. Still will not let me turn on USB storage. It just spins for a while and ends up giving up when the display is changed.
3. End goal...I could care less about root. I've always used modded ROM's and prefer them. I only did "OTA" when the RUU would not take. I became a bull in a china shop and started banging with a hammer...Was dumb but I think I had already corrupted the memory by hitting factory reset. (I'll be honest I never meant to hit that).
I've rooted and installed many a custom ROM's, but I prefer the simple methods of following one of the many awesome easy setups on here. I'm not completely useless...
I would like to get it back to the SD card working and be able to update the firmware and a moderately functioning ROM.
Thank you for any help. I really do appreciate it.
stampy101 said:
OK So it sounds like I've probably corrupted my memory from what you are saying. Any going back?
1. S-Off. I'm going with no. It was 2 years ago when I rooted it and installed CM10. I do not recall doing this but just flashing CM.
1a. Attempting to do it now just shows error 99 unknown error...
2. Yes. I do believe that I had hit the factory reset. Attempting to do the wipe in TWRP shows "success" but it also shows it could not mount E:\
2a. Still will not let me turn on USB storage. It just spins for a while and ends up giving up when the display is changed.
3. End goal...I could care less about root. I've always used modded ROM's and prefer them. I only did "OTA" when the RUU would not take. I became a bull in a china shop and started banging with a hammer...Was dumb but I think I had already corrupted the memory by hitting factory reset. (I'll be honest I never meant to hit that).
I've rooted and installed many a custom ROM's, but I prefer the simple methods of following one of the many awesome easy setups on here. I'm not completely useless...
I would like to get it back to the SD card working and be able to update the firmware and a moderately functioning ROM.
Thank you for any help. I really do appreciate it.
Click to expand...
Click to collapse
There's no point in attempting s-off at the moment because s-off requires that a working OS is installed. You can tell whether you're s-off by looking at your bootloader, it'll say s-on or s-off in the first line under the unlocked and tampered banners.
Your problem with your sd might be that the version of TWRP you have installed is too old, only the newer versions are able to fix a corrupt sd card. Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now try wiping and mounting the sd card again. Once we have that sorted out we can move onto getting your firmware updated.
Sent from my Evita
OK! Looks like we are getting somewhere! It is now mounted.
Now you can copy files across to flash. You'll need to get s-off now so you can update your firmware. You'll need a bootable OS installed to do that, I'd suggest installing Kickdroid and then you can attempt getting s-off via the Rumrunner method.
Sent from my Evita
You are awesome! Thank you so very much for your help. Up and running.
How far have you gotten?
Sent from my Evita
S-Off and firmware updated and running with different ROM's. I'm golden man. Unless you can think of something I should consider?
As long as you're on the 2.15 firmware or higher, you are indeed golden. I was just curious.
Sent from my Evita
Hey there, I just noticed you made a donation to me with this thread as the reference. I just wanted to thank you, that's very generous of you. Donations aren't expected in return for my assistance but are greatly appreciated. Anyway, thanks again and have a great day.