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

[ON HOLD] Stuck in boot screen (not bootloader, rooted)

Hi, after searching through many posts and trying different things which didn't solve my problem for ours, I decided to just ask...
I have a rooted HTC (Switzerland / Europe version) and I tried to unroot it with different "europe" RUU's from this forum, none worked but I saw in the comments that some of those RUU's required S-OFF. So without any experience whatsoever my mastermind decided to just give it a try and turn S-OFF with the moonshine method. I guess I chose the wrong file (again?) and it didnt work, it always ran 10 restarts in the moonshine method at the end and then the error message "don't drink and shine" popped up. So I gave up and just started the phone.
After starting, I realised that the WIFI and the camera wasn't working anymore (tried all I could) and again I came to this forum and looked for solutions. I tried to wipe everything on the phone, including data wipe and all the wiped I found in twrp. After I did that, I chose the option reboot and well, the phone didnt shut off anymore and I was stuck in the starting screen ( HTC - quitly brilliant -- with the text below: this build is for development....) I tried all the shut down methods with sound button down and so on, also to keep a fleshlight on it (found: http://forum.xda-developers.com/showthread.php?t=2418404 )
I don't know what else to do and I'm pretty much lost. I shouldn't have tried all this without the knowledge damn -.-
please help!

Enion said:
Hi, after searching through many posts and trying different things which didn't solve my problem for ours, I decided to just ask...
I have a rooted HTC (Switzerland / Europe version) and I tried to unroot it with different "europe" RUU's from this forum, none worked but I saw in the comments that some of those RUU's required S-OFF. So without any experience whatsoever my mastermind decided to just give it a try and turn S-OFF with the moonshine method. I guess I chose the wrong file (again?) and it didnt work, it always ran 10 restarts in the moonshine method at the end and then the error message "don't drink and shine" popped up. So I gave up and just started the phone.
After starting, I realised that the WIFI and the camera wasn't working anymore (tried all I could) and again I came to this forum and looked for solutions. I tried to wipe everything on the phone, including data wipe and all the wiped I found in twrp. After I did that, I chose the option reboot and well, the phone didnt shut off anymore and I was stuck in the starting screen ( HTC - quitly brilliant -- with the text below: this build is for development....) I tried all the shut down methods with sound button down and so on, also to keep a fleshlight on it (found: http://forum.xda-developers.com/showthread.php?t=2418404 )
I don't know what else to do and I'm pretty much lost. I shouldn't have tried all this without the knowledge damn -.-
please help!
Click to expand...
Click to collapse
If you can restart and get into bootloader by holding power and vol. down, flash TWRP, put your RUU zip on your phone storage, and then flash it.

kibmikey1 said:
If you can restart and get into bootloader by holding power and vol. down, flash TWRP, put your RUU zip on your phone storage, and then flash it.
Click to expand...
Click to collapse
Hi, thanks for your advice. The problem is that, after recharging the phone again and trying several times, I just can't get into bootloader. When I hold the power button and vol. down the home and "arrow" touch-buttons at the bottom of the phone just start blinking. As long as I hold these two buttons the blinking doesn't stop, I did hold them for a full minute and nothing happend on the screen itself. After releasing the blinking stopped but the screen remained on it's state...

Enion said:
Hi, thanks for your advice. The problem is that, after recharging the phone again and trying several times, I just can't get into bootloader. When I hold the power button and vol. down the home and "arrow" touch-buttons at the bottom of the phone just start blinking. As long as I hold these two buttons the blinking doesn't stop, I did hold them for a full minute and nothing happend on the screen itself. After releasing the blinking stopped but the screen remained on it's state...
Click to expand...
Click to collapse
Blinking is good, just hold POWER + VOLDOWN with the phone sensors under a bright light (not kidding!!), it should reboot after 30sec to 2 minute. If it doesn't reboot, let go and try again; the bright light is important!!
Once it reboots, keep holding VOLDOWN so it reboots to bootloader.

Thank you guys, I tried it and it strangely worked (literally 2minutes with a light on it). I'm in the bootloader now and will try to
flash TWRP, put your RUU zip on your phone storage, and then flash it.
Click to expand...
Click to collapse
as kibmikey1 wrote. I hope I'll find the right files and manuals this time. Will report back

Enion said:
Thank you guys, I tried it and it strangely worked (literally 2minutes with a light on it). I'm in the bootloader now and will try to as kibmikey1 wrote. I hope I'll find the right files and manuals this time. Will report back
Click to expand...
Click to collapse
You can't flash a RUU zip through recovery.
Most important question: What's your final goal?? Where do you want to get with your phone??
also post a "fastboot getvar all" (remove IMEI and s/n), and date of bootloader.
PS: hit the thanks button if we helped

