Database Users

[dev][apx][nvflash][tegra-note-7][update]

If anybody bricks his/her device and has only the APX mode available or is trying to get an nvflash utility for a Tegra Note 7, now the solution can be found: the Advent company has published a full package including a nvflash working with the Tegra Note 7. Moreover, the package contains a signed bootloader and bct and all the other parts of the entire storage (including the system partition for a 4.3. JellyBean).
It can be downloaded from their website of adventcomputers.co.uk in the downloads section (I can't post links yet), select Product range: "Advent"; Product type: "Tablet"; and then choose "ADVENT Vega Tegra Note 7", do not be mystified by the "driver" type and download the "Advent Vega Tegra Note Factory Image (4.3)" (about 641 MB package)
Many thanks to the dev and support guys at Advent (Dixons retail plc), because they have put the final cherry on the top of the cake. The Nvidia Tegra Note 7 is now not only a top of the top devices regarding its power, but this package renders it into an unbrickable device.
(note: I'm NOT affiliated with any of the companies, I just bricked my device and had no other mode available than the APX mode. I'm posting this post due to the abovementioned reasons, because I find this quite and important source for further hacking(orig. meaning) of the devices. In fact I regard this as an utlimate source for development on this platform.)
I have tried the package (including the batchfile, that does the automation), it works for me on my Advent Vega Tegra Note 7, however Im not sure if it will work on others (EVBA for example), so please feel free to test and post your experience underneath here.

Link: http://adventcomputers.co.uk/product-download-select/296
Sent from my TegraNote-P1640 using Tapatalk

thx

Thanks for the heads up. I tried it on my bricked dodgy manufactured tablet and I was able to get the device to a new level but it still crashes trying to boot the system partition. Least now I have fastboot.
With the nvflash recovery tools you can replace the images to suit say bat-recovery or latest boot.img with menu options the older version doesn't have.

Wait what?! Why havent I been notified?! And subscription to my own thread has been lost?!?! O__o ill take a look at this!!!!
Edit: I see, this isnt my thread thanks ill reopen my thread

Shaky156 said:
Wait what?! Why havent I been notified?! And subscription to my own thread has been lost?!?! O__o ill take a look at this!!!!
Edit: I see, this isnt my thread thanks ill reopen my thread
Click to expand...
Click to collapse
HEhehee. This nvflash recovery is only new to the scene so I didn't get time to check it out then inform you Shaky.
In my opinion our community can rehash these tools and make a better recovery.

Shaky156 said:
Wait what?! Why havent I been notified?! And subscription to my own thread has been lost?!?! O__o ill take a look at this!!!!
Edit: I see, this isnt my thread thanks ill reopen my thread
Click to expand...
Click to collapse
I have tried to make a request on the admin who locked Your threead and wanted to post it there (see my message to Moscow Desire below), but I did not get any answer, so I did not want to dealy such an important newz anymore, so I have allowed myself to open a new thread with simmilar markings. Sorry for the discomfort, but I do not see any other way of behaving corerctly, if this forum platform and its admins do not provide support for this.
With regards
------ Original message ---------
Reopening a closed thread?
There is a thread I would like you to reopen, since the state of things has heavilly changed. The post I would like to post is an quite important one, while it may contain a link to a commercial site, it also points to an nvflash utility working with Tegra Note 7, including signed bootloader and BCT. Moreover, the (non-purchase and registration free) download package is made by a commercial partner of nVIDIA with (AFAIK from their support) full consent of nVIDIA. For the Tegra Note it is the last missing bit for the full controll of the device starting from APX mode up to the various other run-modes.
Im not affiliated with neither of the abovementioned companies, I just bricked my device and had no way to recover it since APX was the only rescue, so they published the whole package (for 4.3 JB). I think mentioning this as well the link to the package is worthwhile the post, but I do not feel that starting a new thread would be correct.
Thread to be reopened: (link to your original thread)
Would this be possible?
Thanks

rheingold said:
I have tried to make a request on the admin who locked Your threead and wanted to post it there (see my message to Moscow Desire below)., but I did not get any answer, so I did not want to dealy such an important newz anymore, so I have allowed myself to open a new thread with simmilar markings. Sorry for the discomfort, but I do not see any other way of behaving corerctly, if the platform and its admins do not provide support for this.
With regards
------ Original mail ---------
Reopening a closed thread?
There is a thread I would like you to reopen, since the state of things has heavilly changed. The post I would like to post is an quite important one, while it may contain a link to a commercial site, it also points to an nvflash utility working with Tegra Note 7, including signed bootloader and BCT. Moreover, the (non-purchase and registration free) download package is made by a commercial partner of nVIDIA with (AFAIK from their support) full consent of nVIDIA. For the Tegra Note it is the last missing bit for the full controll of the device starting from APX mode up to the various other run-modes.
Im not affiliated with neither of the abovementioned companies, I just bricked my device and had no way to recover it since APX was the only rescue, so they published the whole package (for 4.3 JB). I think mentioning this as well the link to the package is worthwhile the post, but I do not feel that starting a new thread would be correct.
Thread to be reopened: (link to your original thread)
Would this be possible?
Thanks
Click to expand...
Click to collapse
Hi i dont have an issue with this, mistake on my part, I thought this was my thread lol. Ive reopened my thread and its moved to Q&A. Will work on a newer things, I have new files. Will test few things first.

Hi
I try download it but every time when is finish file is corrupted.
Can anybody share Vega Tegra Note Factory Image file?
Best regards

After finding out after a long time about this guide,I managed to reflash the stock firmware and reset the tablet,so hurray and much thanks for sharing this guide
Sent from my HTC One X using XDA Premium 4 mobile app

Ok, I need some help if anyone can.
I erased the boot file on my Nvidia EVGA Tegra Note 7 P1640 tablet and now I'm stuck. I had set usb debugging on in the tablet and as far as I know, it's still on. I have tried everything I can think of and nothing works. First, there are 3 driver_install.bat files in the Vega7\usbpcdriver folder. Being that I'm running windows 7 64bit with an AMD processor, I select driver_install_amd64.bat and it fails wanting $P4ROOT$ to be set. I may be wrong, but I set it to D:\Android\Vega7 (in the install_driver_amd64.bat). Please correct me if I'm wrong. Second, if I set p4root to D:\android\vega7 (where the Vega7 folder is), it fails with "NT DDK at //sw/tools/ddk/nt6/6001.18002/... is not synced" and fails. I have no idea what to do about this. If I goto the vega7 directory and click on flash_signed.bat, it stops at >SN.txt and just sits there. I thought I was fairly computer savy, but apparently I'm not.
I've followed the instructions as written up to the point it freezes up on me, however there is no info on what to do if the batch files fail.
I can get the tablet into APX mode in the device manager, but the drivers are not loaded. I can load the drivers in the usbpcdrivers folder, which installs "Nvidia USB Boot-recovery driver for Mobile devices", but still can't get the flash_signed.bat to go any farther than >SN.txt. (I turned echo on in the bat file so I could see what was happening)
So please, anyone, help. I've only got one hand full of hair left and it's about to go too.

Always use usb without option for power charging.
Change USB port if not try on different computer, I was stuck on my one when I try do flash, go on my girlfriend laptop and done without any problems.
Hiro51 said:
Ok, I need some help if anyone can.
I erased the boot file on my Nvidia Tegra Note 7 P1640 tablet and now I'm stuck. I had set usb debugging on in the tablet and as far as I know, it's still on. I have tried everything I can think of and nothing works. First, there are 3 driver_install.bat files in the Vega7\usbpcdriver folder. Being that I'm running windows 7 64bit with an AMD processor, I select driver_install_amd64.bat and it fails wanting $P4ROOT$ to be set. I may be wrong, but I set it to D:\Android\Vega7 (in the install_driver_amd64.bat). Please correct me if I'm wrong. Second, if I set p4root to D:\android\vega7 (where the Vega7 folder is), it fails with "NT DDK at //sw/tools/ddk/nt6/6001.18002/... is not synced" and fails. I have no idea what to do about this. If I goto the vega7 directory and click on flash_signed.bat, it stops at >SN.txt and just sits there. I thought I was fairly computer savy, but apparently I'm not.
I've followed the instructions as written up to the point it freezes up on me, however there is no info on what to do if the batch files fail.
I can get the tablet into APX mode in the device manager, but the drivers are not loaded. I can load the drivers in the usbpcdrivers folder, which installs "Nvidia USB Boot-recovery driver for Mobile devices", but still can't get the flash_signed.bat to go any farther than >SN.txt. (I turned echo on in the bat file so I could see what was happening)
So please, anyone, help. I've only got one hand full of hair left and it's about to go too.
Click to expand...
Click to collapse

lizard-borys said:
Always use usb without option for power charging.
Change USB port if not try on different computer, I was stuck on my one when I try do flash, go on my girlfriend laptop and done without any problems.
Click to expand...
Click to collapse
Can't use usb without power. The tablet will not stay turned off now and because of that, the battery won't charge enough to usb without power from usb.
I've even plugged in the charger and gone into boot-loader and clicked on shut down, but it still won't stay off or take a decent charge.
I have tried a different computer as well as different ports with the same results.
btw, thanks for replying.
As I reread the posts, I noticed rheingold's post at the bottom says he's not sure if this will work on the (I believe he meant EVGA) model. Can anyone verify it works on EVGA?

Solved. Bad USB cable. Unbelievable! I guess the original cable only works when it wants to. Used usb cable from old kindle with complete success. Fully restored to 4.4.2, rooted, and sd card fixed. I'm back in business. Gotta love those rootjunkys super tools.

Hiro51 said:
Solved. Bad USB cable. Unbelievable! I guess the original cable only works when it wants to. Used usb cable from old kindle with complete success. Fully restored to 4.4.2, rooted, and sd card fixed. I'm back in business. Gotta love those rootjunkys super tools.
Click to expand...
Click to collapse
Nice work mate. I am speaking with Nvidia too see if they will do factory images like the Shield but waiting on a response for that.
Also OTA 2.4 is now Live as of 5 minutes ago.
It seems the USB cables are not of high quality just like the ports.

lizard-borys said:
Hi
I try download it but every time when is finish file is corrupted.
Can anybody share Vega Tegra Note Factory Image file?
Best regards
Click to expand...
Click to collapse
Having the same issue here.. anyone?

I have a copy if its needed still.

Today, panic stations as I thought I had bricked my Advent Vega Tegra Note 7.
I had updated yesterday to KitKat along with additional OTA updates, but decided
to go back to 4.3 to capture the update after main KitKat update (2nd of 6 updates [EDIT: forgot to cap that one]).
I unlocked bootloader via fastboot, then flashed system.img (4.3 from Advent) and then the TWRP
recovery.img EDIT: Also locked bootloader..
On boot, it got itself stuck Powered ON at the TEGRA NOTE (white on black) screen, all was doom and gloom.
I finally figured out that holding down Volume+ then pressing the power button quickly and then
pressing again (whilst still holding the volume+ button down), I could get into the recovery menu
to access TWRP. In TWRP I did a factory reset and hoped for the best.
On reboot, all was still doom and gloom. So I thought maybe it might be necessary to have the
appropriate boot image (rather than the 4.4 boot image), and so flashed that, and Voila,
everything is hunky dory again.
I seem to have lost ability to use nvflash (APX mode) after original 4.3 flashing (which I could access
on the device doing the same dance as above but pressing both volume up and volume down keys before power).
My USB driver Vender ID and Product ID's below, I seem to have two Fastboot Id's, presumably one for stock recovery
and the other for TWRP (I blanked last 5 digits with x's just in case they could be used for nefarious deeds).
Code:
Fastboot Advent Vega Tegra Note 7 Fastboot Vid_0955&Pid_cf01\052101410714600xxxxx
TegraNote-Premium Google Galaxy Nexus ADB Interface Vid_18d1&Pid_d001
Tegra NOTE TegraNote-P1640 Vid_0955&Pid_cf02
Fastboot Advent Vega Tegra Note 7 Fastboot Vid_0955&Pid_cf01\15C4110C904000000100xxxxx
Advent Vega Tegra Note 7 Vid_0955&Pid_cf00&MI_00
Tegra NOTE Advent Vega Tegra Note 7 ADB Vid_0955&Pid_cf00&MI_01
Tegra NOTE USB Composite Device Vid_0955&Pid_cf00
APX NVIDIA USB Boot-recovery driver for Mobile devices Vid_0955&Pid_7535
Anyway, perhaps above is all known to you old salts, but for a newbie like me, is perhaps of use.
Also, thanks for the link

You can access APX by pressing Power plus Volume down and Volume UP at the same time and holding them.

Thanx hacktrix, I could access APX OK (was stuck with power on, ie could not power off, the dance described allowed me the access both fastboot and APX).
The problem was nvflash via flash_signed.bat.

Onn 7" SURF Model 100005206

I have since returned this tablet. The go edition was just too much, or way too little for me to deal with.
The 7" variant shouldn't be considered a variant as it is only similar in shape and color. It is however still rootable. I am assuming you have adb and fastboot set up and know how to use them. Also if on windoze you know how to adjust if needed and to connect device with usb and the other little details I've overlooked. If not then I am also assuming you don't need to try this yet.
The root process is not difficult but tricky in that it is different. Before doing this you need to go to Magisk release thread and check out link for running Recovery Mode and read it all. You must have unlocked bootloader. The process goes something like this:
Edit: You will need the latest platform tools for fastboot to work properly. This link https://www.xda-developers.com/what-is-adb/ provides instructions for windows and Linux. Yes, you may need to update the tools in some Linux installations as not all repositories are kept up to date with regards to android-sdk.
1) Download mtk-su by @diplomatic to your pc.
2) Open a terminal in window where you have mtk-su. You can cd to it but this seems easier. Type the following "adb push mtk-su /data/local/tmp/"
3)Type "adb shell chmod 755 /data/local/tmp/mtk-su
4)Type "adb shell" you will enter a shell with no need to cd to anywhere. If you cd /data/local/tmp then you need to cd back out of it when root shell is achieved. If you run it this way your ready to go without changing directories
5) Type "./data/local/tmp/mtk-su -v" you now have a root shell. If for some reason you do not have root access, run mtk-su again, it will work.
6)Now the confusing part. You need to copy your recovery to patch with Magisk. You use "dd if=/dev/block/mmcblk0p10 of=/sdcard/recovery.img your recovery should be in internal storage when you open your file manager.
7)Install Magisk Manager and open it to select install. Before install you tick advanced settings and tick Recovery Mode. You then select install. A toast will pop up and you select the bottom one which is to patch your boot.img file. Wherever you see boot you use your recovery instead.
8)Magisk will put your patched recovery labeled magisk_patched.img in your download folder. Transfer it to your PC.
9)In terminal on PC open window where you have your magisk_patched.img. Then use adb reboot bootloader.
10) Flash your patched img with "fastboot flash recovery magisk_patched.img" and you're done flashing.
11) Now the fun part, you hold power and volume+ until you first get a glimpse of the boot selection screen. AS SOON AS IT LIGHTS UP LET GO for a second,just a second, then scroll to recovery and hit volume- . If its already on recovery just use volume down, do not scroll around to it. Your tablet will boot into a Magisk rooted system and not recovery.
It can be tricky but however you boot your tablet determines if you're rooted or not. When Magisk Manager reboots after installing a module it know what it's doing and you don't have to do anything but wait on it. Whenever booting your system you need to make your first priority going to magisk to check if it's installed before trying anthing. You need to do this every time you boot until you have your timing right and confidence way up. Then you should probably still check.
From what I can see when not booted to Magisk rooted system, installed modules and changes made are obviously not working. It should stand to reason if Magisk is not installed that magisk modules won't work. Like I said, its not hard it's just odd to me. Don't know how porting recovery is going to go. Wondering if we will need to patch the ported img or port the patched img. It's is treble compatible, I've read a-only but don't know about gsi's yet. Keeping expectations low though.
When I had Magisk installed I was left with no recovery or I didn't keep it long enough to figure it out. When booting with hardware buttons and holding for recovery/unrooted system the tablet booted to an unrooted system bypassing recovery all together. Don't know if it was procedural error on my part or if that is the compromise that has to be made to have perm root for the time being. Flashing stock recovery via fastboot proposed no issues.

