Hello all. I have owned my shield for 2 years now and for the first time attempted to root it. I made it to the twrp image and instead of loading the needed option to root it stayed on the nvidia image. I am guessing the twrp is old and there for not 8.0 twrp. At anyrate now ehen I turn on my shield it says I need to relock the boot loader and that I am not protected. My question is how do I fix this or do I need to ? Does anyone know where to find the current twrp and do I need to relock the bootloader and start over or can I finish from here ? Will I screw anything up keeping it unlocked ?
First of all, what experience version are you on?
And the warning that comes up when you turn on your shield is just a warning, because you have unlocked the bootloader.
You don't need to worry about it.
If you root, you wanna leave the bootloader unlocked.
mLgz0rn said:
First of all, what experience version are you on?
And the warning that comes up when you turn on your shield is just a warning, because you have unlocked the bootloader.
You don't need to worry about it.
If you root, you wanna leave the bootloader unlocked.
Click to expand...
Click to collapse
Thank you for responding ....
I am on 8.0 oreo
elderbrain said:
Thank you for responding ....
I am on 8.0 oreo
Click to expand...
Click to collapse
For Oreo there is only an experimental twrp, but you don't really need twrp to root.
You can use this guide for Nvidia Experience 7.2.3, which is Android 8.0 Oreo.
https://forum.xda-developers.com/shield-tv/general/guide-root-nvidia-shield-experience-t3882254
So to be sure, you are on Android 8.0 Oreo (Nvidia Experience 7.2.3) Correct?
And not Android 9.0 Pie (Nvidia Experience 8.0)
correct. I have a nvidia shield running 8.0 oreo. do I start from where I left off or from the start ? At this point no command workd for me and the shield is not detected. I have a brand new usb cord plugged in and all things enabled.....power shell says the commands i cut and pasted from your link are not correct commands and the minimal and fast boot says I have no device detected.....so at this point non of this matters untill I can fix this. whats the best command prompt to get this going ?
elderbrain said:
correct. I have a nvidia shield running 8.0 oreo. do I start from where I left off or from the start ? At this point no command workd for me and the shield is not detected. I have a brand new usb cord plugged in and all things enabled.....power shell says the commands i cut and pasted from your link are not correct commands and the minimal and fast boot says I have no device detected.....so at this point non of this matters untill I can fix this. whats the best command prompt to get this going ?
Click to expand...
Click to collapse
I'm using minimal adb and fastboot https://forum.xda-developers.com/showthread.php?t=2317790
Use the shortcut it makes when installed to open a command prompt.
What version of the shield do you have?
And are you booted into the bootloader?
I have the 16 gb running 8.0 oreo. I have unlocked the bootloader yes. I did every step up to loading the twrp. I used a you tube video by TT Technology. Made it to the last and final step. As of now my shield keeps disconnecting and reconnecting when connected to through usb so it does not detect any devices. I get lucky for a moment but it then stops recognizing the shield. Whats odd is that the shield is listed and I can open it and access all the storage including the mounted through the computer even when the connection drops. Right now untill i fix this issue everything else is moot.
I didn't ask if you unlocked the bootloader.
I'm asking if you are able to get into it where you do the fastboot commands?
Ah sorry. No, no commands work and I am not able to load the bootloader. It says deamon failed to start and it does not see the shield as a connected device.
elderbrain said:
Ah sorry. No, no commands work and I am not able to load the bootloader. It says deamon failed to start and it does not see the shield as a connected device.
Click to expand...
Click to collapse
If you own a SHIELD Controller
Unplug SHIELD TV.
Connect SHIELD controller to SHIELD TV with a USB cable (use port closest to HDMI).
While holding the A and B buttons at the same time, connect power to SHIELD TV.
If you do not own a SHIELD controller
Unplug SHIELD TV.
Connect a USB keyboard directly to SHIELD TV (use port closest to HDMI)
While holding the "A" and "B" keys down at the same time, connect power to SHIELD TV.
Once you enter Fast Boot mode, on the keyboard use the "X" and "Y" keys to navigate the menu and "A" to select
Click to expand...
Click to collapse
This will get you into the bootloader, and you should be able to use fastboot commands
I tried both keyboard and controller and this is not do anything. When I fire up the command prompt two things happen I get this message:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
adb server version (40) doesn't match this client (36); killing...
* daemon started successfully *
error: no devices/emulators found.
Or it finds the shield and says its offline. My usb connection has been fixed. I was able to run a game through game stream to my pc and even watched a movie with my computers dvd player on my tv using wiredxd. So I know i have a solid connection. I am clearly doing something wrong here as I clearly am connected to the pc now.
elderbrain said:
I tried both keyboard and controller and this is not do anything. When I fire up the command prompt two things happen I get this message:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
adb server version (40) doesn't match this client (36); killing...
* daemon started successfully *
error: no devices/emulators found.
Or it finds the shield and says its offline. My usb connection has been fixed. I was able to run a game through game stream to my pc and even watched a movie with my computers dvd player on my tv using wiredxd. So I know i have a solid connection. I am clearly doing something wrong here as I clearly am connected to the pc now.
Click to expand...
Click to collapse
Oh my bad, I didn't think you were able to boot.
Have you enabled usb debugging on the shield in the developer options?
Anyways, that error is usually because of using an out of date adb.
try this minimal adb and fastboot
https://www.androidfilehost.com/?fid=745425885120698566
Yes. I have made sure all 3 possible options where enabled, from developer options to usb debugging. I even got the message to allow it always on this device. I have full access to the shield through usb and it appears in my DM.........I have tried all three versions I can find for minimal fastboot. v 14.1......1.4.3 and the one you said to try 1.4.2. All have the same message. It just either does not detect a device or it says its offline. I have pretty much thrown in the towel at this point as all options have been attempted and hours of googling where wasted. I really have no idea where to go now. I tried resetting the shield a few times.....then tried revoking usb and re enabling and nothing will get it to connect to the deamon. Thank you for all the help. I appreciate you trying
In what state is your shield currently ? From what I read in your posts , your shield doesn't currently boot ? You said it's stuck at the nvidia logo. I am no expert, but if you really are stucked at the nvidia logo, until you enter fastboot mode properly, ADB won't be of any help. If that's the case , then follow any of the methods in post #10 of this thread to properly enter fastboot mode. From there you'll be able to fix things. Since it was you that unlocked the bootloader then it means that the cable, the drivers and your installation of ADB were all in working order at that moment. Now has to why you are stucked on the nvidia logo , you didn't mention which step of which guide you were following when that happened , but at the very least your recovery.img or boot.img have issues. If it's the recovery (twrp) then you're using a wrong one. I don't think a bad recovery.img will let you get as far as the nvidia logo so I doubt that's the issue here. Your boot.img seems corrupted and cannot proceed past the nvidia logo, so perhaps you tried a pre-patched boot.img that isn't the correct one for your current system version or you patched it yourself with a magisk manager that doesn't properly patch the boot.img . I would suggest that next time you type "fastboot boot boot.img" (boot instead of flash) so that you at least try the boot image before you go on and flash an untested file (not a blame, if its the case then you followed a guide that didn't mention this precaution first). Anyways , if you're stuck at the nvidia logo , then what you should do first is try to flash a clean boot.img . Go to nvidia's site and grab the proper recovery for your system version (7.2.3 you said) by scrolling down to Recovery Images , and first choosing your correct hardware and next the image you need. Extract these files in the same folder as your ADB installation so that you can just click "flash-all.bat" and it will fix your shield (it will flash the correct recovery.img and boot.img). Of course this has to be done while you are in fastboot mode , so it comes back to this, get your device into fastboot mode properly. Any USB keyboard you have around the house should work to do this :
Connect a USB keyboard directly to SHIELD TV (use port closest to HDMI)
While holding the "A" and "B" keys down at the same time, connect power to SHIELD TV. --- I add this : Hold the keys until something happens. Release them only once you reach fastboot mode or the nivida logo and try it with every usb port before ruling it doesn't work.
Once you enter Fast Boot mode, on the keyboard use the "X" and "Y" keys to navigate the menu and "A" to select
Oh, if you get into fastboot mode and the commands still give you errors about client versions not matching, that might be an issue with other software running on your pc, but we'll stay out of this for now.
Roamin64 said:
In what state is your shield currently ? From what I read in your posts , your shield doesn't currently boot ? You said it's stuck at the nvidia logo. I am no expert, but if you really are stucked at the nvidia logo, until you enter fastboot mode properly, ADB won't be of any help. If that's the case , then follow any of the methods in post #10 of this thread to properly enter fastboot mode. From there you'll be able to fix things. Since it was you that unlocked the bootloader then it means that the cable, the drivers and your installation of ADB were all in working order at that moment. Now has to why you are stucked on the nvidia logo , you didn't mention which step of which guide you were following when that happened , but at the very least your recovery.img or boot.img have issues. If it's the recovery (twrp) then you're using a wrong one. I don't think a bad recovery.img will let you get as far as the nvidia logo so I doubt that's the issue here. Your boot.img seems corrupted and cannot proceed past the nvidia logo, so perhaps you tried a pre-patched boot.img that isn't the correct one for your current system version or you patched it yourself with a magisk manager that doesn't properly patch the boot.img . I would suggest that next time you type "fastboot boot boot.img" (boot instead of flash) so that you at least try the boot image before you go on and flash an untested file (not a blame, if its the case then you followed a guide that didn't mention this precaution first). Anyways , if you're stuck at the nvidia logo , then what you should do first is try to flash a clean boot.img . Go to nvidia's site and grab the proper recovery for your system version (7.2.3 you said) by scrolling down to Recovery Images , and first choosing your correct hardware and next the image you need. Extract these files in the same folder as your ADB installation so that you can just click "flash-all.bat" and it will fix your shield (it will flash the correct recovery.img and boot.img). Of course this has to be done while you are in fastboot mode , so it comes back to this, get your device into fastboot mode properly. Any USB keyboard you have around the house should work to do this :
Connect a USB keyboard directly to SHIELD TV (use port closest to HDMI)
While holding the "A" and "B" keys down at the same time, connect power to SHIELD TV. --- I add this : Hold the keys until something happens. Release them only once you reach fastboot mode or the nivida logo and try it with every usb port before ruling it doesn't work.
Once you enter Fast Boot mode, on the keyboard use the "X" and "Y" keys to navigate the menu and "A" to select
Oh, if you get into fastboot mode and the commands still give you errors about client versions not matching, that might be an issue with other software running on your pc, but we'll stay out of this for now.
Click to expand...
Click to collapse
I have all but gave uop at this point, but to answer your question. My shield works and runs it is just in the state where the bootloader is unlocked and I get the warning. I have attempted the instructions before, holding down the a and b keys on both the game controller and a wired keyboard and it does nothing. I agree that the twrp is not current and that I need the proper files. As of now my shield is just not recognized period. That is why holding down the aand b keys does not work ( IE it in the command prompt it says shield is offline or it sees it and when I enter fastboot it just says waiting for device and does nothing more. So half way through it looses connection to the shield ) Untill I can get the shield to be recognized none of these instructions matter. As of now I have decided to give up and maybe in a while try again. I would like to completely restore my shield to the state it was in so I can start from scratch. That is what I am focusing on now, but untill my shield is recognized I dont think even that is possible. Thanks for your post. I appreciate all the help all of you have offered.
Impossible d'accéder au recovery
Bonjour j'ai fait une erreur de flashing, le fimware de NVIDIA Shield TV n'était pas bon, donc le logo NVIDIA reste bloqué, j'ai essayé de faire a et b mais impossible d'accéder au booloader et au recovery comme faire ?
Related
I have searched and couldn't find a fastboot thread. So here it is.
I found out fastboot is working on Linux.
Bad news is Windows seems to need another driver for fastboot.
Please help look for a windows driver or make one.
The fastboot commands all seem to work fine.
Here you guys go! Enjoy.
Code:
[SIZE=5][SIZE=3][SIZE=5][SIZE=3]adb reboot-bootloader
fastboot -i 0x1949 command_here[/SIZE][/SIZE][/SIZE][/SIZE]
Just noticed pokey9000 said this but it was overlooked.
pokey9000 said:
That's it. And you're running fastboot as "fastboot -i 0x1949 your_command_here", and you have udev set to allow permissions for that VID (or are running as root) in Linux?
Click to expand...
Click to collapse
Thank you.
Still don't believe me, look at the last picture.
I'm having issues with some commands. Please test it out and enjoy!
shimp208 said:
In the Fire TV section a fastboot cable was created by splicing two USB A to B cables together, so that the A to A ends were together which when connected from your computer to the Fire TV on bootup put the device in fastboot mode, in the process then your computer recognized (Running Windows 8 was the example given) the device and installed the proper drivers. Since the devices are similar, a potential solution would be use the cable, have the computer recognize it and install the drivers, then backup the drivers, and share them here for others to use.
Click to expand...
Click to collapse
I'm quite sure the cable isn't the issue. Also that's just it, I can't get windows to recognize it or find much info about it. The adb driver for the device isn't enough I guess. The funny thing is windows says it's working properly as 'Kindle' for a little while when you plug it in (while in bootloader) then device manager refreshes and reports 'cannot start'. I tried launching 'fastboot devices' many times but still nothing. I think it needs a software fix and not a hardware one but I have no past experience using fastboot. So... noob alert.
btw the driver windows tries to use is ms_comp_mtp(Generic driver installed=true) and adb uses the Amazon one on the fourm here.
DevNode status Value:
01802400
DN_HAS_PROBLEM
DN_DISABLEABLE
DN_NT_ENUMERATOR
DN_NT_DRIVER
Also Bus reported device description Value:
fastboot
VID=1949 & PID=000C
(0x1949 && 0x000c)
Current Driver files:
\system32\DRIVERS\UMDF\WpdMtpDr.dll
\system32\DRIVERS\winusb.sys
\system32\DRIVERS\WUDFRd.sys
\system32\WpdMtp.dll
\system32\WpdMtpUS.dll
We need someone good on this.
I have a problem
I don't think there's ever been a question of getting into fastboot mode by using the adb reboot-bootloader command.
The issue is how to enter fastboot if the device is semi-bricked.
The device has source in the original bootloader to boot into fastboot mode if both volume buttons are pressed while powering on the device. But this has since been altered and now will only work if the device is unlocked.
Hashcode said:
I don't think there's ever been a question of getting into fastboot mode by using the adb reboot-bootloader command.
The issue is how to enter fastboot if the device is semi-bricked.
The device has source in the original bootloader to boot into fastboot mode if both volume buttons are pressed while powering on the device. But this has since been altered and now will only work if the device is unlocked.
Click to expand...
Click to collapse
Is flashing the stock .bin file any different than doing a factory reset?
I am bricked, have root, have adb, can get fastboot using adb reboot-bootloader in windows 8. I also have a Linux box if necessary.
saphi95 said:
I have a problem
Click to expand...
Click to collapse
I would recommend taking a look at this thread here, specifically the "Fixing No Permissions Error" section which should allow you to fix the problem your encountering.
dcoig1 said:
Is flashing the stock .bin file any different than doing a factory reset?
I am bricked, have root, have adb, can get fastboot using adb reboot-bootloader in windows 8. I also have a Linux box if necessary.
Click to expand...
Click to collapse
Fastboot works with win8? Not with win7.1 If you have fastboot working with win8 please go to device manager (when your in the bootloader) click properties on the device then look for what driver it uses.
Hashcode said:
I don't think there's ever been a question of getting into fastboot mode by using the adb reboot-bootloader command.
The issue is how to enter fastboot if the device is semi-bricked.
The device has source in the original bootloader to boot into fastboot mode if both volume buttons are pressed while powering on the device. But this has since been altered and now will only work if the device is unlocked.
Click to expand...
Click to collapse
My main reason is to get fastboot working with windows. I just can't. Linux seems to work with fastboot but I can't access it via windows.
Just uninstall the kindle driver and replace it with the generic fastboot one
hello all,
i've kindle fire hdx 7" , no adb, grey screen logo then shutdown and goes to black screen.
when connected using cable, it show new devices... QHSUSB_BULK and sometime unknown devices.
press hold power button and volume up only go to recovery mode, but cannot recovery the system..
always go to grey screen logo...
sorry for my bad english language...
hope all of you, understand what i mean here
i need solution for fix the problem soon. thanks
I think all that works is reboot into fastboot mode. Windows 8 says no drivers are loaded. I tried a command (can't remember what) and it just went out to lunch so... I guess windows 8 isn't working either. Only to put the device in fastboot.
there are three oem commands:
oem device-info
oem idme
oem relock
Click to expand...
Click to collapse
but it doesn't support oem unlock so there must be another way of unlocking the bootloader, when you try some of the commands the device returns "not allowed for locked hw". Does anyone know what the "hw" is ?
hw = hardware?
MaximilianOzora said:
hello all,
i've kindle fire hdx 7" , no adb, grey screen logo then shutdown and goes to black screen.
when connected using cable, it show new devices... QHSUSB_BULK and sometime unknown devices.
press hold power button and volume up only go to recovery mode, but cannot recovery the system..
always go to grey screen logo...
sorry for my bad english language...
hope all of you, understand what i mean here
i need solution for fix the problem soon. thanks
Click to expand...
Click to collapse
Read up on this bud.
Hi,
I have a bricked kindle hdx 8.9 that stops at "Kindle Fire" boot screen. I am a newbie at these things.
Just discovered that it still respond to some adb queries. Sounds like there is still hope to recover... Could it be the bootloader is messed up? Anyway to reload an image boot file to repair?
Also "fastboot reboot-bootloader" puts it into fastboot mode...with the status "ready"....and i just dont know how to proceed. Any one can help?
uhg
Facepalm
just back a little: was rooted in April but with subsequent amazon auto updates - didn't have su status. But I was able to load apps & files, installed vpns, quite a few docs,mp4 files, etc. Not really using much of the new freedom or whatever was left of it... Nothing exciting.
Was working well until one fine sunday afternoon, just 2 weeks ago when it just simply stopped after rebooting from a previous low battery charge. Was told it could be an interrupted routine update when the battery power just fell below threshold - but thot it wouldn't have erase the previous image before the new update is effective. Or it could possibly be a deleted file that is related to the booting process as I did a bit of clean up prior to the last reboot?
In the meantime, I did some adb shell/pull to explore or extract the files, photos,etc in /sdcard & other places back to my PC just in case they were not backup by the cloud. Maybe it was not bricked...but just lost a boot file or something...
In a bad situation, have absolutely zero ADB access as my build.prop is botched (bad permissions) and I did a factory reset in hopes of recovering. There is a "fastboot cable" on amazon that says it will reboot a hdx into fastboot mode, but I'm unsure of it's legitimacy. Help?
here try
Tumbtack said:
In a bad situation, have absolutely zero ADB access as my build.prop is botched (bad permissions) and I did a factory reset in hopes of recovering. There is a "fastboot cable" on amazon that says it will reboot a hdx into fastboot mode, but I'm unsure of it's legitimacy. Help?
Click to expand...
Click to collapse
This thread.read read read http://forum.xda-developers.com/showthread.php?t=2588608
I don't quite understand. Why is a special cable required for this? What makes it any different from the standard one that comes with the device?
I don't know if this will add anything to the discussion...but I can confirm fastboot is working on Ubuntu 14.04. I am using a kindle fire HDX 7" and it detects it on devices..and most commands work. Sometimes the terminal must be closed and reopened for commands to go through..
fastboot oem unlock works..or rather it says "Okay" but I'm unable to flash anything.
I have three Shield TV boxes (all stock-rom 2.1) and tried to flash the new Vulkan Update 3.0. I was successful on two of them by doing the follwwing steps:
1. Connected via USB to PC
2. Activated Developer-Mode and then ADB (actually I had that done long time before)
3. Booted into Bootloader using ADB-command
4. Unlocked Bootloader using Fastboot-command (all apps and date wiped out)
5. Reboot (after that had to setup Shield TV and repeat steps 1 and 2)
5. Booted again into Bootloader
6. Flashed TWRP-image using Fastboot-command
7. Reboot
8. Booted again into Bootloader
9. Selected "Boot recovery kernel" (= TWRP)
10. Installed Vulkan 3.0 Update Image via TWRP (Zip-File)
11. Reboot
Done.
It worked perfectly fine on two of my shield TV boxes. But I have problems with the third one: Everytime I enter bootloader I do not have any video. The screen is totally blank (black screen). I can use Fastboot-commands from my PC though (e.g. unlocking Bootloader and flashing TWRP seems to work since the output on the PC tells me so). But since I absolutely do not see anything I cannot enter TWRP and use it for flashing the Vulkan Update 3.0 then. Even more: Not being able to enter (or at least "see" anything in) bootloader and TWRP will make it hard to administrate the box in the future.
I meanwhile tried three different displays - no difference. I also tried factory restore and flashing the older dev-images of 2.1, 2.0 - and even 1.3 and 1.4. I was hoping these images would somehow repair the bootloader (since I suspect it is broken, showing no screen). But they obviouly did not. Bootloader stayed black every time I entered it anyway what firmware I was using. Funny thing is that booting into Android TV itself just works fine all the time. I have the NVidia logo, the start animation and - of course - the Launcher screen with all apps. So I can use the shield box. Just the bootloader seems to show nothing (it is responding to fastboot-commands, but only shows blank screen). Therefore I cannot upgrade to Vulkan 3.0 or do any administrative things that require to "see" the bootloader or TWRP .
Any ideas how to repair it?
Thanks in advance for any help!
Ok, after some trying I was able to boot into stock recovery mode: I connected the Shield TV box via USB with my PC and at the DOS prompt I entered "adb reboot recovery". When I saw the Android-Symbol I pressed the power button on the Shield TV box for 2 seconds and then entered the recovery menu. I then selected ADB sideloading and on my PC I typed "adb sideload name.zip" (whereas "name.zip" was the name of the Vulkan-3.0-Image-ZIP-File). Then flashing went well. Now I am on 3.0 and I can begin setting up all apps again.
However, I once again tried entering the bootloader menu but it still just shows a blank screen. So that is still broken. Does anybody know how I could get the bootloader to display anything again?
Regards,
FantasticN
Something new, strange...
Izsūtīts no manas Nokia 3310 используя бесплатную xda app
You could try flashing the weird box with the factory images ( https://developer.nvidia.com/shield-open-source ), maybe it's somehow on an older bootloader that has a bug, or it's partially corrupted. You don't need to see anything in fastboot to flash the factory images. Heads up, they will wipe your device (unless you remove the -w switch from the batch file that initiates the flashing process).
So i wanted to create a key mapping for android over my android game using my xbox one controller but all the apps that allow it require rooting. So i quickly came here to see if it was rootable and surely my model was listed. LG k20 Plus MP260, So i go and download adb tap my build number, do the usb debugging, allow oem unlocking, downloaded the Lg drivers, moved the recovery.img to the adb file folder directory, moved the super user Zip file and the no-verity-opt-encrypt-5.1.Zip to the internal storage of the phone. Then run Shift+ Right click adb reboot bootloader using Windows powershell command line and i'm in fastboot mode (I can also just power the phone off and hold the volume down button and plug usb into phone to get into it). So i use fastboot devices to make sure the computer recognized my device and it does. Note: (the bootloader is already unlocked) Then i use fastboot flash recovery recovery.img and it flashes. what happens next is well. I use fastboot reboot and well i get "Your device software cannot be checked for corruption lock the bootloader" and below that it say "PRESS THE POWER KEY TO CONTINUE" i press the power key and it boots up normally. In the video's i've watched they say it will boot into the system twrp and my phone is not doing this. I'm willing to let someone team view me and skype me so we can work this out together and i'm even willing to pay 20$ if we can get this done. Please message me asap
I have the exact same problem. Did you ever figure it out?
Bumping an oldish thread, because this still exists. Custom recovery isn't very useful when you can't get to it without reflashing it every time.
dbsc said:
Bumping an oldish thread, because this still exists. Custom recovery isn't very useful when you can't get to it without reflashing it every time.
Click to expand...
Click to collapse
Did you find a solution? I've been fighting my LG K20 plus metroPCS for over 2 weeks. It won't go into download mode or recovery. In recovery it skips over the reset page. I think the phone is possessed lol.
I'll be making a video for this with the 7 inch tablet on Nov. 29th or 30th (depending on the time I have)
General Disclaimer: I'm not responsible if you brick your tablet. This is how I did it personally as other methods here didn't work for me. I have yet to test this method on a 7 inch, also do not have access to the Surf variants. This has only been tested on the 10.1 inch with the keyboard. Will update when I test with the 7 inch.
What's Needed:
MTK Fastboot Drivers: https://online.mediatek.com/Public Documents/MTK_Android_USB_Driver.zip
Magisk Manager Canary: https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
Stock Boot Image: https://forum.xda-developers.com/wa...eral/stock-stock-backups-images-otas-t3998227
ADB and Fastboot: https://www.xda-developers.com/what-is-adb/
Prerequisites:
Personally, I had issues getting my PC to recognize the tablets in Fastboot mode. The drivers wouldn't install. This might be optional for some of you, but I thought I'd include it just in case.
Installing MTK Fastboot Drivers from the link above
If you plugin your device in fastboot mode and your PC doesn't recognize it, follow these steps. If it did, skip this part.
1.) Download the drivers above and unzip the Zip file somewhere on your PC (desktop or My Documents is easiest)
2.) Boot your Tablet into Fastboot Mode by holding Vol + and Power, then select Fastboot from the Menu
*NOTE* There is a bug with these tablet's that the volume buttons are mislabeled. Really dumb, but I guess that's why they were 55 bucks for the 10 inch on black friday
3.) Plug the device into your PC and open Device Manager by pressing WinKey+R and typing devmgmt.msc, hit Enter
4.) If there's an Other Device listed called Android, follow these steps. If it isn't there, follow the next set of steps
5.) Open a Command Prompt window as Admin and type the following command
Code:
bcdedit.exe /set nointegritychecks on
6.) Hit enter, then restart your PC
7.) Once the PC is restarted, make sure your tablet is connected in Fastboot mode and open Device Manager again
8.) Right click Android under Other Devices and select Update Drivers
9.) Click the Browse my Computer for driver software button and select the MTK Folder you extracted from the download link above
10.) From there, you can open command prompt, type fastboot devices and see if your tablet shows up and move on to root!
Unlocking your Bootloader
From here, you can unlock your bootloader very easily to Root your device
This will wipe all data off the tablet!
0.) Enable OEM Unlock and USB Debugging on the tablet by going to Settings->About and tap Build Number 7 times. From here, enter the new Developer Options that unlock and turn on OEM Unlock and USB Debugging.
1.) Boot your tablet into Fastboot mode and connect it to your PC
2.) Open a Command Prompt window and type the following command, then hit enter
Code:
fastboot flashing unlock
3.) Follow the instructions on screen to unlock your bootloader
4.) Now Boot your device and we'll move on to making a rooted Boot Image
Creating a Rooted Boot Image with Magisk Manager
0.) Make sure you already have Wifi setup and connected before the first time you open Magisk Manager on your device! Make sure it auto connects as well
1.) Download Magisk Manager Canary from the link above
2.) Install it to your device
3.) Download boot Image from the Stock Boot Image part of the Prerequisites above and put the boot.img on your devices internal memory
4.) Open Magisk Manager and select Install Magisk
5.) Select Patch File and select the boot.img from your internal storage
6.) Once its done patching the image, take magisk_patched.img from the downloads folder of your device and move it onto your PC
7.) Boot your tablet into Fastboot mode and plug it into your PC
8.) Open Command Prompt and type the following command and hit enter (make sure you know your magisk_patched.img file location)
Code:
fastboot flash boot magisk_patched.img
9.) Reboot the device and you'll be Rooted!
Optional Steps like Modules and Debloating
My basic debloat script: https://forum.xda-developers.com/wa...s-general/root-walmart-bloat-remover-t4011639
Will be testing GSI roms on the spare 7 inch and will list those here
Recommended Magisk Modules:
Viper4Android Legacy
FDE.AI
MagiskHide Props Config
Systemless Hosts
Youtube Vanced Black
Magisk Setting to Enable:
Magisk Hide
Rename Magisk Manager App (keeps app from detecting magisk root)
Credits:
Myself for this root method @byproxy for reminding me to add the steps for OEM Unlock and enabling wifi before opening Magisk Manager for the first time
I'll start this off saying i'm an amateur at this, but I cannot for the life of me get an option to show up in magisk to patch the boot image even though it's on my 7" tablet. Any thoughts?
The bootloader was unlocked and it was successful so that's not the issue.
Are you online? I had the same problem.
Xavster2 said:
I'll start this off saying i'm an amateur at this, but I cannot for the life of me get an option to show up in magisk to patch the boot image even though it's on my 7" tablet. Any thoughts?
The bootloader was unlocked and it was successful so that's not the issue.
Click to expand...
Click to collapse
Xavster2 said:
I'll start this off saying i'm an amateur at this, but I cannot for the life of me get an option to show up in magisk to patch the boot image even though it's on my 7" tablet. Any thoughts?
The bootloader was unlocked and it was successful so that's not the issue.
Click to expand...
Click to collapse
Sorry, been a busy few days, but make sure you're connected to Wifi, close Magisk Manager, then reopen it and you'll be good to go!
Onn 8" walmart tablet
I purchased the 8" Onn walmart tablet second hand from a store called dirt cheap. Box didnt look to be opened but it had been. The tablet had been setup with someones gmail account that i do not know. The tablet was for a 4yo girl to use to learn preschool. Is there just any simple way to remove this google FRP lock ? I dont care if i lose the info on it as its not mine. I just want her to be able to use the tablet. Any help would be much appreciated please
CoachDad said:
I purchased the 8" Onn walmart tablet second hand from a store called dirt cheap. Box didnt look to be opened but it had been. The tablet had been setup with someones gmail account that i do not know. The tablet was for a 4yo girl to use to learn preschool. Is there just any simple way to remove this google FRP lock ? I dont care if i lose the info on it as its not mine. I just want her to be able to use the tablet. Any help would be much appreciated please
Click to expand...
Click to collapse
Forced factory reset should do it. There is small pin hole near the power button. I believe pressing this hidden button(with a Sim card ejector, or paper clip).
If pressing does not do anything. Maybe press the button then hold power button too
mrmazak said:
Forced factory reset should do it. There is small pin hole near the power button. I believe pressing this hidden button(with a Sim card ejector, or paper clip).
If pressing does not do anything. Maybe press the button then hold power button too
Click to expand...
Click to collapse
Thank you for responding so fast. I've boot into recovery mode /wiped everything...its back to factory. The pinhole reset button does nothing other than reboot it . Ive tried all combos to with the reset button but nothing. Also i've read that its possible to use odin? if i can get it into download mode.
Ive downloaded the stock rom posted on an sdcard wondering if i can possibly update in recovery mode? Im sorta a newb at this stuff. I've been reading for 4 days on this matter. I've practiced a root on an old tablet with success. I guess at this point unless i can sell it as is giving the customer that it has this frp lock on it. If the know how to fix it so be it. Im not sure there is a working solution for frp bypass on these tablets.
CoachDad said:
Thank you for responding so fast. I've boot into recovery mode /wiped everything...its back to factory. The pinhole reset button does nothing other than reboot it . Ive tried all combos to with the reset button but nothing. Also i've read that its possible to use odin? if i can get it into download mode.
Ive downloaded the stock rom posted on an sdcard wondering if i can possibly update in recovery mode? Im sorta a newb at this stuff. I've been reading for 4 days on this matter. I've practiced a root on an old tablet with success. I guess at this point unless i can sell it as is giving the customer that it has this frp lock on it. If the know how to fix it so be it. Im not sure there is a working solution for frp bypass on these tablets.
Click to expand...
Click to collapse
This is an mtk device not Samsung. So there is no Odin or download mode. There is spflash tool, and preloader.
And if you flash firmware (with default frp partition) then frp lock is cleared.
But you will have to find that file. It maybe in the stock firmwares that are shared, I do not know.
EDIT:
i was having issues but figure it out. maybe it should be so common knowledge that it shouldn't need to be included as a step, but since i don't do this THAT often i didn't think about it and it took me a bit to figure out why i was having issues.
once you get your computer to recognize your device (mine did without needing to mess with any drivers) you need to first make sure to got into the tablet settings -> about and then tap on the build number 7 times to access developer options. then you need to go into developer options and turn on OEM Unlocking & USB Debugging.
THEN follow the guide to unlock bootloader.
then (since the tablet is factory reset once you unlock) do the above AGAIN to turn USB Debugging back on after you reboot.
also note that you need to have an internet connection on the tablet to utilize magisk. once you got all that square, then continue on with steps for full root.
hope that helps!
byproxy said:
EDIT:
i was having issues but figure it out. maybe it should be so common knowledge that it shouldn't need to be included as a step, but since i don't do this THAT often i didn't think about it and it took me a bit to figure out why i was having issues.
once you get your computer to recognize your device (mine did without needing to mess with any drivers) you need to first make sure to got into the tablet settings -> about and then tap on the build number 7 times to access developer options. then you need to go into developer options and turn on OEM Unlocking & USB Debugging.
THEN follow the guide to unlock bootloader.
then (since the tablet is factory reset once you unlock) do the above AGAIN to turn USB Debugging back on after you reboot.
also note that you need to have an internet connection on the tablet to utilize magisk. once you got all that square, then continue on with steps for full root.
hope that helps!
Click to expand...
Click to collapse
I did not realize I didn't include that step. Total noob mistake when typing a tutorial up for android. I do this almost daily at work, so I forget to include it
CoachDad said:
Thank you for responding so fast. I've boot into recovery mode /wiped everything...its back to factory. The pinhole reset button does nothing other than reboot it . Ive tried all combos to with the reset button but nothing. Also i've read that its possible to use odin? if i can get it into download mode.
Ive downloaded the stock rom posted on an sdcard wondering if i can possibly update in recovery mode? Im sorta a newb at this stuff. I've been reading for 4 days on this matter. I've practiced a root on an old tablet with success. I guess at this point unless i can sell it as is giving the customer that it has this frp lock on it. If the know how to fix it so be it. Im not sure there is a working solution for frp bypass on these tablets.
Click to expand...
Click to collapse
I was able to remove FRP lock on one of mine by flashing the stock rom with SP Flash Tool. I used the full wipe and download selection with every partition selected including boot.
no worries! i didn't think about it either until i was having issues. thanks for the tutorial... it was super helpful!! btw it definitely works on the 8" tablet.
Hello! I'm new to all of this, but what I'm trying to accomplish is removing the Google account from this tablet and putting a new image on the ONA19TB002, ONA19TB003, ONA19TB007, Surf 7 and 10 tablets. I followed all of the steps as far as installing the drivers. I had to go through hoops to get the MediaTek Drivers installed, but I have a "warning" cone by it. I haven't been able to find any resolution to this. Any help would be appreciated. I' have a Windows 10 64-bit system that I'm using and the tablet I'm specifically working on at the moment is the ONN ONA19TB003 tablet. The tablet is not being recognized by my laptop when I run the 'fastboot devices' command in PowerShell. Is there something that I'm missing? Any help would be appreciated.
'Quis said:
Hello! I'm new to all of this, but what I'm trying to accomplish is removing the Google account from this tablet and putting a new image on the ONA19TB002, ONA19TB003, ONA19TB007, Surf 7 and 10 tablets. I followed all of the steps as far as installing the drivers. I had to go through hoops to get the MediaTek Drivers installed, but I have a "warning" cone by it. I haven't been able to find any resolution to this. Any help would be appreciated. I' have a Windows 10 64-bit system that I'm using and the tablet I'm specifically working on at the moment is the ONN ONA19TB003 tablet. The tablet is not being recognized by my laptop when I run the 'fastboot devices' command in PowerShell. Is there something that I'm missing? Any help would be appreciated.
Click to expand...
Click to collapse
Personally, I avoid PowerShell at all costs. This kinda stuff has always just seemed to work better with CMD.exe instead of Powershell.
These tablets are kind of a nightmare for this. If you've done the mediatek drivers and still have the warning cone icon, I'm not sure what's next as I haven't hit that wall myself. All I can maybe recommend is right click delete drivers in Device Manager, then start over with the driver install
Removing the Google Account would be needing a FRP Bypass. Someone above stated "I was able to remove FRP lock on one of mine by flashing the stock rom with SP Flash Tool. I used the full wipe and download selection with every partition selected including boot. " so if you can get it recognized, try that
KaptinBoxxi said:
Personally, I avoid PowerShell at all costs. This kinda stuff has always just seemed to work better with CMD.exe instead of Powershell.
These tablets are kind of a nightmare for this. If you've done the mediatek drivers and still have the warning cone icon, I'm not sure what's next as I haven't hit that wall myself. All I can maybe recommend is right click delete drivers in Device Manager, then start over with the driver install
Removing the Google Account would be needing a FRP Bypass. Someone above stated "I was able to remove FRP lock on one of mine by flashing the stock rom with SP Flash Tool. I used the full wipe and download selection with every partition selected including boot. " so if you can get it recognized, try that
Click to expand...
Click to collapse
Ok, thank you! This is a shot in the dark, but in order for ADB to work, USB debugging has to be enabled. I can't do that as the tablet is locked by FRP and I have looked countless times on Google and MSN to see if it's possible. Do you have any tips for that?
I don't know what I'm doing wrong, but for some reason I can't seem to get. The tablet to stay in fastboot mode. It just says waiting for device.
will this root onn 8 inch tablet running android 9
soateufel said:
I don't know what I'm doing wrong, but for some reason I can't seem to get. The tablet to stay in fastboot mode. It just says waiting for device.
Click to expand...
Click to collapse
Sorry for late reply. Been away from home with work. When fastboot mode indicates "waiting for device," it generally means that your device is not properly communicating with your PC or laptop. This is nearly always due to missing or incorrect drivers 9n your computer. There are several comprehensive guides here on XDA for installing necessary ADB & Fastboot drivers.
installed magisk manager on onn 8 and also have img zip but win i go to patch it magisk manager crashes
when you mean patch boot img do mean to unzip file on onn 8
After reading for hours, I was successful to find an OTG micro-USB adapter with male USB-A end which allowed a Logitech dongle to be inserted and the mouse allowed me to start afresh from a factory reset. The touch screen didn't work.
There was an OTA update and I got all excited thinking, "This will be the update that fixes the touch (or lack thereof) issue."
Sadly, after the message said this was the final update, the touch screen still didn't work.
I was successfully able to enable USB Debugging because of the OTG Mouse.
When I connect to the PC and run an ADB command (e.g. adb devices), a message pops up asking to verify I trust the RSA Fingerprint for that computer and to remember that device.
Now my huge predicament: there is no way for me to touch the checkbox and choose OK.
Once I unplug in the cable to connect the OTG Mouse, the dialog box disappears.
I read about TeamViewer on the PC and TeamViewer Host from the Play Store. I installed both and was able to see the Essential Phone on the computer but whenever I touched the screen of the computer (or used the trackpad), nothing happened on the phone.
I tried pressing spacebar thinking that might enable the checkbox but no remote response on the phone.
I'm so close...all I need is one checkbox and one ok and it'll remember the USB Debugging settings.
From there I can then figure how to either downgrade from Android 10 or hopefully some kind soul can let me know what file to install so I can get this stupid touch screen to work.
I explained in a lot of detail as I wanted you folks to know I've tried many options to troubleshoot this problem before asking for help.
If there's a non-USB Debugging checkbox checked way in Fastboot Mode (e.g. ADB Sideload in Recovery), I'm willing to try that.
Thanks.
Update 2020-07-07: I had an idea to connect a SteelSeries Stratus XL wireless gaming controller to the phone via bluetooth and was successfully able to use the controls of the controller to enable the checkbox and remember the RSA Fingerprint for USB Debugging. Whooo-hoo! Now for the rest of the matter...getting this darn touch screen working with an device image that solves the problem....
I had the same problem after flashing the newest (and final) Image on top of a rooted, very old marshmallow build.
I found a fix on reddit however, and hopefully it works for you too.
I tried the second method described there:
1. Connect to fastboot to unlock bootloader and critical
Code:
fastboot flashing unlock
(didn't do anything for me since I was already unlocked)
Code:
fastboot flashing unlock_critical
Let the phone wipe itself and reboot, then go into fastboot again
2. Then flash the image of September 2018 (PH1-Images-PPR1.180905.036) via the "flashall.bat". After a reboot my touchscreen worked again.
3. Upgrade to the newest image or whichever one you like.
I don't understand the whole problem exactly, so maybe you could try flashing the newest image directly after the unlock_critical step, but I just followed the instructions I found.
Good luck!
Thanks for the suggestion and the link for the file.
When I try and run the command
Code:
fastboot flashing unlock
in fastboot mode, I keep getting the message "Waiting for device".
Same thing, when I try and run the flashall.bat file.
I booted in to FastBoot mode, but when I type adb devices in an admin command prompt, it doesn't show any devices listed, even though adb devices does show the phone listed when the phone has booted up normally.
I have:
uninstalled the Essential Phone driver and reinstalled it (multiple times).
installed the 15 Seconds ADB installer and uninstalled it (multiple times).
rebooted the Windows 10 computer multiple times.
IconBoy said:
Thanks for the suggestion and the link for the file.
When I try and run the command
Code:
fastboot flashing unlock
in fastboot mode, I keep getting the message "Waiting for device".
Same thing, when I try and run the flashall.bat file.
I booted in to FastBoot mode, but when I type adb devices in an admin command prompt, it doesn't show any devices listed, even though adb devices does show the phone listed when the phone has booted up normally.
I have:
uninstalled the Essential Phone driver and reinstalled it (multiple times).
installed the 15 Seconds ADB installer and uninstalled it (multiple times).
rebooted the Windows 10 computer multiple times.
Click to expand...
Click to collapse
Make sure to use a proper cable and not the one that comes with the phone for charging.
I use the one from my Nexus 6p. The cable from Essential is only for charging, not data transfer.
I'm using a USB-A TO USB-C cable which shows device in normal boot mode.
I have tried three different cables which all work when using adb devices in normal boot mode.
Still no phone when List of devices attached is shown.
Just for clarity: adb and fastboot are completely different modes. To test if you successfully booted into fastboot and have a working connection, you have to type "fastboot devices". "adb devices" doesn't work here.
But the unlock command should have worked anyway. How did you boot into fastmode? Can you see this fastboot screen?
If not, the easiest way to get to fastboot is to connect the turned off phone to the PC while keeping the volume down button pressed, until you see the screen linked above.
But if you do see the fastboot screen, and still don't get anything from "fastboot devices", I'd try Google's official adb/fastboot tools.
xxera said:
...you have to type "fastboot devices".
Click to expand...
Click to collapse
Yes! I can see the device listed now! I had no idea that you had to type that command! Wow....years later of working with phones and I am still learning. :good: I guess I didn't progress because I mistakenly thought the device was not being found.
I ran both commands fastboot flashing unlock and fastboot flashing unlock_critical successfully.
Once the phone wiped itself and booted up (without progressing from the startup screen prompts), I shut it down then went back in to fastboot mode and successfully ran the flashall.bat command.
I shut it down and restarted it. Touchscreen is still not working. :crying:
When I finally get this working...would I just run the commands fastboot flashing lock and fastboot flashing lock_critical to relock the phone...? I need Google Pay and other banking apps to work so want the phone to be secure.
There is always more to learn
Shame that it didn't work, though :/ Did you flash the image from September 2018 that I linked, or the newest build? If you directly flashed the newest one, maybe try the 2018 build, since that worked for me. Alternatively, from the same reddit post I linked before, someone got it working by flashing the August 2018 build, and sideloading the September 2018 OTA Update after. But I never did this sideloading thing, so can't help much there. All builds and OTAs are available on this neat website by the way.
Regarding relocking, it is generally advised to only relock if you have a good reason to do it. You can only relock a completely unmodified stock image, otherwise your phone won't boot, so no root, magisk or anything.
My banking apps still work on my unlocked and rooted phone, but I'm using a Pixel 3, and not sure about Google Pay.
But yes, if you want to relock, make absolutely sure you're stock, and use the commands you mentioned. Just be aware that this also wipes the phone again.
xxera said:
Shame that it didn't work, though :/ Did you flash the image from September 2018 that I linked
Click to expand...
Click to collapse
Yes, I used the link you gave me for the Sep 2018 build.
I will try the Aug 2018 build and see if I get any joy with that.
Thank you so much for your patience and help!
Just to be clear, you should sideload the September OTA after that, the August build itself won't do much as far as I understood.
Glad to help, I just had the same hunt for clues behind me, I know how frustrating it can be
I tried the Aug 2018 build then sideload flashing the Sep 2018 build. No joy...touchscreen still not working.
The whole fastboot flashing worked except for this one error:
fastboot format userdata
CreateProcess failed: The system cannot find the file specified. (2)
fastboot: error: Cannot generate image for userdata
This message came up once the flash was complete and the phone rebooted itself):
Android Recovery
essential/mata/mata
9/PPR1.180610.091/249
user/release-keys
Use volume up/down and power.
Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device.
--------------------------------------------------
Try again
Factory data reset
--------------------------------------------------
There was no choice to Apply update from ADB so I can sideload the Sep 2018 update so I went ahead and chose Factory data reset.
Once it factory reset, I was able to go in to recovery and sideload the Sep 2018 update.
Have I missed anything in this procedure...?
I also tried fastboot flashing the Apr 2019 build but that hasn't helped either.
(Attached is a screenshot of the two files I downloaded. The links are the purple ones I chose). Did I get the correct ones?
The files look right to me.
After some research I found that updating the adb tools worked for some people with that error. The creator of the 15 Seconds ADB installer even edited the post and said the tool is outdated by now. There's a newer version in this post, and maybe you are already using that, but I'd strongly recommend the official ADB from google, since I never had a problem with that one.
Also, I read that you should use a USB-3 cable. The official one from essential itself is USB-2 which can cause some problems in flashing sometimes (which is pretty stupid tbh).
Yes, after you updated ADB/fastboot, I'd just try the Aug image + Sept OTA again. Or directly the Sept image.
Not sure about the factory reset message, I'd say yes again just in case.
Edit: Ah, since it says "can't load android system", I guess the flashing failed.
I managed to fix phones with flashing a second time exactly the same way many times, sometimes fastboot is just moody. But may updating ADB can help here.
I updated fastboot and adb from the Google site.
Reflashed Aug and Sep 2018 files.
No joy. Touchscreen still doesn't respond.
An idea...I tried to install TWRP to see if the touchscreen is actually working but get the error fastboot: error: Couldn't parse partition size '0x' when running the command to install the TWRP Mata recovery image file.
Any way to check if the screen/digitizer is not a hardware fault?
Weird error... Can you post the whole log? If the partition size was read as 0, something went wrong with identifying the partition (if I interpret the error message correctly). Did you correctly flash to boot_a/boot_b depending on which one is active?
But TWRP might not help diagnosing the issue, I think touch stopped working in TWRP for essential phone a while ago, because it is also very outdated...
But to me it sounds like the usual problem after updating that many people had. The screen stopped working after an update, right?
Also, did you make sure to use the new platform-tools fastboot? Google's version doesn't automatically install itself system-wide, so if you just type "fastboot" in the command line, that might still be the old "15 Seconds ABD installer" fastboot. You can type "adb --version"to find out, it tells you in which folder the adb.exe file is.