Database Info

[Q] Desire S stuck on boot - cant get to recovery

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

[Q] Nook tablet with Cyanoboot does not boot

I had installed CM9 (alpha 0.04) and Nook recovery flasher on Nook tablet 8Gb. After the reboot Cyanoboot was loading. After the Cyanoboot logo the screen was shaking and Nook doesn't load. I still have some seconds to enter the CWM. In CWM I tried to wipe all data/restore to factory defaults. Also I tried to install CM7. But that didn't help. I still have an option to boot from sd card (works). So i think that the problem is with Cyanoboot. Can anyone help? How can I remove Cyanoboot from system? (It is loaded in main memory, I think). Thank You.

Same here.

Nook tablet with Cyanoboot does not boot
I'm having the same problem...
I'm running the 16gb Nook tablet and I tried loading Cyanoboot. I can run using the sd card method, but after shutting down, removing the card and trying to boot beyond that point, all I get is the black "n" screen. Then the screen flashes and I get a much bigger "N"
Any suggestions would be more than welcome!! I've tried to get back to CWM, and no dice!!
Thanks in advance for your help!!

NookHD+ 16gig rooted to 4.4.2 suddenly not booting past cyanoboot universal bootloadr
I am having a similar problem. Anyone found a solution?
My Nook HD+ 16gig was working well under CM10. But I wanted it to run faster under the streamlined Kitkat 4.4.2, so I flash it to CM11. It worked well for a few days, but it seemed slower. Eventually, one morning it just stopped booting past the NookHD+ boot screen or sometimes past that but stuck at the cyanoboot universal bootloader screen.
I have tried booting from the internal bootloader and from the SD Card with the bootloader image. No luck on either front.
I also can no longer get into the CWM or TWRP (I have CWM). I try all forms of power key and volume/"n" keys combinations, but I can't get into the CWM menu to re-flash my NookHD+ (I have tried so many combinations, I now forget what is the proper key combination/order to boot into CWM. someone repost the proper key sequence please).
Well, help! I feel like the dog that barked at his own reflection on the well and dropped/lost his bone. I wanted my NookHD+ to run faster and more efficiently under KitKat 4.4.2, and now I lost the CM10 and CM11 settings. It really sucks.
Can someone help me re-set everything to factory default, so I can re-flash it CM10? Please help. Thanks!!

[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.

[HELP] Shield Tablet: did a full wipe and it doenst boot anymore

good day,
i have a Nvidia Shield Tablet, non rooted, not unlocked, stock ROM, updated via OTA only and its included in the RMA.
so i was cleaning a bunch of files first then i did a factory reset on the tablet but after rebooting after the Nvidia logo, it just got stuck on a blank screen.
how can i go about this? i wanted to give this to my child once i got the new tablet.
if any kind sir can point me to do a recovery OS and its rom file that would be very helpful.
thank you

Did you already receive the replacement? If you did and you used it already, you are hooped. Your old one has been deactivated

Just force reboot the tablet with the Power button, and you will be fine. But why would you give your child a tablet that could possibly explode??

Phen0m said:
Just force reboot the tablet with the Power button, and you will be fine. But why would you give your child a tablet that could possibly explode??
Click to expand...
Click to collapse
I was wondering the same thing...

will it really explode? i thought it will just die down?
yesterday we decided we will just use it during drumming session. mounted on a tablet holder
i waited 15 mins from the blank screen and eventually the android animation for the factory reset showed up.

get stuck on splash screen with the KitKiss logo without being able to use the tablet

Asus Transformer TF 101… Was lying for a few years in the drawer.
Have decide to start using it for my daughter.
Had KatKiss rom 5.1 installed and was working fine.
Tried to upgrade to KatKiss 6.0.1 when troubles started.
Upgrade went OK but when was looking for the Google Play app (and service) and tried to install it, something went wrong…
At the moment, after spending a few hours with "POWER + VOLUME DOWN" and / or "POWER + VOLUME UP" I get stuck on splash screen with the KitKiss logo (the dog with the 4 balls) unable to do anything (trying to turn off, it starts automatically – the only way I can get it off is by letting the battery to runout) – Any advise would be appreciated !!!

I just got mine going again and had the same issue. I have re-flashed the latest ROM and the SU that was still on the system. GAPS is working but I am going to try to get something else on there like MicroG.
So re-flash it and see how it goes.

i cannot get into recovery.
Did you do it via ADX and ADB?