Develop Bugs

Help phone stuck at boot screen

Hello. I just tried to unlock the bootloader on on Verizon Galaxy nexus. Now it's stuck at the bootscreen with the lock image. I did a search and couldn't find a exact answer for my issue. I hope I haven't bricked my phone. Anyway, any help would be appreciated.
I wasn't trying to root just unlock the bootloader. It appeared everything went ok but, now I'm stuck. I used the same method for unlocking the bootloader on my GSM G-nex and it worked.
I know I've done something wrong or this may be something simple. I just need help so I can use my phone.

are you able to boot into the bootloader? if so you should be able to recover and can't worry a little less.

same thing here... I posted a request for a LTE boot.img since can still get into the bootloader

Goat_For_Sale said:
are you able to boot into the bootloader? if so you should be able to recover and can't worry a little less.
Click to expand...
Click to collapse
No I don't believe I can. When I type fastboot it just says "waiting on device" I can hold the volume down & power buttons and get to the screen were it says "start" at the top and below that "downloding"

Yea, that was what I was eluding too, The device just came out and google released the GSM image. I am sure that it will appear online in the near future.
if you are able to get into the bootloader does it say that its unlocked ? is your google splash screen showing the unlocked padlock ? you could also try fastboot flash recovery to get cwm on there and provide additional potential solutions.
---------- Post added at 11:40 AM ---------- Previous post was at 11:39 AM ----------
qnet said:
No I don't believe I can. When I type fastboot it just says "waiting on device" I can hold the volume down & power buttons and get to the screen were it says "start" at the top and below that "downloding"
Click to expand...
Click to collapse
That is download mode used for odin.
hold BOTH volumn buttons and power to get into the bootloader/fastboot

Goat_For_Sale said:
Yea, that was what I was eluding too, The device just came out and google released the GSM image. I am sure that it will appear online in the near future.
if you are able to get into the bootloader does it say that its unlocked ? is your google splash screen showing the unlocked padlock ? you could also try fastboot flash recovery to get cwm on there and provide additional potential solutions.
---------- Post added at 11:40 AM ---------- Previous post was at 11:39 AM ----------
That is download mode used for odin.
hold BOTH volumn buttons and power to get into the bootloader/fastboot
Click to expand...
Click to collapse
Yeah, when I did the procedure it said that it was unlocked. Everything looked ok , it booted show the unlock symbol under Google. It then went to the colorful animation and was stuck there. At that time I pulled the battery and, it's been stuck at the screen showing google and the unlock image.

qnet said:
Yeah, when I did the procedure it said that it was unlocked. Everything looked ok , it booted show the unlock symbol under Google. It then went to the colorful animation and was stuck there. At that time I pulled the battery and, it's been stuck at the screen showing google and the unlock image.
Click to expand...
Click to collapse
you should have let the animation run for like 10 minutes the phone has to rebuild the first boot can take like 15 minutes sometimes.
try booting into the bootloader see if that works still

Sorry I wasn't paying attention and didn't read the part were you told me how to get to the fastboot screen. I'm there now. Can I just relock or fix the bootloader from problem there? It shows it unlocked at the fastboot screen.

qnet said:
Sorry I wasn't paying attention and didn't read the part were you told me how to get to the fastboot screen. I'm there now. Can I just relock or fix the bootloader from problem there? It shows it unlocked at the fastboot screen.
Click to expand...
Click to collapse
you could try fastboot oem lock and see if that works but if the phone wasn't booting i don't know if that will fix it but worth a shot.
try it out and see. it shouldn't do any harm to try

I had the issue with the failure to boot up after doing the fastboot oem unlock (I had to use the pda net drivers to get my device recognized to get even that far). I did a lot of things like pulling the battery, locking again and then unlocking and nothing worked until I went here http://rootzwiki.com/topic/11732-galaxy-nexus-root-procedure-adb-method/, then downloaded the files following their directions and doing the fastboot boot boot.img command. It took a LONG time to boot up, but it did boot finally.