Good information, thanks!
What prevented the usual patched boot image method from working?

NFSP G35 said:
Good information, thanks!
What prevented the usual patched boot image method from working?
Click to expand...
Click to collapse
No ramdisk in boot.img. It works but just feels weird. Also from what I've gathered it can't be installed/upgraded via custom recovery. Not that there is one but down the road that's a bummer.

My apologies I withdraw my question.... I see that the 7 is different from the 8 & 10 where the recovery.img is being patched instead of the boot.img I will make note of that when I start my video tutorial series for the onn line of tablets.

The 7" definitely does not belong to the same family as the x003 and x002. The items partition (items.ini) only has hardware configuration for 10" and 8" tablets. I don't own the x007 keyboard variant, but I would not doubt the the 10" x003 dump would probably run on it. (speculation; not conclusive)

CaffeinePizza said:
The 7" definitely does not belong to the same family as the x003 and x002. The items partition (items.ini) only has hardware configuration for 10" and 8" tablets. I don't own the x007 keyboard variant, but I would not doubt the the 10" x003 dump would probably run on it. (speculation; not conclusive)
Click to expand...
Click to collapse
It's Android (go edition) and it appeared as if everything were different. Even its google apps are different. I don't think they show up in play store unless you are on a go edition device. I have an account but only have google services on one device so don't use playstore enough to be sure. But the names all have go on them as in maps go, youtube go and chrome go. Go is slow, no ? I don't believe I seen a /vbmeta partition either. I was going to install a gsi to get rid of go but it was a no go. Not aware of any documentation for installing gsi's on go edition devices although it is supposed to be compatible, what's the point? Modified should mean some type of performance gain, somewhere at least. Coming in with just over 900MiB of RAM (not 1G) it's only close but still roughly 10% down from advertised. I had referred to it as the runt at one point, and it is that in every sense of the word. Smaller, weaker and slower was more than I cared to deal with. You can polish a pile of crap all day long, and at the end of the day, the best you can hope for is just a shiny turd. Too many other options and way better things to waste 50 bucks on. I returned it after a couple of days. The 8" and 10" tablets could stand a little better build quality. But over all I believe they knocked it out of the park with them. The 7", well... foul ball!

