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 :/

[Q] Endless loop of restarts into recovery

hi everyone,
I am in a quite a pickle here. I tried updating my phone with ARHD43 and after doing it couldn't get the WIFI to turn on. I read a bit and found that this is becuase I do not have the latest firmware. So I tried going back to stock through RUU (flashed stock recovery and boot.img) and in the process flashed new recovery and boot images. Now the my phone keeps booting into stock recovery with the red triangle continuously and I can't boot into the OS. From recovery when I select apply from SD card I throws CID error and reboots into recovery again!
I cannot connect to fastboot so I am stuck bad. :crying:
did I brick my device? can I save it? I am S-ON with unlocked boot loader. region is .707
Appreciate your help.
<I have posted a similar question in the ARHD43 thread but haven't recevied a response so posting in here in the general forum again>

simplyaha said:
I cannot connect to fastboot so I am stuck bad. :crying:
Click to expand...
Click to collapse
This part is your biggest issue. As you know, you can't do much without fastboot.
Make sure you are in bootloader-fastboot mode when issuing fastboot commands. Try to uninstall and re-install fastboot drivers, a different USB post on your computer, even another computer.
Once you get fastboot working, it should be as simple as flashing TWRP again (bootloader must be unlocked) than installing the proper stock nandroid and stock recovery from the following thread (instructions on how to restore the nandroid in Post #3 of the thread, under Questions & Answer). Then OTA to Lollipop.
http://forum.xda-developers.com/showthread.php?t=2701376
---------- Post added at 09:34 AM ---------- Previous post was at 09:33 AM ----------
simplyaha said:
So I tried going back to stock through RUU (flashed stock recovery and boot.img) >
Click to expand...
Click to collapse
Why would you do this? You realize that boot.img is just the kernel (not a full ROM)?

redpoint73 said:
This part is your biggest issue. As you know, you can't do much without fastboot.
Make sure you are in bootloader-fastboot mode when issuing fastboot commands. Try to uninstall and re-install fastboot drivers, a different USB post on your computer, even another computer.
Once you get fastboot working, it should be as simple as flashing TWRP again (bootloader must be unlocked) than installing the proper stock nandroid and stock recovery from the following thread (instructions on how to restore the nandroid in Post #3 of the thread, under Questions & Answer). Then OTA to Lollipop.
http://forum.xda-developers.com/showthread.php?t=2701376
---------- Post added at 09:34 AM ---------- Previous post was at 09:33 AM ----------
Why would you do this? You realize that boot.img is just the kernel (not a full ROM)?
Click to expand...
Click to collapse
thank you for replying.
I have have fast boot on my pic and it is working fine. I have used it to install custom rom on my wife's phone and my phone earlier. the problem is I am not able to get into the boot loader and push commands to my phone through fastboot or adb.
my plan was to actually run RUU and update to stock. I couldn't find the RUU for my 707 M8. I read somewhere that to make this work I should run RUU and extract and flash the boot.img it stores in the temporary folder on the PC. I also saved the stock rom file and was planning to flash that through recovery. but I cannot do that now because I am stuck in recovery.
any idea how I can get into boot loader.. this should give me a lot of options to fix my phone.

simplyaha said:
thank you for replying.
I have have fast boot on my pic and it is working fine. I have used it to install custom rom on my wife's phone and my phone earlier. the problem is I am not able to get into the boot loader and push commands to my phone through fastboot or adb.
any idea how I can get into boot loader.. this should give me a lot of options to fix my phone.
Click to expand...
Click to collapse
To get into bootloader, hold down power and vol up for several seconds (maybe up to 10 seconds or more). Once the screen goes black to reboot, immediately let go of both those buttons, and just hold vol down. Keep holding vol down until bootloader appears. If you fail to get into bootloader, you simply started holding vol down too late, or let go of it too early. Just repeat until you get it right.
Fastboot command only work in fastboot mode. adb commands will only work in OS or in recovery. So if you try to issue adb commands in bootloader or bootloader-fastboot modes, it won't work.
simplyaha said:
my plan was to actually run RUU and update to stock. I couldn't find the RUU for my 707 M8. I read somewhere that to make this work I should run RUU and extract and flash the boot.img it stores in the temporary folder on the PC. I also saved the stock rom file and was planning to flash that through recovery. but I cannot do that now because I am stuck in recovery.
Click to expand...
Click to collapse
Pulling files from another CID's RUU is not the proper way to restore to stock. I linked the proper thread with your stock ROM (which also includes boot.img) and stock recovery for your CID.
Plus, the stock ROM and recovery you restore has to match your firmware number, as indicated as OS number on bootloader screen, or main version on getvar all.

redpoint73 said:
To get into bootloader, hold down power and vol up for several seconds (maybe up to 10 seconds or more). Once the screen goes black to reboot, immediately let go of both those buttons, and just hold vol down. Keep holding vol down until bootloader appears. If you fail to get into bootloader, you simply started holding vol down too late, or let go of it too early. Just repeat until you get it right.
Fastboot command only work in fastboot mode. adb commands will only work in OS or in recovery. So if you try to issue adb commands in bootloader or bootloader-fastboot modes, it won't work.
Pulling files from another CID's RUU is not the proper way to restore to stock. I linked the proper thread with your stock ROM (which also includes boot.img) and stock recovery for your CID.
Plus, the stock ROM and recovery you restore has to match your firmware number, as indicated as OS number on bootloader screen, or main version on getvar all.
Click to expand...
Click to collapse
I did try this combination to get into boot loader but I couldn't successfully do that. I had also tried Hold power then immediately volume up and down at same time. When phone powers off release the volume up button.
I will try again and reply.
I couldn't find the 707 RUU anywhere on the web.. please share the link with me if you got it. I hope I get it into boot loader..

simplyaha said:
I did try this combination to get into boot loader but I couldn't successfully do that. I had also tried Hold power then immediately volume up and down at same time. When phone powers off release the volume up button.
Click to expand...
Click to collapse
You're making it more complicated than it needs to be. Stop trying other button combos, and just do it they way I said previously, this works every time as long as you don't start pressing vol down too late (it has to be while the screen is still black before the HTC logo screen appears - you have about 3 seconds which is plenty of time) or don't let go of vol down too early (don't let go until the bootloader screen appears - should only take a second).
If it doesn't work, its pilot error.
simplyaha said:
I couldn't find the 707 RUU anywhere on the web.. please share the link with me if you got it. I hope I get it into boot loader..
Click to expand...
Click to collapse
Only if you promise to stop messing around with incorrect processes, like trying to pull the recovery and boot.img out of the RUU.

redpoint73 said:
You're making it more complicated than it needs to be. Stop trying other button combos, and just do it they way I said previously, this works every time as long as you don't start pressing vol down too late (it has to be while the screen is still black before the HTC logo screen appears - you have about 3 seconds which is plenty of time) or don't let go of vol down too early (don't let go until the bootloader screen appears - should only take a second).
If it doesn't work, its pilot error.
Only if you promise to stop messing around with incorrect processes, like trying to pull the recovery and boot.img out of the RUU.
Click to expand...
Click to collapse
yeah.. i guess I tried all those random things because I am not very clear on all the processes.. but I am learning :victory:
yes, no more messing around, promise.. :angel:

