Database Users

[Solved] Stuckup on fastboot

C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot reboot-bootlo
ader
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.021s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash bootloa
der bootloader-grouper-4.13.img
sending 'bootloader' (2096 KB)...
OKAY [ 0.408s]
writing 'bootloader'...
OKAY [ 1.267s]
finished. total time: 1.679s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot -w update ima
ge-nakasi-jop40d.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.13
Baseband Version.....: N/A
Serial Number........: 015###***##f80a
--------------------------------------------
checking product...
OKAY [ 0.030s]
checking version-bootloader...
OKAY [ 0.017s]
sending 'boot' (4942 KB)...
OKAY [ 1.058s]
writing 'boot'...
OKAY [ 0.332s]
sending 'recovery' (5444 KB)...
OKAY [ 1.144s]
writing 'recovery'...
OKAY [ 0.335s]
erasing 'system'...
OKAY [ 0.125s]
sending 'system' (477136 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 107.320s
Please some one help.... I already deleted boot,cache,recovery,system, user data... Now My device not stating... it just open till bootloader

Usually you would boot into the new bootloader after having flashed a new one in place, and then continue (your steps #1 and #2 are reversed).
But, I'm not sure that is the cause of the problem here, and I wouldn't keep flashing the bootloader over and over when no errors are given, as a bootloader flash is the single most dangerous thing you can do. Just make sure you restart the tab.
Whenever you see a communications failure you should try a different cable or a different USB port on your PC. Communication failures are most likely with the system image simply because it is the largest - there are more opportunity for errors. FWIW, poor quality or damaged cables are the most likely cause of USB data transfer problems.
It could be some other problem with the tab, but those are two easy things to try.
good luck

Try using the flash-all.bat in the factory image.
Actually the only difference is in the wait of 10 seconds between reboot and -w update.
Give it i try.:fingers-crossed:
bye

Problem Solved... Problem with my usb Port....
Thanks bftb0

hirenvasani said:
Problem Solved... Problem with my usb Port....
Thanks bftb0
Click to expand...
Click to collapse
Good news! Glad something I said helped.
Please edit your thread title to include the token "[SOLVED]" - that might help others or let them skip over.
enjoy your tablet - it is a fantastic little device.

[Request]Stock 4.1.2 Firware for Aus xt905

Recently I attempted to flash a custom rom after root and unlocking my bootloader on my Australia xt905. Unfortunately I made the rookie mistake no backup stock rom to fallback on. After a frustrating soft brick I finally got it on but now its running on xt907 firmware. Best I could do. In an effort to get some functionality back I have tried custom roms which have worked and am currently runnning the xt907 carbon rom on 4.2.2 But still cannot get the cellular to work. I have looked for a stock 4.1.2 but am unable to find it anywhere. Is there anyone that has a copy?

TheSpecificOcean said:
Recently I attempted to flash a custom rom after root and unlocking my bootloader on my Australia xt905. Unfortunately I made the rookie mistake no backup stock rom to fallback on. After a frustrating soft brick I finally got it on but now its running on xt907 firmware. Best I could do. In an effort to get some functionality back I have tried custom roms which have worked and am currently runnning the xt907 carbon rom on 4.2.2 But still cannot get the cellular to work. I have looked for a stock 4.1.2 but am unable to find it anywhere. Is there anyone that has a copy?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2169220&highlight=xt905

aviwdoowks said:
http://forum.xda-developers.com/showthread.php?t=2169220&highlight=xt905
Click to expand...
Click to collapse
Yes I have this file now thanks but am having trouble flashing installation is aborted error in cwm whenever I try

TheSpecificOcean said:
Yes I have this file now thanks but am having trouble flashing installation is aborted error in cwm whenever I try
Click to expand...
Click to collapse
Post all the details!!
---------- Post added at 04:57 PM ---------- Previous post was at 04:54 PM ----------
Use this http://forum.xda-developers.com/showthread.php?t=2246081
The original not my vzw workaround.

aviwdoowks said:
Post all the details!!
Click to expand...
Click to collapse
After clearing cache and dalvik cache then factory reset i run the retail version of the zip from the link earlier using cwm recovery and it says
installing 9.8.2Q_SMUIRD-7_SEMEAUnlk_USAXT90501TLSTRAE1019.0R_SMJBLTEAURETAIL_P008_A014_1FF_fb.xml.zip
finding update package...
opening update package...
installing update...
installation aborted...
And thats it nothing else comes up. I wanting to try using rds lite 6.1.4 but my device is refusing to show up and i have all the neccessary drivers.

TheSpecificOcean said:
After clearing cache and dalvik cache then factory reset i run the retail version of the zip from the link earlier using cwm recovery and it says
installing 9.8.2Q_SMUIRD-7_SEMEAUnlk_USAXT90501TLSTRAE1019.0R_SMJBLTEAURETAIL_P008_A014_1FF_fb.xml.zip
finding update package...
opening update package...
installing update...
installation aborted...
And thats it nothing else comes up. I wanting to try using rds lite 6.1.4 but my device is refusing to show up and i have all the neccessary drivers.
Click to expand...
Click to collapse
The xml needs rsd. What is your computer?
Mac needs parallels desktop.
Try ap fastboot mode from the bootloader screen.

aviwdoowks said:
The xml needs rsd. What is your computer?
Mac needs parallels desktop.
Try ap fastboot mode from the bootloader screen.
Click to expand...
Click to collapse
I'm running a custom built PC running win 8 pro build 9600 and I'll try this when I get back currently away for Christmas holidays.

TheSpecificOcean said:
I'm running a custom built PC running win 8 pro build 9600 and I'll try this when I get back currently away for Christmas holidays.
Click to expand...
Click to collapse
Get rsd 615.

aviwdoowks said:
Get rsd 615.
Click to expand...
Click to collapse
Couldn't get rdslite 6.1.5 to show device either but did manage to get the fastboot.bat to work. Unfortunately this failed as well was getting variable not supported errors above each stage and then would get fastboot.exe has stopped working errors mid flash but the command would continue after closing program. Have been reading that win 8 may be the cause of this will try on a win xp computer and if i can get my hands on a win7 if that doesn't work

TheSpecificOcean said:
Couldn't get rdslite 6.1.5 to show device either but did manage to get the fastboot.bat to work. Unfortunately this failed as well was getting variable not supported errors above each stage and then would get fastboot.exe has stopped working errors mid flash but the command would continue after closing program. Have been reading that win 8 may be the cause of this will try on a win xp computer and if i can get my hands on a win7 if that doesn't work
Click to expand...
Click to collapse
I use w7.

aviwdoowks said:
I use w7.
Click to expand...
Click to collapse
just tried xp was a no go but am going away again tomorrow till the 5/1. Will try again then got it back to the stock xt907 firmware. I guess that will have to do for now. Is there any xt905 compatible roms by any chance. I have managed to get both the carbon xt907 and unofficial xt905 of akop but neither were getting reception or less than one bar on the odd occasion. Would a gsm fix this? As i have been unable to get my hands on one every link seems to be broken

TheSpecificOcean said:
just tried xp was a no go but am going away again tomorrow till the 5/1. Will try again then got it back to the stock xt907 firmware. I guess that will have to do for now. Is there any xt905 compatible roms by any chance. I have managed to get both the carbon xt907 and unofficial xt905 of akop but neither were getting reception or less than one bar on the odd occasion. Would a gsm fix this? As i have been unable to get my hands on one every link seems to be broken
Click to expand...
Click to collapse
Did you try this http://forum.xda-developers.com/showthread.php?t=2246081
St.Noigel knows a lot about gsm.

aviwdoowks said:
Did you try this http://forum.xda-developers.com/showthread.php?t=2246081
St.Noigel knows a lot about gsm.
Click to expand...
Click to collapse
no i haven't i am going to try the ose 4.3 with a 4.3 gsm fix and if that fails i will try that one it will respond with results maybe if i have time
EDIT: OSE didn't work gonna try the link u posted
Edit: Finally got the rom u posted above to work but no improvement the service didnt improve however i noticed i was unable to select any other band types from the mobile networks menu

I'm a bit off topic after all this but what i'm effectively looking for is a backup that can be flashed via CWM or installed via zip. I cannot for the life of me get fastboot or rdslite to work. The files from the http://forum.xda-developers.com/show...ighlight=xt905 are all fastboot files and can't be installed by CWM from zip. Or alternatively a working xt905 rom because at the moment all unofficial or official versions with gsm fixes are unable to find any cellular in Australia. I'm currently with Telstra through ALDImobile at the moment if it helps, not looking for lte just h+ or 3g if possible. At the moment i'm stuck with a glorified mp3 player.

I thought i might post the log from the fastboot attempts when im using the fastboot that comes with the retail stock firmware. I noticed some that looked out of place and have searched them but found nothing that helped main culprits being
(bootloader) Variable not supported!
(bootloader) Preflash validation failed
Invalid sparse file format at header magi
Code:
Flashing bootloader images ...
So as to use latest flash capabilities
< waiting for device >
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'partition' (32 KB)...
OKAY [ 0.012s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 0.284s
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'sbl1' (101 KB)...
OKAY [ 0.018s]
writing 'sbl1'...
OKAY [ 0.559s]
finished. total time: 0.578s
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'sbl2' (126 KB)...
OKAY [ 0.019s]
writing 'sbl2'...
OKAY [ 0.929s]
finished. total time: 0.948s
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'sbl3' (512 KB)...
OKAY [ 0.049s]
writing 'sbl3'...
OKAY [ 1.111s]
finished. total time: 1.160s
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'rpm' (140 KB)...
OKAY [ 0.017s]
writing 'rpm'...
OKAY [ 0.552s]
finished. total time: 0.570s
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'tz' (192 KB)...
OKAY [ 0.023s]
writing 'tz'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.319s
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'aboot' (256 KB)...
OKAY [ 0.025s]
writing 'aboot'...
OKAY [ 0.827s]
finished. total time: 0.853s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.008s
Flashing modem SW...
error: < waiting for device >
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'fsg' (2825 KB)...
OKAY [ 0.221s]
writing 'fsg'...
OKAY [ 1.169s]
finished. total time: 1.391s
(bootloader) Variable not supported!
erasing 'modemst1'...
OKAY [ 0.617s]
finished. total time: 0.618s
(bootloader) Variable not supported!
erasing 'modemst2'...
OKAY [ 0.613s]
finished. total time: 0.613s
Flashing AP Images...
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'logo' (854 KB)...
OKAY [ 0.071s]
writing 'logo'...
OKAY [ 1.120s]
finished. total time: 1.190s
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'devtree' (512 KB)...
OKAY [ 0.047s]
writing 'devtree'...
OKAY [ 0.348s]
finished. total time: 0.395s
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.789s]
writing 'boot'...
OKAY [ 2.806s]
finished. total time: 3.595s
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.790s]
writing 'recovery'...
OKAY [ 2.002s]
finished. total time: 2.794s
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
Invalid sparse file format at header magi
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
Invalid sparse file format at header magi
(bootloader) Variable not supported!
erasing 'tombstones'...
OKAY [ 0.801s]
finished. total time: 0.801s
(bootloader) Variable not supported!
erasing 'cache'...
OKAY [ 1.045s]
finished. total time: 1.045s
Erasing userdata...
(bootloader) Variable not supported!
erasing 'userdata'...
OKAY [ 4.423s]
finished. total time: 4.423s
All images flashed. Check logs for errors!
Press any key to continue . . .

http://forum.xda-developers.com/showthread.php?t=2169220&page=2 just found this which solves half my problem any ideas on getting rdslite to work is it a win 8 issue maybe

FIXED i finally got it to flash using fastboot. The errors were occuring because there wasn't a fastboot.exe in the files with the firmware. I read on another post that they needed to copy a fastboot across. After trying this it fixed.

TheSpecificOcean said:
FIXED i finally got it to flash using fastboot. The errors were occuring because there wasn't a fastboot.exe in the files with the firmware. I read on another post that they needed to copy a fastboot across. After trying this it fixed.
Click to expand...
Click to collapse
Would you post a screen shot of the bottom half of your about phone page?

aviwdoowks said:
Would you post a screen shot of the bottom half of your about phone page?
Click to expand...
Click to collapse
yeah sure

[Q] Installing a factory image of 4.4 with a mac

hi can someone please help me. i am unrooted but unlocked i am trying desperately but when i try to run flash-all.sh it says it is not found. somewhere on the internet it said i should open that file in a text editor and place a ./ in front of every fastboot command. i tried that but still no luck

Feedback
robe5pierre said:
hi can someone please help me. i am unrooted but unlocked i am trying desperately but when i try to run flash-all.sh it says it is not found. somewhere on the internet it said i should open that file in a text editor and place a ./ in front of every fastboot command. i tried that but still no luck
Click to expand...
Click to collapse
make sure the file is executable try this open terminal at the directory the flash-all.sh is located and type
Code:
chmod +x flash-all.sh
this should make it executable than try to run the command
Code:
flash-all.sh
let me know if this helps.....Thx lj

lj50036 said:
What is the OS of your PC??
Click to expand...
Click to collapse
Osx 10.6.8

fastboot
robe5pierre said:
Osx 10.6.8
Click to expand...
Click to collapse
How did you install fastboot??

lj50036 said:
How did you install fastboot??
Click to expand...
Click to collapse
im trying to do everything all over again from scratch. can you recommend a thorough walkthrough? I had followed instructions from here: http://www.androidbeat.com/2013/11/flash-factory-image-nexus-device/ and picked up some other pointers elsewhere (like including not only ./ but ./fastboot-mac before any command)

fastboot/adb
robe5pierre said:
im trying to do everything all over again from scratch. can you recommend a thorough walkthrough? I had followed instructions from here: http://www.androidbeat.com/2013/11/flash-factory-image-nexus-device/ and picked up some other pointers elsewhere (like including not only ./ but ./fastboot-mac before any command)
Click to expand...
Click to collapse
Check this out for a very easy way to install fastboot/adb correctly
http://forum.xda-developers.com/showthread.php?t=2638673

lj50036 said:
Check this out for a very easy way to install fastboot/adb correctly
http://forum.xda-developers.com/showthread.php?t=2638673
Click to expand...
Click to collapse
thanks, when i run the script it asks me for the sudo password. what is this?

sudo
robe5pierre said:
thanks, when i run the script it asks me for the sudo password. what is this?
Click to expand...
Click to collapse
It means super user do... Take a look here http://support.apple.com/kb/ht4103

lj50036 said:
Check this out for a very easy way to install fastboot/adb correctly
http://forum.xda-developers.com/showthread.php?t=2638673
Click to expand...
Click to collapse
thanks! i installed fastboot your way, but when i tried to run ./flash-all.sh this is what was returned:
erasing 'boot'...
OKAY [ 0.032s]
finished. total time: 0.032s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.104s]
finished. total time: 0.104s
erasing 'recovery'...
OKAY [ 0.028s]
finished. total time: 0.028s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.445s]
finished. total time: 0.446s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.369s]
finished. total time: 0.369s
error: cannot open 'bootloader-manta-mantamf01.img'
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
ERROR: could not get pipe properties
< waiting for device >
error: failed to load 'image-mantaray-kot49h.zip': No such file or directory
any ideas?

