Database Develop

Phone randomly reboots after 20-30 seconds. Help?

Decided to rewrite this as the problem is different now, not as bad, but a lot weirder! I can't get my head round whats up
Description of Problem
Right, so simplistically, the phone boots up, and you can use it (sort of) for about 30 seconds, before it reboots. Whilst its on, you can open apps, but there is definite issues with menu's not opening and you cant set a wallpaper, but its almost fully working. Then without any warning it just reboots, and does the same thing again.
I'm just confused at how it can boot up and almost fully work before rebooting. Failing to boot at all or bootlooping at the start animation, I can understand that, but not this.
Video of the Problem
What Caused the Issue
Its been a week or so since it first died, so I cant fully remember exact things that happened (I appreciate this will not be helpful!)
I had converted the phone to a google edition version using the tutorial here: http://forum.xda-developers.com/showthread.php?t=2358781
Changed the MID and CID, flashed the bootloader, recovery and RUU and the whole thing worked great.
Then I got my Xperia Z, so wanted it back to stock to be sold. Problem is I locked the bootloader and went S-ON before flashing the stock bootloader because i'm an idiot! Then obviously it wouldn't boot due to locked bootloader and custom recovery, so I tried to flash stock RUU, failed naturally due to upgraded bootloader, so I unlocked the bootloader again, flashed stock, and now this happens
Things I've Tried
Factory Reset
Flashed Stock Roms (1.28 / 2.17 / 2.24 and google edition) via both flashable zip and CWM backups - flashing in fastboot doesnt work because of signature error
Revone to re S-OFF (On HBOOT 1.54 so get a -6 error)
Maybe some other things?
Does anyone have any ideas? Any help is appreciated at the moment, don't want to wait for S-OFF on 1.54 or a 2.24 RUU as that could mean a brick on my shelf for a while.

Can't you use revone to unlock? Or did you do s-on as well?
Edit: didn't mean to thank you there - this app is killing me..
Have you tried downgrading your firmware to give you the old 1.44 bootloader?
Sent from my HTC One using xda premium

redbull123 said:
Can't you use revone to unlock? Or did you do s-on as well?
Edit: didn't mean to thank you there - this app is killing me..
Have you tried downgrading your firmware to give you the old 1.44 bootloader?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
After hours of playing round I managed to get it to unlock the bootloader, so I should be fine, no idea what changed to make it work, but now it does. Out of interest for the future, how can you downgrade via fastboot with locked bootloader and S-ON?

dh2311 said:
Out of interest for the future, how can you downgrade via fastboot with locked bootloader and S-ON?
Click to expand...
Click to collapse
You can't downgrade when you're s-on.

iElvis said:
You can't downgrade when you're s-on.
Click to expand...
Click to collapse
Thats what I thought, hence why I got a bit concerned earlier. Phones not fixed yet, stuck in a bootloop but my internet is slow for downloading firmwares

If you're unlocked, you should be able to flash a new recovery, and from there a new rom. You've probably mucked up something with the OS, so hopefully a wipe and flash should do the trick.

dh2311 said:
After hours of playing round I managed to get it to unlock the bootloader, so I should be fine, no idea what changed to make it work, but now it does. Out of interest for the future, how can you downgrade via fastboot with locked bootloader and S-ON?
Click to expand...
Click to collapse
You can't - I thought you were s-off since I didn't read in your post that you went back to s-on, that's what I was asking..
Sent from my HTC One using xda premium

iElvis said:
If you're unlocked, you should be able to flash a new recovery, and from there a new rom. You've probably mucked up something with the OS, so hopefully a wipe and flash should do the trick.
Click to expand...
Click to collapse
The partition tables are ******, dont know why, sd card partition is unreadable and an ADB sideload still causes bootloops, this phone is really messed up and i dont know what i did
Usually I can figure the problem out. No idea now. Going to try and get the SD card back and restore an RUU from a CWM backup, then RUU it and should be fixed!
Luckily I have my trusty Xperia Z to use whilst I sort this out!