nkk71 said:
You can't flash a RUU zip through recovery.
Most important question: What's your final goal?? Where do you want to get with your phone??
also post a "fastboot getvar all" (remove IMEI and s/n), and date of bootloader.
PS: hit the thanks button if we helped
Click to expand...
Click to collapse
Didn't know about the thank you, my bad there.
My final goal is to have an up-to-date phone. I couldn't update my phone while it was rooted and therefore tried to unroot it and ran into all these complications.
I tried the command you wrote and the result was:
(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.161.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP110
(bootloader) battery-status: good
(bootloader) battery-voltage: 4218mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.062s
thanks!

Enion said:
Didn't know about the thank you, my bad there.
My final goal is to have an up-to-date phone. I couldn't update my phone while it was rooted and therefore tried to unroot it and ran into all these complications.
I tried the command you wrote and the result was:
(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.161.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH35xxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP110
(bootloader) battery-status: good
(bootloader) battery-voltage: 4218mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.062s
thanks!
Click to expand...
Click to collapse
hey mate, edit your post and remove IMEI and s/n we don't need to see those.
can you confirm your hboot is dated before June 2013. I'll post your options after that

Hi, thanks for noticing, I removed it, please dit your post aswell
If you're talking about the date at the top of the bootloader, it says May 3

Enion said:
Hi, thanks for noticing, I removed it, please dit your post aswell
Click to expand...
Click to collapse
I already did when quoting you, changed them all to XXXXXXXXXXX, or is it showing up on your computer?
Enion said:
If you're talking about the date at the top of the bootloader, it says May 3
Click to expand...
Click to collapse
gimme a few minutes while I write down all the options
BTW: Easy on the thanks button, you only have 8 per day

nkk71 said:
I already did when quoting you, changed them all to XXXXXXXXXXX, or is it showing up on your computer?
gimme a few minutes while I write down all the options
BTW: Easy on the thanks button, you only have 8 per day
Click to expand...
Click to collapse
My bad again, it doesn't show up. I need to learn to read the forum rules first before posting stuff I guess.

Enion said:
My bad again, it doesn't show up. I need to learn to read the forum rules first before posting stuff I guess.
Click to expand...
Click to collapse
Code:
(bootloader) version-bootloader: 1.44.0000 (May 3)
(bootloader) version-main: 1.29.161.16
OK, so you have two primary choices:
A) Stay S-On
B) Get S-Off: with the above hboot and firmware, you can easily get s-off using revone
Now, with an unlocked bootloader but S-ON, you can
---- flash custom or stock ROM
---- flash different radios (ie baseband)
---- flash custom kernel
---- flash custom recovery
you cannot:
---- you cannot flash unsigned firmware
---- you cannot downgrade (firmware and hboot)
---- you cannot remove TAMPERED
---- you cannot LOCKED your phone, at best it will say RELOCKED
---- you cannot run a downgrade RUU
With S-Off, you can do ALL of these and more, e.g. you can reset your phone to 100% out-of-the box, and you can even change your phone from a Vodafone phone to ANY other variant (eg unbranded European, US Developer, 100% Google Play Edition, etc.)
I'm in no way encouraging you to go S-Off, unless YOU are comfortable with the thought and procedure.
If you're looking at always having the latest releases, then I personally would stick with custom ROMs, these get updated way quicker (even if sometimes based on a leak), than carrier dependent OTAs.
Should you stay S-On, the only way to upgrade the firmware, will be using an official Vodafone OTA, in one of two methods:
1- go back to stock rom & stock recovery, download and install, and then reinstall custom ROM
2- get your hands on the OTA file (either by downloading it yourself, or if you find it on the net), then extract "firmware.zip" and flash it in fasboot RUU mode (this will work cause the OTA contains a signed firmware specifically for your phone)
[and you cannot downgrade if for some reason you would want to]
On the other hand, if you are S-Off, you can use an unsigned firmware package found in various threads.
Ok, that's enough for now, even my head is spinning LOL.
Let me know what you think, and if you need more explanations. Then rethink your ultimate goal, and we can proceed from there.
(Now all this writing deserves a thanks )

