As of right now the 2017 Nvidia Shield CAN be rooted. Updated 1/26/2017
What we do know So far.
1. How to access Fast boot mode?
there are two ways to access fast boot. The first way to access fast boot mode,
1. Buy a male to male USB 3 cable, & plug it into the USB port furthest away from the hdmi port.
2. In settings of the shield, go to storage.
3. Enable USB transfer
4. In settings go to about, then build version.
5. Click on build version 5 times.
6. Under settings, go to developer options.
7. Enable USB debugging.
8. Make sure you have the latest drivers installed from Nvidias website.
9. Download ADB Command prompt/fastboot
10. Type "adb devices"
11. You may get a prompt on your shield about allowing debugging, if so make sure you allow it.
12. Type "adb devices" again if a device shows up then great! move on to the next step.
13. Type "adb reboot bootloader"
The second way of getting into fastboot mode, is the following
1. Unplug your power cable from the device.
2. Plug in your Shield game controller in the usb closest to the hdmi port.
3. Hold down buttons A & B.
4. While holding down the two buttons, put in your power cable.
5. Keep holding down the buttons.
6. If all done correctly you should see the fast boot menu now on your screen.
Congratulations your device should now be in the fastboot menu, Note in order to navigate the fast boot menu you will need your game controller plugged into the usb port next to the hdmi port.
2. Is their a download link for the latest OTA update?
Yes, you can get 5.0.1 from here, http://ota-downloads.nvidia.com/ota...-full_ota-1749719_832.2408.20170116175313.zip
3. What will happen if i try and install twrp on my shield?
Your device will try to boot it, then it will reboot and repair the recovery partition of your shield, then boot into androids 7.0 operating system.
4. A unofficial version of TWRP is out
https://forum.xda-developers.com/shield-tv/development/recovery-twrp-shield-android-tv-2017-t3545544 use at your own risk!
5. Recovery images are out for the 2017 Shield (16GB Only)
5.01 Retail: http://developer.download.nvidia.co...1/nv-recovery-image-shield-atv-2017-5.0.1.zip
5.01 Developer: http://developer.download.nvidia.co...ry-image-shield-atv-2017-5.0.1-dev_rooted.zip
Can't you directly boot the twrp.img without flashing it first?
fastboot boot twrp...img
Then install SuperSU from there?
brotbuexe said:
Can't you directly boot the twrp.img without flashing it first?
fastboot boot twrp...img
Then install SuperSU from there?
Click to expand...
Click to collapse
You probably could... But, that in-and-of itself isn't exactly the problem. It's the unfortunate way Google have started implementing System Updates on Nougat going forward. They've call this System the a/b System.
To simply explain it, on Devices which support it. (Like the new Shield 2017, possibly the 2015 post update?), there are now Two System Partitions. The active one, which we have always known. (And, indirectly referencing in your question.), and, the new mirrored System Partition that has Two jobs. One to make System (e.g. Security), Updates simplier, and the other is to make sure the first System Partition does NOT get corrupted by allowing One to say root it or by installing "malicious" Software (i.e. SuperSU) onto the Device. Without it blasting it straight out of existence again.
So yes you could try to load TRWP up from somewhere, and install SuperSU. Like you've always done. But, as soon as you start to reboot it again the a/b System will revert your hard work again.
Ichijoe said:
You probably could... But, that in-and-of itself isn't the problem. It's the way Google have started implementing System Updated on Nougat going forward. They call that System the a/b System.
Click to expand...
Click to collapse
I read it is the same in pixel devices. So I hope it is just an update for SuperSU to recognize this on the new shield.
brotbuexe said:
Can't you directly boot the twrp.img without flashing it first?
fastboot boot twrp...img
Then install SuperSU from there?
Click to expand...
Click to collapse
pretty much what the guy above said, it will detect a modification in the recovery partition and fix it, then boot into android.
so are we SOL indefinitely or will there ever come a time where we can override the two partitions so root sticks? ie is it possible.
HUYI said:
so are we SOL indefinitely or will there ever come a time where we can override the two partitions so root sticks? ie is it possible.
Click to expand...
Click to collapse
I dont think we are SOL. i think the developer of twrp for shield just needs to update it. im not a developer. so i dont know, but here is some good news, i was talking to nvidia and they will be releasing a prerooted image for the 2017 shield.
Hello Brandon,
Thank you for contacting NVIDIA Customer Care.
This is Kenny, assisting you in regards to your query about the ISO Image download availability for the SHIELD TV Console V2.
Please be informed that the image isn't available for this unit yet. This is our download centre : https://developer.nvidia.com/gameworksdownload where it will be available once the Image is available for this unit.
So you may check this website often to see the availability.
Disclaimer : Rooting the device will void the software warranty of the unit.
Click to expand...
Click to collapse
Unfortunately we don't have any ETA on this Brandon,
As it's a new device it may be added there in sometime. However I can't give you a precise date about this. Sorry.
You can register there as a developer and wait for the Image release.
Regards,
NVIDIA Customer Care
Click to expand...
Click to collapse
brandonb21 said:
I dont think we are SOL. i think the developer of twrp for shield just needs to update it. im not a developer. so i dont know, but here is some good news, i was talking to nvidia and they will be releasing a prerooted image for the 2017 shield.
Click to expand...
Click to collapse
0_0 whaaa! cool i can't wait for that that's awesome news! so cool that nvdia have given us support like this.
i will install when it's available but it seems it's going to be a long wait till it's available, maybe late spring summer my guess, hopefully sooner.
and it's obvious that it will void warranty..
brandonb21 said:
pretty much what the guy above said, it will detect a modification in the recovery partition and fix it, then boot into android.
Click to expand...
Click to collapse
But if you just fastboot the twrp.img you wouldn't touch the recovery partition.
You would change the boot.img and /data for systemless root while flashing SuperSU. So at the next boot the system has to check if you changed the boot img/partition, and I guess the supersu installer has to take care of this verification.
There would be not much of a problem to not have twrp directly on the device, as you can always boot the img through fastboot.
Does booting the twrp img via fastboot works on the 2017 shield?
brotbuexe said:
But if you just fastboot the twrp.img you wouldn't touch the recovery partition.
You would change the boot.img and /data for systemless root while flashing SuperSU. So at the next boot the system has to check if you changed the boot img/partition, and I guess the supersu installer has to take care of this verification.
There would be not much of a problem to not have twrp directly on the device, as you can always boot the img through fastboot.
Does booting the twrp img via fastboot works on the 2017 shield?
Click to expand...
Click to collapse
i did "fastboot boot twrp.img" and it booted into the android OS
From what I gathered from recovery logs and tearing apart the boot.img I do not think the Shield 2017 uses two system partitions like the Pixel. I have only seen one partition.
I was able to modify the boot.img to make it not secure, flashed it and it booted fine. It was not replaced with stock boot. I then tried to flash TWRP with the not secure boot.img but TWRP would not boot.
I believe TWRP needs new zImage from Shield 2017 and a few variables need to be tweaked too for it to work on the Shield 2017.
I am going to download the OmniROM source files and try to compile TWRP for the Shield 2017. Should be a quick fix for the current Shield TWRP device maintainer to make so I am a little hesitant to take the time to set everything up. With my luck the current maintainer will build TWRP for Shield 2017.
*Edit*
I attached the modified boot.img which is insecure for whoever wants to play with it.
Make sure you have ADB enabled and your PC has been authorized to use ADB with your Shield2017...
brotbuexe said:
But if you just fastboot the twrp.img you wouldn't touch the recovery partition.
You would change the boot.img and /data for systemless root while flashing SuperSU. So at the next boot the system has to check if you changed the boot img/partition, and I guess the supersu installer has to take care of this verification.
There would be not much of a problem to not have twrp directly on the device, as you can always boot the img through fastboot.
Does booting the twrp img via fastboot works on the 2017 shield?
Click to expand...
Click to collapse
AndroidUser00110001 said:
From what I gathered from recovery logs and tearing apart the boot.img I do not think the Shield 2017 uses two system partitions like the Pixel. I have only seen one partition.
I was able to modify the boot.img to make it not secure, flashed it and it booted fine. It was not replaced with stock boot. I then tried to flash TWRP with the not secure boot.img but TWRP would not boot.
I believe TWRP needs new zImage from Shield 2017 and a few variables need to be tweaked too for it to work on the Shield 2017.
I am going to download the OmniROM source files and try to compile TWRP for the Shield 2017. Should be a quick fix for the current Shield TWRP device maintainer to make so I am a little hesitant to take the time to set everything up. With my luck the current maintainer will build TWRP for Shield 2017.
*Edit*
I attached the modified boot.img which is insecure for whoever wants to play with it.
Make sure you have ADB enabled and your PC has been authorized to use ADB with your Shield2017...
Click to expand...
Click to collapse
Sounds great! good luck on the twrp port!
Yes good luck dude
brandonb21 said:
As of right now the 2017 Nvidia Shield CANNOT be rooted. Updated 1/20/2017
What we do know So far.
1. How to access Fast boot mode?
there are two ways to access fast boot. The first way to access fast boot mode,
1. Buy a male to male USB 3 cable, & plug it into the USB port furthest away from the hdmi port.
2. In settings of the shield, go to storage.
3. Enable USB transfer
4. In settings go to about, then build version.
5. Click on build version 5 times.
6. Under settings, go to developer options.
7. Enable USB debugging.
8. Make sure you have the latest drivers installed from Nvidias website.
9. Download ADB Command prompt/fastboot
10. Type "adb devices"
11. You may get a prompt on your shield about allowing debugging, if so make sure you allow it.
12. Type "adb devices" again if a device shows up then great! move on to the next step.
13. Type "adb reboot bootloader"
The second way of getting into fastboot mode, is the following
1. Unplug your power cable from the device.
2. Plug in your Shield game controller in the usb closest to the hdmi port.
3. Hold down buttons A & B.
4. While holding down the two buttons, put in your power cable.
5. Keep holding down the buttons.
6. If all done correctly you should see the fast boot menu now on your screen.
Congratulations your device should now be in the fastboot menu, Note in order to navigate the fast boot menu you will need your game controller plugged into the usb port next to the hdmi port.
2. Is their a download link for the latest OTA update?
Yes, you can get 5.0.1 from here, http://ota-downloads.nvidia.com/ota...-full_ota-1749719_832.2408.20170116175313.zip
3. What will happen if i try and install twrp on my shield?
Your device will try to boot it, then it will reboot and repair the recovery partition of your shield, then boot into androids 7.0 operating system.
Click to expand...
Click to collapse
I can get into the boot menu but none of my buttons on my controller work? I have it all plug in as the steps show. I just received it and maybe it not paired right?
GhostRider5666 said:
I can get into the boot menu but none of my buttons on my controller work? I have it all plug in as the steps show. I just received it and maybe it not paired right?
Click to expand...
Click to collapse
the controller has to be plugged in before going into fastboot menu, also X is to go down and Y is to go up and A is to select an option.
brandonb21 said:
the controller has to be plugged in before going into fastboot menu, also X is to go down and Y is to go up and A is to select an option.
Click to expand...
Click to collapse
Everything is plugged in. I did adb root bootloader no controller and did the steps with the A and B buttons.
GhostRider5666 said:
Everything is plugged in. I did adb root bootloader no controller and did the steps with the A and B buttons.
Click to expand...
Click to collapse
maybe it was B and Y to go up and down. you know your controller is working if it vibrated going into fastboot mode, then it's working correctly
I fastboot oem unlocked and it booted up and shut down now It doesn't power back up and in device manager it shows APX?
GhostRider5666 said:
I fastboot oem unlocked and it booted up and shut down now It doesn't power back up and in device manager it shows APX?
Click to expand...
Click to collapse
apx?, i oem unlocked mine and everthing went fine.
brandonb21 said:
apx?, i oem unlocked mine and everthing went fine.
Click to expand...
Click to collapse
I don't know, I can't even get it to power on?
Related
First of all, let me say this isn't my post, and I didn't develop this method. The user, "Teletype" got this all figured out and did an amazing write-up for it. I'm posting it on their behalf so it can be in this newly added forum. The link to the recovery zip is also in his original thread, which I've linked below.
Here's the link to his original thread. If you feel the urge to press "thanks", please go to his original thread and press it for him, he deserves all the credit.
teletype said:
I just managed to get TWRP running on the new Shield console, and installed SuperSU successfully. Two caveats: the display is upside down, and the USB host ports don't work. I had to plugin a mouse via an OTG cable in order to interact with it. ETA: That's only an issue when booted to TWRP. Everything's working fine in the stock ROM after rooting.
Procedure:
- enable developer tools / USB debugging
- adb push supersu.zip /sdcard
- adb reboot bootloader
- fastboot oem unlock
- fastboot boot twrp-2.8.6.0-shieldtv-unofficial.img
- unplug USB cable, connect mouse via USB, install SuperSU
TWRP boot image is attached. Off to explore...
EDIT: by request, some more detailed instructions:
On the Shield device, head to Settings -> About, and click "Build number" 7 times. This will enable Android's Developer options.
Go to Settings -> Developer options, and enable USB debugging.
Install the ADB/fastboot drivers and utilities if you don't already have them. When "adb devices" shows your Shield, you're good to go.
Download and extract recovery.zip from this thread.
Head to the SuperSU forum and download the latest version.
Open a command prompt and navigate to the directory where you downloaded everything. (Google this for your OS if you don't know how).
With the Shield still booted, run "adb push supersu.zip /sdcard" (change supersu.zip to appropriate file name). This will upload the SuperSU update zip to your device, which you'll install from TWRP.
If that worked fine, run "adb reboot bootloader". Your device should shut down, and display the Fastboot screen after a few seconds.
FOLLOW THE NEXT THREE INSTRUCTIONS AT YOUR OWN RISK. This WILL wipe all your user data, back it up with ADB first if you want to preserve it. DISCLAIMER #2: I have no idea if there are any DRM keys or anything that get wiped when this is done (this was the case on my Xperia Z3 Compact). I will say that Grid streaming still works fine after doing this.
This step will unlock your bootloader to enable booting unsigned images.
Run "fastboot devices" and make sure your Shield is visible.
Run "fastboot oem unlock" and follow the prompts on the screen. Your bootloader is now unlocked.
Now, boot the TWRP image with: "fastboot boot twrp-2.8.6.0-shieldtv-unofficial.img" - Note: I used this instead of "fastboot flash" so I could keep the stock recovery around, to grab an image of it after rooting.
You should now see a TWRP recovery menu (upside down for now).
Connect a keyboard or mouse via OTG cable, and select "Install", navigate to your SuperSU zip, select it, and follow the prompts.
Click "reboot" and you should now be rooted.
Click to expand...
Click to collapse
does this have to be done with an otg cable
You can use the supplied micro USB cable to do the adb portion. You shouldn't ever need otg with this device since it also has 2 full sized USB ports.
Sent from my nexus 9 using XDA Free mobile app
Instructions got updated
Hi,
I have updated the instructions to ones that more closely aligned with my experience of doing this. The initial instructions were good for me - but some were in slightly the wrong order or not quite clear enough to be immediately intuitive. I've tried to fix that Hope it helps.
On the Shield device, head to Settings -> About, and click "Build number" 7 times. This will enable Android's Developer options.
Exit settings, then go back in to settings -> Developer options, and enable USB debugging.
Install the ADB/fastboot drivers and utilities on to your PC if you don't already have them. When "adb devices" shows your Shield, you're good to go.
Download the latest Super user zip file from the super user thread here.
Download and extract the recovery file from here. (it needs to be a .img not a .zip)
run "adb reboot bootloader". Your device should shut down, and display the Fastboot screen after a few seconds.
FOLLOW THE NEXT THREE INSTRUCTIONS AT YOUR OWN RISK. This WILL wipe all your user data, back it up with ADB first if you want to preserve it. DISCLAIMER #2: I have no idea if there are any DRM keys or anything that get wiped when this is done.
This step will unlock your bootloader to enable booting unsigned images.
Run "fastboot devices" and make sure your Shield is listed when you do so.
Run "fastboot oem unlock" and follow the prompts on the Shield's screen. You use the power button on the shield device itself to navigate the menu, and long press to select an option. Once you have confirmed, this can take along time to unlock (hour and a half for me on the Pro version). Your bootloader is now unlocked.
"Fastboot reboot" to reboot to AndroidTV.
run "adb push supersu.zip /sdcard/" (change supersu.zip to appropriate file name that you downloaded earlier). This will upload the SuperSU update zip to your device, which you'll install from TWRP.
Now, boot the TWRP image with: "fastboot boot RECOVERYFILENAME.img" - Note: I used this instead of "fastboot flash" so I could keep the stock recovery around, to grab an image of it after rooting. (change the name of the file in the instructions to the name of your recovery file that you downloaded).
After a short while you should now see a TWRP recovery menu.
Connect a keyboard or mouse via OTG cable, and select "Install", navigate to your SuperSU zip, select it, and follow the prompts.
Click "reboot" and you should now be rooted.
Click to expand...
Click to collapse
Anyone tried kingroot?
Sean09 said:
Anyone tried kingroot?
Click to expand...
Click to collapse
We have a factory supported way to unlock and root. No real point in trying to exploit the system. If you are rooted, you should have a custom recovery anyway, which means you need to unlock the bootloader anyway in case you need to fix something.
Hey, I have rooted my shield and I didn't backup my stock recovery, anyone have a stock recovery img, I want to update to 1.4
Thanks
Gig11gs said:
Hey, I have rooted my shield and I didn't backup my stock recovery, anyone have a stock recovery img, I want to update to 1.4
Thanks
Click to expand...
Click to collapse
You can download the 1.4 firmware and flash it manually. There's a discussion on it a few pages back :good:
Will I be able to get OTA updates if I root ?
rahulkadukar said:
Will I be able to get OTA updates if I root ?
Click to expand...
Click to collapse
You'll get the OTA notification but I was not able to install the OTA. You will need to download and new firmware and flash from fastboot.
Can I still root it this way if I already updated to 1.4 as I'm still fully stock and took the OTA
Im asking the same, im on the latest as of 2015 10 19, can i root using this method ?
baileyjr said:
You'll get the OTA notification but I was not able to install the OTA. You will need to download and new firmware and flash from fastboot.
Click to expand...
Click to collapse
You're guided imagery? I read without understanding very much
Can anyone confirm this rooting method works for new firmware 2.1?
garz said:
Can anyone confirm this rooting method works for new firmware 2.1?
Click to expand...
Click to collapse
I struggled to get root with this write up, and I am not a rookie. There were a few key steps missing, for example, you actually have to flash twrp, you can't just boot from twrp as suggested, if you are on 1.4 and up. Also, you have to let the unit reboot after you do the OEM unlock before flashing twrp. I didn't and mine just froze after flashing the recovery img. I found this write up http://nvidiashieldzone.com/index.php/shield-android-tv/root-shield-android-tv/
That one in the shield zone forum was so much more complete. And yes, it worked just fine with the 2.1 update. I did it yesterday with no problems. It will wipe out your data, and it will take a long time after you do the fastboot oem unlock, especially if you have the PRO version. But root is working with no problems.
RyanInBinary said:
First of all, let me say this isn't my post, and I didn't develop this method. The user, "Teletype" got this all figured out and did an amazing write-up for it. I'm posting it on their behalf so it can be in this newly added forum. The link to the recovery zip is also in his original thread, which I've linked below.
Here's the link to his original thread. If you feel the urge to press "thanks", please go to his original thread and press it for him, he deserves all the credit.
Click to expand...
Click to collapse
Do you want to build pre-root shiled TV firmware by nvidia open source？ and have experience？
Rooting.
KingRoot dose not work on this device.
Good guide thanks.
OK i have a 16gb model on 2.1, got adb hooked up but get this when trying to push supersu.zip to sdcard0:
C:\shield>adb push supersu.zip /sdcard1
failed to copy 'supersu.zip' to '/sdcard1': Read-only file system
Any ideas?
bearkilla said:
OK i have a 16gb model on 2.1, got adb hooked up but get this when trying to push supersu.zip to sdcard0:
C:\shield>adb push supersu.zip /sdcard1
failed to copy 'supersu.zip' to '/sdcard1': Read-only file system
Any ideas?
Click to expand...
Click to collapse
Try
Adb push supersu.zip /sdcard/
Inviato dal mio SHIELD Tablet utilizzando Tapatalk
Hi all,
i haven't a Nexus 10 but I want to let you know that Jade Remix OS ROM is now available for flashing on the Nexus 10:
Here is the link to download the ROM: https://drive.google.com/open?id=0B6QbFTXmsda3VDhCMUU3OVg1S2s
Here you'll find screenshots and videos: http://www.jide.com/en/remixos - https://www.youtube.com/channel/UC0U64-AHqJfeAnFJ5vQnM8w/feed
Here is the JIDE forum: https://forum.jide.com/index.php?p=/discussion/601/nexus-10-rom-available-here#Head
This is the greatest "fork" Android base ROM!!
P.S.: I don't want anything, just a Thank You
ROM Installation Instructions
Want to try to flash a Remix OS ROM to other android devices? Yes! We will soon put the Remix OS ROM on the Internet for users to download and flash onto their own device. To start, we will provide the guideline and support to flash the Remix OS ROM on Google Nexus 10.
Disclaimer
Flashing Remix OS ROM on Nexus 10 requires strong android knowledge. Flashing this ROM on Nexus 10 will be at your own risk. You will have to bear responsibility for all the resulting consequences. Jide will NOT be responsible for any damage caused.
Further Note:
Unfortunately, as a startup, we lack the resources to support installation Remix OS ROM on other android devices, thus, we will ONLY provide support for the Nexus 10 device. The Nexus 10 is a touchscreen tablet manufactured by Samsung with direct support from Google. It is the second Nexus tablet. Of course, we will look forward to the support of Remix fans to share with the world about their experience on flashing the ROM on other Android devices.
Installation Instructions
The followings are the steps to install Remix OS ROM: Unlocking the device & Installing image files using fastboot
Unlocking the device
1. Make sure your computer has working fastboot and adb.
2. Enable USB debugging on the device.
3. Connect the device to the computer through USB.
4. From a terminal on a computer, type the following to boot the device into fastboot mode:
- adb reboot bootloader
5. Once the device is in fastboot mode, verify your PC sees the device by typing
- fastboot devices
- If you don't see your device serial number, and instead see "", fastboot is not configured properly on your machine. See fastboot documentation for more info.
- If you see "no permissions fastboot", try running fastboot as root.
6. From the same terminal, type the following command to unlock the bootloader:
fastboot oem unlock
7. A disclaimer will display on the device that must be accepted. Use the volume keys to cycle through the options. Pressing the power button should confirm your selection.
8. If the device doesn't automatically reboot, reboot it from the menu. It should now be unlocked. You can confirm this is the case if you see an unlocked icon at the bottom of the Google boot screen during reboots.
9. Since the device resets completely, you will need to re-enable USB debugging on the device to continue.
Installing image files using fastboot
1. Make sure your computer has working fastboot and adb.
2. Download images
- you should have a download link from us in the email. The information of the image zip file:
- Images Zip File Name: images_Nexus_10-5.0.2-B2015070105-signed.zip
- md5: bdb08b6a0508dd1088f177a9e19c2875
- sha1: 9d6df824ef8c32af1a3a9d89e5f870133bcdebf6
3. Unzip the downloaded zip file ( images_Nexus_10-5.0.2-B2015070105-signed.zip ) and go to the folder
4. Connect the Nexus 10 to the computer via USB.
5. Make sure the fastboot binary is in your PATH or that you place the recovery image in the same directory as fastboot.
6. Open a terminal on your PC and reboot the device into fastboot mode by typing
adb reboot bootloader
or by using the hardware key combination for your device while it is powered off.
7. Once the device is in fastboot mode, verify your PC sees the device by typing
fastboot devices
- If you don't see your device serial number, and instead see "", fastboot is not configured properly on your machine. See fastboot documentation for more info.
- If you see "no permissions fastboot", make sure your UDEV rules are setup correctly.
8. Clean the existing data by entering the following command:
- fastboot -w
9. Flash images onto your device by entering the following three commands:
- fastboot flash system system.img
- fastboot flash recovery recovery.img
- fastboot flash boot boot.img
10. Once the flash completes successfully, run the following command to reboot the device into recovery to verify the installation.
- fastboot reboot
Some of the external link of this documents will link to CM website. The installation process is referenced by http://wiki.cyanogenmod.org/w/Install_CM_for_manta
You are the man!
Yea that didn't work for me, no recovery on boot to recovery just blank screen. Also stuck on remix boot logo.
Works for me. You have to fastboot -w to wipe your device, then flash at least the system and boot image through fastboot.
I didn't wipe my device ,didn't wanna lose the sdcard content. I simply did a factory reset from twrp. Question, can it be rooted with cfautoroot like normal android 5.0?
its totally a new dev rom! the best out there! Love this rom!
How to add other languages, for example, russian?
So far I'm loving this rom. The only thing is that I wish there was a way to add widgets.
For some reason i can't hear any media volume whether it be youtube videos, music, or netflix. Any ideas on what might be wrong?
For some odd reason Tapatalk doesn't work on this ROM for me.
How do we root? Anyone know?
I've found this YOUTUBE link, but didn't test yet
EddyTeddy01 said:
For some reason i can't hear any media volume whether it be youtube videos, music, or netflix. Any ideas on what might be wrong?
Click to expand...
Click to collapse
I'm having the same problem, did you ever figure this out?
Corvidd said:
I'm having the same problem, did you ever figure this out?
Click to expand...
Click to collapse
Why is this always a problem with N10 roms?
Sent from my Nexus 5 using Tapatalk
I'm trying to get this ROM off my nexus 10, but I don't have ADB connection for some reason. I don't have TWRP recovery anymore either. Anyone have any tips?
blkhrt13 said:
I'm trying to get this ROM off my nexus 10, but I don't have ADB connection for some reason. I don't have TWRP recovery anymore either. Anyone have any tips?
Click to expand...
Click to collapse
ADB - do you have USB debugging on? is Fastboot not working either? may need to re-install drivers on your PC
TWRP - are you saying it was installed, but you can't access it? unclear on your exact issue.
drewski_1 said:
ADB - do you have USB debugging on? is Fastboot not working either? may need to re-install drivers on your PC
TWRP - are you saying it was installed, but you can't access it? unclear on your exact issue.
Click to expand...
Click to collapse
Okay, I'll power off the tablet, then hold volume up AND down + power and that boots it into.... Recovery I think. When it boots to that, adb and fastboot are connected. I have a Nexus toolkit installed on my pc for flashing etc. Whenever I click flash recovery to reinstall twrp, it reboots the tablet into the OS and that's it. And when it's booted into the OS, there's no adb connection. And USB debugging is on. I finally just gave up.
blkhrt13 said:
Okay, I'll power off the tablet, then hold volume up AND down + power and that boots it into.... Recovery I think. When it boots to that, adb and fastboot are connected. I have a Nexus toolkit installed on my pc for flashing etc. Whenever I click flash recovery to reinstall twrp, it reboots the tablet into the OS and that's it. And when it's booted into the OS, there's no adb connection. And USB debugging is on. I finally just gave up.
Click to expand...
Click to collapse
Power + Vol Up/Down boots to bootloader.
If you have fastboot, then download the TWRP img file to your computer and issue the following command in the bootloader (forget the toolkit)
Code:
fastboot flash recovery <recovery img file name>
then you should be able to get into TWRP by using the Power Up/Down buttons until you see "Recovery" aligned with the Power Button.
press Power and you should be good to go.
blkhrt13 said:
I'm trying to get this ROM off my nexus 10, but I don't have ADB connection for some reason. I don't have TWRP recovery anymore either. Anyone have any tips?
Click to expand...
Click to collapse
I'm in the EXACT same situation. Fastboot and adb not working for this, but all my other android devices are working fine. Luckily I have twrp installed so I'll just flash something else then start over on a diff rom.
Edit: and of course, just like that, I restart one more time and it actually works. very temperamental i guess.
This is a great ROM with fast clean I interface. I used official manta 5.1 from Jide. Unfortunately google device manager now sees my N10 as a Linux device, and google play services will not load properly so I cannot play cloud connected games which is really sad, I will have to back to an android custom ROM..... If you don't need play services give jide a try.. Its a pretty cool concept.
Hi all! It took me a lot of time to finally being able to root this tablet. It's old, slow and practically unusable, but with some tricks it can be made much, much better. I'm going to explain what you need to do to root this tablet, and in case of brick (which happened to me many, many times) how to unbrick it. I even got to a point where I could not even boot into recovery mode, and only fastboot was working, that was scary, but I managed to get out. Every single file I will use will be bundled in a ZIP you can download, and I'll try to make sure this link stays up, because there's nothing more frustrating than wanting to make these things in the future only to find out the link is dead, along with all your hopes. Before we begin, a little disclaimer:
Code:
#You, and only you are responsible for everything that you do or happens to your tablet.
#If you screw up, I have a number of backups to help you recover, but if that's not enough don't point a finger at me.
#I will not be babysitting anybody to help restore their tablet or recover lost data.
#This process WILL wipe all of your data, do a backup before beggining.
#YOU HAVE BEEN WARNED!
1. ENABLING USB DEBUGGING
This is a very basic step, but it's needed if you want to even begin to do this. You'll need to go to "Settings -> About Phone". There, look for a line that says "Compilation Number" (or something like that) and tap it multiple times. You will see a message pop up saying "You are now a developer" (I wish it was that easy). Go back to the settings screen, you will see a new option appeared called "USB Debugging". Enable it, and make sure "Developer Options" are enabled too at the very top of the screen. Now, connect the tablet to your computer. You will see a message pop up asking for permission, tap "Always allow from this computer" and press "Allow".
That's it for this step.
2. SETTING UP ADB TOOLS AND MAKING SURE THEY WORK
Now that we have USB debugging enabled, and we have allowed our PC to access the tablet, we can begin setting up ADB. The required files are attached in the zip.
Extract the "platform-tools" folder and move it somewhere nice. Then open it, hold shift and right click in a white space and select the option "Open command window here". CMD will pop up, now type:
Code:
adb devices
It will probably say something about a server followed by a list of attached devices. If you see a serial number there, then great! ADB is working as it should. If not, make sure the tablet is connected, that USB Debugging is on, and if all else fails, try with another cable.
Now for the juicy part.
3. UNLOCKING THE BOOTLOADER
We will have to unlock the bootloader if we want to do anything here. Here's what to do. Type:
Code:
adb reboot fastboot
Wait until the tablet reboots into fastboot. Once there type:
Code:
fastboot oem unlock
fastboot oem unlock confirm
This should unlock the bootloader.
NOTE: This method of unlocking is reported to not work anymore, but I listed it anyway just in case, as it doesn't hurt to try. If this is not working for you, don't panic, it's normal, use the following code instead:
Code:
fastboot oem asus-go
fastboot oem asus-go confirm
This should work, and the bootloader should be unlocked now.
4. INSTALLING THE REQUIRED FIRMWARE
Now, your tablet may or may not have the required firmware for the procedure, but just in case we will flash one that's sure to work. If you followed along, you should be in fastboot mode right now. Type:
Code:
fastboot reboot
Your tablet should boot as normal, without any changes (unless the first bootloader unlock method worked for you, in which case it probably wiped all of your data). Now we can access ADB once again, so type:
Code:
adb reboot recovery
The tablet will reboot into recovery mode and you should see an image of wasted android with an open belly (if you don't see this it doesn't matter). You should see a list of options with blue text, you must use the volume keys to navigate this menu. If you don't see any options, press any volume key and they should appear. If instead of getting into recovery mode, the tablet just turned off, then go to the "Fixing recovery" section.
In this menu, you must select "Wipe data/factory reset". This will, obviously, wipe all of your data. Once that finishes, select the "Install update through ADB" option. Once that's done, make sure the "updated_firmware.zip" file is in the same directory as the "adb.exe" file, then type:
Code:
adb sideload updated_firmware.zip
This will install the firmware, it will take about 20 mins. Once finished, reboot the device. You may think it got bricked at this point, fear not, the first boot really takes this long (about 10 mins).
Once everything is done, the device should boot up and everything should be exactly as it was when you took it out of the box, meaning, it doesn't even remember your wifi password. Do a quick (but proper) set up and enable USB Debugging again, make sure to allow the PC again (and check the "always allow" box). Also, scroll down a bit more in the developer options section and look for one that says "Verify apps installed through USB" or something of that kind. Make sure it's unchecked. Now, we gotta install root.
5. ROOTING
The all holy root, finally here. Type this into the terminal:
Code:
adb reboot fastboot
You should be familiar with this process by now. Once in fastboot mode, type:
Code:
fastboot boot root.img
Once finished, reboot. You should boot up as a rooted user, hooray! Only one final step, we gotta give ourselves some means to control this new power, that's where the SuperSU app comes into play.
6. INSTALLING SUPERSU
Apparently, not every single SuperSU apk file works... but lucky for you, I managed to scout and bundle one that does, so use that one. Make sure the apk file is in the same folder as "adb.exe" (as with all of the previous files) and type:
Code:
adb install supersu-2-82.apk
Leave it a few mins, and you should see a "success!" message when it's finished. Open the SuperSU app and it will tell you that you need to update the binaries. Say yes to that, and when asked wether to do a "Normal" update or "TWRP" update, select normal. It should be successful and prompt you to reboot, do so.
That's about it, you now have root access in the ASUS ZenPad C 7.0.
NOTE: Every single attempt I made to make the SuperSU app a system app resulted in the app crashing and I needed to reinstall it again, do as you please.
Why would you even want to do this you might ask? Well, I personally used this to make a few tweaks with Kernel Auditor and L Speed, two apps that will let you customize the performance of the machine to its maximum... sacrificing battery of course. You can search online for the best configuration for you for these apps. With the right tweaks, it transforms from **** to usable, and you need root for all of this.
As a quick note, you might notice that the SuperSU pop up that prompts you wether to grant or deny root access to an app is delayed, that's just how life is with this machine, it's slow. As a tip, when an app is trying to acquire root access, go back to the home screen and open the SuperSU app, then go back to the app you were trying to give it access to, it should appear quicked that way. Sometimes it's so slow that the app says I don't have root, only to have the pop up appear 10 seconds later. Now... to a final chapter.
7. UNBRICKING
This would be the end of the story if nothing went wrong, you have a rooted tablet and you can now do whatever you want with it, but that's not how life is. **** happens, things can go wrong, and when they do, you better have a backup plan. I don't know how to get back your ex, but I know how you can unbrick your tablet if that should happen. Follow these steps if you want to recover this machine...
Code:
#This process will wipe all data, but you shouldn't care about that since you can't access it anyway.
So, if the tablet doesn't turn on and gets stuck at the boot up screen, what can we do? Well, let it sit at the boot up screen for a few mins, and then type in the terminal:
Code:
adb devices
If it's recognized, then type:
Code:
adb reboot recovery
If it's not recognized, press the power button and the volume down key until the tablet turns off. Once that happens, press the power button and the volume down key, when the logo appears, let go of the power button and keep the volume down key pressed, that should boot the tablet into recovery mode. If you got into recovery mode, skip to 7.2
7.1 FIXING RECOVERY MODE
Sometimes, (it happened to me), recovery mode is broken.... it just doesn't appear, no matter what you do you can't get into it. To fix this, we gotta flash it again. We gotta enter fastboot mode. One option is to boot up the device until it gets stucked and wait a few mins, then adb should be able to recognize it and you type:
Code:
adb reboot fastboot
If that's not the case, turn the tablet off and press power and volume up, that should get you to fastboot. Once there type:
Code:
fastboot devices
And the tablet should appear there, if it doesn't... well it better do. I don't really know what to do if it doesn't appear there, but there shouldn't be a reason for it not to. I guess you can try to enter fastboot once again, with the tabler connected from the beggining or something like that, let's just assume it does, and if it doesn't then I'm sorry to tell you that's homework you will have to do.
Once here, we must format the cache and the data partition, for that type the following:
Code:
fastboot format cache
fastboot format userdata
Now, we need to get the recovery files, grab them from the zip I gave you. The files in question are "recovery.bin" and "vrl.bin". We will start with vrl. Once the two formats are finished, type:
Code:
fastboot flash vrl vrl.bin
Followed by:
Code:
fastboot flash recovery recovery.bin
Once that's done, press the power button and volume down keys until the tablet turns off. Then, press them again until the logo appears, and when that happens let go of the power button, that should get you (finally) into recovery.
7.2 UNBRICKING (FOR REAL THIS TIME)
Well, now that everybody is on the same page, and we could get to recovery mode, it's time to repeat some steps really... Follow the procedure from step 4 onwards (from the part that tells you to go to recovery). So, wipe data and apply that damn zip with sideload, the tablet should work now.
That's all I have to offer guys. I'm not a developer, I'm just a guy with a bunch of free time on his hands, so I was able to gather all of this information and (most importantly) files so you can root and fix this god damn tablet. Until the next one!
FINAL NOTE: In the files I included, there's a TWRP.img file. This is the TWRP custom recovery. As far as I know, this version should work with this tablet, but I was unable to flash it and make it work. IF YOU WANT TO TRY THIS DO SO AT YOUR OWN RISK, IT'S HIGHLY PROBABLE THAT THIS WILL RESULT IN BRICKING YOUR TABLET AND BREAKING THE STOCK RECOVERY, IN WICH CASE YOU WILL NEED TO FOLLOW THE STEPS STATED IN THIS GUIDE.
I couldn't upload the files as an attachment directly... sorry.
The "updated_firmware.zip" file is added as a separate download because it's a bigger file, and I prefer to let people decide if they even want it in the first place.
updated_firmware.zip
Everything else
None of the 8 drivers from Intel or Google detect the device in fastboot mode. I tried fixing this tablet years ago and had the fastboot drivers. As far as I know I have the same ones. These all loaded with no problem, but I could never get ADB Device to detect it in fastboot mode
Google: Android ADB Interface | Android Bootloader Interface | Android Composite ADB Interface
Intel: Android ADB Interface | Android Bootloader Interface | Intel AndroidADB Interface | Intel Android Bootloader Interface | Intel Android Composite ADB Interface
neghvar said:
None of the 8 drivers from Intel or Google detect the device in fastboot mode. I tried fixing this tablet years ago and had the fastboot drivers. As far as I know I have the same ones. These all loaded with no problem, but I could never get ADB Device to detect it in fastboot mode
Google: Android ADB Interface | Android Bootloader Interface | Android Composite ADB Interface
Intel: Android ADB Interface | Android Bootloader Interface | Intel AndroidADB Interface | Intel Android Bootloader Interface | Intel Android Composite ADB Interface
Click to expand...
Click to collapse
Make sure you enable usb debugging, no driver will work without that enabled.
tralph3 said:
Make sure you enable usb debugging, no driver will work without that enabled.
Click to expand...
Click to collapse
Not possible. This hangs during boot up or I can enter fast boot mode. It has been like this for years. Basically a soft brick. I tried to fix this years ago as stated above, but having seen this latest post about it, I decided to try again. But this time, I cannot find a fastboot driver that shows the device as attached when I run ADB devices
neghvar said:
Not possible. This hangs during boot up or I can enter fast boot mode. It has been like this for years. Basically a soft brick. I tried to fix this years ago as stated above, but having seen this latest post about it, I decided to try again. But this time, I cannot find a fastboot driver that shows the device as attached when I run ADB devices
Click to expand...
Click to collapse
Be aware that when in fastboot mode, adb devices never lists anything, you must use "fastboot devices"
tralph3 said:
Be aware that when in fastboot mode, adb devices never lists anything, you must use "fastboot devices"
Click to expand...
Click to collapse
Yep! That's where I was messing up. Thank you.
And the tablet is now working. Thank you very much.
One last question though. I tried to install the twrp.img file included in the pack
fastboot flash recovery TWRP.img
Here is what I got
Sending 'recovery' (26588 KB) (bootloader) Ready to receive: 0x019f7000 size of data
OKAY [ 0.741s]
Writing 'recovery' (bootloader) Flashing partition: recovery
FAILED (remote: ' Download image size is large than partition size')
fastboot: error: Command failed
How do I get around this if the image file is too large?
neghvar said:
Yep! That's where I was messing up. Thank you.
And the tablet is now working. Thank you very much.
One last question though. I tried to install the twrp.img file included in the pack
fastboot flash recovery TWRP.img
Here is what I got
Sending 'recovery' (26588 KB) (bootloader) Ready to receive: 0x019f7000 size of data
OKAY [ 0.741s]
Writing 'recovery' (bootloader) Flashing partition: recovery
FAILED (remote: ' Download image size is large than partition size')
fastboot: error: Command failed
How do I get around this if the image file is too large?
Click to expand...
Click to collapse
Yeah I never could get around it either. I never could install a custom recovery on this tablet, it just wasn't made for it. But hey, root is cool.
Work?
Still working?
jerryspring said:
Still working?
Click to expand...
Click to collapse
Why wouldn't it? This tablet ain't gonna change. Everything should work no problem.
Hi, any custom rom for this device to make it useful ?
It is in my drawer for more than 2 years and I just do not know what with it
Also how to play with settings in root mode so I can make it faster ?
Hey folks,
I recently followed this guide and a couple of issues.
First, I had expected all my data to be gone, which is fine. But it wasn't. I seemed to have gotten all the way through without it being reformatted, and this makes me suspect I never really achieved all the goals.
One thing I should note, in recovery boot, I had to use the volume button to select a source. No big deal, but it had not worked until I guessed I needed to do that.
Oh, and another thing is I had to install the driver package, and then after, once it was rebooted into fastboot, manually guide the device manager to select from list.
It seems after complete shutdown and then a fresh bootup, my SuperSU software was gone. So, is this only a tethered root boot? Is there a completely untethered?
After rebooting again, it seems my device will not complete booting, but I will give it some more time. I may have bricked it, though I have no idea how lol. All I did was enable USB debugging again and issued the reboot command.
I know this is an old guide, and probably long forgotten by most participants, but I recently got one of these tablets online, open box but new or like new, for around $20, and I would like to get it rooted because otherwise, it is extremely sluggish and the battery drains very fast. I read online it is google play services at fault, but I do not know for sure.
Anyway, if anyone has any updated info or alternative method to achieve full root access untethered, please advise. Unless this guide is that, in which case I just need to try again. Just out of curiosity, what is the TWRP.img for?
Good day community,
My Stick Gen 2 tried to do an update and somehow got bricked. The stick boots up to "installing new updates" then goes into a bootloop.
I tried the unbrick/root solution but the stick does not boot into fastboot, but instead tries to install updates again.
Is there a way to cancel this update step and just flash a stock rom?
Your help is much appreciated!
Regards
Phaisto
Phaisto said:
Good day community,
My Stick Gen 2 tried to do an update and somehow got bricked. The stick boots up to "installing new updates" then goes into a bootloop.
I tried the unbrick/root solution but the stick does not boot into fastboot, but instead tries to install updates again.
Is there a way to cancel this update step and just flash a stock rom?
Your help is much appreciated!
Regards
Phaisto
Click to expand...
Click to collapse
If you have done the unlock/root thing, you can boot to twrp recovery with the boot-recovery script... take a look in the unlock thread.
In TWRP you can flash the latest prerooted rom for your 'tank' device (or a stock update.bin renamed to zip, if you have one), wipe cache and dalvic cache.
Before you reboot, you could delete the ota update file, it's on sdcard... you can google the path. Then reboot.
Sus_i said:
If you have done the unlock/root thing, you can boot to twrp recovery with the boot-recovery script... take a look in the unlock thread.
In TWRP you can flash the latest prerooted rom for your 'tank' device (or a stock update.bin renamed to zip, if you have one), wipe cache and dalvic cache.
Before you reboot, you could delete the ota update file, it's on sdcard... you can google the path. Then reboot.
Click to expand...
Click to collapse
Hi, thanks for your quick reply!
Unfortunately the unlock doesn't run through, it does not boot into the fastboot mode, so I can not run fastboot-step, and therefore I do not have twrp...
Is there an other option to send a "kill-order" to stop the installing? Maybe during bootrom step?
Adb is not available....
Phaisto said:
Hi, thanks for your quick reply!
Unfortunately the unlock doesn't run through, it does not boot into the fastboot mode, so I can not run fastboot-step, and therefore I do not have twrp...
Is there an other option to send a "kill-order" to stop the installing? Maybe during bootrom step?
Adb is not available....
Click to expand...
Click to collapse
Is the ota really looping?
You see the update screen?
You may test the first script again. Start it, then plug the stick in without any short...
Then report back, please
Sus_i said:
Is the ota really looping?
You see the update screen?
You may test the first script again. Start it, then plug the stick in without any short...
Then report back, please
Click to expand...
Click to collapse
Yes, I see the update screen, the bootrom-step goes through until the script says "reboot to fastboot". When I put sudo bash fastboot- step.sh, it's just waiting for device and the update loops again...
https://photos.app.goo.gl/cnz3JEwhQL1G4Gbp7
https://photos.app.goo.gl/SNK9c7Ly43a3NuVx6
If I plug the stick in without short, the bootrom-step is waiting for device...
Phaisto said:
Yes, I see the update screen, the bootrom-step goes through until the script says "reboot to fastboot". When I put sudo bash fastboot- step.sh, it's just waiting for device and the update loops again...
https://photos.app.goo.gl/cnz3JEwhQL1G4Gbp7
https://photos.app.goo.gl/SNK9c7Ly43a3NuVx6
If I plug the stick in without short, the bootrom-step is waiting for device...
Click to expand...
Click to collapse
ok, don't know, maybe @k4y0z can tell you what to do...
Edit: I suppose you have disabled modemmanager and installed the required packages, i.e python3 python3-serial adb-tools-adb adb-tools-fastboot ??
Sus_i said:
ok, don't know, maybe @k4y0z can tell you what to do...
Edit: I suppose you have disabled modemmanager and installed the required packages, i.e python3 python3-serial adb-tools-adb adb-tools-fastboot ??
Click to expand...
Click to collapse
Yes, all the packages are installed as in the unlock threat, I copy/pasted the inputs. Modemmanager was removed as well.
Phaisto said:
Yes, all the packages are installed as in the unlock threat, I copy/pasted the inputs. Modemmanager was removed as well.
Click to expand...
Click to collapse
Ok, I've seen that behavior somewhere months ago, but I can't remember what causes that.
Unfortunately you can't delete the update package without adb... and you need twrp to flash a new system.
Your best bet is to do the unlock, flash a prerooted rom, flash magisk.zip, wipe cache and dalvic, and then delete that update package with adb shell:
Code:
rm -f /sdcard/Android/data/com.amazon.device.software.ota/files/*.bin
or twrp file manager, if you have an otg cable and a mouse.
Sus_i said:
Ok, I've seen that behavior somewhere months ago, but I can't remember what causes that.
Unfortunately you can't delete the update package without adb... and you need twrp to flash a new system.
Your best bet is to do the unlock, flash a prerooted rom, flash magisk.zip, wipe cache and dalvic, and then delete that update package with adb shell:
or twrp file manager, if you have an otg cable and a mouse.
Click to expand...
Click to collapse
That was exactly my plan for unlocking the stick in the hope of deleting that pesky update file. But I can not manage to get the twrp installed. As far I can understand it is installed with the fastboot-step script. But to execute this script I need the stick to enter fastboot, somehow the update is blocking that. Is there a way to modify the bootrom-step script to delete it, or wipe something?
Phaisto said:
That was exactly my plan for unlocking the stick in the hope of deleting that pesky update file. But I can not manage to get the twrp installed. As far I can understand it is installed with the fastboot-step script. But to execute this script I need the stick to enter fastboot, somehow the update is blocking that. Is there a way to modify the bootrom-step script to delete it, or wipe something?
Click to expand...
Click to collapse
No. You can't improve the scripts
Usually that whole unlock thing is done in 5 minutes, including booting linux and disassemble the stick
Something must be wrong on your side.
Sus_i said:
No. You can't improve the scripts
Usually that whole unlock thing is done in 5 minutes, including booting linux and disassemble the stick
Something must be wrong on your side.
Click to expand...
Click to collapse
I meant, if there is a possibility to add a function to the script to delete the update.
And yes, I know that the scripts are very good, and I also realize that the issue is with my stick not the script....
Phaisto said:
I meant, if there is a possibility to add a function to the script to delete the update.
And yes, I know that the scripts are very good, and I also realize that the issue is with my stick not the script....
Click to expand...
Click to collapse
Why you run the scripts with bash instead of dash?
Have you downloaded and extracted the amonet.zip with windows?
You may test this out...
Plug your stick into a hdmi port. Run the boot-fastboot script with:
sudo ./boot-fastboot.sh
then power the stick with your laptop.
If you see on your TV down in the left corner a hacked fastboot message together with the amz. logo, it worked.
You can then try a fastboot devices...
Sus_i said:
Why you run the scripts with bash instead of dash?
Have you downloaded and extracted the amonet.zip with windows?
You may test this out...
Plug your stick into a hdmi port. Run the boot-fastboot script with:
sudo ./boot-fastboot.sh
then power the stick with your laptop.
If you see on your TV down in the left corner a hacked fastboot message together with the amz. logo, it worked.
You can then try a fastboot devices...
Click to expand...
Click to collapse
I have downloaded the zip- files with Ubuntu and extracted as well. I used bash, as I saw it in the posts as a possible fix to problems, but my Linux knowledge is limited so I just used it without thinking about it....
I just tried your suggestions, but no luck. The stick stays on the Amazon logo and doesn't go into the update cycle ( maybe small victory?).
I tried to redo the bootrom step, after it finished, took the USB off, run boot-fastboot followed by fastboot-step, but as you can see, still stuck in waiting for device....
https://photos.app.goo.gl/BAL9V2sQhjowTq498
https://photos.app.goo.gl/iL5D3meE6LgNjdDW8
Any ideas?
Update: the device shows up on adb now, but unfortunately it is unauthorized.... Any chance to fix this?
Phaisto said:
I just tried your suggestions, but no luck. The stick stays on the Amazon logo and doesn't go into the update cycle ( maybe small victory?).
Click to expand...
Click to collapse
probably it goes into fastboot, but maybe not the unlocked hacked one
Phaisto said:
I tried to redo the bootrom step, after it finished, took the USB off, run boot-fastboot followed by fastboot-step, but as you can see, still stuck in waiting for device....
Any ideas?
Click to expand...
Click to collapse
have you tried to run: fastboot devices
behind the boot-fastboot script?
Phaisto said:
Update: the device shows up on adb now, but unfortunately it is unauthorized.... Any chance to fix this?
Click to expand...
Click to collapse
With TWRP shell you can authorize ADB access, like you can see in this link.
But without TWRP this won't work.
Sus_i said:
probably it goes into fastboot, but maybe not the unlocked hacked one
have you tried to run: fastboot devices
behind the boot-fastboot script?
With TWRP shell you can authorize ADB access, like you can see in this link.
But without TWRP this won't work.
Click to expand...
Click to collapse
No luck with fastboot devices:
https://photos.app.goo.gl/bd4Qrjr6si9b9gZm9
How come the script doesn't let the stick boot into hacked fastboot mode?
Anyone an idea?
Phaisto said:
No luck with fastboot devices:
https://photos.app.goo.gl/bd4Qrjr6si9b9gZm9
How come the script doesn't let the stick boot into hacked fastboot mode?
Anyone an idea?
Click to expand...
Click to collapse
I had trouble running the boot-fastboot script with ubuntu, debian worked as expected.
I would try also an other usb port/cable/hub.
Since amz. can't patch the exploit, there isn't a reason why it should not work.
Sus_i said:
I had trouble running the boot-fastboot script with ubuntu, debian worked as expected.
I would try also an other usb port/cable/hub.
Since amz. can't patch the exploit, there isn't a reason why it should not work.
Click to expand...
Click to collapse
Debian did not work either, same result....
Changing cable, same result....
I suspect, the bootrom-step script can't write the hacked fastboot...
Does anyone have an other idea how to fix this stick?
Amazon took the lazy way out and just offered 15% discount.... On a device their update broke....
Okay so when I flashed Magisk boot image my device activated boot problems. And when I tried to access recovery mode via adb (from Android Studio), my phone entered a bootloop from which I cannot exit.
Vol down + power buttons does not work. Neither does volum up + power. But when I press vol up+vol down+power my PC emits sound of connected device. I think that it is a problem of A/B partition, but I need to get to fastboot to fix it.
Any solution? I have already tried battery running out.
marcos_rgn said:
... my PC emits sound of connected device.
Click to expand...
Click to collapse
Yes, but what's it seeing?
You can poke around in Device Manager (View Devices by Connection can be helpful) and find which "device instance" is there.
You can also simply adb devices and fastboot devices to see if anything is there.
You could also try UsbLog.exe. Just run it and plug/unplug things.
.
Renate said:
Yes, but what's it seeing?
You can poke around in Device Manager (View Devices by Connection can be helpful) and find which "device instance" is there.
You can also simply adb devices and fastboot devices to see if anything is there.
You could also try UsbLog.exe. Just run it and plug/unplug things.
Click to expand...
Click to collapse
This is with usblog.exe.
I have checked and adb devices and fastboot devices are empty even while device is connected (in that 3 seconds window). I have runned some commands with "wait-for-device" and they didnt work.
So you have the MediaTek ROM bootloader there.
I've played with some of the MediaTek stuff (and even started to write a native Windows MTK client), but I'm no expert.
There are two modes, 0e8d/0003 (ROM) and 0e8d/2000 (preloader).
You might look here: https://github.com/bkerler/mtkclient
Try holding the VolUp while rebooting to try to get 2000.
I hope that you have a copy of your original boot? You can flash it back and see if things work.
It's always good to have a good recovery before you get deep in modification.
you can flash with this spflash tool to take back your phone.
SP Flash Tool v5.2044 Edited By Kurdish Gsm Team (Free Downlowd)
SP Flash Tool v5.2044 Modefiad Version With Auth Bypass Button
www.firmware4mobile.com
here is the video tutorial
Renate said:
I hope that you have a copy of your original boot? You can flash it back and see if things work.
It's always good to have a good recovery before you get deep in modification.
Click to expand...
Click to collapse
I have stopped boot loop by flashing boot.img and vbmeta.img with MTK client, thank you!
Generally speaking, if I want to return to default ROM, what files should I flash? What are the "software pieces" that Magisk touches and modify?
marcos_rgn said:
What are the "software pieces" that Magisk touches and modify?
Click to expand...
Click to collapse
Normally, Magisk only needs to have the boot image replaced.
The instructions tell you to optionally make the vbmeta inactive, but Magisk ignores all that verification anyway.