Hi, I just flashed CM7.2 MiRaGe - KANG build, from the recovery, and now i`m stuck at it.
I did a dalvik wipe before flash it.
Now, every time reboots into recovery. (CWM 3.2.0.1)
I did a nandroid restore, i flashed again, and wipe all and restore, and wipe all and flashed again... :/
Is there any solution, before I search the "back to stock and root again" posts?
Were you trying to install onto the SD card or the internal emmc memory? Give us some more details of which method you were using. I don't understand your reference to a Nandroid restore as part of this. That would normally be used to restore a previous back up.
If you were installing onto SD card then just removing the card should get you back to stock and then you can start again.
If you were installing to internal then it sounds like you have somehow managed to flash just Recovery and not the real ROM. In that case you should be able to just check you have a good ROM download, put MiRaGe back on the SD card, wipe, and reflash it from recovery.
Sorry, I'll start from the beginning
I was on CM 7.1 RC, on emmc (always on emmc) and i downloaded 7.2 mirage, copied it to SD card, reboot to recovery, wipe dalvik, and flashed (and gapps too).
Then rebooted, and rebooted into recovery.
Then i downloaded 7.2 mirage again and flash it, nothing.
Then i did a complete wipe, and flashed again 7.1 rc, reboot, nothing.
Then i restore a previous backup of my 7.1 RC, reboots to recovery.
I turned off for a while too, nothing, it boots into recovery.
That does sound strange as your first steps sound like they should have worked fine, although I probably would have done a data and cache wipe when doing a major ROM change.
What may be worth a try is to power up with N key held down so you get into the boot menu. You can then select the boot source (emmc) and the boot type Normal and then see if that boots into CM7.
If not then it sounds like your Normal boot image has got overwritten with a clockwork image but the flash should update that unless something is failing.
I think you have to try the flash again and watch for errors.
I flashed a couple of times again, and then i make a sd-bootable card with cwm recovery and a new rom and everything goes well now (already installed ics)
A detail: when booting into boot menu, n+power, the source always is set to SD, then I change to emmc, reboot, nothing. Go to that boot menu, and again is set to SD...
Thanks for your time
ooops... it happens again!, how can i fix this, how can i format the boot entirely and start from 0 ?
Mariohyeah said:
ooops... it happens again!, how can i fix this, how can i format the boot entirely and start from 0 ?
Click to expand...
Click to collapse
Two ways I think you can go.
1. Make a clockwork SD card from eyeballer image. Put MiRaGe ROM on. This should boot and allow you to install ROM onto emmc. If card is then removed and replaced with a clean single partition non-bootable SD then this should then boot into CM7 MiRaGe and allow you to install gapps and you can then also download ROM Manager app and use that to flash CWM onto emmc as well.
2. If you have a running SD CM7 system, get ROM Manager app from the market, then use Flash CWM function to get a decent 3.2.0.1 Nook Color CWM onto emmc. Then you should be able to power + N select emmc, recovery and be able to boot into recovery OK. From there you can then install a new ROM (e.g. MiRaGe) onto emmc.
If your internal partitioning is completely screwed up then you will need to check out
http://forum.xda-developers.com/showthread.php?t=914690
and maybe use the repartition-boot-with-stock.zip to get you back to a stock boot set up.
Mariohyeah said:
Sorry, I'll start from the beginning
I was on CM 7.1 RC, on emmc (always on emmc) and i downloaded 7.2 mirage, copied it to SD card, reboot to recovery, wipe dalvik, and flashed (and gapps too).
Then rebooted, and rebooted into recovery.
Then i downloaded 7.2 mirage again and flash it, nothing.
Then i did a complete wipe, and flashed again 7.1 rc, reboot, nothing.
Then i restore a previous backup of my 7.1 RC, reboots to recovery.
I turned off for a while too, nothing, it boots into recovery.
Click to expand...
Click to collapse
A fundamental question.
After flashing and before rebooting, did you remove the uSD card off NC?
Related
I will try to cover any info you might need. I am using windows 7, my phone had 1.5 originally 1.47 hboot. I got the 2.1 official ota.
On monday, I rooted using the pb00img.zip, loaded amon-ra 1.6.2, did factory/data wipe, dalvik wipe, flashed kaos v20, boot looped, tried v.19 with full and dalvik wipe, same.
I have tried all version of kaos from 19-23, evileris 3, celb, cyanogenmod 6. All have the same boot loop, I have done the following:
Reloaded the pb file
Reloaded amon-ra
Have tried manually wiping data and dalvik using adb shell
I have formatted my sd card through windows
I have partitioned my card through amon-ra
Here is a pastebin of my bootup.
http://pastebin.com/SMhKDYZq
The phone starts up with the 3 skateboarding droids, sits there for a bit, screen goes black, i get a little vibrate, then the 3 skaters come back, rinse and repeat.
I have dont have apps2sd, or setcpu. Any help would be greatly appreciated,
cdjadex said:
I will try to cover any info you might need. I am using windows 7, my phone had 1.5 originally 1.47 hboot. I got the 2.1 official ota.
On monday, I rooted using the pb00img.zip, loaded amon-ra 1.6.2, did factory/data wipe, dalvik wipe, flashed kaos v20, boot looped, tried v.19 with full and dalvik wipe, same.
I have tried all version of kaos from 19-23, evileris 3, celb, cyanogenmod 6. All have the same boot loop, I have done the following:
Reloaded the pb file
Reloaded amon-ra
Have tried manually wiping data and dalvik using adb shell
I have formatted my sd card through windows
I have partitioned my card through amon-ra
Here is a pastebin of my bootup.
http://pastebin.com/SMhKDYZq
The phone starts up with the 3 skateboarding droids, sits there for a bit, screen goes black, i get a little vibrate, then the 3 skaters come back, rinse and repeat.
I have dont have apps2sd, or setcpu. Any help would be greatly appreciated,
Click to expand...
Click to collapse
Did you ever create a nand backup? If so, go back to it first and verify you don't have a hardware issue.
If you don't have a backup, search this forum for the Eris RUU and I'd go back to that and root using the newest method...basically start over from a working phone.
I do have a nand backup, I have been restoring when i leave work because my phone has to be working. It works fine with the OTA 2.1 that i had just rooted...
have you tried doing full data wipe/dalvik wipe after flashing a rom when i first installed roms i didn't wipe anything for 2 or 3 roms but they all seemed to flash over eachother. but then i couldn't flash anything and i thought somehow i broke something. but then i just did a full wipe after a flash and started up like it should have. took a while the first boot but ever since then i haven't run into any issues
Sjflowerhorn said:
have you tried doing full data wipe/dalvik wipe after flashing a rom when i first installed roms i didn't wipe anything for 2 or 3 roms but they all seemed to flash over eachother. but then i couldn't flash anything and i thought somehow i broke something. but then i just did a full wipe after a flash and started up like it should have. took a while the first boot but ever since then i haven't run into any issues
Click to expand...
Click to collapse
I had this same issue last night, though I kept repeating the Nexus-style boot screen (the "X" thing) over and over. I did a full data/dalvik wipe and everything came up just fine. I had this experience with two different CyanogenMod ports.
I have my nook rooted and all of that and for some reason I decided to wipe the thing clean in CWM recovery and now it won't boot to anything unless I boot from SD. I've tried booting into a rom from SD and installing CWM recovery again through rom manager and it says that is has flashed successfully but when I tell it to restart it goes back to the rom on the SD of course, so I tried taking the SD out and holding down the N and booting into recovery and I get nothing no loading screen no nothing, am I not getting CWM installed? Is there a zip I can flash from CWM on SD to flash it?
EDIT!!!!! If i had remembered to format the right things then I wouldn't have had an issue.
If you are having the problem described above remember to format BOOT, System, and Data. And then flash your rom.
See post#4 here: http://forum.xda-developers.com/showthread.php?t=1205047
Thank you I don't know what I was thinking, if I had just formated the right things it would have worked just fine, I am a tard sometimes.
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 an Acer A500, it has the v9 bootloader installed. I also have TWRP 2.6.3 installed as the secondary ROM, the recovery is also completely broken, fastboot and zip will not install on it (TWRP 2.6 is to big), but recovery using 2.4.4.0 does boot. That fine since with secondary and recovery installed I can use TWRP from either, which works great, but if I install a ROM it only boots once, then poof, its as if there is no kernel it will not boot. To boot a new ROM I have to format everything except the external SD (which I have removed) then install the ROM reboot to TWRP install it again, then reboot at which time it will boot about 1 is 3 times, if it fails try again and repeat.
Now the ACER is basically useless now as I can not boot safely to anything other than TWRP, I've tried 2 4.0.3 ROMs but I can not get the Installers to run, I've tried 2 10.1 ROMS boot both booted only once and also a 4.3 ROM (build 5 and 6) boot again both booted only once. I'm out of ideas I'd flash almost anything at this point to reset, but then there is that Windows 8.1 issue in which I can not get ACER driver to work (Duh!), and I do not think the issue is going to be fixed, I can only come up with 2 options 1 the internal storage is going bad, or the entire setup is just toast, since it can work, it just does not do so more than once.
Currently I have 10.2 (build6) running, so long as I do not need to reboot, so for now it is charging.
Any suggestions,
ERIC
egandt said:
Now the ACER is basically useless now as I can not boot safely to anything other than TWRP
ERIC
Click to expand...
Click to collapse
I have same problem with TWRP. Try to replace TWRP with TouchRecovery