Develop Bugs

[Q] Stuck on sony logo

Hi,
My phone is stuck at sony logo, after install a custom rom (RomAur). I have locked BL, and I put my phone into fastboot mode and im tryng to fix it with flashtool (pc recognize the phone). Can I flash a rom in fastboot? it doesn´t work into flashmode. Any help? (As you can see im new in this topics...)

Did you try download stock ftf - run flashtool - choose the ftf, when ask for the phone ... push the off button for 5s (behind the phone next to sd slot), then put the phone in flash mode (vol. down) - connect your usb, phone should flash.
Sent from my C6506 using Tapatalk 2

Pablo256 said:
Hi,
My phone is stuck at sony logo, after install a custom rom (RomAur). I have locked BL, and I put my phone into fastboot mode and im tryng to fix it with flashtool (pc recognize the phone). Can I flash a rom in fastboot? it doesn´t work into flashmode. Any help? (As you can see im new in this topics...)
Click to expand...
Click to collapse
Every ZL/Z is meant to work in Flash Mode, just reset the phone by holding the OFF button on the back panel where the SD-card and SIM card are placed. Disconnect your phone from the computer, hold the OFF button until it vibrates THREE times (hold it for 3 seconds it vibrates twice (hard restart), hold for 5 it vibrates thrice(forced flashmode)) soon after plug in the phone into your computer (along with the proper drivers installed from Flashtool in (or wherever you installed it) C:/FlashTools/Drivers (these drivers are SOE-blah, ADB, and fast boot mainly located at the bottom.) Once you've accomplished this, head on over to the Android Development section download a FTF file and restore. If you wish to keep all your data try reinstalling RomAur with proper installation instructions, due to my lack of experience with that rom I cannot give you the best advice other than if you have CWM installed it's an option to constantly flash other roms/zips to possibly fix your scenario. Good luck!

I'll give you more details now, about my problem.
1.- My phone was OK (rooted and with CWM) running Hackit custom rom.
2.- I install RomAur, then on reboot the phone got stuck on sony logo (it means, sony logo, and then reboot, sony logo and then reboot, infinite loop). Pressing OFF button (back next to the SD) it restarts the phone but the infinite loop continues.
3.- I installed flashtool (drivers, etc)
4.- I run the phone and then pressing VOL DOWN and plugin the usb cable at the same time it puts on yellow light (i dont know what mode it is). Infinite loops stops, phone is off and battery charging icon is displayed.
5.- On yellow light then i disconnect the phone and then pressing VOL DOWN and reconnecting flashtool recognize it ("28/024/2013 20:24:13 - INFO - Device connected in flash mode"). No light on the phone. If i do the same but with VOL UP it runs fastboot (blue light).
6.-On flashmode, I press the flash device button (black beam icon), it ask for mode, i choose flashmode. Then i select the ftf. and flashtool displays
28/043/2013 20:43:29 - INFO - Preparing files for flashing
28/044/2013 20:44:07 - INFO - Device disconnected
And the infinite loop returns...
If i pressthe powe off button nothing happens, it vibrates only one time, every restart on the loop
HELP! and thanks for your answers

From your comments, get to your step 5. Meaning get your phone off. Run flashtool choose stock ftf when it asked for the phone. Holding Vol.Down plug in usb - this should reset your phone and get you going.
Sent from my C6506 using Tapatalk 2

[Q] I can't access Bootloader or Recovery PLEASE Help!

My HTC One M8 (Verizon) is seemingly bricked. My phone is rooted, S-Off, with the stock ROM. I have been trying to update to the latest OTA update by returning to stock. I had previously modified some entries in the Build.prop and Platform.xml. I knew those had to be default in order for the OTA to work. I had copied the original files and pasted them to my SD Card so that I could simply cut the modified versions, paste them to my SD Card, and cut the originals from my SD Card and put them in their corresponding system folders.
Upon a reboot something apparently went horribly wrong because all my phone does now is boot with the white screen and green HTC Logo, then the screen goes black. I have tried the typical Power Button + Volume Down but it won't enter the boot loader. The good news is that the USB port seems to still work for my windows computer recognizes a device connecting to it but it doesn't show up as an interactive device in windows explorer..if that makes sense.
Please Help!

SF-Echo18 said:
My HTC One M8 (Verizon) is seemingly bricked. My phone is rooted, S-Off, with the stock ROM. I have been trying to update to the latest OTA update by returning to stock. I had previously modified some entries in the Build.prop and Platform.xml. I knew those had to be default in order for the OTA to work. I had copied the original files and pasted them to my SD Card so that I could simply cut the modified versions, paste them to my SD Card, and cut the originals from my SD Card and put them in their corresponding system folders.
Upon a reboot something apparently went horribly wrong because all my phone does now is boot with the white screen and green HTC Logo, then the screen goes black. I have tried the typical Power Button + Volume Down but it won't enter the boot loader. The good news is that the USB port seems to still work for my windows computer recognizes a device connecting to it but it doesn't show up as an interactive device in windows explorer..if that makes sense.
Please Help!
Click to expand...
Click to collapse
When you connect it to the PC can you pick up the device with adb? If so, have you tried to run the command from adb to boot it into bootloader? adb devices ... if found, adb reboot bootloader
:fingers-crossed:

BerndM14 said:
When you connect it to the PC can you pick up the device with adb? If so, have you tried to run the command from adb to boot it into bootloader? adb devices ... if found, adb reboot bootloader
:fingers-crossed:
Click to expand...
Click to collapse
I'm not too familiar with ADB commands but I typed in "adb reboot recovery" and it said: "error: device not found" so even if my command was wrong it's still not detecting it. I also tried: "fastboot reboot bootloader" and it just says "waiting for device"
Also I feel like it's worth mentioning the phone is automatically rebooting every two minutes or so (haven't timed it exactly but it's a while). Still showing the green HTC Logo then the screen goes dim, then the screen turns off.

SF-Echo18 said:
I'm not too familiar with ADB commands but I typed in "adb reboot recovery" and it said: "error: device not found" so even if my command was wrong it's still not detecting it. I also tried: "fastboot reboot bootloader" and it just says "waiting on device for device"
Also I feel like it's worth mentioning the phone is automatically rebooting every two minutes or so (haven't timed it exactly but it's a while). Still showing the green HTC Logo then the screen goes dim, then the screen turns off.
Click to expand...
Click to collapse
Try holding volume UP + Power button, this simulates a "battery pull", just hold it in for a while it can take a while to "pull", when it's off try again booting into bootloader, volume DOWN + Power button.

BerndM14 said:
Try holding volume UP + Power button, this simulates a "battery pull", just hold it in for a while it can take a while to "pull", when it's off try again booting into bootloader, volume DOWN + Power button.
Click to expand...
Click to collapse
I held Volume Up + Power Button and it showed the white screen with the green HTC logo. I then released all buttons. Once the screen turned off I then held Volume Down + Power Button for two minutes straight and nothing happened.
Even though we haven't found a solution yet, I am appreciative of the help.

sounds like you never installed the htc drivers for your phone, hence your pc doesn't see the phone when you are doing ADB commands.
install the drivers for it, then try the ADB commands via your pc
and dont mess with the build prop or other system files unless you have a working back up and are 101% certain about what you are doing..

Just remember to change directory in command prompt to the folder where adb.exe is located.
I don't know why the device doesn't reboot into bootloader though when you hold volume down + power button, shouldn't have to hold it for 2minutes. Holding volume up + power button to simulate a "pull" should only take up to 20 seconds or so at most and pressing volume down + power will then immediately take you into bootloader mode, or at least it's supposed to.
Did you release the volume up / power combo when the screen went dead or before? Try holding it until the phone shuts off and then right away press volume down + power.
Sorry if I'm not answering right away though, busy eating, and will be here and away for the next hour or so while I get ready for work =o( once I leave for work I'll only be able to help some more after like 2 hours or so. Hopefully we can do something before then though =o)

