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?
Related
Hi,
I will prefix this (as there are a few people around with this problem who can get into recovery mode) with the fact that holding down Vol- on boot is not getting me to the recovery / bootloader screen.
I have a rooted HTC Desire S (rooted it nearly a year ago, so info about the hboot etc is a distant memory).
Anyhoo, I decided to have a play about with one of the ICS roms but it was a bit buggy and the camera drivers still aren't working for video so I decided to go back to Endymion V3.4 - http://forum.xda-developers.com/showthread.php?t=1310845
I did a full wipe, installed base rom, installed optional addons and then upgraded to 3.4 - booted fine into the OS so set about getting my system set up the way I like it.
I noticed that endy came with a theme installer so clicked on one of them to have a look, it asked for root, said it was installed and would need to reboot to take effect...
SO
the problem is, it now won't boot and is stuck on the white HTC boot screen.
Holding vol+/- and power buttons reset it but it just ends up back hanging on the boot screen.
Have tried pulling battery and trying again.
Holding Volume Down when powering up is no longer doing anything
So, I either need a saviour to point me in the direction of a fix.. or a kindly sould to break it to me gently when they tell me my phone has gone to the USB Dock in the sky..
Any help will be greatly appreciated.
Thanks
update:
After pulling battery again, pulling out sim and sd cards, booting with vol- held down, i got into recovery. Am going to try and flash a different rom after doing a full wipe, I'll update once it's done but any insights in the meanwhile will still be appreciated
Sorted, cleared the thing out, stuck reaper CM rom on it, rebooted and everything is peachy for now.
Thanks me
Curious if anyone knows why this might have happened?
because you didnt flash the addon zip which was released alongside endymon and then tried to use the addons,it does say on the screen do not use these unless you have installed the addons
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
So ive been running CM 10.1 with CWM v6.0.4.3 for several months without major issue until last night. I went to send a text message to someone, and right as i went back to my home screen, the phone froze, rebooted, and when it finished rebooting, the deice would freeze again as soon as the lock screen was reached, and reboot again. Cue repeated circle of freeze, reboot, finish rebooting, freeze, reboot.
I turned the phone off by taking out the battery, put it back in and charged it overnight without booting it up. Went to start the phone today, same issue still. I would boot into recovery and try to re-flash the OS, and it would give me a status 7 error. After re-downloading everything into my sd card, i was eventually able to get the system to re-install cm10.1.3, and it booted up normally. I downloaded and installed ROM Manager, and installed the newest version of CWM Touch, version 6.0.4.5, and then tried to boot into recovery to install CM11. It showed the CWM Hat icon in the middle of the screen, with the version on the bottom of the screen, then rebooted on its own without showing any menu options.
Now if i try to boot into recovery, it just shows the icon and version again, then reboots, and wont go past the CM loading screen with the spinning cyanogenmod icon.
Not sure what to do at this point, i cant get into recovery to try and flash something new, and i cant get past the CM loading screen to actually use my phone. Any ideas? I have zero experience with adb, so im stumped.
UPDATE: Solved, i flashed TWRP over CWM using Odin, and was from there able to re-install the OS. Things seem to be working fine for the most part, with the exception of one random reboot last night.
Salomon3068 said:
So ive been running CM 10.1 with CWM v6.0.4.3 for several months without major issue until last night. I went to send a text message to someone, and right as i went back to my home screen, the phone froze, rebooted, and when it finished rebooting, the deice would freeze again as soon as the lock screen was reached, and reboot again. Cue repeated circle of freeze, reboot, finish rebooting, freeze, reboot.
I turned the phone off by taking out the battery, put it back in and charged it overnight without booting it up. Went to start the phone today, same issue still. I would boot into recovery and try to re-flash the OS, and it would give me a status 7 error. After re-downloading everything into my sd card, i was eventually able to get the system to re-install cm10.1.3, and it booted up normally. I downloaded and installed ROM Manager, and installed the newest version of CWM Touch, version 6.0.4.5, and then tried to boot into recovery to install CM11. It showed the CWM Hat icon in the middle of the screen, with the version on the bottom of the screen, then rebooted on its own without showing any menu options.
Now if i try to boot into recovery, it just shows the icon and version again, then reboots, and wont go past the CM loading screen with the spinning cyanogenmod icon.
Not sure what to do at this point, i cant get into recovery to try and flash something new, and i cant get past the CM loading screen to actually use my phone. Any ideas? I have zero experience with adb, so im stumped.
Click to expand...
Click to collapse
You can try to reflash CWM with Odin, if that not working, you could try to Odin back to stock.
buhohitr said:
You can try to reflash CWM with Odin, if that not working, you could try to Odin back to stock.
Click to expand...
Click to collapse
I figured it out yesterday actually and forgot to update! Indeed I was able to flash TWRP with odin, since CWM seemed to be blocking me from doing anything. Once that was up and running, things went back to normal, i was able to flash CM 10.2.1 and things seem to be working now.
One thing though, while playing skyrim last night i had it on the charger next to me, and the phone randomly rebooted without any interaction from me. Was odd, but it hasnt done it since. Keeping an eye on it still.
So I decided to try to flash Zombie-Pop today and everything went fine during installation but when the tablet started booting up it was stuck on "android is starting.." and it seems to load the apps. I knew it would take a bit of time to stabilize so I let it run but after 1 hour of it stuck there, I tried to reboot into recovery but I get a black screen and I can't access TWRP. It just boots right back to the android is starting screen. It doesn't seem to be a boot loop since it finishes the boot sequence. My biggest problem is not being able to access recovery because of the black screen which apparently is happening to some people with TWRP. I tried to go through adb but since my tablet isn't done installing, it doesn't have the drivers to run adb. Is my tablet toast? bricked?
edit: apologies for the title. I must have deleted the text before posting.
agentkalaw said:
So I decided to try to flash Zombie-Pop today and everything went fine during installation but when the tablet started booting up it was stuck on "android is starting.." and it seems to load the apps. I knew it would take a bit of time to stabilize so I let it run but after 1 hour of it stuck there, I tried to reboot into recovery but I get a black screen and I can't access TWRP. It just boots right back to the android is starting screen. It doesn't seem to be a boot loop since it finishes the boot sequence. My biggest problem is not being able to access recovery because of the black screen which apparently is happening to some people with TWRP. I tried to go through adb but since my tablet isn't done installing, it doesn't have the drivers to run adb. Is my tablet toast? bricked?
edit: apologies for the title. I must have deleted the text before posting.
Click to expand...
Click to collapse
Which bootloader are you on?
How are you trying to boot to recovery?
My Karbonn Sparkle V appears to have bricked itself, I don't know why, I don't know how to fix it, and I don't have the money or time to replace it. I turned it off when I was going to a job interview, prior to which it was working fine. Afterwards I tried to turn it back on, and for the last 12 hours I've been fighting to get it working again with no success.
I can get into recovery mode, but nothing more. If allowed to try a normal boot, then it will either stay on the "Karbonn Smart" logo screen forever and ever amen, or it will APPEAR to boot, but once it reaches the lock screen it dies on its arse. The best-case is that the lock screen will stay up for about 3 seconds, then the screen will go black for another 3 seconds, and then we go back to the lock screen and the process repeats. OR, the lock screen comes up, 3 seconds, and then we go back to the bouncing dots loading screen forever and ever amen.
I tried a hard wipe from recovery mode - it's made absolutely no difference.
This is a stock phone which has only ever received the OTA updates; I've never rooted it, I don't have a custom recovery installed, and I've never used ADB before today.
I've downloaded a number of "stock ROMs" for this phone, but none of them actually work for me; it doesn't seem to matter whether I try to install them through Recovery mode\Apply update from ADB, or put them on the SD card and try "Apply update from SD card". For most of them, I get the error "failed to verify whole-file signature" and it won't install; I tried to install the stock file from https://forum.xda-developers.com/crossdevice-dev/android-one-general/ota-links-t3287707 but that doesn't get me much further; The error becomes
"Package expects build thumbprint of 6.0.1/MMB290/2459718:user/release-keys or 6.0.1/MMB29K/2419427:user/release-keys; the device has 6.0.1/MOB31E/3142026:user/release-keys"
Click to expand...
Click to collapse
I have pretty much no idea what I'm doing here; Please help.