Related
Hi,
I need to get my phone back to stock for warranty before my USB port completely dies (not it works only at certain angles).
I read few threads regarding getting the phone back to stock but I am missing few infos I am asking for your help on this.
The data that I got and believe that is needed:
mainver: 2.32.1010.1
RADIO: 3822.01.08.14_M
HBOOT: 6.13.1002
and I bough phone in Switzerland and have: HTC_GER version (102)
I believe that following the post http://forum.xda-developers.com/showthread.php?t=1359555 is the way to go.
Which RUU do I use due to my mainver ang HTC_GER?
Will vivo_downgrade.img from mentioned thread work for me; basically should the procedure and links on mentioned thread work for my phone?
Thank you very much!
mrepovz said:
Hi,
I need to get my phone back to stock for warranty before my USB port completely dies (not it works only at certain angles).
I read few threads regarding getting the phone back to stock but I am missing few infos I am asking for your help on this.
The data that I got and believe that is needed:
mainver: 2.32.1010.1
RADIO: 3822.01.08.14_M
HBOOT: 6.13.1002
and I bough phone in Switzerland and have: HTC_GER version (102)
I believe that following the post http://forum.xda-developers.com/showthread.php?t=1359555 is the way to go.
Which RUU do I use due to my mainver ang HTC_GER?
Will vivo_downgrade.img from mentioned thread work for me; basically should the procedure and links on mentioned thread work for my phone?
Thank you very much!
Click to expand...
Click to collapse
Yes you have found the correct procedure to follow:
At this link:
http://forum.xda-developers.com/showthread.php?t=1033922
I noticed that they have the 2.32.1010.1 RUU that you should use given the current mainver you have.
Thank you but I do have a question regarding the radio.
Will I have a problem flashing mainver RUU since I upgraded the radio or will everything work ok?
Sent from my HTC Incredible S using XDA App
mrepovz said:
Thank you but I do have a question regarding the radio.
Will I have a problem flashing mainver RUU since I upgraded the radio or will everything work ok?
Sent from my HTC Incredible S using XDA App
Click to expand...
Click to collapse
The RUU should work
I checked on http://www.filefactory.com/f/e45d6fe3dcf51228/ for ROM for mainver: 2.32.1010.1 nad it is KT_KR (honestly I do not know what it stands for) but I figured out that my phone is suppose to have HTC_GER version (102).
How will that work for warranty - which ROM to use?
mrepovz said:
I checked on http://www.filefactory.com/f/e45d6fe3dcf51228/ for ROM for mainver: 2.32.1010.1 nad it is KT_KR (honestly I do not know what it stands for) but I figured out that my phone is suppose to have HTC_GER version (102).
How will that work for warranty - which ROM to use?
Click to expand...
Click to collapse
Then you will need to use the 3.08.405.3 version because the 2.30.405.1 version is lower than the mainver that your phone is reporting. You only option is to use a RUU with a higher version. You should be able to use 3.08.405.3 for your region.
Now I am stuck at splash screen.
What I did is download RUU_VIVO_SENSE30_S_HTC_WWE_3.08.405.3_Radio_20.4802.30.0822U_3822.10.08.28_M_release_227170_signed.exe
got out the rom.zip file, renamed it to PG32...zip and rebooted my phone to update (go back to stock ROM). Later my intentions were to use the vivodowngrade to get back to S-ON.
After the update I am stuck at HTC logo. What to do?
mrepovz said:
Now I am stuck at splash screen.
What I did is download RUU_VIVO_SENSE30_S_HTC_WWE_3.08.405.3_Radio_20.4802.30.0822U_3822.10.08.28_M_release_227170_signed.exe
got out the rom.zip file, renamed it to PG32...zip and rebooted my phone to update (go back to stock ROM). Later my intentions were to use the vivodowngrade to get back to S-ON.
After the update I am stuck at HTC logo. What to do?
Click to expand...
Click to collapse
Just follow this guide.
I managed to somehow get it to the next state:
I installed a rom.zip form (RUU_Vivo_Gingerbread_S_KT_KR_2.32.1010.1_Radio_20.2810.30.085AU_3805.06.03.16_M_release_199684_signe.exe) since it has the same maiver as I had it by renaming it to PG32IMG.zip and placing it to the SD.
After "flashing" it wrote me that it is a wrong version. The result:
If I turn it off it turns on again by it self (I can't turn it off unless i bull the battery) and it displays (no ROM is started):
**** Security Warning****
VIVO PVT SHIP S-ON RL
HBOOT-1.13.0000
RADIO-3805.06.03.16_M
eMMC-boot
...
...
...
It looks like it is S-ON - is this correct? (I might have done something wright )
Can I now try to install a RUU (RUU_VIVO_SENSE30_S_HTC_WWE_3.08.405.3_Radio_20.4802.30.0822U_3822.10.08.28_M_release_227170_signed.exe) ? or do I have to get rom.zip and the procedure on http://forum.xda-developers.com/showthread.php?t=1359555 ?
Thank you!
I tried to install via RUU and it worked
Thanks everyone for help
While flashing a new rom, something happened and now I'm stuck in bootloop. I can access hboot/fastboot and the computer does recognize the phone when hooked up via usb. I've tried running an RUU, but I got an error message stating I was installing the wrong one. I can't seem to find any RUU's that will download completely. Can anyone please help me save this phone? My wife is going to kill me if I can't get it working. I'm not that familiar with running cmd prompts, so if you could walk me through it, or send me to a youtube video, I would be greatly appreciated.
I was running TWRP 2.6.0, and the issue occured when I tried flashing to 2.6.3 and then tried installing 4.4 kit kat. The more I messed with it, the worse it got. I had backed up the phone and used it several times to reflash it to the back up, but finally, it gave out too. Now I have no recovery and no clue where to begin. I just want this thing back to stock. Here is what I've working with:
M7_WLS PVT SHIP S-ON RH
HBOOT - 1.56.0000
OpenDSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
Jan 23 2014,22:11:35.0
redsoxfanatic76 said:
While flashing a new rom, something happened and now I'm stuck in bootloop. I can access hboot/fastboot and the computer does recognize the phone when hooked up via usb. I've tried running an RUU, but I got an error message stating I was installing the wrong one. I can't seem to find any RUU's that will download completely. Can anyone please help me save this phone? My wife is going to kill me if I can't get it working. I'm not that familiar with running cmd prompts, so if you could walk me through it, or send me to a youtube video, I would be greatly appreciated.
I was running TWRP 2.6.0, and the issue occured when I tried flashing to 2.6.3 and then tried installing 4.4 kit kat. The more I messed with it, the worse it got. I had backed up the phone and used it several times to reflash it to the back up, but finally, it gave out too. Now I have no recovery and no clue where to begin. I just want this thing back to stock. Here is what I've working with:
M7_WLS PVT SHIP S-ON RH
HBOOT - 1.56.0000
OpenDSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
Jan 23 2014,22:11:35.0
Click to expand...
Click to collapse
I've tried running the update utility to install the new rom, but it doesn't work. Everything appears to load fine...it says erasing, and then sending...and I get the message that it will take 10 minutes. After about 6 minutes or so, I get an error (155) Unknown Error. "The rom update utility cannot update your Android phone. Please get the correct ROM update utility and try again.
What rom update do I need??
redsoxfanatic76 said:
I've tried running the update utility to install the new rom, but it doesn't work. Everything appears to load fine...it says erasing, and then sending...and I get the message that it will take 10 minutes. After about 6 minutes or so, I get an error (155) Unknown Error. "The rom update utility cannot update your Android phone. Please get the correct ROM update utility and try again.
What rom update do I need??
Click to expand...
Click to collapse
The RUU I tried was...Sprint_HTC_One_m7wls_3_04_651_2_RUU
Now downloading Guru_Reset_M7_Sprint_1.29
Tried every RUU I can find....all get the same error. I'm hoping that because it's even being recognized and starts installing that's a good thing right?
I think it's because there is no OS installed, so there is nothing to upgrade the rom from. Does anyone have any suggestions? I really don't want to send this back to HTC, as I know the warranty will be voided...I've got tampered and unlocked at the top.
Even if I do have to send it in for repair...anyone know how much it might cost? Would it be cheaper to file with insurance? I've got twin babies...and they are always getting into stuff "ahem". Honestly though, I can't even afford the insurance cost to replace it. Any help would be greatly appreciated.
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
So I feel like I've pretty much shat on my myself here so now I'm finally coming for specific help.
Brand New Sprint HTC one m7 from the store after a purple camera replacement.
I unlock the bootloader, flash recovery. Still S-ON Somewhere along the way I can't get signal after I install the new ROM ( I assume from the wipe)
Try to manually input APN after I had to install an apk because APN wasn't a choice. Doesn't save.
Try installing a different rom. Either I can get into the rom and no signal or it will install and reboot after 5 min into the OS.
Restore from twrp recovery I moved to my PC before I did anything. Still nothing. possible cycling reboot.
Now here's the tricky part. (for me anyway)
So going into fasboot and inputting "getvar all" it returns with a version-main: none and version-baseband: N/A. Now trying to RUU the situation. With the windows program it gives me an error and when I "fastboot flash zip firmware.zip" it continually fails.
it says my CID is SPCS_001
RUUs i've tried:
1.29.651.10
1.29.651.7
4.06.651.4
I'm not exactly sure which one I'm meant to be using from this point because they all fail. I've them both locked and unlocked. And yes Inputted the flash command multiple times for each file.
what software version is currently installed in the phone? Post full pnone info
you must RUU the same version to get back to stock and eturn baseband if you are s-on.
I have had same situation. I was on 5.03.651.3. And i can only flash 5.03.651.30or newer (5.05.651.2), BUT NOT OLDER.
relock bootloader, enter fastboot usb, run AruWizard and wait. it may look loke process hangs while flashing, but just wait and be quiet. it can take 10-20 minutes
nick_fc said:
what software version is currently installed in the phone? Post full pnone info
you must RUU the same version to get back to stock and eturn baseband if you are s-on.
I have had same situation. I was on 5.03.651.3. And i can only flash 5.03.651.30or newer (5.05.651.2), BUT NOT OLDER.
relock bootloader, enter fastboot usb, run AruWizard and wait. it may look loke process hangs while flashing, but just wait and be quiet. it can take 10-20 minutes
Click to expand...
Click to collapse
So here's my problem now. The newest firmware I can find 5.05.651.2 the exe file from the HTC site loads the install wizard and nothing happens or the zip file from http://forum.xda-developers.com/showthread.php?t=2795856 the ARUwizard file gives me the side by side error. for some reason even after repairing c++ redistributable it still pops up the error. flashing the firmware portion also from the above thread fails locked and unlocked.
Synesthesis said:
So here's my problem now. The newest firmware I can find 5.05.651.2 the exe file from the HTC site loads the install wizard and nothing happens or the zip file from http://forum.xda-developers.com/showthread.php?t=2795856 the ARUwizard file gives me the side by side error. for some reason even after repairing c++ redistributable it still pops up the error. flashing the firmware portion also from the above thread fails locked and unlocked.
Click to expand...
Click to collapse
nobody can help you if you will not post full detailed phone info and detailed error description
Synesthesis said:
So here's my problem now. The newest firmware I can find 5.05.651.2 the exe file from the HTC site loads the install wizard and nothing happens or the zip file from http://forum.xda-developers.com/showthread.php?t=2795856 the ARUwizard file gives me the side by side error. for some reason even after repairing c++ redistributable it still pops up the error. flashing the firmware portion also from the above thread fails locked and unlocked.
Click to expand...
Click to collapse
We still have no idea what version your phone is ... if it just come back from servicing i would guess the updated it for you
What PC are you running the RUU from (OS / age of PC) ? what is the error you get when flashing just the firmware ?
Synesthesis said:
So I feel like I've pretty much shat on my myself here so now I'm finally coming for specific help.
Brand New Sprint HTC one m7 from the store after a purple camera replacement.
I unlock the bootloader, flash recovery. Still S-ON Somewhere along the way I can't get signal after I install the new ROM ( I assume from the wipe)
Try to manually input APN after I had to install an apk because APN wasn't a choice. Doesn't save.
Try installing a different rom. Either I can get into the rom and no signal or it will install and reboot after 5 min into the OS.
Restore from twrp recovery I moved to my PC before I did anything. Still nothing. possible cycling reboot.
Now here's the tricky part. (for me anyway)
So going into fasboot and inputting "getvar all" it returns with a version-main: none and version-baseband: N/A. Now trying to RUU the situation. With the windows program it gives me an error and when I "fastboot flash zip firmware.zip" it continually fails.
it says my CID is SPCS_001
RUUs i've tried:
1.29.651.10
1.29.651.7
4.06.651.4
I'm not exactly sure which one I'm meant to be using from this point because they all fail. I've them both locked and unlocked. And yes Inputted the flash command multiple times for each file.
Click to expand...
Click to collapse
post your getvar all here, remove your imei and serial number before posting.
No one can help you until we know exactly what firmware you already have on the device? And what Operating system you have on your pc? What recovery your using? and what Rom you tried to flash?
The side by side error can be addressed by installing a different or updated version of Microsoft c++ and your version main is missing because you used a version of TWRP recovery with the misc partition bug. But that's all I can tell you based on what you've shared already.
Danny201281 said:
post your getvar all here, remove your imei and serial number before posting.
No one can help you until we know exactly what firmware you already have on the device? And what Operating system you have on your pc? What recovery your using? and what Rom you tried to flash?
The side by side error can be addressed by installing a different or updated version of Microsoft c++ and your version main is missing because you used a version of TWRP recovery with the misc partition bug. But that's all I can tell you based on what you've shared already.
Click to expand...
Click to collapse
Ok to answer all the burning questions:
On the computer front I'm using a macbook pro with windows 7 Ultimate installed under bootcamp.
The phone is brand new. If it was serviced I'm not aware of it.
Recovery I'm currently using is TWRP 2.8.1.0. I was using 2.7 because I read a feint whisper in some other rom thread that the apn issue might be resolved that way. However since I was having intermittent OS cycling on reinstall to not have a mtp function during mount was frightening.
The first rom I tried to flash was ARHD 83.1 in an attempt to possibly s-off my device with firewater. Never got passed the rom flashing.
and for the big reveal:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4181mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e1af350
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Synesthesis said:
Ok to answer all the burning questions:
On the computer front I'm using a macbook pro with windows 7 Ultimate installed under bootcamp.
Click to expand...
Click to collapse
meh! I've no experiance with Mac, I don't know for sure but running Windows I assume as a VM could cause problems using the ruu.
The phone is brand new. If it was serviced I'm not aware of it.
Recovery I'm currently using is TWRP 2.8.1.0. I was using 2.7 because I read a feint whisper in some other rom thread that the apn issue might be resolved that way. However since I was having intermittent OS cycling on reinstall to not have a mtp function during mount was frightening.
Click to expand...
Click to collapse
Are you sure you flashed the Sprint compatible TWRP recovery. You can download them here http://techerrata.com/browse/twrp2/m7wls
The first rom I tried to flash was ARHD 83.1 in an attempt to possibly s-off my device with firewater. Never got passed the rom flashing
Click to expand...
Click to collapse
And here is what I believe is the root of your problem (hehe pun intended ) This Rom is definitely not Sprint compatible. Flashing this Rom would have messed up your partitions. It's for International Brand HTC one.
If your sure your recovery is the Sprint version. You probably just need to Format the device. With "Format Data" in TWRP then flash Sprint compatible Rom. Or if you think you need to, flash a TWRP from the above link.
Based on the fact your on Hboot 1.57 the latest Sprint RUU should work for you. But because your s-on you will need to relock your bootloader in order to flash it. Assuming you can get round the side by side error. But I think a proper Windows pc is whats required there. :good:
The Sprint Section of the forums here http://forum.xda-developers.com/sprint-htc-one is where you'll find roms for your phone. In Android Development and Original Android Development
Danny201281 said:
meh! I've no experiance with Mac, I don't know for sure but running Windows I assume as a VM could cause problems using the ruu.
Click to expand...
Click to collapse
bootcamp is a separate install. not a virtual machine
And here is what I believe is the root of your problem (hehe pun intended ) This Rom is definitely not Sprint compatible. Flashing this Rom would have messed up your partitions. It's for International Brand HTC one.
Click to expand...
Click to collapse
Yeah I realized that later but I even tried installing the Nocturnal Lollipop rom, the badboyz sense 6 rom which was what was on my last HTC one, viper, etc. with no good.
If your sure your recovery is the Sprint version. You probably just need to Format the device. With "Format Data" in TWRP then flash Sprint compatible Rom. Or if you think you need to, flash a TWRP from the above link.
Click to expand...
Click to collapse
going to try this part now. OK reformatted. so flashing 5.03.651.3 and 5.05.651.2 firmware full and modified gives me this:
sending 'zip' (25541 KB)...
OKAY [ 1.952s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 5.176s
I am locked again and in rebootRUU
Synesthesis said:
bootcamp is a separate install. not a virtual machine
Yeah I realized that later but I even tried installing the Nocturnal Lollipop rom, the badboyz sense 6 rom which was what was on my last HTC one, viper, etc. with no good.
going to try this part now. OK reformatted. so flashing 5.03.651.3 and 5.05.651.2 firmware full and modified gives me this:
sending 'zip' (25541 KB)...
OKAY [ 1.952s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 5.176s
I am locked again and in rebootRUU
Click to expand...
Click to collapse
Just flash a Sprint Rom with TWRP. The format will have sorted your partitions out. It should except a Sprint compatible Rom now.
Danny201281 said:
Just flash a Sprint Rom with TWRP. The format will have sorted your partitions out. It should except a Sprint compatible Rom now.
Click to expand...
Click to collapse
OK so I finally got to another computer last night. (which is a hassle since I travel all the time) and ran the ARUwizard that didn't work on my computer. THANK THANK THANK YOU YOU YOU.
And we're up and running with 5.03.651.3
So Now I'm back to square one. After the RUU it did removed the tampered flag which I thought was cool. But now I want to tamper again. :laugh:
So from this point any sprint based rom should be ok right? I feel like all this wasn't as hard when I was romstalling a year ago with my original phone or with the EVO.
Also what's this about the twrp partition error? What version of the recovery should I be using? I had been using CWM on the old phone because CM11 stopped installing correctly after a certain version of TWRP.
Synesthesis said:
OK so I finally got to another computer last night. (which is a hassle since I travel all the time) and ran the ARUwizard that didn't work on my computer. THANK THANK THANK YOU YOU YOU.
And we're up and running with 5.03.651.3
So Now I'm back to square one. After the RUU it did removed the tampered flag which I thought was cool. But now I want to tamper again. [emoji23]
So from this point any sprint based rom should be ok right? I feel like all this wasn't as hard when I was romstalling a year ago with my original phone or with the EVO.
Also what's this about the twrp partition error? What version of the recovery should I be using? I had been using CWM on the old phone because CM11 stopped installing correctly after a certain version of TWRP.
Click to expand...
Click to collapse
Ok cool, nice to hear your back up
You should be fine to flash any Sprint Compatible Rom also recovery must be Sprint Compatible. The reason is that Sprint HTC one's have a different partition layout the the International variants, so anything you flash must be specifically for your Sprint phone. Basically anything you find in the Sprint forums I linked previously should be fine :good:
The TWRP problem is that some version (unfortunately I don't know exactly which Sprint version) have a bug that inadvertently wipes the OS version information from the misc partitions. This is only a cosmetic bug and shouldn't cause any problems with your device but if your a little ocd like myself you'll preffer to avoid it. It can be rectified by flashing firmware.
For the International HTC One this happens with 2.7.x.x versions of TWRP with 2.7.1.1 being the worst offender. Best advice I can give is check in the Sprint forums use the search box to search for "blank os" or "blank version main" that should turn up something or ask your fellow Sprint users in the Sprint Q&A forums, they should be able to give you more direct advice on what versions to avoid
So my current setup is this:
Tampered
Relocked
SecurityWarning
M7_MLS PVT SHIP S-ON RH
HBOOT 1.57.0000
Radio 1.01.20.0904_2
Open DSPv32.120.274.0909
OS-3.04.651.2o (the little o at the end of this line is highlighted)
eMMC-boot 2048MB
I'm just trying to get this phone back in working condition so I can give it to my daughter. But nothing I do is working. Currently phone boots into some old version, not sure what. But I can't do over the air updates because it just reboots into the bootloader and won't finish.
I've refreshed back to stock from the bootloader, and started down the path found in this thread:
http://forum.xda-developers.com/showthread.php?t=2618524
to get S-OFF (NOTE: I'm on hboot 1.57 and it's for 1.55, but I have no idea how to get back to 1.55)
I got through the first step (tricking it into thinking it's on version 3.04.651.2) and now when I do an adb devices, it isn't seeing my phone anymore. Also, I seem to have lost recovery? I had TRWP on there and now if I try to select 'recovery' it just returns to the bootloader screen and won't go into recovery any more.
Help. It literally just want to wipe the thing and put something useable on it. Stock, rooted or not, whatever. If I try to update the software on the phone from within the phone settings, it reboots into the bootloader and gets stuck.
Thanks in advance!
Probably the easiest thing to do then is to flash the full firmware first. Then run the RUU. You probably can get by with just the RUU, but it sometimes errors out if the firmware is not flashed first. You can get the firmware and the RUU (along with basic instructions on how to use them) from here: http://forum.xda-developers.com/showthread.php?t=2795856
coal686 said:
Probably the easiest thing to do then is to flash the full firmware first. Then run the RUU. You probably can get by with just the RUU, but it sometimes errors out if the firmware is not flashed first. You can get the firmware and the RUU (along with basic instructions on how to use them) from here: http://forum.xda-developers.com/showthread.php?t=2795856
Click to expand...
Click to collapse
That worked! Thank you so much!!