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
Related
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.
OK, so I got tired of seeing the garbled bootup screen with pershoot's kernel, so I decided to flash stock recovery and do a factory reset as that is supposed to fix the issue.
So I did that, and sure enough the garbled screen is gone. It proceeds to boot my ROM, and I see the ICS bootanimation from the ICS theme I am running on GalaxyTask ROM. The problem is that it never gets past the boot animation. I even tried ODINing CWM back on and doing a factory reset in CWM. Same issue.
With a phone, I could boot into CWM, out into USB mode, and then transfer a ROM on to the sd card and reinstall it. However when I try to mount as usb storage it fails.
What am I doing wrong? Thanks.
hmmm, found a copy of the 3.1 HC in ODIN format, going tot ry and ODIN that on there and install it.
ok that fixed my issue, sorry for the thread.
My Iconia has CWM installed. I used it a while ago to install the leaked ICS rom. I tried to install the most recent (official) ICS rom. Now my Iconia will not boot past the Iconia logo. I've loaded CWM and formatted everything and reinstalled the official rom. No go.
I figure at this point I have to use nvflash to install a new recovery image and rom. Could somebody tell me how to do that and what files to get?
Thanks
Before doing anything else have you tried wiping cache and data? Has worked for me when a rom wont boot. Have you still got cwm can you access it? If no cwm you can accomplish this by holding power and volume up then toggle the rotation lock.
Yes, I have access to CWM. I have tried wiping everything. I even successfully installed a new rom. The device still will not boot past the Acer logo.
I booted wit hte method you described. Two messages appeared in quick succession, "Clearing data..." and "Clearing cache". After the cache message, the device just sits there doing nothing at all.
Previously I had the data partition encrypted. Could that be causing trouble?
did you install an ICS bootloader?
I'm not sure. That is why I created this thread. I'm looking to get the recovery and OS image necessary to get this device working again.
As the previous poster noted, have you switched to the ICS bootloader? When I flashed my A500 with an ICS rom it too got stuck in a bootloop. I then discovered that I actually had to flash the ICS bootloader berfore installing the new rom.
vangorra said:
My Iconia has CWM installed. I used it a while ago to install the leaked ICS rom. I tried to install the most recent (official) ICS rom. Now my Iconia will not boot past the Iconia logo. I've loaded CWM and formatted everything and reinstalled the official rom. No go.
I figure at this point I have to use nvflash to install a new recovery image and rom. Could somebody tell me how to do that and what files to get?
Thanks
Click to expand...
Click to collapse
You can't install official ROM with CWM. You need Acer recovery! This issue has been answered several times. Use search button!!!
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.
ive tried a whole bunch of roms and the behavior seems to be very consistent.
Here's the scenario, same for every rom:
-boot into TWRP, advanced wipe -> wipe everything
-flash rom over adb sideload
-reboot system
-rom comes up just fine the first time, log into google, restore apps
-any time i reboot after, it sits on "Galaxy s4" boot screen, if I then reboot into recovery, TWRP asks for password because it can't mount partitions.
-only way ive found to get out of this is to format data, then reflash.. only until the first reboot again.
stock rom works flawless, the only custom rom that also worked flawless was task650's AOKP 4.2 rom, which was strange but i used it for couple months. now since i i updated to his latest 4.3 release the same issue came up, so i tried again a number of different roms.. no luck
ive exausted my google-fu and these forums, can someone please help... is this a kernel issue? bad hardware? am i just doing something very simple very wrong?
In twrp, just do the standard wipe, the one that you just swipe the wipe. I think your wiping too much.
Then install the Rom, kernel, and what else you may need, no need to side load it
jd1639 said:
In twrp, just do the standard wipe, the one that you just swipe the wipe. I think your wiping too much.
Then install the Rom, kernel, and what else you may need, no need to side load it
Click to expand...
Click to collapse
same thing, except this time it didnt even boot once, stuck on "galaxy s4" logo, then rebooting back into TWRP prompted a password coz it couldnt mount anything...
i think it gets stuck on boot logo because it cant mount partition same way TWRP cant, but i have no idea why it wouldnt be able to after a reboot or what could be screwing it up
Why don't you try flashing a new recovery?