When I reboot the phone it hangs on the splash screen. So then I go into twrp and do a few things but still cant get back. I end up doing a full wipe and install my backup. Backup installs but upon reboot, it bootloops between the splash screen and trying to get to recovery. I see the blue twrp page for a sec and then back to splash screen and so on and on. Then I cant access twrp at all. I can only get into bootloader.
This happens no matter what ROM I use. So then I have to use fastboot to install twrp. Then use otg in twrp to install a new ROM. The new ROM installs fine and everything functions normal. But if I were to reboot and especially when the phone is left in fastboot mode, the whole cycle starts again.
My phone was fine a few days ago. It was stock running kitkat and not rooted never did anything to it. Then the phone turned off and got stuck at the splash screen. I could not do anything to recover the phone. I ended up being able to root so I did and here I am
Does this seem to be a hardware problem? That's the only thing I can think of. Everything gets wiped on the phone and loaded from a jump drive.
Which twrp are you using?
Sent from my One using XDA Premium 4 mobile app
Zandoz said:
Which twrp are you using?
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
2.6.3.3
For kitkat it is recommended to have the latest twrp. 2.7
Sent from my One using XDA Premium 4 mobile app
Does it really make a difference? I think I have other problems
Sent from my myTouch 4G using xda app-developers app
Post a fastboot getvar all. Maybe your backup is at fault also post a screen shot of your bootloader
Sent from my GT-I9505 using XDA Premium 4 mobile app
dpshptl said:
Does it really make a difference? I think I have other problems
Click to expand...
Click to collapse
TWRP 2.6.3.3 is fine for 4.4 ROMs.
dpshptl said:
When I reboot the phone it hangs on the splash screen. So then I go into twrp and do a few things but still cant get back. I end up doing a full wipe and install my backup. Backup installs but upon reboot, it bootloops between the splash screen and trying to get to recovery. I see the blue twrp page for a sec and then back to splash screen and so on and on. Then I cant access twrp at all. I can only get into bootloader.
This happens no matter what ROM I use. So then I have to use fastboot to install twrp. Then use otg in twrp to install a new ROM. The new ROM installs fine and everything functions normal. But if I were to reboot and especially when the phone is left in fastboot mode, the whole cycle starts again.
My phone was fine a few days ago. It was stock running kitkat and not rooted never did anything to it. Then the phone turned off and got stuck at the splash screen. I could not do anything to recover the phone. I ended up being able to root so I did and here I am
Does this seem to be a hardware problem? That's the only thing I can think of. Everything gets wiped on the phone and loaded from a jump drive.
Click to expand...
Click to collapse
Could very well be (very likely be a hardware problem), can you post a "fastboot getvar all" (excluding IMEI and s/n), maybe there's an RUU for you that could fix it if it's software related.
nkk71 said:
TWRP 2.6.3.3 is fine for 4.4 ROMs.
Could very well be (very likely be a hardware problem), can you post a "fastboot getvar all" (excluding IMEI and s/n), maybe there's an RUU for you that could fix it if it's software related.
Click to expand...
Click to collapse
Here is the info but there is no more back I deleted it. There is nothing on the phone right now. I did relock my bootloader but I can unlock it if need be.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.24.3263.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.531.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(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-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
Hi Guys,
Hope that anyone can help me with the following:
I normally have Openrecovery-twrp-2.6.3.3-m7 running on my M7.
However, with the new software update of 5.11.1540.9 pushed out, I normally go back to original recover, then update my software by downloading it an installing on the phone.
A couple of months ago I changed my version, originally an ATT phone, to I think a European or WWE version. I am not sure anymore.
Anyway, when I try to flash the original recovery ecovery_Cingular_US_3.17.502.3.img back and reboot in to recovery I get a black screen and eventually a phone icon with exclamation mark.
After holding the power button for a while, I can reboot and get back in the phone or restore TWRP.
My question is, does anyone know how to get the original recovery working again so that I can run the update.
This is the info of the bootloader:
(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.1540.9
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 111111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4263mV
(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
I rather do not wipe the whole device if I don't have to. Before I changed the firmware to European or WWE I was able to restore the original bootloader at leisure. So I think it would be best to go back to the correct country firmware, or find a recovery file that does work with my current firmware.
If I can install the latest Developer Edition ROM with TWRP, and have to wipe, that is fine. I don't want to risk bricking my phone with doing all kind of updates. Have done so many and it is still working, would hope to keep it that way
Any help appreciated.
I thought all you needed to do was re-lock the bootloader, then run the correct RUU file for your phone.
I do not remember having to flash back to stock recovery when I ran RUU for the latest update - I just relocked the bootloader. After the RUU is run, you will be back on stock recovery
mike-y said:
I thought all you needed to do was re-lock the bootloader, then run the correct RUU file for your phone.
I do not remember having to flash back to stock recovery when I ran RUU for the latest update - I just relocked the bootloader. After the RUU is run, you will be back on stock recovery
Click to expand...
Click to collapse
Well, last time it worked for me when I had the Dev edition. My phone was unlocked with S-On, and I had TWRP for recovery.
I remember receiving the OTA, installing it and then seeing the message in TWRP that it couldn't install.
I then set the Recovery_Cingular_US_3.17.502.3.img for recovery and I was able to install the OTA.
After that I went back to TWRP.
Couple of months ago I set my CID to 11111111 and S-off and I installed, I believe a european version or a WWE version (not sure anymore what i did ) to get a radio that might unlock 4G here in Australia (which failed cause of hardware restrictions of bands).
Anyway, my phone works fine and I received the OTA but I can't repeat the back to stock recovery trick cause after flashing the Recovery_Cingular_US_3.17.502.3.img it doesnt enter recovery. Probably something to do with my WWE or Euro firmware?
What does relock mean in this case.
I also am at loss at what the correct RUU is. Is RUU firmware, or a whole complete ROM?
Can you see from my bootloader info what version I have and should consider?
I am just a bit confused with all the terms and was quite into it a couple of months ago, but now its a blur.
You don't need relock boot loader
When you boot in recovery got exclamation mark press volume up for4-5 sec then press power upto home back light blinks leave power button you got recovery with blue options
from HTC One
yatindroid said:
You don't need relock boot loader
When you boot in recovery got exclamation mark press volume up for4-5 sec then press power upto home back light blinks leave power button you got recovery with blue options
from HTC One
Click to expand...
Click to collapse
Well I tried your suggestion but it doesnt work. After I hold the power button when seeing the exclamation mark, the phone finally reboots. It tried to install the OTA this way, but it doesnt work.
I think the current recovery:Recovery_Cingular_US_3.17.502.3.img doesnt match my current firmware of something like that.
Any other suggestions?
Can I just install a fresh ROM with the latest version, not sure where to get it from.
Not really sure what to do, I tried another recovery but after choosing to install the OTA, and reboot, I see progress bar which ends up in red triangle.
Tried to lock bootloader but then of course I can go back to standard recovery using TWRP.
I just tried to install again and when progress bar appeared I hit volume up and then power button. Now I see status updates of the installation.
If fails while verifying the current system:
"/system/lib/libcryptox.so" has unexpected contents
Installation aborted.
mattileblanc said:
Not really sure what to do, I tried another recovery but after choosing to install the OTA, and reboot, I see progress bar which ends up in red triangle.
Tried to lock bootloader but then of course I can go back to standard recovery using TWRP.
I just tried to install again and when progress bar appeared I hit volume up and then power button. Now I see status updates of the installation.
If fails while verifying the current system:
"/system/lib/libcryptox.so" has unexpected contents
Installation aborted.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2791123
from HTC One
I wanted to change my rom on my HTC One. I first fastbooted a new recovery img TWRP.
On the TWRP recovery screen, I decided to wipe all of my data on my phone out with the advanced settings of wipe on TWRP..I still don't why I did that. The data isn't the problem however, I then decided to go back to Clockwork recovery and use adb to push a stock rom to fix my problem.
However after flashing the Stock rom onto my phone, the phone is stuck on the boot loading screen. My HTC One is S-On so I used a special rom that works for S-On HTC One phones. However the stock rom doesn't seem to work.
I'm stuck here not knowing on what to do next. I've tried everything...different roms etc.
Any Ideas?
HabitRPG said:
I wanted to change my rom on my HTC One. I first fastbooted a new recovery img TWRP.
On the TWRP recovery screen, I decided to wipe all of my data on my phone out with the advanced settings of wipe on TWRP..I still don't why I did that. The data isn't the problem however, I then decided to go back to Clockwork recovery and use adb to push a stock rom to fix my problem.
However after flashing the Stock rom onto my phone, the phone is stuck on the boot loading screen. My HTC One is S-On so I used a special rom that works for S-On HTC One phones. However the stock rom doesn't seem to work.
I'm stuck here not knowing on what to do next. I've tried everything...different roms etc.
Any Ideas?
Click to expand...
Click to collapse
oh dear, got yourself into a bit of a mess there.
first thing is to get your phone back to the bootloader, so hold down the power button and the volume down together, DO NOT LET GO, the lights on the bottom will flash 10-15 times, when they stop flashing, release the power button only, continue to hold down the volume down, it will now enter the bootloader.
Post your fastboot getvar all please, WITHOUT IMEI & SERIAL NUMBER.
also, please provide some links to the special :fingers-crossed: stock rom you flashed ? all rom's for your model work, s-on or s-off.
Seanie280672 said:
oh dear, got yourself into a bit of a mess there.
first thing is to get your phone back to the bootloader, so hold down the power button and the volume down together, DO NOT LET GO, the lights on the bottom will flash 10-15 times, when they stop flashing, release the power button only, continue to hold down the volume down, it will now enter the bootloader.
Post your fastboot getvar all please, WITHOUT IMEI & SERIAL NUMBER.
also, please provide some links to the special :fingers-crossed: stock rom you flashed ? all rom's for your model work, s-on or s-off.
Click to expand...
Click to collapse
C:\AndroidSDK>fastboot getvar all
(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3677mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
I can't post links because of my post count however it was a Stock Rom guru reset
Stock ROM version for these types:
modelid: PN0710000
cid: HTC__001, HTC__E11
HTC__102, HTC__203
HTC__405, HTC__Y13
HTC__304, HTC__032
HTC__A07, HTC__J15
HTC__016
HabitRPG said:
C:\AndroidSDK>fastboot getvar all
(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3677mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
I can't post links because of my post count however it was a Stock Rom guru reset
Stock ROM version for these types:
modelid: PN0710000
cid: HTC__001, HTC__E11
HTC__102, HTC__203
HTC__405, HTC__Y13
HTC__304, HTC__032
HTC__A07, HTC__J15
HTC__016
Click to expand...
Click to collapse
ok, guru reset works fine, recovery is the problem, you need to use twrp 2.6.3.3, push the zip again and install, select wipe data, install stock recovery and install stock radio.
also check the MD5 and file size before pushing the zip, the site has some issues with the files at the moment.
however, once you have done that, you have a good HBOOT there, so if you want s-off on your phone, now is the time to do it after you've got that guru reset installed, before any OTA's, try rumrunner to get s-off.
Seanie280672 said:
ok, guru reset works fine, recovery is the problem, you need to use twrp 2.6.3.3, push the zip again and install, select wipe data, install stock recovery and install stock radio.
also check the MD5 and file size before pushing the zip, the site has some issues with the files at the moment.
however, once you have done that, you have a good HBOOT there, so if you want s-off on your phone, now is the time to do it after you've got that guru reset installed, before any OTA's, try rumrunner to get s-off.
Click to expand...
Click to collapse
i flashed TWRP 2.6.3.3
however i can't adb the rom
C:\AndroidSDK>adb sideload Guru_Reset_M7_3.62.401.1.zip
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
* failed to write data 'protocol fault (no status)' *
when i used Clockwork i used
adb usb
adb push filename.zip /sdcard/obb
which put the file onto the sdcard and i was able to flash the zip file
however this doesn't work with TWRP because it doesn't show me the obb file on the SD card and just comes up blank.
HabitRPG said:
i flashed TWRP 2.6.3.3
however i can't adb the rom
C:\AndroidSDK>adb sideload Guru_Reset_M7_3.62.401.1.zip
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
* failed to write data 'protocol fault (no status)' *
when i used Clockwork i used
adb usb
adb push filename.zip /sdcard/obb
which put the file onto the sdcard and i was able to flash the zip file
however this doesn't work with TWRP because it doesn't show me the obb file on the SD card and just comes up blank.
Click to expand...
Click to collapse
from the main screen only inside TWRP recovery, no sub menus, you seem quite experienced, but obviously the zip must be inside your adb and fastboot folder, it will appear unresponsive, takes about 5 mins to push, but your cmd window will let you know when its done.
Code:
adb push Guru_Reset_M7_3.62.401.1.zip /sdcard/
Seanie280672 said:
from the main screen only inside TWRP recovery, no sub menus, you seem quite experienced, but obviously the zip must be inside your adb and fastboot folder, it will appear unresponsive, takes about 5 mins to push, but your cmd window will let you know when its done.
Code:
adb push Guru_Reset_M7_3.62.401.1.zip /sdcard/
Click to expand...
Click to collapse
same problem is still occurring, I've installed the new zip file with TWRP, I wiped, rooted and installed radio etc. Still stuck on the HTC one loading screen.
I've check the MD5 and it matched however instead of 1.11GB as stated on the site its 1.12GB with the file being 1,176,264. I don't know if that means anything.
HabitRPG said:
same problem is still occurring, I've installed the new zip file with TWRP, I wiped, rooted and installed radio etc. Still stuck on the HTC one loading screen.
I've check the MD5 and it matched however instead of 1.11GB as stated on the site its 1.12GB with the file being 1,176,264. I don't know if that means anything.
Click to expand...
Click to collapse
that's strange, Try these commands:
Code:
fastboot erase cache
fastboot reboot
Seanie280672 said:
that's strange, Try these commands:
Code:
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
Sadly nothing has changed. I used erase cache after installing the recovery, if that means anything.
HabitRPG said:
Sadly nothing has changed. I used erase cache after installing the recovery, if that means anything.
Click to expand...
Click to collapse
just wondering:
1- is the installation successful
2- how long are you waiting for the phone to boot up?
nkk71 said:
just wondering:
1- is the installation successful
2- how long are you waiting for the phone to boot up?
Click to expand...
Click to collapse
1. yes the installation is successful
2.It takes the same amount of time as a HTC One usually takes however it hangs on the HTC one loading screen after the green HTC logo screen
HabitRPG said:
1. yes the installation is successful
2.It takes the same amount of time as a HTC One usually takes however it hangs on the HTC one loading screen after the green HTC logo screen
Click to expand...
Click to collapse
I had hoped you would say something like __ minutes, because i don't know how long "same amount of time" actually is.
When I do a clean install of a 4.4 ROM, it takes close to 20 minutes for it to boot up properly, but when I just reboot the phone, it's done in less than 2 minutes.... so i don't know which one of those would be the "same amount of time".
nkk71 said:
I had hoped you would say something like __ minutes, because i don't know how long "same amount of time" actually is.
When I do a clean install of a 4.4 ROM, it takes close to 20 minutes for it to boot up properly, but when I just reboot the phone, it's done in less than 2 minutes.... so i don't know which one of those would be the "same amount of time".
Click to expand...
Click to collapse
when i boot up the phone it takes 30 seconds for it to go on the HTC one beats audio screen, then it hangs there. However I've never left it for more than 5 minutes as I have never experienced any phone taking that long to load. I'll leave it on this time for 30 minutes and see if that is any change
HabitRPG said:
when i boot up the phone it takes 30 seconds for it to go on the HTC one beats audio screen, then it hangs there. However I've never left it for more than 5 minutes as I have never experienced any phone taking that long to load. I'll leave it on this time for 30 minutes and see if that is any change
Click to expand...
Click to collapse
small recommendation: reflash the ROM first (including wipe), then let it boot up, if you check the Frequently Asked Question sticky page 3
you'll see my personal opinion about bootup time (and other things)
This is very strange as ive used that guru-reset file myself, and its never taken much longer than 5 to 10 mins to boot, however, if its getting past the splash screen, then onto the boot screen, then its defiantly doing something, usually a boot loop is a phone stuck at the splash screen or a restart whilst booting.
it's been 20 minutes and it's still on the boot screen, so not sure what to do next. if this helps at all, I was tyring to download Android HD then i found out you needed S-Off, by then Android HD ruined my old rom so I used guru reset which worked. I then was going to do the S-Off procedure. This is when i went on TWRP and wiped all of my settings by mistake...still don't know how I did that. So i know it's not the file but my phone
Seanie280672 said:
This is very strange as ive used that guru-reset file myself, and its never taken much longer than 5 to 10 mins to boot, however, if its getting past the splash screen, then onto the boot screen, then its defiantly doing something, usually a boot loop is a phone stuck at the splash screen or a restart whilst booting.
Click to expand...
Click to collapse
Once you're past the bootsplash, it should be OK, but "5 minutes" has become a relative term.... It's usually the 4.4+ ROMs that take a lot longer to load than the previous ones, but I have seen someone post "I waited 10 minutes" and the two posts were 3 minutes apart (after he waited it worked fine)... so a little exaggeration about the close to 20 minutes is just trying to encourage a little patience
---------- Post added at 09:52 PM ---------- Previous post was at 09:46 PM ----------
HabitRPG said:
it's been 20 minutes and it's still on the boot screen, so not sure what to do next. if this helps at all, I was tyring to download Android HD then i found out you needed S-Off, by then Android HD ruined my old rom so I used guru reset which worked. I then was going to do the S-Off procedure. This is when i went on TWRP and wiped all of my settings by mistake...still don't know how I did that. So i know it's not the file but my phone
Click to expand...
Click to collapse
okay, that's too long, check the Frequently Asked Question sticky page 3
iirc only GPE ROMs need S-Off, all the others should be fine; make sure you're using a recovery (and ROM) meant for m7_u / ul
HabitRPG said:
it's been 20 minutes and it's still on the boot screen, so not sure what to do next. if this helps at all, I was tyring to download Android HD then i found out you needed S-Off, by then Android HD ruined my old rom so I used guru reset which worked. I then was going to do the S-Off procedure. This is when i went on TWRP and wiped all of my settings by mistake...still don't know how I did that. So i know it's not the file but my phone
Click to expand...
Click to collapse
This may sound crazy, but when you flash the guru reset file, and booting it, your phone needs to be unplugged from the computer, I only discovered this problem myself a few days ago, I couldn't figure out why it was stuck on the splash screen, pulled the usb cable and it fired straight up (try this first before below comment)
Download this one mate, it will work fine, again use twrp 2.6.3.3 I know there are newer versions on the TeamWin site, but this version is proven to be the most compatible with roms, this rom is stock looks and stock features, you should get S-OFF easily with it using rumrunner, and once your S-OFF, you can just use an RUU to get to fully stock if that's what you want.
again, download the zip and just push it to your sdcard and install
http://www.androidrevolution.org/downloader/download.php?file=Android_Revolution_HD-One_31.6.zip
Seanie280672 said:
This may sound crazy, but when you flash the guru reset file, and booting it, your phone needs to be unplugged from the computer, I only discovered this problem myself a few days ago, I couldn't figure out why it was stuck on the splash screen, pulled the usb cable and it fired straight up (try this first before below comment)
Download this one mate, it will work fine, again use twrp 2.6.3.3 I know there are newer versions on the TeamWin site, but this version is proven to be the most compatible with roms, this rom is stock looks and stock features, you should get S-OFF easily with it using rumrunner, and once your S-OFF, you can just use an RUU to get to fully stock if that's what you want.
again, download the zip and just push it to your sdcard and install
http://www.androidrevolution.org/downloader/download.php?file=Android_Revolution_HD-One_31.6.zip
Click to expand...
Click to collapse
Tried both methods and still the same problem occurs.
HabitRPG said:
Tried both methods and still the same problem occurs.
Click to expand...
Click to collapse
So you've tried downloading and flashing the ARHD 31.6 rom too and that did the same thing ?
Hello guys,
I have a weird problem that happened not to my phone but a friend of mine... I'll try to make the details as good as possible but it may be different since I did not own the phone, but as I said, a friend did.
She says it was Sense6.0 4.4.2 and that one day the phone booted, showed the HTC logo like 3 times (between bootloop) and it went down (power off), so she charged it for like 1 days but it didn't turn the display on... Now, it had pattern lock so getting adb to work was a complete PITA but we figured that the phone wasn't dead when we tried to call her and she swept the screen to answer and she did, so, after a lot of pain, we managed to unlock it blindly and accept the recogniztion so we could have adb...
Now, we rebooted into fastboot, unlocked bootloader (which wiped the system to factory reset) and installed a custom kernel/recovery (via fastboot)
The phone has 1.57 HBOOT and I understand firewater works, but here is the major problem: I don't have access to Wireless because I cant see a damn thing so were screwed there... 3G connection doesn't work at all and I go and ping and it says failed...
ALTHOUGH I tried rumrunner (before I knew HBOOT was 1.57) and somehow it rebooted and the screen turned on so I figured the screen wasnt dead, but as soon as it finished booting, the screen went off again forever...
The phone has CID: HTC__332 (Latin American variant) so I cant find a suitable RUU so I can flash without S-OFF
I am really screwed but maybe anyone here with some experience can shed a light here and save an M7
PD: I have working adb and fastboot but just through command line
Poesini said:
Hello guys,
I have a weird problem that happened not to my phone but a friend of mine... I'll try to make the details as good as possible but it may be different since I did not own the phone, but as I said, a friend did.
She says it was Sense6.0 4.4.2 and that one day the phone booted, showed the HTC logo like 3 times (between bootloop) and it went down (power off), so she charged it for like 1 days but it didn't turn the display on... Now, it had pattern lock so getting adb to work was a complete PITA but we figured that the phone wasn't dead when we tried to call her and she swept the screen to answer and she did, so, after a lot of pain, we managed to unlock it blindly and accept the recogniztion so we could have adb...
Now, we rebooted into fastboot, unlocked bootloader (which wiped the system to factory reset) and installed a custom kernel/recovery (via fastboot)
The phone has 1.57 HBOOT and I understand firewater works, but here is the major problem: I don't have access to Wireless because I cant see a damn thing so were screwed there... 3G connection doesn't work at all and I go and ping and it says failed...
ALTHOUGH I tried rumrunner (before I knew HBOOT was 1.57) and somehow it rebooted and the screen turned on so I figured the screen wasnt dead, but as soon as it finished booting, the screen went off again forever...
The phone has CID: HTC__332 (Latin American variant) so I cant find a suitable RUU so I can flash without S-OFF
I am really screwed but maybe anyone here with some experience can shed a light here and save an M7
PD: I have working adb and fastboot but just through command line
Click to expand...
Click to collapse
So does the screen come on when the phone is booted to the bootloader and recovery?
Can you post fastboot getvar all?
Code:
fastboot getvar all
Post the output here but remove imei and serial numbers before posting.
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Danny201281 said:
So does the screen come on when the phone is booted to the bootloader and recovery?
Can you post fastboot getvar all?
Code:
fastboot getvar all
Post the output here but remove imei and serial numbers before posting.
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
No, the screen never turn on... It did only when trying the first time rumrunner but not anymore (But so, I know the screen isn't dead)
Here is the getvar all
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.15.599.101
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__332
(bootloader) battery-status: good
(bootloader) battery-voltage: 3854mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
Poesini said:
No, the screen never turn on... It did only when trying the first time rumrunner but not anymore (But so, I know the screen isn't dead)
Here is the getvar all
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.15.599.101
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__332
(bootloader) battery-status: good
(bootloader) battery-voltage: 3854mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
Click to expand...
Click to collapse
It does sound like a dead LCD to me. Weird how it came on once while running rumrunner though. Try powering off the device then hold a it under a bright light hold power on + volume down for 90+ seconds. Maybe a fault with proximity sensor.
There is no ruu you can use while s-on and I can't even find a firmware you can try to flash. So if that doesn't work I don't know what else to try
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Danny201281 said:
It does sound like a dead LCD to me. Weird how it came on once while running rumrunner though. Try powering off the device then hold a it under a bright light hold power on + volume down for 90+ seconds. Maybe a fault with proximity sensor.
There is no ruu you can use while s-on and I can't even find a firmware you can try to flash. So if that doesn't work I don't know what else to try
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
Holding the device under a bright light seems to power on the device SOMETIMES with the HTC logo visible and then it gets past that (with a little backlight movement meanwhile -dimmer- or -brighter-) and then back to desktop with no light
Is there any way to disable the proximity sensor or maybe flash a custom ROM via adb commands to flash it into recovery inside OS (TWRP 2.8.1.0 right now) or something?
Poesini said:
Holding the device under a bright light seems to power on the device SOMETIMES with the HTC logo visible and then it gets past that (with a little backlight movement meanwhile -dimmer- or -brighter-) and then back to desktop with no light
Is there any way to disable the proximity sensor or maybe flash a custom ROM via adb commands to flash it into recovery inside OS (TWRP 2.8.1.0 right now) or something?
Click to expand...
Click to collapse
Well that's promising. You can push a Rom with adb but you need the recovery menu to install it which may prove difficult if you can't see it.
To push the Rom put it in your fastboot folder and rename it rom.zip. connect the usb with the phone for adb and type in the command window
Code:
adb push rom.zip /sdcard
The command window will appear unresponsive until the push completes.
You may be better to use TWRP 2.6.3.3 to avoid install problems. Remember to
Code:
fastboot erase cache
when you flash a new recovery.
And keep using the bright light power on trick. May be give the sensors a clean (top left of the phone).
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Danny201281 said:
Well that's promising. You can push a Rom with adb but you need the recovery menu to install it which may prove difficult if you can't see it.
To push the Rom put it in your fastboot folder and rename it rom.zip. connect the usb with the phone for adb and type in the command window
Code:
adb push rom.zip /sdcard
The command window will appear unresponsive until the push completes.
You may be better to use TWRP 2.6.3.3 to avoid install problems. Remember to
Code:
fastboot erase cache
when you flash a new recovery.
And keep using the bright light power on trick. May be give the sensors a clean (top left of the phone).
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
I know my ways to push files via ADB, but I am saying like SuperSU does when it asks if you want to update it via TWRP option where it reboots directly to recovery and flashes a zip without you doing anything
I could push many files via ADB, but I couldn't flash them correctly (and I don't want to screw this phone) without seeing the screen
Poesini said:
I know my ways to push files via ADB, but I am saying like SuperSU does when it asks if you want to update it via TWRP option where it reboots directly to recovery and flashes a zip without you doing anything
I could push many files via ADB, but I couldn't flash them correctly (and I don't want to screw this phone) without seeing the screen
Click to expand...
Click to collapse
Flash twrp 2.6.3.3 newer versions of twrp can be temperamental and probably why your having trouble flashing roms
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
---------- Post added at 07:26 PM ---------- Previous post was at 07:07 PM ----------
Try the bright light trick again but this time power off the device. Hold the sensors close to the light
Hold volume up and down +power for 60 secs the phone will bootloop while your holding the buttons. Hopefully that will be enough to reset the sensor. :fingers-crossed:
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Hi you all,
So to start things off i might say i tried alot of things to revive my htc one.
What happenend?
I wanted to give my htc one some new life so I thought lets factory reset it. All worked well but then the horror just began. My One began rebooting and rebooting itself over and over. So what i did next was enabled flight mode throught the power button and restarted the phone. So from then on it was running for about 30 seconds untill it starts rebooting again.
So what I did is unlock the phone and tried several Custom Roms. The only ones working are old cm11 roms, but I can not get S-Off to reflash the firmware because I am stuck with an eMMC 9001xxxxx... chip, so I guess bad luck for me.
So now my phone will not detect ANY SIM Card and will not show any imei number or baseband in the os. In the bootloader however they are still there, both of them.
RUU's will not work for me as I am S-ON and stuck on hboot 1.57
SunShine is not working either as my phone shuts down after aprox. 30 seconds on sense rom.
Firewater is not working either as it has an 9001.... eMMC chip.
my getvar stats:
PHP:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3972mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
So my question is are there still any suggestions for me, that I didn't do or just overlooked?
So I would appreciate anything, before tearing it apart..
Cheers
shieldeverything said:
Hi you all,
So to start things off i might say i tried alot of things to revive my htc one.
What happenend?
I wanted to give my htc one some new life so I thought lets factory reset it. All worked well but then the horror just began. My One began rebooting and rebooting itself over and over. So what i did next was enabled flight mode throught the power button and restarted the phone. So from then on it was running for about 30 seconds untill it starts rebooting again.
So what I did is unlock the phone and tried several Custom Roms. The only ones working are old cm11 roms, but I can not get S-Off to reflash the firmware because I am stuck with an eMMC 9001xxxxx... chip, so I guess bad luck for me.
So now my phone will not detect ANY SIM Card and will not show any imei number or baseband in the os. In the bootloader however they are still there, both of them.
RUU's will not work for me as I am S-ON and stuck on hboot 1.57
SunShine is not working either as my phone shuts down after aprox. 30 seconds on sense rom.
Firewater is not working either as it has an 9001.... eMMC chip.
my getvar stats:
PHP:
(bootloader) version: 0.5(bootloader) version-bootloader: 1.57.0000(bootloader) version-baseband: 4A.21.3263.04(bootloader) version-cpld: None(bootloader) version-microp: None(bootloader) version-main: 6.09.401.10(bootloader) version-misc: PVT SHIP S-ON(bootloader) serialno: (bootloader) imei: (bootloader) meid: 00000000000000(bootloader) product: m7_ul(bootloader) platform: HBOOT-8064(bootloader) modelid: PN0710000(bootloader) cidnum: HTC__102(bootloader) battery-status: good(bootloader) battery-voltage: 3972mV(bootloader) partition-layout: Generic(bootloader) security: on(bootloader) build-mode: SHIP(bootloader) boot-mode: FASTBOOT(bootloader) commitno-bootloader: dirty-6d8a0b9b(bootloader) hbootpreupdate: 11(bootloader) gencheckpt: 0
So my question is are there still any suggestions for me, that I didn't do or just overlooked?
So I would appreciate anything, before tearing it apart..
Cheers
Click to expand...
Click to collapse
You don't need s-off to flash firmware. You only need s-off to downgrade or to use custom firmware. You will however need to relock your bootloader. Although I should tell you Unknown imei & Baseband often turns out to be a hardware problem.
You can flash this firmware with a relocked bootloader. You will need to 're flash custom recovery and Rom to boot the phone afterwards. Unless you flash a stock Rom first, Stock Rom can be downloaded here http://forum.xda-developers.com/htc-one/development/rom-4-4-3-sense-6-6-09-401-5-100-stock-t2854300
Firmware download
http://xda7.androidrevolution.org/db_mirror/Firmware/HTC/HTC_One/401/6.09.401.10.zip
Download it and put it in your fastboot folder and rename it firmware.zip.
Reboot the phone to the bootloader and Connect fastbootusb. Now open your Fastboot command line and type
Code:
fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader
Code:
fastboot oem rebootRUU
--- case sensitive. ---^^^
The phone will reboot to a black screen with a Silver HTC LOGO. This is RUU mode. Now we're going to flash the firmware.
Code:
fastboot flash zip firmware.zip
The first flash will be short. It's just a preupdate preparing the hboot for the new firmware. So we need to do the same command again.
Code:
fastboot flash zip firmware.zip
The second flash will take a little longer and this time it will flash the full firmware. The progress bar on the phone screen will not reach 100% this is normal as long as the command window has completed its output the flash is done.
Code:
fastboot reboot-bootloader
If you found my posts helpful, no need to say thanks. There's a button for that
Danny201281 said:
You don't need s-off to flash firmware. You only need s-off to downgrade or to use custom firmware. You will however need to relock your bootloader. Although I should tell you Unknown imei & Baseband often turns out to be a hardware problem.
You can flash this firmware with a relocked bootloader. You will need to 're flash custom recovery and Rom to boot the phone afterwards. Unless you flash a stock Rom first, Stock Rom can be downloaded here http://forum.xda-developers.com/htc-one/development/rom-4-4-3-sense-6-6-09-401-5-100-stock-t2854300
Firmware download
http://xda7.androidrevolution.org/db_mirror/Firmware/HTC/HTC_One/401/6.09.401.10.zip
Download it and put it in your fastboot folder and rename it firmware.zip.
Reboot the phone to the bootloader and Connect fastbootusb. Now open your Fastboot command line and type
Code:
fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader
Code:
fastboot oem rebootRUU
--- case sensitive. ---^^^
The phone will reboot to a black screen with a Silver HTC LOGO. This is RUU mode. Now we're going to flash the firmware.
Code:
fastboot flash zip firmware.zip
The first flash will be short. It's just a preupdate preparing the hboot for the new firmware. So we need to do the same command again.
Code:
fastboot flash zip firmware.zip
The second flash will take a little longer and this time it will flash the full firmware. The progress bar on the phone screen will not reach 100% this is normal as long as the command window has completed its output the flash is done.
Code:
fastboot reboot-bootloader
If you found my posts helpful, no need to say thanks. There's a button for that
Click to expand...
Click to collapse
Ok cheers m8!
I am gonna try it right now. Yeah I heard about the hardware problem, but I was thinking mine might be not because it happened after a factory reset (done in the os itself). I once was able to bring back baseband and imei but I just can't remember what exactely I did.
So I am going to report back as soon as I tried. I am wondering.
Btw you know what hardware defect actually would cause it (just wondering)
Thx!
shieldeverything said:
Ok cheers m8!
I am gonna try it right now. Yeah I heard about the hardware problem, but I was thinking mine might be not because it happened after a factory reset (done in the os itself). I once was able to bring back baseband and imei but I just can't remember what exactely I did.
So I am going to report back as soon as I tried. I am wondering.
Btw you know what hardware defect actually would cause it (just wondering)
Thx!
Click to expand...
Click to collapse
With your phone s-on and on the latest firmware there's not much else you can do but flash the firmware package I linked. If you can get s-off you can try an ruu.
From a hardware perspective It's the antenna connector pin that causes the issue as far as I'm aware. I only know of one that was repaired without returning to HTC and the antenna connector pin was the cause. Replacing it solved the problem.
If you found my posts helpful, no need to say thanks. There's a button for that
Danny201281 said:
With your phone s-on and on the latest firmware there's not much else you can do but flash the firmware package I linked. If you can get s-off you can try an ruu.
From a hardware perspective It's the antenna connector pin that causes the issue as far as I'm aware. I only know of one that was repaired without returning to HTC and the antenna connector pin was the cause. Replacing it solved the problem.
If you found my posts helpful, no need to say thanks. There's a button for that
Click to expand...
Click to collapse
So I did everything and it worked. But only for 5-10 minutes and then it startet rebooting again and again. So I guess this is a hardware problem too and as I don't have any warranty or something there my m7ul goes...
Thx for your help anyways!