tek3195 said:
It's Android (go edition) and it appeared as if everything were different. Even its google apps are different. I don't think they show up in play store unless you are on a go edition device. I have an account but only have google services on one device so don't use playstore enough to be sure. But the names all have go on them as in maps go, youtube go and chrome go. Go is slow, no ? I don't believe I seen a /vbmeta partition either. I was going to install a gsi to get rid of go but it was a no go. Not aware of any documentation for installing gsi's on go edition devices although it is supposed to be compatible, what's the point? Modified should mean some type of performance gain, somewhere at least. Coming in with just over 900MiB of RAM (not 1G) it's only close but still roughly 10% down from advertised. I had referred to it as the runt at one point, and it is that in every sense of the word. Smaller, weaker and slower was more than I cared to deal with. You can polish a pile of crap all day long, and at the end of the day, the best you can hope for is just a shiny turd. Too many other options and way better things to waste 50 bucks on. I returned it after a couple of days. The 8" and 10" tablets could stand a little better build quality. But over all I believe they knocked it out of the park with them. The 7", well... foul ball!
Click to expand...
Click to collapse
It's probably 1GB or 953MiB of RAM. Powers of ten rather than powers of two.

CaffeinePizza said:
It's probably 1GB or 953MiB of RAM. Powers of ten rather than powers of two.
Click to expand...
Click to collapse
May have been 953 can't remember now thankfully can't check either. But less than a G which is more like 1024 i believe. That would still be in the ballpark with what I called roughly 10 percent. I only put that because 10 percent could be huge considering a lot of times we tweak and modify for gains much smaller. It wasn't meant to be a technical review. When you get one, get as technical as you want with it. It will still be a piece of sh*t.

