TWRP for U Play
WARNING: SOME USERS ARE EXPERIENCING BOOTLOOP AFTER OTA UPDATING WITH TWRP.
DO NOT FLASH THIS RECOVERY INSTEAD USE FOR TEMPORARY BOOT IF YOU WANT OTA UPDATE
For direct booting without installation use
"fastboot boot twrp-3.1.1-0-alpine.img" in the bootloader menu (white screen )
If you want permanent installation follow these steps
NOTE: Please Check the partition table for your model and flash recovery to that block,
using wrong block can brick your device
use this command in terminal emulator or adb to check partition table
Code:
cat proc/emmc
for me its mmcblk0p39
Boot twrp from bootloader
Code:
fastboot boot twrp-3.1.1-0-alpine.img
now that your booted into twrp open adb and use these commands
Push Recovery Image to phone
Code:
adb push twrp-3.1.1-0-alpine.img /data/local/tmp
Set permission for recovery image
Code:
adb shell chmod 777 /data/local/tmp/twrp-3.1.1-0-alpine.img
Backup Current Recovery Image (in case you want to go back or failed)
Code:
adb shell dd if=/dev/block/mmcblk0p39 of=/sdcard/backup.img
Copy recovery to block
Code:
adb shell dd if=/data/local/tmp/twrp-3.1.1-0-alpine.img of=/dev/block/mmcblk0p39
Download
Source
Github
Can someone of devs create roms for our htc u play??
dranzer006 said:
TWRP for U Play
Click to expand...
Click to collapse
Has this been tested? I tried another twrp recovery and it's left my phone in a bootloop after trying to do a system update
Dutty106 said:
Has this been tested? I tried another twrp recovery and it's left my phone in a bootloop after trying to do a system update
Click to expand...
Click to collapse
yes i have used it however you need to have s off to install it. Else you can just boot it temporary ( fastboot boot )
OTA updates might crash the system
dranzer006 said:
yes i have used it however you need to have s off to install it. Else you can just boot it temporary ( fastboot boot )
OTA updates might crash the system
Click to expand...
Click to collapse
Thanks for that, how do you recover after OTA crashes the system? I wish I'd known, I'm trying to see if I leave it off for about 72 hours if it will switch back on as advised in another forum. How do you get S-OFF on HTC U Play? I've only managed to unlock bootloader
Dutty106 said:
Thanks for that, how do you recover after OTA crashes the system? I wish I'd known, I'm trying to see if I leave it off for about 72 hours if it will switch back on as advised in another forum. How do you get S-OFF on HTC U Play? I've only managed to unlock bootloader
Click to expand...
Click to collapse
try connecting the phone to pc and see if adb/fastboot reboot commands work Also try holding power key for 10-15secs.
you will have to flash stock rom zip back to get OTAs
For now there isn't any s off available
htc u play
installing twrp on installing twrp then black scren and vibrates around.can you help me please thanx
dranzer006 said:
try connecting the phone to pc and see if adb/fastboot reboot commands work Also try holding power key for 10-15secs.
you will have to flash stock rom zip back to get OTAs
For now there isn't any s off available
Click to expand...
Click to collapse
I've tried all of that I'm afraid as soon as it gets a bit of power the cycle happens and the PC doesn't have time to recognize the device before it reboots, it doesn't respond to the power key or any combination of key pressing, just keeps on in the boot loop. From what I've learned I'm assuming the problem is that 52MB TWRP image, it doesn't work on this phone, the update will be trying to boot the phone into recovery but because the recovery doesn't work it creates a bootloop..so far it's been 48hrs, will try switch it back on on monday as suggested here https://forum.xda-developers.com/an...g-failures-t3596427/post74189767#post74189767 . In the meantime we need to spread the word and shame whoever uploaded that TWRP image, evil!!!
---------- Post added at 03:41 PM ---------- Previous post was at 03:40 PM ----------
martinsimir said:
installing twrp on installing twrp then black scren and vibrates around.can you help me please thanx
Click to expand...
Click to collapse
You're another victim of this TWRP image, sorry mate. Check this out..https://forum.xda-developers.com/an...g-failures-t3596427/post74189767#post74189767
Dutty106 said:
I've tried all of that I'm afraid as soon as it gets a bit of power the cycle happens and the PC doesn't have time to recognize the device before it reboots, it doesn't respond to the power key or any combination of key pressing, just keeps on in the boot loop. From what I've learned I'm assuming the problem is that 52MB TWRP image, it doesn't work on this phone, the update will be trying to boot the phone into recovery but because the recovery doesn't work it creates a bootloop..so far it's been 48hrs, will try switch it back on on monday as suggested here https://forum.xda-developers.com/an...g-failures-t3596427/post74189767#post74189767 . In the meantime we need to spread the word and shame whoever uploaded that TWRP image, evil!!!
---------- Post added at 03:41 PM ---------- Previous post was at 03:40 PM ----------
You're another victim of this TWRP image, sorry mate. Check this out..https://forum.xda-developers.com/an...g-failures-t3596427/post74189767#post74189767
Click to expand...
Click to collapse
52mb ???? the image i have posted is around 14mb only.
if your able to restart the device then press the volume down key while booting (you will feel the vibration )
Brick htc u play
I know what i did. I just wanted to know what happened to the phone.thank you for your help, even if it's going to happen, so there's nothing going on, on Monday comes a new htc at play.people are learning mistakes.
---------- Post added at 07:11 PM ---------- Previous post was at 06:27 PM ----------
dranzer006 said:
52mb ???? the image i have posted is around 14mb only.
if your able to restart the device then press the volume down key while booting (you will feel the vibration )
Click to expand...
Click to collapse
black screen and vibrating all the time .can not even connect to the PC
martinsimir said:
I know what i did. I just wanted to know what happened to the phone.thank you for your help, even if it's going to happen, so there's nothing going on, on Monday comes a new htc at play.people are learning mistakes.
---------- Post added at 07:11 PM ---------- Previous post was at 06:27 PM ----------
black screen and vibrating all the time .can not even connect to the PC
Click to expand...
Click to collapse
I won't recommend you this but you can try pulling off the back panel and removing the battery cable (its the black one)
https://www.youtube.com/watch?v=KcNNGpsn7JY
dranzer006 said:
52mb ???? the image i have posted is around 14mb only.
if your able to restart the device then press the volume down key while booting (you will feel the vibration )
Click to expand...
Click to collapse
i feel vibration but black screnn
---------- Post added at 09:50 PM ---------- Previous post was at 09:46 PM ----------
dranzer006 said:
I won't recommend you this but you can try pulling off the back panel and removing the battery cable (its the black one)
https://www.youtube.com/watch?v=KcNNGpsn7JY
Click to expand...
Click to collapse
thanx mate on Monday I will see a new htc at play.but am try this
I dismantled it, but it does not help the same problem again black screen and vibrating .I put it in the garbage can
dranzer006 said:
52mb ???? the image i have posted is around 14mb only.
if your able to restart the device then press the volume down key while booting (you will feel the vibration )
Click to expand...
Click to collapse
Hi, I'm refering to this one "twrp-3.0.3-1_UNOFFICIAL-U Play.img" Not yours.. I flashed twrp-3.0.3-1_UNOFFICIAL-U Play.img and I'm now stuck and panicking, I hope I can have me phone back again .. The device tries to reboot itself into recovery repeatedly after you try a system update, no combination of button pressing etc works, the PC doesn't even have time to pick up the phone..Like I've said in previous posts, I'm trying to see if I leave it off for some days and then recharge and try to switch it back on if it will work..So far that's the only solution I've seen from anyone.. I hope this clears up my problem and suggestions..
Dutty106 said:
Hi, I'm refering to this one "twrp-3.0.3-1_UNOFFICIAL-U Play.img" Not yours.. I flashed twrp-3.0.3-1_UNOFFICIAL-U Play.img and I'm now stuck and panicking, I hope I can have me phone back again .. The device tries to reboot itself into recovery repeatedly after you try a system update, no combination of button pressing etc works, the PC doesn't even have time to pick up the phone..Like I've said in previous posts, I'm trying to see if I leave it off for some days and then recharge and try to switch it back on if it will work..So far that's the only solution I've seen from anyone.. I hope this clears up my problem and suggestions..
Click to expand...
Click to collapse
i am not sure what problem your having but if you try to press the volume up or down key while booting up you will boot into download mode. or else try pressing volume up and down both while the phone starts
Is there a possibility that comes out a working version.?
Dutty106 said:
Hi, I'm refering to this one "twrp-3.0.3-1_UNOFFICIAL-U Play.img" Not yours.. I flashed twrp-3.0.3-1_UNOFFICIAL-U Play.img and I'm now stuck and panicking, I hope I can have me phone back again .. The device tries to reboot itself into recovery repeatedly after you try a system update, no combination of button pressing etc works, the PC doesn't even have time to pick up the phone..Like I've said in previous posts, I'm trying to see if I leave it off for some days and then recharge and try to switch it back on if it will work..So far that's the only solution I've seen from anyone.. I hope this clears up my problem and suggestions..
Click to expand...
Click to collapse
Hi, did you have any luck? I'm stuck in the same boot loop.. I even took off the case and removed the black battery cable over night but still same boot loop, did running down battery help?
Hi, don't dismantle it or any of that other stuff suggested above, let it bootloop til the battery is flat, leave it, do not charge it or do anything to it for 11+ days, then charge it and it will switch back on, no problem, you'll have your phone back.
Ok thanks, it's been about 5 days off so far from dying from the boot loop, I'll give it another 10 days before charging it and see how it goes..
Thanks again for your response..
online4yourmind said:
Ok thanks, it's been about 5 days off so far from dying from the boot loop, I'll give it another 10 days before charging it and see how it goes..
Thanks again for your response..
Click to expand...
Click to collapse
No problem :good: it will definitely work
Related
I tried to root my phone, and something messed up.
Now the phone restarts all the time, in a loop.
How can I facotory reset him?
I tried to do it from the volume - and power, but it doing automatically HBOOT, and then I have to restart the phone, and again the same thing.
Please help!
uSv'Flame said:
I tried to root my phone, and something messed up.
Now the phone restarts all the time, in a loop.
How can I facotory reset him?
I tried to do it from the volume - and power, but it doing automatically HBOOT, and then I have to restart the phone, and again the same thing.
Please help!
Click to expand...
Click to collapse
AAHK tool ???
Don;t worry , do it again
Elliott1993 said:
AAHK tool ???
Don;t worry , do it again
Click to expand...
Click to collapse
Theres a notice that if the phone in a boot loop, I need to open the aahk fast boot, but when I do the things that it says <waiting for device>, and then quit the program, why?
I think I just fu**ed up my phone.
What state was your phone in? What did you do? What tool did you use? What state is your phone in now?
Listen to banana. He knows his dhds..?
marknoll said:
Listen to banana. SHe knows hisher dhds..?
Click to expand...
Click to collapse
Hope you get it resolved , i decided to root my phone after all these years got tired of the stock 2.3.
Followed the instructions provided here careful and phew it went well running aospX 1.0.0-MR1 without any issues , i was afraid something like this might happen to me as well.
bananagranola said:
Click to expand...
Click to collapse
Omg. I didn't know u were a lady. Cool! Thanks for past help btw
uSv'Flame said:
Theres a notice that if the phone in a boot loop, I need to open the aahk fast boot, but when I do the things that it says , and then quit the program, why?
I think I just fu**ed up my phone.
Click to expand...
Click to collapse
Plug into PC. Let drivers install..then reboot boot loader. Type fast boot devices and see if your device is recognized. I am thinking your PC isn't seeing your device.
P.s. I think you may have "cross contaminated your boot IMG. Are u s off...unlocked? Need more info!!!
---------- Post added at 06:19 AM ---------- Previous post was at 06:15 AM ----------
If your phone don't reboot without a boot loop... Hold power and volume down for about 7 mins. I am also thinking u flashed a bad zip. Let us know if it boots after holding that combo for 7 mins. I know its a long time...
---------- Post added at 06:20 AM ---------- Previous post was at 06:19 AM ----------
U thinking what I am banana? "I am a dumbass" section? Lol
I think usvflames cell is shot. Hasn't replied back. :-\
Q&A for [RECOVERY]ClockworkMod Recovery v6.0.4.7
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
same here
mbwambo said:
heloo ,,,,,, i have a problem with my htc desire816 dual sim, after installng custom recovery fail to work and my phone wrote tampered above unlocked line and fail to show custom recovery help plz.............
Click to expand...
Click to collapse
Hello Bro,
Here i 've the same issue and awaiting for solution. Do you have any update ?
I'll share if i found anything.
you can have some idea on below link and ": ADVANCED BOOT PROBLEMS"
http://forum.xda-developers.com/showthread.php?t=1275632
But, i haven't tried...it's quiet fear about to have try (becuase they mentioned it's a worst situation and the link is not exactly for Desire 816 model).
Thanks in Advance, SR
Sivasr said:
Hello Bro,
Here i 've the same issue and awaiting for solution. Do you have any update ?
I'll share if i found anything.
you can have some idea on below link and ": ADVANCED BOOT PROBLEMS"
http://forum.xda-developers.com/showthread.php?t=1275632
But, i haven't tried...it's quiet fear about to have try (becuase they mentioned it's a worst situation and the link is not exactly for Desire 816 model).
Thanks in Advance, SR
Click to expand...
Click to collapse
hey bro
now i solve the problem to my own ........................what about you you still have the same issue
how ?
how did u solve this problem ?
mbwambo said:
hey bro
now i solve the problem to my own ........................what about you you still have the same issue
Click to expand...
Click to collapse
Really!!!!!!!!.....It's nice to know you geeting out from hectic. Would you plz explain step by step process...it would help many guys to get relieve from the issue...
Eagerly waiting for your response.. plz help us
---------- Post added at 02:41 AM ---------- Previous post was at 02:02 AM ----------
mbwambo said:
hey bro
now i solve the problem to my own ........................what about you you still have the same issue
Click to expand...
Click to collapse
Yes brother, i have still same issue
Did you all try to use the .exe or did you use the fastboot command to flash this? If this does not work for you go to the CM thread, download that recovery file and use the same fastboot command in this thread. When you download the CM clockworkmod rename it to what the command says so it should be recovery_en.img
Sent from my 710C using XDA Free mobile app
I solved the problem by flashing via command not use exe thing........
So just use recovery.img ...hope will work ......
---------- Post added at 09:59 PM ---------- Previous post was at 09:41 PM ----------
But bad enough now i have other problem after flashing recovery.img .....my phone write ...TAMPERED......above unlocked...line..
Then doesnt show bettery sign....while am charging and my phone is off...also write some words in red colour that no permission to write this and so on those comes while my phone is charching or during restarting ...and going into recovery mode...
Anyone can help me...?????
mbwambo said:
I solved the problem by flashing via command not use exe thing........
So just use recovery.img ...hope will work ......
---------- Post added at 09:59 PM ---------- Previous post was at 09:41 PM ----------
But bad enough now i have other problem after flashing recovery.img .....my phone write ...TAMPERED......above unlocked...line..
Then doesnt show bettery sign....while am charging and my phone is off...also write some words in red colour that no permission to write this and so on those comes while my phone is charching or during restarting ...and going into recovery mode...
Anyone can help me...?????
Click to expand...
Click to collapse
Everyone experiencing the no recovery or the exclamation mark on the recovery screen its because you tried to run the .exe or flash the recovery with a fastboot command WHILE IN HBOOT MODE. You need to be in fastboot to do this and your device bootloader has to be unlocked before you try anything root wise.
Mine does the same thing. When it enters recovery just hit reboot device and let it start up. It charges in 2-3 hours on or off as long as the screen isn't active.
Also, ANY device that you unlock the bootloader for will say Tampered. Its HTC's way of knowing if you unlocked the device, but that doesn't mean you can't return it. It is done through HTC though and you are allowed to relock it to return it.
If your device power button stops working HTC will take it back regardless of bootloader status as that's a hardware problem. If your phone is not charging properly that isn't a bootloader problem that is the software of Android and is valid for a claim.
If you try to flash an entirely different bootloader then they'll reject your device because you went further then to just "Tamper".
If it voided warranty to unlock the bootloader there would be no root apps on the Playstore allowed.
Sent from my 710C using XDA Free mobile app
@jaysoblitzed
Does yours shows those words in read colour that you dont have permission and so on...????
mbwambo said:
@jaysoblitzed
Does yours shows those words in read colour that you dont have permission and so on...????
Click to expand...
Click to collapse
Yes it does say the exact same thing but the message actually states:
This build is for development purposes only.
Do not distribute outside of HTC without HTC's permission.
Failure to comply may lead to legal action.
No worries though, this message is automatically put there by HTC after unlocking the bootloader. :laugh:
@jaysobitzed
Yes.....that is the message i was talking about.......but to my side its coming even in charging mode while my phone iz off.......then directly goes into CWM mode...How about yours ??
mbwambo said:
@jaysobitzed
Yes.....that is the message i was talking about.......but to my side its coming even in charging mode while my phone iz off.......then directly goes into CWM mode...How about yours ??
Click to expand...
Click to collapse
@mbwambo Yep, mine does the same thing :good: :good:
---------- Post added at 08:41 AM ---------- Previous post was at 08:36 AM ----------
[NEW UPDATE]:
IF YOU RECEIVE AN EXCLAMATION MARK ON THE RECOVERY SCREEN AFTER RUNNING THE .EXE THEN IT IS BECAUSE YOU NEED TO FLASH AN OLDER CLOCKWORKMOD FIRST!
POWER OFF YOUR DEVICE BY HOLDING VOLUME UP + POWER BUTTON FOR 15 SECONDS IF YOUR STUCK AND THEN POWER ON BY HOLDING VOLUME DOWN+POWER BUTTON AND YOU'LL GO BACK INTO THE BOOTLOADER.
ONCE YOUR DEVICE IS SET IN FASTBOOT USB MODE DOWNLOAD THIS FILE BELOW:
https://s.basketbuild.com/dl/devs?dl=Grarak/recovery.img
NOW SAVE THAT FILE WHERE THE ADB FOLDER / PLATFORM-TOOLS IS THAT YOU INSTALLED AT THE BEGINNING OF THE VIDEO IN (Local Disk C:/adb)
ONCE THAT'S COMPLETE GO INTO THAT FOLDER AND RIGHT-CLICK IN ANY WHITE AREA OF THE FOLDER AND PRESS "RUN COMMAND LINE HERE" & RUN THE FOLLOWING COMMAND:
fastboot flash recovery recovery.img
REBOOT TO RECOVERY AND CONFIRM!
NOW YOU CAN RUN THE .EXE IN FASTBOOT USB MODE AGAIN OR FLASH THE RECOVERY HERE FOR THE LATEST VERSION!
Done!
mbwambo said:
I solved the problem by flashing via command not use exe thing........
So just use recovery.img ...hope will work ......
---------- Post added at 09:59 PM ---------- Previous post was at 09:41 PM ----------
But bad enough now i have other problem after flashing recovery.img .....my phone write ...TAMPERED......above unlocked...line..
Then doesnt show bettery sign....while am charging and my phone is off...also write some words in red colour that no permission to write this and so on those comes while my phone is charching or during restarting ...and going into recovery mode...
Anyone can help me...?????
Click to expand...
Click to collapse
Hi mbwambo, I'm not sre aboput problem you face that "Bettery sign missing and power of ur phone "..but as you told, (it's n going to Recovery mode Or Hboot) You can able the fast boot option under settings > Power . then sytem will go automaticall into normal start up instead of going into recovery or Hboot mode. i had the same problem what you have. after checked in the fast boot it's simply restarts as usual in charging or not charging status. hope this would help ur restarting issue.
I've the same tampered, but still not enter into recovery mode....u r lucky at this case...now you root ur mobile
Thnx, SR
Sivasr said:
Hi mbwambo, I'm not sre aboput problem you face that "Bettery sign missing and power of ur phone "..but as you told, (it's n going to Recovery mode Or Hboot) You can disable the fast boot option under settings > Power . then sytem will go automaticall into normal start up instead of going into recovery or Hboot mode. i had the same problem what you have. after checked in the fast boot it's simply restarts as usual in charging or not charging status. hope this would help ur restarting issue.
I've the same tampered, but still not enter into recovery mode....u r lucky at this case...now you root ur mobile
Thnx, SR
Click to expand...
Click to collapse
Thanks Sivasr!
@mbwambo:
By going into your settings and checking fastboot it will stop the device from booting into recovery if put to charge when powered off. This will show the battery icon and no red text will appear.
@Sivasr:
Try the method I just posted it will work to get into the recovery. I have had some people ask me about that same issue and that solution has worked for them. Also, make sure to uncheck fastboot in Power - Settings!
13330
jaysoblitzed said:
Thanks Sivasr!
@mbwambo:
By going into your settings and checking fastboot it will stop the device from booting into recovery if put to charge when powered off. This will show the battery icon and no red text will appear.
@Sivasr:
Try the method I just posted it will work to get into the recovery. I have had some people ask me about that same issue and that solution has worked for them. Also, make sure to uncheck fastboot in Power - Settings!
Click to expand...
Click to collapse
thanks again.....but too sad, i had relocked my phone after all tries are done. this evening i tried again to unlock it's not unlocking my phone only sticks with "Unlock Bootloader? " screen and it's says entering Rocovery... very long time. I don't think i can do unlock my phone again. i know iwe could not flash the recovery.img without unlock booloader....:crying::crying::crying::crying::crying::crying:
Sivasr said:
thanks again.....but too sad, i had relocked my phone after all tries are done. this evening i tried again to unlock it's not unlocking my phone only sticks with "Unlock Bootloader? " screen and it's says entering Rocovery... very long time. I don't think i can do unlock my phone again. i know iwe could not flash the recovery.img without unlock booloader....:crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
@Sivasr
To unlock it again just use the same unlock.bin file you got in the email. Then use the recovery.img file I listed or go to the CM11 thread and download the recovery from there and use that one.
After you flash that old version you can go into it from the bootloader. Just go to advanced in the recovery, reboot to bootloader, and flash the new recovery with the .exe or with the recovery file from the CWM thread.
Done
You can't flash the recovery if it's still locked you are correct. If it seems frozen use the volume keys to navigate and power button to select.
Sent from my 710C using XDA Free mobile app
bricked phone
hi all
My htc desire 816 dual sim got hard bricked after flashing rom
Please help
:crying:
abdealli dalal said:
hi all
My htc desire 816 dual sim got hard bricked after flashing rom
Please help
:crying:
Click to expand...
Click to collapse
Hard bricked? There is no help for you.
CWM auto boot
Hi there.
Can anybody explain me, why my 816w (CWM v6.04.7) when I put it on charger after total battery discharge, turns on automatically and boots in recovery
Thank you in advance!
FoxyDrew said:
Hard bricked? There is no help for you.
Click to expand...
Click to collapse
What ROM did you flash? Does your device still turn on? Can you access the bootloader and/or recovery?
Sent from my 710C using XDA Free mobile app
---------- Post added at 08:14 PM ---------- Previous post was at 08:12 PM ----------
bunkker said:
Hi there.
Can anybody explain me, why my 816w (CWM v6.04.7) when I put it on charger after total battery discharge, turns on automatically and boots in recovery
Thank you in advance!
Click to expand...
Click to collapse
This is a glitch with the old CWM recovery. If you use the one from the CM12 thread; 6.0.5.1 CWM then you will be able to avoid this issue. Only thing is instead of it booting into recovery it won't boot unless you remove it from the power source. Lol so you win some you lose some.
Sent from my 710C using XDA Free mobile app
Hi Guys!
Today I was getting to rooting the device, until I ran into a problem
I accidentally flashed Android KK aboot and the rest on Android L versions.
The result was inability to boot ANYTHING (System/Download/Recovery)
It also showed an error message saying to following
ERROR : boot certification verify
[630]-----------------------------------------------
[630]
[630] Secure booting Error!
[630] Cause : boot certification verify
[630]
[630]-----------------------------------------------
Shortly following that is a black screen with red and blue flashing LED. (Vol. Down leads to restart and Vol.Up seems to stop the flashing, however still on black screen)
Is it possible for me to get out of this problem? Or have I hard bricked my phone?
Its bricked, there is a version mismatch between your android bootloader and your phone's bootloader meaning that it prevents you from going into download or recovery mode
KuHaKu said:
Hi Guys!
Today I was getting to rooting the device, until I ran into a problem
I accidentally flashed Android KK aboot and the rest on Android L versions.
The result was inability to boot ANYTHING (System/Download/Recovery)
It also showed an error message saying to following
ERROR : boot certification verify
[630]-----------------------------------------------
[630]
[630] Secure booting Error!
[630] Cause : boot certification verify
[630]
[630]-----------------------------------------------
Shortly following that is a black screen with red and blue flashing LED. (Vol. Down leads to restart and Vol.Up seems to stop the flashing, however still on black screen)
Is it possible for me to get out of this problem? Or have I hard bricked my phone?
Click to expand...
Click to collapse
I HAVE YOUR SOLUTION flash this patched boot img which is used for phones when you downgrade the aboot and laf to kk to get twrp working http://forum.xda-developers.com/lg-g3/orig-development/recovery-twrp-touch-recovery-2-8-2-0-t2966129
Quote100 said:
I HAVE YOUR SOLUTION flash this patched boot img which is used for phones when you downgrade the aboot and laf to kk to get twrp working http://forum.xda-developers.com/lg-g3/orig-development/recovery-twrp-touch-recovery-2-8-2-0-t2966129
Click to expand...
Click to collapse
If you bothered to read properly he cant boot anything
itsbighead said:
If you bothered to read properly he cant boot anything
Click to expand...
Click to collapse
if you bothered to android properly he doesn't need to boot into anything if the computer can recognize it
---------- Post added at 01:45 PM ---------- Previous post was at 01:41 PM ----------
Also ever since i flashed twrp on mine, whenever i click reboot my phone doesn't reboot and i just get a black screen with no led and i have to remove the battery for it to boot again. I'm not sure if this will work in your situation but it couldn't hurt to try
Quote100 said:
if you bothered to android properly he doesn't need to boot into anything if the computer can recognize it
---------- Post added at 01:45 PM ---------- Previous post was at 01:41 PM ----------
Also ever since i flashed twrp on mine, whenever i click reboot my phone doesn't reboot and i just get a black screen with no led and i have to remove the battery for it to boot again. I'm not sure if this will work in your situation but it couldn't hurt to try
Click to expand...
Click to collapse
itsbighead said:
If you bothered to read properly he cant boot anything
Click to expand...
Click to collapse
Yep, I cannot get my computer to recognize my phone in anyway (i tried going into TWRP and Download) and both did not work.
Any ideas?
KuHaKu said:
Yep, I cannot get my computer to recognize my phone in anyway (i tried going into TWRP and Download) and both did not work.
Any ideas?
Click to expand...
Click to collapse
did you try to boot into the factory reset mode? (hold volume down and power to turn it on and stop when you see the lg logo and then hold them again after stopping)
Quote100 said:
did you try to boot into the factory reset mode? (hold volume down and power to turn it on and stop when you see the lg logo and then hold them again after stopping)
Click to expand...
Click to collapse
That would be what i would of noted as TWRP or Recovery - No
KuHaKu said:
That would be what i would of noted as TWRP or Recovery - No
Click to expand...
Click to collapse
ah i have no idea then you might just have a permanent brick but i have one last idea that may or may not help, (probably not) you said you stop the flashing by pushing the volume up button im not at all sure what that mode is supposed to be but does the computer recognize it in that mode?
FIXED
I have a solution to your problem..
Heres a solution to your problem... http://forum.xda-developers.com/spr...y-download-t3053985/post60106965#post60106965
brick
it bricks bro
Quote100 said:
ah i have no idea then you might just have a permanent brick but i have one last idea that may or may not help, (probably not) you said you stop the flashing by pushing the volume up button im not at all sure what that mode is supposed to be but does the computer recognize it in that mode?
Click to expand...
Click to collapse
BINGO!
Currently working on finding a way of throwing over the system, but other than that, i got my computer to recognize it, if any progress is made, I'll post it here .
THX TO QUOTE100 ))))
Celly624 said:
I have a solution to your problem..
Heres a solution to your problem... http://forum.xda-developers.com/spr...y-download-t3053985/post60106965#post60106965
Click to expand...
Click to collapse
Fastboot doesnt work for any variant with a locked bootloader
OP can try the old LG Flash Tool guide but i doubt that will work
KuHaKu said:
BINGO!
Currently working on finding a way of throwing over the system, but other than that, i got my computer to recognize it, if any progress is made, I'll post it here .
THX TO QUOTE100 ))))
Click to expand...
Click to collapse
Alright! that's great, glad i could help
Please help urgently! So I just S-OFF'd my phone (right after unlocking my bootloader via htcdev) and I was excited to finally manually flash a 5.1 update to my EE UK One m9. I sort of made it a European version by changing one of its update numbers to [BLANK].401.[BLANK]. I then spent the whole night booting my phone into download mode and using fastboot commands: "htc_fastboot flash zip...".
Each zip was the previous update to the other, I.e. I was already on 1.32.401.6, so I used fastboot to get to 1.32.401.8 as the cmd. prompt said that it was successfully installed on my phone (p.s. I didn't have an sd card big enough to exfat 32 and put the update zips on it). I then repeated the steps again, but then fastboot flashed "2.10.401.", this was the update that would hopefully bring my phone to 5.1 . The cmd. prompt said that it was a success so I booted my phone up as normal, but I went to the settings to check software information and it was still on 1.32.401.6! It then said an update was ready to install so I just installed it as normal. Once it went into the bootloader it flashed it without any problems and tried to boot back up again. It then lit up a blue screen for 10 seconds and then went into the black HTC RUU screen with the grey htc logo. My phone has now, for the last hour, been stuck in this infinite loop of blue screen, vibrate, ruu screen and REPEAT. I've tried pressing vol. down and power as well as up to get into other modes like download mode, but it doesn't work. I CAN'T EVEN TURN IT OFF! I HAVE TO WAIT FOR IT TO RUN OUT OF BATTERY! MORE IMPORTANTLY, ADB DOESNT RECOGNISE IT, NOR DOES FASTBOOT!!!! SO I CAN'T EVEN FLASH A STOCK RECOVERY, SYSTEM IMG, ETC! PLEASE IF ANYONE CAN, HELP ME. I REALLY DON'T WANT TO HAVE TO BUY A NEW ONE AND PAY S-OFF AGAIN!
Louis118 said:
Please help urgently! So I just S-OFF'd my phone and I was excited to finally manually flash a 5.1 update to my EE UK One m9. I sort of made it a European version by changing one of its update numbers to [BLANK].401.[BLANK]. I then spent the whole night booting my phone into download mode and using fastboot commands: "htc_fastboot flash zip...".
Each zip was the previous update to the other, I.e. I was already on 1.32.401.6, so I used fastboot to get to 1.32.401.8 as the cmd. prompt said that it was successfully installed on my phone (p.s. I didn't have an sd card big enough to exfat 32 and put the update zips on it). I then repeated the steps again, but then fastboot flashed "2.10.401.", this was the update that would hopefully bring my phone to 5.1 . The cmd. prompt said that it was a success so I booted my phone up as normal, but I went to the settings to check software information and it was still on 1.32.401.6! It then said an update was ready to install so I just installed it as normal. Once it went into the bootloader it flashed it without any problems and tried to boot back up again. It then lit up a blue screen for 10 seconds and then went into the black HTC RUU screen with the grey htc logo. My phone has now, for the last hour, been stuck in this infinite loop of blue screen, vibrate, ruu screen and REPEAT. I've tried pressing vol. down and power as well as up to get into other modes like download mode, but it doesn't work. I CAN'T EVEN TURN IT OFF! I HAVE TO WAIT FOR IT TO RUN OUT OF BATTERY! MORE IMPORTANTLY, ADB DOESNT RECOGNISE IT, NOR DOES FASTBOOT!!!! SO I CAN'T EVEN FLASH A STOCK RECOVERY, SYSTEM IMG, ETC! PLEASE IF ANYONE CAN, HELP ME. I REALLY DON'T WANT TO HAVE TO BUY A NEW ONE AND PAY S-OFF AGAIN!
Click to expand...
Click to collapse
hold power and vol up and vol down all at the same time will get you to bootloader, we hope
Aldo101t said:
hold power and vol up and vol down all at the same time will get you to bootloader, we hope
Click to expand...
Click to collapse
That helped thanks, but I still can't boot into anything else... I'm pretty sure I can't install anything through fastboot without download or run mode...
Louis118 said:
That helped thanks, but I still can't boot into anything else... I'm pretty sure I can't install anything through fastboot without download or run mode...
Click to expand...
Click to collapse
you can't boot into download mode from bootloader?
or boot into recovery and restore a backup,
Aldo101t said:
you can't boot into download mode from bootloader?
or boot into recovery and restore a backup,
Click to expand...
Click to collapse
nope, NOTHING. THE ONLY THING THAT WORKS IS THE POWER OFF OPTION.
Aldo101t said:
you can't boot into download mode from bootloader?
or boot into recovery and restore a backup,
Click to expand...
Click to collapse
what you should do is if you can restore a backup, put a 5.1 rom on your sd card and after you flash the latest firmware 2.10.401.xx. then boot to recovery and install the 5.1 rom.
---------- Post added at 07:43 PM ---------- Previous post was at 07:41 PM ----------
Louis118 said:
nope, NOTHING. THE ONLY THING THAT WORKS IS THE POWER OFF OPTION.
Click to expand...
Click to collapse
you still have TWRP INSTALLED, do you have a backup.
Aldo101t said:
what you should do is if you can restore a backup, put a 5.1 rom on your sd card and after you flash the latest firmware 2.10.401.xx. then boot to recovery and install the 5.1 rom.
---------- Post added at 07:43 PM ---------- Previous post was at 07:41 PM ----------
you still have TWRP INSTALLED, do you have a backup.
Click to expand...
Click to collapse
How do you expect me to boot into it? I told you, pressing any other mode besides power off, causes the blue screen loop
Louis118 said:
nope, NOTHING. THE ONLY THING THAT WORKS IS THE POWER OFF OPTION.
Click to expand...
Click to collapse
try powering it off then go back to bootloader and try to get to recovery again
Aldo101t said:
try powering it off then go back to bootloader and try to get to recovery again
Click to expand...
Click to collapse
Nope, still does the blue loop.
Louis118 said:
Nope, still does the blue loop.
Click to expand...
Click to collapse
well, that's the sh^ts, I don't know at this point.maybe someone else can chime in here that can help.
I've seen this before, and there is no fix that I'm aware of. You've corrupted something important in your firmware, probably by flashing all those firmware packages.
You made several mistakes here, the first in thinking you needed to flash every firmware for your phone. All you needed was the last one. The other mistake was confusing your OS version with your firmware version. You were still on 1.32 base but your firmware was updated.
The last mistake, and the one that probably did the damage, was trying to take an OTA after all that. You were stock enough for it to run, but since your firmware was already updated, the OTA broke something.
As far as I know, the only thing you can do is return it to HTC for service.
Sent from my HTC One M9 using Tapatalk
iElvis said:
I've seen this before, and there is no fix that I'm aware of. You've corrupted something important in your firmware, probably by flashing all those firmware packages.
You made several mistakes here, the first in thinking you needed to flash every firmware for your phone. All you needed was the last one. The other mistake was confusing your OS version with your firmware version. You were still on 1.32 base but your firmware was updated.
The last mistake, and the one that probably did the damage, was trying to take an OTA after all that. You were stock enough for it to run, but since your firmware was already updated, the OTA broke something.
As far as I know, the only thing you can do is return it to HTC for service.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Thanks for trying to help anyway. Also, I got this under contract from EE, so do I have UH OH protection automatically from htc? Or will it cost me to get it serviced?
Louis118 said:
Thanks for trying to help anyway. Also, I got this under contract from EE, so do I have UH OH protection automatically from htc? Or will it cost me to get it serviced?
Click to expand...
Click to collapse
Uh Oh protection isn't available in the UK.
As you unlocked your bootloader and got S-OFF, they will almost certainly charge you for repairs as this isn't a hardware issue and was actually caused by you flashing your phone.
Sent from my HTC One M9 using Tapatalk
Questions............
Did u install any recovery like twrp?
Did you root?
Post pictures of bootloader/try to post any other screen you may be able to enter
LLegion said:
Questions............
Did u install any recovery like twrp?
Did you root?
Post pictures of bootloader/try to post any other screen you may be able to enter
Click to expand...
Click to collapse
I'm able to enter the boot loader menu (with the options to reboot, power down, download mode and bootloader). Unfortunately, clicking any of the options (apart from power down) causes the blue screen boot loop to continue.
This wasn't really Crazy you now All You have to do is go to the bootloader menu and from there Ashley you can actually flash the Recovery ebusiness Leave me and if you don't believe me godaddy redirect link to the Team Win recovery project Website Just follow the instructions to flash recovery as they say
---------- Post added at 05:17 PM ---------- Previous post was at 05:13 PM ----------
You can flash recovery from bootloader menu i did that way when by mistake did erease all my internal card including system.img.....i was lost my phone didnt boot line yours also getting the bluescreen and voilaaa!!! I did flash on bootloader menu but download the 2.8.7.1 beta here the proof link....https://twrp.me/devices/htconem9.html
LLegion said:
This wasn't really Crazy you now All You have to do is go to the bootloader menu and from there Ashley you can actually flash the Recovery ebusiness Leave me and if you don't believe me godaddy redirect link to the Team Win recovery project Website Just follow the instructions to flash recovery as they say
---------- Post added at 05:17 PM ---------- Previous post was at 05:13 PM ----------
You can flash recovery from bootloader menu i did that way when by mistake did erease all my internal card including system.img.....i was lost my phone didnt boot line yours also getting the bluescreen and voilaaa!!! I did flash on bootloader menu but download the 2.8.7.1 beta here the proof link....https://twrp.me/devices/htconem9.html
Click to expand...
Click to collapse
I flashed the recovery file successfully (according to the command window) but when I click the "reboot recovery mode" option it brings up the red development text and then goes back into the bluescreen loop.
Louis118 said:
I flashed the recovery file successfully (according to the command window) but when I click the "reboot recovery mode" option it brings up the red development text and then goes back into the bluescreen loop.
Click to expand...
Click to collapse
You said before that fastboot wasn't working. It's working now? Does it show up in fastboot devices?
If so, you might try running a RUU from bootloader.
The trixk is to flash and just after reboot press power and down vol to wnter immediatly into rexovery twrp just as it says in the link...just do it and will go into twrp once you have entered justflash any nandroid or flash a zip ruu from sd card in a sexond boot
I'm not able to enter RUU mode...
My Pixel XL is now dead. Won't turn on when pressing or long pressing or long pressing the power button for 5 minutes.
Long pressing the volume down and power button leads to vibration feedback but the screen is black, can't even get to the bootloader.
Last thing before it bricked is browsing through my photos, my phone suddenly froze as usual. And then it powered off automatically. After that, I can't get into the system, neither the bootloader.
Anybody know how to fix hard bricked Pixel?
Thx.
Queentus said:
My Pixel XL is now dead. Won't turn on when pressing or long pressing or long pressing the power button for 5 minutes.
Long pressing the volume down and power button leads to vibration feedback but the screen is black, can't even get to the bootloader.
Last thing before it bricked is browsing through my photos, my phone suddenly froze as usual. And then it powered off automatically. After that, I can't get into the system, neither the bootloader.
Anybody know how to fix hard bricked Pixel?
Thx.
Click to expand...
Click to collapse
try this one here
if not, call harware support for a possible rma
reyscott said:
try this one here
if not, call harware support for a possible rma
Click to expand...
Click to collapse
Won't work cause I can't even get to the bootloader. Thx anyway.
call google support to initiate RMA.
There is no laymans method to fix a hard bricked Pixel.
Only soft bricks.
CZ Eddie said:
There is no laymans method to fix a hard bricked Pixel.
Only soft bricks.
Click to expand...
Click to collapse
Thanks for the reply.
My Pixel is already on it's way to RMA.
My Pixel XL shut down this morning. After several attempts to restart, it hung on the Google splash screen. I got into bootloader and tried to reflash OPR3 with flash-all.bat. It got a little ways but quit with “remote: flash write failure”. I got into bootloader again and tried the reflash again. It got the same error earlier in the process and ever since, no button combinations will get it to turn on and I get no lights or battery image when plugged in.
When I plug it into my computer, I get the connection beep from the computer, but no evidence of a connection in Device Manager or in remove media. Since my computer recognizes the phone somehow, is there a way to retrieve data from my phone? I have seen many references to programs that can do this, but I am skeptical. My warranty replacement has been ordered, but I'd like to get whatever I can before it gets here.
Same thing happened to me last night. RMA is on its way, but this month old Pixel XL is dead.
CZ Eddie said:
There is no laymans method to fix a hard bricked Pixel.
Only soft bricks.
Click to expand...
Click to collapse
do you have an advanced guide to fix it? I have pixel past warranty that has the same problem
JimSmith94 said:
My Pixel XL shut down this morning. After several attempts to restart, it hung on the Google splash screen. I got into bootloader and tried to reflash OPR3 with flash-all.bat. It got a little ways but quit with “remote: flash write failure”. I got into bootloader again and tried the reflash again. It got the same error earlier in the process and ever since, no button combinations will get it to turn on and I get no lights or battery image when plugged in.
When I plug it into my computer, I get the connection beep from the computer, but no evidence of a connection in Device Manager or in remove media. Since my computer recognizes the phone somehow, is there a way to retrieve data from my phone? I have seen many references to programs that can do this, but I am skeptical. My warranty replacement has been ordered, but I'd like to get whatever I can before it gets here.
Click to expand...
Click to collapse
There are 2 things you can try 1.) Go-to you folder where you have adb & fastboot. Download factory zip and unzip into adb & fastboot folder. Plug phone into PC. Open a cmd window that's NOT the administrator one try adb devices, then fastboot reboot bootloader. Click once to advance in cmd, then double click flash-all.bat and let it run through the install process. It will stop a few time, but just ignore, may even spit out an error, just ignore and let it keep installing, it may keep doing this stop and start thing,let it run. It will eventually boot up. It will wipe phone and you will have to do a new phone install. Then you can go into bootloader mode and fastboot twrp and twrp installer and go back and install super su go back and install suhide 109.
When installing TWRP I would recommend the previous version of December 1, I think and not the Dec. 15 version. Same with twrp installer.
The other thing you can try is to (if you can turn phone off) hold down power button for 5 seconds then press volume UP , that should put you in the Android on it's back and say No Command. Then you can use the options given you.
Good luck
fiverings said:
There are 2 things you can try 1.) Go-to you folder where you have adb & fastboot. Download factory zip and unzip into adb & fastboot folder. Plug phone into PC. Open a cmd window that's NOT the administrator one try adb devices, then fastboot reboot bootloader. Click once to advance in cmd, then double click flash-all.bat and let it run through the install process. It will stop a few time, but just ignore, may even spit out an error, just ignore and let it keep installing, it may keep doing this stop and start thing,let it run. It will eventually boot up. It will wipe phone and you will have to do a new phone install. Then you can go into bootloader mode and fastboot twrp and twrp installer and go back and install super su go back and install suhide 109.
When installing TWRP I would recommend the previous version of December 1, I think and not the Dec. 15 version. Same with twrp installer.
The other thing you can try is to (if you can turn phone off) hold down power button for 5 seconds then press volume UP , that should put you in the Android on it's back and say No Command. Then you can use the options given you.
Good luck
Click to expand...
Click to collapse
My post was over three months ago and as I said, I got a refurb replacement, which I have since sold and have a Pixel 2 XL. Guess I should have said that although my computer recognized it, adb didn't. That's why I was asking if there was any other way to retrieve the data. I ended up using a week old backup so it wasn't too bad.
I tried to install a custom rom, and it didn't boot, so I tried to restore backup with twrp. Now no power, no vibration. PC doesn't recognize it. I wonder if it's on, and just has to run out of power, to be able to boot back to recovery. I thought it was weird my twrp backup didn't take very long. Any other advice? I got mine Verizon unlocked refurbished off amazon.
---------- Post added at 07:30 PM ---------- Previous post was at 06:53 PM ----------
perfectswanson said:
I tried to install a custom rom, and it didn't boot, so I tried to restore backup with twrp. Now no power, no vibration. PC doesn't recognize it. I wonder if it's on, and just has to run out of power, to be able to boot back to recovery. I thought it was weird my twrp backup didn't take very long. Any other advice? I got mine Verizon unlocked refurbished off amazon.
Click to expand...
Click to collapse
I was able to get it to boot into twrp. Should be OK from here. Thank you.
perfectswanson said:
I tried to install a custom rom, and it didn't boot, so I tried to restore backup with twrp. Now no power, no vibration. PC doesn't recognize it. I wonder if it's on, and just has to run out of power, to be able to boot back to recovery. I thought it was weird my twrp backup didn't take very long. Any other advice? I got mine Verizon unlocked refurbished off amazon.
---------- Post added at 07:30 PM ---------- Previous post was at 06:53 PM ----------
I was able to get it to boot into twrp. Should be OK from here. Thank you.
Click to expand...
Click to collapse
Even i am facing the same issue on the Verizon unlocked phone. What did you do to get into twrp??
nikinnikin said:
Even i am facing the same issue on the Verizon unlocked phone. What did you do to get into twrp??
Click to expand...
Click to collapse
I'm sorry I should have responded sooner. I don't remember much, but I had a feeling that it was still running because it was warm so I left it alone for a couple hours to see if it would die and then I could try to boot it again it's exactly what I did but what was funny was that it still had battery life when I turned it back on I hope you had some some luck.
nikinnikin said:
Even i am facing the same issue on the Verizon unlocked phone. What did you do to get into twrp??
Click to expand...
Click to collapse
Son of a gun. I did it again! Today. I followed a guide telling me to uninstall magisk with twrp before flashing 9.0. Now I have the same problem again. Goddamn TWRP. It told me no OS installed. Then I realized I forgot to put the magisk uninstaller file on my Verizion Pixel XL. Last time I just let my phone sit for a few hours or so, and it boot again. Not sure if it needs to run out of power, so it can boot again or what. Do you remember what you did when it happened to you?
perfectswanson said:
Son of a gun. I did it again! Today. I followed a guide telling me to uninstall magisk with twrp before flashing 9.0. Now I have the same problem again. Goddamn TWRP. It told me no OS installed. Then I realized I forgot to put the magisk uninstaller file on my Verizion Pixel XL. Last time I just let my phone sit for a few hours or so, and it boot again. Not sure if it needs to run out of power, so it can boot again or what. Do you remember what you did when it happened to you?
Click to expand...
Click to collapse
I couldnt switch it on at all. I'm planning to take it to Ubreakifix store, I guess they are the official google pixel repair people.
nikinnikin said:
Even i am facing the same issue on the Verizon unlocked phone. What did you do to get into twrp??
Click to expand...
Click to collapse
nikinnikin said:
I couldnt switch it on at all. I'm planning to take it to Ubreakifix store, I guess they are the official google pixel repair people.
Click to expand...
Click to collapse
You gotta be kidding me. Last time I left the phone alone, and my hunch was that it would run out of power, and then you can atleast get into the bootloader. I fixed it before. I wish I could get a hold of software those guys use to repartition, or however they do it. We have Pixel 3 leaks, but no repair software. All I did was install TWRP, and it said no OS installed. It just kept booting up into TWRP. Then I switched slots to see if that would change it, but I think that might have been what screwed it up.
---------- Post added at 01:37 PM ---------- Previous post was at 01:36 PM ----------
What version of TWRP did you use?
---------- Post added at 01:50 PM ---------- Previous post was at 01:37 PM ----------
I just got back into the bootloader. After a dozen times I just held down and power for like five seconds. Should I try recovery and try to remove Magisk, or should I just try to flash 9.0?
---------- Post added at 01:53 PM ---------- Previous post was at 01:50 PM ----------
What I did this time that was different, and I don't know if this is what helped or what, but this time I plugged in headphones and held power and vol down.
Putting the headphones in worked, or maybe it was just a fluke, but it worked on the first try. I got into Bootloader, "fastboot boot twrp.img", then I flashed the magisk uninstaller zip, the booted back to bootloader, and did flash-all.bat. It said it failed on the vendor partition, but everything still works.