Kids nabi dream tablet freezing on boot now. cant get it to factor reset think he has the Intel version. Wondering any options I have? Want to reset it back to factory defaults and see if that fixes the freezing issues.
Related
How would I go about changing roms? I can't seem to find a good walkthrough on how to do it. Can anyone point me to one or just tell me how?
I've been wanting to try a different one for a while now, but was afraid of losing all my Angry Birds data (highly important ). I went to turn on the tablet last night and it wouldn't get past what I call the TNT loading screen (the screen after the viewsonic birds, after the gTablet logo, where it is honeycomb looking). It would just cycle through the honeycomb screen until it eventually shut off. I did do a backup in CWM .8. I tried clearing all the cache in CWM, but that didn't help. So I did the factory wipe/reset which got me back to a working TNT Lite, but no data so I thought I could restore the data using CWM option, but it went back to same honeycomb loading cycle and would never boot fully into Android.
So now I'm ready to try another rom since I'm to the point of not having my Angry Birds data anyway. So as the title says I want to try Vegan-tab 7.1.
Thanks
ba1980
Hi everybody, I have a problem and I don't know what to do, so I'm hoping I can get some help with this.
I bought a used cheap tablet off ebay a few months ago. It looked new and came with everything, but its always had software issues. It would be working fine then it would get infinite errors saying various android processes have stopped, it would automatically close apps when I tried to run them, and would prevent me from even changing the settings. This was a frequent problem which I solved by doing a factory reset. This was practically an everyday occurrence until I learned to clear the cache several times a day, which gave me probably around 5 to 7 days before I would have to reset it.
Well, the other day my tablet froze up and wasn't responding. I left it for a long time with no change. I turned it off and rebooted and was greeted by the infinite error problem. I turned it off and cleared the cache from the recovery menu. I tried to boot the tablet and it got stuck at the shiny android logo and won't go past that point. It won't boot into safe mode either.
I tried to do a factory reset like I've done countless times. As soon as I tell it to do the factory reset it says...
-- Wiping data...
Formatting /data...
and.. it does nothing. It never finishes or gets past this point. Not knowing what to do I've turned it off and tried again, I've tried rebooting it but it still won't go past the android logo. I've tried just letting it sit while supposedly "formatting" but that didn't do any good either. Has anyone else encountered this problem before?
I've been trying to figure out how to fix it as I'm broke and can't just go buy another tablet. I'm assuming my only option at this point is to flash a rom, but does it need to be rooted in order to do that? Can I even flash a rom when the tablet won't even do a factory reset and format the data?
Any ideas?
Thanks in advance.
Hello everyone,
Not sure if this is the right area to ask. If it's not my apologies. I am trying to fix an ellipsis 7. My cousin had it requesting a system update but he kept on postponing it. when he did decide to update it there was a glitch I assume and android was somehow wiped from the tablet. I have managed to get into factory mode but there is no way to do a factory reset. In factory mode all I see is reboot, auto test, manual test, item test, tet report, debug test, clear emmc, safe mode, and version. I have tried both clear emmc and safe mode, but nothing happens there. I have checked version and like I said it shows no android version on it which I assume means no android on the device. Is there some way of making a bootable sd card to get the software back on it?
Is there anyone with any ideas?
Now this is the weirdest thing I've ever encountered! I have a Samsung Galaxy Note 8.0 tablet (n5110) which runs TWRP recovery and Resurrection-Remix-5.7.4 (CM13 based). Everything used to work beautifully until the end of July when an app called “EPB DVR Manager” (in the Play store) received an update. My tablet had to do a whole bunch of updates, so I gave it the “go” and Play Store started doing its thing, updating one app after the other.
At some point the tablet froze. Dead. Even the clock in the status bar stopped. I had to reset the device by pressing and holding power until it rebooted. The next thing was ... boot loop. It seemed to finish the boot animation and at the point when the main screen is supposed to show up it rebooted!
Tried to wipe dalvik & cache. No go, still boot loop. Had to format data to get the device back to life. From there it took me quite some hours of repeated tries of restoring 100+ apps and crashing the device all over until I figured out that it was this specific app - the “EPB DVR Manager”. After figuring out that this app causes the problem, I did two more attempts to confirm what is going on:
First, I did a wipe of dalvik, cache & data, reboot, android setup wizard (setup Google account). Then, as the first action at all, I tried to install the “EPB DVR Manager”. Boom - device messed up again.
Second, I reverted back to stock firmware (kitkat) and installed the “EPB DVR Manager” - no problem at all. So it has something to do with the Resurrection-Remix ROM, but here's the thing:
I have 3 different devices (a Moto G 3rd Gen, a LG GPAD 7.0 and that Samsung Note 8.0) and all three of them run Resurrection-Remix 5.7.4 and the Samsung is the only device which all in a sudden has these catastrophic problems with the latest version of this app (earlier versions installed/updated fine).
Now I understand that my devices run different kernels with different hardware drivers despite all of them running RR-5.7.4.
I would really like to get a clue about what the heck is going on here. Now before y'all are telling me that RR-5.7.4 is dead because it is based on CM13 - I know that. Still, RR-5.7.4 is a way better daily driver than the newer Nougat builds. So how should I try to get “live logs” because the problem always ends in a crashed installation and Android needs a full wipe to recover. I would like to find out what is going on to be able to let the app developer know about the problem (if the app's apk is at least partially to blame).
Even if it turns out that it is RR's fault (and therefore the bug will not be fixed because RR-5.7.4 is dead) I would still want to learn how such a simple transaction like installing an app can cause such a dramatic (and 100% reproducible) crash of Android's data partition.
Thanks for any suggestions on how to catch logging information for this kind of mystery.
Markus.
Hi all,
Last night my phone started to randomly reboot itself, even in Safe Mode! It's now to the point where I can't even login -- I enter my pin, the 'Phone is starting' overlay shows for a while, and then it suddenly reboots. I haven't installed a new app for at least 2 weeks at this point, and the reboot was happening before I updated my apps. After updating, things seemed to get worse maybe?
Is there any way I can salvage my phone or do I have to hard factory reset via hardware buttons?
Its called bootloop. you need to flash your phone to fix this problem and flashing can fix all the software issues of your device.
I was afraid of that... Just a bit worrying that it happened randomly when running stock.
Ok, thanks!
I had same issue when ran android 9 in 2019, however, I fix this issue by doing a clean flash. Yes, you will lose everything, so make sure you do a backup via google.
Tom_usborne said:
Its called bootloop. you need to flash your phone to fix this problem and flashing can fix all the software issues of your device.
Click to expand...
Click to collapse
If you didn't add an app or update that caused it either the boot load got corrupted or it's a hardware issue. The flash memory should not spontaneously get corrupted unless it's defective ie a hardware issue. However anything is possible... quantum physics.
More than likely it was a poorly written app or update that caused it. 3rd party launchers and power management apps are prime suspects. It may take a week or more to manifest its self as a boot loop. Any signs of system lagging or instability should be taken seriously as they are the only warnings you may get before a boot loop*.
A virus or rootkit** is another prime candidate.
Do a factory reset now. Be wary of which apps you load and avoid any updates until the system is know to be stable. Then add apps and updates one at a time. Updates many times aren't really needed.
Over a year ago I had 2 back to back boot loops on my Note 10+... yes, and 2 factory resets and full reloads.
The prime suspects were as I mentioned above. Neither one was reloaded after the 3red factory reset. A year latter that 3rd reload is still running fast and stable. Fun times
**if your Android version is 9 or above a factory reset will purge any virus or rootkit as long as you don't inadvertently reintroduce it. Be careful what apps you load and what you download.
If the Android version is 8 or below, they are suspectable to a nasty rootkit that requires a firmware reflash to purge. Pie and above are not.
1. For me, it was also itself rebooting, only while phone were in pocket / case. So do not use any of them (searched on reddit forum, was exactly same topic)
2. Maybe sim ejection tool is not correct be inside, don't often open and close it