dh2311 said:
The partition tables are ******, dont know why, sd card partition is unreadable and an ADB sideload still causes bootloops, this phone is really messed up and i dont know what i did
Usually I can figure the problem out. No idea now. Going to try and get the SD card back and restore an RUU from a CWM backup, then RUU it and should be fixed!
Luckily I have my trusty Xperia Z to use whilst I sort this out!
Click to expand...
Click to collapse
Did you try formatting your sdcard partition from your computer? That sounds like the issue. Likely you corrupted something with all those changes. Remember revone is a hack, so it;s not 100% reliable.

iElvis said:
Did you try formatting your sdcard partition from your computer? That sounds like the issue. Likely you corrupted something with all those changes. Remember revone is a hack, so it;s not 100% reliable.
Click to expand...
Click to collapse
Genius! Dont know how i didnt think of that. Now i have an accessible SD card, just still bootlooping, itll work with the 1.28 backup and then the RUU will correct everything I've messed up

Okay, this needs a bump since this problem is weird now. The phone boots, with a number of roms, but after about 15 seconds, crashes and reboots every single time, no matter what ROM.
I have wiped system, data, cache everything, and it still does this!
Any ideas? an RUU is out of the question since i am on 2.17 and there is no RUU

dh2311 said:
Okay, this needs a bump since this problem is weird now. The phone boots, with a number of roms, but after about 15 seconds, crashes and reboots every single time, no matter what ROM.
I have wiped system, data, cache everything, and it still does this!
Any ideas? an RUU is out of the question since i am on 2.17 and there is no RUU
Click to expand...
Click to collapse
Sounds like a kernel or firmware conflict. Try flashing 2.24 and see if that helps.
Edit: n/m, just saw you're s-on. I think the problem is that you've got an incompatible mix of firmwares from trying to convert to GE. You need to get s-off again somehow.

iElvis said:
Sounds like a kernel or firmware conflict. Try flashing 2.24 and see if that helps.
Click to expand...
Click to collapse
Thats what I thought, tried 1.28, 2.17 and 2.24 with still no success. It doesnt make sense to me.Trying flashing CM10 as i saw someone else suggest
EDIT: same problem! :'(

dh2311 said:
Thats what I thought, tried 1.28, 2.17 and 2.24 with still no success. It doesnt make sense to me.Trying flashing CM10 as i saw someone else suggest
Click to expand...
Click to collapse
Are you flashing firmware or just roms?

iElvis said:
Are you flashing firmware or just roms?
Click to expand...
Click to collapse
I cant flash RUU's becuase of my firmware version (2.17) flashed 1.28 via a CWM backup and the other 2 via ARHD stock odexed roms, best I think i can get becuase theres no 2.17 or 2.24 RUU that I know of

dh2311 said:
I cant flash RUU's becuase of my firmware version (2.17) flashed 1.28 via a CWM backup and the other 2 via ARHD stock odexed roms, best I think i can get becuase theres no 2.17 or 2.24 RUU that I know of
Click to expand...
Click to collapse
I don't mean RUUs, I mean one of the custom firmware packages that you flash in fastboot. But you need to be s-off to do that. You did something like this when you converted to GE.
This is one of the risks of going s-off, unfortunately. It lets you do stuff to your phone that can really screw it up.

iElvis said:
I don't mean RUUs, I mean one of the custom firmware packages that you flash in fastboot. But you need to be s-off to do that. You did something like this when you converted to GE.
This is one of the risks of going s-off, unfortunately. It lets you do stuff to your phone that can really screw it up.
Click to expand...
Click to collapse
Going back to S-ON was my mistake, if this phone was still S-OFF I'd have been able to fix it. But i still cant explain why it bootloops? All I did was change the MID and CID, which are now back to stock (HTC_001) and (PN07100) but it still has the Google edition bootloader, surely if that was the issue then it wouldnt boot past the bootloader, so where does the issue lie?

dh2311 said:
Going back to S-ON was my mistake, if this phone was still S-OFF I'd have been able to fix it. But i still cant explain why it bootloops? All I did was change the MID and CID, which are now back to stock (HTC_001) and (PN07100) but it still has the Google edition bootloader, surely if that was the issue then it wouldnt boot past the bootloader, so where does the issue lie?
Click to expand...
Click to collapse
It could be any number of things. You changed a lot going to GE, and with S-on, the phone is now doing all its usual security checks. Something somewhere got bollixed up. It could be the GE firmware is conflicting with your CID or MID.
One way or another, you've got to get back to s-off.

