Related
Shield has Android TV 2017
I am following this process and the shield is not working.
—–
fastboot oem unlock
twrp boot (fail)
Infinite reboot
(controller a,b key pushing
power cable in)
hw mode bootloader connect to pc
(pc recovery img “fastboot-all.bat” Execution)
error devices not connect after install 2 things finished
—
shield tv Does not wake from sleep mode
pc to connect (pc devices manager display others-apx)
hw mode is not working
How can I recover it?
If your shield TV doesn't boot correctly, fastboot-all.bat won't work because you need to have adb working.
You should indeed rather follow the instructions given on Nvidia website, i.e. for Shield TV 2015 16GB with Marshmallow or newer installed:
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot reboot
Before that, be sure you use a good quality USB OTG cable.
Sounds like you can't boot into fastboot or bootloader mode.
If you can't, it means that you are hard bricked.
If you already had latest Nvidia experience version 5.1, there was no need to reflash the whole recovery image, PLUS you don't mention what recovery image you flashed.
To sum up your error was eather a bad usb cable (this a very known issue now, shield is picky) AND/OR wrong blob (which is the bootloader and it comes in all nvidia recovery image packages) flash.
What makes the device brick is a corrupted bootloader.
If bad USB and fail while flashing blob (which again is the bootloader), it gets corrupted.
If wrong blob flash (by using one that is not for you device model OR when attempting to downgrade to MM or lower bootloader), it gets corrupted.
Moral of the story:
Never mess with the bootloader a.k.a blob if you dont know what you're doing.
I know there are many hard bricked users around so better start reading. Take your time and make sure you understand all the instructions and also the pros and cons of the restore/unbrick method.
NOTE: just so you know next time for Shield TV 2017 , when you unlock bootloader and flash TWRP recovery or custom firmware you must root, because root with SuperSU disables some checks Nvidia run at boot. If you don't root, then your Shield will be stuck at boot.
- Sent from my Tapatalk Hub -
If I helped hit the Thanks button. Follow Me! ~ Buy Me a Coffee ~ Full Android for ShieldTV and Nexus Player
I'm trying to restore my Shield TV back to stock. Following Neo's thread I get to the very end where I'm stuck with the message below. Can anyone help out with this message?
C:\Users\......................\Downloads\nv-recovery-image-shield-atv-5.1.0\nv-recovery-im
age-shield-atv-5.1.0>fastboot flash dtb tegra210-foster-e-p2530-0930-e02-00.dtb
error: cannot load 'tegra210-foster-e-p2530-0930-e02-00.dtb'
This is how (Or, what), you (need to do to), recover your Shield TV using the correct Recovery Image from nVIDIA.
NOTE its CRITICAL to make sure you use the correct Image Standard, or Pro 2015, or 2017 Model. Flashing the incorrect, or an older version e.g. Experience 3.x over the current Experience 5.x.x. Will most likely (Perma) -brick you Device.
That said you need to place your Device into Fastboot Mode. Than use the following commands...
Code:
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
Of these flashing system.img will take the longest. About Five-ish Minutes or so, as the Shield will first erase the contents of the /system before rewriting it again.
P.s. As an aside to this, and as a bit of advice, if your lucky enough to have a Pro version. Have a look at the few SSHD to SSD migration Threads on this Site, and contemplate making a Backup of your Device, and then storing said backups on Google Drive, and or a USB Stick. Should you ever find yourself in a brick situation. This WILL probably save your delicious Bacon.
I used the correct image. Device rebooted. How long should the Nvidia logo stay there on the first reboot? Wondering if I need to give it time or if I did something wrong.
From the link below what's then what's the difference in this thread?
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash dtb <DTB file name>
http://developer.download.nvidia.co...TV/Upgrade-2.1/HowTo-Flash-Recovery-Image.txt
Worrying about my device being bricked I was able to get back into fastboot. I'm assuming that means I can flash and flash again?
My device has some overscan going on so I can't read the complete fastboot menu options but I'm assuming I don't need to do anything with those for this to flash?
I find it odd that your using a "dtb" File as normally there isn't one. Perhaps way, way back when. But, I know Experience 3.x (i.e. Marshmallow), Recoveries never hosted such a File. Neither would any Experience 5.x (Nougat) Recovery.
This seems to suggest (to me), that you attempted to flash an otherwise correct, but older ROM., which is a HUGE NO NO!!!
It would seem that newer ROMs manage to alter the overall partition map of the SSHD / eMMC in such a way that revering to an older version will cause the Device to brick.
Besides the order is wrong. You need to go by what nVIDIA tells you to do (flashall *.bat / *.sh), and less what some outdated Website suggests. Again see above. dtb Files just (Well as far as the Pro goes...), Just don't exist anymore. I gather they had, but ONLY in the earliest Firmware ROMs.
One other thing... In some cases depending on how it goes... It may well Stick at the nVIDIA logo for up to Two plus Hours! As the Shield is rebuilding itself. In which case the best advice would be to leave it and go out for some Coffee, and a Crawler and check it out again well after the Two Hour mark. Of course this shouldn't happen on a 16Gb eMMC version. Which should be IMO near instantaneous. Alas the SSHD isn't quite that fast.
Ichijoe said:
I find it odd that your using a "dtb" File as normally there isn't one. Perhaps way, way back when. But, I know Experience 3.x (i.e. Marshmallow), Recoveries never hosted such a File. Neither would any Experience 5.x (Nougat) Recovery.
This seems to suggest (to me), that you attempted to flash an otherwise correct, but older ROM., which is a HUGE NO NO!!!
It would seem that newer ROMs manage to alter the overall partition map of the SSHD / eMMC in such a way that revering to an older version will cause the Device to brick.
Besides the order is wrong. You need to go by what nVIDIA tells you to do (flashall *.bat / *.sh), and less what some outdated Website suggests. Again see above. dtb Files just (Well as far as the Pro goes...), Just don't exist anymore. I gather they had, but ONLY in the earliest Firmware ROMs.
One other thing... In some cases depending on how it goes... It may well Stick at the nVIDIA logo for up to Two plus Hours! As the Shield is rebuilding itself. In which case the best advice would be to leave it and go out for some Coffee, and a Crawler and check it out again well after the Two Hour mark. Of course this shouldn't happen on a 16Gb eMMC version. Which should be IMO near instantaneous. Alas the SSHD isn't quite that fast.
Click to expand...
Click to collapse
Thank you for the detailed response. I wonder if that thread on here can be decommissioned. That's where I found the info about that dbt file. I left it at startup a few hours ago so I'll see if there is any change when I return.
Assuming since it's not the mechanical HD something is probably wrong. What does Nvidia tell me? Do they have steps on their site? I didn't think to go there since this shield I acquired already had regular Android on it figuring I needed the XDA or some other community.
I still couldn't get the flash dtb file name portion to work from the steps below. These were listed on Nvidia's steps. Anyways this worked! Back to stock.
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash dtb <DTB file name> (Use result from "fastboot oem dtbname" in <DTB file name>)
fastboot reboot
@Liip008, so the only thing you did was to wait? (I can't see any different steps in your second post).
I'm trying to downgrade to Marshmallow but all I get is a black screen. Not even the logo displays. Nvidia should change really consider to change their instructions since someone may brick their device. For instance, the installation readme of 3.2 says "SHIELD UNITS WITH ANDROID MARSHMALLOW OR NEWER", thus implying downgrading shouldn't be a problem.
TWRP Custom Recovery for the Onn Android Tablet series
This is the first fully-featured custom recovery for Walmart's MediaTek-based Onn tablets: ONA19TB002, ONA19TB003 and ONA19TB007. TWRP needs no introduction. If you have come here, you probably have some idea of what it is and what it's used for. This TWRP build does not need the bootloader unlocked or VBMeta verification disabled, although it's recommended that you at least unlock the bootloader.
DISCLAIMER
Everything described in this thread is done at your own risk. No one else will be responsible for any data loss, corruption or damage of your device, including that which results from bugs in this software.
FEATURES
Decrypted data partition
All USB modes functional: MTP, ADB, Mass Storage, OTG, Charging
Fast boot time
Adoptable storage mounting
Firmware image backup and restore
Works under locked bootloader
Android 9 build fits within the 16MB recovery partition -- no compromises or partition resizing necessary
INSTALLATION METHOD 1
Download the recovery to your PC and unzip the image
Unlock the bootloader (skip if you have already done this)
Enable OEM Unlock in Developer Options in Android Settings
Boot into fastboot mode either by holding vol. up+power to power it on and selecting "Fastboot mode", or by running the 'adb reboot bootloader' command from within Android.
Install fastboot and appropriate drivers on your PC if you have not set those up
Unlock the bootloader with the command
Code:
fastboot flashing unlock
...and follow the instructions on the screen. This will wipe your data.
Flash the custom recovery with
Code:
fastboot flash recovery twrp-3.3.1-ONA19TB002.img
(use the right file name path for your device)
Reboot to recovery with
Code:
fastboot oem reboot-recovery
INSTALLATION METHOD 2
This assumes you are familiar with SP Flash Tool or can figure it out on your own
Download the recovery to your PC and unzip the image
Get the appropriate scatter file for your device. The scatter file may be found in the device's firmware under /system/data/misc.
Set up SPFT Download tab as Download Only. Load your scatter file.
Under the recovery line, double-click Location and open your TWRP image.
Click Download and connect your powered-off tablet to your PC. SPFT will automatically flash the recovery to the emmc and disconnect when finished.
INSTALLATION METHOD 3
Head over to Amazing Temp Root for MediaTek ARMv8, read the requirements and directions, and grab the latest mtk-su.
Open a root shell with mtk-su
Flash the (unzipped) recovery with the command:
Code:
dd bs=1048576 if=twrp-3.3.1-0-ONA19TB002.img of=/dev/block/by-name/recovery
(replace the if= file name with your appropriate recovery image path)
Exit root shell
START RECOVERY
Three methods:
On a powered off tablet, hold Vol. up+power for about 3 seconds. In the menu that appears, select "Recovery mode"
With Android ADB, use the command 'adb reboot recovery'
From Android root shell, use the command 'reboot recovery' or just use any root app with OS reboot features
NOTES
Kind of important: Make a backup of your Crypto Footer as soon as you can. This is the encryption key to your data partition. When accessed from TWRP, this key can get "upgraded" so that you will get locked out of Android. TWRP uses a hacky workaround that saves and restores the original footer on every /data decrypt. But that method is not what I would call 100% reliable.
Make sure you have a backup of the untouched stock system and vendor images. There are no official firmware packages available to download.
Only mount system/vendor partitions in read/write mode if you have unlocked the bootloader. It is recommended to choose to leave system read-only at the startup prompt unless you have a specific reason to modify it. If the bootloader is locked, then dm-verity is enforced.* So merely mounting it once in r/w will cause a boot loop.
It's currently not possible to install incremental OTA updates using this TWRP. Use the stock recovery to update the FW. That will only work if you have never mounted system/vendor in write mode.
DOWNLOAD (Nov. 30, 2019)
Current version: 3.3.1-1
ONA19TB002 - Onn 8" model
ONA19TB003 - Onn 10.1" model
ONA19TB007 - Onn 10.1" w/keyboard model
Source code
ONA19TB002 | ONA19TB003 | ONA19TB007
ACKNOWLEDGEMENTS
The team behind TWRP & OmniROM
@tek3195 for testing and feedback on the 8" model
Please post feedback since these are still pretty new and not exhaustively tested. Let me know if I should port it to other models in the series.
Reserved also
grabbing this one too cuz why not
Very nice! I'll download and test the 003 one soon.
I also have a 007 model to experiment with.
I tried about a dozen times to build TWRP and failed miserably LOL. Closest I got was one that would boot but the rotation was all messed up, USB wouldn't work, didn't mount some partitions... Yeah, it was a hot mess.
Do you happen to have sources available?
Hi @NFSP G35,
I'll have the source code soon. Most of the tricks involved patching bootable/recovery. So I need to commit those changes and include the proper patch set from my tree....
Amazing!! Gonna install and test 8" right now.
Has anyone tried a GSI on these tablets yet?
MishaalRahman said:
Has anyone tried a GSI on these tablets yet?
Click to expand...
Click to collapse
I do know @tek3195 , the Onn 8 thread starter, has tried many of them as well as others here, somewhere on that thread he listed his tests and opinion of several of them.
I'm pretty sure others on that thread have also tried GSI's.
MishaalRahman said:
Has anyone tried a GSI on these tablets yet?
Click to expand...
Click to collapse
I did try both Phhuson vanilla and also Liquid Remix (I'm keeping this one for now). I didn't flash them through twrp, but using fastboot via bootloader.
WoW! AwEsOmE! I cannot wait to try this! THANK YOU!!!!!!
Hey,
This is a neat thing to see for the Onn tablets. I have a question though. I own a device based on the mt8163, and am trying to help people with another device I don't own (the powkiddy x18 which also uses the mt8163). One of the things I wanted to do was to make a custom rom for the x18, since it's stock firmware is horrible. And of course, one of the first steps to custom roms is twrp. So I have a question for you that I hope you can answer for me. How did you make this build of twrp? I have seen no device trees for this device so I was kinda curious. If you can help me in any way, I'd be so grateful, and I'm sure the other people with the x18 would be grateful for help.
@diplomatic
Is there a different procedure for installing TWRP on a locked bootloader?
I can confirm that using SP Flash to load your TWRP.img will produce a bootloop when installing to a device with the BL locked. Reflashing the original recovery.img makes the problem go away. You mentioned in the OP that this TWRP will work on a locked BL so I thought I would share my case study with you in following the procedure you defined.
MY SINCERE GRATITUDE FOR YOUR EFFORTS IN PORTING THIS TO THE ONN!
You're welcome, @Spatry.... Can you describe how you ended up with a locked BL? Was it unlocked before? Have you ever tweaked vbmeta? Also, when you say bootloop, do you mean for Android or just for recovery? I'm not going to insist that it works under locked BL. I tested it once and it did boot up...
diplomatic said:
You're welcome, @Spatry.... Can you describe how you ended up with a locked BL? Was it unlocked before? Have you ever tweaked vbmeta? Also, when you say bootloop, do you mean for Android or just for recovery? I'm not going to insist that it works under locked BL. I tested it once and it did boot up...
Click to expand...
Click to collapse
Presently, I am running stock with Magisk patched BOOT on locked bootloader, stock vbmeta. The boot loop was at the ONN Android screen, I could not get it to even boot into recovery.
At one time I did run with the bootloader unlocked (with --disable-verification on stock vbmeta) and I ran Phusson's AOSP, Liquid Remix and Bliss. I found there was no benefit to me in running the other mods so I reverted back to stock courtesy of @CaffeinePizza and the bootloader re-locked to get rid of that annoying 5 second orange state.
In each instance, I always used SP Flash tools to load all .img files. I only used fastboot to install magisk_patched.img onto the stock installation. Unlocking the bootloader erases all data and I did not feel like reinstalling everything again, so I figured I would try to install TWRP per your instruction to see if it would work while the BL was still locked... Restoring the original recovery got rid of the bootloop. I do want to try your TWRP so I will try it with BL unlocked when I get some free time to do so.
Spatry said:
Presently, I am running stock with Magisk patched BOOT on locked bootloader, stock vbmeta. The boot loop was at the ONN Android screen, I could not get it to even boot into recovery.
Click to expand...
Click to collapse
This sounds like you might have flashed a wrong/corrupt image to recovery. It may have to do with AVB checks rather than bootloader lock. But those conditions might be interdependent somehow so I can't tell you for sure. The fact that you are able to boot a patched image on a locked BL says it doesn't care too much about verification. I can tell you for sure that any recovery image must have avb metadata, not necessarily the required hash, for both Android and recovery to boot. Can you try to unzip the image file and flash it over again?
Hmm, the situation with the bootloader lock sounds eerily similar to the Nabi SE. The latter also had a similar implementation where there's not much in the way of locking things down, other than an (easily circumvented) SP Flash Tool signature check and different preloader keys. And here's the real kicker: the nearly-identical Fisher Price Nabi also ran on the MT8163, so it makes me wonder if it's possible to boot Pie on it, or perhaps a GSI assuming that Treble can be tacked onto it.
Also, do you have the source repo to this TWRP port of yours?
If anyone here gave me an XDA ad-free subscription, thanks a lot! I didn't get a notification of who it was. Using this site is a lot more bearable now.
diplomatic said:
If anyone here gave me an XDA ad-free subscription, thanks a lot! I didn't get a notification of who it was. Using this site is a lot more bearable now.
Click to expand...
Click to collapse
Where do I find crypto footer to backup
diplomatic said:
If anyone here gave me an XDA ad-free subscription, thanks a lot! I didn't get a notification of who it was. Using this site is a lot more bearable now.
Click to expand...
Click to collapse
Kinda cool without the ads isn't it. I know I sent one about a week ago or so. I think everybody ought to send you one, you deserve it. THANKS and AWESOME work.
Onn Surf 7" gen 2 on sale for 28$ today. Bought one... Was able to unlock bootloader
So, stopped at walmart this morning for stuff and saw the Onn Surf is now on Gen 2. 2.0 GHz quad core, 16gb storage and 2 gb ram. Seemed pretty decent for 28$. Much snappier than my 2017 Galxay Tab A 7". Runs Android Go 10. So far, have a 128 GB sd card in the slot. I have ran a few games(Raid Shadow Legends, Pubg) on it and it seems pretty decent so far. Hoping somebody smarter than me can find out if we can root and rom it. I would love to have pure ASOP on it. Even if that doesn't happen, would love to have root to get rid of the pre-installed stuff. At the price point, I couldn't pass it up. I haven't figured out the CPU, guessing it is a Media Tek. The GPU is a Mali-G52 MC2 if that helps. Running GeekBench right now to see how it scores. Seems it is not bad. Chip is listed as ARM MT8168B Motherboard is listed as tb8168p1_bsp if that helps at all. Geekbench gave it a 542 score. Not sure how that compares.
I was able to unlock the bootloader in the normal fashion. adb reboot bootloader. fastboot flashing unlock. fastboot reboot when finished unlocking. It then had a series of prompts on the screen that I followed. Once it was done, I rebooted via fastboot. The reboot took a bit as it factory reset the device as expected. I was trying root with mtk-su, but have been unsuccessful so far.
Well, it looks like mtk-su will not work on this device. So I will have to wait for someone much smarter than I to figure out root for us
I just got this one also at walmart. For $28 is not bad. It feels snappier than amazon fire 7 or 8
Okiera29 said:
So, stopped at walmart this morning for stuff and saw the Onn Surf is now on Gen 2. 2.0 GHz quad core, 16gb storage and 2 gb ram. Seemed pretty decent for 28$. Much snappier than my 2017 Galxay Tab A 7". Runs Android Go 10. So far, have a 128 GB sd card in the slot. I have ran a few games(Raid Shadow Legends, Pubg) on it and it seems pretty decent so far. Hoping somebody smarter than me can find out if we can root and rom it. I would love to have pure ASOP on it. Even if that doesn't happen, would love to have root to get rid of the pre-installed stuff. At the price point, I couldn't pass it up. I haven't figured out the CPU, guessing it is a Media Tek. The GPU is a Mali-G52 MC2 if that helps. Running GeekBench right now to see how it scores. Seems it is not bad. Chip is listed as ARM MT8168B Motherboard is listed as tb8168p1_bsp if that helps at all. Geekbench gave it a 542 score. Not sure how that compares.
Click to expand...
Click to collapse
I got it as well [emoji1] for $28 it very very good, it comes with a $10 grocery pickup coupon as well [emoji23]. These devices can really use custom roms, some overclocking, and remove the Walmart bloatware which is not as bad as a fire blu cell phone that I used long time ago. The first thing I did was to disable the widow animation scale, transition animation scale, and animator duration scale. Tried kingo root app it does not work on this device, tried custom navigation bar .apk not compatible with this device will try to root either by conventional way or magisk.
Sent from my 100015685-E using Tapatalk
Saw these in store and grabbed 2. Set one up and tinkering with it. Runs a bit smoother compared to Fire 7 2019. FCC ID A2HCT9E78Q for those interested. Has BT 5, tiny noticeable audio lag watching YT video & Pluto TV connected to bt wireless earphones. Android 10 Go doesn't appear to support youtube pip mode.
I will be interested to see how development goes. Seems like at lot of devices use this SOC, so that leaves some hope. I had some wifi issues yesterday, but restarting the tablet fixed it. So far, I am happy for 28$. It is quite a bit lighter than my Samsung Tab A 7 ". Pubg is still running fine. Frame rate is nothing to write home about, but that is to be expected
I'm in the same boat. Picked one up this morning, unlocked the bootloader successfully but had no luck with mtk-su or any of that. Hopefully someone smarter than me gets this figured out
FredQ said:
I'm in the same boat. Picked one up this morning, unlocked the bootloader successfully but had no luck with mtk-su or any of that. Hopefully someone smarter than me gets this figured out
Click to expand...
Click to collapse
Unlikely; need to read up on the (ridiculous and inexcusable) vulnerability mtk-su exploited, manufacture response and the heavy-lift challenges rooting newer Android builds. Possible, but unlikely.
After spending most of last night trying to get this working I'm uploading what I've got in the hopes that someone can get it to boot.
Following several tutorials and using a combination of SP Flash Tool and WWR MTK I managed to create the scatter file and then extract the whole rom giving me the boot.img.
However, after patching the boot.img with magisk manager and flashing it I'm getting a boot loop. I can flash the original boot.img back and it boots as normal but obviously this is without root.
If anybody wants to take a look and see if they can get it figured out feel free.
There are 4 files. The scatter file, original boot.img, then there are 2 magisk patched boot.img files. The first one is smaller than the original boot.img which I read is quite usual but some devices don't take well to the size difference. So the second patched img is padded to match the file size of the original. I can't get any of these to boot, both put me in a boot loop which can only be fixed by flashing the unpatched img again.
Model: 100015685-E
https://app.mediafire.com/91m2g8if4iain
FredQ said:
After spending most of last night trying to get this working I'm uploading what I've got in the hopes that someone can get it to boot.
Following several tutorials and using a combination of SP Flash Tool and WWR MTK I managed to create the scatter file and then extract the whole rom giving me the boot.img.
However, after patching the boot.img with magisk manager and flashing it I'm getting a boot loop. I can flash the original boot.img back and it boots as normal but obviously this is without root.
If anybody wants to take a look and see if they can get it figured out feel free.
There are 4 files. The scatter file, original boot.img, then there are 2 magisk patched boot.img files. The first one is smaller than the original boot.img which I read is quite usual but some devices don't take well to the size difference. So the second patched img is padded to match the file size of the original. I can't get any of these to boot, both put me in a boot loop which can only be fixed by flashing the unpatched img again.
Model: 100015685-E
Click to expand...
Click to collapse
how did you manage to get out of the boot loop? I'm currently stuck in it from trying the exact same thing and I can't seem to access recovery mode or the boot loader or even manage to turn off the tablet.
To get out of the boot loop I had to flash the original boot.img using SP Flash Tool. Put the scatter file and the boot.img in the same folder. Then open the scatter file in SPF Tools and with only the boot.img checked click download when the tablet screen goes black as it's looping. It should then flash the file and when you power the tablet back on you should be good.
are you guys using windows 10 or 7 or? also, i have the -a verision of this tablet (100015685-A) and i was able to just get the scatter file that includes only the, Preloader? if that sounds right, and nothing else using WwR MTK v2.51(wich i believe is what RetroTho is using). now when i try and take that scatter file and use it SP flash Tool to do anything with it, it doesnt seem to do anything. i seen something about VCOM drivers (which i thought i had installed) but just in case tryed to install them using the .bat, and had no luck,(hence the OS question). so what am i missing if someone can help me? id like to try and get a complete rom backup if possible, to be safe, before i do anything else. or at least a boot.img and recovery.img. any help would be much appreciated.
Removed
After playing around with this for a while I got it to work. The problem is with Android Verified Boot. I used the scatter file created by @FredQ (Thanks!) and SP Flash tool to dump the vbmeta partition. Then I used the following commands to flash the modified boot image.
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase cache
fastboot flash boot magisk_patched.img
fastboot reboot
This disables AVB and allows it to boot. I verified that I had root afterwards.
http://gofile.io/d/HXCmPd
One unfortunate thing I found out is that the way the navigation bar is handled changed with Android 10. So far I haven't found a way to remove the Walmart button. This was one of the things I was hoping to do with root.
thecaptain0220 said:
After playing around with this for a while I got it to work. The problem is with Android Verified Boot. I used the scatter file created by @FredQ (Thanks!) and SP Flash tool to dump the vbmeta partition. Then I used the following commands to flash the modified boot image.
Click to expand...
Click to collapse
This is great news! Thanks for the hard work. I will attempt to replicate on my second device and report back. Root should at least make it easier to get a system dump and such. Thanks again!
Well, shoot! now I am getting "--disable-verity is not recognized as an internal or external command, operable program or batch file" when I run the first command.
Never mind, if I run fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img then it runs fine. Just flashed your patched boot as well. I will report in a moment. Well, now disable verity works, but it says there is no vbmeta file or directory. so it fails. so far, no root
Well, DUH! needs to be in bootloader mode LOL. Now that I have it there, all commands work, but I still don't have root after flashing your patched boot image
thecaptain0220 said:
After playing around with this for a while I got it to work. The problem is with Android Verified Boot. I used the scatter file created by @FredQ (Thanks!) and SP Flash tool to dump the vbmeta partition. Then I used the following commands to flash the modified boot image.
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase cache
fastboot flash boot magisk_patched.img
fastboot reboot
This disables AVB and allows it to boot. I verified that I had root afterwards.
http://gofile.io/d/HXCmPd
Click to expand...
Click to collapse
Amazing. I'm up and running and rooted now! Thanks for the help
thecaptain0220 said:
After playing around with this for a while I got it to work. The problem is with Android Verified Boot. I used the scatter file created by @FredQ (Thanks!) and SP Flash tool to dump the vbmeta partition. Then I used the following commands to flash the modified boot image.
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase cache
fastboot flash boot magisk_patched.img
fastboot reboot
This disables AVB and allows it to boot. I verified that I had root afterwards.
http://gofile.io/d/HXCmPd
Click to expand...
Click to collapse
hi, do you know if this will work with 100015685-A? thanks
seems like finding a way to root the $28 onn tablet is coming to an end (a video tutorial would be great)
but when i do unlock the bootloader on my 100015685-e tablet (adb reboot bootloader, fastboot flashing unlock), adb gives me this and my tablet keeps disconnecting from my laptop
Code:
C:\Users\Ted\Documents\platform-tools>fastboot flashing unlock
< waiting for any device >
this does the same thing with fastboot oem unlock
what is going on and how would i fix this? nothing was done towards the tablet
teddyv1974 said:
seems like finding a way to root the $28 onn tablet is coming to an end (a video tutorial would be great)
but when i do unlock the bootloader on my 100015685-e tablet (adb reboot bootloader, fastboot flashing unlock), adb gives me this and my tablet keeps disconnecting from my laptop
Code:
C:\Users\Ted\Documents\platform-tools>fastboot flashing unlock
< waiting for any device >
this does the same thing with fastboot oem unlock
what is going on and how would i fix this? nothing was done towards the tablet
Click to expand...
Click to collapse
Sorry, I was not clear in my first post. I know this sounds silly, but make sure developer options are turned on and that OEM unlock and adb debugging is turned on.
Go to settings, about tablet. Then tap the build number at the bottom seven times and that will turn on developer options. Then in developer options, turn on oem unlocking and adb debugging.
Then run adb devices. It should return your tablet's serial number and 'device' If it shows the device 'unauthorized' (mine did the first couple of times) revoke ADB authorization and plug the tablet back in.
Then it is just adb reboot bootloader and then fastboot flashing unlock.
Okiera29 said:
Sorry, I was not clear in my first post. I know this sounds silly, but make sure developer options are turned on and that OEM unlock and adb debugging is turned on.
Go to settings, about tablet. Then tap the build number at the bottom seven times and that will turn on developer options. Then in developer options, turn on oem unlocking and adb debugging.
Then run adb devices. It should return your tablet's serial number and 'device' If it shows the device 'unauthorized' (mine did the first couple of times) revoke ADB authorization and plug the tablet back in.
Then it is just adb reboot bootloader and then fastboot flashing unlock.
Click to expand...
Click to collapse
i was going to edit my post but oh well
i had fixed what i was looking for: i used snappy driver installer origin to update my android driver, android adb showed up in my sdio list and i installed the driver from there, that resolved my issue (stupid mistakes can happen)
Attached with this post are :
+ Stock boot of OOS12 ( C41) for Oneplus 8T+ 5G (T-Mobile KB2007)
+ Magisk patched boot of OOS12 (C41) for Oneplus 8T+ 5G (T-Mobile KB2007)
+ Modded stock recovery of OOS12 (C41) for Oneplus 8T+ 5G (T-Mobile KB2007) with ADB enabled, security disabled, ability to debug enabled and allow mock location by default.
Just flash in Fastboot mode as usual!
Hi! I'm not very up-to-speed. I just restored my phone to TMO android 11, I was running PixelExperience and I have run the EU rom, what post should I look to for "flash...as usual". I'm not sure what the normal process is. Thanks!
bookofjoshua said:
Hi! I'm not very up-to-speed. I just restored my phone to TMO android 11, I was running PixelExperience and I have run the EU rom, what post should I look to for "flash...as usual". I'm not sure what the normal process is. Thanks!
Click to expand...
Click to collapse
I don't really understand your question but these files are for OnePlus 8T+ 5G Stock OOS12 C41 only, so if u r on A11, then these files are no use for u bro.
LinhBT said:
I don't really understand your question but these files are for OnePlus 8T+ 5G Stock OOS12 C41 only, so if u r on A11, then these files are no use for u bro.
Click to expand...
Click to collapse
It says "just flash in fastboot as usual". I don't know what "as usual" means. I wasn't looking for info on using them with my phone, just what I need to look at for the flashing procedures as I have seen several different methods and requirements,.
bookofjoshua said:
It says "just flash in fastboot as usual". I don't know what "as usual" means. I wasn't looking for info on using them with my phone, just what I need to look at for the flashing procedures as I have seen several different methods and requirements,.
Click to expand...
Click to collapse
Ah, what I mean by "flash in fastboot as usual" is : just flash those files in fastboot mode with fastboot commands which is used to flash boot.img recovery.img.....etc. In this case, are "
+ fastboot flash recovery recovery.img
+ fastboot flash boot boot.img
or you may input option like :
+ fastboot --slot-all flash boot boot.img ( to flash boot.img into both boot slot A/B )
Just that, my friend!
LinhBT said:
Ah, what I mean by "flash in fastboot as usual" is : just flash those files in fastboot mode with fastboot commands which is used to flash boot.img recovery.img.....etc. In this case, are "
+ fastboot flash recovery recovery.img
+ fastboot flash boot boot.img
or you may input option like :
+ fastboot --slot-all flash boot boot.img ( to flash boot.img into both boot slot A/B )
Just that, my friend!
Click to expand...
Click to collapse
So by using those fastboot commands you'll be able to root the KB2007 if you are running 12 as long as your bootloader is unlocked as well as SIM unlocked? That's my current situation right now and was looking go root sometime soon
kevinco1 said:
So by using those fastboot commands you'll be able to root the KB2007 if you are running 12 as long as your bootloader is unlocked as well as SIM unlocked? That's my current situation right now and was looking go root sometime soon
Click to expand...
Click to collapse
True, if you are on OOS12 C41 ( TMO ) to be specific, then u can use the magisk patched boot image from my post to root your device using normal fastboot commands as mentioned!
LinhBT said:
Ah, what I mean by "flash in fastboot as usual" is : just flash those files in fastboot mode with fastboot commands which is used to flash boot.img recovery.img.....etc. In this case, are "
+ fastboot flash recovery recovery.img
+ fastboot flash boot boot.img
or you may input option like :
+ fastboot --slot-all flash boot boot.img ( to flash boot.img into both boot slot A/B )
Just that, my friend!
Click to expand...
Click to collapse
Thank you! I appreciate you taking the time to clear that up for me, and actually type the commands. I was originally flashing Roms to get access to my 5G radio, as I'm using it on Verizon towers, but after applying the latest update my phone connected to 5G so I may not even need it anymore
bookofjoshua said:
Thank you! I appreciate you taking the time to clear that up for me, and actually type the commands. I was originally flashing Roms to get access to my 5G radio, as I'm using it on Verizon towers, but after applying the latest update my phone connected to 5G so I may not even need it anymore
Click to expand...
Click to collapse
There's a guide to enable 5G and/or VoLTE for KB2007 also in our forum. But since u did it, congrats
I just got this device yesterday. Already sim unlocked and requested the bootloader unlock code. Since it's only day one, I haven't flashed the euro firmware/rom yet. Is it worth upgrading it to 12 and then simply rooting it. I don't mind running stock for a while, but I hear 12 is really that bad. Obviously it can't be too bad if you are using it. I am just hesitant on installing the update. What are your thoughts?
works beautifully
heyChristo said:
I just got this device yesterday. Already sim unlocked and requested the bootloader unlock code. Since it's only day one, I haven't flashed the euro firmware/rom yet. Is it worth upgrading it to 12 and then simply rooting it. I don't mind running stock for a while, but I hear 12 is really that bad. Obviously it can't be too bad if you are using it. I am just hesitant on installing the update. What are your thoughts?
Click to expand...
Click to collapse
not bad so far just more security . disabled pinch out hidden menu.. had to create code and use dialer to access hidden menu. i fastbooted this and now rooted have not tried recovery yet im afraid actually
So I converted mine to the EU version and then to the global version and updated to 12 via OTA. However I could not find the file prior to flashing so I couldn't pull it to the PC. Obviously I lose root on that full update. Can I flash this boot image to restore root or will that brick the device?
For those that want the latest C42 update with September security, find attached the stock boot image as well as the magisk patched image
Hey. Thanks for all your work. I'm rooted on stock kb2007. My OTA update to 41 is not working. Would flashing these before asking the system to update fix it, or are these for after you unroot and allow the update. I think the unroot is where I'm having trouble. I uninstalled Magsik and wiped cache for google play. The OTA still won't work. I'm sure there is every note on XDA about this, but I thought I'd ask here because I think I'm so close.
droidgreg said:
For those that want the latest C42 update with September security, find attached the stock boot image as well as the magisk patched image
Click to expand...
Click to collapse
you wouldnt have the last android modem img for android? thx in advance. i forgot to safe modem via msm tool before i converted to global smh
The real question is where can obtain the original firmware for C42? Haven't been able to find it anywhere online
kevinco1 said:
The real question is where can obtain the original firmware for C42? Haven't been able to find it anywhere online
Click to expand...
Click to collapse
There is no 100% confirmation that C42 was released as a full update and not incremental on C41.
If I'm already on Android 12, C41 unrooted than I don't need to do any other flashing except the magisk patched boot image from the post to root my device using normal fastboot?
What is the purpose of the modded stock recovery?
MustangLife03 said:
What is the purpose of the modded stock recovery?
Click to expand...
Click to collapse
The main reason is enabled adb access.
Having ADB enabled on the stock recovery can be really helpful if you are unlocked and rooted.
For example, removing problematic magisk modules.
Though there is unofficial TWRP for A12 which makes stock adb enabled a bit obsolete in this case.
But anyway thanks for LinhBT for compiling it.