simplyaha said:
yeah.. i guess I tried all those random things because I am not very clear on all the processes.. but I am learning
Click to expand...
Click to collapse
Yeah, stop doing that (trying random things). You can get yourself in a lot of trouble by "experimenting". Stick to proven solutions provided by knowledgeable XDA members.
Here is a link to the 4.19.707 RUU: http://forum.xda-developers.com/showpost.php?p=61886163&postcount=15
I only know of this, since xunholyx linked to it last week while we were helping another 707 owner. I take no responsibility for it. Just linking you to it by request.

redpoint73 said:
Yeah, stop doing that (trying random things). You can get yourself in a lot of trouble by "experimenting". Stick to proven solutions provided by knowledgeable XDA members.
Here is a link to the 4.19.707 RUU: http://forum.xda-developers.com/showpost.php?p=61886163&postcount=15
I only know of this, since xunholyx linked to it last week while we were helping another 707 owner. I take no responsibility for it. Just linking you to it by request.
Click to expand...
Click to collapse
ccol thank! I will try this tonight and share the outcome.. :good:

eureka! got my phone up and running now. the ruu was perfect. but got my memory card messed up (showing as raw format on the pc). gotta look for a solution for this now :banghead:
but my phone is back! thank you for all the help. much appreciated. :thumbup:
Sent from my HTC One_M8 using XDA Free mobile app

HTC One m8 doesn't boot

