Hello everyone. I am having an issue and cannot seem to understand what I am doing wrong. I have a view I got for Christmas. It seems like it was partially got the OTA updates. It ran for a while and then started just cycling through the power on / sprint 4g splash screen then would reboot. I can get into Fastboot. I have been messing with it for a few days. Here is where I am at. I was able to find this link http://forum.xda-developers.com/showthread.php?t=1423397 and follow the recomendations there. I flashed the firmware.zip and that went fine then i was able to unlock the bootloader via the HTC dev site (I was unable to do this prior to flashing). After that it seems that everything else fails.
on the fastboot screen I am showing:
unlocked
express PVT SHIP s-on RL
hboot-1.14.0005
microp-0656
radio-1.05.01.1006_3
emmc-boot
c:\htcview>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.14.0005
(bootloader) version-baseband: 1.05.01.1006_
(bootloader) version-cpld: None
(bootloader) version-microp: 0656
(bootloader) version-main: 2.23.651.1
(bootloader) serialno: HT163HY00369
(bootloader) imei: 355195000000017
(bootloader) product: express
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG4120000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4116mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: f821d4db
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.007s
I have tried flashing:
RUU_Express_KT_KT_KR_1.24.1010.1_Radio_20.35c.30.089BU_3809.06.05.01_M_release_199840_signed
which fails once it hits the signatures on the install. So it is communicating and deletes the user data and starts the install. I have tired several different RUU packages and they all fail. Right now this thing just reboots constantly. any ideas? Suggestions?
Thanks,
Aaron
Wait, are you implying that OTA updates bricked your stock view?
You are not rooted or s-off'ed or anything, is that correct?
the only thing I did was try to unlock the device via the htcdev site. followed their instructions and then started getting the reboots not sure what I did wrong. I would like to be able to s-off and load custom roms but I cannot get anything to load. I have tried the viper rom and also the ruu file in the above post. I do not believe I am rooted but I cannot tell as I cannot boot into the operating system. I can get to the fastboot menu and I can get into Revolutionary CWM v4.0.1.4 console. I am stuck there as nothing else seems to load or install. everything keeps failing.
Downgrade to Gingerbread using RUU and then run revolutionary then just use the update method posted in the forums.
the problem is that when I run the RUU it fails. I cannot get anything to complete for me to be able to even get the system up. The ruu starts and eventually gives me an error stating it cannot communicate with the phone.
still trying different things, but have not progressed anywhere past that yet.
Fastboot flash a recovery (i made a supertool that flashes a recovery its in flyer and view development boards.)
Sent aboard the Evo Express
where do I find the recovery image?
....I suggest you just use the tool I made. It comes with all the images you could need and automatically chooses your device. You just decide which recovery you want and you need to declare which OS you're on (Honeycomb or Gingerbread)
cool got it. Finally got an image to take. Thanks for all your help!
Related
Hello, I’m having trouble fixing my girls phone and could use some help I’m posting here as a last resort. Here’s the situation.
Phone is HTC EVO 3D S-ON and has never been S-OFF or Rooted. But the phone has stopped booting and I can only get into Hboot and fastboot I have tried flashing the OTA RUU buy placing the PG86IMG.zip on the root of the sdcard and also pushing the file buy fast boot and I keep getting a sig check error “FAILED (remote: signature verify fail)”
The RUU is the same version that I am running now here’s the file name but its not the only one I tried.
PG86IMG_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2_Radio_1.09.00.0706__NV_NV_SPCS_1.43_release_271101-signed.zip
Output from fastboot
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.58.0000
(bootloader) version-baseband: 1.09.00.0706
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.89.651.2
(bootloader) serialno: HT17DHX15682
(bootloader) imei: 355195000000010
(bootloader) product: shooter
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG8610000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3800mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-3f645641
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Can anyone help me here im stuck???
Are you htcdev unlocked? If so, you need to run "fastboot OEM lock" from the cmd
Sent from my PG86100 using xda app-developers app
Jordan Cason said:
Hello, I’m having trouble fixing my girls phone and could use some help I’m posting here as a last resort. Here’s the situation.
Phone is HTC EVO 3D S-ON and has never been S-OFF or Rooted. But the phone has stopped booting and I can only get into Hboot and fastboot I have tried flashing the OTA RUU buy placing the PG86IMG.zip on the root of the sdcard and also pushing the file buy fast boot and I keep getting a sig check error “FAILED (remote: signature verify fail)”
Click to expand...
Click to collapse
If the phone is completely stock (locked bootloader and S-ON) you can only run the RUU from Windows, since any PG86IMG.zip file flashed from the bootloader in that configuration has to be signed by HTC. You can download the 2.89.651.2 RUU.exe from one of the links in this post and give that a try, but it sounds like there might be something else wrong with the phone.
ramjet73
I bought a T-Mobile USA HTC One from a guy who said it would randomly reboot. When I got it, it was S-ON had Bixie GE Rom and would reboot consistently about every 3 minutes. I managed to downgrade to get S-OFF and have spent a week trying every back-to-stock guide, RUU, firmware flash, Nandroid backup imaginable for both Sense and GE. On GE, I can at least get past the intro and use the phone until reboot, but Sense will always boot to the lock screen and never go further. Any Sense Rom or RUU would not bring up the initial setup. All still had a 3 minute reboot.
Of everything I tried, the [ROM] [AUG 3] [ANDROID 4.3] 3.06.1700.10 - Stock HTC Google Play Edition v1.1 was the only one to fix the reboot issue, but I'm still not able to get service (Baseband and IEMI unknown).
I accept there might be problem with the SIM slot, but does anyone happen to know why this particular Rom would work when everything else failed? All my Google-fu point toward using RUU's, but they simple will not stick, unlocked, relocked, stock recovery, you name it.
T-Mobile Kernel issue?
Any help is appreciated.
does it go into the bootloader and can you get fastboot usb going? try doing
Code:
fastboot getvar all
and see if it looks normal. use mine for reference.
This is after I tried stock
Sieze said:
does it go into the bootloader and can you get fastboot usb going? try doing
Code:
fastboot getvar all
and see if it looks normal. use mine for reference.
Click to expand...
Click to collapse
Yes, it goes into bootloader just fine. This is my getvar after my last attempt at T-Mo RUU:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.531.11
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA**********
(bootloader) imei: 355**************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4042mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.069s
looks normal too me. have you tried a cutsom kernel? and have you tried full GPE conversion at any time?
it deffinately sounds like the phone is being a boner. if you have TWRP flashed try doing a factory data reset through it and see if it has issues wiping certain things most namely cache and dalvik cache.
and if after you do that nothing presents itself make sure youve got a ROM zip in phone storage or on a flash drive for use with usb otg and wipe system then try and flash a stock ROM and see if it fixes it.
best of luck and hopefully you get it working.
Hi!
After reading massive amounts of tutorials and forums, I just have to admit I cannot handle this and a little help would be nice!
I just bought a nice second hand HTC One (the European m7_ul version, it seems) and there is a big problem: I cannot install any ROMs and the phone just kind of gets into a boot-recovery (ClockworkMod) loop.
This phone has been ridiculously tampered with no knowledge, so it's very hard to pinpoint what on earth has happened in the past. That is why I got it quite cheap. Nice, but now it does not work as a phone at all after I tried some recovery techniques myself.
THE HISTORY AS FAR AS I UNDERSTAND:
-The phone has been first rooted in order to install custom ROMs: Android Revolution HD etc I think.
-It has also been S-offed
-The original user tried to do a "Total factory reset", he wanted the phone to be completely "Stock". He failed-ending up with S-On BUT Tampered/Unlocked etc..
WHAT HAVE I TRIED:
-Tried to OTA Update as the system offered this option. Didn't work, because of Status 7 error on ClockWorkMod.
-Same problem with all of the ROMs I downloaded and then tried to install from SDcard/Sideload (Status 7 error)
-Tried also fastboot flash recoveries, just ending up in a boot loop with HTC logo and sometimes even the exclamation mark+red triangle.
-Frustrated and tired, tried also several instructed ways of S-OFF (Which probably was a dumb idea also).
THE STATUS NOW:
-HTC One only boots into the HTC Logo Screen/ClockWorkMod, but does not let me install any of the ROMs I've tried.
INFO:
Fastboot getvar all gives me:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4010mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I also got some info from the last known working system while it still was running, before the stuck-in-boot-loop-era:
Android Version 4.3
Sense 5.5
Version 3.62.401.1
HTC SDK API 5.65
Build 3.62.401.1 CL264544 release-keys
The big question: IF it was first rooted, s-offed and then messed up completely (S-on seems to be now forever), is there still hope to get it to work?
--
UPDATE: Got it booting after installing Android_Revolution_HD-One_51.0, which seems to work OK. Normal fastboot sideload installation. I think this phone has been locked (S-ON) while using this exact ROM (Android_Revolution_HD-One_51.0, even the build numbers seem to match with the previously mentioned system. Still, no other ROM can be installed on this phone.
So, seems like we're just stuck with Android 4.3 and I need to backup closely. Am I completely lost with this S-ON theory?
--
Thanks!!
** UPDATE **
Got past the stuck screen by doing this:
http://forum.xda-developers.com/showthread.php?t=2386084 Jeez.
Tried to install the .12 RUU but this failed repeatedly with an error 155. Wasn't sure if this was caused by a newer HBOOT or a different firmware. Downloaded a KK RUU from here:
http://forum.xda-developers.com/showthread.php?t=2428276
Almost back to stock. Now need to get rid of the RELOCKED message in the bootloader. Will attack that later.
I'm trying to get my phone back to stock so I can return it to AT&T due to the purple camera problem. What I was attempting to do was to restore a 4.1.2 JB nandroid backup, then install an RUU as described in post #55 here:
http://forum.xda-developers.com/showthread.php?t=2394155&page=6
I had changed the cid number back to CWS__001 and restored the nandroid backup. When I went to reboot the phone I got the AT&T animation, then the HTC One screen. This is where I'm stuck. I can't reboot into recovery or anything. Is this phone recoverable or am I SOL? Thanks for any help.
These were my settings before I started this.
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT*************
(bootloader) imei: ********************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4103mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.073s
Stay s-off, lock bootloader with revone -l, then flash 3.17.502.3 RUU. That should do it.
RUU : http://www.androidruu.com/getdownlo...13_10.38j.1157.04_release_334235_signed_2.exe
I'm also trying to revert to stock in order to return to HTC for purple tint issue. I am running an AT&T HTC One.
Originally, I followed the instructions on this thread and basically converted my phone to GPE (http://forum.xda-developers.com/showthread.php?t=2358781).
To revert to stock I followed these instructions (http://www.htc1guru.com/guides/return-stock-guide/) multiple times and kept failing getting the error 155 message. I was using the RUU.exe file. Eventually I got stuck and decided to follow another post on a different site. That post had me re-lock the bootloader and rever to S-ON. Then all went to hell. Bootloop city.
I was able to load TWRP recovery and I side-loaded a different ROM that I had from when I was first tinkering around with custom ROMs (the one described here http://htconeroot.com/htc-one-stock-roms/android-4-4-kitkat-sense-5-5-stock-rom-for-htc-one/). It booted but threw tons of errors and was unusable. So, I re-unlocked my bootloader (still S-ON) and this time ran the RUU.exe (named RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.14.3250.13_10.33.1150.01_release_318450_signed_2.exe). Only instead of run through the GUI I tried to use fastboot to load the rom.zip that was extracted to a temp folder. It ran but ended up failing with the error "FAILED (status read failed (Too many links))."
I believe I then reinstalled the rom from (http://htconeroot.com/htc-one-stock-roms/android-4-4-kitkat-sense-5-5-stock-rom-for-htc-one/) and now it it boots and is "working."
Here is where I am at:
TAMPERED
UNLOCKED
S-ON
hboot 1.54
TWRP 2.6.3.3 recovery (note: when I boot into recovery i see a Google logo with an unlocked padlock)
this ROM, rooted: http://downloadandroidrom.com/file/HTCOne/M7/roms/Sense4.4/One_4.06.1540.2_odexed.zip
When I boot the system from power off I get the htc animation with no other warning text
If I boot the system from TWRP recovery I first get the Google logo with an unlocked padlock, followed by the htc animation with no other warning text.
I assume I need to go back to S-OFF, lock the bootloader and run an RUU, but I'm concerned about the error 155, as well as the "too many links" error.
Here is the log from the RUU.exe that fails:
Code:
<T135636><DEBUG><CMD>htc_fastboot -s H******* -d flash zip C:\Users\o****\AppData\Local\Temp\{A08E6688-8B3D-493C-BEF3-013152BF8F99}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip</CMD>
</DEBUG></T135636>
<T135844><DEBUG><OUT>sending 'zip'... (1029872 KB) OKAY</OUT>
</DEBUG></T135844>
<T135844><DEBUG><OUT>writing 'zip'... (bootloader) adopting the signature contained in this image...</OUT>
</DEBUG></T135844>
<T135844><DEBUG><OUT>(bootloader) signature checking...</OUT>
</DEBUG></T135844>
<T135844><DEBUG><OUT>(bootloader) rom parsing start ...</OUT>
</DEBUG></T135844>
<T135844><DEBUG><OUT>(bootloader) rom parsing finish ...</OUT>
</DEBUG></T135844>
<T135844><DEBUG><OUT>(bootloader) zip header checking...</OUT>
</DEBUG></T135844>
<T135844><DEBUG><OUT>(bootloader) zip info parsing...</OUT>
</DEBUG></T135844>
<T135844><DEBUG><OUT>FAILED (status read failed (Too many links))</OUT>
</DEBUG></T135844>
<T135927><DEBUG><CMD>adb kill-server</CMD>
Code:
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
Any help would be greatly appreciated.
cschmitt said:
Stay s-off, lock bootloader with revone -l, then flash 3.17.502.3 RUU. That should do it.
Click to expand...
Click to collapse
The revone switch worked. I wasn't sure if it would since I was on 4.4.2 and what I have READ didn't really say it would work or not since it was for 4.2 ROMs. The RUU in your link just gave me the error 155, so I installed the KK RUU I linked above. Took the phone by AT&T today and got it switched out.
BTW, thanks for the NOOB link, much appreciated, since I spend hours reading through these forums.
ZBell said:
The revone switch worked. I wasn't sure if it would since I was on 4.4.2 and what I have READ didn't really say it would work or not since it was for 4.2 ROMs. The RUU in your link just gave me the error 155, so I installed the KK RUU I linked above. Took the phone by AT&T today and got it switched out.
BTW, thanks for the NOOB link, much appreciated, since I spend hours reading through these forums.
Click to expand...
Click to collapse
If you don't mind, which RUU specifically?
ocieb said:
If you don't mind, which RUU specifically?
Click to expand...
Click to collapse
this is the only kitkat RUU for AT&T
http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe
clsA said:
this is the only kitkat RUU for AT&T
Click to expand...
Click to collapse
Thanks. Do I need S-OFF to flash this RUU? I am unlocked and rooted but don't have S-OFF and it wouldn't flash. It starts sending 1/5 and then the program freezes up and windows error recovery comes up and I get a 171 error. I'm also running TWRP recovery.
ocieb said:
Thanks. Do I need S-OFF to flash this RUU? I am unlocked and rooted but don't have S-OFF and it wouldn't flash. It starts sending 1/5 and then the program freezes up and windows error recovery comes up and I get a 171 error. I'm also running TWRP recovery.
Click to expand...
Click to collapse
no you don't need s-off .. but your not the first to have an error while trying to flash it. funny it worked fine for me
clsA said:
no you don't need s-off .. but your not the first to have an error while trying to flash it. funny it worked fine for me
Click to expand...
Click to collapse
I just get an error message saying htc_fastboot.exe has stopped working.
I tried extracting the zip from a temp folder and flashing it but I get this back:
Code:
c:\HTCOne\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot flash zip rom.zip
target reported max download size of 1526722560 bytes
Invalid sparse file format at header magi
In the meantime, I may have screwed myself up even more (or potentially not?).
After the above error messages, I went in search of an alternative method to get myself up and running again. I followed the instructions by OP in this post http://forum.xda-developers.com/showthread.php?t=2283112 and they "worked." However, when the phone boots my touchscreen is unresponsive. I no longer am lock and I have S-ON. Rest of the info should be below.
If you see my post above, I am coming from GPE. Could the baseband/radio be causing this issue?
In the bootloader I see
TAMPERED
RELOCKED
Here is my getvar dump
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT***
(bootloader) imei: ***
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4182mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e82187e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.062s
I'm just trying to get to a point where I can send this back to HTC and get my purple tint issue fixed. Any help would be greatly appreciated!
ocieb said:
I just get an error message saying htc_fastboot.exe has stopped working.
I tried extracting the zip from a temp folder and flashing it but I get this back:
Code:
c:\HTCOne\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot flash zip rom.zip
target reported max download size of 1526722560 bytes
Invalid sparse file format at header magi
In the meantime, I may have screwed myself up even more (or potentially not?).
After the above error messages, I went in search of an alternative method to get myself up and running again. I followed the instructions by OP in this post http://forum.xda-developers.com/showthread.php?t=2283112 and they "worked." However, when the phone boots my touchscreen is unresponsive. I no longer am lock and I have S-ON. Rest of the info should be below.
If you see my post above, I am coming from GPE. Could the baseband/radio be causing this issue?
In the bootloader I see
TAMPERED
RELOCKED
Here is my getvar dump
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT35GW916488
(bootloader) imei: 354439055183836
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4182mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e82187e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.062s
I'm just trying to get to a point where I can send this back to HTC and get my purple tint issue fixed. Any help would be greatly appreciated!
Click to expand...
Click to collapse
yeah I knew the rom.zip won't flash but the RUU worked ... try this RUU
http://dl3.htc.com/application/RUU_...13_10.38j.1157.04_release_334235_signed_2.exe
clsA said:
yeah I knew the rom.zip won't flash but the RUU worked ... try this RUU
http://dl3.htc.com/application/RUU_...13_10.38j.1157.04_release_334235_signed_2.exe
Click to expand...
Click to collapse
Thanks, I'll try this. Should it matter that I'm relocked and S-ON?
Also, I want to run this exe while my phone is connected to my computer and un fastboot usb, correct?
---------- Post added at 07:14 PM ---------- Previous post was at 06:51 PM ----------
Hi again,
Just failed both using the exe and extracting the rom.zip file. Any advice?
I was thinking of trying to go back to full GPE and either starting over, or just sending the device in like that and keeping my fingers crossed
cschmitt said:
Stay s-off, lock bootloader with revone -l, then flash 3.17.502.3 RUU. That should do it.
RUU : http://www.androidruu.com/getdownlo...13_10.38j.1157.04_release_334235_signed_2.exe
Click to expand...
Click to collapse
Is a locked bootloader needed to run a signed ruu.exe when S-OFF? I thought lock status didn't matter when S-OFF. Or was that to just get rid of the RELOCKED banner the OP had? I may need to run this as well, so just need to make sure. Thanks.
sharksfan7 said:
Is a locked bootloader needed to run a signed ruu.exe when S-OFF? I thought lock status didn't matter when S-OFF. Or was that to just get rid of the RELOCKED banner the OP had? I may need to run this as well, so just need to make sure. Thanks.
Click to expand...
Click to collapse
Locked bootloader is not require to RUU when s-off. OP just wanted to remove relocked.
Okay, so I've got an AT&T M7 that has has (as far as I can tell - a stock version running 4.42 and HTC Sense 6.0) the Software number is 5.12.502.2.
The problem is, that apparently something is extremely corrupted - and I get messages like "Swiftkey has stopped", except replace Swiftkey with tons of other things, as it keeps happening over and over.
If I reboot, any changes that were made (downloads, settings, ANYTHING), apparently gets erased, or is not saved.
I can boot into recovery (which is TWRP 2.7.1.1, and again - any changes I make are not actually written. I can attempt to flash roms (cm, htc1guru stock images, etc.), and they will generally go through the motions of running - and even say 'successful' at the end, but if you reboot after that, everything is still as it was before. No changes at all (think of it like Groundhog Day... every day I can kill myself, eat whatever I want, kill other people(delete stuff, change things, add things) - but after the phone sleeps (aka restarts), the day (aka the phone) is reset as if I did absolutely nothing.)
I have tried wiping cache, data, system, literally EVERYTHING and it does absolutely nothing.
Also, if I try the main Factory Reset from inside the ROM itself, it says it is doing something, but then reboots and everything is back as it was also.
I've tried fastboot boot <insert multiple recovery images multiple times.img>, and it just locks up the phone and I have to hard restart it.
I've tried fastboot flash <new recovery.img> - it actually says successful, but again - does nothing after rebooting.
I am literally going crazy here... I can push files temporarily to the device, and try to do stuff with them, but in the end nothing can seem to make any difference.
I have tried going through htcdev unlock with Unlock_code.bin, and it doesn't do anything.
fastboot oem lock does nothing
Everything I've found says maybe S-OFF would help, but I can't seem to find any way to get that done.
Please, can ANYONE help me figure out how to get this stupid thing to be at all useful again? All help is appreciated. Below is my
e:\Downloads>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: CENSOREDFORMYPARANOIA
(bootloader) imei: CENSOREDFORMYPARANOIA
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4272mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.068s
Follow the unlock your bootloader thread..
wingsltd said:
Follow the unlock your bootloader thread..
Click to expand...
Click to collapse
Bootloader is unlocked, and I have tried re-unlocking. Nothing changes. I mean, I appreciate the input - but did you even read the post above? Answers like that make me feel like I'm talking to Tier I tech support at Gateway or something.