GirLuvsDroid said:
I had the issue with the failure to boot up after doing the fastboot oem unlock (I had to use the pda net drivers to get my device recognized to get even that far). I did a lot of things like pulling the battery, locking again and then unlocking and nothing worked until I went here http://rootzwiki.com/topic/11732-galaxy-nexus-root-procedure-adb-method/, then downloaded the files following their directions and doing the fastboot boot boot.img command. It took a LONG time to boot up, but it did boot finally.
Click to expand...
Click to collapse
Thank you, I'll try that.

I have another question. One of the selections on the fastboot screen is recovery mode. Can I try that or is this something were you have to have a rom stored on a sd-card?

qnet said:
I have another question. One of the selections on the fastboot screen is recovery mode. Can I try that or is this something were you have to have a rom stored on a sd-card?
Click to expand...
Click to collapse
you could download the recovery image from
http://forum.xda-developers.com/showthread.php?t=1392336
then when connected in fast boot flash it with
fastboot flash recovery recovery.img
(rename the file from the linked thread to recovery.img)
this should write your custom recovery partition.
once you have that though you are still not going to be able to boot but it would allow you to flash a nandroid backup if someone made one for you or a LTE based rom
EDIT: you could also try a factory data reset and wipe dalvk cache from withing cwm. that may fix your boot problem

I had this problem, too.
I downloaded Clockwork Recovery and used 'fastboot boot LTErecovery_cwr.img' to boot into it, I wiped data and cache / factory reset and then rebooted. It rebooted twice, but after ten minutes or so I was back to the ICS Welcome screen. All of the files I'd put on my internal storage were wiped (during the oem unlock, I assume) but I'm in the stock rom but Superuser was installed and I have root access.
Hope it helps.
EDIT: looks like this is the same thing Goat_For_Sale posted above, but his command flashes CWM where mine temporarily boots into it. Since most of us will be installing CWM anyway I'd recommend using his command instead.

mixedlemon said:
I had this problem, too.
I downloaded Clockwork Recovery and used 'fastboot boot LTErecovery_cwr.img' to boot into it, I wiped data and cache / factory reset and then rebooted. It rebooted twice, but after ten minutes or so I was back to the ICS Welcome screen.
Hope it helps.
Click to expand...
Click to collapse
where did you get the lterecovery_cwr.img ? could you link to it please

I linked to the thread in my post, but here's a link to the mediafire upload from that thread: http://www.mediafire.com/?mdf0mtacskob5yg

mixedlemon said:
I linked to the thread in my post, but here's a link to the mediafire upload from that thread: http://www.mediafire.com/?mdf0mtacskob5yg
Click to expand...
Click to collapse
Thanks, my bad I didn't realize you were refering to the recovery image, thought it was the boot image for the LTE device.

Goat_For_Sale said:
Thanks, my bad I didn't realize you were refering to the recovery image, thought it was the boot image for the LTE device.
Click to expand...
Click to collapse
Ahh no problem.
I got pretty worried for a second that I'd already broke my shiny new Nexus, so I'm really hoping I can help out someone else that had the same problem.

Solved
I believe it's fixed now. I use the method that GirLuvsDroid posted from the Rootzwiki forum. Once it rebooted, I stopped there and didn't root the phone. I was just happy to get it booted.
It's downloading all my apps and settings now. Thanks to everyone who tried to help me, I really appreciate. This was a good learning experience for me.

qnet said:
I believe it's fixed now. I use the method that GirLuvsDroid posted from the Rootzwiki forum. Once it rebooted, I stopped there and didn't root the phone. I was just happy to get it booted.
It's downloading all my apps and settings now. Thanks to everyone who tried to help me, I really appreciate. This was a good learning experience for me.
Click to expand...
Click to collapse
So you were just able to go through the Rootzwiki method? Were you stuck at "Downloading...Do not turn off target !!" screen when you went to boot screen originally? My device still can't be detected :/

