Alrighty... So I'm in the weeds here after going through three variants of the Samsung JPop (Which have bootloaders locked up like Fort Knox) and decided today to break down and dish out $59 for this bargain device. First thing I did upon getting it home was fastbooting it, and was able to unlock the bootloader with no issue. (So easy, a caveman could do it)
I've read just about every thread in here and though there seems to be TWRP support for quite a few models of the Onn tablets, I didn't see this one in here. Right now I have a throwaway laptop which is installing ubuntu for building TWRP for this device. Now, I have NEVER built TWRP. But I have plenty of free time, ambition, and am willing to learn. I have the basic guide to building TWRP open elsewhere. I will take whatever help I can get on doing this, big or small. Building a basic TWRP image should be easy enough, but the guides don't really go into device specific details (as expected), so this is where I could use some veteran help.
Device Specs:
Model: 100026191
Out-of-the-box Android Version: 11
Display: 7" 1024 x 600 Resolution
Processor: 2.0 GHz Quad-core CPU
RAM: 2GB
Cameras: 2MP front & back
USB: Type-C
Ubuntu just finished, and I am getting the build environment ready as we speak. Will keep this thread updated with progress and hickups that may occur along the way. Wish this noob some luck!!!!
Alrighty, so here's what I've been able to come up with as far as more detailed system information. Sorry for the late post, had trouble getting wifi working on ubuntu but got it going.
I suspected a MediaTek CPU and was eager to do a readback with SP Flash Tool, but as you can tell from the provided screenshots, it's actually a Cortex-A53 CPU. my goal here is to some how pull my stock recovery out of here. I thought about dd'ing it but someone in another thread advised against it. Does Onn have stock firmwares hidden away in the internet somewhere? Or is there another tool I can use to pull recovery?
Good evening guys and gals. New day, new opportunity. So i'm still stuck at pulling off boot and recovery from this tablet. I used
Code:
/adb shell cat /proc/mtd
to no avail. Permission denied just like with dd.
Today, I got the MTK droid tool and hooked the tablet to it and got these results. Still no scatter file, still no progress on pulling these partitions. (I apologize for my dumbness yesterday, this device is in fact MediaTek)
Alright. Eighty of you have clicked in this thread, zero of you show any motivation to do anything to contribute. You guys must hate this tablet because I went through this entire board, and each thread that even mentioned this model were left with no response. I just want the boot and recovery partitions off of the stock tablet. I am willing to do the rest. I said before, I'd take any help I could get but since this device is "so" insignificant, I'm not trying anything else on it.
I don't know if you guys dodge this device because it's Android 11, or what. But the least you veterans could do is either tell us it's not going to happen (given that you tried), or give us some other ideas we could try. Hell I'll paypal you enough for you to have the device in your hands in order to help. But that's where I stand. Moderator can lock this thread if he wishes. There's nothing else I can do for this device at the moment.
guess i'll return it to walmart
was hoping to root it easily with twrp
just gonna go grab the 8' if this is how it ended for the 7'
thanks for the help though!
I need a firmware for the 100026191
TWRPN00b said:
Alright. Eighty of you have clicked in this thread, zero of you show any motivation to do anything to contribute. You guys must hate this tablet because I went through this entire board, and each thread that even mentioned this model were left with no response. I just want the boot and recovery partitions off of the stock tablet. I am willing to do the rest. I said before, I'd take any help I could get but since this device is "so" insignificant, I'm not trying anything else on it.
I don't know if you guys dodge this device because it's Android 11, or what. But the least you veterans could do is either tell us it's not going to happen (given that you tried), or give us some other ideas we could try. Hell I'll paypal you enough for you to have the device in your hands in order to help. But that's where I stand. Moderator can lock this thread if he wishes. There's nothing else I can do for this device at the moment.
Click to expand...
Click to collapse
I have the boot and recovery images if you want them.
I unfortunately accidentally deleted the original boot image, but I have a magisk patched image still present.
I can walk you through the process of extracting the original if you would prefer that, it's quite simple, I just don't feel like buying a second Onn tablet at the moment.
Just note that if you want to extract the original boot image, do NOT flash the Magisk image, it will permanently erase the original boot image. There is another way, I can walk you through it.
PseudoDistant said:
I have the boot and recovery images if you want them.
I unfortunately accidentally deleted the original boot image, but I have a magisk patched image still present.
I can walk you through the process of extracting the original if you would prefer that, it's quite simple, I just don't feel like buying a second Onn tablet at the moment.
Click to expand...
Click to collapse
I oicked up one of the gen3 tablets. Do you think your way of pulling the boot image would work on it?
alarmdude9 said:
I oicked up one of the gen3 tablets. Do you think your way of pulling the boot image would work on it?
Click to expand...
Click to collapse
My way of pulling the images should work on any Android device that ships Android 8.0+, however if you got it brand new, don't update it.
Factory reset it if it downloaded an update, then disable OTA updates before enabling Wi-Fi.
You can run `adb logcat` while the update is downloading to find out where to download the OTA, and dump the boot partition from that.
From there, if you install Magisk, you can dump the recovery partition with `adb shell`.
PseudoDistant said:
Factory reset it if it downloaded an update, then disable OTA updates before enabling Wi-Fi.
You can run `adb logcat` while the update is downloading to find out where to download the OTA, and dump the boot partition from that.
From there, if you install Magisk, you can dump the recovery partition with `adb shell`.
Click to expand...
Click to collapse
Ok I will have to reset it then go from there. Do you have a guide on how to pull the image?
alarmdude9 said:
Ok I will have to reset it then go from there. Do you have a guide on how to pull the image?
Click to expand...
Click to collapse
When doing first time setup, don't connect to Wi-Fi.
Enable Developer Settings
Disable OTA Updates
Enable USB Debugging
Connect to Wi-Fi
Connect the device to your computer
Run `adb logcat > ota.txt`
Reenable OTA Updates
Go to Software Updates and start downloading the Android 12 update (If it's not the Android 12 update, disable OTA updates again after this one finishes installing, then try logcat again after rebooting)
Search for a link that looks like `https://android.googleapis.com/packages/ota-api/package/827ee737174e0e8f761bcaeb12738221a924c810.zip` in the logcat.
Put the update link in your browser, and download the zip file.
Extract the zip file
There's your boot.img, very conveniently.
The update link I have provided is for the 100074181, the 3rd gen Onn 7, if you happen to have that one then go ahead and just use my link.
Though update to Android 12 before actually using that boot.img with Magisk, it won't work with Android 11.
After you're done with that, and you're rooted.
`adb shell`
`su`
`dd if=/dev/block/by-name/recovery of=/storage/emulated/0/recovery.img`
Then connect your tablet to your PC and enable file transfer in USB settings, then just pull recovery.img out of your tablet and you have the recovery image.
PseudoDistant said:
When doing first time setup, don't connect to Wi-Fi.
Enable Developer Settings
Disable OTA Updates
Enable USB Debugging
Connect to Wi-Fi
Connect the device to your computer
Run `adb logcat > ota.txt`
Reenable OTA Updates
Go to Software Updates and start downloading the Android 12 update (If it's not the Android 12 update, disable OTA updates again after this one finishes installing, then try logcat again after rebooting)
Search for a link that looks like `https://android.googleapis.com/packages/ota-api/package/827ee737174e0e8f761bcaeb12738221a924c810.zip` in the logcat.
Put the update link in your browser, and download the zip file.
Extract the zip file
There's your boot.img, very conveniently.
The update link I have provided is for the 100074181, the 3rd gen Onn 7, if you happen to have that one then go ahead and just use my link.
Though update to Android 12 before actually using that boot.img with Magisk, it won't work with Android 11.
Click to expand...
Click to collapse
Awesome. Thank you so much I do appreciate it. Going to download the zip file because I have a 100071481. You sir are awesome!
alarmdude9 said:
Awesome. Thank you so much I do appreciate it. Going to download the zip file because I have a 100071481. You sir are awesome!
Click to expand...
Click to collapse
Update to Android 12 before using Magisk, just in case.
alarmdude9 said:
Awesome. Thank you so much I do appreciate it. Going to download the zip file because I have a 100071481. You sir are awesome!
Click to expand...
Click to collapse
Could you share the ota? This is the same model I'm using but its bricked rn
MoistSpoon said:
Could you share the ota? This is the same model I'm using but its bricked rn
Click to expand...
Click to collapse
I will look for it. Saved it to a USB drive and of course it decided to be stupid and it is repairing now. Slow going but as soon as it gets done I will look to see if it survived and if so I will get it uploaded.
MoistSpoon said:
Could you share the ota? This is the same model I'm using but its bricked rn
Click to expand...
Click to collapse
Sorry just noticed that the file that PseudoDistant posted is still good. I used this one....
https://forum.xda-developers.com/attachments/magisk_patched-25200_fvdeh-img.5794395/
Related
OK, just got the Fire today. The OS says 5.0.1 from Nov 17th, and says update is available, version 541112720. I block OTAVerifier only, thinking by blocking the verification I can intercept the update file in /cache. then I turn on airplane mode, play a bit and boot into TWRP via fastboot, install SuperSu. All is good.
Then I decide to see what the update is all about, and let it download. To my surprise, it starts installing. After the installation, I see FireOS 5.1.1 Now, I try to go into TWRP via fastboot, and it does not reboot and just hangs. A couple more tries - and still nothing.
I go back to stock recovery, and start sideloading update-kindle-37.5.2.2_user_522054520.bin . It sideloads OK, and upon reboot i get dark screen. Nothing works. This sounds very similar to the 4th gen issues where downgrades were bricking Fires :
http://forum.xda-developers.com/fire-hd/general/stop-upgrade-to-lollipop-via-twrp-t3216817
It'll be simple to install 5.1.1 via TWRP once the update file is captured, such that the older bootloaders can be kept.
But beware of the update - without TWRP there likely won't be root!
Dang, sucks about the brick! Hopefully getting TWRP to work again won't take a herculean effort. Right now I'm loving SlimLP but anyone getting one for xmas would likely get that Fire OS 5.1.1 pushed to them right away upon booting up and logging in and I would hate to see them stuck on that!
Damn!
What if an open wifi network is within range? Will the Fire OS ask before connecting?
My friend has a new fire in the box & has an open wifi network within range of their place.
The 5.1.1 update should find it's way to amazon's Software Updates page in time. It's not there yet. http://www.amazon.com/gp/help/customer/display.html?nodeId=201830180
blueberry.sky said:
What if an open wifi network is within range? Will the Fire OS ask before connecting?
My friend has a new fire in the box & has an open wifi network within range of their place.
Click to expand...
Click to collapse
afaik they don't ship with wifi on, and you have to agree to connect if wifi is detected.
Still, anyone who might want to root needs to keep wifi off until this is sorted--or until they're rooted and can rename DeviceSoftwareOTA.apk . And everyone on rooted stock should confirm /system/priv-app/DeviceSoftwareOTA/DeviceSoftwareOTA.apk is renamed to .apkOFF (or whatever), which should prevent a download. Don't know how the roms handle OTA.
I do believe that you should have to agree to connect to wifi. But I'd like to be 100% sure. Don't want to take the slightest chance.
I would appreciate confirmation from anyone with a brand new Fire & an open wifi network within range, that it will not auto-connect.
bibikalka said:
It'll be simple to install 5.1.1 via TWRP once the update file is captured, such that the older bootloaders can be kept.
But beware of the update - without TWRP there likely won't be root!
Click to expand...
Click to collapse
So, 5.1.1 can't boot TWRP and downgrading produces bricks. Lovely!
Wonder if there's any chance the CM recovery will boot?
I assume some of the "old-timers" here will capture the update soon enough. If not, I'm glad to give it a go.
tried the downgrade as well, same result. I think the reason we can't get back into recovery\fastboot is because the device is just endlessly rebooting (you can see in device manager). it wont let you power it off to try the volume down+power combo and just holding them does nothing. im going to let mine die overnight hopefully and maybe getting the volume down+power from off will let us back into recovery?
---------- Post added at 01:14 AM ---------- Previous post was at 12:46 AM ----------
DoLooper said:
So, 5.1.1 can't boot TWRP and downgrading produces bricks. Lovely!
Wonder if there's any chance the CM recovery will boot?
I assume some of the "old-timers" here will capture the update soon enough. If not, I'm glad to give it a go.
Click to expand...
Click to collapse
Well 5.0.1 is available on the Amazon website here: https://www.amazon.com/gp/help/customer/display.html?nodeId=201830180 so I contacted Amazon for the 5.1.1 file and this was what I got:
Jyothirmayi: In this case, I'll personally follow up your contact and email you the link for the update because we currently don't have the manual link for the update in our website.
I will post here if\when I hear back
dmesg on linux machine when plug usb, open mediatek preloader com port.
Have this on bricked fire ?
usb 1-2.4: Product: MT65xx Preloader
usb 1-2.4: Manufacturer: MediaTek
cdc_acm 1-2.4:1.1: ttyACM0: USB ACM device
adb
usb 1-2.4: New USB device found, idVendor=1949, idProduct=0222
usb 1-2.4: New USB device strings: Mfr=2, Product=3, SerialNumber=4
usb 1-2.4: Product: Fire
usb 1-2.4: Manufacturer: Amazon
usb 1-2.4: SerialNumber: xxxxxxxxxxxxxxxxxxx
fastboot
usb 1-2.4: New USB device found, idVendor=0bb4, idProduct=0c01
usb 1-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-2.4: Product: Android
usb 1-2.4: Manufacturer: MediaTek
usb 1-2.4: SerialNumber: xxxxxxxxxxxxxx
If you have TWRP, why didn't you just use the file manager to copy and paste the OTA from your /cache to your sd card? If you can boot to TWRP, see if it's still there.
You can also dump your cache via adb shell from within TWRP and get the OTA by extracting the cache.img that dumps. There are several ways, as long as TWRP and fastboot are still booting.
Also, you can use adb shell within twrp to dd a system.img dumped from another fire tab, and restore your device that way if all else fails.
hp420 said:
If you have TWRP, why didn't you just use the file manager to copy and paste the OTA from your /cache to your sd card? If you can boot to TWRP, see if it's still there.
You can also dump your cache via adb shell from within TWRP and get the OTA by extracting the cache.img that dumps. There are several ways, as long as TWRP and fastboot are still booting.
Also, you can use adb shell within twrp to dd a system.img dumped from another fire tab, and restore your device that way if all else fails.
Click to expand...
Click to collapse
I think in the OP, he mentioned that he is no longer able to get into TWRP after 5.1.1 update...
So I bricked my device last night trying to downgrade before anyone had posted about it. Oops.
I did some Googling and theoretically these tools here should help us unbrick, but I believe we don't have the Amazon firmware in the right format.
HOWEVER, this tool, if I understand it right, should be able to pull the firmware from a working device in the right format for us to try flashing to a bricked device. Anyone want to give it a shot?
87racer said:
Jyothirmayi: In this case, I'll personally follow up your contact and email you the link for the update because we currently don't have the manual link for the update in our website.
I will post here if/when I hear back
Click to expand...
Click to collapse
mmoogle said:
So I bricked my device last night trying to downgrade before anyone had posted about it. Oops.
I did some Googling and theoretically these tools here should help us unbrick, but I believe we don't have the Amazon firmware in the right format.
HOWEVER, this tool, if I understand it right, should be able to pull the firmware from a working device in the right format for us to try flashing to a bricked device. Anyone want to give it a shot?
Click to expand...
Click to collapse
When we get the official file from Amazon, we can format it to the way the MTK Droid Tool wants it, and then that would theoretically work.
mmoogle said:
So I bricked my device last night trying to downgrade before anyone had posted about it. Oops.
I did some Googling and theoretically these tools here should help us unbrick, but I believe we don't have the Amazon firmware in the right format.
HOWEVER, this tool, if I understand it right, should be able to pull the firmware from a working device in the right format for us to try flashing to a bricked device. Anyone want to give it a shot?
Click to expand...
Click to collapse
Vlasp said:
When we get the official file from Amazon, we can format it to the way the MTK Droid Tool wants it, and then that would theoretically work.
Click to expand...
Click to collapse
Well, I've been there before with the 4th gen Fire HD :
http://forum.xda-developers.com/fire-hd/help/mtk-tools-people-hopeless-bricks-t3139784
In a nutshell, MTK Droid tools don't even talk to the working Fire properly, so it's unlikely they'd help with a bricked one ...
87racer said:
tried the downgrade as well, same result. I think the reason we can't get back into recovery\fastboot is because the device is just endlessly rebooting (you can see in device manager). it wont let you power it off to try the volume down+power combo and just holding them does nothing. im going to let mine die overnight hopefully and maybe getting the volume down+power from off will let us back into recovery?
Click to expand...
Click to collapse
Just pull your battery. The back cover is very easy to get off. Use a knife just to widen the seam so you can get your fingernail in at the corner. Keep one fingernail at the corner & side a 2nd nail down along the edge.
Then the battery connector lifts out upwards.
http://forum.xda-developers.com/ama...o-photo-amazon-fire-2015-motherboard-t3227808
bibikalka said:
Well, I've been there before with the 4th gen Fire HD :
http://forum.xda-developers.com/fire-hd/help/mtk-tools-people-hopeless-bricks-t3139784
In a nutshell, MTK Droid tools don't even talk to the working Fire properly, so it's unlikely they'd help with a bricked one ...
Click to expand...
Click to collapse
We might be in luck. I happen to have 3 of them One bricked, one mostly untouched on 5.1.1 and another with OTA blocked on 5.0.1. I will fiddle with the tools you posted and see if I can come up with something.
blueberry.sky said:
Just pull your battery. The back cover is very easy to get off. Use a knife just to widen the seam so you can get your fingernail in at the corner. Keep one fingernail at the corner & side a 2nd nail down along the edge.
Then the battery connector lifts out upwards.
http://forum.xda-developers.com/ama...o-photo-amazon-fire-2015-motherboard-t3227808
Click to expand...
Click to collapse
Good to know, even over night, it still isn't dead so I might give this a shot.
So, if i previously installed the google framework and blocked ota like most people did, this won't block the ota really ?
87racer said:
We might be in luck. I happen to have 3 of them One bricked, one mostly untouched on 5.1.1 and another with OTA blocked on 5.0.1. I will fiddle with the tools you posted and see if I can come up with something.
Click to expand...
Click to collapse
The best deal is of course to capture the 5.1.1 update file. I am eager to try it, provided I get root with requires installing via TWRP.
bibikalka said:
Well, I've been there before with the 4th gen Fire HD :
http://forum.xda-developers.com/fire-hd/help/mtk-tools-people-hopeless-bricks-t3139784
In a nutshell, MTK Droid tools don't even talk to the working Fire properly, so it's unlikely they'd help with a bricked one ...
Click to expand...
Click to collapse
So MTK tools does talk but from what I gather it is looking for /proc/dumchar_info which contains the partition structure. This is used to create the scatter file that would allow us to push the firmware back. This file is non-existent. I tried to find some alternate way to build a scatter file but am coming up short and without it we can't really do anything using SP Flash...
Also tried looking into /proc/mtd for info but that file is basically blank. Not sure if Amazon is storing the partition information somewhere else or maybe its hard coded into a chip?
If anybody has any ideas, I have the working devices and can try pulling stuff but I am stumped atm
---------- Post added at 12:28 PM ---------- Previous post was at 12:24 PM ----------
bibikalka said:
The best deal is of course to capture the 5.1.1 update file. I am eager to try it, provided I get root with requires installing via TWRP.
Click to expand...
Click to collapse
We were replying at the same time. I don't think a 5.1.1 file is going to help us on the bricked devices. Once bricked, the preloader seems to just endlessly loop so we would have no way to get the firmware on the device without using something like SP Flash and a scatter file (which eludes me atm)
Theoretically if we have the scatter file I think we should be able to use our 5.0.1 file and restore, then upgrade to 5.1.1 (or stay for root and fastboot boot support)
nEUTRon666 said:
So, if i previously installed the google framework and blocked ota like most people did, this won't block the ota really ?
Click to expand...
Click to collapse
What makes you say that? No one who did that has reported it updating.
I been looking around and havent found anything on how to root my device. Is there any info on how to root my device? Its upgraded to Android Marshmallow
bump
I've been looking for over a year
I've been looking for an answer to that question for over a year now. From what I've found it can't be done once you upgrade to marshmallow. If you downgrade to Android 5 you can though. There's instructions on how to do both on this site. I had rooted before upgrading to to marshmallow if you search "root Asus z580c" on here you will find the instructions easily but it only works on nugat. This is something that's been driving me crazy for months now and every once in a while I do a search to see if someone has found a way to do it...that's how I came across this post actually...but no luck. I've considered going back to android 5 plenty of times but for me there not that many apps I use that I need it rooted for anymore anyway. The biggest one is adblock but if you search for an app called DNS66 its an ad blocker that works really well and doesn't require root. its not just an ad blocking browser its an actual app. Good luck.
This pisses me off on a cellular level. This is such a good tablet, spec-wise. But Asus dumped updates after a year, and it seems like no one is interested in trying to crack it open. Which is a shame, because debloated, this thing would run so well. The screen is fantastic, the size is great. But all the Asus bloat on it infuriates me. I hate ZenUI, and while you can use a different launcher, it doesn't remove it all-together (for instance, the pull down menu stays as it is). If anyone is trying to do work on this front and needs a tester, I'll happily lend a hand. I'm nowhere near skilled enough to DIY, but I can certainly follow instructions and get you logs and crap.
TheQuicksilver said:
This pisses me off on a cellular level. This is such a good tablet, spec-wise. But Asus dumped updates after a year, and it seems like no one is interested in trying to crack it open. Which is a shame, because debloated, this thing would run so well. The screen is fantastic, the size is great. But all the Asus bloat on it infuriates me. I hate ZenUI, and while you can use a different launcher, it doesn't remove it all-together (for instance, the pull down menu stays as it is). If anyone is trying to do work on this front and needs a tester, I'll happily lend a hand. I'm nowhere near skilled enough to DIY, but I can certainly follow instructions and get you logs and crap.
Click to expand...
Click to collapse
Thanks to shakalaca
original post:
https://medium.com/@shakalaca/zenpad-s-8-0-z580ca-bootloader-unlocked-d878335365ab
download the file here and unzip freemyzenpad.7z
https://mega.nz/#F!F1FlzAoY!u6zR1Y14xvqoSbz-YQGFrw
enable usb debug mode, connect your usb cable to Z580
run root.bat
follow the steps , after it's done, install magisk manager, voila, rooted!
Anyone tried this method?
sniperx1211 said:
Thanks to shakalaca
original post:
https://medium.com/@shakalaca/zenpad-s-8-0-z580ca-bootloader-unlocked-d878335365ab
download the file here and unzip freemyzenpad.7z
https://mega.nz/#F!F1FlzAoY!u6zR1Y14xvqoSbz-YQGFrw
enable usb debug mode, connect your usb cable to Z580
run root.bat
follow the steps , after it's done, install magisk manager, voila, rooted!
Click to expand...
Click to collapse
Anyone tried this method?
Thanks.
tcbys said:
I been looking around and havent found anything on how to root my device. Is there any info on how to root my device? Its upgraded to Android Marshmallow
Click to expand...
Click to collapse
I'm struggling to find an update to Marshmallow for Zenpad 8.0 P022 380C. You say you've updated...do you still have the zip file with the code please? I'll make sure to root the tablet before I upgrade after reading this thread...
Bruno Rodrigues said:
Anyone tried this method?
Thanks.
Click to expand...
Click to collapse
I tried it from a Linux laptop as I couldn't get Win10 to recognise the tablet at all...
I changed the script to point at local adb/fastboot rather than the ".mac" executables, so it should perform exactly the same actions - and all seemed OK to begin with - but one of the reboots after a flash stage never returned to a screen... and now it refuses to even start up.
Whether it was something I did, or the script, I cannot say...
is it possible to flash the stock rom via fastboot ?. I have twrp installed, but it gives me error 7 when I try to flash the stock ROM.zip. And the tablet doesn't turn me on either, it stays on the asus logo. thanks
sniperx1211 said:
Thanks to shakalaca
original post:
https://medium.com/@shakalaca/zenpad-s-8-0-z580ca-bootloader-unlocked-d878335365ab
download the file here and unzip freemyzenpad.7z
https://mega.nz/#F!F1FlzAoY!u6zR1Y14xvqoSbz-YQGFrw
enable usb debug mode, connect your usb cable to Z580
run root.bat
follow the steps , after it's done, install magisk manager, voila, rooted!
Click to expand...
Click to collapse
do you know how to use the files in the unbrick folder? thanks
Im attempting to get info or at least start a thread on the possibility of ROOTING the (Walmart) ONN Surf 100005208 10.1"
It's a rebranding of the ONA19TB003. Same hardware, new name.
jordianz said:
Im attempting to get info or at least start a thread on the possibility of ROOTING the (Walmart) ONN Surf 100005208 10.1"
Click to expand...
Click to collapse
As @razredge stated, the Onn Surf 10.1 is merely a rebranding of its predecessor tablet. The Surf 10.1 can be rooted with or without TWRP. Follow the guides on rooting the previous Onn 10.1. Everything works exactly the same. TWRP is fully compatible as well.
can you share your stock firmware with me
no
the thing was a brick when i attempted the mod its a MT8768WA chipset not MT8163
Viva La Android said:
As @razredge stated, the Onn Surf 10.1 is merely a rebranding of its predecessor tablet. The Surf 10.1 can be rooted with or without TWRP. Follow the guides on rooting the previous Onn 10.1. Everything works exactly the same. TWRP is fully compatible as well.
Click to expand...
Click to collapse
KaosKreationz said:
the thing was a brick when i attempted the mod its a MT8768WA chipset not MT8163
Click to expand...
Click to collapse
Regardless of chipset platforms, both Onn 10.1" tablet variants can be rooted using the same TWRP and the same root method, and without TWRP by fastboot flashing a Magisk patched boot image.
Viva La Android said:
Regardless of chipset platforms, both Onn 10.1" tablet variants can be rooted using the same TWRP and the same root method, and without TWRP by fastboot flashing a Magisk patched boot image.
Click to expand...
Click to collapse
I keep reading it can’t and I do not want to brick this tablet so tell me exactly how to root it it’s the android 10 preloaded version.
---------- Post added at 08:37 PM ---------- Previous post was at 08:34 PM ----------
KaosKreationz said:
I keep reading it can’t and I do not want to brick this tablet so tell me exactly how to root it it’s the android 10 preloaded version.
Click to expand...
Click to collapse
Also how does one patch the image with magisk if the magisk software does not work on said tablet?
As well as how does one dump the images when so flash nor mt software doesn’t recognize the image.
KaosKreationz said:
I keep reading it can’t and I do not want to brick this tablet so tell me exactly how to root it it’s the android 10 preloaded version.
---------- Post added at 08:37 PM ---------- Previous post was at 08:34 PM ----------
Also how does one patch the image with magisk if the magisk software does not work on said tablet?
As well as how does one dump the images when so flash nor mt software doesn’t recognize the image.
Click to expand...
Click to collapse
Well, you just taught me something I wasn't aware of. I have not yet seen the Onn 10.1" variant with preloaded Android 10. My variant (Onn Surf 10.1, Model No. 100005208) came with Android 9 Pie. And I was able to root it using the TWRP build from my tablet's predecessor, which had the same chipset and also rah on Android 9 Pie. You seem to be referring to an entirely new variant that ships with Android 10. What is your exact model number and your current firmware build number? I'll see what I can find out.
Viva La Android said:
Well, you just taught me something I wasn't aware of. I have not yet seen the Onn 10.1" variant with preloaded Android 10. My variant (Onn Surf 10.1, Model No. 100005208) came with Android 9 Pie. And I was able to root it using the TWRP build from my tablet's predecessor, which had the same chipset and also rah on Android 9 Pie. You seem to be referring to an entirely new variant that ships with Android 10. What is your exact model number and your current firmware build number? I'll see what I can find out.
Click to expand...
Click to collapse
It just got a silent OTA update which I was trying to find in the saved directory but it went right to it and installed before i had a chance to pull it. ****ing thing has been a pain since i got it. trying to root and remove bloat bc its a decent setup and could run pretty fast if it were a clean android OS.
To answer your question it is the ONN 10003562 with MT8768WA Chipset ill update with the firmware one i fix the damn thing it bricked on me again while removing bloatware. this thing has some kinda tamper check or something. i get it starting to run really nice without root and then on reboot its a brick.
KaosKreationz said:
It just got a silent OTA update which I was trying to find in the saved directory but it went right to it and installed before i had a chance to pull it. ****ing thing has been a pain since i got it. trying to root and remove bloat bc its a decent setup and could run pretty fast if it were a clean android OS.
To answer your question it is the ONN 10003562 with MT8768WA Chipset ill update with the firmware one i fix the damn thing it bricked on me again while removing bloatware. this thing has some kinda tamper check or something. i get it starting to run really nice without root and then on reboot its a brick.
Click to expand...
Click to collapse
So you have yet another variant of the Onn 10.1" tablet. That's good to know. My 100005208 was merely a rebranding of its predecessor but it appears now that Onn has released yet another variant. Yeah, hold off on trying to root right now. Anything released with Android 10 out of the box uses the system-as-root (SAR) implementation. While Magisk does support SAR, the rooting process has changed up some. I'll see what I can dig up for you.
Viva La Android said:
So you have yet another variant of the Onn 10.1" tablet. That's good to know. My 100005208 was merely a rebranding of its predecessor but it appears now that Onn has released yet another variant. Yeah, hold off on trying to root right now. Anything released with Android 10 out of the box uses the system-as-root (SAR) implementation. While Magisk does support SAR, the rooting process has changed up some. I'll see what I can dig up for you.
Click to expand...
Click to collapse
ok thanks. the only thing I am able to really do is remove some bloatware. but even then it still runs like ****. I found some OTA's in one of the threads here and also its supposedly a stock from the box backup but the scatter doesnt match the chipset. I was hoping someone could inform me if there is a way to get an android ten backup of the older device and swap out keys or whatever the thing is checking for when it boots and flash it.
very limited with no real su so stuff wont work right when I delete certain bloatware. Also if anyone can inform as to how I can even pull my firmware and recover.img and boot.img etc. I have tried MTK device or whatever that software is as well as sp flashtool and nothing seems to read the device rom. can see the device but cant pull. its been so long since ive used or attempted to root an android device im out of practice.
KaosKreationz said:
ok thanks. the only thing I am able to really do is remove some bloatware. but even then it still runs like ****. I found some OTA's in one of the threads here and also its supposedly a stock from the box backup but the scatter doesnt match the chipset. I was hoping someone could inform me if there is a way to get an android ten backup of the older device and swap out keys or whatever the thing is checking for when it boots and flash it.
very limited with no real su so stuff wont work right when I delete certain bloatware. Also if anyone can inform as to how I can even pull my firmware and recover.img and boot.img etc. I have tried MTK device or whatever that software is as well as sp flashtool and nothing seems to read the device rom. can see the device but cant pull. its been so long since ive used or attempted to root an android device im out of practice.
Click to expand...
Click to collapse
Earlier, you mentioned a "silent OTA." Could you elaborate on that? Did the OTA install seamlessly, without rebooting to recovery? I'm wondering if your variant has A/B partitions.
Viva La Android said:
Earlier, you mentioned a "silent OTA." Could you elaborate on that? Did the OTA install seamlessly, without rebooting to recovery? I'm wondering if your variant has A/B partitions.
Click to expand...
Click to collapse
When I said silently I meant I was sitting at the computer with the tablet hooked up in adb mode and i walked away for maybe 3 minutes to relieve myself and upon returning the tablet was rebooting and installing an update. I swear I had the automatic updates in dev mode turned to off.
Here is what I gather from the device.
KaosKreationz said:
When I said silently I meant I was sitting at the computer with the tablet hooked up in adb mode and i walked away for maybe 3 minutes to relieve myself and upon returning the tablet was rebooting and installing an update. I swear I had the automatic updates in dev mode turned to off.
Here is what I gather from the device.
Click to expand...
Click to collapse
Thanks for the stats. Yeah it looks like you're fully Treble supported but non-A/B. Ok just to make sure I'm not missing something, sort of give me a simple outline on everything you've done from start until now. Did you mention your device was a brick when you got it, or did you brick it initially attempting to root? How did you recover from the brick? I'm assuming SP Flash Tool and I recall you mentioned something about a mismatched scatter file. I believe I have a root solution for you but I want to make sure I have my info correct. Thanks for helping me to help you. You seem to know your Android well.
It was a soft brick via adb removal of bloat ware it was able to be restored from factory settings..
I think I may almost have it but i'm to afraid of flashing the boot.img bc I did brick the first one I had via sp flash. The firmware someone added in this thread a bit back says 100003562 but the chipset is MT6765 not the MT8768WA. I was able to mod that boot.img with magisk but as I stated I'm to afraid to flash it I tried the fastboot boot magiskpatched.img command it seemed to read with no errors but it shutdown and then rebooted. soo im afraid it may cause a loop. Im trying now to figure out a way to remove the dm verity check but have had no success as of yet. if i could just pull my own roms Im sure I could get this to root with magisk maybe.
link to larger files https://drive.google.com/drive/folders/1-j0wj9d0FuLxvHdvW8CjYICp3-xV00cs?usp=sharing
I cant seem to get SP Flash to read the device scatter properly Im unable to pull roms with readback I think i have to set it up manually?
I have attached the screenshots, rom, magisk image created as well as the bug report from soft brick.
It would Be soo much easier if i could get the DM verity off and or pull my roms.
KaosKreationz said:
It would Be soo much easier if i could get the DM verity off and or pull my roms.
Click to expand...
Click to collapse
Ok as you probably know, your device has SAR (system-as-root) implementation, because it shipped with Android 10. It appears that you will need to install Magisk to recovery ramdisk, because your boot image contains no ramdisk. Magisk does support this, as you probably know. Go to this link and look under the heading "Magisk in Recovery"
https://topjohnwu.github.io/Magisk/install.html#magisk-in-recovery
My Moto G7 Play is SAR as well, and has no boot image ramdisk, so I have it rooted with Magisk installed to recovery. It's different indeed, but as of now, it's the only root solution for SAR devices with recovery ramdisk implementations like yours and mine. Magisk will actually "live" within the recovery partition and actually becomes hijacked by Magisk. As you will read in the link I sent, it is still possible to use recovery mode. You will need to get a stock recovery image from somebody with your variant who has pulled the image, or from a stock firmware package. In sum, you will be patching your recovery image, not your boot image. Accordingly, you will be flashing your /recovery partition to achieve root, not your /boot partition. As you know, as long as you are bootloader unlocked, you can flash the patched recovery image using fastboot. You will not need a TWRP for root. In the link I sent, also look for the previous heading "Patching Images." To test and make sure I'm 100% right on this, install the latest Magisk Manager app on your device and open the app. Look in the "Ramdisk" section. If it says NO, then I'm right and you must install Magisk to recovery as I've stated. If it says YES I'm wrong and you need to disregard this entire post.
But please let me know the status on things, and if you manage to get Magisk systemless root installed properly.
Anyone have a 100003562 boot.img or recovery.img for the MT8678WA
---------- Post added at 06:52 PM ---------- Previous post was at 06:45 PM ----------
I tried the recommended and it bricked I'm only able to use and now when the device boots it hangs at the logo screen or does anyone know Walmarts update software command.
I know I’m a newb here but I wanted to make a thread dedicated to theses devices in which I I have detailed instructions for rooting as well as CFW’s and unbricking!
I appreciate any donations sent via PayPal email for PayPal is on my profile.
Onn 100003562 Root instructions:
****UPDATE*****
With the newly uploaded rom all you have to do is download use sp flash to install .
May still have to run " fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img " command in fastboot mode.
Step 1: Downloads
Download Magisk manager and update.
Download ADB & FASTBOOT.
Below I'll have a link for windows. for linux run command "sudo apt install adb".
Dwnload boot.img and vbmeta.img.
Download SP Flash Tools and wwrMTK <---Will make this much faster XD.
I have all of these available
here--> https://drive.google.com/drive/folders/1lREGI_nd7kghuR6vCDjhiOZvbWrpJfBo?usp=sharing <--here.
Step 2:
Install magisk manager and update.
You can either download on the tablet or sideload with adb.
For sideload in windows shift + right click in the platform tools directory and click open power shell here.
Make sure you have MagiskManager-v8.0.0[1].apk saved within this directory.
Then run command "adb install MagiskManager-v8.0.0[1].apk"
For linux Right click the directory in which you have MagiskManager-v8.0.0[1].apk stored and click open terminal here.
Then run command "adb install MagiskManager-v8.0.0[1].apk"
Step 3:
Either make a backup with SP Flash tools or use the boot.img i have provided and copy it to your tablet.
Open magisk on the tablet and click the install then click select image to patch. Locate the boot.img and select it by clicking on it. Watch it finish make sure it fully completes the patch and creates the magisk-patched.img file. Also it may or may not be necessary to patch the recovery.img depending on your system. most likely not.
Step 4:
Flashing the .img files.
Now that you have adb and the images necessary to flash your device power it down and back up holding the volume up key. Once It boots it should load into the bootloader screen click the up key until you have fastboot selected and then click the down key.
Now that you are in fast boot mode you are going to navigate to adb fastboot directory and right click and select open powershell here. again make sure you have all necessary .img files stored in the adb fastboot directory. you should have the patched .img and the vbmeta.img stored in the directory for windows.
Run these commands:
fastboot flashing unlock
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase cache
fastboot flash boot magisk_patched.img
fastboot reboot
Wait for it to reboot and then you will be rooted with magisk. enjoy.
I'm always grateful for donations paypal email for donations is on my profile.
Thanks for everyone's work for these tablets. I have both the new 7" and 10.1". Does anyone know how to edit the lk.bin file to remove that ugly Orange State warning after unlocking the bootloader?
This is a post that works great for the 7".
Onn Surf 7" gen 2 on sale for 28$ today. Bought one... Was able to unlock bootloader
Onn Surf 7" gen 2 on sale for 28$ today. Bought one... Was able to unlock bootloader So, stopped at walmart this morning for stuff and saw the Onn Surf is now on Gen 2. 2.0 GHz quad core, 16gb storage and 2 gb ram. Seemed pretty decent for...
forum.xda-developers.com
I just want to see if the same thing can be done with the 10.1"? If the files are identical great, but I don't want to risk needing to restore my tablet by just trying it blind. Not yet anyway.
PleaseBeNicetoMe said:
Thanks for everyone's work for these tablets. I have both the new 7" and 10.1". Does anyone know how to edit the lk.bin file to remove that ugly Orange State warning after unlocking the bootloader?
This is a post that works great for the 7".
Onn Surf 7" gen 2 on sale for 28$ today. Bought one... Was able to unlock bootloader
Onn Surf 7" gen 2 on sale for 28$ today. Bought one... Was able to unlock bootloader So, stopped at walmart this morning for stuff and saw the Onn Surf is now on Gen 2. 2.0 GHz quad core, 16gb storage and 2 gb ram. Seemed pretty decent for...
forum.xda-developers.com
I just want to see if the same thing can be done with the 10.1"? If the files are identical great, but I don't want to risk needing to restore my tablet by just trying it blind. Not yet anyway.
Click to expand...
Click to collapse
That thread has a modified lk.bin file to remove the orange state warning. It has worked great on both of my Gen 2 7 inch tablets
Okiera29 said:
That thread has a modified lk.bin file to remove the orange state warning. It has worked great on both of my Gen 2 7 inch tablets
Click to expand...
Click to collapse
I'm looking to do the same on my 10", do you think they're interchangeable?
Yes onm
Abelbody said:
Yes onm
Click to expand...
Click to collapse
Something must be lost in translation. I'm looking for a patched lk.bin for the 10.1", not the 7".
If anyone is interested, the 7" version is not compatible with the 10.1" version. Luckily SP Flash restored it.
PleaseBeNicetoMe said:
Something must be lost in translation. I'm looking for a patched lk.bin for the 10.1", not the 7".
If anyone is interested, the 7" version is not compatible with the 10.1" version. Luckily SP Flash restored it.
Click to expand...
Click to collapse
Sorry about that. It appears that Fred patched your lk.bin file for you on the other thread today
Okiera29 said:
Sorry about that. It appears that Fred patched your lk.bin file for you on the other thread today
Click to expand...
Click to collapse
Yes it worked too if anyone has the same question
Help! I followed the instructions in the OP, and everything worked fine. I then used ADB to uninstall some of the preinstalled apps, but I think I uninstalled something I shouldn't have. i'm getting crashes from mutltiple apps (Bluetooth, Contacts, etc).
I've downloaded the stock firmware/full in the linked GDrive share; how can I restore back to this stock firmware? I'm pretty new/noob with this, but I am familiar with Linux commands. (familiar enough to be dangerous...)
hightowerc said:
I've downloaded the stock firmware/full in the linked GDrive share; how can I restore back to this stock firmware? I'm pretty new/noob with this, but I am familiar with Linux commands. (familiar enough to be dangerous...)
Click to expand...
Click to collapse
I believe that you need to download SP Flash tools if you haven't already. You can then, using the provided scatter file and the downloaded firmware, just reflash the stock firmware to the tablet. You will of course, have to re-root the tablet after it finishes
PleaseBeNicetoMe said:
Thanks for everyone's work for these tablets. I have both the new 7" and 10.1". Does anyone know how to edit the lk.bin file to remove that ugly Orange State warning after unlocking the bootloader?
This is a post that works great for the 7".
Onn Surf 7" gen 2 on sale for 28$ today. Bought one... Was able to unlock bootloader
Onn Surf 7" gen 2 on sale for 28$ today. Bought one... Was able to unlock bootloader So, stopped at walmart this morning for stuff and saw the Onn Surf is now on Gen 2. 2.0 GHz quad core, 16gb storage and 2 gb ram. Seemed pretty decent for...
forum.xda-developers.com
I just want to see if the same thing can be done with the 10.1"? If the files are identical great, but I don't want to risk needing to restore my tablet by just trying it blind. Not yet anyway.
Click to expand...
Click to collapse
I’ll look into it sorry I’ve been having some issues lately and haven’t gotten much done on this thread. I was hoping to make an all in one spot for the newer android 10 models. I’ll get the 7 model info and stocks here soon. Is there already a working orange state mod already? If so can you link it and I’ll get into messing with it.
also these Mtk devicesseem to be difficult to get the source for. I’ve contacted mtk multiple times now and still have not gotten a response. I have however been digging through the hidden settings of thesedevices and it seems if they were to release their source they and Walmart may get into a huge amount of trouble as well as lawsuits filed against them. I’m finding these tablets have a sim installed somewhere and are uploading and downloading data via hidden software I’ve disabled the Verizon network locks and the data services in my device I just haven’t been able to really get into it to see what data is being transfer but I have also found some kinda remote camera and sound recorder software also hidden on the device.
KaosKreationz said:
I’ll look into it sorry I’ve been having some issues lately and haven’t gotten much done on this thread. I was hoping to make an all in one spot for the newer android 10 models. I’ll get the 7 model info and stocks here soon. Is there already a working orange state mod already? If so can you link it and I’ll get into messing with it.
also these Mtk devicesseem to be difficult to get the source for. I’ve contacted mtk multiple times now and still have not gotten a response. I have however been digging through the hidden settings of thesedevices and it seems if they were to release their source they and Walmart may get into a huge amount of trouble as well as lawsuits filed against them. I’m finding these tablets have a sim installed somewhere and are uploading and downloading data via hidden software I’ve disabled the Verizon network locks and the data services in my device I just haven’t been able to really get into it to see what data is being transfer but I have also found some kinda remote camera and sound recorder software also hidden on the device.
Click to expand...
Click to collapse
Don't know about your data transfer theory but there's the post with the 10.1" Pro lk.img edit to remove the Orange State warning.
Onn Surf 7" gen 2 on sale for 28$ today. Bought one... Was able to unlock bootloader
Onn Surf 7" gen 2 on sale for 28$ today. Bought one... Was able to unlock bootloader So, stopped at walmart this morning for stuff and saw the Onn Surf is now on Gen 2. 2.0 GHz quad core, 16gb storage and 2 gb ram. Seemed pretty decent for...
forum.xda-developers.com
PleaseBeNicetoMe said:
Don't know about your data transfer theory but there's the post with the 10.1" Pro lk.img edit to remove the Orange State warning.
Onn Surf 7" gen 2 on sale for 28$ today. Bought one... Was able to unlock bootloader
Onn Surf 7" gen 2 on sale for 28$ today. Bought one... Was able to unlock bootloader So, stopped at walmart this morning for stuff and saw the Onn Surf is now on Gen 2. 2.0 GHz quad core, 16gb storage and 2 gb ram. Seemed pretty decent for...
forum.xda-developers.com
Click to expand...
Click to collapse
thnx ill check this out very soon. im working on a Wiko Ride rn. frp bypass was a total pain took 2 days of trial and error but i was able to bypass.XD
hightowerc said:
Help! I followed the instructions in the OP, and everything worked fine. I then used ADB to uninstall some of the preinstalled apps, but I think I uninstalled something I shouldn't have. i'm getting crashes from mutltiple apps (Bluetooth, Contacts, etc).
I've downloaded the stock firmware/full in the linked GDrive share; how can I restore back to this stock firmware? I'm pretty new/noob with this, but I am familiar with Linux commands. (familiar enough to be dangerous...)
Click to expand...
Click to collapse
What’s your system? Did you get it fixed? I know I screwed up my first go round with the 10.1 Bluetooth and such kept crashing after I removed one of the un used features well supposed to be unused. It was the telephony and the contacts and autodialer that caused my issues. But like I stated before there seems to be some kind of wireless data traffic that’s not supposed to be there hidden software wise and it seems to utilize the cellphone apps that are supposed to be unused. Like the original bloatware remover from one of these threads on the original android 9 versions cannot be used bc there is something utilizing the cellphone data apps.
Anyway if there is anything you need firmware wise let me know I’ll upload whatever I have available.
This is just BS. I agree about the hidden sim. I went through the different log files. This entire system is corrupt. My Google play store was installed by.... You guessed it Google Play. Click on it and I get a retry
My new Samsung phone is also screwed up and the 102.00 for Norton VPN and security was shredded in seconds.
There is NO original boot, no original system. What an I supposed to do? This is the 2nd one. Can't hard reset damn phone, Cricket because I've lost so many. I was able to hard set the Samsung without the SIM card, and it was perfect. Put the SIM card in, and all that freaking bloat comes in.
So I'm no IT person, with compromised systems that's supposed to download ANYTHING and just hope I'm not redirected?? I'm just so suck and Tues off this. I just need to search, make phone calls. I don't even do any social media any longer! Please, tell me what I can trust anymore??? And I'm just out another round it up to 500.00 and I'm in disability. I'm so disheartened and hopeless
I used this method to root the new tablet I just picked up, and now whenever I launch any app it freezes my tablet and forces a fast reboot of the tablet, I believe I am on android 10, but I can't confirm as I can't even open settings
okay, so I tried to completely flash the stock images you provided in the other thread, got everything working again, without root, then flashed the patched images you had and got stuck in a screen that just said onn with nothing else happening
edit: I have adb access to the device when it's plugged in so I'm not sure what is happening
Alright, I found out my issue, I was flashing the wrong patched boot img on an older firmware instead of updating to latest, I have gotten a working magisk root on the 10.1 tablet.
So as promised I have attached the lk.bin with the no orange state modification it does still seem to hang for 5 seconds but the ugly message is no longer visible.
this is for the 100003562 10.1 inch model but should work with the newer 10.1 inch models with the MT8768WA chipset that come with android 10.
Installation Instructions:
1. Download lknoorange.bin attached to post.
2. Open either powershell (Windows) or Terminal (linux) where you have the file saved.
3. Put device in fastboot mode by powering on and holding the volume up button and selecting fastboot with volume down button.
4. Use command:
"fastboot flash lk lknoorange.bin"
5. Use command:
"fastboot reboot"
Now you should no longer see the ugly message on boot.
Always love getting donations thanks again all and I wish you the happiest of holidays.
Trixi Needs a Rabbit said:
This is just BS. I agree about the hidden sim. I went through the different log files. This entire system is corrupt. My Google play store was installed by.... You guessed it Google Play. Click on it and I get a retry
My new Samsung phone is also screwed up and the 102.00 for Norton VPN and security was shredded in seconds.
There is NO original boot, no original system. What an I supposed to do? This is the 2nd one. Can't hard reset damn phone, Cricket because I've lost so many. I was able to hard set the Samsung without the SIM card, and it was perfect. Put the SIM card in, and all that freaking bloat comes in.
So I'm no IT person, with compromised systems that's supposed to download ANYTHING and just hope I'm not redirected?? I'm just so suck and Tues off this. I just need to search, make phone calls. I don't even do any social media any longer! Please, tell me what I can trust anymore??? And I'm just out another round it up to 500.00 and I'm in disability. I'm so disheartened and hopeless
Click to expand...
Click to collapse
I guess i'm kinda lost here at what you may be stating and or asking? what device are you needing help with? I do not have a samsung so i honestly can not be of much help other then to point you in the right direction.
If you need help with a stock image for the 100003562 i have one here.
So I didn't happen to back up my scatter or boot.img files when I used fastboot to try and flash the TWRP for the onn 10 inch, I was assuming it would work, but now I'm stuck with no recovery, no fastboot, no system, won't boot up when you hold the power button.
The only method of recovery I have is through MTK preloader and spflash, but I don't have the correct factory images or scatter file required to reflash stock. I've been looking everywhere online and can't find the right recovery files or any guides on how to recover from this.
Any help/files/advice would be greatly appreciated!!
Two things, I got access to my old account after a password reset
and, I got my tab back up and running, as well as root & xposed + gravitybox
I'm working on a guide as we speak.
Also, I will be dumping my firmware and adding the 10001885 to the list of stock image dumps on the main onn thread.
Hope this helps if still needing it, scatter file for the 100011885 mt8168 , good luck not responsible for anything lol i still cant get mine to work, anklosburner
Ankylo'sburner said:
So I didn't happen to back up my scatter or boot.img files when I used fastboot to try and flash the TWRP for the onn 10 inch, I was assuming it would work, but now I'm stuck with no recovery, no fastboot, no system, won't boot up when you hold the power button.
The only method of recovery I have is through MTK preloader and spflash, but I don't have the correct factory images or scatter file required to reflash stock. I've been looking everywhere online and can't find the right recovery files or any guides on how to recover from this.
Any help/files/advice would be greatly appreciated!!
Click to expand...
Click to collapse
hope this helps if you still need it for 100011885 mt8168 scatter file, but not responsible for any damages, because i still cant get mine to work, i had it to where it would come on, or i could see back light but thats it, which im impatient too, maybe it takes a min, but i did a readback on every downloadable item and flashed it but idk, let me know if you or how you get yours to work if you do
bbcdt22 said:
Hope this helps if still needing it, scatter file for the 100011885 mt8168 , good luck not responsible for anything lol i still cant get mine to work, anklosburner
hope this helps if you still need it for 100011885 mt8168 scatter file, but not responsible for any damages, because i still cant get mine to work, i had it to where it would come on, or i could see back light but thats it, which im impatient too, maybe it takes a min, but i did a readback on every downloadable item and flashed it but idk, let me know if you or how you get yours to work if you do
Click to expand...
Click to collapse
Hey, i've had that same issue but have since fixed it by flashing the rom to the 100011886. I used some of the posts here to flash both vbmeta.img and boot.img to gain root, with success https://drive.google.com/drive/folders/17LtLtjKg4JJU9EJdIXPsyNjen0H-ilMX?usp=sharing . i eventually went too far and currupted my rom and had a hard time finding the stock ROM. I found the stock ROM to the 100011886 and flashed that to fix the problem, now i run that as my system and it boots up just fine. https://www.mediafire.com/file/107jp6gwbiwq87q/MT8168_ONN_Gen2_100011886.zip/file
fastboot erase super
fastboot flash super super.img
Would you happen to have the preloader bin file for the MT8168? After digging around, you have helped me get closer to bringing my hard brick back to life.
Edit: @bbcdt22
onn. said:
Would you happen to have the preloader bin file for the MT8168? After digging around, you have helped me get closer to bringing my hard brick back to life.
Edit: @bbcdt22
Click to expand...
Click to collapse
I don't, but this thread may help:
[STOCK] Stock Backups/Images/OTAs
Since these tablets don't have an external online resource for downloading system updates, only a sketchy OTA app (com.adups.fota) I'm collecting a library of OTAs, as well as boot/recovery/system images. I have access to a 10.1 with keyboard...
forum.xda-developers.com
Any rom you come across has to be extracted in order to get any necessary files from it. The thread mentions using 7zip but I've personally had better results extracting using ZArchiver. Also, a workaround I've found very useful when dealing with extraction issues, is removing the extension from the file. If all else fails, you may need to erase the super partition and reflash THAT
KMerrimanJr said:
I don't, but this thread may help:
[STOCK] Stock Backups/Images/OTAs
Since these tablets don't have an external online resource for downloading system updates, only a sketchy OTA app (com.adups.fota) I'm collecting a library of OTAs, as well as boot/recovery/system images. I have access to a 10.1 with keyboard...
forum.xda-developers.com
Any rom you come across has to be extracted in order to get any necessary files from it. The thread mentions using 7zip but I've personally had better results extracting using ZArchiver. Also, a workaround I've found very useful when dealing with extraction issues, is removing the extension from the file. If all else fails, you may need to erase the super partition and reflash THAT
Click to expand...
Click to collapse
Thanks for the response. I'm at the end of that thread currently trying to see what I can find to fix my issue. Aside from buying another one from Walmart and trying to see if I can pull everything from a vanilla tablet, I'm not sure if I'll ever find the exact files.
onn. said:
Thanks for the response. I'm at the end of that thread currently trying to see what I can find to fix my issue. Aside from buying another one from Walmart and trying to see if I can pull everything from a vanilla tablet, I'm not sure if I'll ever find the exact files.
Click to expand...
Click to collapse
onn. said:
Thanks for the response. I'm at the end of that thread currently trying to see what I can find to fix my issue. Aside from buying another one from Walmart and trying to see if I can pull everything from a vanilla tablet, I'm not sure if I'll ever find the exact files.
Click to expand...
Click to collapse
When my tab crashed on me, flashing the super image solved my issue but it was a different rom. My tab's model number ended in 885 but the super file I flashed came from an 886, it still worked though
KMerrimanJr said:
When my tab crashed on me, flashing the super image solved my issue but it was a different rom. My tab's model number ended in 885 but the super file I flashed came from an 886, it still worked though
Click to expand...
Click to collapse
I wish I would have waited until I read this today instead of further messing with it yesterday. It looks like everything you have is what I need, but now I am battling trying to get the COM port to stay active when the device is plugged in. I'll tinker with it and see if I can get back to the state I had it in yesterday where it was staying connected.
KMerrimanJr said:
When my tab crashed on me, flashing the super image solved my issue but it was a different rom. My tab's model number ended in 885 but the super file I flashed came from an 886, it still worked though
Click to expand...
Click to collapse
Would you happen to know/remember all the settings you checked in SP Flash Tool (I assume you used that) when you flashed things to get it working? It seems that my PC is able to communicate with the device again, but I'm unsure of how to proceed next.
Have you installed all of the adb & mtk drivers? If so, you should be able to use adb to reboot into the boot loader then use fast boot to flash the super file
KMerrimanJr said:
Have you installed all of the adb & mtk drivers? If so, you should be able to use adb to reboot into the boot loader then use fast boot to flash the super file
Click to expand...
Click to collapse
It's hard bricked at the moment unfortunately, so there's no appearance of life to it. Attached picture is the error I get. https://www.gizmoadvices.com/list-sp-flash-tool-error-codes-solution-fix/ appears show info about the error, but it's not something I know how to fix yet.
The only way I can get the tablet to make moves in device manager (which I assume is a sign that the PC can at least partially recognize/see the device) is to click on Download in SPFT, connect tablet to PC via USB cord, and then hold down power button, which led to the error. Errors in SPFT I've received so far are 0xC0060001 and 0xC0060003.
When the tablet is active in the device manager, I assume that the device is in a powered state. However, when the device is grayed out, I assume it's in a powered off state (see other pic). I've yet to find away to actually flash anything to it.
KMerrimanJr said:
Have you installed all of the adb & mtk drivers? If so, you should be able to use adb to reboot into the boot loader then use fast boot to flash the super file
Click to expand...
Click to collapse
Also, apologies if I'm being a bother, but do you know what version of SPFT you used as well as which DA file?
bbcdt22 said:
Hope this helps if still needing it, scatter file for the 100011885 mt8168 , good luck not responsible for anything lol i still cant get mine to work, anklosburner
hope this helps if you still need it for 100011885 mt8168 scatter file, but not responsible for any damages, because i still cant get mine to work, i had it to where it would come on, or i could see back light but thats it, which im impatient too, maybe it takes a min, but i did a readback on every downloadable item and flashed it but idk, let me know if you or how you get yours to work if you do
Click to expand...
Click to collapse
where did you get this? did you dump it? if so how?