I have a really strange issue and I've done everything I can think of to fix it to no avail. I'm hoping someone here can give me a few pointers.
I'm working on a Inspire 4G for someone. The issue is that the phone reverts to a specific state no matter what I do. For example, if I wipe the phone, the phone boots back up to Froyo with all of his stuff on it. If I try loading an RUU or IMG file (Froyo or Gingerbread), it will "take" but boot to Froyo with all of his stuff on it. It's almost like it wipes itself and loads this image out of nowhere...
Another weird thing, which may or may not be related, is that I see a weird download in his notification tray. Apparently, the file named "WinBej2Setup.exe" was downloaded twice. I did some research on that and everything I see points to some kind of malware for a Windows PC.
Any and all help is appreciated.
Forgive me if this sounds stupid, but you do have S-off correct? I'm not sure about the weird file, have you tried to access it? Also what other roms have you tried to flash? Also what method did you use to root?
Sent from my Inspire 4G using xda premium
I don't have S-OFF. Here's all the bootloader info:
ACE PVT SHIP S-ON RL
HBOOT-0.85.0019
MICROP-0438
RADIO-26.06.04.06_m
Emmc-boot
Dec 27 2010, 14:47:30
As for the file, I'm not sure where it's located. I can only see the notifications that they have finished downloading.
As for the history on the phone, I really can't say much since it's not my personal phone. The person I'm doing this for said he tried to root it using the ACE Hack kit and "some ADB commands" and failed. That's all the information I was given.
At this point, I can load anything to the phone but it will just revert to Froyo in the exact state that it's currently in.
For example, I just tried installing Gingerbread via the official RUU file. It goes through the entire process without a hiccup. Then it reboots and takes forever to load; but when it does, it's back on Froyo with all the owners files...
Personally I would root it, make sure s off, and make sure to format the memory card the corrrect way also.
Then I would install a custom rom.
And the file you speak of is also a game called bejewled. My girl loves that game.
Sent to you by ......
This p-o-s I'm addicted to, and my woman is jealous of.
Reformat the sd card then do an official upgrade thru HTC. Go to the website and download the Gingerbread RUU and HTC Sync. If this doesn't work, complete the root process as suggested.Tell your friend you can't install exe files on Android. They need to be apk files or zip files if installed thru recovery.
Sent from my Inspire 4G using Tapatalk
I appreciate the advice guys, but I think you guys are overlooking what I'm trying to say... I've already tried running the official upgrades from HTC. The RUU says it's completed fine, but on reboot, I'm back on Froyo with all the same stuff on it.
I've even gone as far as extracting the IMG file out of the RUU and loading it through the bootloader. If I do this, it does the same thing-- says everything loaded fine but reverts on boot back to Froyo in the same state it was in prior.
I can temp root the phone using psneuter but that's about it. I have no idea how I'm going to achieve S-OFF if everything I do is wiped on reboot...
What I'm wondering is if there is a way to lock the entire phone down in a state where nothing can be changed; and if so, is there a way to disable this feature.
Are you sure you do not have a file on the root of the card named PD98IMG.zip? You may be installing this every time the phone boots.
How can you install a non RUU ROM when you have s-on?
Something does not make sense here. Also the exe file you talked about has no use on android as android can do nothing with it. Where do you actually see it?
Go back to square 1. What ROM is on the phone now? Do you have clockwork installed?
I'm not sure how to many different times/ways I can explain the same thing. The phone is on stock AT&T Froyo 2.2.1 (1.80.502.3). Currently, there is no custom recovery and it's not rooted.
The issue is that the phone always reverts (almost like it's doing a nandroid restore in the background) during boot to Froyo 2.2.1 (1.80.502.3) with all his stuff on it.
I've installed Gingerbread 2.3.3 (2.47.502.7) via the official AT&T RUU file
I've extracted the PD98IMG.zip from the Gingerbread 2.3.3 (2.47.502.7) RUU and loaded it via bootloader
I've installed Froyo 2.2.1 (1.80.502.3) via the official AT&T RUU file.
I've extracted the PD98IMG.zip from the Froyo 2.2.1 (1.80.502.3) RUU and loaded it via bootloader
I've done a factory reset from within the phone
I've deleted user data & cache with the stock recovery
After performing each and everyone of these steps, the phone hangs on the white HTC screen while booting and eventually boots up to Froyo 2.2.1 (1.80.502.3) along with all the guys stuff on it.
How can you install a non RUU ROM when you have s-on?
Click to expand...
Click to collapse
I don't believe I've ever said that the phone has a non-RUU ROM...
Also the exe file you talked about has no use on android as android can do nothing with it
Click to expand...
Click to collapse
I agree completely; however, the issue I'm running into very unusual. With that being said, I'm trying to point out anything unusual that I notice with the phone. This file most likely has absolutely nothing to do with the problem I'm encountering, but I mentioned it just in case.
Are you sure you do not have a file on the root of the card named PD98IMG.zip? You may be installing this every time the phone boots.
Click to expand...
Click to collapse
I wish this was the case; however, this wouldn't explain why all his stuff is still on the phone... The only time there is a PD98IMG.zip on the sdcard is when I put it there. Even so, I would have to boot the phone into bootloader mode and go through the prompts to get it take. More so, even if I did do this, it would just revert upon rebooting (hints the problem).
I appreciate the help but I think the problem is a little deeper than what has be presented.
That clears it up for me. You obviously know what you are doing. You mentioned "wipe" a few times which confused me. Didn't think there was a way to actually wipe it without a recovery installed. Sounds like one helluva confusing issue there. Goodluck.
Its always going to revert back to the previous state because its still s-on.
You need to get s-off before anything will change.
Sent from my Inspire 4G using xda premium
Its always going to revert back to the previous state because its still s-on.
You need to get s-off before anything will change.
Click to expand...
Click to collapse
This I know is not true-- You can load signed code with S-ON. If what you said was true there would be no way to load an official RUU or OTA...
I appreciate the help, but telling me to get S-OFF (which I've clearly stated that I'm unable to do) is not getting me anywhere.
Is the original ROM branded? Have you tried installing a PD98IMG.zip from a gold card? Just a thought.
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 one SV on cricket (US)
K2_PLC_CL (s-on) still
Ok so it was all stock from store. Tan I did this in order:
1.) Unlocked bootloader from HTC dev...
2.) (flashed) Installed CMW v6.0.2.8 via ADB
3.) MADE BACKUP with CWM
4.) Rooted by flashing a zip via CMW (worked great)
5.) tried moonshine.io for s-off tried twice. Failed
-program (distiller) closed after saying "moonshining 1...2...3...to 10)
-now on boot it gets to "Htc
I booted into CMW and retored that backup i had before any rooting or s-off etc... but it still hangs :silly:
Should I try the hboot option to restore? (I thought CMW backup was like a complete nand backup. Which should be bullet proof right?)
Thanks for looking guys! I have no communication as of now I just want to make calls at least
This is my first android device and I always like getting to know my devices from the inside, the iphone BS was too much haha. I gues i dont really need s off or super cid if it means no phone. but why not if it works.
Did you have ICS or JB, when you have tried S-off?
Please remember, as long as you are S-on you must flash the boot.img with fastboot commands (also, if you are restoring a backup and you did a full wipe)! If you have a cwm backup, boot.img should be inside of your backup folder.
Did you wipe everything before your restore? Maybe fragments of moonshine still there.
Did you try TWRP recovery?
[HTC oneSV boot hang, FIXED] THANKS!!
LOL I had no idea the boot.img had to to be manually flashed, thank you very much it work s great now!
This time I cleared/wiped data AND cache. it still hanged and wont boot. Than I re tried using CWM again to restore (still hangs). than I flashed boot.img THAT DID THE TRICK after "fastboot reboot".
BTW major fail on my part; I was rooting and moonshining for JB it turns out I have ICS (i forgot to update) now that you mentioned it hehehe
I had 4.0.4 sense 4.1. I think that is why everything went to hell...
Alright Ill try moonshine after the update to JB 4.1.2 if that fails than Ill try the facepalm.
One last question; if i do update to JB 4.1.2 and achieve s-off could I use that CMW backup to always go back to ICS 4.0.4? (just incase I ever wanted to get SUPER CID and get JB 4.2.2) I wonder if super cid works with k2-PLC-cl.... Ill try it when I get find the funds a better phone to risk a brick
-Thank you sir!
Ok, lets bring a bit light into these darkness:
- Facepalm S-Off only works, as long as you did not achieve the JB update!
- You can restore a ics cwm backup, also when you are on JB and S-Off, but
- Restoring ics from a backup is not the same, as you where on ics before the update.
Thats because of the updated hboot (ics-> hboot 1.0; jb-> hboot 2.0). In hboot 2.0 the Supercid/Facepalm exploit is fixed. You can still get Supercid under hboot 2.0, but you must do moonshine S-Off before.
So, at all you must think about, what you want and whats the best way to get, before updating to jb.
If this was to difficult to understand, ask again and i will try my best to explain it for you to understand.
Ok
Hum they creators of these phones really enjoy making puzzles for us don't they...
Alright so my options are:
1.) [stay on ICS]
-get super cid
-facepalm for s-off
(can I still update to JB after this and still have super cid and s-off? But that would install hbot2 wouldnt it? so....)
I think I want method 2↓
2.) [update to JB]
-use moonshine to get s-off
-some how get super cid? (I dont really need super cid but it would be nice to know I have it just in case)
-profit
//edit//(ohh yes, once on JB hboot v2, if i have s off and on hboot2 could I go back to hboot1 along with ICS should i need to)
Any ways thank you again
1. Right, you can update and both will stay.
2. Right, after S-Off you should be able to change SuperCid. But it should be said, that its a very risky operation and phone can be bricked very easily if you are doing something wrong.
And for your edit: You can restore a ics backup, but without a RUU it is difficult to bring back hboot 1. Only a backup of it will solve this. Recoveries usually don't backup hboot.
SV ICS super cid
I know this thread : http://forum.xda-developers.com/showthread.php?t=2264322
says to do super cid on original stock, but could I just go ahead and HEX my cid with my ICS that is unlocked/rooted/custom-recovery?
Do I have to un-do all of that to change the CID? or is that just good technique? [im also on cricket ics 4.0.4 if it matters, k2_plc_cl]
Thank you very much! I wish to change my cid right now but ill wait and see what you say if it saves me from a brick
than I'm off to s-off for all the goodies that follow haha.
I don't think, that this will be important, because SuperCid is located in a partition which has nothing to do with root or recovery.
alrighty than
haha wrong link in previous post I meant this one: http://forum.xda-developers.com/showthread.php?p=26516911#post26516911
WHEN HTCDEV UNLOCKS YOUR DEVICE YOU MUST START FROM SCRATCH!!!
Click to expand...
Click to collapse
I was reading his link and somehow posted your link, Ill use your link actually now that I read it... I thought it wouldn't matter, better safe than sorry. Ill try it out and see how it goes.
Thanks for helping
Questions about hexing CID
old.splatterhand said:
I don't think, that this will be important, because SuperCid is located in a partition which has nothing to do with root or recovery.
Click to expand...
Click to collapse
Alright its late and I'm not going to flash it yet ill wait to see what you make of this:
I have used hxd many times for xbox/psp/etc so i know how it works... it found 3 instances of my CID
(some info omitted as the 'x' char)
Code:
maincid=CRICK001xx.xx.cidlist=CRICK001.xx.xx.rid=105.xx.xx.modelid=PL8xxxxxx.xx.xx.report=com.xx.xx.skulist=1xxx.xx.xx.taskid=30xxxx.xx.xx.mainsku=1xxx.xx.onecid=1.xx.cwkey=CRICK001.ro.com.google.clientidbase=android-htc //more stuff after........
Im assuming only the first instance "maincid=CRICK001" needs to be 11111111
(or should all 3 instances of "CRICK001" be changed to 11111111)
Ill give it a go after work tomorrow when Im confident that my modifications wont render my phone as a door stop.
I need to buy you a beer, but the donation is in german, ill have to translate it when I get done
Gain_Medium said:
Alright its late and I'm not going to flash it yet ill wait to see what you make of this:
I have used hxd many times for xbox/psp/etc so i know how it works... it found 3 instances of my CID
(some info omitted as the 'x' char)
Code:
maincid=CRICK001xx.xx.cidlist=CRICK001.xx.xx.rid=105.xx.xx.modelid=PL8xxxxxx.xx.xx.report=com.xx.xx.skulist=1xxx.xx.xx.taskid=30xxxx.xx.xx.mainsku=1xxx.xx.onecid=1.xx.cwkey=CRICK001.ro.com.google.clientidbase=android-htc //more stuff after........
Im assuming only the first instance "maincid=CRICK001" needs to be 11111111
(or should all 3 instances of "CRICK001" be changed to 11111111)
Ill give it a go after work tomorrow when Im confident that my modifications wont render my phone as a door stop.
I need to buy you a beer, but the donation is in german, ill have to translate it when I get done
Click to expand...
Click to collapse
At this point i only can tell you about my guide and the picture inside. To be honest, i only noticed only one cid, together with imei. So maybe this helps you.
Edit:
Please, really be careful if your file/block is different than in my guide!
I'm on mobile and can't look at your code completely.
My guide for sure works for k2u & k2ul cause i did it myself at two different phones but i don't know, if cricket has changed more and i don't want your phone bricked.
Edit2:
I really not sure, if changing CID will work. Maybe you'll try the S-Off step by Moonshine after update to JB, would be better than a bricked phone!
You must also think, what do i profit from SuperCID?
K2u & k2ul can be unbranded this way, maybe they also profit from earlier updates.
But you can't use k2u/l Software on US phones, different network, so this point is useless for you. And i don't think, cricket will release their updates earlier for phones with SuperCID.
Just my two cents, now its on you to make your decision...
What i also want to say, i had help the first time i did.
It was @jmz who helped me, maybe he reads that and know more about cricket cid.
I think ill give it a go
I actually tried to contact him and others, but since im so new I can't send PMs (they send but nothing is in my sent box. link it never happened) so I guess unless JMZ stumbles upon this thread thats it.
As for me I don't think it would brick my phone (like a real brick) if all else I could just boot into recovery and flash back my backup stuff right?
Or if i screw up would it not even allow recovery / shell? Although a brick would permit me to buy a better popular phone
If i try it all post more details on it for other cricket users.
This is modifying the bootloader. If you do something wrong, the phone wont boot. Not in recovery, not in OS, bricked.
PS. @Gain_Medium
If you write a xda username with an @ before, the one will be notified, the he is mentioned somewhere
Side note: I don't believe that there is any reason for super cid on a cricket us carrier, unless you plan on traveling to Europe, Asia, or anywhere out of the continent.
Yes, it's cool to have accomplished superCID. But there is really no benefit here in the US, if you plan on maybe using a different service plan provider, you'll still need to unlock your SIM, even if you do achieve superCID without bricking.
Good luck with your decision. I hope to read your updates on what you have chosen. And how everything goes for you.
THESE ARE ONLY MY THOUGHTS AND OPINIONS. NOT TRYING TO SWAY YOU AWAY FROM ATTEMPTING ANYTHING.
but please research superCID for cricket mobile and see what you find.
Pros vs Cons