Hi guys,
This is mostly my fault I believe. Like a young boy, excited about a new toy that just came out, I tried to flash the new Sprint OTA update in TWRP. Well, it failed just as I thought it may. Later on, I read that flashing that OTA in any recovery was something that should not be done. At any rate, it is too late to change what has been done.
The issue that I am facing, which seems to coincide with the day that I flashed the OTA in TWRP, is that people are only receiving only one part of my text messages. For instance, say I type a long message which would equal the length of 3 SMS messages. The recipient will only receive part 1/3 or part 3/3.
I updated my PRL and Profile.... No change... So, I decided to go back to stock and endure the grueling process of restoring my phone's SMS logs, contacts, configuration, etc, etc. I know that Google will sync and most of my contacts will be replaced. But some things like games I pay money to play must be reconfigured and other customizations will have to be "re-customized".
Regardless, I need to go back to stock and start all over. I tried several methods, all required that the bootloader be re-locked. This is when the trouble started. I relocked the bootloader via Fastboot. But running the RUU for version 1.29.651.7 fails as I am on 1.31 I believe? I will paste my specs below.
Anyway, it all boils down to a couple of things.
1.) Returning to Stock using an image that is NOT roooted (and also encrypted)?
2.) Returning my Bootloader to stock so that I can run the latest OTA (Is it recommended to run the latest OTA?)
3.) Doing it without bricking my device. Lol!
Now, I have the latest SDK for ADB installed. I have several different Stock images I've downloaded and tried but they all fail. I'm afraid that I am going to have to use one that is 1.31.xxx..
So here is my info from Fastboot, I can provide more detailed information if needed.
C:\adt-bundle-windows-x86_64-20130917\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 1.00.20.0626
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.31.651.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4197mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.194s
Click to expand...
Click to collapse
Again, the goal is stock (unrooted), just like it came out of the box. I will re-root again later but for now I need to fix this SMS issue as it's making it hard to communicate with my colleagues and friends. Again, should I flash the new Sprint OTA update that takes me up to 4.3.3? It does sound tantalizing to see what new features they have incorporated in this update. Here is the name of the OTA:
OTA_M7_WL_JB43_SENSE50_SPCS_MR_Sprint_WWE_3.04.651.2-1.31.651.2_release_335437r9p4z0zrva4gqsfs
Click to expand...
Click to collapse
As usual, any help or insight in to my problem(s) is appreciated. And for the record, the bootloader is again "unlocked". My plan as of right now is to recover using a NANDROID I made about a month ago. This should fix the SMS issue, but I still need to go back to stock so I can start from scratch.
Thanks in advance!
Regards,
Whatever you do do not take the 4.3 OTA!
Get back to 1.29 and root and s-off, there is no RUU for 4.3 so if you get that and mess anything up your screwed unless you have s-off.
Follow this guide to RUU back to 1.29 on 1.31 (you will see an error in doing this just keep going)
http://forum.xda-developers.com/showthread.php?p=44243635
Sent from my HTCONE using xda app-developers app
Here is a helpful link also: http://forum.xda-developers.com/showthread.php?t=2277892
Sent from my HTCONE using Tapatalk
Konfuzion said:
Whatever you do do not take the 4.3 OTA!
Get back to 1.29 and root and s-off, there is no RUU for 4.3 so if you get that and mess anything up your screwed unless you have s-off.
Follow this guide to RUU back to 1.29 on 1.31 (you will see an error in doing this just keep going)
http://forum.xda-developers.com/showthread.php?p=44243635
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
Ok, I'll follow the instructions. Thank you for pointing me in the right direction. It does suck though, 4.3.3 is supposed to bring some new and exciting additions to the Android OS.
Anyway, I'll post if I run in to problems.
Thanks!
tonyrance said:
Here is a helpful link also: http://forum.xda-developers.com/showthread.php?t=2277892
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
Thanks Tonyrance!
PAinguINx said:
Ok, I'll follow the instructions. Thank you for pointing me in the right direction. It does suck though, 4.3.3 is supposed to bring some new and exciting additions to the Android OS.
Anyway, I'll post if I run in to problems.
Thanks!
Click to expand...
Click to collapse
You can update to 4.3 manually after getting s-off
Shoot me a PM if you need help with any of it
Konfuzion said:
Whatever you do do not take the 4.3 OTA!
Get back to 1.29 and root and s-off, there is no RUU for 4.3 so if you get that and mess anything up your screwed unless you have s-off.
Follow this guide to RUU back to 1.29 on 1.31 (you will see an error in doing this just keep going)
http://forum.xda-developers.com/showthread.php?p=44243635
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
Konfuzion,
After I complete this process, do I need to use revone to obtain S-OFF or is there another method?
PAinguINx said:
Konfuzion,
After I complete this process, do I need to use revone to obtain S-OFF or is there another method?
Click to expand...
Click to collapse
Run the 1.29.651.10 RUU then use revone or mooshine to s-off
bigdaddy619 said:
Run the 1.29.651.10 RUU then use revone or mooshine to s-off
Click to expand...
Click to collapse
Ok, that's the RUU I have, well the only one I have that has a "Setup.exe" the others just contain misc files and a .img file..
Could you run through the process for installing revone via ADB please? I've seen several different methods. Just want to make sure everything works out properly.
Ok, following these instructions I still run in to issues with ADB. I was able to open a Shell while the phone was on and booted but when I boot in to recovery and try to start a shell it states "error: device not found".
This is what I'm doing...
Hello, here is a very simple guide to be able to use revone to s-off on the 1.31 update.
Make sure you have dev unlocked and you flashed a custom recovery (CWM or TWRP both work fine)
After that, you need to make sure adb works (if you can't figure out how to do any of this, I will not help you. If you can't find out basic things about Android, then you shouldn't have s-off)
So, as we all know, HTC has made it so with newer bootloaders, you cannot downgrade to older firmwares. Well, this is true except when the software version changes but the hboot version doesn't. So all we need to do is this:
Boot into recovery
adb shell
echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
adb reboot bootloader
fastboot oem lock
then just flash an RUU of 1.29 and it'll work out. All you do is flash the misc partition to contain the proper mainver and it works.
Click to expand...
Click to collapse
What am I doing wrong as to not obtain a shell?
PAinguINx said:
Ok, that's the RUU I have, well the only one I have that has a "Setup.exe" the others just contain misc files and a .img file..
Could you run through the process for installing revone via ADB please? I've seen several different methods. Just want to make sure everything works out properly.
Click to expand...
Click to collapse
Check PM
PAinguINx said:
Konfuzion,
After I complete this process, do I need to use revone to obtain S-OFF or is there another method?
Click to expand...
Click to collapse
This is the easiest way I know of to use Revone
http://forum.xda-developers.com/showthread.php?p=42452138#post42452138
However moonshine might be a better bet since it has the modified hboot which gets rid of the red warning text on boot. I am guessing bigdaddy pointed you in the right direction for the RUU.
bigdaddy619 said:
Check PM
Click to expand...
Click to collapse
I thought I messaged you man. But I didn't get a confirmation. Anyway, I donated $25 to you. Thanks again for your help bro. It has been appreciated!
Related
Hello XDA,
I have noticed a lot of Sprint(CDMA) HTC One users are flashing GSM roms and soft bricking their devices lately.
I have personally rescued 50+ devices in the past couple weeks so I'm posting this guide in hopes that it will save some headaches and stress for Sprint users.
These instructions are for the Sprint variant only
You will need to be unlocked and have TWRP or CWM installed for this to work
1. Follow this guide Guide - Get s-off on 1.31 HTC One (Sprint) Update:
You will get a failed warning after issuing the echo blah blah command this is normal and nothing to be worried about and after the echo command type exit to exit the adb shell and continue.
2. Get the RUU HERE click the first link in the thread(extract it to your desktop/open it and click setup it will scan your device,go thru the various screens reading the warnings and checking the boxes, once it starts it will take 10-20 minutes to complete) once it's done you will be back to completely stock.
Device not recognized?
On your PC go to device manager and find your phone(usually M7WLS), right click and select properties
Select the driver tab
Select update driver
Select browse my comp
Let me pick
Look for ADB USB device or similar should be one of the first couple choices
Select MyHTC install and you should be good
Latest HTC Drivers
Optional:
Use revone to gain s-off (if you go with this option once you are s-off you won't need to use HTC-Dev to unlock your bootloader again because revone does it for you) A sidenote about revone it will fail several times just press the UP arrow on your keyboard to issue the same command and press enter.Watch the cmd window for instructions to reboot and continue.
or flash a Sprint rom from the Sprint forum
Thanks to Indirect for his Guide
Thanks to OMJ for the RUU
Thanks to Revolutionary dev team for Revone
If you need assistance I'll be happy to help.
**NOTE** this guide will be obsolete once Sprint/HTC pushes an OTA and the hboot changes.
Updated 4.3/4.4 Guide found HERE
no adb
bigdaddy619 said:
Hello XDA,
I have noticed a lot of Sprint(CDMA) HTC One users are flashing GSM roms and soft bricking their devices lately.
I have personally rescued 15-30 devices in the past couple weeks so I'm posting this guide in hopes that it will save some headaches and stress for Sprint users.
These instructions are for the Sprint variant only
You will need to be unlocked and have TWRP or CWM installed for this to work
1. Follow this guide Guide - Get s-off on 1.31 HTC One (Sprint) Update:
You will get a failed warning after issuing the echo blah blah command this is normal and nothing to be worried about and after the echo command type exit to exit the adb shell and continue.
2. Get the RUU here click the first link in the thread(extract it to your desktop/open it and click setup it will scan your device,go thru the various screens reading the warnings and checking the boxes, once it starts it will take 10-20 minutes to complete) once it's done you will be back to completely stock.
Optional:
Use revone to gain s-off (if you go with this option once you are s-off you won't need to use HTC-Dev to unlock your bootloader again because revone does it for you) A sidenote about revone it will fail several times just press the UP arrow on your keyboard to issue the same command and press enter.Watch the cmd window for instructions to reboot and continue.
or flash a Sprint rom from the Sprint forum
Thanks to Indirect for his Guide
Thanks to OMJ for the RUU
Thanks to Revolutionary dev team for Revone
If you need assistance I'll be happy to help.
**NOTE** this guide will be obsolete once Sprint/HTC pushes an OTA and the hboot changes.
Click to expand...
Click to collapse
I cant access adb from recovery even with the sideload feature and have no os to boot to this Is what I get for variables
C:\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 1.00.20.0626
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.31.651.2
(bootloader) version-misc: PVT SHIP
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4327mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) gencheckpt: 0
all: Done!
please help and i would rather not get s off i dont need a hard brick
Please remove your serial number and imei and meid
Uninstall everything HTC reboot your PC then reinstall the drivers and follow step 1 then run the RUU then you're done
Sent from my ElipticNexus7
I have been thinking about putting together a guide, but I was lazy. Glad someone finally did. Thanks!
3340 49969225
replying here so other's can find it. I was getting the "remote: 12 signature verify fail" issue when I would try to RUU on sprint HTC one and this was the fix. I honestly think the current stable of cyanogen is to blame. Hopefully this will help others find this thread as it was a life saver.
Uninstall SuperSU/Full Unroot
bigdaddy619 said:
Hello XDA,
I have noticed a lot of Sprint(CDMA) HTC One users are flashing GSM roms and soft bricking their devices lately.
I have personally rescued 15-30 devices in the past couple weeks so I'm posting this guide in hopes that it will save some headaches and stress for Sprint users.
These instructions are for the Sprint variant only
You will need to be unlocked and have TWRP or CWM installed for this to work
1. Follow this guide Guide - Get s-off on 1.31 HTC One (Sprint) Update:
You will get a failed warning after issuing the echo blah blah command this is normal and nothing to be worried about and after the echo command type exit to exit the adb shell and continue.
2. Get the RUU here click the first link in the thread(extract it to your desktop/open it and click setup it will scan your device,go thru the various screens reading the warnings and checking the boxes, once it starts it will take 10-20 minutes to complete) once it's done you will be back to completely stock.
Optional:
Use revone to gain s-off (if you go with this option once you are s-off you won't need to use HTC-Dev to unlock your bootloader again because revone does it for you) A sidenote about revone it will fail several times just press the UP arrow on your keyboard to issue the same command and press enter.Watch the cmd window for instructions to reboot and continue.
or flash a Sprint rom from the Sprint forum
Thanks to Indirect for his Guide
Thanks to OMJ for the RUU
Thanks to Revolutionary dev team for Revone
If you need assistance I'll be happy to help.
**NOTE** this guide will be obsolete once Sprint/HTC pushes an OTA and the hboot changes.
Click to expand...
Click to collapse
I have a brand new Sprint HTC One. Never even registered it with Sprint. I unlocked it to change carriers, Twerp is installed, Still using stock rom 1.29 version, Had SuperSu 1.63 or 1.65 installed. Today I uninstalled SuperSU as the option said "complete clean to unroot". Twerp still will not flash the OTA 1.31 version. When I installed TWERP also did a backup of the original recovery in the device. How do I proceed from here?.
upowersystems said:
I have a brand new Sprint HTC One. Never even registered it with Sprint. I unlocked it to change carriers, Twerp is installed, Still using stock rom 1.29 version, Had SuperSu 1.63 or 1.65 installed. Today I uninstalled SuperSU as the option said "complete clean to unroot". Twerp still will not flash the OTA 1.31 version. When I installed TWERP also did a backup of the original recovery in the device. How do I proceed from here?.
Click to expand...
Click to collapse
You have to re-lock to accept the 1.31 update
relock
bigdaddy619 said:
You have to re-lock to accept the 1.31 update
Click to expand...
Click to collapse
When I attempt to re lock the bootloader and type fastboot oem lock it errors saying faatboot is not a recognized internal or external command operable program or command
thanks
upowersystems said:
When I attempt to re lock the bootloader and type fastboot oem lock it errors saying faatboot is not a recognized internal or external command operable program or command
thanks
Click to expand...
Click to collapse
You are not in the correct folder use android-sdk/platform-tools
fastboot folder
bigdaddy619 said:
You are not in the correct folder use android-sdk/platform-tools
Click to expand...
Click to collapse
Ha you are correct sir! I was right clicking on the wrong folder. Both of the same name! Got to change that! Thanks Locked the bootloader. It rebooted. Thats all I need, can update now? Dont need to mess with Twerp recovery?
Thanks
upowersystems said:
Ha you are correct sir! I was right clicking on the wrong folder. Both of the same name! Got to change that! Thanks Locked the bootloader. It rebooted. Thats all I need, can update now? Dont need to mess with Twerp recovery?
Thanks
Click to expand...
Click to collapse
I have never personally taken an OTA so not really sure of the correct procedure
What if the message in bootloader mode shows relocked . S- on and i recieve an ota 4.3 update and it does restart but in only in fast boot. Recovery option not accessible.
Sent from my HTCONE using xda app-developers app
Not Updating
bigdaddy619 said:
I have never personally taken an OTA so not really sure of the correct procedure
Click to expand...
Click to collapse
It did not work. I tried the OTA it reboots to the Bootloader and has no option to update. The message is "Tampered" "Relocked" "Security Warning"
Is an OTA important. Will I be able to upgrade to 4.3 without this OTA?
---------- Post added at 11:40 AM ---------- Previous post was at 11:16 AM ----------
upowersystems said:
It did not work. I tried the OTA it reboots to the Bootloader and has no option to update. The message is "Tampered" "Relocked" "Security Warning"
Is an OTA important. Will I be able to upgrade to 4.3 without this OTA?
Click to expand...
Click to collapse
MeetBala said:
What if the message in bootloader mode shows relocked . S- on and i recieve an ota 4.3 update and it does restart but in only in fast boot. Recovery option not accessible.
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
Mine also boots directly into fastboot. Recovery option does not open when initiated
Just wanted to say thanks for making this guide.
Soft bricked my One a couple weeks ago and fixed it using this thread.
With s off I can flash any gsm ROM? Without bricking?
Sent from my HTCONE using XDA Premium 4 mobile app
pyrobo0by said:
With s off I can flash any gsm ROM? Without bricking?
Sent from my HTCONE using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Only if it has Sprint support
Am in over my head here, please help!
After installing cyanogenmod onto my htc one EE UK model I tried to return to stock but am unable to find the correct stock files. somehow I have also installed teamwin recovery and cannot use the touchscreen during this mode?
I am able to get back into the bootloader but when I try to start up the phone the cyanogenmod start up screen seems stuck!
Any help to get back to EE UK stock for the htc one or cyanogenmod again would be extremely appreciated.
Thanks for reading my post.
VincSingh said:
Am in over my head here, please help!
After installing cyanogenmod onto my htc one EE UK model I tried to return to stock but am unable to find the correct stock files. somehow I have also installed teamwin recovery and cannot use the touchscreen during this mode?
I am able to get back into the bootloader but when I try to start up the phone the cyanogenmod start up screen seems stuck!
Any help to get back to EE UK stock for the htc one or cyanogenmod again would be extremely appreciated.
Thanks for reading my post.
Click to expand...
Click to collapse
You can use the volume buttons to move and the power button to select on TWRP (assuming it is not the touch version). Then to fix the problem with CM you should just do a wipe and flash the rom again. To return to stock you have to find your carriers RUU and send that through fastboot/adb, after follow Gizmoe's instructions on this thread to get everything back to stock (http://forum.xda-developers.com/showthread.php?)t=2592068
VincSingh said:
Am in over my head here, please help!
After installing cyanogenmod onto my htc one EE UK model I tried to return to stock but am unable to find the correct stock files. somehow I have also installed teamwin recovery and cannot use the touchscreen during this mode?
I am able to get back into the bootloader but when I try to start up the phone the cyanogenmod start up screen seems stuck!
Any help to get back to EE UK stock for the htc one or cyanogenmod again would be extremely appreciated.
Thanks for reading my post.
Click to expand...
Click to collapse
can you post a "fastboot getvar all" (remove IMEI and s/n), you may wanna take a look at my guide if you want to return to stock: http://forum.xda-developers.com/showthread.php?t=2541082
once s-off, going S-ON is NOT recommended.
O-rangePeels said:
You can use the volume buttons to move and the power button to select on TWRP (assuming it is not the touch version). Then to fix the problem with CM you should just do a wipe and flash the rom again. To return to stock you have to find your carriers RUU and send that through fastboot/adb, after follow Gizmoe's instructions on this thread to get everything back to stock (http://forum.xda-developers.com/showthread.php?)t=2592068
Click to expand...
Click to collapse
Thanks O-rangeReels for the advice however for some reason now when I try to go into recovery the htc quietly brilliant screen says entering recovery and does not do anything?
VincSingh said:
Thanks O-rangeReels for the advice however for some reason now when I try to go into recovery the htc quietly brilliant screen says entering recovery and does not do anything?
Click to expand...
Click to collapse
I would be VERY careful using things meant for a Verizon device on a GSM one!
nkk71 said:
can you post a "fastboot getvar all" (remove IMEI and s/n), you may wanna take a look at my guide if you want to return to stock: http://forum.xda-developers.com/showthread.php?t=2541082
once s-off, going S-ON is NOT recommended.
Click to expand...
Click to collapse
Thanks for the advice, I do not know what you are asking me"post a getvar? please explain
VincSingh said:
Thanks for the advice, I do not know what you are asking me"post a getvar? please explain
Click to expand...
Click to collapse
are you (at least somewhat) familiar with "adb" and "fastboot"??
you need to boot your phone to bootloader/FASTBOOT USB, and then on your PC :
fastboot getvar all
nkk71 said:
are you (at least somewhat) familiar with "adb" and "fastboot"??
you need to boot your phone to bootloader/FASTBOOT USB, and then on your PC :
fastboot getvar all
Click to expand...
Click to collapse
fastboot getvar all
(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.61.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3892mV
(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
all: Done!
finished. total time: 0.067s
VincSingh said:
fastboot getvar all
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-main: 2.24.61.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
finished. total time: 0.067s
Click to expand...
Click to collapse
There's no "two-minute" fix, so a couple of more questions, if you don't mind:
1- does it matter to you if bootloader says UNLOCKED?
2- does it matter to you if bootloader says TAMPERED?
3- you want to go back to stock, in order to receive OTA updates?
4- do you intend on selling the phone or returning for warranty? (and so you need the phone to look "out of the box")
nkk71 said:
There's no "two-minute" fix, so a couple of more questions, if you don't mind:
1- does it matter to you if bootloader says UNLOCKED?
2- does it matter to you if bootloader says TAMPERED?
3- you want to go back to stock, in order to receive OTA updates?
4- do you intend on selling the phone or returning for warranty? (and so you need the phone to look "out of the box")
Click to expand...
Click to collapse
1 and 2 - does not matter at this point I would just like to get the phone back to working in any format stock or rooted.
3 - OTA not necessary in view of 1 and 2
4 - don't intend to sell or return the phone
appreciate your help, thanks
VincSingh said:
1 and 2 - does not matter at this point I would just like to get the phone back to working in any format stock or rooted.
3 - OTA not necessary in view of 1 and 2
4 - don't intend to sell or return the phone
appreciate your help, thanks
Click to expand...
Click to collapse
fair enough, here's a quick fix: just download and install this: http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-1-zip/
using CWM: http://forum.xda-developers.com/showthread.php?t=2173863
or TWRP: http://forum.xda-developers.com/showthread.php?t=2173870
the above ROM is for a Europan unbranded version; it's stock, can be rooted or not (selectable in the installer), unselect "stock recovery" in installer as it won't allow OTA's with your current configuration.
I'm gonna check something, and will get back to you when I can, in the meantime the above ROM will get you up and running. (or you can choose any one of the custom ROMs around)
I'll get back to you later
cheers
PS: maybe you could give me a little background info on why you ended up in this situation, eg do you want to be on stock rom (or custom), do you want to be rooted, etc etc. and if not, how come you unlocked your bootloader
If I understand your intentions, I could help better
nkk71 said:
fair enough, here's a quick fix: just download and install this: http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-1-zip/
using CWM: http://forum.xda-developers.com/showthread.php?t=2173863
or TWRP: http://forum.xda-developers.com/showthread.php?t=2173870
the above ROM is for a Europan unbranded version; it's stock, can be rooted or not (selectable in the installer), unselect "stock recovery" in installer as it won't allow OTA's with your current configuration.
I'm gonna check something, and will get back to you when I can, in the meantime the above ROM will get you up and running. (or you can choose any one of the custom ROMs around)
I'll get back to you later
cheers
PS: maybe you could give me a little background info on why you ended up in this situation, eg do you want to be on stock rom (or custom), do you want to be rooted, etc etc. and if not, how come you unlocked your bootloader
If I understand your intentions, I could help better
Click to expand...
Click to collapse
once I have downloaded the ROM how do I install it?
what are the links for CWM and TWRP for, do I need to download anything from them?
As you can tell I dont fully understand the tech side of this much. I thought to root the phone I could get more custom features however after doing this I did not like it and wanted to return to stock but could not find the correct ROM and so the issues began.
VincSingh said:
once I have downloaded the ROM how do I install it?
what are the links for CWM and TWRP for, do I need to download anything from them?
As you can tell I dont fully understand the tech side of this much. I thought to root the phone I could get more custom features however after doing this I did not like it and wanted to return to stock but could not find the correct ROM and so the issues began.
Click to expand...
Click to collapse
@nkk71 full guide for returning to stock is here
http://forum.xda-developers.com/showthread.php?t=2541082
you would do well to read and try and understand all that's going on
clsA said:
@nkk71 full guide for returning to stock is here
http://forum.xda-developers.com/showthread.php?t=2541082
you would do well to read and try and understand all that's going on
Click to expand...
Click to collapse
There are many more downloads required when following the superguide of which I have tried the RUU M7 before and failed at the final stage due to it not being compatible with UK HTC.
the last message from nk77 suggested that all I needed is the Guru reset , which I have downloaded but do not know how to install and cannot see how to do this on the superguide either. Do you know how to install the guru reset?
VincSingh said:
There are many more downloads required when following the superguide of which I have tried the RUU M7 before and failed at the final stage due to it not being compatible with UK HTC.
the last message from nk77 suggested that all I needed is the Guru reset , which I have downloaded but do not know how to install and cannot see how to do this on the superguide either. Do you know how to install the guru reset?
Click to expand...
Click to collapse
1- the guide is made to return to 100% stock; mostly for people going for warranty or want to sell the phone, and put it "out of the box"
2- the Guru Reset i mentioned will only get your phone working (or any other custom ROM), it will not get any OTA updates etc.
3- in order to restore to stock (in your case), you need S-Off
4- if you do have S-Off, you can even turn your phone into an unbranded European version
5- to get the ROM (Guru Reset or any other custom ROM), you can use one of three methods (using custom recovery CWM or TWRP):
i- OTG cable
ii- adb push <name of rom>.zip /data/media/0/
iii- adb sideload <name of rom>.zip
nkk71 said:
1- the guide is made to return to 100% stock; mostly for people going for warranty or want to sell the phone, and put it "out of the box"
2- the Guru Reset i mentioned will only get your phone working (or any other custom ROM), it will not get any OTA updates etc.
3- in order to restore to stock (in your case), you need S-Off
4- if you do have S-Off, you can even turn your phone into an unbranded European version
5- to get the ROM (Guru Reset or any other custom ROM), you can use one of three methods (using custom recovery CWM or TWRP):
i- OTG cable
ii- adb push <name of rom>.zip /data/media/0/
iii- adb sideload <name of rom>.zip
Click to expand...
Click to collapse
I tried S-Off using Rumrunner but could not do it, the error said debugging is on.
sorry this was the exact error message
ERROR: run rumrunner again and READ (no adb connection to device. Debugging on?
Drivers?)
VincSingh said:
sorry this was the exact error message
ERROR: run rumrunner again and READ (no adb connection to device. Debugging on?
Drivers?)
Click to expand...
Click to collapse
have you attempted the Guru reset yet ?
sorry this was the exact error message
ERROR: run rumrunner again and READ (no adb connection to device. Debugging on?
Drivers?)
No. was trying to S-Off but am getting error message which I last posted!
Any suggestions?
If anyone has some time to spare, I could really use some individual guidance.
I just purchased a used HTC One, it had 4.1.2 on it and would not update so I unlocked it and rooted it.
Now though, I keep getting stuck no matter what I try...
I've been trying to get S Off, I have the 1.44 version of hboot I think it's called, and CWS_001 and PN0712000. I can't get S Off to work, even after updating to 4.2.2, now my wifi will not connect. I keep getting stuck in boot loop, or TWRP will not load. I've tripped the 'tamper' flag and would like to get rid of that.
I'm just not familiar enough with all the instructions to purposefully move from where I'm at to where I want to go. I would like to have 4.4 eventually and be unlocked and rooted with a custom ROM with no HTC overlay.
If there is any chance anyone would be willing to walk me through, I would greatly appreciate it. My S3 is working fine so I'm not desperate, but getting there quickly.
Thank you.
I've spent the last 12 hours going around in circles, my Chrome browser looks like 100 tabs are open across the top with all the pages I've been reading trying to figure this thing out. I feel like an idiot about now. Anyways, thanks to anybody for considering helping ahead of time.
bubsnews said:
If anyone has some time to spare, I could really use some individual guidance.
I just purchased a used HTC One, it had 4.1.2 on it and would not update so I unlocked it and rooted it.
Now though, I keep getting stuck no matter what I try...
I've been trying to get S Off, I have the 1.44 version of hboot I think it's called, and CWS_001 and PN0712000. I can't get S Off to work, even after updating to 4.2.2, now my wifi will not connect. I keep getting stuck in boot loop, or TWRP will not load. I've tripped the 'tamper' flag and would like to get rid of that.
I'm just not familiar enough with all the instructions to purposefully move from where I'm at to where I want to go. I would like to have 4.4 eventually and be unlocked and rooted with a custom ROM with no HTC overlay.
If there is any chance anyone would be willing to walk me through, I would greatly appreciate it. My S3 is working fine so I'm not desperate, but getting there quickly.
Thank you.
I've spent the last 12 hours going around in circles, my Chrome browser looks like 100 tabs are open across the top with all the pages I've been reading trying to figure this thing out. I feel like an idiot about now. Anyways, thanks to anybody for considering helping ahead of time.
Click to expand...
Click to collapse
You have an AT&T HTC one
it's very simple to update it to 4.3 >> Download This
all you need is this one file and read the instruction Here
clsA said:
You have an AT&T HTC one
it's very simple to update it to 4.3 >> Download This
all you need is this one file and read the instruction Here
Click to expand...
Click to collapse
Thank you! So, there is no requirement for root, locked/unlocked, previous/installed ROM etc??? Doesn't care what build of my HTC ONE or anything?
Sounds too good to be true.
Will I still be rooted and unlocked afterwards?
Is this a stock ROM?
Downloading now, thanks for the help.
bubsnews said:
Thank you! So, there is no requirement for root, locked/unlocked, previous/installed ROM etc??? Doesn't care what build of my HTC ONE or anything?
Sounds too good to be true.
Will I still be rooted and unlocked afterwards?
Is this a stock ROM?
Downloading now, thanks for the help.
Click to expand...
Click to collapse
It's not a Rom it's a RUU
It's full factory reset it wipes everything and updates the firmware
sent from my recliner
clsA said:
It's not a Rom it's a RUU
It's full factory reset it wipes everything and updates the firmware
sent from my recliner
Click to expand...
Click to collapse
"Sent from my recliner" Well played Sir...
I see by your signature, you are exactly where I want to be. I too have the CSW_001 version. I was up until 2 this morning messing with it so I'm 'off' for the night but will be up bright and early following your suggestion, thank you for that.
Might I still find you in your recliner should I happen to falter? I'm hoping that after this works, I can put my One in the same condition as yours, S Off etc...
Any further pointers on that score? You know exactly the state my One will be in after I get done with your previous advice.
Thanks again, I really appreciate your assistance.
Yeah I'll be here
sent from my recliner
clsA said:
Yeah I'll be here
Click to expand...
Click to collapse
Because ViperOne 5.0 is so new it's going to take a couple of steps for you to get to where I am.
I'm going to use @nkk71 SuperGuide from here http://forum.xda-developers.com/showthread.php?t=2541082.
Lets see If I can get this in the right order
First lets get all the files together before you start
Download
the RUU.exe
TWRP 2.6.3.3 >> http://techerrata.com/browse/twrp2/m7
Guru Bootloader Reset from here: http://www.htc1guru.com/dld/guru_boo...reset_1-0-zip/ (this is the thread http://forum.xda-developers.com/show....php?t=2527194)
Get Both rumrunner and firewater to get S-Off: http://firewater-soff.com/ and http://rumrunner.us/
I Recommend having ARHD 31.6 for Getting s-off >> http://xda7.androidrevolution.nl/db_mirror/ROMs/HTC_One/Android_Revolution_HD-One_31.6.zip
and finally download your ViperOne 5.0 Rom
I'm going to alter the steps somewhat from the above guide because of what you have already done to the phone.
as I understand it your already on 4.2.2 from 4.1.2 is this correct?
here's the steps using the above files
Run the 3.17.502.3 RUU for AT&T (don't bother setting up the phone much your going to loose everything in the next step)
Unlock the bootloader again @ HTCDEV.com
Reboot to bootloader (fastboot USB)- Flash the 2.6.3.3 TWRP Recovery
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
Boot into Recovery and flash ARHD 31.6 (again use minimal setup your not going to be here long)
Get S-off (rumrunner should work fine / or just go with firewater your choice)
next is the Guru reset to remove the Tampered flag ... don't lock the bootloader.
and last step is flash ViperOne 5.0 and Enjoy your new phone
Note: I typed most of this from memory and if I missed any important steps Please feel free to correct me @nkk71 :good:
clsA said:
Note: I typed most of this from memory and if I missed any important steps Please feel free to correct me @nkk71 :good:
Click to expand...
Click to collapse
Sounds good to me :good: :good: :laugh:
(there's also a ruu.zip just in case)
Good luck OP :fingers-crossed:
clsA said:
Because ViperOne 5.0 is so new it's going to take a couple of steps for you to get to where I am.
I'm going to use @nkk71 SuperGuide from here http://forum.xda-developers.com/showthread.php?t=2541082.
Lets see If I can get this in the right order
First lets get all the files together before you start
Download
the RUU.exe
TWRP 2.6.3.3 >> http://techerrata.com/browse/twrp2/m7
Guru Bootloader Reset from here: http://www.htc1guru.com/dld/guru_boo...reset_1-0-zip/ (this is the thread http://forum.xda-developers.com/show....php?t=2527194)
Get Both rumrunner and firewater to get S-Off: http://firewater-soff.com/ and http://rumrunner.us/
I Recommend having ARHD 31.6 for Getting s-off >> http://xda7.androidrevolution.nl/db_mirror/ROMs/HTC_One/Android_Revolution_HD-One_31.6.zip
and finally download your ViperOne 5.0 Rom
I'm going to alter the steps somewhat from the above guide because of what you have already done to the phone.
as I understand it your already on 4.2.2 from 4.1.2 is this correct?
here's the steps using the above files
Run the 3.17.502.3 RUU for AT&T (don't bother setting up the phone much your going to loose everything in the next step)
Unlock the bootloader again @ HTCDEV.com
Reboot to bootloader (fastboot USB)- Flash the 2.6.3.3 TWRP Recovery
Boot into Recovery and flash ARHD 31.6 (again use minimal setup your not going to be here long)
Get S-off (rumrunner should work fine / or just go with firewater your choice)
next is the Guru reset to remove the Tampered flag ... don't lock the bootloader.
and last step is flash ViperOne 5.0 and Enjoy your new phone
Note: I typed most of this from memory and if I missed any important steps Please feel free to correct me @nkk71 :good:
Click to expand...
Click to collapse
Wow, this is great! Just what I need, step by step by step. Like when the golfer hits something up there a couple of inches and the announcer proclaims, "Even I could make that putt." Thank you.
Now, I'm going to give you an opportunity to look your instructions over again while I'm downloading the V1 5.0 ROM (or, another RUU?) (What's the difference btw?) and the ARHD 31.6 file (I'm on lowly 12mb connection so going to take me 40 minutes) before I get started. I already had the other files.
I'm following your instructions blindly so if you've missed something, I'm hosed (I don't want to be hosed, tyvm).
Is that enough?
bubsnews said:
Wow, this is great! Just what I need, step by step by step. Like when the golfer hits something up there a couple of inches and the announcer proclaims, "Even I could make that putt." Thank you.
Now, I'm going to give you an opportunity to look your instructions over again while I'm downloading the V1 5.0 ROM (or, another RUU?) (What's the difference btw?) and the ARHD 31.6 file (I'm on lowly 12mb connection so going to take me 40 minutes) before I get started. I already had the other files.
I'm following your instructions blindly so if you've missed something, I'm hosed (I don't want to be hosed, tyvm).
Here are the particulars, phone state as of right now...
4.2.2
HTC Sense 5.0
CID CWS_001
MID PN0712000
Software MaximusHD 11.0.0
HTK SDK API 5.34
Kernel
3.4.10-g28df0d6
[email protected] #1
SMP PREEMPT
Baseband 4A.17.3250.20_10.441150.04L
Build 2.24.401.8 CL235216 release-keys
Browser WebKit/534.30
Is that enough?
Click to expand...
Click to collapse
Yeah the instruction are fine
run the RUU and get your bootloader unlocked and twrp installed while your downloading ARHD and viperOne
clsA said:
Yeah the instruction are fine
run the RUU and get your bootloader unlocked and twrp installed while your downloading ARHD and viperOne
Click to expand...
Click to collapse
Snag #1, ERROR [155]: UNKNOWN ERROR
Please get the correct TOM Update Utility and try again.
bubsnews said:
Snag #1, ERROR [155]: UNKNOWN ERROR
Please get the correct TOM Update Utility and try again.
Click to expand...
Click to collapse
post your results for fastboot getvar all ( - SerialNo and IEMI )
clsA said:
post your results for fastboot getvar all ( - SerialNo and IEMI )
Click to expand...
Click to collapse
Well, not sure what to do though, the error claims my phone should be in one of two states, either rebooted (no) or black screen with HTC logo and 4 exclamation marks in the corners of the screen (no either). I have the HTC logo but no exclamation points.
The options given by the program are EXIT if phone has rebooted or NEXT to start recovery process.
Not sure which I should choose...
bubsnews said:
Well, not sure what to do though, the error claims my phone should be in one of two states, either rebooted (no) or black screen with HTC logo and 4 exclamation marks in the corners of the screen (no either). I have the HTC logo but no exclamation points.
The options given by the program are EXIT if phone has rebooted or NEXT to start recovery process.
Not sure which I should choose...
Click to expand...
Click to collapse
Error 155 usually means your using the wrong RUU
which means you phone is not CID CWS_001
MID PN0712000. not sure how you got that info
Just exit the update utility
then post your "fastboot getvar all" ( excluding SerialNo and IEMI )
clsA said:
Error 155 usually means your using the wrong RUU
which means you phone is not CID CWS_001
MID PN0712000. not sure how you got that info
Click to expand...
Click to collapse
I can't remember exactly but I did run something and that was returned, I wrote it down.
I use Chrome (I've heard others having problems with Chrome and large file downloads) so I'm downloading that RUU again using IE.
I'm going to hit NEXT to start recovery process.
Will getvar once done, if I can...
I'm positive about the CWS_001 etc...
bubsnews said:
I can't remember exactly but I did run something and that was returned, I wrote it down.
I use Chrome (I've heard others having problems with Chrome and large file downloads) so I'm downloading that RUU again using IE.
I'm going to hit NEXT to start recovery process.
Will getvar once done, if I can...
I'm positive about the CWS_001 etc...
Click to expand...
Click to collapse
Stop !!
if your going to download again we need to change the file
post your getvar so we can continue
bubsnews said:
I can't remember exactly but I did run something and that was returned, I wrote it down.
I use Chrome (I've heard others having problems with Chrome and large file downloads) so I'm downloading that RUU again using IE.
I'm going to hit NEXT to start recovery process.
Will getvar once done, if I can...
I'm positive about the CWS_001 etc...
Click to expand...
Click to collapse
version: 0.5
version-bootloader: 1.44.0000
version-baseband: 4A.17.3250.20
version-cpld: None
version-microp: None
version-main: 1.26.502.15
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: CWS__001
battery-status: good
battery-voltage: 4311mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: RUU
bubsnews said:
version: 0.5
version-bootloader: 1.44.0000
version-baseband: 4A.17.3250.20
version-cpld: None
version-microp: None
version-main: 1.26.502.15
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: CWS__001
battery-status: good
battery-voltage: 4311mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: RUU
Click to expand...
Click to collapse
ok 2 things did you MD5 check the the RUU.exe ?
and did you hard reboot the phone after the RUU failed
it looks like it's still in RUU mode (last line in your getvar)
clsA said:
ok 2 things did you MD5 check the the RUU.exe ?
and did you hard reboot the phone after the RUU failed
it looks like it's still in RUU mode (last line in your getvar)
Click to expand...
Click to collapse
I did not check MD5 (I know I've done that before but not very familiar, instructions?) (I am downloading that file again with IE, almost done).
I did not reboot the phone, only exited the program as instructed and ran getvar.
I've successfully played with custom roms for years, but I managed to completely corrupt my Sprint HTC One M7 and I'm having a hard time figuring out how to get it back to being a working phone.
It's rooted and unlocked. I think a bad download of a recovery or rom corrupted either the storage or firmware or both.
When I first rooted it, I did have some problems. However, I was able to recover and successfully ran the Revolution ROM for about a month. I wanted to try the Viper ROM and that action (not the ROM itself, of course) put the device into its current bricked state.
I can still flash different recoveries. I can install new ROMs. I've even attempted to flash stock recoveries and run a factory reset to completely reset the phone's partitions. However the phone is unusable. I even have a OTG cable to grab ROMS from a USB stick. TWRP doesn't recognize the internal storage of the phone, but it does recognize the USB stick on the OTG cable. ClockWork can see all of the storage on the phone.
I have tried relocking and running RUUs, but I think I am doing it incorrectly because my phone is still S-ON and if that is the case, you have to find the right version of RUU that is an upgrade rather than a downgrade of the phone. The RUUs always error out. Perhaps someone will be able to provide a correct link as I have screen pictures and Model ID info I can include.
Behavior: As I try to show in the pictures I've attached, I can install customer ROMS or alleged stock ROMS onto the phone. When the process completes, I am presented with the stock lock screen for the M7. When I swipe the screen I am presented with a white HTC screen that is similar to the boot screen, but note there is no other writing. This is not the boot screen. Rather, it is all you get.
If you are tethered to a PC, you can see the storage on your list of drives.
However, after about 90 seconds, the phone auto reboots, and you are in a loop.
The phone is 13 months old, so I don't think I can just relock it and walk into a Sprint store and ask for a replacement.
Moreover, I think this is fixable, I just don't know how quite yet.
Thanks for those pros out there who can help me get out of this mess of my own making.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.651.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4242mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.035s
It's not bricked.....
Go Here and follow the instructions exactly===============>http://forum.xda-developers.com/showthread.php?t=2250904
There is no RUU for 4.06.651.9.
This guide will get you fixed up use either the 4.06.651.9 or 5.03.651.3 s-on firmware
http://forum.xda-developers.com/showthread.php?t=2503646
twisteddan said:
It's not bricked.....
Go Here and follow the instructions exactly===============>http://forum.xda-developers.com/showthread.php?t=2250904
Click to expand...
Click to collapse
That RUU won't work it's super old
BD619 said:
That RUU won't work it's super old
Click to expand...
Click to collapse
Oh ok.....Sorry about that.
twisteddan said:
Oh ok.....Sorry about that.
Click to expand...
Click to collapse
No harm no foul
Since he/she is s-on they need to run an RUU equal to or newer then their main version
BD619 said:
No harm no foul
Since he/she is s-on they need to run an RUU equal to or newer then their main version
Click to expand...
Click to collapse
The question is, does such an RUU exist?
If it does not, is there a stock or custom ROM Zip that, while not packaged in an RUU, might work? Although if that were the case, the ROM's I've already tried to use might actually work.
Or, should I attempt to S-Off the phone (something I've never done before) in order to try an RUU to work?
Thanks for your initial answers. Sounds like I don't have enough to move forward quite yet.
BD619 said:
No harm no foul
Since he/she is s-on they need to run an RUU equal to or newer then their main version
Click to expand...
Click to collapse
I googled the version number 4.06.651.9 and came up with this:
http://forum.xda-developers.com/showthread.php?t=2687690
What do you think?
bethesdaadk said:
I googled the version number 4.06.651.9 and came up with this:
http://forum.xda-developers.com/showthread.php?t=2687690
What do you think?
Click to expand...
Click to collapse
This is not an RUU,it's firmware, the the guide I linked to will get you fixed up.
I'm actually surprised you were able to run ARHD for so long without issues, it's most likely the cause of the problems.
Edit: I noticed I did not include the 4.06.651.9 firmware in the rescue guide...it's now added.
BD619 said:
This is not an RUU,it's firmware, the the guide I linked to will get you fixed up.
I'm actually surprised you were able to run ARHD for so long without issues, it's most likely the cause of the problems.
Edit: I noticed I did not include the 4.06.651.9 firmware in the rescue guide...it's now added.
Click to expand...
Click to collapse
I have downloaded two firmwares from your guide. the 4.06.651.9 and the 5.03.651.3
The biggest problem I am currently having is downloading the TWRP recovery without an error. I'm even using download manager on one of my laptops and it sticks at 99%. This is probably how I got into trouble in the first place. I'm attempting 2.7.1.0
Is there a solid version of TWRP earlier that should try and download instead?
bethesdaadk said:
I have downloaded two firmwares from your guide. the 4.06.651.9 and the 5.03.651.3
The biggest problem I am currently having is downloading the TWRP recovery without an error. I'm even using download manager on one of my laptops and it sticks at 99%. This is probably how I got into trouble in the first place. I'm attempting 2.7.1.0
Is there a solid version of TWRP earlier that should try and download instead?
Click to expand...
Click to collapse
I use this one http://forum.xda-developers.com/showthread.php?t=2651035
BD619 said:
I use this one http://forum.xda-developers.com/showthread.php?t=2651035
Click to expand...
Click to collapse
I've tried to parse out your directions to make sure I do this correctly. Can you please check to make sure I'm understanding you correctly?
First step is to flash the firmware:
I've downloaded 4.06.651.9 s-on firmware per your suggestion becuase that's the current version of my phone.
Then I need to rename it to just plain firmware.zip
Then on the phone:
Boot to bootloader and lock the bootloader by typing:
fastboot oem lock
in my ADB/Fastboot dos session.
Then use these commands:
Fastboot oem rebootRUU
Fastboot flash zip firmware.zip
Fastboot reboot-bootloader
which will flash the firmware.
Then: If you get this error after the second command (most likely will)
failed 90 hboot pre-update! please flush image again immediately
press the UP Arrow on your keyboard and press enter to issue the command again. Essentially, you are flashing the firmware a second time.
Then, unlock the bootloader again
fastboot flash unlocktoken Unlock_code.bin
Here's the part where I'm a little uncertain. You state:
8a. If you are using the 4.06.651.4 s-on firmware I would suggest you push this Stock Rooted Odexed Rom to your device or it may not boot.
8b. After flashing the 4.06.651.4 rom you will most likely need to flash the latest radio because the 4.06 firmware does not have a radio included find it HERE
Since I am flashing the 4.06.651.9 s-on firmware and not the 4.06.651.4 s-on firmware, do I need to used that suggested Rom? Or can I use any other standard Rom?
Also, earlier in the guide, you state:
If you are already on 4.06.651.4 or 4.06.651.9 you will have to flash the 3.05.651.6 s-off firmware first...reason being is the 4.06 s-off firmware does not have the latest radio included
Do I need to worry about that since I'm flashing the s-on firmware and not the s-off firmware?
Thanks for your help on this. If I were this careful the first time around, maybe I wouldn't have gotten to this point. Luckily, my old Evo4G is in good condition so I've put it into service while I try and fix the HTC One.
bethesdaadk said:
I have downloaded two firmwares from your guide. the 4.06.651.9 and the 5.03.651.3
The biggest problem I am currently having is downloading the TWRP recovery without an error. I'm even using download manager on one of my laptops and it sticks at 99%. This is probably how I got into trouble in the first place. I'm attempting 2.7.1.0
Is there a solid version of TWRP earlier that should try and download instead?
Click to expand...
Click to collapse
tdhite's 2.7.0.9 worked fine for me?
Since I am flashing the 4.06.651.9 s-on firmware and not the 4.06.651.4 s-on firmware, do I need to used that suggested Rom? Or can I use any other standard Rom?
Click to expand...
Click to collapse
I would use this rom just to get you up and running and you can then make a backup of the stock rom.
If you are already on 4.06.651.4 or 4.06.651.9 you will have to flash the 3.05.651.6 s-off firmware first...reason being is the 4.06 s-off firmware does not have the latest radio included
Click to expand...
Click to collapse
This only applies to folks that are s-off.
BD619 said:
I would use this rom just to get you up and running and you can then make a backup of the stock rom.
This only applies to folks that are s-off.
Click to expand...
Click to collapse
I will try and do this tomorrow and will let you know it goes.
Interestingly enough, I just saw someone with an HTCONE M7 tonight running Sense 6. I was floored at how different and sleek it looked. I hope that once I have a working phone again, I'll be able to get all the way to Sense 6.
But until then, I have to get this one working.
Thanks.
bethesdaadk said:
I will try and do this tomorrow and will let you know it goes.
Interestingly enough, I just saw someone with an HTCONE M7 tonight running Sense 6. I was floored at how different and sleek it looked. I hope that once I have a working phone again, I'll be able to get all the way to Sense 6.
But until then, I have to get this one working.
Thanks.
Click to expand...
Click to collapse
Well the 5.03.651.3 firmware and rom are sense 6
BD619 said:
Well the 5.03.651.3 firmware and rom are sense 6
Click to expand...
Click to collapse
Ok. So I am reporting back. It's a good news / bad news kind of situation.
I relocked the device.
Flashed the 4.06.651.9_firmware
It took two times exactly as predicted and was successful.
I had a little trouble re-unlocking it again, because I needed to resubmit the device of a new unlock.bin. The process changed the token. I suppose that makes sense.
I then flashed TWRP. On a positive note, TWRP allowed me to mount selections that were previously un-mountable.
However, when I put the unit into ADB Sideload mode and then attempted to adb side load from my PC, adb still did not recognize the device. Fastboot does, but adb doesn't.
However, since I had an OTG cable, I merely used that to have TWRP install the stock ROM you suggested.
It finished. I rebooted.
And it's still un-usable. Boots with the nice Sprint screen. One difference, I get an error about htcdialer freezing. I get the stock lock screen. I unlock to a white HTC screen.
The device shows up in device manager as my HTC but I don't see it as a listed drive anymore.
And the device reboots after about 2 minutes.
So, like I said, some success, but it still isn't usable.
Suggestions?
bethesdaadk said:
Ok. So I am reporting back. It's a good news / bad news kind of situation.
I relocked the device.
Flashed the 4.06.651.9_firmware
It took two times exactly as predicted and was successful.
I had a little trouble re-unlocking it again, because I needed to resubmit the device of a new unlock.bin. The process changed the token. I suppose that makes sense.
I then flashed TWRP. On a positive note, TWRP allowed me to mount selections that were previously un-mountable.
However, when I put the unit into ADB Sideload mode and then attempted to adb side load from my PC, adb still did not recognize the device. Fastboot does, but adb doesn't.
However, since I had an OTG cable, I merely used that to have TWRP install the stock ROM you suggested.
It finished. I rebooted.
And it's still un-usable. Boots with the nice Sprint screen. One difference, I get an error about htcdialer freezing. I get the stock lock screen. I unlock to a white HTC screen.
The device shows up in device manager as my HTC but I don't see it as a listed drive anymore.
And the device reboots after about 2 minutes.
So, like I said, some success, but it still isn't usable.
Suggestions?
Click to expand...
Click to collapse
Did you remember to flash the radio?
BD619 said:
Did you remember to flash the radio?
Click to expand...
Click to collapse
I did not flash the radio. I may have been confused, but I thought I didn't need to because I was S-On, not S-Off. At this point, it doesn't matter though, so I'll try it.
Do I need to go through the same steps as flashing the firmware?
Relock.
rebootRUU
Or can I just fastboot flash the radio?
Thanks.
bethesdaadk said:
I did not flash the radio. I may have been confused, but I thought I didn't need to because I was S-On, not S-Off. At this point, it doesn't matter though, so I'll try it.
Do I need to go through the same steps as flashing the firmware?
Relock.
rebootRUU
Or can I just fastboot flash the radio?
Thanks.
Click to expand...
Click to collapse
Nope just flash the radio from recovery
Hi everyone,
I've spent the last 6 hours attempting various fixes from forums and I just can't &^%$ing get this.
Here's what I did.
(1) Phone got stuck in a bootloop.
(2) I did a backup in TWRP version 2.6.
(3) Factory reset.
(4) Everything worked again, no bootloop.
(5) Tried to recover from the backup in TWRP, backup failed.
(6) Phone now stuck on the HTC One screen.. won't load a thing.
I really just want things back to normal, as in stock ROM.
Some info about the phone:
S-ON
TWRP ver 2.6
rooted
can access recovery
don't need anything on the phone
I'm looking for a solution to get this phone going again.. any solution. I'd prefer to be on stock ROM. I'd love some help on this. I'm here.
post your fastboot getvar all please
2dayquestion said:
Hi everyone,
I've spent the last 6 hours attempting various fixes from forums and I just can't &^%$ing get this.
Here's what I did.
(1) Phone got stuck in a bootloop.
(2) I did a backup in TWRP version 2.6.
(3) Factory reset.
(4) Everything worked again, no bootloop.
(5) Tried to recover from the backup in TWRP, backup failed.
(6) Phone now stuck on the HTC One screen.. won't load a thing.
I really just want things back to normal, as in stock ROM.
don't need anything on the phone
Click to expand...
Click to collapse
well if you don't need anything on the phone and you previously did a factory reset and the phone stopped boot-looping, why did you restored that faulty backup? just do a factory reset and you'll be good
alray said:
well if you don't need anything on the phone and you previously did a factory reset and the phone stopped boot-looping, why did you restored that faulty backup? just do a factory reset and you'll be good
Click to expand...
Click to collapse
The backup contained all of the original apps. Thought I could get it rolling again, but no go. Now the phone just won't boot. Stuck on the HTC one screen, even after another factory reset.
2dayquestion said:
The backup contained all of the original apps. Thought I could get it rolling again, but no go. Now the phone just won't boot. Stuck on the HTC one screen, even after another factory reset.
Click to expand...
Click to collapse
post the ouput of fastboot getvar all
Seanie280672 said:
post your fastboot getvar all please
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.00.000.0
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ---------------
(bootloader) imei: ----------------
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3855mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
2dayquestion said:
The backup contained all of the original apps. Thought I could get it rolling again, but no go. Now the phone just won't boot. Stuck on the HTC one screen, even after another factory reset.
Click to expand...
Click to collapse
factory reset again
Install Titanium backup it will restore apps & data from nandroid backup
from HTC One
yatindroid said:
factory reset again
Install Titanium backup it will restore apps & data from nandroid backup
from HTC One
Click to expand...
Click to collapse
The factory reset isn't working. It still hangs. I did the initial backup through TWRP. Will Titanium backup be compatible with that backup?
Now the phone is currently locked, no OS.Should I flash another ROM?
http://www.htc1guru.com/dld/ruu_m7_..._10-38r-1157-04l_release_351317_signed_2-exe/
Looks like your RUU to return to fully stock
You could do with seeing if you can see this number anywhere in the bootloader 4.19.631.9 usually under os- however, radio's match
Seanie280672 said:
http://www.htc1guru.com/dld/ruu_m7_..._10-38r-1157-04l_release_351317_signed_2-exe/
Looks like your RUU to return to fully stock
You could do with seeing if you can see this number anywhere in the bootloader 4.19.631.9 usually under os- however, radio's match
Click to expand...
Click to collapse
The OS is set to 1.000.000. I used some **** utility that reset it. I started clicking things... lol
One thing I'm wondering is since this phone is S-ON, will I be able to even flash a ROM? Could that be the reason that the TWRP restore function isn't working? As far as I know... SON would prevent system files from being written.. correct me if I'm wrong
..downloading that file as I write this
Seanie280672 said:
http://www.htc1guru.com/dld/ruu_m7_..._10-38r-1157-04l_release_351317_signed_2-exe/
Looks like your RUU to return to fully stock
You could do with seeing if you can see this number anywhere in the bootloader 4.19.631.9 usually under os- however, radio's match
Click to expand...
Click to collapse
The phone is the HTC One m7 through Rogers. It was recently asking me for the latest OTA update. The ROM was stock, if that helps.
2dayquestion said:
The phone is the HTC One m7 through Rogers. It was recently asking me for the latest OTA update. The ROM was stock, if that helps.
Click to expand...
Click to collapse
looks like your RUU, like I said, its a Rogers RUU and contains the same radio, your version-main just threw me off a bit, leave your bootloader locked / relocked and plug into your computer in bootloader mode, then run the RUU on your computer, follow the instructions, make sure your battery is 50% or more before running.
regarding your other question, you can flash custom roms whilst s-on, you just have to make sure your bootloader is unlocked, s-on is not there to protect system files, its there to protect you from messing with the HBOOT and radio's etc which will brick the phone if done wrong, you cant brick by flashing rom's.
Seanie280672 said:
looks like your RUU, like I said, its a Rogers RUU and contains the same radio, your version-main just threw me off a bit, leave your bootloader locked / relocked and plug into your computer in bootloader mode, then run the RUU on your computer, follow the instructions, make sure your battery is 50% or more before running.
regarding your other question, you can flash custom roms whilst s-on, you just have to make sure your bootloader is unlocked, s-on is not there to protect system files, its there to protect you from messing with the HBOOT and radio's etc which will brick the phone if done wrong, you cant brick by flashing rom's.
Click to expand...
Click to collapse
Thanks a lot for that link. I found an RUU file about 7 hours ago, but it was in .zip format, not .exe like the link you provided me. This made it damn easy. I relocked the bootloader, installed, now it's all great. Thanks a lot. Can I thumbs up you, or do anything in return?
2dayquestion said:
Thanks a lot for that link. I found an RUU file about 7 hours ago, but it was in .zip format, not .exe like the link you provided me. This made it damn easy. I relocked the bootloader, installed, now it's all great. Thanks a lot. Can I thumbs up you, or do anything in return?
Click to expand...
Click to collapse
Just hit the thanks button a couple of times is plenty.
The Zip would of worked too, you just have to flash it in a special kinda way.
Glad its all working now, could you edit your title in your first post to SOLVED now please.
Seanie280672 said:
Just hit the thanks button a couple of times is plenty.
The Zip would of worked too, you just have to flash it in a special kinda way.
Glad its all working now, could you edit your title in your first post to SOLVED now please.
Click to expand...
Click to collapse
I'm guessing a side-load? I really like the install wizard, the RUU method is pretty ingenious. One quick question for you: It's asking me for a system update, OTA, that's not installing after I download it. I unlocked the bootloader through HTC dev using the binary they e-mail you. Would I have to unroot? Any tips on what I could do?
[edit: for some reason, OTA worked] thanks a lot for your help and especially for that magical link. cheers
2dayquestion said:
I'm guessing a side-load? I really like the install wizard, the RUU method is pretty ingenious. One quick question for you: It's asking me for a system update, OTA, that's not installing after I download it. I unlocked the bootloader through HTC dev using the binary they e-mail you. Would I have to unroot? Any tips on what I could do?
[edit: for some reason, OTA worked] thanks a lot for your help and especially for that magical link. cheers
Click to expand...
Click to collapse
No, you have to put your phone in fastbootRUU mode and then flash the zip from your computer using fastboot commands.
Glad the OTA worked in the end, but in future when installing OTA's just make sure your bootloader is locked / relocked first.
Seanie280672 said:
No, you have to put your phone in fastbootRUU mode and then flash the zip from your computer using fastboot commands.
Glad the OTA worked in the end, but in future when installing OTA's just make sure your bootloader is locked / relocked first.
Click to expand...
Click to collapse
That may have been the issue. Thanks for your time. Another 'thanks' is in order. Cheers