I am trying to restore my nook color to stock and am running into an issue with it hanging at the N logo on reboot.
I've gone through several different recovery docs which basically point down the same path of
boot from a CWM recovery SD
Format /system and /data
apply the stock ROM
I've also formatted /boot and applied several different stock boot partition images (including the repartition-boot-with-stock fix). I'm _pretty_ sure the boot partition is OK because I get past the "Touch the Future of Reading", the inital N logo, and gets to the N logo with the "Contains Reader Mobile technology by Adobe Systems".
Unfortunately it simply hangs there forever (I've left it overnight).
I have also tried the
I'm sure it's something simple I've missed here, but at this point I'm stumped.
Any thoughts on what I can do to recover my nook would be greatly appreciated.
Thanks!
I was having the same problem. The "8 failed boots" method here got me back to stock. I'm feeling MUCH better now!!
http://nookdevs.com/NookColor/RestoreToStock
Thanks so much for the suggestion, unfortunately my Nook is now hung @ the "Touch the future of Reading" screen. Time to try and re-flash the 1.0.1 recovery images.
As an update I was able to get back to working stock 1.0.1. From a recovery SD I formatted /boot, /system, and /data. Then applied the "repartition-boot-with-stock.zip" and then "nook-complete-restore-1.0.1.zip". reboot and I'm all good.
Thanks!
Related
After playing a youtube video, suddenly my tab reboot by itself, and it stuck in a boot loop.
I tried to wipe factory setting and cache, still the same problem occured. I even tried to reinstall the same rom, it still give the same problem.
When i tried to install other rom (My-Rom 1.0) it stucks on installing kernel.
i try to find any hint on the xda, brought me to this post
http://forum.xda-developers.com/showthread.php?t=1128565
it still unable to solve my problem. Hope anyone can help.
Try installing a different ROM, besides the two you installed, I had the same problem when I flashed HoneyVillain to Taboonay then to Lightspeed, I was stuck on a bootloop, couldn't flash back Taboonay, but was able to get HoneyVillain.
Still has the problem
I tried as you said, Installed honeyvillain 1.2 rom, and still has the same problem.
2 things which i realized is that,
1. there is sudden blink of loop screen that is different from boot loop that i have seen before.
2. there is error when i tried to do factory wipe
error moving data/data/com.estrong.android.pop/lib/libes_dropbox.so
hopefully anyone can help me
have you tried using acer recovery app to reinstal CWM, then use it to download just a basic 3.2 rom if possible and see how that goes
I am having the exact same problem error removing data/bluestacks, bootloops with little flashes in boot animation. tried every option in recovery and like 4 different back up restoration and the boot animation changes to that of the new restore but same thing.Help!!
thor's 13 then updated to 14 and this started
If you want, go to www.tegraowners.com . Thor's site. He made the recovery. If you go to his forums, Rom section, you will see he posted some steps to completely wipe internal memory. More than what the usual steps we take.
I suppose, there is some residual data left, which is why some errors are happening.
Also, any files named "update.zip", should be removed from SD.
Then you should be able to flash a new rom.
Here are the steps....
go to in recovery enter Backup and Restore and click on Toggle backup and restore of internal storage (/data/media)
should say enabled....
then go into Mounts and Storage and format /data
this will REALLY format data and you will loose all you have in the in the internal memory
then reinstall the rom and everything should work as expected....
im currently having this issue as of right now , idk wat the problem is
EDIT: and i cannot access CWM either
OK, this mat have been asked many time, but none of the thread I found applies to my case.
My device is Nexus 7 16Gb Wifi, the internal ROM is stock 4.1.2 (I cannot use 4.2.2 because of a backward compatibility issue for an app I have to use)
The recovery is the latest TWRP 20030227 version, with MultiROM bootloader 4.18. An armhf raring build of Ubuntu is also installed in the internal sdcard and all have worked fine until I tried to flash a alternative kernel.
The new kernel I flashed is the M-kernel mr1.1. I flashed it by booting into recovery and chose to install the M-kernels zip file from there. After I have got a kernel flash successful message I chose to reboot system. Then the weird thing began: at first the device seems to be booting because I saw the usual Google logo and then it turned into the boot animation with a colorful cross in the middle of the screen. But then on nothing seems to follow. The boot animation persists forever. I hve also noticed that during the initial boot it somehow skipped the step of choosing ROMs as usual (because I have Ubunto installed), so I also lost the choice of booting into Ubuntu.
I have to press the power button for more than 10 seconds to power off the device. Then I tried to boot into fastboot mode and recovery mode, both works file, so it still looks not bad. I have kept a copy of my working patched kernel which is kernel_kexec_41-2.zip. Booting into recovery and using the command
adb push kernel_kexec_41-2.zip /sdcard/
I managed to copy this zip into the device. Then, once again, I tried to flash this old kernel by installing it in the recovery. The installation exited with a success. However, when I tried to reboot the device, it is still stuck on the boot animation screen. No choose ROM screen either. So, I am totally lost. Can anybody give some hint on where I was doing wrong and how can I get my device working again without totally reflashing a stock rom and loosing all data I have installed previously? Many thanks.
Any helps please.
Let me update the situation. Tried to wipe cache/Dalvik and reflash the kernels (both the original and the newly downloaded omega3 kernel, both changed nothing -- always stuck in the boot animation. Tried MultiROM->Advanced->Inject curr.boot.sector, the screen allowing to choose rom reappeared and from there Ubuntu boots correctly. However, If the internal ROM is chosen in that screen, the device reboots and stuck in the boot animation screen again.
How about if you make a backup?
Then - no matter what follows - no matter what experiments you do - you can always restore just the /data partition. Or any of the other partitions.
Frankly, you should have done it already, but nothing is stopping you from doing it now.
Backups give you power - and freedom - to experiment with very few risks.
good luck.
Thanks! I didn't realize that I can still make a backup even the system is already broken. Did the backup for the data partition and reflashed the stock rom, it now boots ok. Even though I still lost the desktop configuration and the Ubuntu installation.
instanton said:
Thanks! I didn't realize that I can still make a backup even the system is already broken. Did the backup for the data partition and reflashed the stock rom, it now boots ok. Even though I still lost the desktop configuration and the Ubuntu installation.
Click to expand...
Click to collapse
Had it happened that you still had a bootloop after dirty-flashing /system and/or boot (without doing the custom recovery "factory reset" wipe of /data exclusive of /data/media), a backup can still save your bacon: it can be restored and then manually:
- all system app related /data/data/ and /data/app-lib/ folders removed
- all system app updated .apks in /data/app/ deleted
- wipe dalvik-cache
This leaves all market apps and their data intact while starting from scratch from with the base ROM's system apps. Probably doing that reduces the chances of boot loops.
UID mismatch troubles can still occur if you are coming from a "debloated" ROM and dirty-flashing something like a stock ROM (where there are more system apps than in the prior ROM which generated the /data partition); but I think that TWRP's "fix permissions" should take care of that.
But anyway - backups give you flexibility.
I have the international/unlocked i9505 and i rooted via cf auto root and flashed the cwm recovery..
I then flashed the ge rom from here and i setup it all nice until I rebooted when it is just stuck at the google animation (with the four colors in the center) and it just stays there. I left it there for a good hour before I put the phone into the cwm recovery and follows steps like wipe the "d" cache and formatting the /system, and /cache. it still boots the animation.. flashed the rom again and it still hung there...Any help would be much appreciated.
EDIT: If possible, i would rather just flash the official touchwiz rom to avoid more problems down the line.
leowan731 said:
I have the international/unlocked i9505 and i rooted via cf auto root and flashed the cwm recovery..
I then flashed the ge rom from here and i setup it all nice until I rebooted when it is just stuck at the google animation (with the four colors in the center) and it just stays there. I left it there for a good hour before I put the phone into the cwm recovery and follows steps like wipe the "d" cache and formatting the /system, and /cache. it still boots the animation.. flashed the rom again and it still hung there...Any help would be much appreciated.
EDIT: If possible, i would rather just flash the official touchwiz rom to avoid more problems down the line.
Click to expand...
Click to collapse
Reflash, and when your phone gives you the option to `fix` recovery, select no. Then let your phone reboot and install.
leowan731 said:
I have the international/unlocked i9505 and i rooted via cf auto root and flashed the cwm recovery..
I then flashed the ge rom from here and i setup it all nice until I rebooted when it is just stuck at the google animation (with the four colors in the center) and it just stays there. I left it there for a good hour before I put the phone into the cwm recovery and follows steps like wipe the "d" cache and formatting the /system, and /cache. it still boots the animation.. flashed the rom again and it still hung there...Any help would be much appreciated.
EDIT: If possible, i would rather just flash the official touchwiz rom to avoid more problems down the line.
Click to expand...
Click to collapse
How long did it hang for? i was having problems reflshing, my phone hung for about 20 minutes before doing anything the first time i flashed it with google rom. I left it came back thinking it was unseccessful and when i was reading for solution it just booted up. Since then i have had no problems reflashing.
Also as above post suggests, in TWRP recovery after i installed a rom when exiting it would say FIX permissions, when i swiped yes the rom wouldnt boot. now it all seems fine however i think i didnt know what i was doing.
SSThing said:
Reflash, and when your phone gives you the option to `fix` recovery, select no. Then let your phone reboot and install.
Click to expand...
Click to collapse
i just tried it and its still stuck at the animation..
Not sure if this is ok but I'm still stuck so please help? I reflashed and click no. When I rebooted in cwm.
Simply put, this is what happens when a rooting newbie discovers custom bootloaders and ROMs.
Current State:
A full stock ROM installed (no root) with the Skrillax V8 bootloader plopped on top of it. (which of course means the recovery-from-boot.p file still exists and that I don't have CWM.) The tablet will show the Acer logo then the Android logo and will give the appearance of booting. Then the icon flashes. It does this intermittently and forever.
What I want:
CM 10+ running with Skrillax and TWRP stably. I'd go with Flexreaper for next choice. Maybe I'll try to compile a KitKat version for it someday. Who knows.
How I managed to get my tablet in this crappy state:
Rooted tab a long while ago with a probably far outdated method.
Looked all over the internet later on how to unlock the bootloader and settled on the manual method in this excellent thread.
I flashed V8 and TWRP without a hitch using nvflash.
I wiped and installed Flexreaper.
I liked it but wanted a higher prize. I make a nandroid backup of it onto the external_sd and wiped and installed CM 10.1 from this thread.
This is where everything started going sour. It told me the install was invalid halfway. Disappointed, I wiped again and tried to restore my nandroid backup. It seemed to restore properly, but then Skrillax hung forever loading the kernel.
I wiped again and installed Flexreaper fresh. This time it booted. I downloaded the newest unofficial version of CM they mention on their wiki.
Booted to recovery and installed CM 10. It ran fine and I was impressed with the new OS. Then I noticed the apparent lack of Gapps.
I flashed the Gapps Jellybean package and rebooted. Skrillax hung.
Wiped everything I could fine in the TWRP menu and installed Flexreaper. Got past the primary kernel loading but the android icon would work for a bit then flash, starting all over again.
At this point I flashed several other recoveries, hoping it was my recovery. No such luck. I tried all of them included in V8.
Then finally, I downloaded full stock ICS and flashed it. I rebooted and noticed the same Android flashing thing.
Finally, I flashed V8 again, being the newbie I was, and then suddenly remembered while trying to boot to recovery that the Full install probably rewrote the recovery-from-boot.p.
And here I am.
Tl;dr version:
Went click-happy with ROMs, wiping, and recovery flashing until I was left with a stock OS that wouldn't boot with a Skrillax bootloader but no recovery.
The good news is, I still have cpuid+sbk, it still boots to APX (no idea how I didn't screw that up too.), and I have a nandroid backup on my external_sd which is probably untouched, since I was careful to not wipe it in TWRP.
Please help me fix this. I don't want an excuse to waste money on a flashy new Nexus or Asus Transformer tablet, I already have too many for my wallet's comfort.
I quess you renamed stock rom to update.zip and than flashed it? If you havent do it, put it on sd card and pres power+vol down (if nuttin happens than vol up). That shld trigger flashing proces
poslato sa elmag radija
uglyjohny said:
I quess you renamed stock rom to update.zip and than flashed it? If you havent do it, put it on sd card and pres power+vol down (if nuttin happens than vol up). That shld trigger flashing proces
poslato sa elmag radija
Click to expand...
Click to collapse
I don't have access to a micro sd card reader if the file must be placed on the micro SD card. I already have flashed the stock rom supposedly via TWRP, so I shouldn't have to flash it again, I wouldn't think. If I do, I guess I'll have to get a reader.
Yes. Micro sd. Rename it. You have guodes gere on xda. Im hoping it will help you.
poslato sa elmag radija
It didn't work. Still in same state as before.
I also have access to fastboot if that would help.
m27frogy said:
Simply put, this is what happens when a rooting newbie discovers custom bootloaders and ROMs.
Current State:
A full stock ROM installed (no root) with the Skrillax V8 bootloader plopped on top of it. (which of course means the recovery-from-boot.p file still exists and that I don't have CWM.) The tablet will show the Acer logo then the Android logo and will give the appearance of booting. Then the icon flashes. It does this intermittently and forever.
What I want:
CM 10+ running with Skrillax and TWRP stably. I'd go with Flexreaper for next choice. Maybe I'll try to compile a KitKat version for it someday. Who knows.
How I managed to get my tablet in this crappy state:
Rooted tab a long while ago with a probably far outdated method.
Looked all over the internet later on how to unlock the bootloader and settled on the manual method in this excellent thread.
I flashed V8 and TWRP without a hitch using nvflash.
I wiped and installed Flexreaper.
I liked it but wanted a higher prize. I make a nandroid backup of it onto the external_sd and wiped and installed CM 10.1 from this thread.
This is where everything started going sour. It told me the install was invalid halfway. Disappointed, I wiped again and tried to restore my nandroid backup. It seemed to restore properly, but then Skrillax hung forever loading the kernel.
I wiped again and installed Flexreaper fresh. This time it booted. I downloaded the newest unofficial version of CM they mention on their wiki.
Booted to recovery and installed CM 10. It ran fine and I was impressed with the new OS. Then I noticed the apparent lack of Gapps.
I flashed the Gapps Jellybean package and rebooted. Skrillax hung.
Wiped everything I could fine in the TWRP menu and installed Flexreaper. Got past the primary kernel loading but the android icon would work for a bit then flash, starting all over again.
At this point I flashed several other recoveries, hoping it was my recovery. No such luck. I tried all of them included in V8.
Then finally, I downloaded full stock ICS and flashed it. I rebooted and noticed the same Android flashing thing.
Finally, I flashed V8 again, being the newbie I was, and then suddenly remembered while trying to boot to recovery that the Full install probably rewrote the recovery-from-boot.p.
And here I am.
Tl;dr version:
Went click-happy with ROMs, wiping, and recovery flashing until I was left with a stock OS that wouldn't boot with a Skrillax bootloader but no recovery.
The good news is, I still have cpuid+sbk, it still boots to APX (no idea how I didn't screw that up too.), and I have a nandroid backup on my external_sd which is probably untouched, since I was careful to not wipe it in TWRP.
Please help me fix this. I don't want an excuse to waste money on a flashy new Nexus or Asus Transformer tablet, I already have too many for my wallet's comfort.
Click to expand...
Click to collapse
Babsector should still work - you would need t do a search for it
It seems to have worked properly, sort of. Flashing FLEXReaper results in an "Encryption failed." prompt at boot, which the button, of course, does not work. Wiping everything works except that the prompt notes "E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p4" Trying to reflash V8 with TWRP with the V8.bat file fails at format. More help?
My tablet is still displaying "Encryption failed", the button still doesn't work, and I still love my a500. Help?
Anyone?
I guess I'm screwed, then.
In the end, I think my data partition failed. Formatting or wiping data fails and when installing FlexReaper, it reports /data size as -1. Unless anyone knows how to fix flash memory, I think I'm stuck.
Hi guys
(SM-N9005)
So yesterday I had liquid smooth rom installed for the past month or so (I have been trying a variety of roms for the last year or so) and I was getting some bugs occuring and decided to put a new rom on.
I booted into recovery, did the normal backup, factory restore, clear cache and dalvik, installed the rom and restarted my phone. It then went into a boot loop.
At this point I assumed it was no biggy, so I just went back to recovery and chose to restore with the backup... except it wouldnt. it couldnt recognise the file it had just made.
So I then coppied some previous backups to the external micro sd, stuck the micro sd card in, booted in recovery and tried to recover with them... couldnt recognise them.
I also noticed that when trying to reboot, it came up saying that I didn't have root access... even though I certainly have for the past year.
I tried flashing an updated version of superuser as that was the suggested method on some forum - didnt help the situation.
Now when my phone boot loops, it goes straight to android system recovery <3e> and nolonger have access to CWM
No idea what to do, and my uni work greatly depends on me having access to my phone :/
Any help would be greatly appreciated
my baseband version is LRX21V.N9005XXUGBOB6
i got some problem ... it freak me oute but i founnd how to back my stock firmware backk
you shoud find your firmware ... it can be downloaded from sammobile.
and flash tar.md5 file via ONDIN.
good luck!