wase4711 said:
sounds like you never installed the htc drivers for your phone, hence your pc doesn't see the phone when you are doing ADB commands.
install the drivers for it, then try the ADB commands via your pc
and dont mess with the build prop or other system files unless you have a working back up and are 101% certain about what you are doing..
Click to expand...
Click to collapse
You're right, I didn't install the drivers. I did so and ADB was able to recognize it and I was able to access the bootloader. Thank you everyone for your help. I won't be making the mistake again.

SF-Echo18 said:
You're right, I didn't install the drivers. I did so and ADB was able to recognize it and I was able to access the bootloader. Thank you everyone for your help. I won't be making the mistake again.
Click to expand...
Click to collapse
So you'll be able to fix it from here on then? I was just about to link this thread to you as well should you have gotten adb to work again, it's for the RUU for Verizon seeing as you said you're on Verizon.
But going by your response up there you might already know how to fix this issue further :good:

BerndM14 said:
So you'll be able to fix it from here on then? I was just about to link this thread to you as well should you have gotten adb to work again, it's for the RUU for Verizon seeing as you said you're on Verizon.
But going by your response up there you might already know how to fix this issue further :good:
Click to expand...
Click to collapse
Indeed I appreciate it, but I just finished installing the RUU ha. Hopefully this thread will be of use to someone in a similar circumstance in the future.