nkk71 said:
Code:
(bootloader) version-bootloader: 1.44.0000 (May 3)
(bootloader) version-main: 1.29.161.16
OK, so you have two primary choices:
A) Stay S-On
B) Get S-Off: with the above hboot and firmware, you can easily get s-off using revone
Now, with an unlocked bootloader but S-ON, you can
---- flash custom or stock ROM
---- flash different radios (ie baseband)
---- flash custom kernel
---- flash custom recovery
you cannot:
---- you cannot flash unsigned firmware
---- you cannot downgrade (firmware and hboot)
---- you cannot remove TAMPERED
---- you cannot LOCKED your phone, at best it will say RELOCKED
---- you cannot run a downgrade RUU
With S-Off, you can do ALL of these and more, e.g. you can reset your phone to 100% out-of-the box, and you can even change your phone from a Vodafone phone to ANY other variant (eg unbranded European, US Developer, 100% Google Play Edition, etc.)
I'm in no way encouraging you to go S-Off, unless YOU are comfortable with the thought and procedure.
If you're looking at always having the latest releases, then I personally would stick with custom ROMs, these get updated way quicker (even if sometimes based on a leak), than carrier dependent OTAs.
Should you stay S-On, the only way to upgrade the firmware, will be using an official Vodafone OTA, in one of two methods:
1- go back to stock rom & stock recovery, download and install, and then reinstall custom ROM
2- get your hands on the OTA file (either by downloading it yourself, or if you find it on the net), then extract "firmware.zip" and flash it in fasboot RUU mode (this will work cause the OTA contains a signed firmware specifically for your phone)
[and you cannot downgrade if for some reason you would want to]
On the other hand, if you are S-Off, you can use an unsigned firmware package found in various threads.
Ok, that's enough for now, even my head is spinning LOL.
Let me know what you think, and if you need more explanations. Then rethink your ultimate goal, and we can proceed from there.
(Now all this writing deserves a thanks )
Click to expand...
Click to collapse
Thanks for the help. I will try to get S-Off then. I hope I can do it this time though. I'll report when I get it Off or need help again. Looking forward

Enion said:
Thanks for the help. I will try to get S-Off then. I hope I can do it this time though. I'll report when I get it Off or need help again. Looking forward
Click to expand...
Click to collapse
No problem mate, remember for revone to work your firmware is good ((bootloader) version-main: 1.29.161.16), but you will need a ROM based on 4.1.2 preferably (I have one - which worked for me and two others) in case you can't find one.
Also read here: http://forum.xda-developers.com/showthread.php?t=2431515
here: http://forum.xda-developers.com/showthread.php?t=2365506
and of course: http://forum.xda-developers.com/showthread.php?t=2314582
Let me know if you need any more help.
Once you are S-Off, you can easily upgrade/downgrade firmware in @vomer's guide (same as before, but down in the firmware section): http://forum.xda-developers.com/showthread.php?t=2365506

Enion said:
Thanks for the help. I will try to get S-Off then. I hope I can do it this time though. I'll report when I get it Off or need help again. Looking forward
Click to expand...
Click to collapse
Hey @Enion, you all good now?

nkk71 said:
Hey @Enion, you all good now?
Click to expand...
Click to collapse
Hi, sry for the late reply, didn't have much time today. I flashed the rom (4.2.1) that nkk71 gave me in a PM and the phone is working just fine now. I decided to just stay in this state for the moment and think about getting S-Off later. I want to thank everyone involved in this thread and especially nkk71, really quick & reliable message board.
//Enion

Enion said:
Hi, sry for the late reply, didn't have much time today. I flashed the rom (4.2.1) that nkk71 gave me in a PM and the phone is working just fine now. I decided to just stay in this state for the moment and think about getting S-Off later. I want to thank everyone involved in this thread and especially nkk71, really quick & reliable message board.
//Enion
Click to expand...
Click to collapse
I know what you mean, just got back from work myself, and didnt have a minute to scratch my head all day :silly:
Just for your info, it took me less than ten minutes to get S-Off using my setup (that ROM and firmware 1.28.61.7), worked like a charm from the first time.
Anyway, until you decide to do it, could you edit the main thread title to include something like [ON HOLD], I usually prefer [SOLVED], but [ON HOLD] should do for now, until you revive your thread

nkk71 said:
I know what you mean, just got back from work myself, and didnt have a minute to scratch my head all day :silly:
Just for your info, it took me less than ten minutes to get S-Off using my setup (that ROM and firmware 1.28.61.7), worked like a charm from the first time.
Anyway, until you decide to do it, could you edit the main thread title to include something like [ON HOLD], I usually prefer [SOLVED], but [ON HOLD] should do for now, until you revive your thread
Click to expand...
Click to collapse
I tried to set in "on hold" but I think I'm missing some rights in this forum, it just doesn't work. I tried http://forum.xda-developers.com/showthread.php?p=27117213 this method aswell.

Enion said:
I tried to set in "on hold" but I think I'm missing some rights in this forum, it just doesn't work. I tried http://forum.xda-developers.com/showthread.php?p=27117213 this method aswell.
Click to expand...
Click to collapse
didnt read the the link you sent, usually you just go to the first post, click EDIT then at the bottom of the edit window, click GO ADVANCED and it would show the main thread title.
anyway don't worry about, most people (unfortunately) never bother to [CLOSE] [SOLVED] etc. no wonder the forum is hard to navigate through
take care
---------- Post added at 07:29 PM ---------- Previous post was at 07:24 PM ----------
nkk71 said:
didnt read the the link you sent, usually you just go to the first post, click EDIT then at the bottom of the edit window, click GO ADVANCED and it would show the main thread title.
anyway don't worry about, most people (unfortunately) never bother to [CLOSE] [SOLVED] etc. no wonder the forum is hard to navigate through
take care
Click to expand...
Click to collapse
Thank you sir!

i need help i think my device is bricked

