Navon Platinum Explorer fix boot loop - Android Q&A, Help & Troubleshooting

The history of the tablet
My father bought this tablet to use as a GPS navigation, but the dalvik chache is filled up completly so the tablet can't boot. So we took it back to the person whom we bought it and he reinstalled the operating system on it, but the main issue is left unresolved. That was about 5-6 years ago. After some months I read about this topic and I figured out how can I clear the dalvik-chache my self, but I can't solve the issue permanently. I left the tablet on the shelf for years, and now I want to completly repair the tablet. (My main purpose with this is to learn how these things work.) But now I can't wipe the dalvik chache with DDMS because it doesn't recognize the device.
From the tablet
The tablet is a Navon Platinum Explorer (which is not a Navon tablet) and there is another tablet called Evolio Evotab Fun wich is almost the same.
Specifications
OS: Android 4.0
Screen: 7 inch TFT LCD capacitive tuch screen, 800x480 pixels
CPU: 1,2GHz, Cortex A8
GPU: Mail-400 ghraphical cpu
Symptoms
When I simply turn on it displays the android logo and stuck there.
If I press [Vol Up]/[Vol Down] + [Power] it connects or if already connected to the PC it disconnects and doesnot display anything.
Windows 10 doesn't see the device, but the Oracle VM shows as an USB device with name: Onda (unverified) V972 tablet in flashing mode
I stuck at
finding a boot.img that I can try to flush on the device, but I also don't know that this is possible because nothing recognize the tablet (I tried with fastboot, adb and ddms).
My goal with this tablet is
1. Fix the bootloop, so the device can start
2. Install some kind of Linux on it

Related

[Q] ALLWINNER A10 Booting Problems, stuck on Android Logo

Hi
Having major issues with my Tablet
Make - ArtView, Model - AT9C-A10WAA
Its an Allwinner A10 with ARM Cotex A8 and 1GB DDR3 Ram.
Turn it on and it just hangs and shows Android Logo for ever. Have tried coupl eof things to resolve such as use LiveSuit to flash new img.
I have downloaded both images from Artview Support Website and no joy opn either, tried another rom but still no luck each time just hangs and gets stuck on android logo.
I did however manage to get tablet to load up, and it worked fine but not sure if relaterd but went into settings and signed in with my gmail account and then just froze, turned off and then got stucvk again at android logo.
I have since tried reflashing but no joy. Tried the Advanced format setting on LiveSuit with rom from ArtView but nothing.
Any ideas what to do, rather than using LiveSuit rebooted tablet holding down VOL - and Power into Recovery Mode but when selecting flash from SD Card it doesnt show anything

BRICKED 7inch Irola Tablet...PLEASE HELP

BRICKED 7inch Irola Tablet...PLEASE HELP
I am in DIRE need of some help with my tablet. I received this irola dx752 tablet bricked and cannot fix it for the life of me. I am able to hold power and volume up and get into recovery system version 4.2.01. I Have tried a factory reset and a wipe system cache and the tablet just reboots to the green robot with and exclamation mark. If I press volume up, it brings me back to the system recovery. Now i am not very versed in ADB but I tried to sideload just about every firmware I could find for an a13 allwinner a8 cortex 7inch tablet, since the irola website has taken down its firmware. Also, fastboot will not work on this tablet whatsoever (it just says waiting for device) when i enter any command. I have never seen this tablet boot into a rom of any kind and therefore cannot tell if USB Debugging was ever enabled. I also Have tried different drivers but the one that seem to hold is the Android ADB Interface. CAN ANYONE PLEASE GIVE ME SOME SUGGESTIONS OR SOME HELP? It would be greatly appreciated. Thank you.

qualcomm MDP 810 soft bricked itself

HI my MDP 810 tablet soft bricked itself after crashing. it can still boot into recovery and fastboot but whenever i try booting normally it shuts itself off after the blue LED light comes on and displaying the penguin (boot) logo.
Ive tried factory reset from recovery and wiping data and cache but it doesnt solve the problem. When i turn it on with a depleted battery the OS home shows with the message that it is shutting down. Is there a way around this or is it possible to get a flash backup from another mdp 810 owner? I wasnt even able to create a backup of it because it bricked itself on the first day.
i think you should contact intrinsyc for that
i assume that's where you got the tablet from?
tried to get approved but was rejected, no reason given
join have a tablet TIR 8960 is preloaded with windows rt, tablet says about the problems of the system,

Q88 bricked itself

Hello,
I have a tablet that looks similar to Q88 A13. CPU is wm8801, OS - Android 4.1. So I had stopped using it and left it sit for like 1 year. Now I charged it and tried to turn on, but it wouldn't get past first logo(the one that appears first, not the os loading one) and would attempt to go into recovery itself, but then the android with exclamation mark would appear for a while and then device would reboot and so on and so on...
Then I triggered a hard reset with a button combo, but it didn't really help. Tablet stopped trying to go into recovery and simply kept getting stuck at logo.
I can't access recovery, and neither ADB nor fastboot is working. PC with win 7 reports it as unrecognized device and other PC with win xp doesn't even see that anything is connected to it.
I've tried unsoldering the battery, completely discharging tablet without it, soldered it back on, but didn't help.
Help?
bump
Try Livesuit 1.11.
I've used it to load several ROM's
I'm currently running FaaastJB v2.5 found at http://forum.xda-developers.com/showthread.php?t=2447819

SGP311 boot loop (might be HW bricked)

So mom dropped off her old Xperia Tablet Z SGP311 as a "gift". It did not work for her anymore, so if I wanted it and could fix it then I would have another tablet in the pile.
Her description of what did not work was what you would expect from a non-techie aka "some error turned up but I cannot remember what the screen said, so can you fix it?".
In the beginning I thought the problem was the common USB/charging problem, however I feel anything about this tablet seems different than other Android tablets, so after finally managing how volume buttons along with power buttons work, I could rule out it was a charging issue.
Getting the Tablet to boot it seemed that it had been updated and was booting into OS doing the "optimising applications 1 out of 258". However going to the step "starting applications", then tablet would just reboot a few times and then start over with optimising applications, starting applications, reboot and repeat all over. So some sort of bootloop.
I then used Sony's Xperia Companion to repair the tablet from fastboot (volume up + power) which succeded until it should reboot the tablet, then I was stuck in the same loop as above.
After a few tries I then managed to unlock bootloader and get TWRP 3.2.2 booted onto the tablet (booted NOT installed since I have no root).
With TWRP I tried deleting Dalvik cache etc., which did not help the situation, same bootloop.
With TWRP I then gave LineageOS a shot, but LineageOS experience kinda the same bootloop (both LineageOS 14.1 and 15.1).
LineageOS boots fine and proceeds with the fresh install questions (region, timezone, Internet access) but as soon as I hit next on the "Location Services" page the tablet will reboot.
Since this tablet has no value to me, I have tried deleting all data on all partitions from TWRP, I have checked the filesystem with e2fsck on the tablet which shows no errors, but in any attempts it simply reboots at the same stage every time.
So are we at the level where this might be some internal hardware failure (GPS/WiFi chip, NVRAM)? Or is there any suggestions of what else to try other than throwing this to recycle bin.
bjoeg said:
So are we at the level where this might be some internal hardware failure (GPS/WiFi chip, NVRAM)? Or is there any suggestions of what else to try other than throwing this to recycle bin.
Click to expand...
Click to collapse
probably memory problem either RAM or ROM.

Categories

Resources