Share another method of getting into recovery mode on non-responsive blank screen
Hi,
I just want to share how I accessed recovery mode with the same build.prop issue but with S-ON (might work with S-Off too).
I found the solution from here:
http://forum.xda-developers.com/htc...ter-download-mode-t2853100/page2#post62490577
To get into recovery mode on a non-responsive blank screen, hold the power button and volume up button at the same time and then approximately after 10 seconds, switch from pressing the volume up to volume down button before the HTC logo white screen shows while still holding down the power button. After, a white boot screen will give an option to go into recovery mode.

Cant recognize phone in fastboot!! HELP!!

The phone is in bootlopp (i think).When i turn on appears android on groundb with the red triangle and a chinese word.This disappears and appears again,for an infinite time.Display stays turned on.Turning on in bootloader it works,but just in bootloader.If i try to enter in "Restart bootloader,"recovery,"normal boot"ecc it's in bootloop again.So i can access only bootloader at the moment.I want to reflash system,droidboot imgs ecc with fastboot but...tried to recognize phone on an old HP Compaq nx6110 with usb 2.0 and win7.installed on it adb drivers,adb and fast-tools.don't think zenf2 drivers are important at the moment,now should consider just the adb drivers cause i can access only bootloader.however i think zenf2 drivers are installed on it.nothing.phone no recognized by fastboot and no recognized by windows.consider that on a xp and 2.0 usb pc (with fastboot,adb,and adb drivers on it) phone is recognized by windows as Android-Phone but then windows says i've not the drivers for the installation (appears the drivers' choosing window).No asus driver on it,on the win7 pc there are!!

CenereZar said:
The phone is in bootlopp (i think).When i turn on appears android on groundb with the red triangle and a chinese word.This disappears and appears again,for an infinite time.Display stays turned on.Turning on in bootloader it works,but just in bootloader.If i try to enter in "Restart bootloader,"recovery,"normal boot"ecc it's in bootloop again.So i can access only bootloader at the moment.I want to reflash system,droidboot imgs ecc with fastboot but...tried to recognize phone on an old HP Compaq nx6110 with usb 2.0 and win7.installed on it adb drivers,adb and fast-tools.don't think zenf2 drivers are important at the moment,now should consider just the adb drivers cause i can access only bootloader.however i think zenf2 drivers are installed on it.nothing.phone no recognized by fastboot and no recognized by windows.consider that on a xp and 2.0 usb pc (with fastboot,adb,and adb drivers on it) phone is recognized by windows as Android-Phone but then windows says i've not the drivers for the installation (appears the drivers' choosing window).No asus driver on it,on the win7 pc there are!!
Click to expand...
Click to collapse
When you see the dead android with red triangle, hold the power button and keep pressing it and quickly
press volume up button and release it but keep the power button and you will see the Recovery options.
Then choose "format Cache" with volume up & down button and enter with power button to format cache partition.
It would take a long time so don't be alarmed. When done, choose restart system and the boot loop should be fixed.
Good luck.