Help!!!! Bricked one m9! No fastboot commands, no adb, just a blue screen!

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...

Boot Verification Failed

Hey all, I really have no knowledge when it comes to phones, so any help would be appreciated.
I have been trying to root my LG G3 for a few days now, but it just wont happen. I have tried PurpleDrake and ioroot and end up with the same error every time whilst the phone is restarting. As the screen is black and attempts to boot, in the top right of the screen, the message "Verification boot failed! cause- MISMATCH_SIG_LEN" and then the phone will just go to a black screen while the LED alternates blue and red. This also happens when I try to enter stock recovery. I know I have the latest ADB drivers installed and the right drivers for my phone, so that can't be it. My G3 is a D852 with SV 30b on Marshmallow, my carrier is Bell. Thanks.

HaiM80 said:
Hey all, I really have no knowledge when it comes to phones, so any help would be appreciated.
I have been trying to root my LG G3 for a few days now, but it just wont happen. I have tried PurpleDrake and ioroot and end up with the same error every time whilst the phone is restarting. As the screen is black and attempts to boot, in the top right of the screen, the message "Verification boot failed! cause- MISMATCH_SIG_LEN" and then the phone will just go to a black screen while the LED alternates blue and red. This also happens when I try to enter stock recovery. I know I have the latest ADB drivers installed and the right drivers for my phone, so that can't be it. My G3 is a D852 with SV 30b on Marshmallow, my carrier is Bell. Thanks.
Click to expand...
Click to collapse
Switch of your phone then hold volume up &connect your phone with pc by using usb cable.....
See what happen? Able to enter download mode..

Anik49 said:
Switch of your phone then hold volume up &connect your phone with pc by using usb cable.....
See what happen? Able to enter download mode..
Click to expand...
Click to collapse
Sorry for being so dumb, but could you clarify what that will do for me?

HaiM80 said:
Sorry for being so dumb, but could you clarify what that will do for me?
Click to expand...
Click to collapse
If you able to do that than you can flash your phone again.....for more clarify you have to install your phone software again to solve this issue also you cant flash v30b again right now you have to flash any other version to boot up your phone.

Anik49 said:
If you able to do that than you can flash your phone again.....for more clarify you have to install your phone software again to solve this issue also you cant flash v30b again right now you have to flash any other version to boot up your phone.
Click to expand...
Click to collapse
Ah, sorry for the confusion, but my phone starts just fine. I should have clarified in the original question that i can just hold the power button and volume down button and my phone will restart like nothing happened. Its only when root programs try to reboot into recovery and when I try to do it manually. Again, sorry about that

HaiM80 said:
Ah, sorry for the confusion, but my phone starts just fine. I should have clarified in the original question that i can just hold the power button and volume down button and my phone will restart like nothing happened. Its only when root programs try to reboot into recovery and when I try to do it manually. Again, sorry about that
Click to expand...
Click to collapse
You have working twrp....if you want root in mm you need twrp first...
---------- Post added at 01:13 AM ---------- Previous post was at 01:06 AM ----------
HaiM80 said:
Ah, sorry for the confusion, but my phone starts just fine. I should have clarified in the original question that i can just hold the power button and volume down button and my phone will restart like nothing happened. Its only when root programs try to reboot into recovery and when I try to do it manually. Again, sorry about that
Click to expand...
Click to collapse
Look here you get more info
http://forum.xda-developers.com/lg-g3/general/lg-g3-d852-telus-koodo-marshmallow-t3348286

And that's where I get confused, because when I look up how to get twrp, I am told I need root first. I have temp rooted before and used flashify to try and flash a twrp but then on reboot I would get the error.