robe5pierre said:
thanks! i installed fastboot your way, but when i tried to run ./flash-all.sh this is what was returned:
erasing 'boot'...
OKAY [ 0.032s]
finished. total time: 0.032s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.104s]
finished. total time: 0.104s
erasing 'recovery'...
OKAY [ 0.028s]
finished. total time: 0.028s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.445s]
finished. total time: 0.446s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.369s]
finished. total time: 0.369s
error: cannot open 'bootloader-manta-mantamf01.img'
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
ERROR: could not get pipe properties
< waiting for device >
error: failed to load 'image-mantaray-kot49h.zip': No such file or directory
any ideas?
Click to expand...
Click to collapse
Did you get the file from here???
https://developers.google.com/android/nexus/images

lj50036 said:
Did you get the file form here???
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
yes i did. i will try again fresh. i unpack it into a folder on my desktop and run the flash-all.sh like this: Users/myname/Desktop/myfolder/./flash-all.sh is that correct?

feedback
robe5pierre said:
yes i did. i will try again fresh. i unpack it into a folder on my desktop and run the flash-all.sh like this: Users/myname/Desktop/myfolder/./flash-all.sh is that correct?
Click to expand...
Click to collapse
Yes run all the command from the directory that contains flash-all.sh
It should aslo contain the bootloader and the zip folder