samteeee said:
When you see the dead android with red triangle, hold the power button and keep pressing it and quickly
press volume up button and release it but keep the power button and you will see the Recovery options.
Then choose "format Cache" with volume up & down button and enter with power button to format cache partition.
It would take a long time so don't be alarmed. When done, choose restart system and the boot loop should be fixed.
Good luck.
Click to expand...
Click to collapse
Thank you bro,you saved me

samteeee said:
When you see the dead android with red triangle, hold the power button and keep pressing it and quickly
press volume up button and release it but keep the power button and you will see the Recovery options.
Then choose "format Cache" with volume up & down button and enter with power button to format cache partition.
It would take a long time so don't be alarmed. When done, choose restart system and the boot loop should be fixed.
Good luck.
Click to expand...
Click to collapse
Didn't work for me ... if I keep pressed the power button for a long time, power off the phone and it doesn't entry in Recovery mode...
I resolved with "fastboot erase cache" command

It is normal to get that error when selecting 'recovery mode'
The next step is a little tricky. You have to press and hold the power button, then press the volume up button. It may take a few tries. Both buttons will have to be pressed together simultaneous to enter Android system recovery. Please also see http://www.asus.com/us/support/FAQ/1011956/
Sincerely,
ASUS_USA

Asus_USA said:
It is normal to get that error when selecting 'recovery mode'
The next step is a little tricky. You have to press and hold the power button, then press the volume up button. It may take a few tries. Both buttons will have to be pressed together simultaneous to enter Android system recovery. Please also see http://www.asus.com/us/support/FAQ/1011956/
Sincerely,
ASUS_USA
Click to expand...
Click to collapse
Hi,
I´m having a problem with mine. Can´t recognize phone in fastboot but it´s different. I already asked for help in general thread - all resources (page 47 to 50) but still can´t solve.
I rooted my device using method 3 (one click root) and first everything seems fine, but on my first reboot i entered on bootloader - recovery and started a wipe cache, but didn´t finished it, push power button and force it of (i seemeed stuck there - was wipping for more than 10 minutes). Since then i can´t solve anything, tried many ways to unbrick my phone but i seem the problem was i can´t connect fastboot. After a lot o tries, i entered in TWRP using method 2 and wipe, made a recovery, everything and as magic i can enter again on recovery, even tried adb sideload (it started, but when starts to write something - at 50% of the process just ended). So, long story short, i did a flash of the original firmware i downloaded from asus website using method 2 and now it´s working as original, but i still having the same problem (or maybe worst, since i can´t enter the TWRP recovery using method 2 anymore) and can´t root my device. When i tried to do anything using fastboot it´s just shows "FAILED", When i request adb devices shows a blank line. If my phone is on, using android, it shows the correct serial number.
I don´t know what´s happening, it seems to estabilsh a connection (when on its ok, method 2 freeze on teamwin logo - the tool can write something on phone) but can´t write anything. i´m worried because i think i won´t be able to do any update and i wanted a rooted phone to.
Anyone seems a solution?