HaiM80 said:
And that's where I get confused, because when I look up how to get twrp, I am told I need root first. I have temp rooted before and used flashify to try and flash a twrp but then on reboot I would get the error.
Click to expand...
Click to collapse
Use autorec not flashify.....but be sure you install autorec for mm version also for d852.....go to this page you will get all your file http://forum.xda-developers.com/lg-g3/development/canadian-d852-stock-bumped-rooted-rom-t3056843

Anik49 said:
Use autorec not flashify.....but be sure you install autorec for mm version also for d852.....go to this page you will get all your file http://forum.xda-developers.com/lg-g3/development/canadian-d852-stock-bumped-rooted-rom-t3056843
Click to expand...
Click to collapse
Thanks a lot for your help Anik! I can be really dumb sometimes and the fact that I can't think straight at the moment doesn't help. Seems like the main problem would be is that I was downloading Autorec of the play store, which is for lollipop. Should have seen that coming with the logo... Again, thanks!

TWRP 3.1.1-0

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

Your device is corrupt. It can't be trusted and may not work properly :(

https://forum.xda-developers.com/showpost.php?p=74525204&postcount=16
How do i fix this? My phone is working and i can use it but when i boot the phone i get the "your device is corrupt" I cannot get fastboot to boot to twrp so i cannot root.

So to be extremely polite, you posted your issue(s) in different posts and different sub-forums. Everyone has been extremely helpful but it seems you are doing something wrong somewhere. Please start from scratch with the factory images and the newest platform tools and follow carefully the guide by Nathanchance
https://forum.xda-developers.com/showthread.php?t=3702418
Then if doesn't work read some then come back with screen caps, detailed procedure, failures....etc.
Also it seems your are trying to use TWRP to root, since it's in beta and messing things up for you, root without it. And don't use any toolboxes.
Sent from my Pixel 2 XL using Tapatalk

equlizer said:
https://forum.xda-developers.com/showpost.php?p=74525204&postcount=16
How do i fix this? My phone is working and i can use it but when i boot the phone i get the "your device is corrupt" I cannot get fastboot to boot to twrp so i cannot root.
Click to expand...
Click to collapse
I had this issue when using outdated ADB to flash Google factory image. If you did this, redo with updated ADB software.
Sent from my Pixel 2 XL using XDA Labs

---------- Post added at 03:39 PM ---------- Previous post was at 03:39 PM ----------
equlizer said:
https://forum.xda-developers.com/showpost.php?p=74525204&postcount=16
How do i fix this? My phone is working and i can use it but when i boot the phone i get the "your device is corrupt" I cannot get fastboot to boot to twrp so i cannot root.
Click to expand...
Click to collapse
Update your ADB software files - that seems to be the issue.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip

I'm using version 27 from November already

equlizer said:
https://forum.xda-developers.com/showpost.php?p=74525204&postcount=16
How do i fix this? My phone is working and i can use it but when i boot the phone i get the "your device is corrupt" I cannot get fastboot to boot to twrp so i cannot root.
Click to expand...
Click to collapse
I had This same issue but got it solved using Skipsoft and Deuces tools after about 5 tries
I had to factory reset and delete everything on the phone
You should try these tools

if the message is displayed on your phone, at each boot, the ONLY way to fix it, is to relock your bootloader.

I fixed it!!!!!!!!!! If anyone gets the red triangle and its saying "your device is corrupt, hit power button to continue", flash the boot img from the rom you are currently on. That's it!!
I got twrp installed and magisk installed now.

I'm getting that same exact error. My phone will boot up but I am definitely getting "your device is corrupt" in red letters when I start it. My bootloader is not unlocked because I have the Verizon version. Any ideas?

ClassickWORLD said:
I'm getting that same exact error. My phone will boot up but I am definitely getting "your device is corrupt" in red letters when I start it. My bootloader is not unlocked because I have the Verizon version. Any ideas?
Click to expand...
Click to collapse
Did you do anything to cause it, or did it just show up on it's own??

Just took an OTA update. But maybe the person who had it before me did something. I dont know. I don't see how. The bootloader is still locked.