Related
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.
OK i will admit I am over my head on this one. Frustration kicked in and I think I just lost all the data on my phone (pics and videos and everything which is the worst part). Here's the story.
I was originally on Team Venom 4.2 and was having random reboots.
I tried fixing by updating the Radio to ATT 3.18: http://d-h.st/DcT in this thread: http://forum.xda-developers.com/showthread.php?t=1694012 I flashed WITh the RIL (under the line that says do not flash these with newer roms) yeah I know.
flashed 3.18 again without RIL (above the 'do not flash' line
flashed att 2.0 radio
so now my radio still isnt working, tries to prepare sim card and will not work.
now I am trying to flash a new ROM to rewrite everything. tried to install android revolution HD. http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
flashed the android revolution boot.img file and attempted to flash the android revolution rom and would not flash, rebooted twrp after 30%
messed around in twrp a bit and hit factory reset. thought that would do a reboot of the android install. looks like i just formatted my sd card AND deleted android operating system. i cannot reboot into system 'no android os installed' and under twrp file manager i have NOTHING LEFT in my sd card. except the twrp folder. the phone has not been rebooted since.
DID I JUST LOSE EVERYTHING?
i am seriously interested in getting the pictures and data off the sd partition somehow. that is my main concern, i will deal with reinstalling android afterward.
any help will be rewarded, thank you in advance.
beppomarx said:
OK i will admit I am over my head on this one. Frustration kicked in and I think I just lost all the data on my phone (pics and videos and everything which is the worst part). Here's the story.
I was originally on Team Venom 4.2 and was having random reboots.
I tried fixing by updating the Radio to ATT 3.18: http://d-h.st/DcT in this thread: http://forum.xda-developers.com/showthread.php?t=1694012 I flashed WITh the RIL (under the line that says do not flash these with newer roms) yeah I know.
flashed 3.18 again without RIL (above the 'do not flash' line
flashed att 2.0 radio
so now my radio still isnt working, tries to prepare sim card and will not work.
now I am trying to flash a new ROM to rewrite everything. tried to install android revolution HD. http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
flashed the android revolution boot.img file and attempted to flash the android revolution rom and would not flash, rebooted twrp after 30%
messed around in twrp a bit and hit factory reset. thought that would do a reboot of the android install. looks like i just formatted my sd card AND deleted android operating system. i cannot reboot into system 'no android os installed' and under twrp file manager i have NOTHING LEFT in my sd card. except the twrp folder. the phone has not been rebooted since.
DID I JUST LOSE EVERYTHING?
i am seriously interested in getting the pictures and data off the sd partition somehow. that is my main concern, i will deal with reinstalling android afterward.
any help will be rewarded, thank you in advance.
Click to expand...
Click to collapse
First, what phone do you have? We will need the first five lines of your bootloader to help you later.
If all you need right now is to try and recover the files and you are on windows, here is a freeware file recovery program I've used in the past. You will need to be able to mount your sd card in TWRP.
http://www.softpedia.com/get/System/Back-Up-and-Recovery/Recuva.shtml
Once you get that done, you do have some problems to work through (Android Revolution Rom is not for our phone.)
beppomarx said:
OK i will admit I am over my head on this one. Frustration kicked in and I think I just lost all the data on my phone (pics and videos and everything which is the worst part). Here's the story.
I was originally on Team Venom 4.2 and was having random reboots.
I tried fixing by updating the Radio to ATT 3.18: http://d-h.st/DcT in this thread: http://forum.xda-developers.com/showthread.php?t=1694012 I flashed WITh the RIL (under the line that says do not flash these with newer roms) yeah I know.
flashed 3.18 again without RIL (above the 'do not flash' line
flashed att 2.0 radio
so now my radio still isnt working, tries to prepare sim card and will not work.
now I am trying to flash a new ROM to rewrite everything. tried to install android revolution HD. http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
flashed the android revolution boot.img file and attempted to flash the android revolution rom and would not flash, rebooted twrp after 30%
messed around in twrp a bit and hit factory reset. thought that would do a reboot of the android install. looks like i just formatted my sd card AND deleted android operating system. i cannot reboot into system 'no android os installed' and under twrp file manager i have NOTHING LEFT in my sd card. except the twrp folder. the phone has not been rebooted since.
DID I JUST LOSE EVERYTHING?
i am seriously interested in getting the pictures and data off the sd partition somehow. that is my main concern, i will deal with reinstalling android afterward.
any help will be rewarded, thank you in advance.
Click to expand...
Click to collapse
Ok, first, you're all over the place. Why did you install a radio+RIL when it explicitly tells you not to? It's actions like this that get people like you into a lot of trouble and destroys phones.
Secondly, there is no Android Revolution HD for this device. I believe you have the HTC One XL / at&t One X (Evita) judging from your post, but like I said there's no ARHD ROM for the Evita, only for the HTC One X (Endeavoru). This leads me to believe that you're jumping between the two device forums, very bad idea, none of the stuff from the Endeavoru forum is compatible with our phone.
You're lucky the ROM install stopped otherwise you would have bricked your phone. Long story short, you have no OS because the ROM install didn't complete, you have a corrupt boot partition because you flashed the ARHD boot.img which isn't compatible. In future do not stray outside our device forum for any reason at all. Here's our forum main page, bookmark it:
http://forum.xda-developers.com/forumdisplay.php?f=1538
Next. Performing a factory reset in TWRP recovery does not wipe user data (images/music etc). I'm not sure what you've done but the factory reset in recovery wasn't it. A factory reset performed in the bootloader does however corrupt the sd card, so never do a factory reset from the bootloader.
You might have a chance at saving some of your data using a data recovery tool in Windows. You'll need to mount usb storage in TWRP for Windows to access the sd. Do not under any circumstances do any writing to the sd card before you attempt to save your data.
In conclusion, you've made numerous mistakes with your device. You need to slow down a bit and educate yourself a bit better, a lack of knowledge when it comes to modifying devices is a very dangerous thing.
Please post the first five lines of your bootloader.
Sent from my Evita.
i could have sworn i got the android revolution rom from the att one x forum but i suppose not....
ok guys thanks so much so far i will pick up again after work today.
bootloader says:
TAMPERED
UNLOCKED
EVITA PVT SHIP S-ON RL
HBOOT-1.09.000
RADIO-0.19as.32.09.11_2
OpenDSP-v34.1.0.45.1219
eMMC-boot
Apr 2 2012,21:08:24
I'm 99.9% i was s-off before this all...
There isn't and never has been an Android Revolution ROM in this forum. It's kinda easy to make the mistake, the forums are named similarly.
I'm 99.9% sure you weren't s-off before all this. A phone can't change the security status without you doing it manually. It just can't happen. Did you actually go through either the Facepalm or Rumrunner s-off processes?
Well, you definitely have the Evita (HTC One XL / at&t One X) so make sure you stay within the forum I linked to earlier.
Good luck with attempting to recover your data, I hope you get at least some of it back.
Sent from my Evita.
Ok so as far as mounting my sd card in twrp, there's something up with my screen touch input I think... I am not able to click that particular box in the 'mount' menu. It seems like that part of the screen was not clickable when installing roms and such but once I get into android everything works perfectly.
Is there a way to rotate the screen in twrp?
Also by looking at my bootloader info once I get my sd card mounted and recovered best as I can, what is my best plan of action? Re-lock and flash a stock att ruu and begin from scratch or what? Or just try and load a correct radio and rom? I'm not a complete newbie I know I made a foolish mistake but I have done this quite a few times playing on the inspire, cha-cha, my kids nabi 2 tablets and on this att one x. This is the first time I have gotten really stuck in probably 35 flashes. Just this time I might be over my head...
To be honest I've never tried rotating the screen while in recovery, so I'm not sure about that. Exactly which recovery type (CWM/TWRP) and version number are you using?
I think your best plan of action would be to run an RUU, this will bring everything back to the way it should be. You're lucky in the sense that you're still on quite an early firmware version, so you should have a couple of RUU options. One thing to be careful of though, absolutely do not run a jb RUU if you have SuperCID, it will brick your device. SuperCID + s-on + jb RUU = brick. We should check your CID just in case, connect your phone in fastboot mode and issue this command:
Code:
fastboot oem readcid
Sent from my Evita.
beppomarx said:
i could have sworn i got the android revolution rom from the att one x forum but i suppose not....
Click to expand...
Click to collapse
There is absolutely no ARHD ROM for EVITA. You've made a grave error, and as timmaaa mentioned, you are lucky your phone isn't a paperweight now.
EVDEAVORU is partitioned completely differently from EVITA, so all bets are pretty much off on whether your data is still intact or not. The ROM itself may have overwritten your data. Also, if you happened to do a factory reset in hboot instead of TWRP (as you mentioned) this will corrupt the SD card on modded EVITAs (known issue, and somewhat common error).
Your best bet is to get the phone back up and running using timmaaa instructions. Then see if the files are still on the SD. If the data files aren't easily visible, you can also try data recovery programs to see if they can be salvaged (sometimes corrupted files get dumped to a temp folder, or otherwise recoverable).
But I wouldn't hold my breath on recovering the files. This is what always puzzles me (why folks never back their data, then freak out when its gone of damaged). If your data is important to you, its important enough to back up. And there are so many easy methods to do so (with built-in cloud backup apps and whatnot) yet so many folks neglect to do that. And all you are left with is regret when things do south. Its pretty much a no-brainer to backup anything important to you when modding the phone. I'm puzzling why so many folks never do it.
So since I have the 1.09.000 hboot i am going to download and install this:
1.85.502.3
File Timestamp: 25/05/12
Publically Seen: 06/06/12
Android: 4.0.3
Kernel: 3.0.8-01155-gca24d1e
hboot: 1.09.0000
radio: 0.17.32.09.12_10.86.32.08
adsp: 28.1.0.32.0504
wcnss: 1031120A
tp_syn3202: 3.0_PR1100755
tz: 001.031.511
sbl1: 001.031.503
sbl2: 001.031.501
sbl3: 001.031.502
OTA: OTA_Evita_UL_Cingular_US_1.85.502.3_R2_NEW_NFCPHON ESTORAGE-1.73.502.1_release_263287jkmeqj8u75z409z9.zip
RUU: RUU_Evita_UL_Cingular_US_1.85.502.3_R2_Radio_0.17. 32.09.12_10.86.32.08L_release_262092_signed.exe (Download)
Source: evita-ics-crc-3.0.8-271616b.zip
is this my best bet? I am going to try and check my CID status right now just need to download the android SDK and get that going...
**EDIT**
my CID is 11111111. is that superCID?
**EDIT**
looking for a way to remove superCID. If i just go S-off am i OK to run a RUU or should I keep looking to change my CID back?
**EDIT**
just downloaded WinDrid HTC One XL Toolkit and seems to be up and running fine. my plan so far is to S-off and run the RUU I posted above but I will wait for someone to chime in before I do anything else.. I feel like I am on the edge here and don't want to brick it... I can't find any way so far to return my CID but from what I read if I am S-off it should keep me safe.
S-off won't work unless you're able to boot into a ROM. I'd forget about using a toolkit for now, it completely bypasses some much needed learning, and doesn't always work anyway. I believe all you need to do is relock your bootloader and then run the RUU.
Sent from my Evita.
Ok I will look into how to re-lock that after work today. Can anyone else confirm this? Not that I don't trust you but wording it like 'I believe this will work' makes me ask again...
I'm 99.99% sure it's only the jb and above RUU that you need to worry about while s-on and SuperCID.
Sent from my Evita.
timmaaa said:
I'm 99.99% sure it's only the jb and above RUU that you need to worry about while s-on and SuperCID.
Click to expand...
Click to collapse
ICS RUUs are free of the S-on and SuperCID bug. Plenty of folks have flashed that RUU (such as 2.20) with SuperCID with no issue.
so I am going to relock the bootloader, it's as simple as 'fastboot oem lock'? that's it? before doing so should i bother s-off first? here's my plan of action:
s-off
relock bootloader
run 2.20.502.7 ruu
unlock bootloader again
install twrp
load custom rom
that should work correct?
If you s-off first, I believe you do not need to relock the bootloader to run the RUU. Just s-off, then run the RUU.
As I've previously mentioned, you won't be able to get s-off unless your phone will boot a ROM. The above process looks right.
Sent from my Evita.
got back to stock just fine, now to work my way back to modded. You guys are the best thank you a million.
Please hit the thanks button on any post that you've found helpful on XDA.
Sent from my Evita.
Remember also to either s-off or change cid back to normal, it will assist in the future if you get in a jam like this.
Although s-off and flashing a rom for a different phone(like you did) may have ended up much worse as some of the checks that likely saved you will be disabled.
At very least do not OTA/RUU update to Jellybean while you are s-on and supercid!
Hello,
I am trying to update my phone without losing all of my data and of coarse, root as well. Below is what I am working with:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-0.19AS.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
Jun 11 2012, 14:36:28
Recovery TWRP v2.6.3.0
Android Version 4.0.4
Sense 4.0
software # 2.20.502.7.710RD
API Level 4.23
HTC extension 403_1_GA_20
Kernel 3.0.8-01558-g7f75e5b
baseband 0.19as
build 2.20.502.7
That's probably way more than you needed to know, but I like to be through. (c;
anyhow, I want to update everything to the latest version... firmware, hboot (if applicable), OS, radio, etc. without losing my data, recovery or root.
I have downloaded RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial.exe from HTC
and OTA_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_0.24p.32.09.06_10.130.32.34_release_3061616bcty3drvawwo01k.zip from my phone.
I tried upgrading using adb sideload (renaming zip from carrier to update.zip) and it failed
I tried upgrading using install feature of TWRP using update.zip and it failed
I then thought I will just extract the .img files and flash using adb, but quickly discovered I don't know what .img file is which. If some one has a better way of accomplishing my goal i am all ears, however if someone can assist in identifying which .img files i should flash and how to best approach it I would be very appreciative.
the files extracted are attached (didn't want to flood the post)
It's better to provide too much information than not enough, which is what most people do lol.
I think you're a bit misguided on the whole process so I'll break it down for you. You've downloaded the right RUU but you don't need the OTA. You're also approaching it with the wrong methodology, you're not meant to extract the RUU and flash any image files manually. All you need to do is connect your phone to your PC in fastboot mode and run the RUU exe program in Windows then follow the prompts. You must get s-off first though, very important, do not skip this step!
You will lose your custom recovery and root, there's no way around that. But getting them back is as easy as flashing the custom recovery again and installing root or a rooted ROM. The RUU shouldn't wipe anything from your sd card but it's a good idea to make a backup just in case. You'll lose text messages, call logs, things like that but you can back those up using backup apps before the process.
So head over to the Rumrunner site and get s-off first and you'll be good to go.
Sent from my Evita
timmaaa said:
It's better to provide too much information than not enough, which is what most people do lol.
I think you're a bit misguided on the whole process so I'll break it down for you. You've downloaded the right RUU but you don't need the OTA. You're also approaching it with the wrong methodology, you're not meant to extract the RUU and flash any image files manually. All you need to do is connect your phone to your PC in fastboot mode and run the RUU exe program in Windows then follow the prompts. You must get s-off first though, very important, do not skip this step!
You will lose your custom recovery and root, there's no way around that. But getting them back is as easy as flashing the custom recovery again and installing root or a rooted ROM. The RUU shouldn't wipe anything from your sd card but it's a good idea to make a backup just in case. You'll lose text messages, call logs, things like that but you can back those up using backup apps before the process.
So head over to the Rumrunner site and get s-off first and you'll be good to go.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the response!
I figured I didn't need both the ruu and the ota, but I didn't know if one had newer componets than the other. Also, I didn't know that s-off had been accomplished, last I checked it was still unavailable.
The reason I was thinking of flashing the images manually was because it was so simple for the nexus 7 upgrade, and prevented data loss. The ruu says data loss will happen on it, so I was skeptical to run it as is. So now I am off to check out that link and get this party started! Thanks again!
Spy_64 said:
Hello,
I am trying to update my phone without losing all of my data and of coarse, root as well. Below is what I am working with:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-0.19AS.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
Jun 11 2012, 14:36:28
Recovery TWRP v2.6.3.0
Android Version 4.0.4
Sense 4.0
software # 2.20.502.7.710RD
API Level 4.23
HTC extension 403_1_GA_20
Kernel 3.0.8-01558-g7f75e5b
baseband 0.19as
build 2.20.502.7
That's probably way more than you needed to know, but I like to be through. (c;
anyhow, I want to update everything to the latest version... firmware, hboot (if applicable), OS, radio, etc. without losing my data, recovery or root.
I have downloaded RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial.exe from HTC
and OTA_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_0.24p.32.09.06_10.130.32.34_release_3061616bcty3drvawwo01k.zip from my phone.
I tried upgrading using adb sideload (renaming zip from carrier to update.zip) and it failed
I tried upgrading using install feature of TWRP using update.zip and it failed
I then thought I will just extract the .img files and flash using adb, but quickly discovered I don't know what .img file is which. If some one has a better way of accomplishing my goal i am all ears, however if someone can assist in identifying which .img files i should flash and how to best approach it I would be very appreciative.
the files extracted are attached (didn't want to flood the post)
Click to expand...
Click to collapse
If you get stuck or need more info, I threw together a guide with info from the forums that may help:
http://forum.xda-developers.com/showthread.php?t=2593037
By the way, tell me about your footer "HTC Evita Gummy 4.4.2 | Torched KK Kernel S-off | 2.14 | Modified TWRP 2.6.3"..... Cooked rom? How do you like it? How does it compare to stock?
Madcat8686 said:
If you get stuck or need more info, I threw together a guide with info from the forums that may help:
http://forum.xda-developers.com/showthread.php?t=2593037
Click to expand...
Click to collapse
Thanks!
Spy_64 said:
By the way, tell me about your footer "HTC Evita Gummy 4.4.2 | Torched KK Kernel S-off | 2.14 | Modified TWRP 2.6.3"..... Cooked rom? How do you like it? How does it compare to stock?
Click to expand...
Click to collapse
It's a really good Rom. Extremely stable with excellent battery life. It's my current "go to" Nandroid back up I use during the day now. I flash new Roms almost daily when I don't need the phone for work. It's based off AOSP and that's what I like most about it. It has tweaks but not too many. For someone making a jump to 4.4+ Roms, I would highly recommend this one as a starter. We are very fortunate to have many like this and I'm getting around too try all of them (we are very lucky to have some talented individuals working Roms in our Forum.)
As for stock, I have to be honest, I can hardly remember what stock is like. I tried most of the stock Roms a few months ago and I have Nandroid backups of them. I remember a few were very stable but as I said, I'm a sucker for pure AOSP.
AHHH shoot, I suppose I just fielded a question meant for Timmaa, my bad!
Madcat8686 said:
It's a really good Rom. Extremely stable with excellent battery life. It's my current "go to" Nandroid back up I use during the day now. I flash new Roms almost daily when I don't need the phone for work. It's based off AOSP and that's what I like most about it. It has tweaks but not too many. For someone making a jump to 4.4+ Roms, I would highly recommend this one as a starter. We are very fortunate to have many like this and I'm getting around too try all of them (we are very lucky to have some talented individuals working Roms in our Forum.)
As for stock, I have to be honest, I can hardly remember what stock is like. I tried most of the stock Roms a few months ago and I have Nandroid backups of them. I remember a few were very stable but as I said, I'm a sucker for pure AOSP.
AHHH shoot, I suppose I just fielded a question meant for Timmaa, my bad!
Click to expand...
Click to collapse
Thanks for the insight. (c; Know of any place i can see screenshots or more info? better battery life is very important to me. I have been steering clear of aftermarket rom's because it always seems that there is always one thing or another that doesn't work... and it always seems to be either or a combination of, tethering, GPS, MMS, or wifi, all are rather important to me. (c;
Spy_64 said:
Thanks for the insight. (c; Know of any place i can see screenshots or more info? better battery life is very important to me. I have been steering clear of aftermarket rom's because it always seems that there is always one thing or another that doesn't work... and it always seems to be either or a combination of, tethering, GPS, MMS, or wifi, all are rather important to me. (c;
Click to expand...
Click to collapse
The Roms are in the development and original development threads. I don't want to steer you down the wrong path and tell you that one Rom is better than another because that's not the XDA way. It implies that one dev's work is better or inferior in some way (plus it's against the rules.)
I can recommend Gummy Rom as a starter if you are ready to try out a custom Rom. I like it and I consider it a daily driver but a couple of the others are just as good. You just have to flash and find out. Many of the 4.4+ Roms on our Forum are stable and work really well.
well I have tried two different PC's running different OS's, and two different USB cables and I cannot get past
....
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (11/120)
Waiting
Test 2: Booting device
Waiting for ADB (49/120)
Device detected.....................
[TTTT********************************************** **********]
Press ENTER to exit
Click to expand...
Click to collapse
when running rumrunner. I cannot seem to find anything out there that fixes it either )c;
Any thoughts?
Sometimes Rumrunner says it's failed but it has actually worked, does it still at s-on in your bootloader?
Sent from my Evita
timmaaa said:
Sometimes Rumrunner says it's failed but it has actually worked, does it still at s-on in your bootloader?
Sent from my Evita
Click to expand...
Click to collapse
Yah bootloader still says s-on. )c;
It's possible that it's the ROM/kernel that's the problem. You might consider flashing the latest MagioRom, I've had confirmed reports of success with that ROM.
Sent from my Evita
timmaaa said:
It's possible that it's the ROM/kernel that's the problem. You might consider flashing the latest MagioRom, I've had confirmed reports of success with that ROM.
Sent from my Evita
Click to expand...
Click to collapse
Wont I lose all my data doing so?
What do you mean by data? If you mean your images, music and such on your sd card, no you won't lose it. You never lose that when changing ROMs, I've flash multiple ROMs every week for the last few years and I've never once lost that data in all this hundreds of flashes.
You will lose your text messages, call logs, apps, stuff like that, but you can use several apps to back those up before you flash and then restore it afterwards. Do you use Titanium Backup? If not I suggest you look into it, it allows you to backup pretty much everything.
Sent from my Evita
timmaaa said:
What do you mean by data? If you mean your images, music and such on your sd card, no you won't lose it. You never lose that when changing ROMs, I've flash multiple ROMs every week for the last few years and I've never once lost that data in all this hundreds of flashes.
You will lose your text messages, call logs, apps, stuff like that, but you can use several apps to back those up before you flash and then restore it afterwards. Do you use Titanium Backup? If not I suggest you look into it, it allows you to backup pretty much everything.
Sent from my Evita
Click to expand...
Click to collapse
Mainly just, well data and apps...stored on sd or internal storage. That's great news though!
No problems. The rule of thumb is this: if it's worth worrying about it's worth backing up, just in case.
Sent from my Evita
I was going to backup using twrp to USB and an OTG cable but apparently that is not implemented in this kernel... so now its onwards to titanium backup... i haven't tried it for a few years now.
another question.... the romrunner page has modified hboots for htc one....does that include onex? could I use it once i get this all sorted out?
No. You don't want to use a modified hboot. Also, in TWRP recovery you can use the mount usb storage feature so your internal storage shows up on your PC and you can backup that way.
Sent from my Evita
Hey folks,
after making few mistakes in the past flashing wrong recovery's and unlocking the One Mini with HBoot 2.22 I thought of making a little information thread for all users, who want to unlock/root/flash custom firmware on their phones.
Here are just few important things you have to check before flashing or unlocking:
Check if HBoot is 2.22:
First, go into the bootloader by pressing and holding the "Power + Vol. Down" Button with the phone on OR off, as long as the phone is in Bootloader.
Now you can check your HBoot Version.
- If it says HBoot 2.21 or lower, you just have to backup all of your SD-Data, just for security reasons.
- If it says HBoot 2.22, also backup your Data AND be careful which recovery you want to flash.
TWRP:
If you like TWRP, please DO NOT flash Version 2.7.0.0. or lower. WHY isn't really important for new users, just don't do it.
Few changes were made since HBoot 2.22 and older recovery's could instantly wipe all of your data and/or don't let you access your internal memory ("SD-card") for making a nandroid backup.
TWRP made a new Version 2.7.0.8. for you, so please use this one. Head over this link, for your download. If your are on HBoot 2.21 or lower, you can also flash the new one.
CWM:
If you like CWM, it's the same procedure, as older Versions may not work well with the new HBoot. For me, I cannot find any updated version and I am not sure which version works fine with new HBoot 2.22.
CWM 6.0.4.8. is the newest one, eventually somebody can confirm, that this versions works with the HBoot.
For the download, just follow this link and scroll down to the "m4" device. But I can say it again, please use only TWRP for now.
So for now, please use TWRP, it should work with all Custom Firmwares so far.
One last important thing: I am not 100% sure, if flashing a new recovery, even the new one, would wipe your data or not. So please be aware, that flashing a new one could erase all of your app data/settings/contacts/data on SD.
If it is possible for you, use the HTC Backup App to backup your data.
Hopefully I can help "newbies" to prevent them of losing all of their data by simply flashing a new recovery, just as I did.
If you have any questions, I try to keep this thread up to date and answer your questions with my knowledge I earned the last few days.
Have fun with your phone and a nice day!
Cheers,
Patrick
Many thanks!
Sent from my GT-I9000 using Xparent Green Tapatalk 2
I want to use clockwork recovery because the twrp-2.8.6.0-m4 dont let me access the backup of my stock rom
I can ensure you as it was the first time that I rooted my HTC One mini it was a very bad experience
Could somebody confirm me if it is compatible with 222 with no issues?
Patrick I owe you a great big thank you! ... I hope you get this reply, even though it may be over 2 years since your post.
Your tip solved a boot loop problem that has had me going crazy for over 3 gruelling days, and despite the fact that I had read, and tried every thing I could on here -
I recently posted for help, but sadly got none - how happy the day I stumbled across your post.
I am quite amazed how little response you have had,
and even more amazed that all the rom developers on here don't mention that TWRP can cause such problems with HBoot 2.22, even though it may be in other threads.
In my opinion stating what TWRP one would need with a specific rom should be stated on the top of an OP's actual rom page.
best regards man!
Kevin
So I lost my phone this week, and my buddy offered me up his old Inspire for free. He didn't mention the fact that it's like, midway through a failed flash (soft-bricked, I guess?). I've been searching and reading, but I just seem to get further down the rabbit hole with what exactly I'm supposed to do. Really, I haven't run across any threads with this problem yet.
It's currently S-ON, but has CWM installed. There doesn't seem to be a rom installed, because it'll hang on the HTC splash screen on boot (matter of fact, he didn't even give me an SD card with the phone, so I had to scavenge one of my good SanDisk ones) and I'm not entirely sure where to go from here to get it up and running. I don't care much for the Inspire's stock rom, but at this point I'm in dire need of a phone and if it's easier to go back to stock than it is to fix this mess and have a nice ROM, I can live for a little while.
What should I do, and how exactly should I do it? It's been quite a while since I tried this (and even then it was with my lineage of janky huawei handsets).
EDIT: I've got a screencap of the info but the board spam prevention won't let me link it.
***UNLOCKED***
ACE PVT SHIP S-ON RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.10.04.03_M
eMMC-boot
burk992 said:
So I lost my phone this week, and my buddy offered me up his old Inspire for free. He didn't mention the fact that it's like, midway through a failed flash (soft-bricked, I guess?). I've been searching and reading, but I just seem to get further down the rabbit hole with what exactly I'm supposed to do. Really, I haven't run across any threads with this problem yet.
It's currently S-ON, but has CWM installed. There doesn't seem to be a rom installed, because it'll hang on the HTC splash screen on boot (matter of fact, he didn't even give me an SD card with the phone, so I had to scavenge one of my good SanDisk ones) and I'm not entirely sure where to go from here to get it up and running. I don't care much for the Inspire's stock rom, but at this point I'm in dire need of a phone and if it's easier to go back to stock than it is to fix this mess and have a nice ROM, I can live for a little while.
What should I do, and how exactly should I do it? It's been quite a while since I tried this (and even then it was with my lineage of janky huawei handsets).
EDIT: I've got a screencap of the info but the board spam prevention won't let me link it.
***UNLOCKED***
ACE PVT SHIP S-ON RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.10.04.03_M
eMMC-boot
Click to expand...
Click to collapse
My strong hunch is that he didn't flash the boot.img in the ROM zip, which you need to do for S-On Unlocked phones. When you flash a ROM in the recovery, make sure you also fastboot flash the boot.img from the ROM zip. The Ace Think Tank thread in DHD General has links with instructions on how to do that.
bananagranola said:
My strong hunch is that he didn't flash the boot.img in the ROM zip, which you need to do for S-On Unlocked phones. When you flash a ROM in the recovery, make sure you also fastboot flash the boot.img from the ROM zip. The Ace Think Tank thread in DHD General has links with instructions on how to do that.
Click to expand...
Click to collapse
Aha! That did the trick. I just flashed Carbon on this thing, but now the Android keyboard won't work. It's okay, I'm sure I can fix it. Thanks for the help!
Yeah, that'll be an issue for the ROM thread. Though of course, if you didn't full wipe first, try that.