Database Users

The unbrick image for HDX 7"

Hey everybody,i have pulled out the image from HDX 7"(base on system version--13.3.2.5_user_325001120),it includes the "boot,recovery and system",i hope that it's useful for those who bricked their HDX 7".
if you need other image like “aboot,dkernel,modem,modemst” and so on,you can leave a message to me,although i think it not useful,it's enough for you having "boot,recovery and system".
By the way,i wanna know how to let the HDX 7" get into the fastboot mode?except of using the command--"adb reboot bootloader" ,it's useful when the HDX 7" in normal use,but in fact,if HDX 7" can't boot into the normal mode,you can't do anything about typing command,because computer can't recognise it as adb devices!
click the link to download the images! http://pan.baidu.com/s/1gd7VPib

Hey, thanks
It would be really nice if somebody came up with a solution to flash the firmware in fastboot mode (even in linux where u dont need any drivers).
I believe that would solve many bricked devices out there.

boom1212go said:
Hey everybody,i have pulled out the image from HDX 7"(base on system version--13.3.2.5_user_325001120),it includes the "boot,recovery and system",i hope that it's useful for those who bricked their HDX 7".
if you need other image like “aboot,dkernel,modem,modemst” and so on,you can leave a message to me,although i think it not useful,it's enough for you having "boot,recovery and system".
By the way,i wanna know how to let the HDX 7" get into the fastboot mode?except of using the command--"adb reboot bootloader" ,it's useful when the HDX 7" in normal use,but in fact,if HDX 7" can't boot into the normal mode,you can't do anything about typing command,because computer can't recognise it as adb devices!
click the link to download the images! http://pan.baidu.com/s/1gd7VPib
Click to expand...
Click to collapse
the question is how to unbrick the kindle if adb doesn't work ??
if using QPST , we need the xml files and how go to download mode
using pc only recognise QHSUSB_BULK, if install Qualcomm driver only detect as 9008, so need to change 9008 to 9006
so how to resolve this problem?? anyone can give some tutorial please.
thank you.

Check out this post, page 2 maybe has a solution for you. Good Luck!
http://forum.xda-developers.com/showthread.php?t=2795602

Hi friend,
I have a kindle hdx with fire os 13.3.2.5
I already rooted and installed safe trap
I already back up rom stock and flash your rom thor gapps 13.3.2.4 on rom slot
But when it go to first screen, it stop and reboot. And bootlop but can access safe trap.
I restore back up but similar can't boot.
I think i must flash rom stock 13.3.2.5 but i don't have zip file. Can you extract it ? please help. Thank. I hope your reply.

