I have a Nook HD+ that has decided to go into a boot loop again. I say again because it also got stuck in a bootloop about 3 months ago when I was trying to upgrade it to CM11. I was able to fix it by flashing the CM11 ROM but that didn't work this time. So I did a data wipe/factory reset from CWM which seemed to work, but it was still bootlooping. So I tried flashing another CM11 ROM (cm-11-20141112-SNAPSHOT-M12-ovation.zip), which seemed to take longer than it should have, but it did install. It's still bootlooping. A few times it did seem to boot up, but it either refused to unlock or rebooted again before I could do anything. The interesting thing is when this did happen, it showed the home screen and all of the apps still seemed to be there, despite me having done a data wipe/factory reset. IDK what else to do. The boot animation is really laggy if that means something. Please help.
sega dude said:
boot loop
Click to expand...
Click to collapse
You should start completely fresh including recovery:
Use sdcard recovery that leapinlar has available.
Put cm11 emmc recovery and the cm11 emmc m12 rom on sdcard.
Boot to sdcard recovery.
Flash cm11 emmc recovery.
Reboot to newly flashed emmc recovery.
Wipe data & cache factory reset, dalvic, and system.
Then flash cm11 emmc m12.
And hope that works. If not, it can get much more complicated.
Related
I keep getting the same problem with various ROM's I flash.
When a flash a ROM I first wipe everything by fastboot, superwipe or a combination of the 2, then I use the wipes in recovery, wipe my ext, and repair ext. Then I proceed to flash the ROM and applicable kernels.
First boot goes fine, and so does consecutive reboots/power offs. After about a week, at a seemingly random time, I reboot, then I get a boot loop.
The last time I got a boot loop, was after a week of using froyo by laszlo and I wiped cache, and dalvik-cache, then rebooted, and boot looped overnight.
Other times it would bootloop just after rebooting the phone (and not wiping anything).
Any tips to prevent this from happening?
Thanks (and sorry if I missed some info)
did you flash any custom mtd files? or have you tried a manual wipe of everything? i usually do the superwipe, than manual wipe in recovery.. wipe everything there is!! data, cache, dalvik cache, sd partition, battery stats and rotate... maybe even re format your sd card... not sure what it could be.. but i did have a slightly similar issue in the past but im always sooo paranoid about bricking so i just un-rooted than started again from scratch lol if you choose to do so this guide may be able to help you! http://forum.xda-developers.com/showthread.php?t=1098899
I've wiped everything through fastboot, recovery, and superwipe before flashing, and I've fully formatted and repartitioned through recovery, and I still get boot loops.
Any other ideas to fix boot loops?
HiddenShadow said:
I've wiped everything through fastboot, recovery, and superwipe before flashing, and I've fully formatted and repartitioned through recovery, and I still get boot loops.
Any other ideas to fix boot loops?
Click to expand...
Click to collapse
uhhhmmm maybe try re rooting...? maybe you just got a bad download file and it's acting screwy.. try link i recommended in first comment and feel free to ask me any questions.. im not sure what else would be ausing the problem..
Boot loops
I use to have similar problems. As for the froyo by laszlo, make sure that you have EXT4 partition.
If you still have problems, give me details about your radio and spl.
Well I tried rebooting this evening, no boot loop, but randomly I just lost all my contacts, but it did resync okay later
My radio is 2.22.28.25 and SPL is 1.33.0013d, and no I dont use a custom mtd
Heres a logcat:
http://pastebin.ca/2074938
Edit:
I used to have apps moving to sd-ext automatically, even when there was quite a bit of space on the internal, this isn't happening anymore, so maybe whatever the problem was, its now fixed. Heres what I did:
Formatted the sd card in ubuntu and made a fat32 and ext4 partition (both primary), and put the files I needed to flash while on ubuntu.
Then I flashed the orange-nbh on ezterry's 2708 radio post, rebooted.
After flashing, went into fastboot and did fastboot erase [system, userdata, cache, local, radio, recovery, boot]
Flashed radio, spl, recovery as per instructions
Flashed rom (and kernel if applicable)
I tried to flash CWM10 into my Samsung Galaxy I9000 Device And here's what happened:
I got into the CWM Recovery screen and chose install from sdcard (after a wipe data + wipe cache factory ofcourse).
Everything seem to go OK, no errors or special things, but when I restarted the device to boot into Android OS, it just came back to the CWM Recovery screen.
Since then, I have tried to install many other ROMS and the phone simply won't boot to android OS.
I have also noticed that usually after a successful ROM flash, folders are created in the internal SD card a thing which DID NOT happen this time.
The only difference that the new ROMS installation does is change the CWM Recovery version/Mod.
So basically, I am stuck at CWM Recovery Screen.
I am clueless and I will really appreciate any thing you can.
Any thoughts?
MPolo1989 said:
I tried to flash CWM10 into my Samsung Galaxy I9000 Device And here's what happened:
I got into the CWM Recovery screen and chose install from sdcard (after a wipe data + wipe cache factory ofcourse).
Everything seem to go OK, no errors or special things, but when I restarted the device to boot into Android OS, it just came back to the CWM Recovery screen.
Since then, I have tried to install many other ROMS and the phone simply won't boot to android OS.
I have also noticed that usually after a successful ROM flash, folders are created in the internal SD card a thing which DID NOT happen this time.
The only difference that the new ROMS installation does is change the CWM Recovery version/Mod.
So basically, I am stuck at CWM Recovery Screen.
I am clueless and I will really appreciate any thing you can.
Any thoughts?
Click to expand...
Click to collapse
cos of new partitions u have to install 1 ROM 2x. sometimes 3x. thats all.
so take ur cm10 zip and flash it. after reboot to recovery just flash the same file again.
Hi all, my name is Daniel.
I am using a motorola Milestone A853 for the past one year and never faced any issue while rooting or installing custom roms right upto cm10.
from last two months the milestone has not been working properly. It so happened i had installed CM 9.0.1d and everything worked fine. but once the battery died the phone did not boot up and was stuck on moto boot logo and kept restarting from there. I tried to go into open recovery (fufu minimod) using the X+power key and it goes into recovery but after loading recovery it did not display any options and the other text was red in color and it showed the error failed to load menu.init. I replaced the update.zip file along with the open recovery folder, but still nothing worked. I then tried another open recovery but still open recovery never loaded. Then i SBF'ed the device and went back to stock and was able to use my phone again. But then when i try to root the device again i am not able to root using vulnerable SBF as it does not install though RSDLite shows pass. Then i used superoneclick to root and that did the trick. But still open recovery never installed or load. Luckily androidiani recovery which displayed an error cannot mount but still created the menu and i was able to install custom OS but only cm 7.2.4e and not cm9 nor cm10. I cannot reboot the phone as the phone never starts up. only after clearing dalvik and wiping cache phone boots up. After a certain time now i still cannot install cm7.2.4e as it does not load and gets stuck on custom bootscreen, so i installed MIUI rom which works and starts up but i still can never reboot my phone.
Errors Seen E: cant mount /cache/recovery/command
Kindly help as the phone is just barely working.
Your phone has some serious issues...
How stable it is with stock rom? Maybe You should flash a stock 2.2 and see if you have any issues.
If not, then flash vulnerable recovery and so on, step-by-step.
Maybe it will be easier to locate the source of the problem this way.
Tried Everything
Erovia said:
Your phone has some serious issues...
How stable it is with stock rom? Maybe You should flash a stock 2.2 and see if you have any issues.
If not, then flash vulnerable recovery and so on, step-by-step.
Maybe it will be easier to locate the source of the problem this way.
Click to expand...
Click to collapse
Thank you for your reply. I have tried flashing stock 2.2 and still I cannot reboot the phone without wiping cache and using the reset factory option in stock recovery. Using superoneclick I can root it and install androidiani recovery but I cannot use cm10 or cm 9. after installing cm9 the phone just restarts after cm9 boot screen and after installing cm10 the phone shows the stock android boot screen. cm 7.2.4e installs as well as miui but if battery dies or if I have to restart the phone if it gets sluggish and slow then I cannot...everytime for the phone to boot I have to wipe dalvik and cache for custom roms and for stock roms I have to wipe cache and factory reset.
SO basically I am stuck...have tried changing the sd card, repartitioning the sd card, but nothing worked
Open recovery cannot be used only andoidiani works after popping up some errors.
Kindly help.
i have a google nexus one. about a day ago i tried to install kitkat 4.4.2 and i dont think it worked.so i wiped all data with clockworkmod.and now everytime i shutdown and reopen it goes directly to the fastboot/bootloader screen.it does not boot up.so please help i tried everything.
pricehockey4 said:
i have a google nexus one. about a day ago i tried to install kitkat 4.4.2 and i dont think it worked.so i wiped all data with clockworkmod.and now everytime i shutdown and reopen it goes directly to the fastboot/bootloader screen.it does not boot up.so please help i tried everything.
Click to expand...
Click to collapse
I recommend using 4EXT recovery. Also, try reinstalling the ROM.
But first, wipe everything (except SD card) and then install the ROM. Also, check the hboot.
Does it get stuck at the X logo? If yes, then boot to recovery and format boot + system, several times. This may be due to a corrupt boot + system file system. Then install the ROM.
The other day i took my HD+. I havent used it for two years, and had been running the hybrid boot from the sd card, which was awesome! Well, I wiped the SD card and wiped the tablet. So essentially it was stock.
I formatted a new microSD card with verygreens recovery, booted it, flashed the rom and google apps, and thought everything was fine. Well, I kept getting a google services stopped working error so I decided to just experiment with Marshmallow. I went into the recovery, wiped everything, and flashed amaces ASOP rom. Then tried flashing gapps, and got an error that said that I didnt have android 6.0.x
Must have failed. And when I booted from the SD, sure enough it booted to KitKat, the one I had flashed previously. Well, eventually I took out the SD and to my surprise, cyanoboot was installed to the tablet and not booting from the SD card. And the marshmallow rom launched (without gapps). I tried booting into the internal cyanoboot, but it was the old one. I held the power button and the home button, but to no avail.
This is probably where I messed stuff up. It started booting and started booting stock, which I didnt want. Where it has the little white loading bar. I force shut it down. Well then it started acting weird and not even booting with the internal cyanoboot. It now just flashes the nook logo.
Luckily, I can boot to the external cyanoboot, but it has an error mounting the emmc. Should I reflash the stock rom and recovery?
Thanks!
SouthernGeorge said:
The other day i took my HD+. I havent used it for two years, and had been running the hybrid boot from the sd card, which was awesome! Well, I wiped the SD card and wiped the tablet. So essentially it was stock.
I formatted a new microSD card with verygreens recovery, booted it, flashed the rom and google apps, and thought everything was fine. Well, I kept getting a google services stopped working error so I decided to just experiment with Marshmallow. I went into the recovery, wiped everything, and flashed amaces ASOP rom. Then tried flashing gapps, and got an error that said that I didnt have android 6.0.x
Must have failed. And when I booted from the SD, sure enough it booted to KitKat, the one I had flashed previously. Well, eventually I took out the SD and to my surprise, cyanoboot was installed to the tablet and not booting from the SD card. And the marshmallow rom launched (without gapps). I tried booting into the internal cyanoboot, but it was the old one. I held the power button and the home button, but to no avail.
Click to expand...
Click to collapse
Running CM internally on EMMC and on SDcard use different CM ROM image versions that are not interchangeable. Currently there is no SDcard build for CM12.x or CM13, so your only choice is to flash and run them on EMMC.
This is probably where I messed stuff up. It started booting and started booting stock, which I didnt want. Where it has the little white loading bar. I force shut it down. Well then it started acting weird and not even booting with the internal cyanoboot. It now just flashes the nook logo.
Luckily, I can boot to the external cyanoboot, but it has an error mounting the emmc. Should I reflash the stock rom and recovery?
Click to expand...
Click to collapse
If you plan to go back to stock ROM and recovery, see item #6 of http://forum.xda-developers.com/showthread.php?t=2062613.
I don't really care about going back to stock, but I can't mount the emmc, will flashing the original recovery fix that do you think?
SouthernGeorge said:
I don't really care about going back to stock, but I can't mount the emmc, will flashing the original recovery fix that do you think?
Click to expand...
Click to collapse
I don't think the cause of your "can't mount emmc" problem is due to not having the original recovery. And there is no point in restoring stock recovery unless you want to re-install stock ROM.
So what do you suggest? Try to flash to CWM recovery and hope it fixes the mounting emmc problem?
Great news! Luckily the rom was still intact. I was able to run a "factory reset" and that fixed the emmc mount problem. The CWM recovery was still installed too and it booted into Marshmallow like I had before!
At this point, can I install a different resident recovery utility? I dont see why not.
Thanks for your help