Hello community,
first of all i want to say that i am now trying to fix my problems since the past 10 hours!
So here it is:
I bought a new HTC One M7 on last saturday. After i done the first steps i checked if there were updates available. So it was. I updated it and after it was done i checked if there is another update. But it wasnt.
So i thought this was the latest and newest firmware and i started to use it.
After a few days i wanted to have sweep2wake. I rooted my device and flashed the Bulletproof 14.2 kernel which is close to stock but with sweep2wake.
Btw i flashed the TWRP recovery.
All went perfect on first try.
On saturday i ordered a case for my HTC One M7 from ROCK with the window on top (which came on monday). I read that i need Sense 6 in order to get it work. But i was on Sense 5.5. I wondered at this point because i updated it on saturday to the latest version. So to make sure i checked it again. And yes there was actually a update to sense 6. But now the problem was that i rooted my device and got custom kernel/recovery. This was a problem.
So first i tried to get back to Stock recovery and relock the phone before updating. (Btw i forgot to get the stock kernel back on). But as i relocked the device, it got stuck in bootloader. Always booting in bootloader. After many trys i got it back to unlock and than i tried to install the update (still with custom kernel). It failed!
Than i thought that i just could restore my backup ( backup was made before i rooted my device with adb) but this doesnt help to install the OTA Update.
I also tried to restore my nandroid backup from TWRP but the problem was, after i restored the ADB backup the nandroid update wasnt on my device. But i saved it on my PC. Now the problem was that i couldnt copy any files over to my HTC M7! :crying:
I tried so many things to get it back to work but its still not working. So i cant copy over my nandroid backup or other things.
Adb push doesnt work too.
Next problem is that i cant find original RUU for my device.
Here is what my bootloaderscreen says:
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PUT SHIP S-ON RH
HBOOT-4A.26.3263.18
OpenDSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
Apr 21 2014, 15:48:24. 0
My firmware (looked up in settings) is: 4.20.111.21
CID: T-MOB101 DE
And there is NO RUU for this device on the internet. This made me sad. Btw after the restores the Bulletproof kernel is still on device.
So i hope you can help me get this Sense 6 OTA Update on this Phone and help to get back the ability to copy things from my pc to my phone.
If you need data from me just post the needed ones.
Now the only thing i can do is wait for your helpful answers.
Sincerely YaaOmo
Yaaomo said:
Hello community,
Than i thought that i just could restore my backup ( backup was made before i rooted my device with adb) but this doesnt help to install the OTA Update.
I also tried to restore my nandroid backup from TWRP but the problem was, after i restored the ADB backup the nandroid update wasnt on my device. But i saved it on my PC. Now the problem was that i couldnt copy any files over to my HTC M7! :crying:
I tried so many things to get it back to work but its still not working. So i cant copy over my nandroid backup or other things.
Adb push doesnt work too.
Here is what my bootloaderscreen says:
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PUT SHIP S-ON RH
HBOOT-4A.26.3263.18
OpenDSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
Apr 21 2014, 15:48:24. 0
My firmware (looked up in settings) is: 4.20.111.21
CID: T-MOB101 DE
And there is NO RUU for this device on the internet. This made me sad. Btw after the restores the Bulletproof kernel is still on device.
So i hope you can help me get this Sense 6 OTA Update on this Phone and help to get back the ability to copy things from my pc to my phone.
Click to expand...
Click to collapse
Follow this post on what to do when you don't have an OS. This will help you get your phone working and talking to your computer. When you get this up and running, we can then address updating your phone.
majmoz said:
Follow this post on what to do when you don't have an OS. This will help you get your phone working and talking to your computer. When you get this up and running, we can then address updating your phone.
Click to expand...
Click to collapse
Which ROM? I dont have Stock ROM and i don't know where i can get it.
And btw i tried to adb push (like i said?) in TWRP after 20 mins i canceled it. Do i need to wait longer?
And my system IS running but not on Sense 6. Sorry if i didnt mention it.
Yaaomo said:
Which ROM? I dont have Stock ROM and i don't know where i can get it.
And btw i tried to adb push (like i said?) in TWRP after 20 mins i canceled it. Do i need to wait longer?
And my system IS running but not on Sense 6. Sorry if i didnt mention it.
Click to expand...
Click to collapse
The thought on the ROM was to put your backup that is on your PC onto your phone. You say your system is running but is it communicating with your phone? If it is then you should be able to run both ADB and FASTBOOT commands. If not, then you might need to install new HTC drivers.
@djtrex If you have a nandroid backup of your stock rom 4.20.111.21 could you post it for Yaaomo? Thanks!
majmoz said:
The thought on the ROM was to put your backup that is on your PC onto your phone. You say your system is running but is it communicating with your phone? If it is then you should be able to run both ADB and FASTBOOT commands. If not, then you might need to install new HTC drivers.
@djtrex If you have a nandroid backup of your stock rom 4.20.111.21 could you post it for Yaaomo? Thanks!
Click to expand...
Click to collapse
ATM i CAN use adb and fastboot but i cannot plugg it into my PC and copy paste files (for example mp3 or zip or whatever).
What do you mean with if my system is communicating with my phone?
Yaaomo said:
ATM i CAN use adb and fastboot but i cannot plugg it into my PC and copy paste files (for example mp3 or zip or whatever).
What do you mean with if my system is communicating with my phone?
Click to expand...
Click to collapse
When you plug your phone to the computer, in Device Manager you should see Android USB Devices -> My HTC. If you don't then you need to re-install your HTC drivers. If that doesn't work then you will need an OTG cable so you can hook up an USB drive to your phone to put files on it.
majmoz said:
When you plug your phone to the computer, in Device Manager you should see Android USB Devices -> My HTC. If you don't then you need to re-install your HTC drivers. If that doesn't work then you will need an OTG cable so you can hook up an USB drive to your phone to put files on it.
Click to expand...
Click to collapse
Okay now im confused
Because now, i dont know why, i suddenly can copy things over dunno what happend i did nothing. The device is in device manager. So now i only need to get that OTA Update working.
But i will go sleep now. Hope you can help me tomorrow (today) again. Would appreciate it.
Greets YaaOmo
Yaaomo said:
Okay now im confused
Because now, i dont know why, i suddenly can copy things over dunno what happend i did nothing. The device is in device manager. So now i only need to get that OTA Update working.
But i will go sleep now. Hope you can help me tomorrow (today) again. Would appreciate it.
Greets YaaOmo
Click to expand...
Click to collapse
To take OTA's you need a couple of things
1. Stock ROM
2. Stock Recovery
3. And I believe a locked bootloader.
You cannot have anything custom at all.
If you didn't take an nandroid backup of your stock rom you will have to try and find one on the web, or maybe via GURU1.
Install stock ROM, flash stock recovery through fastboot.. once flashed fastboot erase cache, relock your bootloader then you should be back 100% stock and should b able now to get OTA's.
good luck
scifitrekkie said:
To take OTA's you need a couple of things
1. Stock ROM
2. Stock Recovery
3. And I believe a locked bootloader.
You cannot have anything custom at all.
If you didn't take an nandroid backup of your stock rom you will have to try and find one on the web, or maybe via GURU1.
Install stock ROM, flash stock recovery through fastboot.. once flashed fastboot erase cache, relock your bootloader then you should be back 100% stock and should b able now to get OTA's.
good luck
Click to expand...
Click to collapse
WIth all the conversation above, I think its now simple. Just do this in the order.
1. Copy the nandroid backup you did before rooting on the Phone, in the exact location.
2. Now boot into recovery, and restore the backup. I suppose this will also restore the stock kernel. reboot the device and check in the settings ->about. If not, find the stock kernel in the forums and flash that through recovery.
3. flash the stock recovery. (you'll easily find in the forums).
4. lastly lock the bootloader.
reboot, find for updates and update your phone. It will happen smoothly.
scifitrekkie said:
To take OTA's you need a couple of things
1. Stock ROM
2. Stock Recovery
3. And I believe a locked bootloader.
You cannot have anything custom at all.
If you didn't take an nandroid backup of your stock rom you will have to try and find one on the web, or maybe via GURU1.
Install stock ROM, flash stock recovery through fastboot.. once flashed fastboot erase cache, relock your bootloader then you should be back 100% stock and should b able now to get OTA's.
good luck
Click to expand...
Click to collapse
Hi, first of all thanks for your answer. I know the required things to do OTAs. But again i dont know why, i can see my phone in device manager and i can go on sdcard but i cant copy things over. It says "Copy pprozess canceled".
I tried to restore my nandroid backup with OTG. It was successful but i got the custom Bulletproof kernel. And yesterday i searched (like i said) for Stock ROM/Kernel but it doesnt exist for my device. So thats a problem.
coolshritz said:
WIth all the conversation above, I think its now simple. Just do this in the order.
1. Copy the nandroid backup you did before rooting on the Phone, in the exact location.
2. Now boot into recovery, and restore the backup. I suppose this will also restore the stock kernel. reboot the device and check in the settings ->about. If not, find the stock kernel in the forums and flash that through recovery.
3. flash the stock recovery. (you'll easily find in the forums).
4. lastly lock the bootloader.
reboot, find for updates and update your phone. It will happen smoothly.
Click to expand...
Click to collapse
Thanks for your answer too. But like i wrote above, i now cant copy my backup over. And i just dont know why :S
And again for my device, i couldnt find neither Stock ROM nor Stock Kernel.
Greets Yaaomo
EDIT: I tried to copy over via OTG but the copy porcess is canceled too. Is the sdcard broken? What can i do?
EDIT2: I wiped dat and internal storage. Now i can copy over things again.
EDIT3: I did the nandroid backup but the kernel is still not Stock. And i cant find one on the internet.
Yaaomo said:
Hi, first of all thanks for your answer. I know the required things to do OTAs. But again i dont know why, i can see my phone in device manager and i can go on sdcard but i cant copy things over. It says "Copy pprozess canceled".
I tried to restore my nandroid backup with OTG. It was successful but i got the custom Bulletproof kernel. And yesterday i searched (like i said) for Stock ROM/Kernel but it doesnt exist for my device. So thats a problem.
Thanks for your answer too. But like i wrote above, i now cant copy my backup over. And i just dont know why :S
And again for my device, i couldnt find neither Stock ROM nor Stock Kernel.
Greets Yaaomo
EDIT: I tried to copy over via OTG but the copy porcess is canceled too. Is the sdcard broken? What can i do?
EDIT2: I wiped dat and internal storage. Now i can copy over things again.
EDIT3: I did the nandroid backup but the kernel is still not Stock. And i cant find one on the internet.
Click to expand...
Click to collapse
I think your only solution at this point is to extract the boot.img file from the International (4.19.401.11) firmware. You can find stock firmware packages at this site. I would think your phone will boot up with it since lot of the custom roms use this as their base. If that doesn't work or you don't want to try it, then I would try to get S-OFF. Then you could change your CID & MID (if necessary) to flash the Int'l RUU. Then you will be able to get the latest updates a little quicker.
majmoz said:
I think your only solution at this point is to extract the boot.img file from the International (4.19.401.11) firmware. You can find stock firmware packages at this site. I would think your phone will boot up with it since lot of the custom roms use this as their base. If that doesn't work or you don't want to try it, then I would try to get S-OFF. Then you could change your CID & MID (if necessary) to flash the Int'l RUU. Then you will be able to get the latest updates a little quicker.
Click to expand...
Click to collapse
So now i just download the 2.17.401.1 RUU and install it on my device? And how you get S-OFF? I read about it but dont know how i get it. Can you help me than? Maybe over some massenger because this is a 2 ppl conversation right now.
Greets YaaOmo
EDIT: In the post you linked me to, is said that i need S-OFF in order to get this firmware on my phone. Should i do it first?
EDIT2: Sry i mean 4.19.401.11
Yaaomo said:
So now i just download the 2.17.401.1 RUU and install it on my device? And how you get S-OFF? I read about it but dont know how i get it. Can you help me than? Maybe over some massenger because this is a 2 ppl conversation right now.
Greets YaaOmo
EDIT: In the post you linked me to, is said that i need S-OFF in order to get this firmware on my phone. Should i do it first?
EDIT2: Sry i mean 4.19.401.11
Click to expand...
Click to collapse
You need to get S-OFF first or the RUU will not run. Here is the site for firewater S-OFF, read the instructions and prerequisites very carefully. If you follow @nkk71 Guide for Going Back to Stock on how to flash a different branded RUU. Just stop following the guide after you flash the RUU and start receiving the OTA.
majmoz said:
You need to get S-OFF first or the RUU will not run. Here is the site for firewater S-OFF, read the instructions and prerequisites very carefully. If you follow @nkk71 Guide for Going Back to Stock on how to flash a different branded RUU. Just stop following the guide after you flash the RUU and start receiving the OTA.
Click to expand...
Click to collapse
So now i tried to do S-OFF. But it failed. here is what my cmd says:
Code:
=========================================================================
preparing, one moment
The first bottle is open
chugging..........
********** whelp, this sucks, firewater can not work on your device **********
********** no amount of reflashing, retrying, or ruuing will fix... **********
********** DO NOT COME TO IRC ASKING FOR UPDATES OR ETAS!!!!!! **********
********** if we are able to fix this issue, it will be announced **********
********** bye bye.....sorry it didn't work out. **********
[email protected]:/ #
[email protected]:/ #
What now?
Yaaomo said:
So now i tried to do S-OFF. But it failed.
What now?
Click to expand...
Click to collapse
Give rumrunner a try. Some S-OFF schemes work on some phones and not others. If you can not get S-OFF, then you will have to install a custom rom unless someone can get you a stock nandroid.
Could you post a fastboot getvar all with the imei and serial number blocked or erased? Also, update your recovery to twrp-2.7.1.2 there are changes made to this version which would have eliminated the missing OS.
majmoz said:
Give rumrunner a try. Some S-OFF schemes work on some phones and not others. If you can not get S-OFF, then you will have to install a custom rom unless someone can get you a stock nandroid.
Could you post a fastboot getvar all with the imei and serial number blocked or erased? Also, update your recovery to twrp-2.7.1.2 there are changes made to this version which would have eliminated the missing OS.
Click to expand...
Click to collapse
Okay. With rumrunner i goes to pouring (1)........ and pouring(2)......... but it never stops. So i waited till pouring(8) and than canceled it.
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.26.3263.18
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(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: T-MOB101
(bootloader) battery-status: good
(bootloader) battery-voltage: 4306mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ae8bbb39
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.054s
I flashed the new recovery but there is still no OS.
EDIT: I now got a custom ROM on my phone. ARHD. In some formus they said the combination of Bulletproof 14.2 and ARHD 71.1 can make the phone to S-OFF. Didn't work for me. So my last question is if i can get S-OFF with another tool or is it atm not available for my phone?
look you original cid o T-MOS101 and roms *.**.111.* so you cant intall roms HTC_001 *.**.401.*
try this one Guru Reset M7 2.24.111.3
http://www.htc1guru.com/dld/guru_reset_m7_2-24-111-3-zip/
in aroma instal also stock recovery and radio
good luck
ps also read that http://www.htc1guru.com/downloads/stock-rom-downloads/
Related
So I RMAd my last HTC One Google Play Edition for hardware issues and the new one arrived yesterday. I haven't sent the malfunctioning one back yet, thankfully. I still have a few days before it needs to be in the mail.
Before first boot, I unlocked the bootloader via htcdev. After initial boot, I entered in my google account info, then downloaded all available app and OTA updates (which put me at 4.4.2), etc. By then it was really late so I let it sit overnight with no SIM card in it yet. Today, I flashed CWM and made a nandroid backup, then pushed SuperSU 1.91 to root it. When I finally tried booting into OS again, it started with the boot loop. The desktop shows up for a few seconds then the device reboots. I can get into bootloader and fastboot, but since it's still S-On I have no way to do a proper RUU flash. I can get back into recovery by "fastboot erase cache" followed by "factory reset" from bootloader/hboot screen. The factory reset strangely loads the recovery (or maybe that's what it's supposed to do), but actually choosing recovery from bootloader still tries to boot OS and I'm back in the boot loop. I tried restoring the nandroid backup I made with CWM to no avail. Boot loop persists. I really don't know what else to try here and I'd rather not do the dance with google support again. Any suggestions?
Here's my current fastboot getvar:
$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: (Yes, this is showing as blank.)
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: x
(bootloader) imei: x
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4290mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e82187e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.042s
(The first malfunctioning device is a touch screen issue, not anything like this. That phone is happily unlocked, S-Off and rooted until I prep it to send it back once the new device is functioning properly.)
Any successful suggestion will get lots of thanks and I'm not above tossing a few bucks of donation money out either.
Thanks in advance for any help you gurus can give.
-/djdead
djdead23 said:
So I RMAd my last HTC One Google Play Edition for hardware issues and the new one arrived yesterday. I haven't sent the malfunctioning one back yet, thankfully. I still have a few days before it needs to be in the mail.
Before first boot, I unlocked the bootloader via htcdev. After initial boot, I entered in my google account info, then downloaded all available app and OTA updates (which put me at 4.4.2), etc. By then it was really late so I let it sit overnight with no SIM card in it yet. Today, I flashed CWM and made a nandroid backup, then pushed SuperSU 1.91 to root it. When I finally tried booting into OS again, it started with the boot loop. The desktop shows up for a few seconds then the device reboots. I can get into bootloader and fastboot, but since it's still S-On I have no way to do a proper RUU flash. I can get back into recovery by "fastboot erase cache" followed by "factory reset" from bootloader/hboot screen. The factory reset strangely loads the recovery (or maybe that's what it's supposed to do), but actually choosing recovery from bootloader still tries to boot OS and I'm back in the boot loop. I tried restoring the nandroid backup I made with CWM to no avail. Boot loop persists. I really don't know what else to try here and I'd rather not do the dance with google support again. Any suggestions?
Here's my current fastboot getvar:
[...]
(The first malfunctioning device is a touch screen issue, not anything like this. That phone is happily unlocked, S-Off and rooted until I prep it to send it back once the new device is functioning properly.)
Any successful suggestion will get lots of thanks and I'm not above tossing a few bucks of donation money out either.
Thanks in advance for any help you gurus can give.
-/djdead
Click to expand...
Click to collapse
Yes, your phone is supposed to enter the recovery after factory reset in bootloader if you have a custom recovery like TWRP or CWM.
Maybe you want to make full wipe within the recovery(I wouldn't remember that you did it)... just wipe everything (including sdcard) except system.
If the bootloop still persists, try flashing a custom ROM... for example ARHD;
http://forum.xda-developers.com/showthread.php?t=2356654
Don't use the stock one... use the altered..
And if you managed to boot your phone -> Go instantaneously S OFF
If this doesn't work, or if you don't understand my explanation, just ask...
P.S.
Remember: only if you quote or mention me, I'll be notified and I'll be able to provide further help
First, thanks for your response. =)
LibertyMarine said:
Yes, your phone is supposed to enter the recovery after factory reset in bootloader if you have a custom recovery like TWRP or CWM.
Maybe you want to make full wipe within the recovery(I wouldn't remember that you did it)... just wipe everything (including sdcard) except system.
Click to expand...
Click to collapse
I did try formatting everything via custom recovery before I restored from my nandroid, even sdcard and system. I have also tried just wiping data and sdcard. No luck. I think I used TWRM, but may have been CWM. I've swapped them out a few times trying to get out of my boot loop. It's a brand new phone so there is no data on it that I care about yet. Is there some other way I should try wiping it? I've looked at most of the soft brick guides that have solutions but they all instruct you to get S-Off first, which I obviously can't do if the OS won't boot up for more than a few seconds. Rumrunner is what I used on my old HTC One with success, but haven't been able to try it yet.
LibertyMarine said:
If the bootloop still persists, try flashing a custom ROM... for example ARHD;
http://forum.xda-developers.com/showthread.php?t=2356654
Don't use the stock one... use the altered..
And if you managed to boot your phone -> Go instantaneously S OFF
Click to expand...
Click to collapse
ARHD says specifically that it requires S-Off to install. Are you suggesting I try it anyway without S-Off? =)
I'm currently downloading both the ARHD Google Edition 6.1 and the v51.0 from their blogspot site. Will have to try them after I get to work. I'll check here first when I get to the office, and will post any results I get, otherwise.
Thanks again!
-/djdead
djdead23 said:
First, thanks for your response. =)
I did try formatting everything via custom recovery before I restored from my nandroid, even sdcard and system. I have also tried just wiping data and sdcard. No luck. I think I used TWRM, but may have been CWM. I've swapped them out a few times trying to get out of my boot loop. It's a brand new phone so there is no data on it that I care about yet. Is there some other way I should try wiping it? I've looked at most of the soft brick guides that have solutions but they all instruct you to get S-Off first, which I obviously can't do if the OS won't boot up for more than a few seconds. Rumrunner is what I used on my old HTC One with success, but haven't been able to try it yet.
Click to expand...
Click to collapse
Ah ok.... maybe you have a corrupt data partition.. then this guide might help you:
http://android-revolution-hd.blogspot.ch/2013/10/fix-data-htc-one.html
As far as I know you don't need s off to do that...
This procedure will delete and reformat(not fakeformat - it will recreate the whole partition) your data partition. Just follow the guide carefully..
ARHD says specifically that it requires S-Off to install. Are you suggesting I try it anyway without S-Off? =)
I'm currently downloading both the ARHD Google Edition 6.1 and the v51.0 from their blogspot site. Will have to try them after I get to work. I'll check here first when I get to the office, and will post any results I get, otherwise.
Thanks again!
-/djdead
Click to expand...
Click to collapse
Sorry... didn't think about that. Yeah. then just install one of the previous versions that don't need s off...
but don't try it without s off... you'll get a even more nasty bootloop.. just don't it's a very very bad idea
good luck :good:
djdead23 said:
First, thanks for your response. =)
I did try formatting everything via custom recovery before I restored from my nandroid, even sdcard and system. I have also tried just wiping data and sdcard. No luck. I think I used TWRM, but may have been CWM. I've swapped them out a few times trying to get out of my boot loop. It's a brand new phone so there is no data on it that I care about yet. Is there some other way I should try wiping it? I've looked at most of the soft brick guides that have solutions but they all instruct you to get S-Off first, which I obviously can't do if the OS won't boot up for more than a few seconds. Rumrunner is what I used on my old HTC One with success, but haven't been able to try it yet.
ARHD says specifically that it requires S-Off to install. Are you suggesting I try it anyway without S-Off? =)
I'm currently downloading both the ARHD Google Edition 6.1 and the v51.0 from their blogspot site. Will have to try them after I get to work. I'll check here first when I get to the office, and will post any results I get, otherwise.
Thanks again!
-/djdead
Click to expand...
Click to collapse
You don't need S-OFF for ARHD! Only unlocked bootloader
Uxepro said:
You don't need S-OFF for ARHD! Only unlocked bootloader
Click to expand...
Click to collapse
Ok. I'm going to give 51.0 a shot without S-Off. Will post results in a bit.
LibertyMarine said:
Ah ok.... maybe you have a corrupt data partition.. then this guide might help you:
As far as I know you don't need s off to do that...
This procedure will delete and reformat(not fakeformat - it will recreate the whole partition) your data partition. Just follow the guide carefully..
good luck :good:
Click to expand...
Click to collapse
Ok. I'll try this before trying ARHD. Will post results in a bit...
djdead23 said:
Ok. I'll try this before trying ARHD. Will post results in a bit...
Click to expand...
Click to collapse
ok.. that thing with s off doesn't seem to be an issue anymore.. so just flash the latest version
LibertyMarine said:
ok.. that thing with s off doesn't seem to be an issue anymore.. so just flash the latest version
Click to expand...
Click to collapse
Ok. I flashed ARHD 51.0, and it's been sitting at the initial "START" for a good 30 seconds without rebooting. Gonna walk through the setup process...
*walks through setup process*
Ok. I have a desktop and it isn't boot looping.
MUCH THANKS!
Should it be possible to go back to stock KitKat now?
Ideally, I'd like to nandroid backup my current HTC One, return it to stock, S-On, locked, etc. Mail it back to google, and restore its nandroid backup to the new device.
-/djdead
djdead23 said:
Ok. I flashed ARHD 51.0, and it's been sitting at the initial "START" for a good 30 seconds without rebooting. Gonna walk through the setup process...
*walks through setup process*
Ok. I have a desktop and it isn't boot looping.
MUCH THANKS!
Should it be possible to go back to stock KitKat now?
Ideally, I'd like to nandroid backup my current HTC One, return it to stock, S-On, locked, etc. Mail it back to google, and restore its nandroid backup to the new device.
-/djdead
Click to expand...
Click to collapse
Yeah you can go back to stock KitKat with the following rom:
http://forum.xda-developers.com/showthread.php?t=2341395
It's not 100% stock... but if you'd like to go 100% stock you mist first go s off then flash a GPE RUU:
http://forum.xda-developers.com/showthread.php?t=2358781
After that you can lock (not relock) your bootloader following this guide
http://forum.xda-developers.com/showthread.php?t=2475914
And to go s on is not recommanded!!! Just don't go back s on...! And because you are GPE I don't know how it'd work... if it works differently.. or something similar.. sry..
But remember:
Going back S-ON with an altered bootloader will inevitably and instantaneously hard brick your device
Click to expand...
Click to collapse
Edit:
I don't understand why you want to return it to google
LibertyMarine said:
Yeah you can go back to stock KitKat with the following rom:
http://forum.xda-developers.com/showthread.php?t=2341395
It's not 100% stock... but if you'd like to go 100% stock you mist first go s off then flash a GPE RUU:
http://forum.xda-developers.com/showthread.php?t=2358781
After that you can lock (not relock) your bootloader following this guide
http://forum.xda-developers.com/showthread.php?t=2475914
And to go s on is not recommanded!!! Just don't go back s on...! And because you are GPE I don't know how it'd work... if it works differently.. or something similar.. sry..
Click to expand...
Click to collapse
Yes, I'm doing S-Off first thing before I make any other changes to it. That is my very next step as soon as I have a few minutes to devote to it.
LibertyMarine said:
Edit:
I don't understand why you want to return it to google
Click to expand...
Click to collapse
I have two HTC One devices. The old one has a touch screen issue, and I am in the process of RMAing it. The new device they sent me to replace it is the one I was having the boot loop issue with. The HTC One with the malfunctioning touchscreen is getting sent back to them, probably tomorrow, as soon as I get the replacement one working properly. I really didn't want to have to call google support again to tell them I was having issues with the new device they sent to replace the old one with. =)
Thanks given where possible. Will post status update later after S-Off attempt and hopefully return to stock kitkat.
djdead23 said:
Yes, I'm doing S-Off first thing before I make any other changes to it. That is my very next step as soon as I have a few minutes to devote to it.
Click to expand...
Click to collapse
Ok, good luck...
djdead23 said:
I have two HTC One devices. The old one has a touch screen issue, and I am in the process of RMAing it. The new device they sent me to replace it is the one I was having the boot loop issue with. The HTC One with the malfunctioning touchscreen is getting sent back to them, probably tomorrow, as soon as I get the replacement one working properly. I really didn't want to have to call google support again to tell them I was having issues with the new device they sent to replace the old one with. =)
Thanks given where possible. Will post status update later after S-Off attempt and hopefully return to stock kitkat.
Click to expand...
Click to collapse
yeah.. that would be annoying to call google a second time... ok I think RUU and then locking the bootloader is the best thing you can do... going back s on is just a risk that won't be compensated by the expectet results.. so my recommandation.. let it be and send it back with s off
Edit: Related to the the thanks... you are awesome... most users don't even show a sing of gratitude.. so don't worry mate !
LibertyMarine said:
Ok, good luck...
Click to expand...
Click to collapse
S-off achieved. Thanks LibertyMarine!
I think I'm good from here. =)
-/djdead
djdead23 said:
S-off achieved. Thanks LibertyMarine!
I think I'm good from here. =)
-/djdead
Click to expand...
Click to collapse
awesome! If you have any further questions don't hesitate to ask me !
LibertyMarine said:
awesome! If you have any further questions don't hesitate to ask me !
Click to expand...
Click to collapse
And we're back to 4.4.2 stock GPE rooted with S-Off. Loading all my apps and data from Titanium Backup now....
Thanks again!
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
Hello everybody!
I want to get back to 100% stock ROM (after having used Cyanogenmod previously) - with LOCKED, not RELOCKED.
Current phone: fastboot getvar all yields:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.63.161.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: MYSN
(bootloader) imei: MYIMEI
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4184mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ea0bccbd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I have already restored a Nandroid backup with the original software: that backup was taken from my own phone some months ago right after purchase. I only unlocked the phone for the very first time, flashed the CWMR and directly made the backup with that recovery. Then I pulled the backup to my PC my adb.
So far, I successfully got the phone to S-Off, using RumRunner and removed the TAMPERED flag using the following method with adb as described within this post: http://forum.xda-developers.com/showthread.php?t=2477792
However, now I seem to have run into a deadlock:
a) To gain LOCKED using the following method with adb as described within this post(http://forum.xda-developers.com/showthread.php?t=2475914) I need adb access to the phone.
As long the CWMR is on the phone, the device is listed as “Android ADB Interface” in the category “Android Device” in the Windows Device Manager. Fine, so I can access the phone through adb and can set the bootloader back to LOCKED successfully. But after locking I am not able flash the stock recovery any more.
b) If I flash the stock recovery and boot into it, then
- the stock recovery does not provide adb access. The phone is not listed in the Windows Device Manager.
- booted up into HTC Sense OS, it does not provide adb access, either .The phone is listed as “CD Serial” with a question mark in the category “Other Devices” and “HTC One” with a question mark in the category “Portable Devices”; Also it automatically mounts a drive that includes the HTC Sync Manager, Drivers, etc. [EDIT] Got rid of the question marks by re-assigning the correct MTP and CDC drivers; now I can see the emulated sdcard folder[EDIT OFF],
So, without adb access I cannot use the above method to get LOCKED (and fastboot oem relock lead to RELOCKED, which voids my warranty )-: ).
c) Having the matching stock recovery (3.63.161.6 - Vodafone.img downloaded from the internet somwhere, checksum OK) installed and trying to boot into a temporary CWMR by using fastboot boot myM7_UL_CWMR.img (I tried recovery-clockwork-touch-6.0.4.3-m7ul) does not work, the phone is stuck, if I sent that command. -Is it because, I have HBOOT 1.55, and fastboot boot recovery.img is only supported by HBOOT 1.44?
Question: Do I really have to go through the complete procedure described here, to get LOCKED ? :
http://www.htc1guru.com/guides/return-stock-guide/
That procedure seems to be a pain for me as my CID is VODAP102, and there seems no RUU to be listed for my phone, so I will have to change the CID during the process and execute some extra process steps - or I am just too dumb to identify the correct one for my phone:
http://forum.xda-developers.com/showthread.php?t=2428276
Or is there any alternative quicker way than that HTC Guru Guide?
As said, I have a CWR backup .zip from my original factory installation and I already have already downloaded the matching stock recovery image, so I can flash it on the phone. Does this help?
Regards
Steven
that's one hell of a long post and a lot of questions, well first of all i'll see if I can help you with this, link below is Vodafone backup which I created from my phone, unzip it, you will find a folder called backup, that contains the backup files, and another called recovery, that contains twrp that I used to create the backup, so flash that first.
STAY S_OFF, DO NOT SET BACK TO S_ON.
enter recovery, create a backup in order to create the required folders, then boot your phone back to android, once booted, plug into your computer, copy the backup folder from my zip to your internal SDcard/TWRP/BACKUPS/"device serial number"/
Reboot the phone back into recovery and restore that backup, you will now have Vodafone kitkat 4.4.2 on your phone, however one problem you may have is 4.4.2 comes with HBOOT 1.56 not 1.55, they may pick up on that.
https://drive.google.com/file/d/0B_nEcSZr5peRZnpMSHRPRjlzX2c/edit?usp=sharing
Dear Seanie,
thanks for willing to help!
Will restoring your backup replace the previously flashed TRWP recovery by the stock recovery?
If not, the TRWP recovery remains, and I cannot send the phone in for repair.
If yes, I cannot use adb to set the phone to LOCKED, as the stock recovery does not support adb.
I see no advantage over using the Nandroid backup from my own phone (see opening post).
I am confused - can you clarify, please?
Steven
ManyPhones said:
Dear Seanie,
thanks for willing to help!
Will restoring your backup replace the previously flashed TRWP recovery by the stock recovery?
If not, the TRWP recovery remains, and I cannot send the phone in for repair.
If yes, I cannot use adb to set the phone to LOCKED, as the stock recovery does not support adb.
I see no advantage over using the Nandroid backup from my own phone (see opening post).
I am confused - can you clarify, please?
Steven
Click to expand...
Click to collapse
check my guide, see if that makes sense to you: http://forum.xda-developers.com/showthread.php?t=2541082
reason why the CWM restore method is so long: http://forum.xda-developers.com/showpost.php?p=52430301&postcount=834
I recommend you stay S-Off, but that's a decision only you can make
---------- Post added at 04:03 PM ---------- Previous post was at 03:38 PM ----------
@ManyPhones
if you're going to follow my guide, these are the files you need (in case htc1guru.com is giving slow/corrupt downloads):
ruu.zip: http://www.androidfilehost.com/?fid=23329332407584993
nandroid: http://www.androidfilehost.com/?fid=23501681358543658
preloaded apps: http://www.androidfilehost.com/?fid=23329332407580574
and probably this stock recovery: http://d-h.st/XMA should work without hanging.
Dear nkk71,
thank you! I carefully read through your posting and the linked instructions. - your guide is excellent and foolproof!
I understood I had to use the Nandroid backup method, as there was neither an RUU.exe nor an RUU.zip file available for CID VODAP102.
Thank you for providing the explicit versions/links for my individual phone in the posting!
So the key is indeed downgrading to HBOOT 1.44 in order to be able to load a temporary custom recovery with fastboot boot temp_ recovery_name.img.
I am right after STEP 7. In Step 6 have made the first OTA update, updating from software 1.29.161.7 to software 2.24.161.1. A further update to 3.63.161.6 is offered.I understand, if I want to to S-On, I have to do it NOW, before doing that further update.
I guess, if I want to have full warranty, it is a MUST to set S-On. Right?
Why do you recommend to stay S-Off? - Isn't it possible to go S-On, OTA update to 3.63.161.6, let the phone repair and then later use RumRunner again (after unlocking and rooting again)?
Regards
Steven
P.S.: Someone provided another, shorter method (without downgrade) per PN:
1st download recovery flasher zip (LINK)
Open this zip with 7zip*
Put stock recovery in it simply but renamed recovery.img*
Close zip if it ask save it press yes*
Copy this new zip to phone storage*
Now download guru boot loader reset tool zip from this link & copy to your phone storage
Now reboot to TWRP recovery
*1 st flash recovery flasher zip*
2 nd flash guru boot loader reset tool zip with Locked & remove tempered options ( it tempered is there ) complete flash*
I have not tried it, as I was half through your method. But I can imagine, it maywork - as I do not need to use external adb to access the internal phone memory for the flags, and since I had my own factory-fresh HTC backup re-installed already before.
ManyPhones said:
I am right after STEP 7. In Step 6 have made the first OTA update, updating from software 1.29.161.7 to software 2.24.161.1. A further update to 3.63.161.6 is offered.I understand, if I want to to S-On, I have to do it NOW, before doing that further update.
I guess, if I want to have full warranty, it is a MUST to set S-On. Right?
Click to expand...
Click to collapse
Hi,
There are always different ways of doing things, some shorter, some longer. My guide was written after many many different one-on-one threads, and the conclusion of every possible outcome I have encountered.
(including IRC chats and teamviewer sessions, and even some shortcut methods were used in my thread, but on a one-to-one basis, not as a general rule)
this includes the infamous "tamper detected - rebooting" (mentioned in the guide) that may (or may not) happen when going from S-Off to S-On, this is why I always recommend that IF you intend on going from S-Off to S-On, you should do so on hboot 1.44 or 1.54
As to the question of S-On vs S-Off, it's really country/carrier/repair centre specific... in theory, it shouldn't matter, but in practice, it's dependent on the previous, so that is something you will have to decide.
For example: I've seen threads with people sending in their phone with a custom ROM, tampered, unlocked -> no problem
but i've also seen a post, 100% stock including S-On, but the repair guy said the power button was pressed with "too much force" and refused warranty (oh and it wasn't sent to repair for the power button!!)
cheers
I see, your's is a general approach that will work under any circumstances. I can imagine it is almost impossible to provide tailored solutions for each and every individual starting point of the restore. So, the long way is always the safe way (-:
It must have been a lot of work to assemble the guide and the case example.
Great work! You'll be thanked!
Final words
nkk71 said:
Hi,
this includes the infamous "tamper detected - rebooting" (mentioned in the guide) that may (or may not) happen when going from S-Off to S-On, this is why I always recommend that IF you intend on going from S-Off to S-On, you should do so on hboot 1.44 or 1.54
As to the question of S-On vs S-Off, it's really country/carrier/repair centre specific... in theory, it shouldn't matter, but in practice, it's dependent on the previous, so that is something you will have to decide.
cheers
Click to expand...
Click to collapse
Final words:
I decided to go S-On - as recommended I made it on HBOOT 1.54 (included in the aforementioned OTA update to OS software version 2.24.161.1). No problems, still LOCKED after three reboots.
Then I started the OTA to OS software version 3.63.161.6 (HBOOT 1.55), then another to OS software version 4.X (HBOOT 1.56), then another to OS software version 5.16.161.2 (HBOOT 1.57). If I ever want to go back to S-off, I'll have to use Firewater and hope, that it will work.
ManyPhones said:
Final words:
I decided to go S-Off - as recommended I made it on HBOOT 1.54 (included in the aforementioned OTA update to OS software version 2.24.161.1). No problems, still LOCKED after three reboots.
Then I started the OTA to OS software version 3.63.161.6 (HBOOT 1.55), then another to OS software version 4.X (HBOOT 1.56), then another to OS software version 5.16.161.2 (HBOOT 1.57). If I ever want to go back to S-off, I'll have to use Firewater and hope, that it will work.
Click to expand...
Click to collapse
you mean "go S-On", right?
and yes, for hboot 1.57 firewater is the only method at the moment that may work to get S-Off, hopefully sunshine will be updated to include the M7
(otherwise the only other solution would be using a JavaCard)
nkk71 said:
you mean "go S-On", right?
Click to expand...
Click to collapse
Yeah, that was a typo - I meant S-On (corrected in post #9, sorry for the confusion!
nkk71 said:
Hopefully sunshine will be updated to include the M7
(otherwise the only other solution would be using a JavaCard)
Click to expand...
Click to collapse
Those concepts are still inknown to me. Never mind, I'll check it out later as needed.
Thanks again, nkk71 for the excellent support - and the others, who wrote me PMs!
Hello, as title says, I need help with going back to stock. I bought this phone super cheap (120€) from some german guy. It works like a charm, but my native language is nowhere so I decided to root and use morelocale2. But when I root I can't update. I already relocked bootloader.
Now I need to pick up right (RUU?), but I just can't understand it.
Radio-4T.27.3218.14
HBOOT-1.57.0000
OS-5.11.401.10
I wondered if I can use http://forum.xda-developers.com/showthread.php?t=2753631 , but it's called firmware so i don't know if it's ota or ruu, or i need to use that stock firmware downwards or am I completely wrong?
Thanks for all responses, cheers
There is no RUU available for your phone version If your phone is S Off then you can flash 4.19.401.9 RUU
If not then you have to restore nandroid backup or flash stock Rom reset according to your software version
yatindroid said:
There is no RUU available for your phone version If your phone is S Off then you can flash 4.19.401.9 RUU
If not then you have to restore nandroid backup or flash stock Rom reset according to your software version
Click to expand...
Click to collapse
Thank you for your reply, I don't think I can restore nandroid backup, because I didn't make any and if If my only choice is to flash stock rom, will you please write me noob friendly tutorial? Thank you.
kajman007 said:
Thank you for your reply, I don't think I can restore nandroid backup, because I didn't make any and if If my only choice is to flash stock rom, will you please write me noob friendly tutorial? Thank you.
Click to expand...
Click to collapse
Check out this site, it has both a stock rom and nandroid. Follow the OP it has the instructions.
majmoz said:
Check out this site, it has both a stock rom and nandroid. Follow the OP it has the instructions.
Click to expand...
Click to collapse
I just can't understand it.. it's too much advanced..I need noob friendly tut.. I don't even know what method should I use. I'm sick of android 4.4.2 it's so slow and lagging..not talking about battery. Please Halp
kajman007 said:
I just can't understand it.. it's too much advanced..I need noob friendly tut.. I don't even know what method should I use. I'm sick of android 4.4.2 it's so slow and lagging..not talking about battery. Please Halp
Click to expand...
Click to collapse
unlock bootloader
flash twrp recovery 2.6.3.3
download and save the zip from method 1 in your adb/fastboot folder
with your phone in recovery, push the zip to your /sdcard either by using adb push or adb sideload
install the zip on your phone using twrp recovery
choose yes to wipe/stock recovery/stock radio
reboot phone
download and install ota
enjoy your phone
and btw there is not much difference between 4.4.2 and 4.4.3, only some security fixes and a crappy file manager.
kajman007 said:
I just can't understand it.. it's too much advanced..I need noob friendly tut.. I don't even know what method should I use. I'm sick of android 4.4.2 it's so slow and lagging..not talking about battery. Please Halp
Click to expand...
Click to collapse
Just what do you want to do? I see you relocked your bootloader. Do you still have a custom recovery installed? Post a fastboot getvar all (except imei and serialno).
majmoz said:
Just what do you want to do? I see you relocked your bootloader. Do you still have a custom recovery installed? Post a fastboot getvar all (except imei and serialno).
Click to expand...
Click to collapse
Yes, I have Cwm.
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.27.3218.14
version-cpld: None
version-microp: None
version-main: 5.11.401.10
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__102
battery-status: good
battery-voltage: 3817mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-e47fb74b
hbootpreupdate: 11
gencheckpt: 0
alray said:
unlock bootloader
flash twrp recovery 2.6.3.3
download and save the zip from method 1 in your adb/fastboot folder
with your phone in recovery, push the zip to your /sdcard either by using adb push or adb sideload
install the zip on your phone using twrp recovery
choose yes to wipe/stock recovery/stock radio
reboot phone
download and install ota
enjoy your phone
and btw there is not much difference between 4.4.2 and 4.4.3, only some security fixes and a crappy file manager.
Click to expand...
Click to collapse
I've done it, not sure if it is right, but I still have 4.4.2. Tried to install new update, but my phone was reset and android is still on 4.4.2.. any suggestions? (I didnt watch the installation - I don't want to any more My phone just got like factory reset?)
kajman007 said:
I've done it, not sure if it is right, but I still have 4.4.2. Tried to install new update, but my phone was reset and android is still on 4.4.2.. any suggestions? (I didnt watch the installation - I don't want to any more My phone just got like factory reset?)
Click to expand...
Click to collapse
search for ota and install it
alray said:
search for ota and install it
Click to expand...
Click to collapse
So I can't install updates right from the phone? I have to download OTA from internet and I'll be installing it like installing zip from sd card. Am I right?
kajman007 said:
So I can't install updates right from the phone? I have to download OTA from internet and I'll be installing it like installing zip from sd card. Am I right?
Click to expand...
Click to collapse
settings ---> about ---> software updates
kajman007 said:
So I can't install updates right from the phone? I have to download OTA from internet and I'll be installing it like installing zip from sd card. Am I right?
Click to expand...
Click to collapse
You should be able to download the OTA from the phone. However, you may have some missing files that the OTA will be looking to update. In the post where you got the ROM towards the bottom is a preload file zip. If you need them this is where you can get them to complete the update.
majmoz said:
You should be able to download the OTA from the phone. However, you may have some missing files that the OTA will be looking to update. In the post where you got the ROM towards the bottom is a preload file zip. If you need them this is where you can get them to complete the update.
Click to expand...
Click to collapse
I don't think I'm missing some files. I didn't install the aroma zip with TWRP, I installed them with CWM. Successful. But when I tried to install software update, my phone reset, I didn't watch the installation, but when phone booted, it had setup screen on it. I'm currently downloading a 4.4.3 OTA so we'll see.
EDIT: Downloaded OTA, put in sdcard, trying to boot into recovery, phone automatically boot to ota install, instead of green, it's red and after a while back to android. Im hopeless guys, I think i'll live with 4.2.2 and let someone more experienced and more skilled let this do.
kajman007 said:
I don't think I'm missing some files. I didn't install the aroma zip with TWRP, I installed them with CWM. Successful. But when I tried to install software update, my phone reset, I didn't watch the installation, but when phone booted, it had setup screen on it. I'm currently downloading a 4.4.3 OTA so we'll see.
EDIT: Downloaded OTA, put in sdcard, trying to boot into recovery, phone automatically boot to ota install, instead of green, it's red and after a while back to android. Im hopeless guys, I think i'll live with 4.2.2 and let someone more experienced and more skilled let this do.
Click to expand...
Click to collapse
you can not apply ota manually from stock recovery with s-on. go in settings --> about --> software update
First time you did, your phone performed a factory reset right? This happen sometimes when re-installing stock recovery. just apply the ota again from settings --> about --> software updates.
then if you get a red triangle with an exclamation mark inside, hold vol+ and press power then release both and you should see some text in yellow. post the text if it fail.
alray said:
you can not apply ota manually from stock recovery with s-on. go in settings --> about --> software update
First time you did, your phone performed a factory reset right? This happen sometimes when re-installing stock recovery. just apply the ota again from settings --> about --> software updates.
then if you get a red triangle with an exclamation mark inside, hold vol+ and press power then release both and you should see some text in yellow. post the text if it fail.
Click to expand...
Click to collapse
Tried to update again and SUCCESS! You've got my big thanks