lj50036 said:
Yes run all the command from the directory that contains flash-all.sh
It should aslo contain the bootloader and the zip folder
Click to expand...
Click to collapse
i did it again and got the same result

paste
robe5pierre said:
i did it again and got the same result
Click to expand...
Click to collapse
Paste the input command include the command prompt line and the command you ran
Your bootloader is unlocked yes??
Im going to do the process on my nexus 10.. Give me a minute im downloader the factory image now....

lj50036 said:
Paste the input command include the command prompt line and the command you ran
Your bootloader is unlocked yes??
Click to expand...
Click to collapse
i think you are saying to paste it here so you can see... so here it is: /Users/myname/Desktop/new/./flash-all.sh
'myname' is my gf's name whose mac i am using. 'new' is the folder i made on the desktop with the kot49h files in it
yes i am unlocked

when i ran the script you gave me to install fastboot. the last thing it says is 'type adb or fastboot to run' it is at this point that i typed the above command. should i instead first type adb or fastboot?

after uninstalling and reinstalling fastboot with the link you provided me, then deleting and redownloading kot49h, unpacking it, unpacking the subsequent zip file that was produced and putting all the files in the same folder called 'new' on my desktop, then running the command i showed you, this is what i am getting:
error: cannot open 'bootloader-deb-flo-04.02.img'
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
< waiting for device >
error: cannot open 'radio-deb-deb-g00_2.37.0_1024.img'
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
< waiting for device >
error: failed to load 'image-razorg-kot49h.zip': No such file or directory

and now it appears i am stuck in bootloader mode. this is a new development