iElvis said:
It could be any number of things. You changed a lot going to GE, and with S-on, the phone is now doing all its usual security checks. Something somewhere got bollixed up. It could be the GE firmware is conflicting with your CID or MID.
One way or another, you've got to get back to s-off.
Click to expand...
Click to collapse
Thats the solution. Or a 2.24 RUU from HTC could also do it. But revone requires a booting phone, which mine cant do, doesnt work out of recovery unfortunately. and moonshine is only for older versions. Tempted to just put this phone on a shelf and wait for an RUU. Carry on using my Xperia Z

Dont know if this will be of any help for sorting the issue, but this is all the hboot info from getvar all
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.17.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: <removed for safety>
(bootloader) imei: <removed for safety>
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN071000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3821mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-21fde4b846
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Definitely cant seem to get this to work, upon booting i get lots of force closes like the messaging app and contacts storage. That a clue for anyone?
Or if anyone knows how to S-Off without a working F/W that would be a help but I doubt it can be done

[Q] HTC One Bricked?

HTC One International : MaximusHD 13.0, Android 4.3 Sense 5 , stock kernel , S-On
So,my HTC One restarted randomly,and it wouldn't turn on.After 30 minutes of button mashing,I managed to get it into bootloader.
All my efforts to unbrick it were unsuccessful.What I've tried so far was:
1)Since I couldn't enter custom recovery (TWRP 2.5 in my case),I tried to reflash it via fastboot,but it was unsuccessful.All it did was making bootloader freeze!
I even tried "fastboot boot recovery recovery.img",but that didn't work either
2)I also tried to format the device,but that also causes bootloader to freeze!
3)After that I decided to try relocking,and unlocking bootloader.I've managed to lock it,but I can't unlock it.It seems that whenever I try flashing anything bootloader just freezes!
4)Since I locked the bootloader,I decided to try installing RUU.Using the .exe RUU,I managed to get as far as restarting bootloader,after which It freezes. I manually restart the phone(power button + volume down).After that RUU proceeds to waiting for bootloader,where it stays for 5+ minutes,and gives me error 171(I always get this fu***** error)
Also,when I try flashing RUU.zip via fastboot,It causes bootloader to freeze,as well !
Can someone please help,I don't know what else to do....Any ideas on how to unbrick it are welcome,thanks in advance
P.S. - Warranty is out of the question,my carrier doesn't accept phones with tampered software...Is there any way to at least remove this sign,if I cant unbrick my phone?

Guys,does anybody have any ideas on what to do?
I'm kinda freaking out,as I don't know what to do :crying:

Try to s off abd then install any ruu
Sent from my HTC One using XDA Premium 4 mobile app

Thank you for your suggestion,but unfortunately I don't have adb access,it doesn't recognize my phone when it's in bootloader
Is there any workaround to this?
Also,does anybody have any other ideas on what to do?
Thanks in advance

filipjablan said:
Thank you for your suggestion,but unfortunately I don't have adb access,it doesn't recognize my phone when it's in bootloader
Is there any workaround to this?
Also,does anybody have any other ideas on what to do?
Thanks in advance
Click to expand...
Click to collapse
you can get into fastboot?
if so, can you try to do factory reset then flash the custom recovery
adb sideload the rom and install using the custom recovery

What is your wondrous version. If it is 8.1 then try to use 7
Sent from my HTC One using Tapatalk

[email protected] said:
you can get into fastboot?
if so, can you try to do factory reset then flash the custom recovery
adb sideload the rom and install using the custom recovery
Click to expand...
Click to collapse
Already tried that,but factory reset causes bootloader to freeze...I left it for an hour like that,and it was still frozen
Thanks for trying to help out,I appreciate it
BTW,the answer to taha198's question is 7

filipjablan said:
Already tried that,but factory reset causes bootloader to freeze...I left it for an hour like that,and it was still frozen
Thanks for trying to help out,I appreciate it
BTW,the answer to taha198's question is 7
Click to expand...
Click to collapse
try fastboot erase cache?

