Database Info

[Q] strange boot behavior

I had the Photon Q with the SIM mod and CM 9 working for 2 mouth. But yesterday, I were using the cellphone when it reboot itself and get freeze on the unlocked bootloader warning. I try to power it of but y could not, the I let it there until batery drain (about 4 hours)
Now when I boot the cellphone it has an strange behavior. Some times it freeze on the unlocked bootloader warning, other time make a loop boot (show the warning and restart). Also some times it display strange colors on the screen when try to boot and many times it display a randomly sorted grey vertical lines and very few times (one of every 50 times) it boot the ROM but when i touch the screen it goes black.
i can not conect to phone by adb and can not enter recovery, but i can access to the fastboot (in fact the fast boot is working but do not display anything on the screen, i suppouse that the same happend with the recovery. but i can not use it if the screen is black)
I used the fastboot and RSD to flash the stock firmware, the phone return fail on every 4.0.4 ROM but it work with the 4.1.2. After the flash some times thes phone display the morotola and sprint logo and then start the handfree configuration, but when I touch the screen it goes to black again.
I do not know if it is bricked, I think that if i have access to the fastboot i can resurrect the phone. but is very strange the random behavior.
Do you have any idea what should I do?
Thanks.
PS: sorry for my bad english

Re-Strange behaviour
Hi there, one of my Q's (also sim modded) was doing a similar bootloop warning etc. I was screwing around with it a bit. It's all good now though.
The way to force power down/reboot is to hold "volume -" and the power button for 10-15 seconds. If you drain the battery, you will be stuck with more boot-loops due to a flat battery. If you plug the charger in & the LED is green, this means it is charging a dead battery, & will need to charge for a while.
By the way, I had issues on my other Q handset running CM, failing to read the mSD card, and causing freezes, boot loops etc, so I went back to stock. Pretty sure most of the trouble is due to the mSD card read/mount error.
Edit:
Come to think about it - my Q failed after I tried to restore my CM10.1 backup from the previous phone. I suggest this may be contributing to the issue, as you are also running CM.
With the black screen/boot loop, force reboot by holding "vol -" & power button for 15 seconds, release power, then immediately hold "vol +" so it forces boot to recovery (TWRP if you have it).
I restored a previous backup eventually, but TWRP was not working too well after the screwy boot-looping etc. I ran a factory reset from the phone menu once it was running again, then rebooted into TWRP.
Super User wouldn't install from TWRP after, so I pushed it across & installed from TWRP, now I'm about to update TWRP to 2.6.
Still want to have a go at another ROM on this handset, so I can compare it to my stock one. I'm pretty sure CM10.1 was part of the problem on the other Q with my mSD card failing, as it has been fine ever since on stock.
Try this:
Try using adb to fastboot into recovery, then push TWRP (again) onto your Q using this method by arrrghhh http://forum.xda-developers.com/showthread.php?t=1887070
Push Super User across onto your mSD & install that from TWRP as instructed also.
Restore a stock/custom backup from an earlier time if you have one, or flash a fresh download.
Let me know how you go.
P.S. make sure you have "USB Debugging" enabled in developer options in order to ADB fastboot recovery.

schmandroid said:
Hi there, one of my Q's (also sim modded) was doing a similar bootloop warning etc. I was screwing around with it a bit. It's all good now though.
The way to force power down/reboot is to hold "volume -" and the power button for 10-15 seconds. If you drain the battery, you will be stuck with more boot-loops due to a flat battery. If you plug the charger in & the LED is green, this means it is charging a dead battery, & will need to charge for a while.
By the way, I had issues on my other Q handset running CM, failing to read the mSD card, and causing freezes, boot loops etc, so I went back to stock. Pretty sure most of the trouble is due to the mSD card read/mount error.
Edit:
Come to think about it - my Q failed after I tried to restore my CM10.1 backup from the previous phone. I suggest this may be contributing to the issue, as you are also running CM.
With the black screen/boot loop, force reboot by holding "vol -" & power button for 15 seconds, release power, then immediately hold "vol +" so it forces boot to recovery (TWRP if you have it).
I restored a previous backup eventually, but TWRP was not working too well after the screwy boot-looping etc. I ran a factory reset from the phone menu once it was running again, then rebooted into TWRP.
Super User wouldn't install from TWRP after, so I pushed it across & installed from TWRP, now I'm about to update TWRP to 2.6.
Still want to have a go at another ROM on this handset, so I can compare it to my stock one. I'm pretty sure CM10.1 was part of the problem on the other Q with my mSD card failing, as it has been fine ever since on stock.
Try this:
Try using adb to fastboot into recovery, then push TWRP (again) onto your Q using this method by arrrghhh http://forum.xda-developers.com/showthread.php?t=1887070
Push Super User across onto your mSD & install that from TWRP as instructed also.
Restore a stock/custom backup from an earlier time if you have one, or flash a fresh download.
Let me know how you go.
P.S. make sure you have "USB Debugging" enabled in developer options in order to ADB fastboot recovery.
Click to expand...
Click to collapse
I tried it, but do not work.
I flash the stock ROM from fastboot and also flash several recoverys, but never boot any ROM and I think that i access to the recoverys but the screen is black then is very dificult to use it. Is strange beacouse some times screen displays perfect the unlocked bootloader warning, but never display anything on the fastboot or the recovery.
Witch part of the software have the video drivers that are used on the recovery and fastboot? I think that maybe is corrupted. how can i flash it again?
Thanks.

