Hello, please I need your help guys.
This morning I wanted to unlock my bootloader, got the .bin file from htc and unlocked my phone. After that, I installed the latest twrp via adb and than flashed superSU.
Rebooted my phone, set it up, restored from htc sync manager and everything was good.
I installed Titanium, Solid explorer and some apps, and went to change something in settings. And suddenly, my phone rebooted, twice in a row. There was a message like "unexpected error, send report?". And again, my phone rebooted. This time it didn't booted back.
I started to panic, went to xda, and find the solution to try it to turn on under bright light. I tried it a few times, and suddenly it booted. I went to recovery, wiped everything, booted back and my phone worked for a few hours.
After that I wanted to call my girl and again, it rebooted and didn't booted back. After that, my nightmare started.
Now, even if I got it to boot, my phone won't boot past the HTC logo. If I got my phone to boot into hboot, it suddenly freezes and turn itself off.
If I got my phone to recovery, it will work for some little time, and again, freezes and shut itself down.
I tried to side load a stock sense rom, somewhere in the proces it freezes, turn itself off and I couldn't side load.
Now I'm in real panic because I got only 17% battery left, and I don't now what to do.
Please, does anyone has an advice what should I do
enel_ said:
Hello, please I need your help guys.
This morning I wanted to unlock my bootloader, got the .bin file from htc and unlocked my phone. After that, I installed the latest twrp via adb and than flashed superSU.
Rebooted my phone, set it up, restored from htc sync manager and everything was good.
I installed Titanium, Solid explorer and some apps, and went to change something in settings. And suddenly, my phone rebooted, twice in a row. There was a message like "unexpected error, send report?". And again, my phone rebooted. This time it didn't booted back.
I started to panic, went to xda, and find the solution to try it to turn on under bright light. I tried it a few times, and suddenly it booted. I went to recovery, wiped everything, booted back and my phone worked for a few hours.
After that I wanted to call my girl and again, it rebooted and didn't booted back. After that, my nightmare started.
Now, even if I got it to boot, my phone won't boot past the HTC logo. If I got my phone to boot into hboot, it suddenly freezes and turn itself off.
If I got my phone to recovery, it will work for some little time, and again, freezes and shut itself down.
I tried to side load a stock sense rom, somewhere in the proces it freezes, turn itself off and I couldn't side load.
Now I'm in real panic because I got only 17% battery left, and I don't now what to do.
Please, does anyone has an advice what should I do
Click to expand...
Click to collapse
I'm pretty sure if you can't access HBOOT the phone needs to be sent back. Fastboot is pretty much the last line that we have to fix stuff, it that doesn't work it's most likely hardware
attanasi0 said:
I'm pretty sure if you can't access HBOOT the phone needs to be sent back. Fastboot is pretty much the last line that we have to fix stuff, it that doesn't work it's most likely hardware
Click to expand...
Click to collapse
The problem is, I can acces HBOOT and even Recovery, but for a short time, after that it freezes and shut itself down.
I got new information, I just tried to boot my phone normaly, it booted to my homescreen. Because I got a low battery, I immediately turned it off, and connected my charge, and it started to charge. And after 20 min, it booted itself on!!! I wasn't even near the phone...
Just some more info, when it freezes and shut down, if I connect my charger it won't charge
This is why I had to immediately turn it off normally, and than it started to charge.
enel_ said:
The problem is, I can acces HBOOT and even Recovery, but for a short time, after that it freezes and shut itself down.
I got new information, I just tried to boot my phone normaly, it booted to my homescreen. Because I got a low battery, I immediately turned it off, and connected my charge, and it started to charge. And after 20 min, it booted itself on!!! I wasn't even near the phone...
Just some more info, when it freezes and shut down, if I connect my charger it won't charge
This is why I had to immediately turn it off normally, and than it started to charge.
Click to expand...
Click to collapse
Do you have enough time before it freezes to get us a "fastboot getvar all" ?
" "
enel_ said:
Hello, please I need your help guys.
This morning I wanted to unlock my bootloader, got the .bin file from htc and unlocked my phone. After that, I installed the latest twrp via adb and than flashed superSU.
Rebooted my phone, set it up, restored from htc sync manager and everything was good.
I installed Titanium, Solid explorer and some apps, and went to change something in settings. And suddenly, my phone rebooted, twice in a row. There was a message like "unexpected error, send report?". And again, my phone rebooted. This time it didn't booted back.
I started to panic, went to xda, and find the solution to try it to turn on under bright light. I tried it a few times, and suddenly it booted. I went to recovery, wiped everything, booted back and my phone worked for a few hours.
After that I wanted to call my girl and again, it rebooted and didn't booted back. After that, my nightmare started.
Now, even if I got it to boot, my phone won't boot past the HTC logo. If I got my phone to boot into hboot, it suddenly freezes and turn itself off.
If I got my phone to recovery, it will work for some little time, and again, freezes and shut itself down.
I tried to side load a stock sense rom, somewhere in the proces it freezes, turn itself off and I couldn't side load.
Now I'm in real panic because I got only 17% battery left, and I don't now what to do.
Please, does anyone has an advice what should I do
Click to expand...
Click to collapse
Did you go s off?
attanasi0 said:
Do you have enough time before it freezes to get us a "fastboot getvar all" ?
" "
Click to expand...
Click to collapse
The time before it freezes is never the same, but I will try my best to get it.
Just now, the following happened, my phone was off, charging, led on. I just wanted to see if everything is ok, picked up my phone from my desk, no charging, no led, again totally turned off, the same way it is totally turned off when it freezes and shut itself down.... I can't turn it on again.
LibertyMarine said:
Did you go s off?
Click to expand...
Click to collapse
No, I just wanted for the first time to unlock my bootloader.
All my phones before this were Nexus phones and Samsung phones, this is my first HTC and this is what I got...
enel_ said:
The time before it freezes is never the same, but I will try my best to get it.
Just now, the following happened, my phone was off, charging, led on. I just wanted to see if everything is ok, picked up my phone from my desk, no charging, no led, again totally turned off, the same way it is totally turned off when it freezes and shut itself down.... I can't turn it on again.
Click to expand...
Click to collapse
Even by holding the power button for 15 seconds ?
attanasi0 said:
Even by holding the power button for 15 seconds ?
Click to expand...
Click to collapse
Out of 20 tries to turn it on, I manage to turn it on one or none times, and every try of these 20 is a by holding the power button over 15 seconds.
enel_ said:
Out of 20 tries to turn it on, I manage to turn it on one or none times, and every try of these 20 is a by holding the power button over 15 seconds.
Click to expand...
Click to collapse
Do the same but while also holding the Volume-down button and make sure there's plenty of light hitting the sensors on top of the screen
attanasi0 said:
Do the same but while also holding the Volume-down button and make sure there's plenty of light hitting the sensors on top of the screen
Click to expand...
Click to collapse
I have done that too, it will boot, but again it freezes at some point and turn itself off and have again to battle with the turn on process.
My biggest concern now is my battery, I can't charge it.
This morning, something was a bit strange to me, I've got a old PC with Win 7 and a laptop with Win 8.
I made the unlock process on my Win 7 machine, but the strange thing was that the identifier token that I got over adb on my Win 8 machine was different than my token on Win 7 machine, the numbers and letters were different.
I used the token from my win 7 machine and completed the whole process of unlocking the bootloader on that machine.
enel_ said:
I have done that too, it will boot, but again it freezes at some point and turn itself off and have again to battle with the turn on process.
My biggest concern now is my battery, I can't charge it.
This morning, something was a bit strange to me, I've got a old PC with Win 7 and a laptop with Win 8.
I made the unlock process on my Win 7 machine, but the strange thing was that the identifier token that I got over adb on my Win 8 machine was different than my token on Win 7 machine, the numbers and letters were different.
I used the token from my win 7 machine and completed the whole process of unlocking the bootloader on that machine.
Click to expand...
Click to collapse
WARNING
Don't push the powerbutton too hard for a too long time! That's how I ****ed up mine!!! BE CAREFUL!
attanasi0 said:
Do you have enough time before it freezes to get us a "fastboot getvar all" ?
" "
Click to expand...
Click to collapse
Here is it:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXX - changed this too
(bootloader) imei: XXXXXXXXXXXXXX - I changed this.
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4276mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.048s
I accomplished to turn my phone off and charge it to 95%. It's now on, but I have no idea how long it will be on and when it's going to shut down itself.
What should I flash, what should I do?
I can access fastboot, recovery, my homescreen, everything but for how long...
Should I relock it? No, I would lose my recovery that would be bad.
Should I change my recovery?
And at the time I'm writing this, he shut down...
I was successful at getting a logcat. Because this is my first logcat, and don't know have I done everything good. I think the logcat ended when my phone restarted itself.
I hope this can help.
But there is a problem, the file is to big to upload on xda and the text is to long to copy it here, can someone help me with this?
enel_ said:
I was successful at getting a logcat. Because this is my first logcat, and don't know have I done everything good. I think the logcat ended when my phone restarted itself.
I hope this can help.
But there is a problem, the file is to big to upload on xda and the text is to long to copy it here, can someone help me with this?
Click to expand...
Click to collapse
Upload on google drive or other file sharing site and post the link here
ok here it is:
1. in HBOOT select FASTBOOT USB with connected cable
2. type in cmd:
Code:
fastboot erase cache
3. now you should be able to access recovery, check if you are using latest recovery I'd recommend THIS
4. reflash recovery in cmd:
Code:
fastboot flash recovery <file_name>.img
5. boot your phone in recovery, you may see some errors but that's fine, mount /data partition only
6. push rom to your (virtual) sd card by cmd:
Code:
adb push <file_name>.zip /data/media/0/
7. wait about 6 minutes until rom is being transferred to your phone.
8. in recovery format /system then format /cache and next format /data (do NOT select /data/media !!!)
9. reboot recovery - you may see some errors but that's fine.
10. reflash your rom
Hope that helps
I managed to upload my logcat, here it is:
http://www14.zippyshare.com/v/26697521/file.html
xavier_largeaux said:
ok here it is:
Click to expand...
Click to collapse
I'm afraid xavier to flash a new rom because my phone is unstable in recovery, what if it freezes and shuts itself down in the middle of the flashing process?
What if I just flash the stock recovery and lock my bootloader again? Maybe my phone is so unstable because of the bootloader?
enel_ said:
I managed to upload my logcat, here it is:
http://www14.zippyshare.com/v/26697521/file.html
I'm afraid xavier to flash a new rom because my phone is unstable in recovery, what if it freezes and shuts itself down in the middle of the flashing process?
What if I just flash the stock recovery and lock my bootloader again? Maybe my phone is so unstable because of the bootloader?
Click to expand...
Click to collapse
if you only unlocked bootloader that's fine you wouldn't have chance to brick your device, however if you S-OFF there is high risk of soft / hard bricking device as you have unrestricted access to ALL partitions, with S-ON you have access to only few partitions.
When you unlocked your bootloader it WIPED automatically your /data partition and you lost everything what you had on it.
I remember some time ago that someone after installing TWRP recovery had the same issue what you have described in your post.
Either you must lock you bootloader and flash entire RUU matching your CID & MID.
Or follow all steps in my previous post.
xavier_largeaux said:
if you only unlocked bootloader that's fine you wouldn't have chance to brick your device, however if you S-OFF there is high risk of soft / hard bricking device as you have unrestricted access to ALL partitions, with S-ON you have access to only few partitions.
When you unlocked your bootloader it WIPED automatically your /data partition and you lost everything what you had on it.
I remember some time ago that someone after installing TWRP recovery had the same issue what you have described in your post.
Either you must lock you bootloader and flash entire RUU matching your CID & MID.
Or follow all steps in my previous post.
Click to expand...
Click to collapse
No no, I just unlocked my bootloader, flashed recovery and installed superSU.
Unfortunately I flashed TWRP also after I unlocker my bootloader...
10 min ago I wanted to flash stock recovery then clockworkmod and then the rest of your process. Somehow I booted my phone into fastboot, after a lot of attempts to boot it, connected it to my laptop, went into cmd, typed fastboot flash recovery recovery. img it started but suddenly my phone shut itself down, I got a failure in cmd and now after over 30 attempts I can't boot my device.
Is the interruption of this process something bad? Bricked device?
enel_ said:
No no, I just unlocked my bootloader, flashed recovery and installed superSU.
Unfortunately I flashed TWRP also after I unlocker my bootloader...
10 min ago I wanted to flash stock recovery then clockworkmod and then the rest of your process. Somehow I booted my phone into fastboot, after a lot of attempts to boot it, connected it to my laptop, went into cmd, typed fastboot flash recovery recovery. img it started but suddenly my phone shut itself down, I got a failure in cmd and now after over 30 attempts I can't boot my device.
Is the interruption of this process something bad? Bricked device?
Click to expand...
Click to collapse
You are S-ON, and no you DID NOT bricked your device. It's TWRP issue I'm sure to 100%
When your HTC is switched off press and hold VOL Down and Power button together for 10 sec. You should be in HBOOT.
Try to flash stock boot.img first and then again follow above instructions. That must resolve the problem.
Related
I am a noob. I tried rooting my HTC First and made huge mistake. I started with unlocking bootloader as some tutorial explained and got successfull with that. problem started when I could start SuperUser. It gave some errors. So I tried to use some other thing. I did flashing without doing any backup. I used TWRP recovery without any recovery image for my device and i also flashed Kernel with some Image that came in that package for HTC One. As I flashed and rebooted the phone it displayed message: 'This build is for development purpose only Do not distribute outside of HTC without HTC's written permission. Failure to comply may lead to legal action.' I am able to go into bootloader menu. but nothing apart from that.
Now I dont understand if my phone is bricked or something. I need somebody to help me out.
Everything you did is a big no.. You should have first checked this forum out before doing anything else.
Congratulations you aren't bricked
Use this tool to get the appropriate recovery for your phone, also flash a boot.img for the device you've got. You can find it somewhere around this place.
http://forum.xda-developers.com/showthread.php?t=2561159
You should first try locking the boot loader to see if it boots. If it does use the oldest RUU to restore
HTC First
thanks for the reply.. i did what u said.
i flashed with boot.img and locked bootloader but no success. Now it shows **** Relocked ****, **** security warning**** and at the top ****Tampered****.
I dont have RUU . Tell me what should I do.:crying:
hussainmustafa21 said:
thanks for the reply.. i did what u said.
i flashed with boot.img and locked bootloader but no success. Now it shows **** Relocked ****, **** security warning**** and at the top ****Tampered****.
I dont have RUU . Tell me what should I do.:crying:
Click to expand...
Click to collapse
1) is it stuck in a bootloop or does it not boot at all?
2) what boot.img did you flash?
3) try side loading the stock ROM to flash it and then flash the boot.IMG as well, of course you'll have to unlock the device first
Ruu needed
abrahammmmmmm_ said:
1) is it stuck in a bootloop or does it not boot at all?
2) what boot.img did you flash?
3) try side loading the stock ROM to flash it and then flash the boot.IMG as well, of course you'll have to unlock the device first
Click to expand...
Click to collapse
Its in bootloops. Cant go into recovery.
Now i dont remember what boot.img I flashed my phone with.
I would really appriciate if u can provide me with the required RUU.
version: 0.5
version-bootloader: 2.08.0000
version-baseband: 1.53.51.0108
version-cpld: None
version-microp: None
version-main: 3.04.708.4
version-misc: PVT SHIP S-ON
product: valente_wx_c9
platform: HBOOT-8960
modelid: PK0711000
cidnum: HTC__622
battery-status: good
battery-voltage: 3753mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
hussainmustafa21 said:
Its in bootloops. Cant go into recovery.
Now i dont remember what boot.img I flashed my phone with.
I would really appriciate if u can provide me with the required RUU.
version: 0.5
version-bootloader: 2.08.0000
version-baseband: 1.53.51.0108
version-cpld: None
version-microp: None
version-main: 3.04.708.4
version-misc: PVT SHIP S-ON
product: valente_wx_c9
platform: HBOOT-8960
modelid: PK0711000
cidnum: HTC__622
battery-status: good
battery-voltage: 3753mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
Click to expand...
Click to collapse
If it doesn't boot the RUU is completely useless. It only works if you can get to the homescreen and turn on USB debugging.
But I thought you could get in the boot loader? That's the only way you can get into recovery.
It you can get to three recovery just select "restore" or whatever it reads. If that doesn't work you'll have to get twrp, sideload a ROM and then flash it
Hold on a sec. Youre in a boot loop? If your bootloader is UNLOCKED...then durring the boot up proccess just keep holding the volume down and power...this should FORCE power down your deivce...you will notice how the home back and menu buttons BLINK.
once it is OFF, then boot into HBoot using the usual method of holding power and volume down...the lock the bootloader IF it is unlocked, this should fix the boot loop. If it is already locked, TRY to do a factory reset, idk if that will help. If you can boot into TWRP, make a back up...FORMAT everything, like the data, system and everything and restore ONLY the /system and /boot.
I have a back up that i made, but its over 1gb and that would take for ever to upload so if anyone can please upload a back up. But if you do get it to boot, then use an RUU.
---------- Post added at 04:49 PM ---------- Previous post was at 04:46 PM ----------
russian392 said:
Hold on a sec. Youre in a boot loop? If your bootloader is UNLOCKED...then durring the boot up proccess just keep holding the volume down and power...this should FORCE power down your deivce...you will notice how the home back and menu buttons BLINK.
once it is OFF, then boot into HBoot using the usual method of holding power and volume down...the lock the bootloader IF it is unlocked, this should fix the boot loop. If it is already locked, TRY to do a factory reset, idk if that will help. If you can boot into TWRP, make a back up...FORMAT everything, like the data, system and everything and restore ONLY the /system and /boot.
I have a back up that i made, but its over 1gb and that would take for ever to upload so if anyone can please upload a back up. But if you do get it to boot, then use an RUU.
Click to expand...
Click to collapse
If your bootloader is locked, try unlocking it, and booting up, if that doesnt work, try locking it again and then boot....if non of that works, then idk.
thing is...next time please consult the community to see if that file is legit and works...
russian392 said:
Hold on a sec. Youre in a boot loop? If your bootloader is UNLOCKED...then durring the boot up proccess just keep holding the volume down and power...this should FORCE power down your deivce...you will notice how the home back and menu buttons BLINK.
once it is OFF, then boot into HBoot using the usual method of holding power and volume down...the lock the bootloader IF it is unlocked, this should fix the boot loop. If it is already locked, TRY to do a factory reset, idk if that will help. If you can boot into TWRP, make a back up...FORMAT everything, like the data, system and everything and restore ONLY the /system and /boot.
I have a back up that i made, but its over 1gb and that would take for ever to upload so if anyone can please upload a back up. But if you do get it to boot, then use an RUU.
---------- Post added at 04:49 PM ---------- Previous post was at 04:46 PM ----------
If your bootloader is locked, try unlocking it, and booting up, if that doesnt work, try locking it again and then boot....if non of that works, then idk.
thing is...next time please consult the community to see if that file is legit and works...
Click to expand...
Click to collapse
wouldn't be easier to sideload then completely flash a rom and then the boot.IMG ?
Uploading a full backup won't be the safest thing to do as anyone from or not from this forum can access it and 1gb might contain allot of personal data..
How to side load
abrahammmmmmm_ said:
wouldn't be easier to sideload then completely flash a rom and then the boot.IMG ?
Uploading a full backup won't be the safest thing to do as anyone from or not from this forum can access it and 1gb might contain allot of personal data..
Click to expand...
Click to collapse
whoa its getting whole lot confusing now!!
Each new reply brings new set of words which I am totally unaware off!
Bt it feels good that You guys are trying to help!
As of now I understand I should flash 'right' boot.img for my phone
Or do sideload(the meaning of which i dont know!)
Ruu is outta option as I CANT BOOT up!!
hussainmustafa21 said:
whoa its getting whole lot confusing now!!
Each new reply brings new set of words which I am totally unaware off!
Bt it feels good that You guys are trying to help!
As of now I understand I should flash 'right' boot.img for my phone
Or do sideload(the meaning of which i dont know!)
Ruu is outta option as I CANT BOOT up!!
Click to expand...
Click to collapse
Sorry. Let's do this in steps and you reply whether it worked or not.
1) go into the boot loader and select the option to factory restore.
Come back to this to tell if it worked or not.
abrahammmmmmm_ said:
Sorry. Let's do this in steps and you reply whether it worked or not.
1) go into the boot loader and select the option to factory restore.
Come back to this to tell if it worked or not.
Click to expand...
Click to collapse
ok tried doing factory reset. Nothing happened. Like it restared the HTC logo came below it displayed 'this build.....' then it stayed like that.
hussainmustafa21 said:
ok tried doing factory reset. Nothing happened. Like it restared the HTC logo came below it displayed 'this build.....' then it stayed like that.
Click to expand...
Click to collapse
OK. Guess the stock recovery got corrupted then.
2) do you know how to flash a custom recovery? If so go ahead and install twrp. There's a tool somewhere in this device's forum that will do it in 1 click for you
abrahammmmmmm_ said:
OK. Guess the stock recovery got corrupted then.
2) do you know how to flash a custom recovery? If so go ahead and install twrp. There's a tool somewhere in this device's forum that will do it in 1 click for you
Click to expand...
Click to collapse
just want to confirm! Is TWRP same for every phone or it too changes?!
abrahammmmmmm_ said:
wouldn't be easier to sideload then completely flash a rom and then the boot.IMG ?
Uploading a full backup won't be the safest thing to do as anyone from or not from this forum can access it and 1gb might contain allot of personal data..
Click to expand...
Click to collapse
um...format the phone,,,back up,,,upload that fresh back up, and then restore the back up of YOUR phone and it should be just the way you left it.
also, based on my previous knowledge. a boot.img is a kernel...is that what you tried to flash? cause if it is, no wonder you cant boot up cause the kernel is what does the boot up.
hussainmustafa21 said:
just want to confirm! Is TWRP same for every phone or it too changes?!
Click to expand...
Click to collapse
each recovery has to be unique to a phone. so now, twrp is NOT universal!
ALSO. go find JMZ's kernel here somewhere in the forums...if your phone is S-OFF (find it in the hboot if it is ) and flash that if you can get the recovery going
To flash a recovery, here is the easy and quick way of doing it...there is alot less to read.
http://argue4android.blogspot.com/2013/12/how-to-root-htc-first_11.html (scroll down to part 2)
also...did you receive an att update? thats probably what messed everything up
He isn't s-off.
And the ota doesn't mess up the phone. Moonshine just doesn't support it.
http://forum.xda-developers.com/showthread.php?t=2561159
That link has the tool to flash the appropriate twrp recovery in 1 click.
abrahammmmmmm_ said:
He isn't s-off.
And the ota doesn't mess up the phone. Moonshine just doesn't support it.
http://forum.xda-developers.com/showthread.php?t=2561159
That link has the tool to flash the appropriate twrp recovery in 1 click.
Click to expand...
Click to collapse
Hey guys!! Phone just got booted up!
I searched the internet and found a boot.img and flashed it! The phone started!
Then when I switched off it again it displayed the Htc logo and the same error message..
Then I locked the bootloader and everything was fine again!
Bt now one more problem that I am facing is, when I inserted my Sim card it is not recognising it!!
And in setting panel all the GSM options are fade!?
What do u all think?!
And one more thing! To be on safeside the first thing I did was to go into recovery and take backup but my phone did go into that mode! Please help!
hussainmustafa21 said:
Hey guys!! Phone just got booted up!
I searched the internet and found a boot.img and flashed it! The phone started!
Then when I switched off it again it displayed the Htc logo and the same error message..
Then I locked the bootloader and everything was fine again!
Bt now one more problem that I am facing is, when I inserted my Sim card it is not recognising it!!
And in setting panel all the GSM options are fade!?
What do u all think?!
And one more thing! To be on safeside the first thing I did was to go into recovery and take backup but my phone did go into that mode! Please help!
Click to expand...
Click to collapse
That's what I first told you to do but OK glad it worke! . And I know exactly what you're talking about with the "gsm settings" you've once again flashed an incompatible but compatible enough boot.img for it to boot but didn't have the correct radios to be able to access data, wifi, etc
Making a backup won't work since you can only do that in cwm/tarp and not on the stock recovery. Right now what you would want to do is use this RUU to restore
http://www.androidruu.com/getdownlo...3_2_10.64.40.33AL_release_316579_signed_2.exe
abrahammmmmmm_ said:
That's what I first told you to do but OK glad it worke! . And I know exactly what you're talking about with the "gsm settings" you've once again flashed an incompatible but compatible enough boot.img for it to boot but didn't have the correct radios to be able to access data, wifi, etc
Making a backup won't work since you can only do that in cwm/tarp and not on the stock recovery. Right now what you would want to do is use this RUU to restore
http://www.androidruu.com/getdownlo...3_2_10.64.40.33AL_release_316579_signed_2.exe
Click to expand...
Click to collapse
Thanks alot buddies... Phone working good! Learned a lot. You guys were amaZing. Thanks for all the help n patience.
N I have skipped rooting! Atleast with this phone.
thing is...anyone know why my ruu isnt working? ran as admin on win7 and it just circled and circled, then nothing...waited like 5 minutes...nothing, ran it like 10 times...nothing...
russian392 said:
thing is...anyone know why my ruu isnt working? ran as admin on win7 and it just circled and circled, then nothing...waited like 5 minutes...nothing, ran it like 10 times...nothing...
Click to expand...
Click to collapse
Must be the computer the RUU has no compatibility issues with any set up, just a regular ol' program. No drivers or anything special needed for it to start up.
Make sure you check all the prompts for permissions it asks you or an antivirus could be holding it back. I'm just throwing out ideas here, I've never had any problems
I recently upgraded to an HTC One, on Verizon in the US. I promptly used rumrunner s-off to get S-OFF, unlock the bootloader, and obtain root. I also flashed the latest ClockworkMod recovery, with the intent of installing CyanogenMod, but decided I'd try out the stock ROM for a few days first, since my old phone was still on Gingerbread.
Everything was working fine until I decided to remove some Verizon bloatware. While I did back up each app before removing it, I forgot to make a nandroid backup. I only removed things that seemed nonessential -- such as the NFL Mobile app, Slacker radio, and My Verizon, which I'd also removed without issue on my old phone -- but apparently that was not the case, as after rebooting, I got stuck on the Verizon logo during the boot sequence.
I then attempted to perform a factory reset in CWMR, and it appeared to be stuck on "wiping cache", so -- like the impatient idiot I clearly am, as I later found a few threads explaining that this part of the reset process can just take a very long time -- I rebooted the phone to try again. This resulted in CWMR throwing errors about failing to mount several partitions, but it finally seemed to finish the reset on the second try. However, upon reboot, it just sat at the HTC logo forever.
After about an hour, and no success in finding anything on the internet indicating that it should take this long to boot up after a reset, I powered the phone off and back on again. After rebooting, the bootloader screen displayed "OS" in red followed by some random symbols. I could still get into recovery, and could still access the device with fastboot, so I decided to try to reflash the stock ROM, using the RUU zip found here.
Due to some problem (this was all about 6 hours ago while I was at work, and I was quite frustrated at this point, so I don't remember what exactly was the problem here) and based on the advice of another forum thread, I decided to try TWRP instead of CWM. But, TWRP wouldn't go any further than its logo splash screen, so I re-flashed CWM. Afterwards, my phone went into a reboot loop -- the HTC logo comes up, the phone vibrates shortly, and then after a few seconds the screen turns off and it does the same thing over again. If I hold the power button down for long enough, it will power down, but if I try to turn it back on, it will either go into the loop again, or just sit at the HTC logo (left it there for upwards of an hour at one point).
I have found several threads about similar boot loop issues, but as I can't get into hboot/fastboot or recovery, I can't try to apply any of the solutions. I cannot connect from my computer with fastboot or adb -- "devices" lists nothing, and all other commands return either "error: no device found" or "waiting for device". No amount of power+volume down makes any difference, nor does holding the phone under a bright light as several threads suggested. Occasionally it will go to a black screen (not off, just black) that maybe it thinks is the bootloader menu, but it doesn't display anything, and after about 30 seconds it will reboot itself.
Does anyone have any suggestions for getting into recovery and trying to reflash.... something?
Alternatively, if I return it to Verizon at this point, will they be able to tell that it's rooted/unlocked/S-OFF?
Any ideas would be much appreciated!
brasstongue said:
I recently upgraded to an HTC One, on Verizon in the US. I promptly used rumrunner s-off to get S-OFF, unlock the bootloader, and obtain root. I also flashed the latest ClockworkMod recovery, with the intent of installing CyanogenMod, but decided I'd try out the stock ROM for a few days first, since my old phone was still on Gingerbread.
Everything was working fine until I decided to remove some Verizon bloatware. While I did back up each app before removing it, I forgot to make a nandroid backup. I only removed things that seemed nonessential -- such as the NFL Mobile app, Slacker radio, and My Verizon, which I'd also removed without issue on my old phone -- but apparently that was not the case, as after rebooting, I got stuck on the Verizon logo during the boot sequence.
I then attempted to perform a factory reset in CWMR, and it appeared to be stuck on "wiping cache", so -- like the impatient idiot I clearly am, as I later found a few threads explaining that this part of the reset process can just take a very long time -- I rebooted the phone to try again. This resulted in CWMR throwing errors about failing to mount several partitions, but it finally seemed to finish the reset on the second try. However, upon reboot, it just sat at the HTC logo forever.
After about an hour, and no success in finding anything on the internet indicating that it should take this long to boot up after a reset, I powered the phone off and back on again. After rebooting, the bootloader screen displayed "OS" in red followed by some random symbols. I could still get into recovery, and could still access the device with fastboot, so I decided to try to reflash the stock ROM, using the RUU zip found here.
Due to some problem (this was all about 6 hours ago while I was at work, and I was quite frustrated at this point, so I don't remember what exactly was the problem here) and based on the advice of another forum thread, I decided to try TWRP instead of CWM. But, TWRP wouldn't go any further than its logo splash screen, so I re-flashed CWM. Afterwards, my phone went into a reboot loop -- the HTC logo comes up, the phone vibrates shortly, and then after a few seconds the screen turns off and it does the same thing over again. If I hold the power button down for long enough, it will power down, but if I try to turn it back on, it will either go into the loop again, or just sit at the HTC logo (left it there for upwards of an hour at one point).
I have found several threads about similar boot loop issues, but as I can't get into hboot/fastboot or recovery, I can't try to apply any of the solutions. I cannot connect from my computer with fastboot or adb -- "devices" lists nothing, and all other commands return either "error: no device found" or "waiting for device". No amount of power+volume down makes any difference, nor does holding the phone under a bright light as several threads suggested. Occasionally it will go to a black screen (not off, just black) that maybe it thinks is the bootloader menu, but it doesn't display anything, and after about 30 seconds it will reboot itself.
Does anyone have any suggestions for getting into recovery and trying to reflash.... something?
Alternatively, if I return it to Verizon at this point, will they be able to tell that it's rooted/unlocked/S-OFF?
Any ideas would be much appreciated!
Click to expand...
Click to collapse
Can u get into bootloader?? Press power + vol down??
brasstongue said:
After rebooting, the bootloader screen displayed "OS" in red followed by some random symbols.
Click to expand...
Click to collapse
that means your firmware is either in a state of limbo, or you corrupted one of your partitions.
so I decided to try to reflash the stock ROM, using the RUU zip found here. Due to some problem
Click to expand...
Click to collapse
which ruu, and what was the problem
But, TWRP wouldn't go any further than its logo splash screen, so I re-flashed CWM.
Click to expand...
Click to collapse
Did you flash the correct recovery for Verizon (M7_WLS), it's different than international (M7_U/UL)
as @khandelwalsiddharth mentioned you need to get to bootloader if a fix is even possible, so POWER OFF your phone completely, then HOLD VOLDOWN and POWER, when it boots up let go of POWER but keep holding VOLDOWN until you get to bootloader
then you need to have working "fastboot devices" (if you're on Win8.1, you probably need to use another computer with Win7 or use a Linux Live USB)
if you can't get to bootloader, then I don't think this is fixable, cause hboot is corrupt
Thanks for the reply.
nkk71 said:
which ruu, and what was the problem
Click to expand...
Click to collapse
Oh, I guess I forgot to make that a link... I had downloaded the only VZW one on this page but I'm not even sure why I bothered to mention it, as downloading it to my computer was the only thing I ever did with it; I was never able to get as far as flashing it to the phone, so it actually had nothing to do with the problem...
nkk71 said:
Did you flash the correct recovery for Verizon (M7_WLS), it's different than international (M7_U/UL)
Click to expand...
Click to collapse
I was under the impression that Verizon was m7vzw, in which case yes, I was using the correct recovery (6.0.4.7 version listed next to "HTC One (Verizon)" on this page) and it was working just fine the first time I flashed it.
nkk71 said:
as @khandelwalsiddharth mentioned you need to get to bootloader if a fix is even possible, so POWER OFF your phone completely, then HOLD VOLDOWN and POWER, when it boots up let go of POWER but keep holding VOLDOWN until you get to bootloader
Click to expand...
Click to collapse
Yeah, I've tried this about 100 times, and the only thing holding VOLDOWN does is occasionally interrupt the boot loop to send me to the black screen for 30 seconds before going back into the boot loop. I did find one thread where the poster was able to get into the bootloader after letting the phone sit overnight, so I'll try again tomorrow, but I'm not very hopeful.
nkk71 said:
then you need to have working "fastboot devices" (if you're on Win8.1, you probably need to use another computer with Win7 or use a Linux Live USB)
Click to expand...
Click to collapse
I'm on Win7, and "fastboot devices" was working the other day, so I know my drivers are all set up properly and functioning. The phone just isn't booting far enough to connect to the computer.
nkk71 said:
if you can't get to bootloader, then I don't think this is fixable, cause hboot is corrupt
Click to expand...
Click to collapse
So... should be safe to take it back to Verizon and ask for a replacement, since they won't be able to tell it's unlocked? >_>
brasstongue said:
Thanks for the reply.
Oh, I guess I forgot to make that a link... I had downloaded the only VZW one on this page but I'm not even sure why I bothered to mention it, as downloading it to my computer was the only thing I ever did with it; I was never able to get as far as flashing it to the phone, so it actually had nothing to do with the problem...
I was under the impression that Verizon was m7vzw, in which case yes, I was using the correct recovery (6.0.4.7 version listed next to "HTC One (Verizon)" on this page) and it was working just fine the first time I flashed it.
Yeah, I've tried this about 100 times, and the only thing holding VOLDOWN does is occasionally interrupt the boot loop to send me to the black screen for 30 seconds before going back into the boot loop. I did find one thread where the poster was able to get into the bootloader after letting the phone sit overnight, so I'll try again tomorrow, but I'm not very hopeful.
I'm on Win7, and "fastboot devices" was working the other day, so I know my drivers are all set up properly and functioning. The phone just isn't booting far enough to connect to the computer.
So... should be safe to take it back to Verizon and ask for a replacement, since they won't be able to tell it's unlocked? >_>
Click to expand...
Click to collapse
my bad, thought I read Sprint, not sure if Sprint and Verizon use same recovery, but that doesn't really matter now
unless you can get to bootloader, you're stuck, sorry.
If your pc does see "fastboot devices" then it must be in bootloader and flashing a ruu.zip (if available) could (that's a very big could) get the device working again.
Well, you'd think I'd have learned after the first two times - don't try to go back to stock. The last few times I was able to figure it out by mere chance, but now I think I may be doomed.
I'm trying to get a ROM, any ROM to load up on my HTC One M7. I've seriously browsed probably every XDA page concerning this kind of stuff, but to no avail can I find a solution. I've also downloaded probably about 10 different ROMs / RUUs to try and flash and now I can't even get as far as the install.
So far, I've gotten AndroidRev 71.1 and ViperOne to get to the final screen before getting a nice little script that says:
"set_metadata_recursive: some changes failed"
This has happened when I tried to sideload these ROMs in CWM.
Now, if I even try to sideload a ROM.zip it gets to appx. 82% and says:
* failed to write data 'protocol fault (no status)' *
I've been without a phone for a day and a half now, trying every solution offered. Am I out of luck?
Some info:
(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.26.502.12
(bootloader) version-misc: PVT SHIP S-ON
\\SN & IMEI\\
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4307mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
My provider is AT&T in the south eastern US. I've tried downloading RUU's and whatnot, but it doesn't work because CWM says it can't find /tmp/data/update.zip or something to that effect.
I'm giving up for the evening though. I would really appreciate any feedback. And yes, I've cleared the data / partitions / caches / Dalvik caches / etc. before doing this stuff and I'm not having any luck.
Does anyone know if HTC will fix this for a cost smaller than purchasing a new phone? If so, does anyone have any idea how much it costs? Honestly, I was trying to get back to stock so I could return it for a refurb since I have the purple tint camera issue.
Flash twrp 2.6.3.3. Android revolution needs that version
Sent from my HTC One using XDA Premium 4 mobile app
---------- Post added at 08:33 AM ---------- Previous post was at 08:29 AM ----------
And if sideload doesn't work try using adb push
Sent from my HTC One using XDA Premium 4 mobile app
glassjoe92 said:
Well, you'd think I'd have learned after the first two times - don't try to go back to stock. The last few times I was able to figure it out by mere chance, but now I think I may be doomed.
I'm trying to get a ROM, any ROM to load up on my HTC One M7. I've seriously browsed probably every XDA page concerning this kind of stuff, but to no avail can I find a solution. I've also downloaded probably about 10 different ROMs / RUUs to try and flash and now I can't even get as far as the install.
So far, I've gotten AndroidRev 71.1 and ViperOne to get to the final screen before getting a nice little script that says:
"set_metadata_recursive: some changes failed"
This has happened when I tried to sideload these ROMs in CWM.
Click to expand...
Click to collapse
have you checked the FAQ sticky thread, if it hasn't been updated/moved the info would still be in the last post
(please remember to never post questions in the sticky, if you have more questions post back here)
nateboi81 said:
Flash twrp 2.6.3.3. Android revolution needs that version
Sent from my HTC One using XDA Premium 4 mobile app
---------- Post added at 08:33 AM ---------- Previous post was at 08:29 AM ----------
And if sideload doesn't work try using adb push
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I managed to install that version of TWRP and I just sideloaded Android Revolution 71. I didn't get the errors I got in CWM, but it seems to still be stuck at the white splash screen with the HTC logo and red text at bottom. It doesn't progress into booting the OS.
After the supposedly successful install to AR 71, the screen went black. Should I have left it? When I pressed the home button, it vibrated. Maybe I should have given it a few more minutes, but I'm sideloading ViperOne right now. Will, update.
glassjoe92 said:
I managed to install that version of TWRP and I just sideloaded Android Revolution 71. I didn't get the errors I got in CWM, but it seems to still be stuck at the white splash screen with the HTC logo and red text at bottom. It doesn't progress into booting the OS.
After the supposedly successful install to AR 71, the screen went black. Should I have left it? When I pressed the home button, it vibrated. Maybe I should have given it a few more minutes, but I'm sideloading ViperOne right now. Will, update.
Click to expand...
Click to collapse
1- "After the supposedly successful install to AR 71, the screen went black" that happens sometimes, but shouldn't be a problem... my recent experience was if I wipe cache before starting the installer it doesn't happen.
If it does happen, (before booting the ROM), I reboot to bootloader using POWER + VOLDOWN, go back to recovery and wipe dalvik and cache, and then boot the system.
2- Did you select "Wipe userpartition" during installation? You have to.
3- How long did you wait? as mentioned my first boot (with wipe), took close to 20mins.
nkk71 said:
1- "After the supposedly successful install to AR 71, the screen went black" that happens sometimes, but shouldn't be a problem... my recent experience was if I wipe cache before starting the installer it doesn't happen.
If it does happen, (before booting the ROM), I reboot to bootloader using POWER + VOLDOWN, go back to recovery and wipe dalvik and cache, and then boot the system.
2- Did you select "Wipe userpartition" during installation? You have to.
3- How long did you wait? as mentioned my first boot (with wipe), took close to 20mins.
Click to expand...
Click to collapse
Okay, I decided to re-flash the AR 71 rom again. The screen is now black. Both caches were wiped prior to install, then I did select wipe userpartition during the install. I've waited for about 4 minutes now on this black screen. I'll give it a little bit more time to see if it works. Otherwise, I will restart and wipe the caches again.
From my experience before, when I boot and have to wait, I can at least get past the first splash screen with the HTC Logo and it usually just stalls on the rom's splash. Anyhow, I appreciate the info. This is farther than I've been able to make it and there's a slight shimmer of hope.
I'll post again once I've given it appx. 20 minutes / wiped caches in recovery and rebooted.
Also, just out of curiosity, I wanted to check my phone's MD5 sum, but I don't know how.
The rom's MD5 sum: CCC848CBF2B74C5FA33FD7E2269B0499
glassjoe92 said:
Okay, I decided to re-flash the AR 71 rom again. The screen is now black. Both caches were wiped prior to install, then I did select wipe userpartition during the install. I've waited for about 4 minutes now on this black screen. I'll give it a little bit more time to see if it works. Otherwise, I will restart and wipe the caches again.
From my experience before, when I boot and have to wait, I can at least get past the first splash screen with the HTC Logo and it usually just stalls on the rom's splash. Anyhow, I appreciate the info. This is farther than I've been able to make it and there's a slight shimmer of hope.
I'll post again once I've given it appx. 20 minutes / wiped caches in recovery and rebooted.
Also, just out of curiosity, I wanted to check my phone's MD5 sum, but I don't know how.
The rom's MD5 sum: CCC848CBF2B74C5FA33FD7E2269B0499
Click to expand...
Click to collapse
the black screen after a successful install has been an issue for quite a few, no need to wait, just force a reboot.
Force reboot: press and hold POWER + VOLDOWN (under a bright light, not kidding!!), after about 5 seconds or so buttons should start blinking, and after 30 seconds or so, the phone will reboot, let go of POWER, but keep holding VOLDOWN to get back to bootloader.
(you may need to try 2 or 3 times to get it right)
when the rom start's booting up, it should stay on the bootsplash for about 3~4 minutes then change screen brightness, and continue (since I use custom bootup animation, I don't know if the standard one comes up with "BeatsAudio" or not), but once it changes from bootsplash to bootanimation, i wait another 15 mins or so.
F*** YES. I pushed ViperOne to /sdcard/ and installed, works! At least it took me to the OS splash, which is great news. Thank the lord.
I really appreciate your help, both of you! I was so scared I was out a phone. Now I have it working, just in time for work tonight. Thanks again!
glassjoe92 said:
F*** YES. I pushed ViperOne to /sdcard/ and installed, works! At least it took me to the OS splash, which is great news. Thank the lord.
I really appreciate your help, both of you! I was so scared I was out a phone. Now I have it working, just in time for work tonight. Thanks again!
Click to expand...
Click to collapse
Cool :good: :good:
in case 2.6.3.3 is giving you headaches (black screen after install), you could always try 2.6.3.4... both are good for 4.4+ ROMs
(for some reason I'm on 2.6.3.3 and works fine 99% of the time, I only got that black screen after install once ... i think i was flashing too many recoveries at the time )
Hi,
My One M7 is stuck in a sort of boot loop. I've had boot loops on other phones when flashing etc. but this is different to any I've had before. My phone is rooted with unlocked bootloader but it is still running stock 4.3. I've never flashed a ROM on this phone. As stated, I've had boot loops on other phones where it tries to boot but doesn't fully boot before it restarts and I assume that's the same with a HTC One. The problem I have is when the phone has fully booted, it then restarts itself after around 10 seconds. It is as if the power button is stuck so it turns itself of then on again endlessly. I can fully press the power button and feel the little click so I assume it isn't stuck. I can't think of any reason it would be doing this. I assume it will just keep looping until it is out of battery.
Any help is appreciated, thanks,
Oli.
PS. I can get into recovery fine.
perceptic said:
Hi,
My One M7 is stuck in a sort of boot loop. I've had boot loops on other phones when flashing etc. but this is different to any I've had before. My phone is rooted with unlocked bootloader but it is still running stock 4.3. I've never flashed a ROM on this phone. As stated, I've had boot loops on other phones where it tries to boot but doesn't fully boot before it restarts and I assume that's the same with a HTC One. The problem I have is when the phone has fully booted, it then restarts itself after around 10 seconds. It is as if the power button is stuck so it turns itself of then on again endlessly. I can fully press the power button and feel the little click so I assume it isn't stuck. I can't think of any reason it would be doing this. I assume it will just keep looping until it is out of battery.
Any help is appreciated, thanks,
Oli.
PS. I can get into recovery fine.
Click to expand...
Click to collapse
I am having the same problem. Please keep this forum up to date because I would like a solution as well.
I would like to try a fcatory reset. But first I would like to find a way to back up all the files on my phone.
If anyone has an idea on how to back up all the stuff on my phone before i reset it, please let me know.
Bump!
I'm not sure if my issue is the same. But I have a very very similar one!
I am running stock kitkat, unlocked, rooted. Have been for a few months now without issue.
Yesterday my phone died, so i charged it while it was off (thought it might charge faster) for a couple hours. I figured it should be close to full but noticed it was only 20% charged. So when I turned it on, i get all the way booted, and can use the launcher for maybe 20-40 seconds before it reboots.
i do get a small amount of time to play on the phone each loop. ive noticed that im not getting or sending any sms (says 4 bars and 4g, but nothing going through).
i can also get into cwm recovery and fastboot so i have some options there.
what are my options? id like to not have to lose everything (i have titanium backups.....but they're on the sd card so a wipe would delete my backups)
I am in the same situation.
Unlocked and rooted
Stock HTC One Sense - no ROMs flashed
CWM Recovery
Kitkat 4.4.2
Sense 5.5
hboot 1.56
software number 4.18.502.7
kernel 3.4 10-ge12f77e
CID CW__001
AT&T
This all started for me back when I tried to restore a CWM nandroid backup. I was able to restore the backup but afterwards, the reboot loop started. If I factory reset the phone from recovery and cleared the cache and davlink I was able to reconfigure my phone and get it back up and running but if I reboot the phone, the reboot loop starts over again.
I can't even return it to stock since I can't S-Off using firewater or rumrunner or anything else in order to run RUU. So basically I am stuck with a phone that I have to reconfigure if I reboot it which causes the reboot loop to start.
Any help would be greatly appreciated!
perceptic said:
Hi,
My One M7 is stuck in a sort of boot loop. I've had boot loops on other phones when flashing etc. but this is different to any I've had before. My phone is rooted with unlocked bootloader but it is still running stock 4.3. I've never flashed a ROM on this phone. As stated, I've had boot loops on other phones where it tries to boot but doesn't fully boot before it restarts and I assume that's the same with a HTC One. The problem I have is when the phone has fully booted, it then restarts itself after around 10 seconds. It is as if the power button is stuck so it turns itself of then on again endlessly. I can fully press the power button and feel the little click so I assume it isn't stuck. I can't think of any reason it would be doing this. I assume it will just keep looping until it is out of battery.
Any help is appreciated, thanks,
Oli.
PS. I can get into recovery fine.
Click to expand...
Click to collapse
Try powering off from the bootloader or hold power + volume up till the phone shuts off. have you installed anything that would have maybe caused it ?
you could try and flash the stock recovery back to the phone and do a factory reset and then flash TWRP 2.6.3.3 and see how that goes
ibarazi said:
I am having the same problem. Please keep this forum up to date because I would like a solution as well.
I would like to try a fcatory reset. But first I would like to find a way to back up all the files on my phone.
If anyone has an idea on how to back up all the stuff on my phone before i reset it, please let me know.
Click to expand...
Click to collapse
read above ..no 2 phones are the same... I need more info like you version of recovery / rom / updates installed / android version / fastboot getvar all / bootloader screen shot
VM0824 said:
I'm not sure if my issue is the same. But I have a very very similar one!
I am running stock kitkat, unlocked, rooted. Have been for a few months now without issue.
Yesterday my phone died, so i charged it while it was off (thought it might charge faster) for a couple hours. I figured it should be close to full but noticed it was only 20% charged. So when I turned it on, i get all the way booted, and can use the launcher for maybe 20-40 seconds before it reboots.
i do get a small amount of time to play on the phone each loop. ive noticed that im not getting or sending any sms (says 4 bars and 4g, but nothing going through).
i can also get into cwm recovery and fastboot so i have some options there.
what are my options? id like to not have to lose everything (i have titanium backups.....but they're on the sd card so a wipe would delete my backups)
Click to expand...
Click to collapse
read above and list the same things I ask them
Houtex2k said:
I am in the same situation.
Unlocked and rooted
Stock HTC One Sense - no ROMs flashed
CWM Recovery
Kitkat 4.4.2
Sense 5.5
hboot 1.56
software number 4.18.502.7
kernel 3.4 10-ge12f77e
CID CW__001
AT&T
This all started for me back when I tried to restore a CWM nandroid backup. I was able to restore the backup but afterwards, the reboot loop started. If I factory reset the phone from recovery and cleared the cache and davlink I was able to reconfigure my phone and get it back up and running but if I reboot the phone, the reboot loop starts over again.
I can't even return it to stock since I can't S-Off using firewater or rumrunner or anything else in order to run RUU. So basically I am stuck with a phone that I have to reconfigure if I reboot it which causes the reboot loop to start.
Any help would be greatly appreciated!
Click to expand...
Click to collapse
same here .. read above and list all the things I ask above
you can also try my guru reset posted here >> http://forum.xda-developers.com/showthread.php?t=2775650
Well my One just fixed itself . I was JUST about to do a factory reset and, when my phone turned itself on, I heard loads of buzzing. Well, turned out it was all my notifications and as VM0824 said, signal wasn't working. I waited a couple of minutes then sighed hugely in relief haha.
Good luck to everyone else in sorting the problem out :good:
Oli.
Android 4.4.2
HTC Sense 5.5
Software number 4.18.502.7
HTC SDK API Level 5.68
Kernel 3.4.10-ge12f77e
I used cwm to factory reset. It seems to work fine now. BUT, if I restore all system and user app + data from titanium backup, then the issues comes back.
So I did another factory reset, and this time only installed missing app+data. It will take me some time to get my stuff back the way it was, but its working.
Now I have a new symptom though, apparently I have space issues???
1. Using Lucky Patcher, I ran into an issue trying to patch titanium backup. As it was doing the step involving creating the .odex, it told me it could not create the .odex or something like that. As if there was no room. I deleted some stuff from my SD card (even though it indicated 18gb free space in the data manager) and it worked.
2. I installed dropbox as my first thing since the reset since I store some apps there. I have an old version of swype (the new ones have been laggy) that I tried to install and it says "storage full or unavailable" when I click it in Dropbox.
Now the data manager indicates i have more than 18gb left....yet i cant find room for swype? I wonder if my storage is going bad? i imagine if there's write contention or i lost access to certain storage, that could cause a crash and reboot (hence the boot loop).
so how do i diagnose if there is an issue with my storage?
VM0824 said:
Android 4.4.2
HTC Sense 5.5
Software number 4.18.502.7
HTC SDK API Level 5.68
Kernel 3.4.10-ge12f77e
so how do i diagnose if there is an issue with my storage?
Click to expand...
Click to collapse
so your using a patched version of titanium and your trying to restore your data with it? Dude pay for the app if it's that useful to you... piracy is not acceptable here, look for help elseware.
Info from Recovery and Fastboot Getvar all
**** TAMPERED ****
**** ULOCKED ****
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-4T.24.3218.09
OpenDSP-v32.120.274.0909
OS-4.18.502.7
eMMC-boot 2048MB
Jan 28 2014,09:32:41.0
C:\ADB>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT**********
(bootloader) imei: *************
(bootloader) meid :************
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3915mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.048s
recovery-clockwork-touch-6.0.4.8-m7
Now that I've done the fastboot getvar all command and rebooted the phone I am stuck in a reboot loop and will have to factory reset and start over. Any help would be appreciated and thanks for your time.
i have the same problem with my one , first in android 4.3 starting auto-restart and then after a flashing 4.4.2(4.19.401.9) the signal is out of range and imei and base band are unkonwn
i update to 4.19.401.11 and didn't change after all
i really confused , please help me , my hboot is 1.56 and i didn't s-off or unlock yet
I did a factory reset and it seemed to fix the problem with one hitch. you can never let the phone die.
i have had this running for a few weeks now and as long as i make sure the battery doesnt die, then the phone wont start boot looping. last night it died -_-
i couldnt even get a light to come on and had to use a trick from another post about holding power + volume + bright light on sensor to even get it to charge. but now that its charging and I turned it on, boot loop again.
i guess ill do another factory reset and be more careful to never let the battery die......until im eligible for an upgrade lol.
Dear xdadevelopers members,
I have anHTC One m7 (GSM Version Unlocked without Providerlock)
It is rootet and Bootloader unlocked and at the moment is TWRP v.2.8.1.0 Recovery installed (before it wasCWM Touch).
It is the Stock ROM it got with which I bought it, not completely ... before rooting I did one OTA update . So it is now 4.2.2 with normal sense edition.
I am trying to resolve the problem, but with no success. So the phone starts normally until I have to enter the PIN, if I'm quick enough I can enter it successfully. Then everything looks quite normal, then only after about 5-10 seconds it goes black and reboots again, this happens all the time.
Booting into Save Mode has the exact same issue!
Recovery is working normally.
Does anyone have any idea why this might be and how I could fix it?
My guess is that it has occurred because I installed a root uninstaller tool to uninstall/disabled some of HTC's own apps, so maybe I have deleted too many of them. But that's a long time ago, it worked for weeks even after the erase with the tool (I did never a restart after), only when I then made a reboot weeks later the problem occured.
Saturos said:
Dear xdadevelopers members,
I have anHTC One m7 (GSM Version Unlocked without Providerlock)
It is rootet and Bootloader unlocked and at the moment is TWRP v.2.8.1.0 Recovery installed (before it wasCWM Touch).
It is the Stock ROM it got with which I bought it, not completely ... before rooting I did one OTA update . So it is now 4.2.2 with normal sense edition.
I am trying to resolve the problem, but with no success. So the phone starts normally until I have to enter the PIN, if I'm quick enough I can enter it successfully. Then everything looks quite normal, then only after about 5-10 seconds it goes black and reboots again, this happens all the time.
Booting into Save Mode has the exact same issue!
Recovery is working normally.
Does anyone have any idea why this might be and how I could fix it?
My guess is that it has occurred because I installed a root uninstaller tool to uninstall/disabled some of HTC's own apps, so maybe I have deleted too many of them. But that's a long time ago, it worked for weeks even after the erase with the tool (I did never a restart after), only when I then made a reboot weeks later the problem occured.
Click to expand...
Click to collapse
First thing you should do is a factory reset and see if its still rebooting
then return to return to 100% stock
what is your fastboot getvar all?
alray said:
First thing you should do is a factory reset and see if its still rebooting
then return to return to 100% stock
what is your fastboot getvar all?
Click to expand...
Click to collapse
THanks for your help. I tried a few things now in the 10 sec I had , moved the phone to air plane mode rebooted again and since then its working normally again. I even diabled airplane mode and everything is up to normal again its running like a charm since 30 minutes. I Also got a HTC message that the phone was recovered from a problem and it would like me to send an error report (I did). But I am a bit afraid now to reboot it again, so I think I can not make the fastboot getvar all command or can I place this command without restarting and booting into the bootloader?
Saturos said:
THanks for your help. I tried a few things now in the 10 sec I had , moved the phone to air plane mode rebooted again and since then its working normally again. I even diabled airplane mode and everything is up to normal again its running like a charm since 30 minutes. I Also got a HTC message that the phone was recovered from a problem and it would like me to send an error report (I did). But I am a bit afraid now to reboot it again, so I think I can not make the fastboot getvar all command or can I place this command without restarting and booting into the bootloader?
Click to expand...
Click to collapse
this command must be entered when in bootloader/fastboot mode