So I recently got a European M8 and thought I would root it which turned out to be a bad idea. To start off with, it didn't root properly anyway so i carried on using it. Today I wanted to recover it back to stock (When I got it out of the box) I did a command using fastboot which was along the lines of fastboot boot boot.img but now my HTC will launch the screen displaying that it is a build for development purposes only and then it goes to a black screen but still turned on. It seems to me like there is no Operating System for the phone to boot from.
PLEASE HELP ME
Issue Solved - 22/01/16

ChiefMustardo said:
So I recently got a European M8 and thought I would root it which turned out to be a bad idea. To start off with, it didn't root properly anyway so i carried on using it.
Click to expand...
Click to collapse
Hard to help, if we don't know exactly what you did. Try to explain in detail (or as best you can) the exact steps (including file names, version numbers, etc.) of what you performed.
ChiefMustardo said:
I did a command using fastboot which was along the lines of fastboot boot boot.img
Click to expand...
Click to collapse
Again, hard to tell what the issue is, if we don't know exactly what you did.
Are you sure you didn't do fastboot flash? I don't think you would do anything permanent with the command fastboot boot.
What exactly were you trying to boot/flash with this command? What was the file name, where did you get it from, and what was the exact intent?
Did you get this idea from a thread or guide?
ChiefMustardo said:
but now my HTC will launch the screen displaying that it is a build for development purposes only and then it goes to a black screen but still turned on. It seems to me like there is no Operating System for the phone to boot from.
Click to expand...
Click to collapse
If you hold power + vol up for a long time (30 seconds or more) does the phone reboot? Then what, black screen again?
Do Power + vol up again. The moment the screen goes dark (but before the HTC logo screen with the red text warning) let go of those buttons, and only hold power down; and don't let go until you see the bootloader screen. If this fails, try again, you probably just got the timing wrong (started pressing vol down too late, or let go of it too early).
Once in bootloader, select fastboot (if not in that mode already) using vol keys, then confirm with power button. Connect to computer and do: fastboot getvar all
Post the getvar output (delete IMEI and serial numbers before you post).

Again, i am really sorry but i do not understand what i did. It asked me to flash the ROM Update Utility and then use fastboot boot boot.img which then screwed it up and yes when i boot up and reboot it just goes to a black screen.
Here is the info:

ChiefMustardo said:
Again, i am really sorry but i do not understand what i did.
Click to expand...
Click to collapse
I seriously doubt that you can't remember any of the steps you did to try to root it.
Just sounds like you are too lazy to type. So why should I put forth more effort than you; when you are the one that wants help?
Describe as best you can, that is all I ask.
ChiefMustardo said:
It asked me to flash the ROM Update Utility and then use fastboot boot boot.img which then screwed it up and yes when i boot up and reboot it just goes to a black screen.
Click to expand...
Click to collapse
Do you have a file in your fastboot folder (wherever fastboot.exe is located) what is actually named boot.img?
And you really can't remember if you got this idea from a thread? You had to come up with it somehow.
What were you even trying to do here? What did you think the command would do?
Again, either you are just being lazy, evasive, or got hit on the head to cause amnesia; if you can't answer the questions.

So I was looking for tutorials on how to root it and I cam across a program (cannot remember the name) which was designed to root it with a few clicks of buttons ect. I already new how to unlock the boot-loader because I owned a HTC desire 510. I went back onto my phone it has twrp installed but I use root checker and it says that proper root access is not granted and I have tried to use SuperSU but I got the binary issue so I gave up. It was working fine but today I decided I wanted to revert it back to stock again but did something which completely messed it up.
Also, i decided i wanted to restore it because if it broke and i needed it to be repaired it would void my warranty. I was thinking when i reset the RUU it would make it stock again but it did not.

Now, that's more like it!
ChiefMustardo said:
So I was looking for tutorials on how to root it and I cam across a program (cannot remember the name) which was designed to root it with a few clicks of buttons ect.
Click to expand...
Click to collapse
An Android app, or PC program?
Either way, one-click type root apps don't work on HTC devices. PC based toolkits worked at one time, but were never updated to support the recent software builds (outdated TWRP versions fail on Lollipop, and outdated SuperSU versions fail).
ChiefMustardo said:
S I decided I wanted to revert it back to stock again but did something which completely messed it up.
Click to expand...
Click to collapse
What did you think you were doing with the fastboot command (fastboot boot boot.img)?
One thing I can say for sure: Don't try mods, fastboot commands, etc. unless you know exactly what you are doing (such as following reputable instructions to the letter). The command you did just isn't right. You either got it from a bad source, or you decided to improvise or experiment (really bad idea). You made the issue much worse than it was to begin with (probably just needed to flash the updated SuperSU zip, maybe also update TWRP).
---------- Post added at 04:00 PM ---------- Previous post was at 03:58 PM ----------
You also didn't answer the question:
redpoint73 said:
Do you have a file in your fastboot folder (wherever fastboot.exe is located) what is actually named boot.img?
Click to expand...
Click to collapse