I'm having the same problem today and I solved it just now! I can't even open the fastboot and recovery. Finally I install the software "shuame"(I'm Chinese, you guys may find other software) on my PC, and with it my computer read zenfone2, and I use the function in the software to open fastboot mode, then I flash the WW version recovery.img and boot.img with a one-click tool in zentalk(TW), then I just double wipe, the phone is alive now !
Sent from my ASUS_Z00AD using XDA Free mobile app

ityoung said:
I'm having the same problem today and I solved it just now! I can't even open the fastboot and recovery. Finally I install the software "shuame"(I'm Chinese, you guys may find other software) on my PC, and with it my computer read zenfone2, and I use the function in the software to open fastboot mode, then I flash the WW version recovery.img and boot.img with a one-click tool in zentalk(TW), then I just double wipe, the phone is alive now !
Sent from my ASUS_Z00AD using XDA Free mobile app
Click to expand...
Click to collapse
I don´t know any other software. Is this software only in chinese ? Can i try?
My phone is actually working, but i can´t flash anything, even MOFD_update.zip (the file it is used to make ota uptades)
is Your phone rooted? which method did you use? Now you can use fastboot normally?

Soft-brick problem

I restored an lineage os update last night, then i restored a BOOT update that didnt belong to that rom and i`m in bootloop unable to enter recovery or enter bootload, my phone responds only to power button+ volume up ( it restarts), tried to connect fastboot and i get that device isnt found( its connected to usb ports, i installed htc sync manager for htc drivers)
What can i do to go into bootloader, because if i get there i flash twrp then restore the correct rom, but now its just bootloops in RR remix( it doesnt restart itself just loading loading )
Can i get some help with right drivers or something that i could use that command" adb reboot bootloader" and it wont answer with device not found
P.S I get the device in device manager but in adb just says "device not found"
P.S2 Close the thread, i let the phone fully discharge then Volume down + power and it entered fastboot and i was able to get to recovery, nvm

Callliope said:
my phone responds only to power button+ volume up ( it restarts)
Click to expand...
Click to collapse
I know you fixed the problem, but for future reference, in the above scenario, as long as you can force a reboot (power+vol up); the moment the screen goes black to reboot, just slide your finger to vol down (no need to hold power button any longer) and keep holding it; and the phone will go to bootloader.
Callliope said:
Can i get some help with right drivers or something that i could use that command" adb reboot bootloader" and it wont answer with device not found
P.S I get the device in device manager but in adb just says "device not found"
Click to expand...
Click to collapse
adb would never have worked in the condition your phone was in. The phone needs to be booted to OS or custom recovery for adb to work.

Question Need help unbricking -> EDL not accessible for MSM

[SOLVED see post below]
Hi all,
Just bricked my Phone and can't access MSM. Hope you can help me. I will try to be very clear on the steps I took to get to this point.
Device: EU OnePlus 9 Pro
What is was trying to do: Go from rooted C.47 to Pixel Entended ROM
What I did:
Code:
Unrooted using Magisk uninstall option
Updated to c.48 through OTA
Go to lineageOS page on how to ensure all firmware partitions are consistent
very stupidly did not flash dtbo and vendor boot partition
did adb reboot fastboot in stead of abd reboot bootloader
Download the "lineage-19.1-20220701-recovery-lemonadep.img" and tried to temporaryly flash it by
fastboot flash boot <recovery_filename>.img
This resulted in the device getting stuck on the 1+ boot logo.
I can still force turn it off by holding Volume Up + Power.
When I try to access EDL by turned off and Vol UP + Vol Down + Plug and release, My PC makes a connection sound and the screen stay black for a while. After +- 10 seconds, the PC makes a disconnection sound and the phone boots up and gets stuck again on the 1+ bootup icon.
Also my phone won't stay turned off when plugged in the charger or pc

Yes, but what is it presenting as (i.e. EDL, fastboot, ADB, UMS...) when it connects?
If this is Windows, UsbLog.exe is handy to identify things popping up (as long as they have drivers installed).
For a list of devices that have ever tried to connect, try "enumusb.exe /l".
Both available here: https://www.temblast.com/windows.htm

Renate said:
Yes, but what is it presenting as (i.e. EDL, fastboot, ADB, UMS...) when it connects?
If this is Windows, UsbLog.exe is handy to identify things popping up (as long as they have drivers installed).
For a list of devices that have ever tried to connect, try "enumusb.exe /l".
Both available here: https://www.temblast.com/windows.htm
Click to expand...
Click to collapse
I will try this

I found the issue:
> EDL exits after 10 seconds if it is not captured by the MSM tool.
> The MSM tool only monitored 4 of my 10 USB ports
> So it was not captured because I was plugged in to an unmonitored USB port and rebooted after 10 seconds
> I have successfully used the MSM tool now

Oh! A bit off-topic, but I have never understood why EDL is commonly used over a "serial" port.
The interface that EDL presents is a generic USB bulk interface with two endpoints. You can use it just like that.
But no. They have to use a Qualcomm driver that makes it look like a "serial" port and then you can connect to that.
Me? I use a generic "WinUSB" Zadig driver. I have an EDL client that just connects to that fine.
So does the Python client implementation.
Also, I've never run into that 10 second timeout.

TraktorHenk said:
[SOLVED see post below]
Hi all,
Just bricked my Phone and can't access MSM. Hope you can help me. I will try to be very clear on the steps I took to get to this point.
Device: EU OnePlus 9 Pro
What is was trying to do: Go from rooted C.47 to Pixel Entended ROM
What I did:
Code:
Unrooted using Magisk uninstall option
Updated to c.48 through OTA
Go to lineageOS page on how to ensure all firmware partitions are consistent
very stupidly did not flash dtbo and vendor boot partition
did adb reboot fastboot in stead of abd reboot bootloader
Download the "lineage-19.1-20220701-recovery-lemonadep.img" and tried to temporaryly flash it by
fastboot flash boot <recovery_filename>.img
This resulted in the device getting stuck on the 1+ boot logo.
I can still force turn it off by holding Volume Up + Power.
When I try to access EDL by turned off and Vol UP + Vol Down + Plug and release, My PC makes a connection sound and the screen stay black for a while. After +- 10 seconds, the PC makes a disconnection sound and the phone boots up and gets stuck again on the 1+ bootup icon.
Also my phone won't stay turned off when plugged in the charger or pc
Click to expand...
Click to collapse
Your phone needs to be in OFF state mode when you're using EDL.
So, very simple:
Enter bootloader mode by holding both volume buttons with the power button together till your phone restarts and enters the bootloader.
From the bootloader screen you can use the volume buttons to navigate through the choices and you can select "Switch off".
When you complete this, you need to hold both volume buttons, and while holding them connect the cable (PC).
If you don't have or you don't have the correct Qualcomm EDL drivers installed, your phone will reboot or start to boot, it won't stay in EDL mode for longer than 10 seconds.
I also got the correct drivers for you, but you need to install the drivers manually while your device is in "EDL" mode, so, you need to be a bit "fast".
I have even a video for you, but need to upload it to YouTube so you can watch it.
I'll share you here the drivers just in case if you're familiar with a manual installation of the drivers.

ekin_strops said:
Your phone needs to be in OFF state mode when you're using EDL.
So, very simple:
Enter bootloader mode by holding both volume buttons with the power button together till your phone restarts and enters the bootloader.
From the bootloader screen you can use the volume buttons to navigate through the choices and you can select "Switch off".
When you complete this, you need to hold both volume buttons, and while holding them connect the cable (PC).
If you don't have or you don't have the correct Qualcomm EDL drivers installed, your phone will reboot or start to boot, it won't stay in EDL mode for longer than 10 seconds.
I also got the correct drivers for you, but you need to install the drivers manually while your device is in "EDL" mode, so, you need to be a bit "fast".
I have even a video for you, but need to upload it to YouTube so you can watch it.
I'll share you here the drivers just in case if you're familiar with a manual installation of the drivers.
Click to expand...
Click to collapse
Thanks for the help. The problem ended up to be a bit different than this for me, but this is a good post for anyone to find in the future!