tek3195 said:
May have been 953 can't remember now thankfully can't check either. But less than a G which is more like 1024 i believe. That would still be in the ballpark with what I called roughly 10 percent. I only put that because 10 percent could be huge considering a lot of times we tweak and modify for gains much smaller. It wasn't meant to be a technical review. When you get one, get as technical as you want with it. It will still be a piece of sh*t.
Click to expand...
Click to collapse
I do not plan on supporting the 7" tablet. Probably just burst some bubbles.

tek3195 said:
No ramdisk in boot.img. It works but just feels weird. Also from what I've gathered it can't be installed/upgraded via custom recovery. Not that there is one but down the road that's a bummer.
Click to expand...
Click to collapse
What about modifying the boot.img to create the ram disk?

callihn said:
What about modifying the boot.img to create the ram disk?
Click to expand...
Click to collapse
Not sure I follow. The ramdisk it uses is in the recovery.img not sure what you would be trying to create or use it for. You lost me.

I've managed to unlock the bootloader, but the system boots up normally... Stock recovery if I choose recovery. Where did I go wrong?

i think your crazy also, I patched the recovery, and it doesn't work, it goes to a blank screen, if you had screen shots it might be more convincing, what does majick do taking over recovery, means using root from a p.c ???

https://gist.github.com/varhub/7b9555cdd1e5ad785ffde2300fcfd0bd
---------- Post added at 06:10 PM ---------- Previous post was at 06:08 PM ----------
if goes to majick recovery see if it's rooted with adb
---------- Post added at 06:17 PM ---------- Previous post was at 06:10 PM ----------
when you say building, found an interesting article where you might build or free ramdisk, even boot to majick root recovery, I'm just researching the idea
https://source.android.com/devices/bootloader/partitions/ramdisk-partitions

have you tried flashing with a gsi ROM, this sounds great
https://forum.xda-developers.com/pr...hVM2htbVVRNGhnUzU5ZktDUUNSZjlzdGE2bkk4TjhZY3M.

flashing gsi rom on surf 7, changed vbmeta to dtbo.img, got a black screen with no way to fix, no recovery ? does anyone know the proper way to flash one

Walmart ONN Surf 100005208

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.

(HELP NEEDED) Onn 8" gen 2, 100011885 no boot

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?

Onn 7" Model 100026191 TWRP Development

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/