It was a computer application and i thought the command would reboot it with a different kernal/firmware thing. But yeah i followed the instructions like an idiot and messed up my phone and no i don't anymore because i deleted it

ChiefMustardo said:
i thought the command would reboot it with a different kernal/firmware thing.
Click to expand...
Click to collapse
Fastboot boot means you are trying to remote boot something without flashing it. A boot.img isn't bootable. I've only seen this done with recovery.img
I think you meant to do: fastboot flash boot boot.img
The one different word makes a huge difference. The action is to flash, not boot. The "boot" is the location of where to flash to.
Also, even if you properly flashed boot.img, this is just the kernel, and wouldn't change much. To return to stock, you want to flash a full ROM. And kernel, ROM and firmware are not interchangeable terms, so don't for a second think they are.

Ok. Is it possible though to revert it back to stock and if yes, do you think you can help me?

Do the fastboot command: fastboot oem lock. Then download the 4.16.401.10 RUU from the following thread, and run it from PC: http://forum.xda-developers.com/showthread.php?t=2701376
Your alternative is to restore the proper stock TWRP backup. While the relevant files are on that same link, you'll find clearer instruction on the following thread: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860

It now says Relocked then underneath security warning. Is that good?

ChiefMustardo said:
It now says Relocked then underneath security warning. Is that good?
Click to expand...
Click to collapse
The security warning just means you altered something in the stock software (root, kernel, etc.). It doesn't matter, as the RUU will write all partitions to factory condition.

Will i have to re unlock the boot-loader for the RUU.exe to work?

ChiefMustardo said:
Will i have to re unlock the boot-loader for the RUU.exe to work?
Click to expand...
Click to collapse
NO. Its required to be LOCKED or RELOCKED to run RUU.
Its the only reason I told you to relock it.

Ok because i had the program running all day with it re-locked but it didn't do anything so i am back to square one

ChiefMustardo said:
Ok because i had the program running all day with it re-locked but it didn't do anything so i am back to square one
Click to expand...
Click to collapse
What does your PC screen say? Is the RUU stuck sending?
You probably just need to disconnect the phone and start again. RUU just gets stuck sometimes. It shouldn't take any more than 5 or 10 minutes.

Yeah it says updating 0 out of 7 sending ........................

ChiefMustardo said:
Yeah it says sending 0 out of 7
Click to expand...
Click to collapse
It should be safe to just disconnect the phone and start over with the RUU again.

This is what comes up

It send that 1 had been sent then it said error

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

L24 completely bricked. Only goes to erecovery. What are the options?

Geez i wish haahwhahai would have a working erecovery. This is maddening.

I've been there before. I was able to use the method involving connecting / disconnecting the usb to get into fastboot, adb the recoveries, and reboot, being immediately prompted to factory restore. I don't know if that's helpful at all.

johncro13 said:
I've been there before. I was able to use the method involving connecting / disconnecting the usb to get into fastboot, adb the recoveries, and reboot, being immediately prompted to factory restore. I don't know if that's helpful at all.
Click to expand...
Click to collapse
Do you have a link to this method of restoring kind sir?
Thanks!

If possible, turn the phone completely off.
Plug the USB cable into the phone
Hold vol down
Hold power and IMMEDIATELY plug the other end of the USB cable into the PC.
This should get you into fastboot. From here, you should be able to use ADB.
Here's the thread that helped me most.

johncro13 said:
If possible, turn the phone completely off.
Plug the USB cable into the phone
Hold vol down
Hold power and IMMEDIATELY plug the other end of the USB cable into the PC.
This should get you into fastboot. From here, you should be able to use ADB.
Here's the thread that helped me most.
Click to expand...
Click to collapse
What should i use after i'm in fastboot? I've downloaded the latest full firmware that's out there, but it seems to be corrupt.