n1234d said:
try fastboot erase cache?
Click to expand...
Click to collapse
I tried it at least 10 times,but it simply isn't working
I also tried formatting & reflashing each partition(there are 6 in total),but fastboot won't let me erase them,let alone flash them
Also,I locked my bootloader,in order to install RUU,but that doesn't work either,as flashing,copying files & restarting causes bootloader to freeze!
In addition to that I can't unlock my bootloader,as bootloader freezes when I try flashing Unlock_Code.bin
So,all in all,I'm royally screwed

filipjablan said:
I tried it at least 10 times,but it simply isn't working
I also tried formatting & reflashing each partition(there are 6 in total),but fastboot won't let me erase them,let alone flash them
Also,I locked my bootloader,in order to install RUU,but that doesn't work either,as flashing,copying files & restarting causes bootloader to freeze!
In addition to that I can't unlock my bootloader,as bootloader freezes when I try flashing Unlock_Code.bin
So,all in all,I'm royally screwed
Click to expand...
Click to collapse
Wow. Lets see if anyone can come up with a solution. Don't lose hope
Was your bootloader unlocked when you tried to clear/flash the partitions?
And absolutely anything you flash freezes your bootloader?
You might want to try an RUU.exe instead of a zip.

17 3528432
n1234d said:
Wow. Lets see if anyone can come up with a solution. Don't lose hope
Was your bootloader unlocked when you tried to clear/flash the partitions?
And absolutely anything you flash freezes your bootloader?
You might want to try an RUU.exe instead of a zip.
Click to expand...
Click to collapse
I know,sucks to be me,right
Anyway,I tried clearing/flashing partition when bootloader was unlocked,and even after it was locked,but nothing seems to work
I also tried using both .zip & .exe RUU,but neither work - .exe always gives me error 171(I tried it on 3 different PC's),and .zip ones causes bootloader to freeze,as soon as it start flashing files
Is there any way to get around errors 170/171 on RUU.exe?

filipjablan said:
I know,sucks to be me,right
Anyway,I tried clearing/flashing partition when bootloader was unlocked,and even after it was locked,but nothing seems to work
I also tried using both .zip & .exe RUU,but neither work - .exe always gives me error 171(I tried it on 3 different PC's),and .zip ones causes bootloader to freeze,as soon as it start flashing files
Is there any way to get around errors 170/171 on RUU.exe?
Click to expand...
Click to collapse
Have a look here http://forum.xda-developers.com/showthread.php?p=46200901
and this http://androidforums.com/incredible-tips-tricks/161463-ruu-error-170-171-solution-windows-7-a.html

Thanks man,I appreciate your help
Anyway,I forgot to mention that orange LED never lights up,even if it's connected to charger or usb port,for a few hours...
I have a question for you - Could all of this be linked to a custom recovery failure,as I had TWRP 2.5 (touchscreen version)?Despite the fact that it worked well for me for 4 months,it is my belief that touchscreen versions of TWRP & CWM,aren't as reliable...
Can a recovery refusing to "stick" f*** up a phone?
Anyway,personal experience is the best teacher...24 hours ago,I was a complete noob that only knew how to unlock bootloader,flash custom recovery & install custom roms..I've come a far way in a short amount of time,at least something good will come out of this
P.S. - And no,I'm not putting blame on TWRP,doing so would be wrong,as they are doing great work - I'm only asking if such a thing is possible

Thanks for trying to help out,I appreciate it,but unfortunately this didn't work...Whatever I do,I still get 170/171 error.
Also,RUU.zip is out of the question,unfortunately,as fastboot can't to flash & copy files,all it manages to do is freeze my bootloader
Still,the fact that I can enter bootloader,and the fact that my PC recognizes it gives me some hope..Hopefully I'll figure something out (I doubt that's gonna happen,but I can at least hope

filipjablan said:
Thanks man,I appreciate your help
Anyway,I forgot to mention that orange LED never lights up,even if it's connected to charger or usb port,for a few hours...
I have a question for you - Could all of this be linked to a custom recovery failure,as I had TWRP 2.5 (touchscreen version)?Despite the fact that it worked well for me for 4 months,it is my belief that touchscreen versions of TWRP & CWM,aren't as reliable...
Can a recovery refusing to "stick" f*** up a phone?
Anyway,personal experience is the best teacher...24 hours ago,I was a complete noob that only knew how to unlock bootloader,flash custom recovery & install custom roms..I've come a far way in a short amount of time,at least something good will come out of this
P.S. - And no,I'm not putting blame on TWRP,doing so would be wrong,as they are doing great work - I'm only asking if such a thing is possible
Click to expand...
Click to collapse
filipjablan said:
Thanks for trying to help out,I appreciate it,but unfortunately this didn't work...Whatever I do,I still get 170/171 error.
Also,RUU.zip is out of the question,unfortunately,as fastboot can't to flash & copy files,all it manages to do is freeze my bootloader
Still,the fact that I can enter bootloader,and the fact that my PC recognizes it gives me some hope..Hopefully I'll figure something out (I doubt that's gonna happen,but I can at least hope
Click to expand...
Click to collapse
I think this could be a hardware fault then.. Maybe your flash memory is just toast, so anything that you flash freezes your phone, and it can't read any partitions either.. If you were s-off you could've tried reflashing the bootloader.. Maybe you could just take it to your carrier after getting it into that state where it takes "button mashing " to boot, and act like a noob.. They aren't great saints either , they'll just see that it doesn't boot, and issue you a replacement
Sent from my iPod touch using Tapatalk

Any ideas on how to f*** it up even more,so it won't even boot?That way the are more likely to exchange it...
If they see ***Tampered*** in bootloader,they will basically escort me to the closest door
Anyway,as hard as it is for me to accept it,I believe you are right - flash memory is probably dead,that's the only thing that explains it...I've been thinking about it since yesterday,and it makes sense,unfortunately
I appreciate for trying to help out,thanks man,I owe you a beer

Have you tried reformatting flash memory ? There's a guide how to do it. There's a good chance you have bad sectors and this can be fixed , gimme a moment to find you a guide.
Edit :
Here this should solve your problems ( I hope )
http://android-revolution-hd.blogspot.com/2013/10/fix-data-htc-one.html?m=1
Edit ...
Crap for this to work you need working recovery , damn , sorry mate , there must be a solution somewhere , if you were only s-off you could've reflash the bootloader that could've fixed all of this ****.
Sent from my HTC One using XDA Premium 4 mobile app

filipjablan said:
Any ideas on how to f*** it up even more,so it won't even boot?That way the are more likely to exchange it...
If they see ***Tampered*** in bootloader,they will basically escort me to the closest door
Anyway,as hard as it is for me to accept it,I believe you are right - flash memory is probably dead,that's the only thing that explains it...I've been thinking about it since yesterday,and it makes sense,unfortunately
I appreciate for trying to help out,thanks man,I owe you a beer
Click to expand...
Click to collapse
what happens when you do a "fastboot getvar all" in bootloader? also freezes, or does it give you an output? (if you're going to post it remove IMEI and s/n)

filipjablan said:
Any ideas on how to f*** it up even more,so it won't even boot?That way the are more likely to exchange it...
If they see ***Tampered*** in bootloader,they will basically escort me to the closest door
Anyway,as hard as it is for me to accept it,I believe you are right - flash memory is probably dead,that's the only thing that explains it...I've been thinking about it since yesterday,and it makes sense,unfortunately
I appreciate for trying to help out,thanks man,I owe you a beer
Click to expand...
Click to collapse
Well, what happens when you just boot the phone? Does it get stuck at the boot screen? Boot the phone into the bootloader and keep it on for a night or sth, It'll probably discharge by morning, and you should be back at the button mashing phase Take it to them and say that you were clicking photos and you noticed the purple noise issue, and your phone started heating up, and then it just died. That's a three in one If there are customers around, make a ruckus, and he'll hopefully give you a new phone on the spot
BTW, I'm underage

nkk71 said:
what happens when you do a "fastboot getvar all" in bootloader? also freezes, or does it give you an output? (if you're going to post it remove IMEI and s/n)
Click to expand...
Click to collapse
C:\adt-bundle-windows-x86-20130917\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.13
(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: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 3685mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-f188f379dbbfee373cd551f7bc62b8435
getvar:all FAILED (unknown status code)
finished. total time: 0.056s

[Q] I've fallen and I can't get up!

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

[SOLVED] [Q] HTC Stuck on Boot Screen, here's what I did

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

[Q] HTC One M7 OTA Sense 6 Stuck

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/