Feedback
robe5pierre said:
i think you are saying to paste it here so you can see... so here it is: /Users/myname/Desktop/new/./flash-all.sh
'myname' is my gf's name whose mac i am using. 'new' is the folder i made on the desktop with the kot49h files in it
yes i am unlocked
Click to expand...
Click to collapse
so open a new terminal window and instead of telling where the file is let move to that directory.....Here is what it would look like on my PC it is Linux but it will be almost the same
when i open my termail this is what I see without any input from me
Code:
[email protected] ~ $
Now lets move to the directory that contains the flash-all.sh.... we will just say that it is in Downloads/mantaray-kot49h thats the path to my sh file
we will type in the terminal
Code:
cd Downloads/mantaray-kot49h
Than my command line will change to this
Code:
[email protected] ~/Downloads/mantaray-kot49h $
Than to verify all the files that are needed to be used in the process are there we can run a
Code:
ls
Code:
[email protected] ~/Downloads/mantaray-kot49h $ ls
bootloader-manta-mantamf01.img flash-all.bat flash-all.sh flash-base.sh image-mantaray-kot49h.zip
There are all the files I need to flash the stock image
let go ahead and I will do that to show you the whole thing...
Code:
./flash-all.sh
Code:
[email protected] ~/Downloads/mantaray-kot49h $ ./flash-all.sh
erasing 'boot'...
OKAY [ 0.029s]
finished. total time: 0.029s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.103s]
finished. total time: 0.103s
erasing 'recovery'...
OKAY [ 0.029s]
finished. total time: 0.029s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.378s]
finished. total time: 0.378s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.435s]
finished. total time: 0.435s
sending 'bootloader' (1280 KB)...
OKAY [ 0.161s]
writing 'bootloader'...
OKAY [ 0.193s]
finished. total time: 0.354s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTAMF01
Baseband Version.....: no modem
Serial Number........: R32D1040PSW
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.001s]
sending 'boot' (4784 KB)...
OKAY [ 0.606s]
writing 'boot'...
OKAY [ 0.120s]
sending 'recovery' (5334 KB)...
OKAY [ 0.678s]
writing 'recovery'...
OKAY [ 0.123s]
erasing 'system'...
OKAY [ 0.152s]
sending 'system' (647286 KB)...
OKAY [ 81.942s]
writing 'system'...
OKAY [ 16.038s]
erasing 'userdata'...
OKAY [ 0.374s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 29783752704
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7271424
Block groups: 222
Reserved block group size: 1024
Created filesystem with 11/1818624 inodes and 158176/7271424 blocks
sending 'userdata' (139141 KB)...
writing 'userdata'...
OKAY [ 29.138s]
erasing 'cache'...
OKAY [ 0.094s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 553648128
Block size: 4096
Blocks per group: 32768
Inodes per group: 6768
Inode size: 256
Journal blocks: 2112
Label:
Blocks: 135168
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/33840 inodes and 4363/135168 blocks
sending 'cache' (10372 KB)...
writing 'cache'...
OKAY [ 1.603s]
rebooting...
finished. total time: 130.879s
---------- Post added at 10:56 AM ---------- Previous post was at 10:48 AM ----------
If that still will not work for you I would get a new image from the nexus site.....
---------- Post added at 10:59 AM ---------- Previous post was at 10:56 AM ----------
robe5pierre said:
after uninstalling and reinstalling fastboot with the link you provided me, then deleting and redownloading kot49h, unpacking it, unpacking the subsequent zip file that was produced and putting all the files in the same folder called 'new' on my desktop, then running the command i showed you, this is what i am getting:
error: cannot open 'bootloader-deb-flo-04.02.img'
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
< waiting for device >
error: cannot open 'radio-deb-deb-g00_2.37.0_1024.img'
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
< waiting for device >
error: failed to load 'image-razorg-kot49h.zip': No such file or directory
Click to expand...
Click to collapse
It looks like you don't have the right file for the nexus 10?? Make sure you get the mantaray!! If thas what your working with
---------- Post added at 11:03 AM ---------- Previous post was at 10:59 AM ----------
robe5pierre said:
and now it appears i am stuck in bootloader mode. this is a new development
Click to expand...
Click to collapse
For sure you dont have a ROM installed now you started the process and it erased all your data.....

lj50036 said:
so open a new terminal window and instead of telling where the file is let move to that directory.....Here is what it would look like on my PC it is Linux but it will be almost the same
when i open my termail this is what I see without any input from me
Code:
[email protected] ~ $
Now lets move to the directory that contains the flash-all.sh.... we will just say that it is in Downloads/mantaray-kot49h thats the path to my sh file
we will type in the terminal
Code:
cd Downloads/mantaray-kot49h
Than my command line will change to this
Code:
[email protected] ~/Downloads/mantaray-kot49h $
Than to verify all the files that are needed to be used in the process are there we can run a
Code:
ls
Code:
[email protected] ~/Downloads/mantaray-kot49h $ ls
bootloader-manta-mantamf01.img flash-all.bat flash-all.sh flash-base.sh image-mantaray-kot49h.zip
There are all the files I need to flash the stock image
let go ahead and I will do that to show you the whole thing...
Code:
./flash-all.sh
Code:
[email protected] ~/Downloads/mantaray-kot49h $ ./flash-all.sh
erasing 'boot'...
OKAY [ 0.029s]
finished. total time: 0.029s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.103s]
finished. total time: 0.103s
erasing 'recovery'...
OKAY [ 0.029s]
finished. total time: 0.029s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.378s]
finished. total time: 0.378s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.435s]
finished. total time: 0.435s
sending 'bootloader' (1280 KB)...
OKAY [ 0.161s]
writing 'bootloader'...
OKAY [ 0.193s]
finished. total time: 0.354s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTAMF01
Baseband Version.....: no modem
Serial Number........: R32D1040PSW
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.001s]
sending 'boot' (4784 KB)...
OKAY [ 0.606s]
writing 'boot'...
OKAY [ 0.120s]
sending 'recovery' (5334 KB)...
OKAY [ 0.678s]
writing 'recovery'...
OKAY [ 0.123s]
erasing 'system'...
OKAY [ 0.152s]
sending 'system' (647286 KB)...
OKAY [ 81.942s]
writing 'system'...
OKAY [ 16.038s]
erasing 'userdata'...
OKAY [ 0.374s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 29783752704
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7271424
Block groups: 222
Reserved block group size: 1024
Created filesystem with 11/1818624 inodes and 158176/7271424 blocks
sending 'userdata' (139141 KB)...
writing 'userdata'...
OKAY [ 29.138s]
erasing 'cache'...
OKAY [ 0.094s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 553648128
Block size: 4096
Blocks per group: 32768
Inodes per group: 6768
Inode size: 256
Journal blocks: 2112
Label:
Blocks: 135168
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/33840 inodes and 4363/135168 blocks
sending 'cache' (10372 KB)...
writing 'cache'...
OKAY [ 1.603s]
rebooting...
finished. total time: 130.879s
---------- Post added at 10:56 AM ---------- Previous post was at 10:48 AM ----------
If that still will not work for you I would get a new image from the nexus site.....
---------- Post added at 10:59 AM ---------- Previous post was at 10:56 AM ----------
It looks like you don't have the right file for the nexus 10?? Make sure you get the mantaray!! If thas what your working with
---------- Post added at 11:03 AM ---------- Previous post was at 10:59 AM ----------
For sure you dont have a ROM installed now you started the process and it erased all your data.....
Click to expand...
Click to collapse
Seriously, thank you thank you thank you. Even though the 4.4.2 kot49h is listed under 'mantaray' and it is the file i was told by another administrator to use and he assured me there would be no problem going from 4.3 jwr66v directly to kot49h since it is a factory image, alas the problem was that i needed to use 4.4 krt16s. Doing this, and following everything else you told me, it worked like a charm. As soon as i booted up, i got the ota for 4.4.2 and installed that smoothly. Thank you sooo much @lj50036!
Now i guess i am going to root again just so i can have usb functionality with stickmount. Do you have any suggestions for a really good set of instructions for this? also, do i need to save this folder i created on my mac desktop??

Forgot fastboot set_active a command, (and other errors) now phone is bricked.amidun?

Here is the sequence of commands:
C:\Users\blah\Desktop\platform-tools>adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
PM1LHMA7blahblah unauthorized
C:\Users\blah\Desktop\platform-tools>adb devices
List of devices attached
PM1LHMA7blahblah device
C:\Users\blah\Desktop\platform-tools>adb reboot bootloader
C:\Users\blah\Desktop\platform-tools>fastboot devices
PM1LHMA7blahblah fastboot
C:\Users\blah\Desktop\platform-tools>fastboot getvar current-slot
current-slot: _a
Finished. Total time: 0.001s
C:\Users\blah\Desktop\platform-tools>fastboot flash vendor_a vendor-QQ1A.200105.088.img # OOPS i should have put b so i try to fix it in the next command
Sending 'vendor_a' (392296 KB) OKAY [ 9.211s]
Writing 'vendor_a' OKAY [ 2.446s]
Finished. Total time: 11.667s
C:\Users\blah\Desktop\platform-tools>fastboot flash vendor_b vendor-QQ1A.200105.088.img
Sending 'vendor_b' (392296 KB) OKAY [ 9.215s]
Writing 'vendor_b' OKAY [ 2.439s]
Finished. Total time: 11.661s
C:\Users\blah\Desktop\platform-tools>fastboot erase system_b
Erasing 'system_b' OKAY [104.577s]
Finished. Total time: 104.580s
C:\Users\blah\Desktop\platform-tools>fastboot flash system_b system.img
Invalid sparse file format at header magic
Sending sparse 'system_b' 1/6 (523151 KB) OKAY [ 12.365s]
Writing 'system_b' OKAY [ 3.943s]
Sending sparse 'system_b' 2/6 (520769 KB) OKAY [ 12.262s]
Writing 'system_b' OKAY [ 3.271s]
Sending sparse 'system_b' 3/6 (523599 KB) OKAY [ 12.327s]
Writing 'system_b' OKAY [ 3.311s]
Sending sparse 'system_b' 4/6 (522306 KB) OKAY [ 12.262s]
Writing 'system_b' OKAY [ 3.563s]
Sending sparse 'system_b' 5/6 (503327 KB) OKAY [ 11.967s]
Writing 'system_b' OKAY [ 8.774s]
Sending sparse 'system_b' 6/6 (42300 KB) OKAY [ 1.068s]
Writing 'system_b' OKAY [ 0.311s]
Finished. Total time: 87.248s
C:\Users\blah\Desktop\platform-tools>fastboot flash boot_b unsigned-new.img
fastboot: error: Couldn't parse partition size '0x'.
C:\Users\blah\Desktop\platform-tools>fastboot flash boot_a unsigned-new.img
fastboot: error: Couldn't parse partition size '0x'.
C:\Users\blah\Desktop\platform-tools>fastboot flash:raw boot_b unsigned-new.img
Sending 'boot_b' (23864 KB) OKAY [ 0.634s]
Writing 'boot_b' OKAY [ 0.298s]
Finished. Total time: 0.958s
##FORGET TO USE COMMAND fastboot set_active a
C:\Users\blah\Desktop\platform-tools>fastboot -w
Erasing 'userdata' OKAY [ 54.443s]
mke2fs 1.45.4 (23-Sep-2019)
Creating filesystem with 26768215 4k blocks and 6692864 inodes
Filesystem UUID: blah
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Allocating group tables: done
Writing inode tables: done
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'userdata' (544 KB) OKAY [ 0.100s]
Writing 'userdata' OKAY [ 0.018s]
Finished. Total time: 54.827s
Now when i restart the phone it just stays on the screen with the essential logo and powered by android at the bottom; never gets to spinning circles. When I restart i can pause it from booting because the bootloader is unlocked, but adb cant find it because to do that i have to give it debug permissions, but no OS to boot to so i cant do that. Did i brick my phone?

If you can still get into the bootloader, its fixable. Just reflash stock

vsn4 said:
If you can still get into the bootloader, its fixable. Just reflash stock
Click to expand...
Click to collapse
When I reboot, it says press power to pause (the screen where it says g.co/ABH), but then eventually proceeds to boot by itself after a few seconds.

noideawtf said:
When I reboot, it says press power to pause (the screen where it says g.co/ABH), but then eventually proceeds to boot by itself after a few seconds.
Click to expand...
Click to collapse
It boots back into the screen with the logo and phrase powered by android and sits there. After it dissipated its power all night doing that, I was able to get the bootloader screen to appear (The word start in big green letters) this morning, but i selected start and now that screen refuses to show up again, so ill try draining it again i guess?

I drained it of power and as soon as i plugged it into a charger it turned on by itself and went into the bootloader unlike it was doing before. Was able to issue the command I missed earlier and now it loads right up.

Onn 100005362 root and CFW help!

Hi all I’m kinda a newb to this scene but I’d like you get some info and possibly some help rooting it and building my own custom firmware.
I’d like to know exactly how to back the entire system up so I can try to possibly deplor it on an emulator etc. I’m interested in learning everything there is to know about android as well as how the systems are setup and how they run. I’ve done some modding in the past PSP Nook kindle fire etc but I’ve never gotten fully involved with the android os as I’d like to. Other then building and running automation scripts for software testing i lack the full knowledge on the os. I’m looking to learn as I said and possibly help build a root method and cfw for the onn 100003562. Thanks for any information and help in advanced.

Anyone out there?
Looking for some direction here. If anyone can point me in the right direction for this subject that would be great

Ok fellas lol I know I’m a newb but I would like some keen insight.
Is there any info out there for these Walmart tablets the 100005362? I was able to pull the bin directory with adb pull. Some how I bricked the first one I was attempting to modify so I went out and bought a new one as well as a 8 inch for my daughter. They are only 28 bucks Walmart special right now they call them gen 2 so I’m not sure if that is helpful at all. Anyway. I was thinking since what I was able to extract has some SeLinux folders with some type of commands, is there any way to modify them and inject them back in and some how initiate theme to run an a su installer? Or some kind of modification or even trick the damn thing to dump the images needed to root with magisk. I can’t seem to dump the .img files to make a stock backup nor can I seem to find where the ota update is downloaded and stored for install. I’ve been working on this and reading all of NSA software information about SeLinux and how it can controls pretty much most of the system above the uid. Now is it a possibility that one could modify the SeLinux files from bin and execute them in a way to grant the uid user superpermissions over everything including the SELinux. The more I’ve read the more suspicious I get on the whole NSA subject of SeLinux anyway and wonder why that type of govnmt made software is in public civilian hands but that’s a whole other subject. Anyway can somebody please advise me as to what can be done so I can back this up and modify for su. I don’t care what I have to do I want this thing as my test subject to build my own android rom. I’d like to build something a bit more secure and in a state that is anonymous to the web 100%. Like run the system under a Tor setup etc. I’m kinda one of those people who thinks everyone is watching and listening so I just prefer to build this myself or with like minded individuals. Again please any advise or any knowledge partaining to these devices and android 10 that can help me would be greatly appreciated thanks again.

backups
Pulling a back up is actually a well known process that seems to be the same for most mediatek devices. Here is the youtube tutorial I use to run backups but there are dozens to choose from:
https://www.youtube.com/watch?v=pj4iFakq33M
I have a section of my google drive I keep open with backups if you need to try a restore. I made a backup of the latest update from October but I forgot to upload it. At 100kbps it will be awhile before I can post it even if I had the chance to start the upload now. You should be able to do a full restore from any of these backups as long as you don't try to piecemeal it.
https://drive.google.com/drive/folders/1DGfI6u-OGaDJr_OkPOMmOKVxYCzrpp5k?usp=sharing
As far as root goes, magisk doesn't seem to have support for these particular tablets yet on my last attempt. Also be aware that these tablets have partitioning based on an android 10 system which means creating roms, kernels, TWRP, rooting and the like is totally different from android 9 and below. If you do follow through with trying to rom this tablet make sure any tutorials you look into pertain to devices that shipped with android 10 or above. I'll try to check back when I get a chance so let me know if you need help at least with the backups. Not sure I can offer help with much else at this point. I've been messing with android as a hobby since the og droid first came out but I haven't done much with devices based off this new system. Good luck.

will160628 said:
Pulling a back up is actually a well known process that seems to be the same for most mediatek devices. Here is the youtube tutorial I use to run backups but there are dozens to choose from:
https://www.youtube.com/watch?v=pj4iFakq33M
I have a section of my google drive I keep open with backups if you need to try a restore. I made a backup of the latest update from October but I forgot to upload it. At 100kbps it will be awhile before I can post it even if I had the chance to start the upload now. You should be able to do a full restore from any of these backups as long as you don't try to piecemeal it.
https://drive.google.com/drive/folders/1DGfI6u-OGaDJr_OkPOMmOKVxYCzrpp5k?usp=sharing
As far as root goes, magisk doesn't seem to have support for these particular tablets yet on my last attempt. Also be aware that these tablets have partitioning based on an android 10 system which means creating roms, kernels, TWRP, rooting and the like is totally different from android 9 and below. If you do follow through with trying to rom this tablet make sure any tutorials you look into pertain to devices that shipped with android 10 or above. I'll try to check back when I get a chance so let me know if you need help at least with the backups. Not sure I can offer help with much else at this point. I've been messing with android as a hobby since the og droid first came out but I haven't done much with devices based off this new system. Good luck.
Click to expand...
Click to collapse
thanks but i need the MT8768WA chipset.

Ok I'm finally able to report I have successfully Unbricked the Walmart ONN 100003562.
Using various bits of information scattered throughout the Walmart ONN general threads section so If anyone else runs into this issue i have the fix.
Step 1
Download both the FULL FACTORY firmware and the Update firmware from this awesome guys google drive. here's the link https://drive.google.com/drive/folde...5k?usp=sharing.
Starting with the Full stock flash all available .img .bin into the proper locations via fastboot.
when flashing the vbmetas use "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img" you should get a result like this if done properly.
"Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (8192 KB) OKAY [ 0.190s]
Writing 'vbmeta' OKAY [ 0.127s]
Finished. Total time: 0.379s"
also take note that there are a few .bin and .img locations that aren't the same location as the name. I used the scatter file in wwrmtk 2.51 to get the proper locations however I will copy and paste all my commands and results here.
after you rewrite all .img .bin you have to start over with the update .img and .bin.
here are the commands and results I used to successfully unbrick the device.
PS C:\Users\KAOS\Desktop\restore 9-3-20 update> fastboot flash boot boot.img
Sending 'boot' (32768 KB) OKAY [ 0.782s]
Writing 'boot' OKAY [ 0.503s]
Finished. Total time: 1.293s
PS C:\Users\KAOS\Desktop\restore 9-3-20 update> fastboot flash cache cache.img
Sending 'cache' (8832 KB) OKAY [ 0.202s]
Writing 'cache' OKAY [ 0.192s]
Finished. Total time: 0.414s
PS C:\Users\KAOS\Desktop\restore 9-3-20 update> fastboot flash dtbo dtbo.img
Sending 'dtbo' (8192 KB) OKAY [ 0.197s]
Writing 'dtbo' OKAY [ 0.129s]
Finished. Total time: 0.335s
PS C:\Users\KAOS\Desktop\restore 9-3-20 update> fastboot flash lk lk.bin
Sending 'lk' (1024 KB) OKAY [ 0.035s]
Writing 'lk' OKAY [ 0.018s]
Finished. Total time: 0.066s
PS C:\Users\KAOS\Desktop\restore 9-3-20 update> fastboot flash lk2 lk2.bin
Sending 'lk2' (1024 KB) OKAY [ 0.034s]
Writing 'lk2' OKAY [ 0.018s]
Finished. Total time: 0.068s
PS C:\Users\KAOS\Desktop\restore 9-3-20 update> fastboot flash logo logo.bin
Sending 'logo' (8192 KB) OKAY [ 0.199s]
Writing 'logo' OKAY [ 0.128s]
Finished. Total time: 0.343s
PS C:\Users\KAOS\Desktop\restore 9-3-20 update> fastboot flash preloader preloader_mid1035_mq.bin
Sending 'preloader' (233 KB) OKAY [ 0.016s]
Writing 'preloader' OKAY [ 0.158s]
Finished. Total time: 0.192s
PS C:\Users\KAOS\Desktop\restore 9-3-20 update> fastboot flash recovery recovery.img
Sending 'recovery' (32768 KB) OKAY [ 0.792s]
Writing 'recovery' OKAY [ 0.498s]
Finished. Total time: 1.298s
PS C:\Users\KAOS\Desktop\restore 9-3-20 update> fastboot flash spmfw spmfw.img
Sending 'spmfw' (1024 KB) OKAY [ 0.033s]
Writing 'spmfw' OKAY [ 0.018s]
Finished. Total time: 0.060s
PS C:\Users\KAOS\Desktop\restore 9-3-20 update> fastboot flash super super.img
Invalid sparse file format at header magic
Sending sparse 'super' 1/23 (129916 KB) OKAY [ 3.023s]
Writing 'super' OKAY [ 2.051s]
Sending sparse 'super' 2/23 (131068 KB) OKAY [ 3.065s]
Writing 'super' OKAY [ 3.812s]
Sending sparse 'super' 3/23 (131069 KB) OKAY [ 3.121s]
Writing 'super' OKAY [ 5.405s]
Sending sparse 'super' 4/23 (131068 KB) OKAY [ 3.074s]
Writing 'super' OKAY [ 5.470s]
Sending sparse 'super' 5/23 (131068 KB) OKAY [ 3.084s]
Writing 'super' OKAY [ 7.373s]
Sending sparse 'super' 6/23 (130593 KB) OKAY [ 3.139s]
Writing 'super' OKAY [ 8.220s]
Sending sparse 'super' 7/23 (131068 KB) OKAY [ 3.000s]
Writing 'super' OKAY [ 5.070s]
Sending sparse 'super' 8/23 (128774 KB) OKAY [ 3.143s]
Writing 'super' OKAY [ 8.107s]
Sending sparse 'super' 9/23 (129432 KB) OKAY [ 3.080s]
Writing 'super' OKAY [ 6.766s]
Sending sparse 'super' 10/23 (127084 KB) OKAY [ 2.943s]
Writing 'super' OKAY [ 5.197s]
Sending sparse 'super' 11/23 (130712 KB) OKAY [ 3.060s]
Writing 'super' OKAY [ 5.269s]
Sending sparse 'super' 12/23 (130612 KB) OKAY [ 3.102s]
Writing 'super' OKAY [ 6.239s]
Sending sparse 'super' 13/23 (131068 KB) OKAY [ 3.151s]
Writing 'super' OKAY [ 5.530s]
Sending sparse 'super' 14/23 (130648 KB) OKAY [ 3.141s]
Writing 'super' OKAY [ 5.893s]
Sending sparse 'super' 15/23 (130936 KB) OKAY [ 3.109s]
Writing 'super' OKAY [ 5.011s]
Sending sparse 'super' 16/23 (130720 KB) OKAY [ 3.106s]
Writing 'super' OKAY [ 4.640s]
Sending sparse 'super' 17/23 (128867 KB) OKAY [ 3.163s]
Writing 'super' OKAY [ 11.114s]
Sending sparse 'super' 18/23 (130500 KB) OKAY [ 3.038s]
Writing 'super' OKAY [ 6.164s]
Sending sparse 'super' 19/23 (131020 KB) OKAY [ 3.061s]
Writing 'super' OKAY [ 4.301s]
Sending sparse 'super' 20/23 (130632 KB) OKAY [ 3.072s]
Writing 'super' OKAY [ 3.810s]
Sending sparse 'super' 21/23 (131069 KB) OKAY [ 3.073s]
Writing 'super' OKAY [ 8.454s]
Sending sparse 'super' 22/23 (129608 KB) OKAY [ 3.061s]
Writing 'super' OKAY [ 2.942s]
Sending sparse 'super' 23/23 (107620 KB) OKAY [ 2.573s]
Writing 'super' OKAY [107.503s]
Finished. Total time: 328.236s
PS C:\Users\KAOS\Desktop\restore 9-3-20 update> fastboot flash scp1 tinysys-scp1.bin
Sending 'scp1' (1024 KB) OKAY [ 0.033s]
Writing 'scp1' OKAY [ 0.018s]
Finished. Total time: 0.059s
PS C:\Users\KAOS\Desktop\restore 9-3-20 update> fastboot flash scp2 tinysys-scp2.bin
Sending 'scp2' (1024 KB) OKAY [ 0.033s]
Writing 'scp2' OKAY [ 0.018s]
Finished. Total time: 0.064s
PS C:\Users\KAOS\Desktop\restore 9-3-20 update> fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (8192 KB) OKAY [ 0.190s]
Writing 'vbmeta' OKAY [ 0.127s]
Finished. Total time: 0.379s
PS C:\Users\KAOS\Desktop\restore 9-3-20 update> fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
Sending 'vbmeta_system' (8192 KB) OKAY [ 0.199s]
Writing 'vbmeta_system' OKAY [ 0.128s]
Finished. Total time: 0.340s
PS C:\Users\KAOS\Desktop\restore 9-3-20 update> fastboot --disable-verity --disable-verification flash vbmeta_vendor vbmeta_vendor.img
Sending 'vbmeta_vendor' (8192 KB) OKAY [ 0.195s]
Writing 'vbmeta_vendor' OKAY [ 0.127s]
Finished. Total time: 0.334s
PS C:\Users\KAOS\Desktop\restore 9-3-20 update> fastboot --disable-verity --disable-verification flash sspm 1 sspm.img
fastboot: error: cannot load '1': No such file or directory
PS C:\Users\KAOS\Desktop\restore 9-3-20 update> fastboot --disable-verity --disable-verification flash sspm_1 sspm.img
Sending 'sspm_1' (1024 KB) OKAY [ 0.033s]
Writing 'sspm_1' OKAY [ 0.018s]
Finished. Total time: 0.059s
PS C:\Users\KAOS\Desktop\restore 9-3-20 update> fastboot --disable-verity --disable-verification flash sspm_2 sspm.img
Sending 'sspm_2' (1024 KB) OKAY [ 0.034s]
Writing 'sspm_2' OKAY [ 0.019s]
Finished. Total time: 0.059s
PS C:\Users\KAOS\Desktop\restore 9-3-20 update> fastboot --disable-verity --disable-verification flash tee1 trustzone1.bin
Sending 'tee1' (5120 KB) OKAY [ 0.122s]
Writing 'tee1' OKAY [ 0.088s]
Finished. Total time: 0.218s
PS C:\Users\KAOS\Desktop\restore 9-3-20 update> fastboot --disable-verity --disable-verification flash tee2 trustzone2.bin
Sending 'tee2' (11264 KB) OKAY [ 0.265s]
Writing 'tee2' OKAY [ 0.167s]
Finished. Total time: 0.449s
PS C:\Users\KAOS\Desktop\restore 9-3-20 update> fastboot --disable-verity --disable-verification flash userdata userdata.img
Sending sparse 'userdata' 1/2 (131068 KB) OKAY [ 2.963s]
Writing 'userdata' OKAY [ 2.007s]
Sending sparse 'userdata' 2/2 (7840 KB) OKAY [ 0.246s]
Writing 'userdata' OKAY [ 0.985s]
NOTE rebooting takes quite awhile its not stuck on the boot logo walk away for a bit if need be. mine took about 5 minutes on the boot logo before it fully loaded.

I have successfully Rooted the Walmart ONN 100003562 preloaded with android 10 SAR.
I had to Flash both a Magisked patched recovery.img and a magisk patched boot.img as well as re flash the vbmeta using the disable varity and verify commands.
Step one:
Download files here.
Step 2
Install magisk_manager8.0.apk and update
adb install command
adb install magisk_manager_8.0.apk
Either patch the files yourself using magisk manager or use the ones provided here. I have provided both patched and unpatched .img as well as vbmeta.img
step 3
Flash .img's
boot flash command.
fastboot flash boot magisk_patched_boot.img
recovery flash command.
fastboot flash recovery magisk_patched_recover.img
vbmeta flash command.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
NOTE .img names may differ adjust accordingly.
reboot command.
fastboot reboot
YOU ARE NOW ROOTED WITH MAGISK!!!!!!!
HAVE AN AWESOME DAY AND DONT FORGET TO DONATE link to paypal in bio.

Here's a screenshot of magisk with successful root.

will160628 said:
Pulling a back up is actually a well known process that seems to be the same for most mediatek devices. Here is the youtube tutorial I use to run backups but there are dozens to choose from:
https://www.youtube.com/watch?v=pj4iFakq33M
I have a section of my google drive I keep open with backups if you need to try a restore. I made a backup of the latest update from October but I forgot to upload it. At 100kbps it will be awhile before I can post it even if I had the chance to start the upload now. You should be able to do a full restore from any of these backups as long as you don't try to piecemeal it.
https://drive.google.com/drive/folders/1DGfI6u-OGaDJr_OkPOMmOKVxYCzrpp5k?usp=sharing
As far as root goes, magisk doesn't seem to have support for these particular tablets yet on my last attempt. Also be aware that these tablets have partitioning based on an android 10 system which means creating roms, kernels, TWRP, rooting and the like is totally different from android 9 and below. If you do follow through with trying to rom this tablet make sure any tutorials you look into pertain to devices that shipped with android 10 or above. I'll try to check back when I get a chance so let me know if you need help at least with the backups. Not sure I can offer help with much else at this point. I've been messing with android as a hobby since the og droid first came out but I haven't done much with devices based off this new system. Good luck.
Click to expand...
Click to collapse
I was able to successfully Unbrick from a full on hard brick and also was successful in obtaining root access. Now a new update downloaded on the device so I am going to attempt updating an re rooting if needed. read through. Thanks again so much for having and sharing the backed up. will be rooting the 28 dollar 8 inch next.

Can I get a mod to rename this thread to "How to successful unbrick and root Walmart ONN 10.1 100003562"

Sp tool
KaosKreationz said:
thanks but i need the MT8768WA chipset.
Click to expand...
Click to collapse
Sorry about that. I should have mentioned most 876x... processors seem to be basically a rebrand of the 6765 with minor updates mostly coming in the clock speed area. Using the 6765 listing in sp tool & wwr tends to work fine for devices using the "updated" processors. That said there is a scatter in all my backups that can be loaded in sp tool to do all the heavy lifting instead of using fastboot. Using sp tool will be a lot easier than fastboot for the majority of people that will hit these forums from google. There is a main backup thread all about that which covers sp tool for all onn tablets. At least nothing changed on that front with the latest gen walmart devices.
https://forum.xda-developers.com/wa...eral/stock-stock-backups-images-otas-t3998227
Now all that said, I don't think anyone has done a full write-up for unbricking with fastboot for the new partitioning. I'm hoping this gets stickied for people that can't get sp tool to detect their devices. I believe your process should be the same on the 8” pro tablets released just before the 10.1. It should be usefull for quite a few people that get either device this holiday season.
I did start the upload for the 10-22 update but apparently my gdrive laptop crashed and I just had to restart the upload. Wish drive resumed uploads like it does downloads. Hoping I'll get it posted some time this week but no telling. I'm too lazy to look through and just upload the changes.
I'll try your root method once I get to my desktop and post back to verify for other people.
Oh before I forget, at that price the 8" you mention sounds like one of the earlier walmart tablets that runs 9. I believe magisk detects those so you shouldn't have to manually disable verity and just the boot.img is enough to root. Not sure how new you are to the walmart tablet line so thought I'd mention it just in case.

Verified
Just ran through and disabling verity was the one thing I didn't try before but it worked. I've done the same procedure on other devices but it didn't even occur to me. My attention span is worse than a 2 year old at this point so I can't say I tried all that hard before. Anyway thanks for the write up and good job. Jrummy's root browser pro gives write access to ./ Directories so this seems to be a proper root method.
Did you have any issues with the ota update after you rooted? I've heard talk of errors on devices running 10. Either the update won't work or it bricks the device. Just wondering if thats something people need to be on the lookout for.
Btw you wrote recover.img instead of recovery.img in your write up. I wouldn't have noticed but I copy/paste a lot. Did I mention I'm lazy?

will160628 said:
Sorry about that. I should have mentioned most 876x... processors seem to be basically a rebrand of the 6765 with minor updates mostly coming in the clock speed area. Using the 6765 listing in sp tool & wwr tends to work fine for devices using the "updated" processors. That said there is a scatter in all my backups that can be loaded in sp tool to do all the heavy lifting instead of using fastboot. Using sp tool will be a lot easier than fastboot for the majority of people that will hit these forums from google. There is a main backup thread all about that which covers sp tool for all onn tablets. At least nothing changed on that front with the latest gen walmart devices.
https://forum.xda-developers.com/wa...eral/stock-stock-backups-images-otas-t3998227
Now all that said, I don't think anyone has done a full write-up for unbricking with fastboot for the new partitioning. I'm hoping this gets stickied for people that can't get sp tool to detect their devices. I believe your process should be the same on the 8” pro tablets released just before the 10.1. It should be usefull for quite a few people that get either device this holiday season.
I did start the upload for the 10-22 update but apparently my gdrive laptop crashed and I just had to restart the upload. Wish drive resumed uploads like it does downloads. Hoping I'll get it posted some time this week but no telling. I'm too lazy to look through and just upload the changes.
I'll try your root method once I get to my desktop and post back to verify for other people.
Oh before I forget, at that price the 8" you mention sounds like one of the earlier walmart tablets that runs 9. I believe magisk detects those so you shouldn't have to manually disable verity and just the boot.img is enough to root. Not sure how new you are to the walmart tablet line so thought I'd mention it just in case.
Click to expand...
Click to collapse
No surprisingly enough the 8 inch or 7.2 inch rather is a newer one with android 10 preinstalled they only had one show case filled with them as a black friday special i honestly shoulda grabbed a bunch and modded and handed em out for xmas. anyway its the MT8162B chipset.

KaosKreationz said:
No surprisingly enough the 8 inch or 7.2 inch rather is a newer one with android 10 preinstalled they only had one show case filled with them as a black friday special i honestly shoulda grabbed a bunch and modded and handed em out for xmas. anyway its the MT8162B chipset.
Click to expand...
Click to collapse
Okay. By that processor and OS it sounds like the 7" surf pro that went on sale a few days ago. I think there's a thread about rooting those somewhere on xda. I haven't had the chance to check that model out yet so I don't know much beyond what I've read. I have heard they can be a bit sluggish though. I think they actually run android 10 go which doesn't seem to get much love from google. I have seen some talk about roming them since the hardware should be more capable than it lets on. If it were the 8" pro with the mt8768 similar to the 10.1 I'd be interested in getting one at that price. I'm looking into one of those for my mom this Christmas but they continually run $99. I don't think she'd tolerate anything with less than 2gb of ram for long considering she just bought an 8" previous gen and already wants to trash it. Some of her games are memory hogs.

onn 7 inch pro gen 2 100015685 models.
step 1
Download files from the google drive link.
https://drive.google.com/drive/folders/14DUU4uyRdKO2lUdkjOH1zETdAqjOWQun?usp=sharing
Step 2
Open the containing folder.
Step 3
Right shift + right click and select powershell
Step 4
Run these commands in order.
fastboot commands.
fastboot flashing unlock
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase cache
fastboot flash boot magisk_patched.img
fastboot reboot
Step 5
Wait till it boots and todahhhh you are now rooted with Magisk.
enjoy and dont forget to donate paypal email is on my info.

KaosKreationz said:
onn 7 inch pro gen 2 100015685 models.
step 1
Download files from the google drive link.
https://drive.google.com/drive/folders/14DUU4uyRdKO2lUdkjOH1zETdAqjOWQun?usp=sharing
Step 2
Open the containing folder.
Step 3
Right shift + right click and select powershell
Step 4
Run these commands in order.
fastboot commands.
fastboot flashing unlock
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase cache
fastboot flash boot magisk_patched.img
fastboot reboot
Step 5
Wait till it boots and todahhhh you are now rooted with Magisk.
enjoy and dont forget to donate paypal email is on my info.
Click to expand...
Click to collapse
hi, do you know if this will work with the 100015685-A model? thanks

jason7246 said:
hi, do you know if this will work with the 100015685-A model? thanks
Click to expand...
Click to collapse
Yes it will there is a thread on here regarding the a model it’s labeled 7 inch gen 2. I happenned to run see it the other day when I was researching. I used there scatter file to pull my software being that I can’t seem to get the wwr software working on my windows 10. Every time I try to create a scatter it results with only the bootloader found.

KaosKreationz said:
Yes it will there is a thread on here regarding the a model it’s labeled 7 inch gen 2. I happenned to run see it the other day when I was researching. I used there scatter file to pull my software being that I can’t seem to get the wwr software working on my windows 10. Every time I try to create a scatter it results with only the bootloader found.
Click to expand...
Click to collapse
if u mean preloader(probably me being confused), then ya im having the same issue, im trying some of these files now to see if i can get mine back to working, i had tryed some files for the -E version a few days ago, the boot.img being the major one, to find it bootlooping my -A model, so fingers crossed.

jason7246 said:
hi, do you know if this will work with the 100015685-A model? thanks
Click to expand...
Click to collapse
jason7246 said:
if u mean preloader(probably me being confused), then ya im having the same issue, im trying some of these files now to see if i can get mine back to working, i had tryed some files for the -E version a few days ago, the boot.img being the major one, to find it bootlooping my -A model, so fingers crossed.
Click to expand...
Click to collapse
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Use the vbmeta and use this command u should be able to get out of bootloop on the other device.

@KaosKreationz Wow 28$ for this tablet model : 100003562? Thats a steal. My local WM has it for 129 + taxes. Even refurb units on Ebay are like 75$.
Also thanks for your efforts on this thread.
Before buying, I came here looking to see if anyone has a custom ROM for this tablet.