lowspeed said:
What should i use after i'm in fastboot? I've downloaded the latest full firmware that's out there, but it seems to be corrupt.
Click to expand...
Click to collapse
Is your bootloader unlocked?

smokinjoe2122 said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
Relocked

lowspeed said:
Relocked
Click to expand...
Click to collapse
I'm not sure how much you can do if the device is locked...A guess a few questions (In my tech support voice):
1.) How did it get to that point?
2.) Can you re-open the bootloader, and if you can, are you opposed to it?
3.) What was the last firmware you installed on it?

smokinjoe2122 said:
I'm not sure how much you can do if the device is locked...A guess a few questions (In my tech support voice):
1.) How did it get to that point?
2.) Can you re-open the bootloader, and if you can, are you opposed to it?
3.) What was the last firmware you installed on it?
Click to expand...
Click to collapse
1) I don't recall.
2) I could probably unlock it again. i'll give it a try.
3) it had some weird restore that i used, but that rom didn't have any update option.
I must sound retarded....

lowspeed said:
1) I don't recall.
2) I could probably unlock it again. i'll give it a try.
3) it had some weird restore that i used, but that rom didn't have any update option.
I must sound retarded....
Click to expand...
Click to collapse
Well most of the time, if it's a software issue, it's fixable. I don't know as much about this phone as I'd like, but I do know there's update packages out there you can use to your benefit if you can get the bootloader unlocked. I believe the Update.APP can even be unzipped or decompiled to get the main imgs from it, such as boot, recovery, and system.

im gonna go ahead and throw this out there. i just returned from the hardest brick i have ever done. i managed to make it so the phone wouldnt boot it would bootloop twice and go to erecovery and fail to restore. then i tried flashing the stock img's extracted from the update.app inside twrp and that made it worse. the screen went completely black and wouldnt do ****, the computer recognized it in bootloader mode but i couldnt flash a single thing as it would say i didnt have permission to or something like that(acting as if the bootloader was locked even though it was unlocked, or locked frp) i was about to give up and put my sim card back in my nexus as no matter what i did i couldnt get the screen to even turn on.
Well i found a post on the mate 9 sub-forum about someone who did the same thing and fixed it with dc-phoenix but costed him 18$, i decided 18 was worth it if it meant i had a working phone. and sure enough 5 minutes after paying and clicking flash update.app in the software it was up and running. now i have no idea how dc-phoenix can flash images when adb couldnt...but it works. if your out of options i would 100% say try it as 18$ is much better than a new phone.
---------- Post added at 07:55 PM ---------- Previous post was at 07:54 PM ----------
something i did notice as the software did the commands to flash each image i noticed it started its commands with some kind of backdoor command. so maybe they know a backdoor to bypass a locked bootloader/frp

darkmage1991 said:
im gonna go ahead and throw this out there. i just returned from the hardest brick i have ever done. i managed to make it so the phone wouldnt boot it would bootloop twice and go to erecovery and fail to restore. then i tried flashing the stock img's extracted from the update.app inside twrp and that made it worse. the screen went completely black and wouldnt do ****, the computer recognized it in bootloader mode but i couldnt flash a single thing as it would say i didnt have permission to or something like that(acting as if the bootloader was locked even though it was unlocked, or locked frp) i was about to give up and put my sim card back in my nexus as no matter what i did i couldnt get the screen to even turn on.
Well i found a post on the mate 9 sub-forum about someone who did the same thing and fixed it with dc-phoenix but costed him 18$, i decided 18 was worth it if it meant i had a working phone. and sure enough 5 minutes after paying and clicking flash update.app in the software it was up and running. now i have no idea how dc-phoenix can flash images when adb couldnt...but it works. if your out of options i would 100% say try it as 18$ is much better than a new phone.
---------- Post added at 07:55 PM ---------- Previous post was at 07:54 PM ----------
something i did notice as the software did the commands to flash each image i noticed it started its commands with some kind of backdoor command. so maybe they know a backdoor to bypass a locked bootloader/frp
Click to expand...
Click to collapse
Which files did you flash in DC Phoenix?
Thanks for posting this!

JDBarlow said:
Which files did you flash in DC Phoenix?
Thanks for posting this!
Click to expand...
Click to collapse
downloaded the latest update on firmware finder for my device(l24) and used winrar to pull the update.app from the zip. then you select that in dc phoenix to do the restore/flash