okk so i was trying to flash a rom for the first time and i really went at it the wrong way. i didin't backup my original RUU and now my device is stuck on the bootloader screen and i really have no idea what to do. i just want to get an OS running on my phone right now cause im freaking out. my company carrier is rogers and this is what my phone is showing right now:
***tampered***
***relocked***
m7_ul pvt ship s-on rh
hboot-1,55,0000
radio-4a.20.3263.16
opendsp -v32,120.274.0909
os-
emmc-boot 2048mb
i try looking for another ruu to flash in my phone but i cant seem to find one that works with my phone..even when i try using the flashboot getvar command to check for the version this is all i got.. : C:\Users\david\Desktop\sdk-tools>fastboot getvar version-main
version-main:
finished. total time: 0.001s
any help at this point would be greatly appreciated i need to get my phone up working so i can receive my calls
i have managed to bring back recovery mode by re-unlocking it via htcdev..now when the phone boots it goes to the google logo and then the language selecting screen then restarts after 10 secs everytime

Instead of the fastboot command you typed, write:
Code:
fastboot getvar all
Then look for "CID". Search for a RUU for that CID. If you can't find one, we'll discuss other solutions.

fenstre said:
Instead of the fastboot command you typed, write:
Code:
fastboot getvar all
Then look for "CID". Search for a RUU for that CID. If you can't find one, we'll discuss other solutions.
Click to expand...
Click to collapse
this is what i got from the fastboot getvar all command :
C:\Users\david\Desktop\sdk-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.20.3263.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA346W904162
(bootloader) imei: 354439050131335
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: ROGER001
(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-fe1214a4f2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.053s
cidnum says ROGER001? im i don't think ive seen cid what that number around
edit: could it be possible that this is what i need ? "M7 CWM Nandroid Backup / CID ROGER001 / 1.29.631.17"
since i did not make a backup is there a chance i can restore this ? ive tried the method that suggest sideloading but it didn't work or maybe i didin't do it right but it didn't wanna recognize my phone when i tried the command'
edit 2: also, im using twrp instead of cwm if that information can help in any way.

If you can let us know which rom you attempted to install and what you managed to do. Did you install custom recovery etc.

gffmac said:
If you can let us know which rom you attempted to install and what you managed to do. Did you install custom recovery etc.
Click to expand...
Click to collapse
well all i was trying to do was install the goole play edition rom (bigxie_m7_GPe_KRT16S_odexed-signed.zip) but after the installation it kept restarting after the language selection screen. i used twrp to flash the rom. right now all im able to do is cycle through the booloader, the recovery screen and to the language selection screen

Unless you have another rom (4.3 rom) copied onto the storage on your phone you will probably have to flash stock recovery and recover by installing a stock RUU for your carrier/CID version.
---------- Post added at 11:59 AM ---------- Previous post was at 11:54 AM ----------
Out of curiosity try going into twrp and doing a factory reset (wipe) and reboot see if you have the same issue.

is there such thing as a stuck RUU for rogers in canada? ive been looking on the internet but i can't seem to find anything that could works for my phone. maybe you could point me in a direction so i could look ?

deerome said:
is there such thing as a stuck RUU for rogers in canada? ive been looking on the internet but i can't seem to find anything that could works for my phone. maybe you could point me in a direction so i could look ?
Click to expand...
Click to collapse
Cant see any for rogers
Just found this http://htconeroot.com/htc-one-tutorials/how-to-copy-files-to-htc-one-using-twrp-mount-and-adb/ if you can copy a rom to the phone it will probably work.
A nandroid backup for rogers is here http://forum.xda-developers.com/showthread.php?t=2207874 or you could flash a pre 4.4 rom. CWM needed to recover a CWM backup and backup would need to be in right directory.
You would need to unlock bootloader to do these things.
If I was you I would download a custom rom like Android Revolution HD 40.3 copy over via above process, do a wipe and install, without s-off you probably have to flash kernel via fastboot.

gffmac said:
Cant see any for rogers
Just found this http://htconeroot.com/htc-one-tutorials/how-to-copy-files-to-htc-one-using-twrp-mount-and-adb/ if you can copy a rom to the phone it will probably work.
A nandroid backup for rogers is here http://forum.xda-developers.com/showthread.php?t=2207874 or you could flash a pre 4.4 rom. CWM needed to recover a CWM backup and backup would need to be in right directory.
You would need to unlock bootloader to do these things.
If I was you I would download a custom rom like Android Revolution HD 40.3 copy over via above process, do a wipe and install, without s-off you probably have to flash kernel via fastboot.
Click to expand...
Click to collapse
thanks for your answers
i definitly am gonna try installing the android revolution hd rom to see if i can at least get an OS running on my phone. what command do i have to use to flash the kernel ?
also, i have tried sideloading/pushing the nandroid backup before but that didint seem to work, not sure if i did something wrong.

deerome said:
thanks for your answers
i definitly am gonna try installing the android revolution hd rom to see if i can at least get an OS running on my phone. what command do i have to use to flash the kernel ?
also, i have tried sideloading/pushing the nandroid backup before but that didint seem to work, not sure if i did something wrong.
Click to expand...
Click to collapse
To flash a kernel via fastboot 'fastboot flash boot boot.img'. Make sure the boot.img (if thats what its called) is in the same folder as fastboot. The corresponding kernel(boot.img) is inside the zip file of most roms.

gffmac said:
To flash a kernel via fastboot 'fastboot flash boot boot.img'. Make sure the boot.img (if thats what its called) is in the same folder as fastboot. The corresponding kernel(boot.img) is inside the zip file of most roms.
Click to expand...
Click to collapse
thanks to your help i was able to install an earlier version of android hd so after many hours of headache i somehow managed to install the android hd rom by sideloading it with cwm. what a pain in the arse -_-. nonetheless that was a great help, what should i do now so something like this don't happen again? i wanted to have the google edtion on my htc but i think im gonna wait until im better at this thing.
anyways thanks again man i really appreciate you have no idea how frustrated i was lol :good:

deerome said:
thanks to your help i was able to install an earlier version of android hd so after many hours of headache i somehow managed to install the android hd rom by sideloading it with cwm. what a pain in the arse -_-. nonetheless that was a great help, what should i do now so something like this don't happen again? i wanted to have the google edtion on my htc but i think im gonna wait until Im better at this thing.
Anyways thanks again man i really appreciate you have no idea how frustrated i was lol :good:
Click to expand...
Click to collapse
No probs glad you got it working again.
If you really want to try a Google Edition rom you would need to s-off your phone which is trickier than what you have done so far so may want to read up some more.

I had the exact same problem while i was flashing a GEdition ROM. The problem here is that my volume Keys dont work and i cant manage to enter recovery/bootloader over ADB. Tried all usb cords and porta. Still giving me Device not found. Any tricky way to access bootloader or recovery?
I've already sent it to warranty but without the original software.... Blablabla they told me that it would only work
with a board replacement... 180€
Any help?
Sent from my Desire HD using Tapatalk

deerxmoose said:
I had the exact same problem while i was flashing a GEdition ROM. The problem here is that my volume Keys dont work and i cant manage to enter recovery/bootloader over ADB. Tried all usb cords and porta. Still giving me Device not found. Any tricky way to access bootloader or recovery?
I've already sent it to warranty but without the original software.... Blablabla they told me that it would only work
with a board replacement... 180€
Any help?
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
You can get to bootloader and recovery via adb commands but thats from a running rom I presume http://forum.xda-developers.com/showthread.php?t=1853159
How come your volume keys dont work, did it come that way? I presume you have tried holding power and volume down for a prolonged length of time??

gffmac said:
You can get to bootloader and recovery via adb commands but thats from a running rom I presume http://forum.xda-developers.com/showthread.php?t=1853159
How come your volume keys dont work, did it come that way? I presume you have tried holding power and volume down for a prolonged length of time??
Click to expand...
Click to collapse
For no reason they stop working. And i think its a hardware malfunction. Besides that, i cant manage to enter bootloader or recovery to instala other ROM.
I guess with Samsung Phones there is a doubletap on the screen to enter bootloader.
Im really stressing here.
Sent from my Desire HD using Tapatalk

deerxmoose said:
For no reason they stop working. And i think its a hardware malfunction. Besides that, i cant manage to enter bootloader or recovery to instala other ROM.
I guess with Samsung Phones there is a doubletap on the screen to enter bootloader.
Im really stressing here.
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
I would contemplate opening the phone up to check the behind the volume buttons but that is very risky.

gffmac said:
I would contemplate opening the phone up to check the behind the volume buttons but that is very risky.
Click to expand...
Click to collapse
Before trying that ill prefer to try Any other solutions. Anyone?
Sent from my Desire HD using Tapatalk

There is no bootloader in Samsung phones, and no doubletap. You need to hit the buttons as well. If you are able to boot into the phone and adb devices shows the device, you can do
adb reboot-bootloader or adb reboot recovery

SaHiLzZ said:
There is no bootloader in Samsung phones, and no doubletap. You need to hit the buttons as well. If you are able to boot into the phone and adb devices shows the device, you can do
adb reboot-bootloader or adb reboot recovery
Click to expand...
Click to collapse
Tried that over and over and it keeps saying device not found.
Sent from my Desire HD using Tapatalk

Then you should fix your computer/adb issues.

[Q] Help with boot loop on brand new HTC One

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!

[Q] [HELP] Possibly bricked phone after firmware update.

Hello, this is my first post here so i'm not sure how to formulate myself or describe the scenario perfectly, but i have been on this forum several times earlier and also now in search for an answer to my phones dysfunction.
Some information about my device:
I have a UL European HTC ONE (m7). I have changed the CID to SuperCID. I had root, unlocked bootloader and s-off.
The problem:
After roaming around the web and searching through posts here and other places, i figured i wanted to upgrade my HTC ONE from rooted stock rom 4.2.2 to 4.4.2. I got the Odexed files from the Android Revolution thread (http://forum.xda-developers.com/showthread.php?t=2224752) and went to TWRP to install it after wiping dalvic, cache, data and system. It failed somehow, but i had no worries as i reverted back to a restore point i made with TWRP, and everything worked. Then i came to the conclusion that it had to do with my firmware being wrong so i tried to flash it with 5.11.401.10 firmware in hope that it would let me install the rom successfully. I followed the instructions of flashing by (i think it was) Android Revolution and everything worked out fine until after i typed the command to restart my device. after that it didn't boot at all.
I have tried the following to turn it back on:
holding the power button (with and without flashlight pointing at the light sensor), holding powerbutton and volume down in hope to get into bootloader but none of these work.
It is also not recognized by my computer but i can hear the "connection" sound windows makes when you plug in an USB device, and in device manager it shows up as "Qualcomm HS-USB Diagnostics 9006 (COM5)".
I'm willing to give more information if it's needed but my question really is just if my phone is hardbricked and i have to buy a new one or not?
Thanks in advance and sorry for my english as it's not my native language!

Hello
The exact same thing happened to me this morning, so I really hope someone can provide with a solution! Maybe wait for the device to run out of battery so it can reset?

Moulsxda said:
Hello
The exact same thing happened to me this morning, so I really hope someone can provide with a solution! Maybe wait for the device to run out of battery so it can reset?
Click to expand...
Click to collapse
I see! i hope some experts see this thread and can have give some experienced insight.
Yeah i thought about that too, but i don't know if it is using any power at all since it's turned off.

goteborg said:
Hello, this is my first post here so i'm not sure how to formulate myself or describe the scenario perfectly, but i have been on this forum several times earlier and also now in search for an answer to my phones dysfunction.
Some information about my device:
I have a UL European HTC ONE (m7). I have changed the CID to SuperCID. I had root, unlocked bootloader and s-off.
The problem:
After roaming around the web and searching through posts here and other places, i figured i wanted to upgrade my HTC ONE from rooted stock rom 4.2.2 to 4.4.2. I got the Odexed files from the Android Revolution thread (http://forum.xda-developers.com/showthread.php?t=2224752) and went to TWRP to install it after wiping dalvic, cache, data and system. It failed somehow, but i had no worries as i reverted back to a restore point i made with TWRP, and everything worked. Then i came to the conclusion that it had to do with my firmware being wrong so i tried to flash it with 5.11.401.10 firmware in hope that it would let me install the rom successfully. I followed the instructions of flashing by (i think it was) Android Revolution and everything worked out fine until after i typed the command to restart my device. after that it didn't boot at all.
I have tried the following to turn it back on:
holding the power button (with and without flashlight pointing at the light sensor), holding powerbutton and volume down in hope to get into bootloader but none of these work.
It is also not recognized by my computer but i can hear the "connection" sound windows makes when you plug in an USB device, and in device manager it shows up as "Qualcomm HS-USB Diagnostics 9006 (COM5)".
I'm willing to give more information if it's needed but my question really is just if my phone is hardbricked and i have to buy a new one or not?
Thanks in advance and sorry for my english as it's not my native language!
Click to expand...
Click to collapse
very strange that it bricked, as that firmware with you being s-off etc should of worked and its your firmware, 401, it may have been a bad download or something, however you are hard bricked, but as it has been caused by software, this should work for you: http://forum.xda-developers.com/showthread.php?t=2770684

Seanie280672 said:
very strange that it bricked, as that firmware with you being s-off etc should of worked and its your firmware, 401, it may have been a bad download or something, however you are hard bricked, but as it has been caused by software, this should work for you: http://forum.xda-developers.com/showthread.php?t=2770684
Click to expand...
Click to collapse
Yeah, i also figured it would update without too much complications, either i have done something very wrong or it just magically bricked.
THANKS for then link! I will try it asap, but i have some questions:
1. I need to get linux, can you tell me of a distro or version, that would work for this? I have no experience with linux you see.
2.it says i need "the appropriate package for the device" what does this reffer to?

goteborg said:
Yeah, i also figured it would update without too much complications, either i have done something very wrong or it just magically bricked.
THANKS for then link! I will try it asap, but i have some questions:
1. I need to get linux, can you tell me of a distro or version, that would work for this? I have no experience with linux you see.
2.it says i need "the appropriate package for the device" what does this reffer to?
Click to expand...
Click to collapse
Here's the Linux stuff I used
ubuntu-13.10-desktop-i386.iso (Be sure and get the 32bit version)
http://www.ubuntu.com/start-download?distro=desktop&bits=32&release=latest
http://www.ubuntu.com/download/desktop/create-a-usb-stick-on-windows
and install adb & fastboot using (copy/paste 1 line at a time into terminal):
Code:
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
you can then check version, by typing "adb version"
and check connection using "adb devices" in custom recovery or booted phone
and "sudo fastboot devices" in bootloader
Click to expand...
Click to collapse
Thanks go to @nkk71

I am forever grateful, i would never have found the correct files! I will try to do this tomorrow as my time is short today. And i suppose the answer to my question about what being "the appropriate package for the device" is in the thread linked earlier, right?
Anyway thanks alot!

goteborg said:
I am forever grateful, i would never have found the correct files! I will try to do this tomorrow as my time is short today. And i suppose the answer to my question about what being "the appropriate package for the device" is in the thread linked earlier, right?
Anyway thanks alot!
Click to expand...
Click to collapse
Ive never had to use the fix myself, thank god, however, at a guess I would say the command sudo ./revive.sh will download the appropriate package. be sure to read the whole of post one before attempting it.

Well i tried tried it now, but something strange happened so i would like the developer to read this feedback but i can't post in the thread since i don't have 10 posts yet..
Anyway, i installed ubuntu, extracted the archive, got to the terminal and proceeded to type "sudo ./revive.sh" where everything went just like it was suppose to.
Then it told me the unbrick was complete, and i should unplug the device for so to turn it on and install the firmware that was in the archive through fastboot when i had charged to 100%.
The next thing that happened was: I unplugged the device, and tried turning it on with no response, i figured it might have been completely decharged, so i plugget it into the wallsocket to see if i could charge it (when it was bricked i got no response from the phone, no led's, vibration, sound, or screenupdate) but even when it's unbricked nothing happens.
So my question is, what should i do now? i figured i would let it charge for a few hours to see if that helps, but aside from that i would like the developers point of view or someone who knows how this works to give me some explanation, if anyone could quote my post and post it in the thread that would be terrific!

goteborg said:
Well i tried tried it now, but something strange happened so i would like the developer to read this feedback but i can't post in the thread since i don't have 10 posts yet..
Anyway, i installed ubuntu, extracted the archive, got to the terminal and proceeded to type "sudo ./revive.sh" where everything went just like it was suppose to.
Then it told me the unbrick was complete, and i should unplug the device for so to turn it on and install the firmware that was in the archive through fastboot when i had charged to 100%.
The next thing that happened was: I unplugged the device, and tried turning it on with no response, i figured it might have been completely decharged, so i plugget it into the wallsocket to see if i could charge it (when it was bricked i got no response from the phone, no led's, vibration, sound, or screenupdate) but even when it's unbricked nothing happens.
So my question is, what should i do now? i figured i would let it charge for a few hours to see if that helps, but aside from that i would like the developers point of view or someone who knows how this works to give me some explanation, if anyone could quote my post and post it in the thread that would be terrific!
Click to expand...
Click to collapse
have you read through the other thread to see if anyone else is experiencing the same problem ?
also, it states you must charge to 100% before switching on, so just leave it on charge for a while, ive also read on that thread somewhere that when you do come to power on, you need to hold the power button for upto 60 seconds before it fires up.
just had a quick read through the thread, read page 3 onwards.......

Seanie280672 said:
have you read through the other thread to see if anyone else is experiencing the same problem ?
also, it states you must charge to 100% before switching on, so just leave it on charge for a while, ive also read on that thread somewhere that when you do come to power on, you need to hold the power button for upto 60 seconds before it fires up.
just had a quick read through the thread, read page 3 onwards.......
Click to expand...
Click to collapse
i figured it out, but now my phone only starts to an icon with the htc one phone and a red triangle over it with an exclamation mark inside the triangle. This is stock recovery right? how can i flash it with fastboot when im in stock recovery, it says no device detected when i try to use ADB to reboot to bootloader, should i just go stright to "fastboot oem rebootRUU" now? i'm sorry for being such a drag, but i don't really have much experience with ADB and fastboot..

goteborg said:
i figured it out, but now my phone only starts to an icon with the htc one phone and a red triangle over it with an exclamation mark inside the triangle. This is stock recovery right? how can i flash it with fastboot when im in stock recovery, it says no device detected when i try to use ADB to reboot to bootloader, should i just go stright to "fastboot oem rebootRUU" now? i'm sorry for being such a drag, but i don't really have much experience with ADB and fastboot..
Click to expand...
Click to collapse
first question has to be have you flashed the stock firmware ? your quite right, that's stock recovery, to get to the bootloader, hold the power button down and the volume down at the same time, the lights on the bottom will flash 10-15 times, when the phone goes off, release the power button only, continue to hold the volume down, phone should now boot to the bootloader.
---------- Post added at 01:44 PM ---------- Previous post was at 01:42 PM ----------
once in the bootloader, first make sure your still unlocked, otherwise you will have to htc dev unlock again before you can flash a custom recovery and proceed any further, sorry but im not sure what the result is from recovery a hard brick, never had it happen and hope it never does.

Seanie280672 said:
first question has to be have you flashed the stock firmware ? your quite right, that's stock recovery, to get to the bootloader, hold the power button down and the volume down at the same time, the lights on the bottom will flash 10-15 times, when the phone goes off, release the power button only, continue to hold the volume down, phone should now boot to the bootloader.
---------- Post added at 01:44 PM ---------- Previous post was at 01:42 PM ----------
once in the bootloader, first make sure your still unlocked, otherwise you will have to htc dev unlock again before you can flash a custom recovery and proceed any further, sorry but im not sure what the result is from recovery a hard brick, never had it happen and hope it never does.
Click to expand...
Click to collapse
WOAH, how could i be this stupid, i thought my bootloader didn't work since i didn't release the powerbutton. i had completely forgotten that! thank you so much, i'll flash the firmware as said in the tutorial i did to unbrick the phone now and see what happens next.
UPDATE:
Finally i got to the point of the tutorial that i am DONE flashing the firmware again! Now am i suppose to flash a new rom, or am i suppose to recover an earlier rom from my restorepoint in twrp?
it all seems to work fine and all seems to be correct according to the variables:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.401.10
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4298mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!

goteborg said:
WOAH, how could i be this stupid, i thought my bootloader didn't work since i didn't release the powerbutton. i had completely forgotten that! thank you so much, i'll flash the firmware as said in the tutorial i did to unbrick the phone now and see what happens next.
Click to expand...
Click to collapse
its easy to forget the simple things when you panicking, but your phone is basically working again, just continue to follow the guide and you'll be good. :good:
think of the bootloader as a computer bios, you have just reflashed the phones bios to fix it, no bios = no power on, if it comes on your bootloadfer is fine.

Seanie280672 said:
its easy to forget the simple things when you panicking, but your phone is basically working again, just continue to follow the guide and you'll be good. :good:
think of the bootloader as a computer bios, you have just reflashed the phones bios to fix it, no bios = no power on, if it comes on your bootloadfer is fine.
Click to expand...
Click to collapse
Haha yeah thanks, but now i only need a rom.. i installed TWRP through fastboot. But if i restore one of the roms i had earlier, will it overwrite the new Firmware? also when i tried to install the rom for the new firmware (stock 4.4.2 with sense 6) i got some error about it being wrong cid, eventhough i have supercid. It's so hard to find stockroms, they are all edited by people..

goteborg said:
Haha yeah thanks, but now i only need a rom.. i installed TWRP through fastboot. But if i restore one of the roms i had earlier, will it overwrite the new Firmware? also when i tried to install the rom for the new firmware (stock 4.4.2 with sense 6) i got some error about it being wrong cid, eventhough i have supercid. It's so hard to find stockroms, they are all edited by people..
Click to expand...
Click to collapse
supercid ive noticed isn't actually in the android-info.txt file of the 401 stock RUU, you have a few choices, you can either change your cid to something like HTC__001 and run the ruu again or you can push a custom rom to your internal storage and flash that, I wouldn't restore any old rom's.

Seanie280672 said:
supercid ive noticed isn't actually in the android-info.txt file of the 401 stock RUU, you have a few choices, you can either change your cid to something like HTC__001 and run the ruu again or you can push a custom rom to your internal storage and flash that, I wouldn't restore any old rom's.
Click to expand...
Click to collapse
Yeah i figured i used the wrong rom, but i got the 4.4.2 sense 6 rom to work now, root, s-off and unlocked. Just like originally planned, now i just have to re-install all my stuff and i'm back up again.
I just have to say thanks to everyone who have helped me fixing this problem, i seriously thought i had to buy a new phone! would give "thanks" if i knew how to also heh.

goteborg said:
Yeah i figured i used the wrong rom, but i got the 4.4.2 sense 6 rom to work now, root, s-off and unlocked. Just like originally planned, now i just have to re-install all my stuff and i'm back up again.
I just have to say thanks to everyone who have helped me fixing this problem, i seriously thought i had to buy a new phone! would give "thanks" if i knew how to also heh.
Click to expand...
Click to collapse
theres a thanks button below each users name on each post, would appreciate it if you could hit it a couple of times.
a true hard brick is if your phone literally dies, if it was caused by software, like yours was, thanks to dexter, it can now be restored in most cases.
---------- Post added at 03:05 PM ---------- Previous post was at 03:00 PM ----------
be sure to post in Dexter's thread to and thank him, he's the true genius.

I am not too sure if anyone is around. I keep getting "command not found after attemping to run revive.sh. Any solution to that?
Edit: nvm. needed to extract directly to the folder.

Unrivalled said:
I am not too sure if anyone is around. I keep getting "command not found after attemping to run revive.sh. Any solution to that?
Edit: nvm. needed to extract directly to the folder.
Click to expand...
Click to collapse
I have my files extracted to the "Downloads" folder but I still get the "command not found"
How did you exactly do it?