I know how to get into fastboot!!!
you just need to get a fastboot cable (the 2nd and 5th pins (or 1st and 4th?) are jumped. If you look up fastboot cable or factory cable you should be able to find it. I personally "made" one by taking a small piece of wire and sticking it under the proper pins in a semi-broken usb cable(wouldn't stay into device). I've had to use it many many times on my kindle fire hd 7"

CalebQ42 said:
you just need to get a fastboot cable (the 2nd and 5th pins (or 1st and 4th?) are jumped. If you look up fastboot cable or factory cable you should be able to find it. I personally "made" one by taking a small piece of wire and sticking it under the proper pins in a semi-broken usb cable(wouldn't stay into device). I've had to use it many many times on my kindle fire hd 7"
Click to expand...
Click to collapse
No, a fastboot cable doesn't do anything on the hdx

epicfailol said:
No, a fastboot cable doesn't do anything on the hdx
Click to expand...
Click to collapse
I've found it works if you first connect it to the device then connect it to the computer. Of course the device I'm working with for some reason has software version 11.3.2.5

umm
CalebQ42 said:
I've found it works if you first connect it to the device then connect it to the computer. Of course the device I'm working with for some reason has software version 11.3.2.5
Click to expand...
Click to collapse
Again again this is the HDX forum completely different from the HD different processor and everything .. If you plug a fast cable into the HDX it puts it in QUPST mode and takes a few minutes of messing with it to get it out of it so far we cannot use that either..so far.

jimyv said:
Again again this is the HDX forum completely different from the HD different processor and everything .. If you plug a fast cable into the HDX it puts it in QUPST mode and takes a few minutes of messing with it to get it out of it so far we cannot use that either..so far.
Click to expand...
Click to collapse
Sorry about that, I didn't know there was a 3rd generation kindle fire hd that looked exactly like the hdx. Been trying to root this thing for hours before I found that out
Sent from my Nexus 5 using XDA Premium HD app

boom1212go said:
Hey everybody,i have pulled out the image from HDX 7"(base on system version--13.3.2.5_user_325001120),it includes the "boot,recovery and system",i hope that it's useful for those who bricked their HDX 7".
if you need other image like “aboot,dkernel,modem,modemst” and so on,you can leave a message to me,although i think it not useful,it's enough for you having "boot,recovery and system".
By the way,i wanna know how to let the HDX 7" get into the fastboot mode?except of using the command--"adb reboot bootloader" ,it's useful when the HDX 7" in normal use,but in fact,if HDX 7" can't boot into the normal mode,you can't do anything about typing command,because computer can't recognise it as adb devices!
Hi Friend,
Flash boot & recovery is ok, but flash system is failed. It says FAILED (Remote: data too large)
Click to expand...
Click to collapse

Flash boot & recovery is ok, but flash system is failed. It says FAILED (Remote: data too large)
Click to expand...
Click to collapse
need special amazon fastboot binary for this
but you always can flash stock image wih twrp if you already unlocked.

ONYXis said:
need special amazon fastboot binary for this
but you always can flash stock image wih twrp if you already unlocked.
Click to expand...
Click to collapse
Thanks for your response. Yes, but in TWRP mode, I run "adb devices", the result is "13160d23................................unauthorized". Cannot push file.

It strange but anyway when you in TWRP you must see your device as MTP.

boom1212go said:
Hey everybody,i have pulled out the image from HDX 7"(base on system version--13.3.2.5_user_325001120),it includes the "boot,recovery and system",i hope that it's useful for those who bricked their HDX 7".
if you need other image like “aboot,dkernel,modem,modemst” and so on,you can leave a message to me,although i think it not useful,it's enough for you having "boot,recovery and system".
By the way,i wanna know how to let the HDX 7" get into the fastboot mode?except of using the command--"adb reboot bootloader" ,it's useful when the HDX 7" in normal use,but in fact,if HDX 7" can't boot into the normal mode,you can't do anything about typing command,because computer can't recognise it as adb devices!
click the link to download the images! http://pan.baidu.com/s/1gd7VPib
Click to expand...
Click to collapse
My device is 13.3.2.0. I follow this “http://forum.xda-developers.com/kin...to-unbrick-kindle-fire-hdx-firmware-t3277197” now in TWRP mode, but I don’t know how to flash the system.img.
By the way, I installed 13.3.2.3.2 stock firmware from TWRP, but it stick at Grey logo as well.

Samson Lau said:
By the way, I installed 13.3.2.3.2 stock firmware from TWRP, but it stick at Grey logo as well.
Click to expand...
Click to collapse
after flashing 13.3.2.3.2 go to TWRP - advanced - copy log to sd
and attach log that locatesd in the root of intrenal memory of your tablet.

ONYXis said:
after flashing 13.3.2.3.2 go to TWRP - advanced - copy log to sd
and attach log that locatesd in the root of intrenal memory of your tablet.
Click to expand...
Click to collapse
I did according to your advice, but it still stick at grey logo during reboot.

Please post your /sdcard/recovery.log here
or flash CM11 to be sure

ONYXis said:
Please post your /sdcard/recovery.log here
or flash CM11 to be sure
Click to expand...
Click to collapse
Good evening:
Are there any methods to get a Thor or Apollo running 4.2.5 or similar rolled back to the pre-3.2.5 as these posts seem to require? I have an Apollo running 14.3.2.5 which seems to be the lowest FW you can get to if you are running the higher than 3.2.5 FW.
I was wondering if the fastboot method would allow the flashing of a complete set of images from the earlier firmware series making an end run around the newer firmware?
Regards

galearned said:
Good evening:
Are there any methods to get a Thor or Apollo running 4.2.5 or similar rolled back to the pre-3.2.5 as these posts seem to require? I have an Apollo running 14.3.2.5 which seems to be the lowest FW you can get to if you are running the higher than 3.2.5 FW.
I was wondering if the fastboot method would allow the flashing of a complete set of images from the earlier firmware series making an end run around the newer firmware?
Regards
Click to expand...
Click to collapse
- can not roll back FireOS v4 below 3.2.8 due to anti-rollback barrier (intentional or inadvertent) that will brick device if further rollbacks are attempted
- 3.2.6 and below can be rolled back to 3.1.0 which can be rooted and unlocked. Rollback method contingent on starting point.
- native fastboot environment is crippled until bootloader unlocked

K1 - 6.0.1 Rollout Day? AH has just posted....

Android 6.0.1 Update Rolling Out To NVIDIA SHIELD Tablet K1
Anyone see anything yet? Sounds like a few good fixes plus the official Vulcan API..
1.2 K1 Update from Nvidia site
Supports the new Vulkan™ API for high-efficiency access to SHIELD’s graphics hardware
Adds Android 6.0.1 changes
Repositioned Navigation Buttons in Landscape mode & Updated Emojis
Double Tap Power Button to launch SHIELD Camera app
Do Not Disturb Until Next Alarm
Support for Android Doze mode & additional power optimizations
Adds USB MIDI support
Adds memory compression enhancement
Improved Wi-Fi connectivity when waking from sleep
Fixed Compass functionality
Fixed Gamepad Mapper issues
Fixed issues with moving apps to SD card
Fixed Doom 3 HDMI output issue
Repositioned Lasso Capture icons in landscape mode
Update to Android 6.0 Security Patch Level March 1, 2016
Overall stability and security enhancements

I got the update a few hours ago, we finally got the new emojis!
Sent from my SHIELD Tablet K1 using Tapatalk

Just got it here too ..

Anyway original Shield users (Y01) can install this update?

I unrooted and restored stock recovery to get the installation process going (same procedure as always), but unfortunately, I always end up getting the "Error!" message after a while, thus having to manually turn off the system. I didn't have any issue like this with Update 1.1, and I can't really think of any substantial change to my system since then.
Anyone got any tips?

This update seems to have broken loading OBB zips from the external SD.

Ralek85 said:
I unrooted and restored stock recovery to get the installation process going (same procedure as always), but unfortunately, I always end up getting the "Error!" message after a while, thus having to manually turn off the system. I didn't have any issue like this with Update 1.1, and I can't really think of any substantial change to my system since then.
Anyone got any tips?
Click to expand...
Click to collapse
I got the same message.
I could press the Power button and the volume-up button once to get into recovery and it shows me:
Verifying current system...
"EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:6699412:2dedcfe2f04<very large hex>" has unexpected contents.
E:Error in @/cache/recovery/block.map
(Status 7)
Installation aborted.
After this I also fastboot flashed the boot.img matching the recovery.img and got a different message:
system partition has unexpected contents
This leads me to believe the boot.img, recovery.img and system.img (and maybe the blob) should come from the same release, in my case I downloaded the 1.1.1 release from Nvidia. I don't have time to keep testing this, but will do tomorrow.
UPDATE: I flashed the system.img of the 1.1 update and then the update to 1.2 is successful.

Hi!
techboydino said:
Repositioned Navigation Buttons in Landscape mode
Click to expand...
Click to collapse
Can someone please post a screen shot of what that looks like? There are several complaints about it over at the nvidia forum but no one has described exactly what's bad with the new button position.
If they made it the same as phones where the bar is placed along the right (short) edge in landscape I'm gonna avoid this update like the plague, as a Lefty I hate that.
/lakris

They're more useful when you're holding the tablet with two hands.

DR_HAX34 said:
They're more useful when you're holding the tablet with two hands.
Click to expand...
Click to collapse
Thanks! Looks like I can live with that change.
/lakris

Any guide on Installing this for TWRP users? I would really appreciate that

+1 for a K1 already rooted on android 6.0

philipp21897 said:
Any guide on Installing this for TWRP users? I would really appreciate that
Click to expand...
Click to collapse
Kasimodo said:
+1 for a K1 already rooted on android 6.0
Click to expand...
Click to collapse
Hi!
I was on vulkan 6.0.1 (dev preview) and kali kernel etc, with TWRP 3.0.0 and Supersu installed, I've only downloaded it from Settings Update( v1.2 I'm on K1 w/o pen) and after that reflashed TWRP's recovery from fastboot and then SuperSu in TWRP's menu (also xposed installer must be reflashed or custom kernel and all other stuff that doesn't survive to OTA)

SHIELD Tablet K1 Software Upgrade 1.2 - FULL |6.0.1 - Release Notes
Full OTA:
productionBL-droid-signed-sb_na_wf-full_ota-40827_689.9034.20160411091106.zip

thank you Zarish.
But how to install it?
FYI, my tablet K1 is updated to 1.1 (Android 6.0) and rooted but I haven't installed TWRP Recovery. I have only boot on TWRP image (with command "fastboot boot twrp.img") and then flashed SuperSu.
Do I have to boot on TWRP with the same command (fastboot boot twrp.img) and then install the "OTA 1.2.zip" you shared?
Sorry for this noob question but I would like t be sure before starting something...
Best regards

Beyond castrwilliam, had anyone run unto issues with this update?

I have made SD card as internal storage can I download update as usual ?

Kasimodo said:
thank you Zarish.
But how to install it?
FYI, my tablet K1 is updated to 1.1 (Android 6.0) and rooted but I haven't installed TWRP Recovery. I have only boot on TWRP image (with command "fastboot boot twrp.img") and then flashed SuperSu.
Do I have to boot on TWRP with the same command (fastboot boot twrp.img) and then install the "OTA 1.2.zip" you shared?
Sorry for this noob question but I would like t be sure before starting something...
Best regards
Click to expand...
Click to collapse
Yes, you could boot TWRP that way and then install the .zip (install SU again also).

DR_HAX34 said:
They're more useful when you're holding the tablet with two hands.
Click to expand...
Click to collapse
Can we use gravitybox to swap the back and recent apps button?

NinjaCoool said:
Can we use gravitybox to swap the back and recent apps button?
Click to expand...
Click to collapse
Don't know. I'm not an Xposed fan, I think it spends way too much battery and causes errors that shouldn't happen to some apps.

Nvidia Shield TV Pro 2015 stuck at nvidia logo / any OTA public*.zip file available?

Hi all,
My Shield TV Pro 2015 unit is stuck at the nvidia logo although I can get to bootloader via hardware method and even fastboot boot twrp. I have followed all nvidia recover tutorials with several versions of Recovery OS image, but nothing seems to work.
From all (the many) threads I have read, it seems that it is possible to "unbrick" the unit by flashing an OTA update public*.zip with twrp. This is the only method I have not tried because I cannot find an appropriate version for 2015 PRO version.
There are some versions online (privately uploaded), but refer to other models like here and here and here.
Have I missed the file somehow or is there anyone that could share this version? Even maybe someone that could share your ideas on how to unblock the unit?
Many thanks in advance for all the possible help,
Carlos

Hello again
I just want to update my own post and at the same time again ask for some help.
So far nobody has stepped forward with a PUBLIC*.zip file download link for the Shield 2015 PRO model (codename foster just like the 2015 16GB model - +1 for confusion master to Nvidia on model release naming) but... I found a hosted file today (it has been freshly uploaded on the 12th/06)) on androidfilehost.com named PUBLIC604eab3c209a3f6146de7e1b8b1ff6c3_foster_e.zip posted by a user named linux4all.
It might be the one... or not. Is there a guru that could point to a file inside these OTA PUBLIC*.zip files that might have some more detailed info about the version that it was built for? The best I could get was this text inside the updater-script:
Code:
getprop("ro.product.device") == "foster" || abort("E3004: This package is for \"foster\" devices; this is a \"" + getprop("ro.product.device") + "\".");
ui_print("Target: NVIDIA/foster_e/foster:8.0.0/OPR6.170623.010/3019194_1155.5338:user/release-keys");
No doubt it's for a Foster device, but which one?
Anyone out there (that means you too "linux4all") that could add a bit more info to my already too long babble?
Thanks in advance!

guardiman said:
Have I missed the file somehow or is there anyone that could share this version? Even maybe someone that could share your ideas on how to unblock the unit?
Click to expand...
Click to collapse
If I understand you correctly you have access to fastboot.
Then why not just register with the Nvidia developer program and download from there:
https://developer.nvidia.com/gameworksdownload
There you can pick any version you'd like to install, they've even got the new 7.0.1 developer images. That would be pre-rooted developer images, but if you install something like 6.0 you can then just follow the normal OTA upgrade path after that.

andersh said:
If I understand you correctly you have access to fastboot.
Then why not just register with the Nvidia developer program and download from there:
https://developer.nvidia.com/gameworksdownload
There you can pick any version you'd like to install, they've even got the new 7.0.1 developer images. That would be pre-rooted developer images, but if you install something like 6.0 you can then just follow the normal OTA upgrade path after that.
Click to expand...
Click to collapse
+1. You can just download a rooted image. Takes just a few minutes to register as a developer.

dk1keith said:
+1. You can just download a rooted image. Takes just a few minutes to register as a developer.
Click to expand...
Click to collapse
Thanks for your help and suggestions.
As I had previously described, I already tried all of this before. I am registered as a developer, I downloaded all the images (recoveryOS and developerOS) for my model (Nvidia Shield 2015 Pro), I followed the restore procedure using fastboot method, the console outputs OKs all the way through the restore procedure and at the end (I understand that it means it has succeeded restoring) but when I reboot the unit nothing has changed (still green nvidia logo, still stuck).
So, as an alternative, I want to try and use the TWRP method that seems to have worked at unblocking units stuck like mine, check this post by pendragon666 https://forum.xda-developers.com/showpost.php?p=72655717&postcount=3.
But this method requires the OTA zip (they are not available for download from nvidia - if I'm wrong, please, link me to my blindness )
Why is it that TWRP only works with OTA zips? I don't know. But from comparing the two zip files, recoveryOS zip and OTA PUBLIC*.zip, the former is like a small number of image files, plus some scripts but no subfolders (if you download the zip from nvidia and open it you can confirm this), whereas the latter his a zip with many subfolders and files than can be read and applied by TWRP as a zip install.
If I can get to confirm that this OTA PUBLIC.*zip file is for my unit (foster pro) I will try to install it with TWRP and see if it works.
I hope it is clearer now.

andersh said:
If I understand you correctly you have access to fastboot.
Then why not just register with the Nvidia developer program and download from there:
https://developer.nvidia.com/gameworksdownload
There you can pick any version you'd like to install, they've even got the new 7.0.1 developer images. That would be pre-rooted developer images, but if you install something like 6.0 you can then just follow the normal OTA upgrade path after that.
Click to expand...
Click to collapse
Yes, I do. Already did download all images but the process produces zero effect, although it finishes successfully. I tried every single recoveryOS and developerOS image but nothing worked...

guardiman said:
Yes, I do. Already did download all images but the process produces zero effect, although it finishes successfully. I tried every single recoveryOS and developerOS image but nothing worked...
Click to expand...
Click to collapse
Just to add a bit more info I digged from the recovery.log after flashbooting twrp on my Shield Pro 2015:
Code:
ro.build.fingerprint=NVIDIA/foster_e_hdd/foster:7.0/NRD90M/1915764_910.7870:user/release-keys
ro.product.name=foster_e_hdd
ro.product.brand=NVIDIA
ro.product.model=SHIELD Android TV
ro.product.device=foster
ro.product.manufacturer=NVIDIA
ro.hardware=foster_e_hdd
In the OTA zip I saw no reference to "foster_e_hdd" and this might proof of mismatch... or not

guardiman said:
Hi all,
My Shield TV Pro 2015 unit is stuck at the nvidia logo although I can get to bootloader via hardware method and even fastboot boot twrp. I have followed all nvidia recover tutorials with several versions of Recovery OS image, but nothing seems to work.
From all (the many) threads I have read, it seems that it is possible to "unbrick" the unit by flashing an OTA update public*.zip with twrp. This is the only method I have not tried because I cannot find an appropriate version for 2015 PRO version.
There are some versions online (privately uploaded), but refer to other models like here and here and here.
Have I missed the file somehow or is there anyone that could share this version? Even maybe someone that could share your ideas on how to unblock the unit?
Many thanks in advance for all the possible help,
Carlos
Click to expand...
Click to collapse
I wanted to downgrade from 7.01 to 6.3. I flashed 6.3 developer image pro via flashfire, flash went well but then when rebooted stuck at splash screen. Plugged in laptop and went back to bootloader hit factory reset and 3 hours later all went well

jionny said:
I wanted to downgrade from 7.01 to 6.3. I flashed 6.3 developer image pro via flashfire, flash went well but then when rebooted stuck at splash screen. Plugged in laptop and went back to bootloader hit factory reset and 3 hours later all went well
Click to expand...
Click to collapse
You mean factory reset inside TWRP or nvidia recovery?

guardiman said:
You mean factory reset inside TWRP or nvidia recovery?
Click to expand...
Click to collapse
inside nvidia shield recovery

jionny said:
inside nvidia shield recovery
Click to expand...
Click to collapse
you mean "force recovery" (last option at the bottom)? There is no factory reset in my nvidia recovery menus (chosing recovery gives a "no command" output and force recovery makes the screen go blank until you unplug it from power.

guardiman said:
you mean "force recovery" (last option at the bottom)? There is no factory reset in my nvidia recovery menus (chosing recovery gives a "no command" output and force recovery makes the screen go blank until you unplug it from power.
Click to expand...
Click to collapse
no not force recovery.... follow these directions http://nvidia.custhelp.com/app/answ...hen-you-are-unable-to-access-android-settings

jionny said:
no not force recovery.... follow these directions http://nvidia.custhelp.com/app/answ...hen-you-are-unable-to-access-android-settings
Click to expand...
Click to collapse
Unfortunately the "boot recovery" option after selected just ends with a black screen and a "no command" message written in white letters in the middle of the screen (no dead android robot)
I got here:
8. You may see the dead Android robot on screen. This is expected behavior.
But no robot

guardiman said:
Unfortunately the "boot recovery" option after selected just ends with a black screen and a "no command" message written in white letters in the middle of the screen (no dead android robot)
Click to expand...
Click to collapse
that is normal just keep trying I had to go through it at last 3-4 times before it took, as long as it says no command follow the instructions

jionny said:
that is normal just keep trying I had to go through it at last 3-4 times before it took, as long as it says no command follow the instructions
Click to expand...
Click to collapse
Managed further to the menu (it was just of question of proper pressing and seconds) let's see what comes now...
Wiping data...

guardiman said:
Managed further to the menu let's see what comes
Wiping...
Click to expand...
Click to collapse
be patient it takes about 3 hours

jionny said:
be patient it takes about 3 hours
Click to expand...
Click to collapse
finally some progress after weeks of waiting... 3 hours is just around the corner
a certainly well deserved thanks for you, sir

guardiman said:
finally some progress after weeks of waiting... 3 hours is just around the corner
a certainly well deserved thanks for you, sir
Click to expand...
Click to collapse
You are welcome, glad I could help.

jionny said:
You are welcome, glad I could help.
Click to expand...
Click to collapse
Well, wipe finished, reboot and.... nvidia logo (same ol' same)
I forgot to say that I had already performed the "fastboot oem unlock" which is said to factory reset the shield. Although the unlock finished successfully the Shield did not boot.
Back to the drawing board....
Any more suggestions? Anyone?

guardiman said:
Well, wipe finished, reboot and.... nvidia logo (same ol' same)
I forgot to say that I had already performed the "fastboot oem unlock" which is said to factory reset the shield. Although the unlock finished successfully the Shield did not boot.
Back to the drawing board....
Any more suggestions? Anyone?
Click to expand...
Click to collapse
What version are you on and did you flash anything and then get stuck on the logo screen?

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.

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/