Is this the right forum area? I posted over in CF-Auto root with no response, figured I would try here.
http://www.randmcnally.com/product/tnd-tablet
It supposedly has a custom proprietary build Rand McNally uses. It has a built in recovery of which I'll post a screen.
The "reboot to bootloader" option simply hangs on the boot screen.
I've tried kingroot/kingoroot, towelroot, and googled my life away trying to root this GPS/tablet.
There doesn't seem to be a way to flash a custom recovery without bricking it(unsupported device), and there's no way to pull the recovery.img without root!
Can anyone help? The rooting of these devices would open up a world of possibilities.
How is it possible to root this thing if its not recognized by fastboot? Any attempt of rebooting into bootloader even through external tools is stuck on bootscreen.
It allows the Delevoper option of unlocking bootloader, but how if I can't even send the command? Not only is bootloader locked, it seems completely off limits.
Some possibly relevant details from bugreport, and the logcat file???
========================================================
== dumpstate: 2017-08-30 20:23:15
========================================================
Build: LVY48E.20170428-091903
Build fingerprint: 'TNDT80B/tulip_p1/tulip-p1:5.1.1/LVY48E/20170428-091903:user/'
Bootloader: unknown
Radio: unknown
Network: (unknown)
Kernel: Linux version 3.10.65 ([email protected]) (gcc version 4.9.3 20150113 (prerelease) (Linaro GCC 4.9-2015.01-3) ) #3 SMP PREEMPT Fri Apr 28 09:03:37 CST 2017
Command line: enforcing=1 earlyprintk=sunxi-uart,0x01c28000 initcall_debug=0 console=ttyS0,115200 loglevel=0 root=/dev/system init=/init [email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected][email protected]:[email protected]:[email protected]:[email protected] cma=256M androidboot.serialno=74005034440c1c05088e androidboot.hardware=sun50iw1p1
------ MMC PERF (/sys/block/mmcblk0/stat) ------
*** /sys/block/mmcblk0/stat: No such file or directory
Ok, it is now recognized by my system by fastboot, but no fastboot commands will work! Stuck on the boot animation even though recognized.
Any checks for OEM Device info, Locked bootloader, or Tamper flags just hangs...
Down another rabbit hole after finding out this thing is an "AllWinner" brand Android tablet...
Hey, any chance you could upload the Launcher APK and lib s? I'm also investigating root on a TND740 (which is also Android based), so maybe I can help if I find anything out. The launcher would be awesome though. Thanks!
I'd love to put that software on my Asus Tablet <3 hook us up
tnd t80b bootloop no adb permissions
Hey guys, I have a bootloop on this tablet. And I managed to wipe adb certificates off it so I cant even adb in anymore. TND T80B Anyone have a stock Firmware or any clue how to use this tablet again.
Thanks for any help!
How did u get into fastboot mode from engineering menu? I cant seem too, it just reboots too system after about 1 min.
I assume, like to enter recovery menu, there is a key press combo i need too use after choosing fastboot mode, but i dont know what it is
I think you adb reboot ....
it could be .. bootloader.. fastboot..RUU...RRU..recovery..
I cant remember exactly. I had to get root first I think. this device has an Allwinner A64 chipset on a tulip board. Allwinner has everything available on github and a wiki site for building roms for this device and others.
Felmode... look it up... these are unbrickable...
if you find a rom or a Stockrom let me know please
---------- Post added at 12:30 AM ---------- Previous post was at 12:26 AM ----------
if I could ever get a copy of the api or a compiler to work correctly on linux... I'd have my own to flash on.
Also I've never tried but there is another USB port on the back of this thing where the 2nd GPS hooks on. you might be able to boot or access some un secured path through that.
Lostwon said:
I think you adb reboot ....
it could be .. bootloader.. fastboot..RUU...RRU..recovery..
I cant remember exactly. I had to get root first I think. this device has an Allwinner A64 chipset on a tulip board. Allwinner has everything available on github and a wiki site for building roms for this device and others.
Felmode... look it up... these are unbrickable...
if you find a rom or a Stockrom let me know please
---------- Post added at 12:30 AM ---------- Previous post was at 12:26 AM ----------
if I could ever get a copy of the api or a compiler to work correctly on linux... I'd have my own to flash on.
Also I've never tried but there is another USB port on the back of this thing where the 2nd GPS hooks on. you might be able to boot or access some un secured path through that.
Click to expand...
Click to collapse
I guess i should have been more careful when i posted here, i actually have an Rand McNally OveryDryve 8 not a TND series tablet, and thats the one i cant get into fastboot too get the bootloader unlocked and then root and stuff....
If i cant get fastboot commands too works i cant do anything else...
I would use dr.Phone like others have, but it does not install seemless root apparently, it modifies files that break updates, and i dont want that, id prefer Magisk with seemless so i can then install safteynet and gapps properly
How can I get a copy of the truck gps app to load on another tablet?
AllenScott said:
How can I get a copy of the truck gps app to load on another tablet?
Click to expand...
Click to collapse
Short answer.... You cant.... I tried with a previously rooted model too send the apk file, even if it installs on your new device, it wont work without ALL of the RM Services apps as well, and all have too be system apps and setup just right or its not going too work... I gave up and never ened up getting it too work because i couldnt get half of the apks too istall let alone run without crashing constantly...
I've spoken to rand and they seem to think their GPS hardware is better than that found in today's phones like they are Holy as ####. Their systems are junk but the 2.0 navigation is far worse, I want to pull the old software and install it to a newer or different device like y'all. I'm willing to put some money towards the goal, I know some of my friends would do the same, anyone up for starting a fund, or someone have the skills to make it happen? Let's get this rolling!
Side notes, if you look at the older devices specifically the tndt80 that has Google play on it, (newer ones don't!) I at one time had the installation files and installed them onto a cell phone. I was able to run a route comparison before the software realized my Samsung galaxy wasn't a tnd tablet, once it realized it wasn't one of their devices it had a message saying that and closed down.
I'm pretty sure that's on one of my old phones with a busted screen, I'll get some screens ordered and see if I'm right (hopefully!)
So besides the installation files that would be the next hurdle, maybe an emulator to bypass the device name/serial etc to allow it to run?
Related
Hello XDA community, this is my first thread, i had never needed to post anything cause i always find everything im searching for in this awesome community... until now :crying:
Last week I got a new android device which is made by Polaroid, model: PSPR355, its a pretty low class device but I thought it would be enough for me.... then i realize I needed root permissions, for obvious reasons... easy I thought... i had rooted many devices...how hard can it be...right?... WRONG! :crying: . The first problem I encountered were the drivers..couldnt find em anywhere... fortunatelly i found a tutorial were i could install the drivers in a different way...although I took 2 days to do this...Ive been about 5 days trying to root my phone.... Ive tryied about 10 different programs with their different versions... and any of those rooted my phone, nor Oneclikroot, nor Unlockroot, etc, etc..... I really gave up trying to find something on the web cause i didnt even find the phone on its official site, so I came her defeated asking for any solution, idea, or if you want to help me with commands, a programm or anything else to root my phone, Im not even afraid of trying programming (Im trying to learn how to make roms, kernels, etc for this phone cause theres nothing on the web abou it but this is a theme for another time) if you wanted to help me i would really appreciate it, im a little desperate so anything would come useful thanks everyone and I hoppe you can help me!!! :fingers-crossed:
MecaMarck said:
If you wanted to help me i would really appreciate it, im a little desperate so anything would come useful thanks everyone and I hoppe you can help me!!! :fingers-crossed:
Click to expand...
Click to collapse
I would recommend trying the towelroot application. It can be downloaded from here, just click on the orange lambda to download the tr.apk file. Then open towelroot follow the instructions in the application. After the device reboots I would recommend downloading, Root Checker Basic form the Play Store and running that to make sure your device is rooted. Finally install SuperSU, and you should be good to go.
First thanks for answering so fast shimp208! And I guess I forgot to tell that I was in Mexico and Im using Telcel's network, I downloaded and installed the apk file but it doesnt starts I click the button pops up a black screen and then closes to the last app I used...any idea about this error...or if its beacuse of the carrier, by the way the device has Android 2.3.7 I dont know if it has something to do with this error
MecaMarck said:
First thanks for answering so fast shimp208! And I guess I forgot to tell that I was in Mexico and Im using Telcel's network, I downloaded and installed the apk file but it doesnt starts I click the button pops up a black screen and then closes to the last app I used...any idea about this error...or if its beacuse of the carrier, by the way the device has Android 2.3.7 I dont know if it has something to do with this error
Click to expand...
Click to collapse
Does it present an error message of any kind before it force closes? Try uninstalling and then re-installing the application, and if that doesn't work go to application manger under settings, find the towelroot application and select the options to clear it's cache and data. The carrier won't have any effect in this case, and with it being Android 2.3.7 your device most definitely has a kernel build date before June 3rd, 2014.
shimp208 said:
Does it present an error message of any kind before it force closes? Try uninstalling and then re-installing the application, and if that doesn't work go to application manger under settings, find the towelroot application and select the options to clear it's cache and data. The carrier won't have any effect in this case, and with it being Android 2.3.7 your device most definitely has a kernel build date before June 3rd, 2014.
Click to expand...
Click to collapse
No it simply closes without showing anything, and without even giving the "Force Close" message, i thought it was because i first installed it on the sd card, or because of not enough space but no, I moved it to the phone and uninstalled some apps I had, I uninstalled and installed towelroot twice and it didnt work, I installed the v1 of it and i got to the [make it ra1n] screen but when I click the button it closes immediately again without any error message
MecaMarck said:
No it simply closes without showing anything, and without even giving the "Force Close" message, i thought it was because i first installed it on the sd card, or because of not enough space but no, I moved it to the phone and uninstalled some apps I had, I uninstalled and installed towelroot twice and it didnt work, I installed the v1 of it and i got to the [make it ra1n] screen but when I click the button it closes immediately again without any error message
Click to expand...
Click to collapse
Very interesting, while in theory the app should work for any kernel build date earlier then June 3rd, 2014 the app many not be compatible with devices running an Android version less then 4.x.
shimp208 said:
Very interesting, while in theory the app should work for any kernel build date earlier then June 3rd, 2014 the app many not be compatible with devices running an Android version less then 4.x.
Click to expand...
Click to collapse
Yes that´s what i thought, do you think that theres no rooting method for this phone? if so, do yo think there´s a way of doing one?
MecaMarck said:
Yes that´s what i thought, do you think that theres no rooting method for this phone? if so, do yo think there´s a way of doing one?
Click to expand...
Click to collapse
Since you have the usb drivers working on your computer, try booting into the bootloader and using fastboot to see if the command fastboot devices returns anything. If the computer see's the device in fastboot that's a good sign. If your device doesn't have a locked bootloader which it likely doesn't, then I can try and create a rooted system image for you to flash in fastboot. Provided fastboot see's your device if it does, if you can provide me an adb dump of your /system folder then I will see what can be done.
Interesting for me.,.
Sent from my LT26w using xda premium
Same Boat
shimp208 said:
Since you have the usb drivers working on your computer, try booting into the bootloader and using fastboot to see if the command fastboot devices returns anything. If the computer see's the device in fastboot that's a good sign. If your device doesn't have a locked bootloader which it likely doesn't, then I can try and create a rooted system image for you to flash in fastboot. Provided fastboot see's your device if it does, if you can provide me an adb dump of your /system folder then I will see what can be done.
Click to expand...
Click to collapse
I'm in the same boat
I use moto-fastboot (any way it's fastboot)
#:\moto-fastboot devices
? fastboot
don't show any info...
I do a system dump in this way
#:\adb pull / c:\PSPR355
mega,co,nz/#!ThIUQYiS!LLbJ9e1-yVJI4juNlWQuPfa9GFH6HP9lr4X8Gwu1MBY
Change "," please, sorry mod if you want i can delete it! =$
klonic0 said:
I'm in the same boat
I use moto-fastboot (any way it's fastboot)
#:\moto-fastboot devices
? fastboot
don't show any info...
I do a system dump in this way
#:\adb pull / c:\PSPR355
mega,co,nz/#!ThIUQYiS!LLbJ9e1-yVJI4juNlWQuPfa9GFH6HP9lr4X8Gwu1MBY
Change "," please, sorry mod if you want i can delete it! =$
Click to expand...
Click to collapse
Unfortunately if fastboot doesn't show your device without any other flashing utility, even with the system dump there is no way to flash a rooted system image if it was created.
Got to see if this guys do the trick!
http://forum.xda-developers.com/showthread.php?t=2066041
shimp208 said:
Since you have the usb drivers working on your computer, try booting into the bootloader and using fastboot to see if the command fastboot devices returns anything. If the computer see's the device in fastboot that's a good sign. If your device doesn't have a locked bootloader which it likely doesn't, then I can try and create a rooted system image for you to flash in fastboot. Provided fastboot see's your device if it does, if you can provide me an adb dump of your /system folder then I will see what can be done.
Click to expand...
Click to collapse
Hello shimp well I connected my device on FastBoot Mode and my computer recognized it and it installed a driver named: ADB Testing Interface I dont know if thats a good sign or what should I do, I tried entering into recovery mode but it shows only an android little guy and exclamation quote... so I think it doesnt have a recovery boot I dont know if thats relevant, Could you help with the adb dump i dont know how to get it. And.... I dont know if besides you help me with the rooted system image you could teach me how I do this.... anyways thanks a lot for helping me! I'll keep doing everything you need so we can root this device!
MecaMarck said:
Hello shimp well I connected my device on FastBoot Mode and my computer recognized it and it installed a driver named: ADB Testing Interface I dont know if thats a good sign or what should I do, I tried entering into recovery mode but it shows only an android little guy and exclamation quote... so I think it doesnt have a recovery boot I dont know if thats relevant, Could you help with the adb dump i dont know how to get it. And.... I dont know if besides you help me with the rooted system image you could teach me how I do this.... anyways thanks a lot for helping me! I'll keep doing everything you need so we can root this device!
Click to expand...
Click to collapse
Since your computer recognizes the device and installed the driver and shows the device when in fastboot mode that's a good sign. The Android with the exclamation point is part of normal stock Android system recovery, it just means that the recovery menu has been hidden (You should be able to get the menu to appear by pressing the power and both the volume buttons in recovery mode). To dump /system run the following command:
Code:
adb pull /system
Then please send me a link to the /system dump, from there I will make a rooted system image.
Factory Rooted??
Hey guys I'm new to this so I may be wrong but has anybody thought to check if the Polaroid PSPR355 comes Factory Rooted??? I had a Polaroid Tablet, PID something(I forget the name), which I tried for hours to root resulting in: bootloop, hard reset, root, bootloop, hard reset, root, bootloop, hard reset, about to give up. So I Googled how to root Polaroid PID something (again, I forget the name), and I come to a post somewhere(forgot that too) that tells me my Tablet and similar Polaroid electronic devices(as well as most electronic devices coming from China) are factory rooted due to some Chinese law. So after the last hard reset, I downloaded HowToRoot App to check if my Polaroid Tablet is, in fact, rooted. I press the little lock button(root checker) and I find that, to my surprise, my Polaroid Table is in fact rooted. So all I had to do was download SuperSU from Google Play Store and Update Binary when prompted and I was Super User. Don't know if this helps but it worked for me.
Haven't been able to find anything on this model as of yet, looking for info for rooting and any possible roms/hacks. also asking for thumper1436 who's original thread is http://forum.xda-developers.com/general/xda-assist/please-help-stock-nextbook-10l-quad-t3254936 --there (sorry, not familiar with proper tagging features for the bulletin boards just yet).
thanks for any info in advance!
found some hope from https://www.youtube.com/watch?v=baIhaJ0Zz5U . not the exact model but a starting point maybe? we'll see.
::edit:: i'm an idiot. after mulling about and using the commands in the video comments, I kind of figured it out. booted into bootloader, flashed the boot and recovery img's via fastboot, and so far so good. rebooted into recovery and twrp is up (yay). now to work on rooting (hopefully as easy as installing the zip files through twrp). worst thing that can happen is I brick it. wish me luck.
oh yeah, android 5.0 kernel version 3.10.20-x86_64byt build v 1.0.7
okay, so attempted backup via twrp but it failed. figured wth, flashed recovery zip and super su zip from link in youtube video ( https://www.youtube.com/watch?v=baIhaJ0Zz5U ). after rebooting, went to play store and installed a root checker, and viola. so root achieved.
keep in mind that using twrp wouldn't work without keyboard attached (which is annoying). controls are normal, though throughout the process the screen goes portrait mode instead of landscape, so figuring out "mouse" controls is wonky but doable. after root, using the touchscreen is all but gone (very very buggy, not sure how to fix as of yet). if i could find a recovery image from mfg it'd be great (already emailed them about it, but very very doubtful it'll show up).
tl;dr
root is possible, but makes system buggy.
DO THIS AT YOUR OWN RISK! YOU ARE RESPONSIBLE IF YOU BRICK YOUR TABLET! WARRANTY IS VOID, ETC.
-----please do a clean install/wipe/factory reset first. it's always a good idea and can save you the headache from bugs that can occur from not doing this. please. google is your friend if you're a bit lost on how to do anything referenced in this "guide" ----
I take no claim of ownership of the files used in this process. respect goes out to the owners/originators.
1) install working adb drivers (through android sdk or however). I went with installing from here . don't forget the java crap (link is on this page too, just read the instructions).
2) download twrp and recovery files from here
3) i downloaded the nocturnal adb stuff as well from here . Was easier to keep files organized imo.
4a) extract files from both and put files from step 2 into the same directory as files from step 3 ( will look like image from looky looky when done right). don't forget to copy the recovery.zip and SuperSU246.zip to the root of an external sd card, going to need these in the future.
4b) i forgot about the developer options thing. if you're working with the tablet already booted up like normal, you have to enable developer options and turn on usb debugging (there's all the info on that in the youtube video referenced from the post above, or by google-ing it).
5) hold down shift and right click in window, select "open command window here". if tablet is loaded up like normal, you'll type in "adb devices" to make sure the drivers installed okay (it'll show a device if all is done right). if tablet is already in the bootloader, type in "fastboot devices" and it'll show a device if all is done right. google is your friend on how to get into the bootloader, or you can always load up the tablet, verify the adb drivers are working, and go to step 6.
6) type in "adb reboot bootloader". when it loads up, type "fastboot flash boot boot.img" and hit enter. When that completes, type in "fastboot flash recovery twrp_recovery.img" and hit enter. all should show okay (mine had a data error from the backup, didn't seem to effect much, though i'll be going back and redoing this with a clearing of data/factory reset first that will hopefully kill the buggyness of the touchscreen.
7) use the volume down button to change the option to "recovery mode" and select with power button. once there the fun begins.
8) as stated before, using the mouse pad seems the only way to go. up is up, down is down. the screen however is turned on it's side this way.
go to the "install" button and click on it. navigate to the root of the external sd card (click the storage button at the top, change to external_sd) and click ok. should have to just scroll down and select the recovery.zip file. click "add more zips" button and select the SuperSU246.zip file. click and drag the "swipe to confirm flash" button and release. wait for confirmation of success.
9) go back to main menu (I used the navigation buttons on the physical keyboard) and reboot into the system.
that's all there is. as stated, it is buggy as hell and the touchscreen is all buggered up. but using the keyboard/touchpad seems to work. not sure of too many other bugs yet as this is fresh off the press and I haven't done anything else with the tablet since doing this (besides installing the root check program from the play store and running it to verify it worked.
hope this helps someone =)
::edit:: damn this is a little confusing to read, sorry about that. first time attempting a guide like this.
device info from skipsoft android toolkit.
DEVICE INFORMATION
==================
Product Manufacturer: Yifang
Product Model: NXA101LTE116
Model ID:
Device Type: NXA101LTE116
Device Characteristics: nosdcard,tablet
Product Serial Number: YFGV0715030938
Build Description: nxm1017bapl_64-user 5.0 LRX21V 20150708.171530 release-keys
Build Date: Wed Jul 8 17:17:24 CST 2015
Hardware: nxm1017bapl
Board Platform: baytrail
Build Version Release: 5.0
Build ID: LRX21V
Bootloader: unknown
Build PDA:
CSC Sales Code:
Region Code: US
Ro.secure Level: 1
Ro.adb.secure Level: 1
Selinux.enforce Level:
Selinux Level:
Alarm Alert: Alarm_Classic.ogg
Notification Sound: pixiedust.ogg
Ringtone: Ring_Synth_04.ogg
------------------------------------------------------------------------------------
Boot Image Status is: SECURE [based on ro.secure value]
Note: This is only an indictation if the boot image files have been modified
------------------------------------------------------------------------------------
::edit:: info was prior to rooting device.
Do you happen to have a stock image or a backup available?
daleguthery said:
Do you happen to have a stock image or a backup available?
Click to expand...
Click to collapse
unfortunately no. i tried emailing the mfg to no avail (they claim they don't have the image files to restore them). haven't tried doing a factory restore yet, though i doubt that'd help. right now i just use it as a "laptop" with using the track pad instead of the touch screen. still a work in progress, just been busy with life happenings. will update if i can find out more (or if i manage to get my hands on another untouched unit that i can try and dump or something).
I have also tried contacting the mfg, and they told me the same thing. I read somewhere that this tablet was actually made by eFun. The stock rom for the model without LTE will work on this tablet, however there are somethings that don't work correctly, the first being enabling LTE and recognizing a SIM card. The others are camera orientation, and screen rotation is always upside-down.
daleguthery said:
I have also tried contacting the mfg, and they told me the same thing. I read somewhere that this tablet was actually made by eFun. The stock rom for the model without LTE will work on this tablet, however there are somethings that don't work correctly, the first being enabling LTE and recognizing a SIM card. The others are camera orientation, and screen rotation is always upside-down.
Click to expand...
Click to collapse
I have the same tablet. I will be attempting to root.
Hello! I am new and don't have much experience here, but I will try to post any/all needed info. I don't really know what I am doing, so a customized step-by-step guide would be awesome.
I recently got two tablets from a garage sale. One is an azpenpc model A745 (Build number KVT49L test-keys), and the other is a "Digital2 Plus" (Build number polaris_chiphd-eng 4.4.2 KVT49L 20140515 test-keys) tablet. Both run Android 4.4.2 with kernel 3.4.39.
The Asenpc one has a QuadCore-A33 processor, and the Digital2 one has a DualCore-A23. They are almost identical and have identical physical layout (buttons, camera, speaker...) Developer tools were enabled, but not root, as far as I know. I used factory reset first thing. I will also add that the UX is very unusual, especially on the Digital2 one. (The layout of the black bar that appears on swiping up from the bottom of the screen is unusual and awkward on the D2, and the other one has a hotbar 90* from the horizontal!)
I don't really trust these not to have weird bugs on them. Both have weird apps installed with vague purposes and lots of permissions, the Digital2 tablet has a massive number of un-unistallable factory apps that are total crap, and the AsenPC one has been displaying suspicious surveys in the web browser if I leave it alone too long. For this reason, and to try to get more space (hopefully), I would like to nuke from orbit.
I don't have any money and not much interest invested in these, though I would like them to work when I get done.
How do I install a custom ROM and Google Apps on these? Do ROMs for these exist (especially now that CyanogenMod went OOB), and what would I need to do to be able to install them?
Do I need Root or just an unlocked bootloader, and how do I get those on such unusual devices?
Currently, I think that I need to install the Android SDK, get a custom recovery and unlocked bootloader, and then somehow(?) use the recovery to install the image (never mind how I even get it there for the recovery to install!). There is also some way to do this directly with the SDK. I do not know the real details of how either work.
Thanks! I would really appreciate any help you can offer on how to do this, and extra kudos to anyone who can tell me how to re-arrange the hotbar, hotbar position, and swipe up/down menus too!
I was unable to locate any sections on these two tablets on this forum, or at LineageOS or PacROM. Can you please advise? How do I install a less-bloated and probably safer ROM on these tablets, and where do I actually get it from?
Lets get you started with recovery, unlocking bootloader and root.
Please search if there are roms for you device, and i ll guide on how to install it.
For now, lets get a fresh installation of your device. Sometimes a lot of stupid apps install themselves into the system partition. They are malware. They have un-suspicious names like system process, system monitor, etc. They make the device ectremely laggy and factory reset doesn't help.
Download sdk and platform tools. Just minimal fastboot package will also do.
extract them in say C:\
enable usb debugging
open cmd and do the following. Assuming the folder name is platform-tools.
Code:
cd C:\platform-tools
Code:
adb devices
if you see a device listed here with an id and an online status, everything is fine so far.
Code:
adb reboot bootloader
fastboot devices
again, if you see a device listed here with an id, everything is fine.
Code:
fastboot oem unlock
if it says success, bootloader is now unlocked
you can check using
Code:
fastboot oem device-info
Code:
fastboot reboot
Reboots phone normally
Now obtain a recovery.img for your device. Place it in platform-tools folder.
Code:
adb reboot bootloader
fastboot boot recovery.img
this will temporarily boot recovery, you can install rom from here (provided you find one online), wipe device, etc.
Thats everything you need.
Hit thanks if i helped.
Okay, thanks!
There's just one problem:
I still can't find a ROM for the AzpenPC tablet, and the Digital2 Plus also does not seem to have a ROM -- The serial number is L741GMB1405, and while there was a post on ROMs for a D2, this is a different series than the one listed.
How might I find or make a ROM for these?
i recently was given an nextbook 10a and it works but is forever stuck at the boot screen "nextbook powered by android".
i can get into recovery and factory wipe, etc but makes no difference. ive also gone to nextbook website but there isnt any support for this device.
is there anyway to reflash entire device restore to stock rom via usb cable and software
model # nx16a10132sps
fcc id# s7jnx16a10132sp
ekoms420 said:
i recently was given an nextbook 10a and it works but is forever stuck at the boot screen "nextbook powered by android"....
Click to expand...
Click to collapse
I don't have this device and i can only locate 1 thread where you might be able to obtain some member guidance within that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3654507
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Do you think it could possibly be a Windows tablet and someone tried flashing Android on it I posted the model number and what not I could post a photo of the recovery because it's all good it's all like lines through the words and stuff like this just a thought I had
ekoms420 said:
Do you think it could possibly be a Windows tablet and someone tried flashing.....
Click to expand...
Click to collapse
Your question is a valid one that prompted me to perform a quick Google search using the model number and such and after looking at a little over a half dozen results, I came to the following conclusion.
This came with Android 6.0 and was a budget Tablet that costs approximately $100.00 +/- brand new.
It seems as though the individual who had given you the tablet may have been unsuccessfully attempted one or more actions like Unlocking, Rooting, etc...
With a very limited amount of resources available for this device, there's really not much out there for help but, I'm not stating that there's no help. It's more of where to find it that's the challenge.
I wish that I could be of more help...
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Thank you very much for your time and help. At least I know it was most likely someone's fuk up then faulty
Still been messing with it cuz I have hope it's just soft breaking set but I got into the recovery log files going through them I found this one section I screenshotted check it out it's the same bored as the 8a 16gig version of what not so like those other post around where is has been mentioned to use the 8a Twrp etc on the 10a because it's the same board. This tablet is like the 2nd or 3rd gen that came out 2017 which has like at all winners CPU or something instead of Intel or something like that I've read somewhere and it also has Android nougat 7. 1 out the gate. So in theory I should be able to put that 8a twrp & boot Image to match on this one and then downgrade to 5. 1 or do something like remix Os or something custom.
??!?!?!!!!??????
so how the puck do I put a picture attached of the recovery log.
ekoms420 said:
i recently was given an nextbook 10a and it works but is forever stuck at the boot screen "nextbook powered by android".
i can get into recovery and factory wipe, etc but makes no difference. ive also gone to nextbook website but there isnt any support for this device.
is there anyway to reflash entire device restore to stock rom via usb cable and software
model # nx16a10132sps
fcc id# s7jnx16a10132sp
Click to expand...
Click to collapse
I have the same tablet I think. I can turn on and off and boat into recovery(words are faced and have lines through them) but I'm its staying stuck with Nextbook showing on screen. I'm trying to find stock or something so I can flash and get it fixed. Its a Nextbook 10" Model:NX16A10132sps. FCC ID: S7JNX16A10132SPS. Ill let you know if I find anything
I have both A64 and Intel versions.
The twrp for the 8a DIDN'T work on the A64 when I tried it.
It DOES work on the Intel.
If you can get to stock recovery and its messed up looking with the lines and stuff, that's the A64 version.
Don't hesitate to ask if anyone needs help if it's Intel.
My A64's are both bricked still so i'd be useless there.
Here are my backups from the Intel version.
Ares10a_NXM1021CAP_ES-IntelAtom-[NX16A10132SP-S] - Google Drive
drive.google.com
And how to tell exactly which you have.
Trying to help a friend fix a Nextbook NX16A10132S/NXM1021CAP that is caught in a boot loop.
This is an Intel Atom based unit.
FTM mode is accessible (limited adb command support).
DNX mode is accessible (limited fastboot command support).
Based on the information in the build.prop file, it would appear to be an Android 6.0.1 system: ro.build.description=NXM1021CAP-user 6.0.1 MMB29M 20160919.050843 release-keys.
I cannot find any ROM, Update or image files for Android 6.
I would attempt re-flashing the unit to Android 5, but the image files linked to your post do not include the android_system or android_data partitions.
As I understand it, the android_data partition only holds user data and consequently does not need to be flashed, it only needs to be wiped, but the android_system partition is a must.
Do you know if stock Android 6 firmware is available anywhere?
If not, do you have a stock Android 5 image of the android_system partition?
Or, if I am completely off course, can you please advise?
Any help would be greatly appreciated.
Thanks in advance.
These tablets were sold with certain Vizio TVs in mid-2016 into 2017, primarily used for Smartcast to the TV.
They are now obsolete since Vizio released firmware for their TVs turning them into normal Smart TVs, requiring the owners of these TVs to get new remotes and the tablets stopped being useful for this function.
Here in 2019, one can buy these tablets, at the low price end, in working condition, for $25 (for the M series) to $40 (for the P series) shipped.
The specs are as follows:
XR6M10:
Snapdragon 410 1.2GHz quadcore APQ8016
2GB RAM
8GB Storage
1280x720 IPS display
802.11n, Bluetooth 4.0
2740mAh battery
MicroUSB for charging, Qi Charging built-in for bundled charge pad or any compatible charging solution
XR6P10:
Snapdragon 615 1.45GHz octocore APQ8039
2GB RAM
16GB Storage
1920x1080 IPS display
802.11n, Bluetooth 4.0
2740mAh battery
MicroUSB for charging, Qi Charging built-in for bundled charge pad or any compatible charging solution
Both tablets feature side-firing stereo speakers, a headphone jack, and NO cameras. The size of the tablet is comparable to the size of a Galaxy Note 9, give or take.
Both tablets came with Android 5.1.1, and OTA updates upgraded them to 6.0.1. There are ZERO available stock ROM files available for the tablets. I've tried sniffing the updater and they seem to go to a dead website.
The stock ROM is fairly clean, and only has the Vizio Smartcast app which needs disabling upon setting up. Aside from this, there is no other bloatware on the tablet to speak of after running a fine-tooth comb through the system apps. You get a clean and snappy tablet.
The problem:
There's no stock ROM file available, neither for Android 5.1.1 or for 6.0.1. Vizio does not have any sort of download for either on their site, nor did in the past. The updater checked a third-party website affiliated with Vizio to manage the tablet's updates, as it does with their TVs. Since the website is inert, it can be safely said that Vizio is no longer interested in their existence at all, especially since the warranty on every single one of these tablets is now up.
The tablet seems it can have the bootloader unlocked, the developer options has the toggle for that, but there's no way to get into fastboot. Holding VOL UP+DOWN+POWER at boot or sending the "adb reboot bootloader" command sends it into a "Qualcomm HS-USB QDLoader 9008" mode under USB. This, from what I understand, is behavior persistent with the locked bootloader, but I have no idea of how to get it out of this and just into fastboot. Stock recovery does not have a fastboot option either.
The desires list:
Have someone that knows the intricacies of the MSM8916 platform and the APQ8016/APQ8039 get their hands on these tablets
Get a ROM dump of both tablets in stock form so people with bricked tablets can flash them with it
Get Root (Patch level on the 6.0.1 stock ROM is from October 2016, shouldn't be hard)
Get the bootloader unlocked, somehow, and if not, figure a way to get something like Safestrap running on it if the out-of-the-box kernel allows for it
Custom ROMs? LineageOS would be sweet, especially with some of the tablet-specific fixes that have dropped in the past couple months overall.
so I ask: is there any interest in the freeing of these super cheap tablets? The price to spec ratio is not bad (once again, I got my 6M10 for $25 shipped, and the seller has like 7 more as of the time of this writing), and it doesn't seem like it would be all too hard to unlock the bootloader and get it rooted (at least, from my perspective, that of a novice in this specific hardware field). There are plenty of these in the wild in the hands of people that bought the TVs and plenty in the hands that bought them from ebay when the tablets became obsolete.
This link contains screenshots of CPU-Z and the About Tablet settings section from the tablet, uploaded to imgur. If anyone needs more information on this tablet that needs an app or adb command, I can make this happen.
Board Pic of the XR6M10, XR6P10 should be the same inside:
(click for larger image)
Update: I have temp root.
I have temp root!-the latest kingroot (NOT Kingoroot) APK seemed to have done the trick. I was able to fire up adaway and get the hosts file set up with adblocks to keep the thing safer.
The root is still temporary so it goes away after a reboot. The rooting process involves it doing the root process once, then rebooting, then failing, then you reboot once more, and then retry rooting from the app. From here, 80% of the time, it works and you're able to get temporary root for that boot session.
Once you're done with anything you need root for, you should reboot and then uninstall Kingroot, which you then need to deactivate the device administrator priveleges for, before it will allow you to cleanly uninstall it.
I also made a huge discovery that may turn out better for anyone that can help getting this thing properly rooted and the bootloader unlocked... it seems the file manager included in the stock ROM is v3.0.0 from Cyanogenmod 12.1.
This makes me think that the ROM creator either used that since it was opensource and readily available than come up with their own solution, or that this ROM has some cyanogenmod roots.
I also found this post from another Q&A thread in this section:
TheDrive said:
This device have made by Chinese/Indian company Borqs. The code name Bennu-M. Platform is Qualcomm APQ8016 (MSM8916 w/o modem). There should work standard method to bring EDL mode. Hold Vol+ and Vol- at power on (press power). Then connect to the PC. Thus device will stay look dead, however should be detected as Qualcomm QDLoader 9008 on the PC side. This is the factory described method.
You can flash factory firmware from this mode using external bootloader (programmer) for MSM8916 firehose protocol. This procedure is described in the thousands of manuals around the net. Qualcomm tools like QPST or QFIL can be used as good as many 3rd party utils to flash and manage any another available way. Many professional 'box' tools should support this device too but only as 'generic' msm8916 (if applicable).
However I can't find the firmware package for this device anywhere. You should ask and require the manufacturer/distributor to publish firmware, the source code and all the corresponding matherials to be able to flash and rebuild firmware from sources in any manner you want without any limitations as required by GNU/GPL free open source software licenses this firmware is obligated to.
Everyone who have the device working or software dead, can try to dump the current firmware and data, stored on the internal eMMC memory module in part(s) or in whole image using free QTools project utilities and suitable external bootloader with ability to dump eMMC, not only to flash as many factory supplied programmers do. There are programmer(s) for MSM8916 available in the project repo. Read and understand manuals carefully before trying anything!
There is definitely another ways to root, dump, flash, manage the device in any manner YOU WANT, not only the way you are "allowed" to use your own device by manufacturer/distributor. FTA!
You can root the device then dump all the multiple partition images manually (dd if=/dev/block/mmbblk0...... of=/sdcard/......) or using built custom recovery like CWM/TWRP for your device. Please note, kernel sources are important but not mandatory to build e.g. CWM. You can build one using CWM image from the similar device and the kernel (boot/recovery) image binaries from your device. There are good manuals and image repacking utils available around like e.g. AndImgTool.
There are the way to produce factory image from the eMMC/partitions dump(s). Use utils like R-Studio to dump particular partition images from the eMMC dump (it's like whole HDD or UFD image with all the sectors raw, one by one, w/o any modifications/compression/etc) Manuals / utils are avavailable to make e.g. sparse and xml scripts set which is flashable by the programmer in the EDL mode (i.e. from any damaged state, because EDL is built in to the PBL and masked to the internal CPU ROM, thus can not be damaged in any manner, except firing the CPU up).
You can also flash partition images from the more common Fastboot mode, unless eMMC GPT and bootloaders (SBL/RPM/TZ/ABoot) stay intact (logo showed). You can't dump from fastboot, which is common due to the (foolish) 'safety' requirements. It's security by obscurity and is definitely not for your favor, but for the corps control over you and force to send valuable private data to foreign clouds.
Please share eMMC full and/or partitions dumps using reliable 'neverending' file cloud/hosting since there is no factory firmware available yet (ever). I do not own this device and never seen being overseas, so I can't share.
Click to expand...
Click to collapse
This gives a little bit more information but seems to be more waffle than helpful. Still need someone, or some individuals, that can get one of these devices into their hands and work on a way to get the bootloader unlocked, the eMMC dumped, and ROMs going.
Update file?
I THINK I have the update file for 6.0.1. I did a packet sniff on a 5.1.1 tablet using a mitm packet sniffer and I ran the system updater, and was able to get this URL:
http://updatev.vo.llnwd.net/v1/idownload/64821.bin
The filesize is 570MB or so, and it looks like it might be the real deal. since it's a .bin file and 7zip can't read it, I won't be able to see what it really is without going over to the box that has a copy of universal extractor installed.
I'll be doing this momentarily and editing this post once I figure out what the contents are or if it's even readable to that extent. Knowing vizio, it could very well be encrypted and need decrypting by the updater application.
Update: it seems to be encrypted. oh joy.
Update 2: I got together with a friend on discord and we successfully decompiled the updater app to a point.
This MEGA link contains all the files thus far and a copy of the tablet's /system/framework folder for decompiling purposes.
However, it doesn't seem we're getting anywhere. the file is still encrypted and I still can't figure out what's needed to decrypt it. Hopefully someone with more knowledge on this can lend a hand.
Sudosftw said:
I THINK I have the update file for 6.0.1. I did a packet sniff on a 5.1.1 tablet using a mitm packet sniffer and I ran the system updater, and was able to get this URL:
http://updatev.vo.llnwd.net/v1/idownload/64821.bin
The filesize is 570MB or so, and it looks like it might be the real deal. since it's a .bin file and 7zip can't read it, I won't be able to see what it really is without going over to the box that has a copy of universal extractor installed.
I'll be doing this momentarily and editing this post once I figure out what the contents are or if it's even readable to that extent. Knowing vizio, it could very well be encrypted and need decrypting by the updater application.
Update: it seems to be encrypted. oh joy.
Update 2: I got together with a friend on discord and we successfully decompiled the updater app to a point.
This MEGA link contains all the files thus far and a copy of the tablet's /system/framework folder for decompiling purposes.
However, it doesn't seem we're getting anywhere. the file is still encrypted and I still can't figure out what's needed to decrypt it. Hopefully someone with more knowledge on this can lend a hand.
Click to expand...
Click to collapse
Just out of curiosity, with the temp root, have you tried using dd to get the recovery image off? If we can do that, we might be able to work on getting a custom recovery built.
Qiangong2 said:
Just out of curiosity, with the temp root, have you tried using dd to get the recovery image off? If we can do that, we might be able to work on getting a custom recovery built.
Click to expand...
Click to collapse
It's not possible to get a proper recovery image from within the system files so far as I know, but my take so far has been that there is no proper way to get that at this time without decrypting that file grabbed from the update server. I'd do it on a 5.x ROM since that will get me permaroot, but the issue is getting and keeping root on a 6.x ROM.
Although encrypted (so far as I can tell) the image linked above is the real deal, and I've given all I can to get it decrypted. A proper exploit to take care of this tablet's vulnerabilities and get temp root (on 6.x) that isn't kingo is what is really needed at this point so to not hinder going around the system with crudware and shady background apps, shouldn't be hard since the security patch level for the 6.x ROM is 2016-10-01.
Even if the ROM is extracted or a recovery image found, custom recovery won't be possible until the bootloader is unlocked, and this isn't doable until someone figures out how the qualcomm qdloader9008 stuff works with this specific tablet. Fastboot is unreachable and I'm almost sure I'm doing something wrong.
I'll get temp root and see about dd'ing stuff later on. What exactly would be needed for me to dd off? Whole disk and then go through it elsewhere? I could definitely see if rsync exists and dd over rsync to another box.
Sudosftw said:
It's not possible to get a proper recovery image from within the system files so far as I know, but my take so far has been that there is no proper way to get that at this time without decrypting that file grabbed from the update server. I'd do it on a 5.x ROM since that will get me permaroot, but the issue is getting and keeping root on a 6.x ROM.
Although encrypted (so far as I can tell) the image linked above is the real deal, and I've given all I can to get it decrypted. A proper exploit to take care of this tablet's vulnerabilities and get temp root (on 6.x) that isn't kingo is what is really needed at this point so to not hinder going around the system with crudware and shady background apps, shouldn't be hard since the security patch level for the 6.x ROM is 2016-10-01.
Even if the ROM is extracted or a recovery image found, custom recovery won't be possible until the bootloader is unlocked, and this isn't doable until someone figures out how the qualcomm qdloader9008 stuff works with this specific tablet. Fastboot is unreachable and I'm almost sure I'm doing something wrong.
I'll get temp root and see about dd'ing stuff later on. What exactly would be needed for me to dd off? Whole disk and then go through it elsewhere? I could definitely see if rsync exists and dd over rsync to another box.
Click to expand...
Click to collapse
I found this today: https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
The miflash tool seems promising (it works with nearly any device)
For the dd stuff, you can usually figure out the partitions easily with the fstab file in /. However, getting a raw dump is always useful.
Really, the big 3 would be the recovery.img, the boot.img, and the system.img. We can work from there
Qiangong2 said:
I found this today: https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
The miflash tool seems promising (it works with nearly any device)
For the dd stuff, you can usually figure out the partitions easily with the fstab file in /. However, getting a raw dump is always useful.
Really, the big 3 would be the recovery.img, the boot.img, and the system.img. We can work from there
Click to expand...
Click to collapse
I've had that installed whilst trying to figure the image out and the qdloader stuff, it doesn't do anything for this tablet sadly :/
Sudosftw said:
I've had that installed whilst trying to figure the image out and the qdloader stuff, it doesn't do anything for this tablet sadly :/
Click to expand...
Click to collapse
Hmmm. Which tablet do you have? The M or the P?
Qiangong2 said:
Hmmm. Which tablet do you have? The M or the P?
Click to expand...
Click to collapse
this is the M. the P was out of my price range ($40 shipped over $25 shipped) when I was looking at them, but now the Ms are going for around 25 bucks but 15 shipping from another seller, bringing the price up to 40 bucks where the P was. ended up buying the other Ms from the one seller and gave them out to family members because I was so impressed... but I really should have set some money aside for one of the Ps as well and didn't.
Sudosftw said:
this is the M. the P was out of my price range ($40 shipped over $25 shipped) when I was looking at them, but now the Ms are going for around 25 bucks but 15 shipping from another seller, bringing the price up to 40 bucks where the P was. ended up buying the other Ms from the one seller and gave them out to family members because I was so impressed... but I really should have set some money aside for one of the Ps as well and didn't.
Click to expand...
Click to collapse
Okay. You said miflash doesn't do anything, does the device show up in the application and not function? Or does it not show up at all?
Qiangong2 said:
Okay. You said miflash doesn't do anything, does the device show up in the application and not function? Or does it not show up at all?
Click to expand...
Click to collapse
just doesn't show up at all. and yet installing the qualcomm qdloader drivers says it's connected in device manager, so something's up. tried on two different boxes, different cables, no dice.
Sudosftw said:
just doesn't show up at all. and yet installing the qualcomm qdloader drivers says it's connected in device manager, so something's up. tried on two different boxes, different cables, no dice.
Click to expand...
Click to collapse
Hmmm. That's unusual. Are you running it in win 7 compatibility mode?
It would be nice to see community roms for these devices. I have the XR6P. If you need any info from this device, just tell me what to do.
I'm very interested in this as I have one of these tablets that I would like to use in my vehicle as a display for my piggyback ECU tuner. It doesn't currently support USB OTG, but I read that if I can gain root access I can add the file to give it USB Host functionality. Can anyone confirm this? I have tried several apps to get it rooted including Kingroot as you were able to get a temp root with that. Unfortunately Kingroot, as all the others I have tried, won't even install on the tablet. Again, I'm only looking to get this thing to be OTG capable. If anyone here has any suggestions, I would be very grateful! Thanks all!
I just bought an M remote to replace my broken P remote. My P remote had Android 6. My M remote has Android 5, and the OTA updater says there's no update. Any way to get Android 6 on this?
I have factory firmware for Bennu P and Bennu M , but take some time to upload the file.
ALANCHONG said:
I have factory firmware for Bennu P and Bennu M , but take some time to upload the file.
Click to expand...
Click to collapse
Hey. You can lay out the firmware for XR6M10
XR6M10 and XR6P10 firmware
konog said:
Hey. You can lay out the firmware for XR6M10
Click to expand...
Click to collapse
Mega Link: mega.nz/#F!n65kVYIT!PKH8A1WoD_Nc4DU_-9dbiQ
ALANCHONG said:
Mega Link: mega.nz/#F!n65kVYIT!PKH8A1WoD_Nc4DU_-9dbiQ
Click to expand...
Click to collapse
All the time, an error pops up at 12 seconds
Flash fail (-4002)
Log:
21:59:03.576 Arrival: \\?\USB#VID_05C6&PID_9008#5&13a74b18&0&11#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
21:59:03.591 Thread '_PortDownloadThread' started
21:59:04.610 Get Port ...
21:59:04.610 _GetDevicePortName (0): COM5
21:59:04.630 _ComPort: COM5
21:59:04.640 Get Port (0)
21:59:04.650 Flash ...
21:59:09.668 _Connect (0)
21:59:09.668 Downloading flash programmer: C:\_qcMUP\v8016-SIGNED-VIZIO-user-IMAGES\v8016-SIGNED-VIZIO-user-IMAGES\prog_emmc_firehose_8916.mbn
21:59:14.669 Failed to read the command from the opened port
21:59:14.669 _FlashProgrammer (-4002)
21:59:15.700 Flash (-4002)
21:59:15.700 Flash fail (-4002)
21:59:15.731 Download ended: -4002
21:59:15.763 Thread '_PortDownloadThread' ended
konog said:
All the time, an error pops up at 12 seconds
Flash fail (-4002)
Log:
21:59:03.576 Arrival: \\?\USB#VID_05C6&PID_9008#5&13a74b18&0&11#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
21:59:03.591 Thread '_PortDownloadThread' started
21:59:04.610 Get Port ...
21:59:04.610 _GetDevicePortName (0): COM5
21:59:04.630 _ComPort: COM5
21:59:04.640 Get Port (0)
21:59:04.650 Flash ...
21:59:09.668 _Connect (0)
21:59:09.668 Downloading flash programmer: C:\_qcMUP\v8016-SIGNED-VIZIO-user-IMAGES\v8016-SIGNED-VIZIO-user-IMAGES\prog_emmc_firehose_8916.mbn
21:59:14.669 Failed to read the command from the opened port
21:59:14.669 _FlashProgrammer (-4002)
21:59:15.700 Flash (-4002)
21:59:15.700 Flash fail (-4002)
21:59:15.731 Download ended: -4002
21:59:15.763 Thread '_PortDownloadThread' ended
Click to expand...
Click to collapse
Please check if the driver is installed