[Q] Nexus 4 softbricked, can't charge

my nexus 4 was on temasek's unofficial cm12 build ver 6.1
recovery in use was recovery-philz_touch_6.59.0-mako
i decided to update the rom to build 6.5, so i downloaded the zip to my sdcard,
i had not made a nandroid bkp
after flashing the rom/gapps/superuser, wiping dalvik and cache, things went wrong
after that the phone would only show 'google', then freeze, then go blank, then again show 'google'. this is the first Loop i have encountered where the boot animation never even showed up.
after that in about 8 hrs, i tried all of the foll-
installing the stock images: my phone booted up the first few times i flashed stock images using fastboot, but after three times (because each time it successfully booted i would go back to recovery to try flashing the customromzip) my phone stopped booting up for stock.
it resolutely stayed stuck on the boot ani.
recovery: flashed many times, via sdcard and also via fastboot. no problem with the recovery
zips. absolute fail. nothing can get me past the 'google'
now there's another peculiarity, which makes me wonder if there is hardware damage involved in this softbrick story
after all this flashing my charge came down to 20%, so i tried to charge it (switched off, obviously, since it isn't booting up)
but every time i connect my charger, it boots up,and then shows me google, and freeze and restart..same old cycle
in a last ditch attempt to somehow charge my phone i have brought it to fastboot, and left it connected to my laptop. i don't know if this will work.
please help, also i am now considering using a toolkit, unified android or wugfresh (the latter, i have a previous bad experience with) to get my phone to atleast switch on with something.
should i use the toolkit or just take my brick to the servicecenter to check for damage to hardware

Stuck on boot loop

This is me story, flashed a OTA to my cel and all the sudden my phone reboots loads up to the Oneplus logo and then nothing... Boot loop, so trying not to worry that much, noticed I could still boot to fastboot, I tried flashing CM11 praying that would get my phone back... Boot loop, Flashed CM12 and I got a low battery message boot loop, then going back to fastboot just got me a qualcomm brick, used the Color Os fix... Yay no more qualcomm brick but phone stuck on red icon, does someone have a clue what happened to my phone or if I would ever get it back to normal? :crying:

How long did you let the phone sit for (wait) and you assume it's stuck? As I know if you use the Qualcomm downloader will flash back to ColorOS and it will wipe everything automatically and your phone should be able to boot normally.(Last time when I revive my OPO if I remember correctly it will show the red 1+ logo for at least 30-45 sec.

It just sits there waited for a couple minutes, all the flashing goes ok, even with CM12S the flasing seems to be good, but it just boot loops, and the other thing when I flash a recovery it does flash it, but I cant make it boot to recovery what so ever... I just hope and pray there is a way to recover my phone since it would be a shame if someone told me, you have to buy a new motherboard... hopefully someone would just say replace the battery XD, because when I flash CM12s it does say the battery is too low to power and it keeps power cycling

[Q] Google logo bootloop after flashing TWRP

Last night I tried to flash TWRP just because I wanted to go to a custom ROM- alas, the phone now will not go past the google logo. It usually hangs there for 10-ish seconds and then reboots. Occasionally hangs there indefinitely. It's not a power button issue- the button worked just fine before flashing and I've confirmed it still works normally with a multimeter.
I tried to reflash stock using the Google images and "flashall.bat", which says it succeeded- but the phone still loops. I can get into fastboot, but I get the bootloop even in recovery. Running the similar script through Nexus Root Toolkit always fails on flashing the system partition- usually a buffer error due to a sparse header. Can't even seem to get it to do the "fastboot boot TWRP.img" or whatnot. I've flashed KitKat, Lollipop, and MM stock roms to no avail- they all say they succeed, then continue to bootloop.
I've tried just about everything I've seen on here- but not being able to get into recovery hampers efforts like repairing the persist partition.
Help?

When you boot into recovery, the phone reboots itself? If it does, it could be a sign of a failing power button.
When flashing a stock ROM, are you flashing userdata.img and then performing a factory reset/wipe before booting the phone with a stock ROM for the first time?

When I can get into recovery (without a restart), the phone is totally fine.
I think part of the issue is that the battery ran down while I was trying to do the repair- hence it trying to restart and failing. Power button still seems fine (again, confirmed with a multimeter). I left it plugged in to my iPad charger (since that's a 2A charger) overnight and it was still blinking red in the morning. I moved it upstairs and now I can't even make it that far.
Perhaps the battery was just shot by the time I got the "repair" done, hence the boot loops. Is there any way to revive it shy of cutting open the battery + charging manually (with a bench supply) or just replacing the battery altogether? I may try doing a motherboard swap with my working Nexus 5 just to see if it is in fact the battery.

When the phone is powered off and connected to a power source, do you ever see a flashing red LED? You flashed the correct twrp for the hammerhead?
I would try a new battery because it seems like everything is working.

No longer able to boot into recovery mode after flashing LineageOS

Hi all, have a rooted OPO that was running ExodusOS. I decided to try a flash of Lineage and so booted into recovery, backed everything up, flashed it. Everything seemed to go okay but after the boot logo the screen just goes black and stays that way until it gets shut back off. I went back to TWRP, loaded my backup and all seemed well as I was still able to use my old backup just as normal. Well, I tried reflashing Lineage from TWRP again and I still get the same black screen issue. This time, however, the phone will neither boot into Fastboot nor into recovery mode and just goes straight into loading Lineage. Because of this I am left with a soft brick until I can get this straightened out. I tried connecting the phone to my PC but it is not detected as a device. I only need to boot into my backup one more time so that I can back everything up, so even if it's only a temporary fix, I'm okay with that too. Any suggestions?

AMpageg2 said:
Hi all, have a rooted OPO that was running ExodusOS. I decided to try a flash of Lineage and so booted into recovery, backed everything up, flashed it. Everything seemed to go okay but after the boot logo the screen just goes black and stays that way until it gets shut back off. I went back to TWRP, loaded my backup and all seemed well as I was still able to use my old backup just as normal. Well, I tried reflashing Lineage from TWRP again and I still get the same black screen issue. This time, however, the phone will neither boot into Fastboot nor into recovery mode and just goes straight into loading Lineage. Because of this I am left with a soft brick until I can get this straightened out. I tried connecting the phone to my PC but it is not detected as a device. I only need to boot into my backup one more time so that I can back everything up, so even if it's only a temporary fix, I'm okay with that too. Any suggestions?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851

Sounds like a Hardware issue? Sorry to say what your saying doesn't add up and or make sense. Fastboot should work no matter what even if you soft brick it and mess up recovery. I suggest letting the power fully drain maybe and google how to fast boot in case you are doing it wrong.

Mr.Ak said:
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Click to expand...
Click to collapse
I've tried that but it can't find the phone. The phone gets detected as a new device in windows as evident from the device connection sound but it also never shows up in the list of devices from My Computer.

AMpageg2 said:
I've tried that but it can't find the phone. The phone gets detected as a new device in windows as evident from the device connection sound but it also never shows up in the list of devices from My Computer.
Click to expand...
Click to collapse
I agree with what @Shinobi_warrior said.Seems like you just have a soft brick,so you should be able to boot into fastboot mode without any issues.Are you sure you're doing it the right way? Did you try draining battery completely and then booting into fastboot(yes,you don't need much battery to boot into fastboot mode)?

Well I was finally able to get the device detected by ADB, but it just shows as offline. I attempted to use the repair kit and nothing seemed to happen. I also attempted a different tool (https://forum.xda-developers.com/on.../oneplus-one-toolkit-manudroid19-gui-t2807418) and then booting into either fastboot or recovery that way, a terminal window pops up and quickly disappears, and then nothing else happens. I still see the TugaPower boot logo and it still goes to the blank black screen after this.