Hey there XDA! I thought I'd root my P920 a few days back, which went smooth, no issues and I was enjoying my newly rooted Optimus
I wanted to get a new kernel for it, so first thing I did was install CWM, Then clicking on 'Flash ClockworkMod recovery' in the app, which then flashed a CWM recovery if I'm not wrong. The final thing left to do was rebooting into the recovery, which I did by clicking 'Reboot into recovery'
Now waiting for the phone to reboot into recovery, the LG logo came up on screen, and stayed there for some time, which is normal behaviour as it takes a bit of a while to boot up for me, but then something odd happened, the logo disappeared and the screen blacked out, leaving the phone off. Immediately noticing this, I tried to boot the phone up as I normally would, but again the same thing occurred, logo appears, then phone blacks out and returns to an off state.I repeated this a few times, but to no avail.
These are some things I tried:
Normal booting multiple times
Normal booting after battery pull
Normal booting while charging
Normal booting after removing SD card (this resulted in a blue screen appearing after the LG logo on bootup, though I was impatient and didn't wait to see what would happen so I pulled the battery out )
Normal booting after removing SD card and then battery pull
Normal booting after removing SD and SIM card
Normal booting after removing SD and SIM and then battery pull
Booting into recovery multiple times
Booting into recovery while charging
Booting into recovery while charging
Booting into recovery after removing SD card and battery pull
Booting into recovery after removing SD card
Booting into recovery after removing SD and SIM card
Booting into recovery after removing SD and SIM card and battery pull
So as can be seen I've tried tons of situations
A few times, the screen turned into repeated patterns of static colour, it's difficult to describe but its only happened a couple times, and appeared on top of the LG logo. From what I've gathered, something is preventing the phone from booting up properly, either normally or into recovery, unless the problem is something else entirely. Also I don't have any NANdroid or Titanium backups.
So my questions are, could it be that I need a full charge for it to boot properly? Otherwise what's the problem and how do I get the phone to boot normally? I would prefer that all data on the phone is not erased but if it's a must then so be it.
I really appreciate any and all help I can get here, thanks!
P.S. I'm new to rooting and customising at that level, so please ask for any additional details or anything I was unclear about. Apologies to all for the lengthy first post, thanks again!
AW: [Q] Boot issues after installing CWM recovery
Hi welcome
Girst thing you have to do before flashing or doining something with your phone is a nandroid backup. I do always a titaniumbackup and saved pictures and music manually only for insurence. Next thing, whcich app do you use for flashing cwm?
For your data im not sure if you can rescue that i dont think so.
If i understand it right your are stuck on bootlogo right?
To rescue your phone you can always go back to gb by flashing kdz file with flashtool. Watch here
http://forum.xda-developers.com/showthread.php?t=1540163
But in that case you will loose all your data on phone.
P.S. and next time if you want to flash cwm use os_hackings all in one tool. And flash twrp recovery its better and didnt have so much bugs
Sent from my LG-SU760 using xda app-developers app
I used ROM Manager for flashing cwm, yes I am stuck on bootlogo
Thanks for the help! I'll try out what you suggested and report back here if it works
Related
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.
Here goes: I was a happy OPO user using the latest crDroid ROM and AK kernel, when suddenly my phone entered the sleep of death. I turned it off and back on, and since then it is in an eternal boot loop, never going beyond the Oneplus logo.
I am able to get into fastboot mode as well as recovery mode (I am using Philz Recovery), however, here is where it gets weird. I was hoping to just flash another ROM from the recovery and fix the problem, but all my files and folders on the SD card are gone, almost as if the chip died.
I also tried flashing a different ROM using ADB, to no avail. ADB shows "OK" but nothing sticks. All I can successfully flash are the boot logo and the recovery. The phone never gets beyond the logo before it reboots.
Does anyone have an idea what else I could try? I feel like sending it back for a replacement, but I am afraid that this will take forever.
Do you have a OTG USB stick ? Maybe you can flash from there.
I was able to get my phone to boot using this:
http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
All data is gone though. But at least I don't have a brick any more.
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
I was trying to update my recovery, TWRP 2.7 or something, to the newest version through the TWRP Manager app and I did that, or so I thought, and rebooted the device. Now it gets to the white screen where it says rebooting recovery in pink text but nothing happens, reboot it, same thing. I can tell that it is in recovery because I can feel the vibrations of the buttons when I press them, like the home and back buttons in the bottom corners, it is just that the white HTC logo screen is still overtop of it. Tried sideloading CWM but got an error so not sure if I did it right, can't really show any pictures though. Any suggestions?
**I am rooted, s-off, unlocked ****I have an SD card in it if that would help with any specific processes
I am very angry as I don't have the money to go out and just purchase a new phone I really hope there is something I can do, because things like this have happened before but I have been able to fix them within an Hour and it has been 3 hours now :/
Is there any way to keep it from rebooting by itself? Can I factory reset it through ADB?
So I flashed CM12 on my Galaxy Tab 2 10.1 and then tried to encrypt it. I had full battery and everything but I saw them message that it failed. It asked me to reset the device so I clicked it. It was the only option. When it rebooted, it went straight to TWRP but instead of loading TWRP, it just kept showing the splash/loading screen. Then it would flash black quickly and then show the splash screen again. I left it plugged in over night to see if it would load. It did not. So I let the battery completely die. Once I charged it, it still does the same thing. I've tried using ODIN to flash TWRP again. It says it successful but the same thing happens. I also successfully flashed CWM with ODIN but the screen flashing thing still happens. (I can put the tablet in Download Mode with no problem).
Does this mean I've fried my SD card or is there some other fix I'm not aware of?
I'm not sure why this worked but I was able to boot into CM by leaving the device in the boot loop and running the command `adb reboot bootloader`. After that CM12 loaded up. I decided to try restarting and it restarted just fine too. Everything seems to be back to normal.