Flash at your own risk!
Not responsible for any damage you may do by attempting to modify stock software!
Recovery will work on all Shield 16GB 2015, Shield Pro 2015 & Shield 2017 16GB. All models...
You need ADB and FASTBOOT to get this installed.
You can follow this guide HERE or HERE
See attachments below for download.
Update 02/01/17
Added proper device info for 2017 Shield 16GB to allow OTA updates. Should work but not 100% sure if it will.
Extract img file from within zip folder
Reboot to bootloader
Use one of the two following commands
To flash recovery
fastboot flash recovery recovery.img
To boot into recovery without flashing
fastboot boot recovery.img
---
Thanks to TWRP for making the sources available and to @Steel01 for his work on TWRP for original shield which this was ported from.
Might be a stupid question but will this be OK to use on the 1st gen 16gb version aswel?
Slayerkodi said:
Might be a stupid question but will this be OK to use on the 1st gen 16gb version aswel?
Click to expand...
Click to collapse
I doubt it since 2015 TWRP did not work on 2017.
Slayerkodi said:
Might be a stupid question but will this be OK to use on the 1st gen 16gb version aswel?
Click to expand...
Click to collapse
The files system files between 2017 and 2015 are different you can try it, you wont hurt anything, but i doubt it will work. if you do try it do fastboot boot and not fastboot flash
My laptops broke so won't be doing this anytime soon, will see if there is a way to flash twrp to recovery without a PC because as far I know android to android adb or fastboot does not work
I'll definitely test it in a few hours when I get home.
not booting for me
jonasgrosch said:
not booting for me
Click to expand...
Click to collapse
4K TV?
If yes, hook it up to 1080 TV or monitor.
AndroidUser00110001 said:
4K TV?
If yes, hook it up to 1080 TV or monitor.
Click to expand...
Click to collapse
no it'S 1080p. tried by flashing and direct booting. both will kinda flash the screen after booting, turn off the shield and reboot it after.
the short flashing screen is the only difference to my tests with the unhacked image of twrp.
jonasgrosch said:
no it'S 1080p. tried by flashing and direct booting. both will kinda flash the screen after booting, turn off the shield and reboot it after.
the short flashing screen is the only difference to my tests with the unhacked image of twrp.
Click to expand...
Click to collapse
your bootloader unlocked?
brandonb21 said:
your bootloader unlocked?
Click to expand...
Click to collapse
yes of course
jonasgrosch said:
yes of course
Click to expand...
Click to collapse
other people in the Q&A thread are saying it works fine. try another 1080p tv/monitor and make sure your using 5.0.1 non developer image on your 2017 shield
brandonb21 said:
other people in the Q&A thread are saying it works fine. try another 1080p tv/monitor and make sure your using 5.0.1 non developer image on your 2017 shield
Click to expand...
Click to collapse
tried with another screen. nothing changed. still not working
---------- Post added at 10:25 PM ---------- Previous post was at 10:18 PM ----------
jonasgrosch said:
tried with another screen. nothing changed. still not working
Click to expand...
Click to collapse
nevermind. got it working by disconnecting usb connection to my pc right after executing the boot command.
Are all the partitions showing up in TWRP that should be? I never put TWRP on my 2015 Shield Pro so not sure what should be showing up.
On my 2017 I can only write to the TWRP folder using the USB cable connected to my PC. I tried to put in a USB stick but TWRP did not recognize it nor does it recognize External Storage.
I have USB hard drive formatted for internal storage so not sure if that is why I don't see any partitions in TWRP and can only write to the TWRP folder.
I am about to build TWRP from source and was just wondering what partitions shows up from more experienced users so I can adjust the TWRP settings so more partitions show up if that is the cause....
AndroidUser00110001 said:
Are all the partitions showing up in TWRP that should be? I never put TWRP on my 2015 Shield Pro so not sure what should be showing up.
On my 2017 I can only write to the TWRP folder using the USB cable connected to my PC. I tried to put in a USB stick but TWRP did not recognize it nor does it recognize External Storage.
I have USB hard drive formatted for internal storage so not sure if that is why I don't see any partitions in TWRP and can only write to the TWRP folder.
I am about to build TWRP from source and was just wondering what partitions shows up from more experienced users so I can adjust the TWRP settings so more partitions show up if that is the cause....
Click to expand...
Click to collapse
I just got an email from nvidia and they processed my rma and now waiting for a tracking number i doubt il see mine till next week or i would help you out.
gunner007dc said:
I was able to unlock the bootloader, enable USB debugging.
I tried flashing the TWRP image, however attempting to boot into recovery gives the sad little android man with the red exclamation (NO COMMAND)
If I attempt to just boot the image I see the TWRP splash screen, then a few seconds later the system reboots.
Click to expand...
Click to collapse
try disconnecting the usb cable going from your pc to your android box right after hitting enter after typing "fastboot boot twrp.img"
seems to be a bug. make sure it downloads the image all the way before disconnecting.
gunner007dc said:
Yep that seemed to do it. I flashed TWRP already, just when I typed adb reboot recovery, you just have to disconnect the USB. Then it booted into TWRP just fine.
Stupid question, but is it best practice to just install the dev image + SuperSU at this point. It's what I'm currently running, but didn't know if it was just better to run stock image + SuperSU. (or maybe dev is needed for root)
Click to expand...
Click to collapse
use the retail one, the dev image can run beta drivers such as graphic drivers that may or may not cause issues at some point. and the developer image dosent get ota updates.
Was able to root mine as well by pulling out the usb cable while booting into twrp. Thanks Guys!
how do u install supersu with the usb cable disconnected?
brand0n9 said:
how do u install supersu with the usb cable disconnected?
Click to expand...
Click to collapse
Enable MTP in TWRP, plug USB cable in and then transfer SU to the internal drive?
Related
It's finally here! TWRP recovery for the Fire TV 1. Most likely, I will not be updating this thread with new releases, as the prerooted ROMs will always contain the latest version. This thread is just here so people on Fire OS 3 can install TWRP and people on rooted but locked bootloader Fire TV 1's can get recovery initially installed.
As usual, this WILL void your warranty and I am NOT responsible for anything you do with this. Installing it properly won't brick your Fire TV, but doing stupid things with it might.
Installing this requires root. If you are not rooted, figure that out first.
Installation for Unlocked Bootloader
Make sure you are on a FULLY unlocked bootloader. From within FireOS and after running su run this:
Code:
cat /proc/cmdline
And MAKE SURE unlocked_kernel=true is present! If it is not, you are NOT fully unlocked and you must Fully Unlock first!
Make sure you are on at least 51.1.4.0 ROM and the latest CWM installed.
Copy the bueller-twrp_3.0.0-6.img file to /sdcard
From within adb shell, use su to become root, and run this command (are you sure you did step 1?)
Code:
dd if=/data/media/0/bueller-twrp_3.0.0-6.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
From outside adb shell, reboot to recovery
Code:
adb reboot recovery
TWRP should load, you can install a FireOS5 prerooted ROM now.
Installation for Locked Bootloader
This requires that you are on at least version 5.0.5 and rooted.
Copy the bueller_recovery_vX.zip file to /sdcard
From within adb shell, use su to become root, and run this command (replace vX with the actual version you downloaded)
Code:
sh /data/media/0/bueller_recovery_vX.zip
Reboot
Notes
This includes bootmenu. For everyone that loved the old bootmenu with Comic Sans, I'm sorry to disappoint you, but the Comic Sans is gone. When the FireTV boots, it will present you with the bootmenu where you can leave it alone and it will boot normally or you can select recovery and it will boot in to recovery. You do need a USB keyboard to interact with the bootmenu. To force it to boot in to Recovery, you can create a file /cache/bootmenu_recovery.
DHCP for Ethernet is enabled, and if there is enough demand I may add in wifi at some point. The IP address should show up in the top left corner.
USB storage and USB keyboard/mice should all work. Hotplugging works, so you should be able to plug and unplug devices as needed.
You can use a USB keyboard, mouse, or the mouse emulator to interact with it. To use a keyboard, you can use the arrow keys to move the cursor and the enter key to select buttons. Sliders don't require sliding, so you can just hit enter/click on them. To use the mouse emulator, use adb shell and then run the program mouse and follow the instructions.
ROMs
Recovery must be included in all ROMs. If you want to develop a ROM, please contact me about including recovery in it.
Installing zips
You can push zips to /sdcard, put it on a USB storage, or use adb sideload. Do note you need adb version 1.0.32 to use adb sideload.
Stuck in a loop?
If you cannot boot normally and keep going back to the bootmenu, wipe Cache from Wipe -> Advanced Wipe.
Source Code
You can find the source code here:
https://github.com/androidrbox/firetv-2ndinit
https://github.com/androidrbox/android_bootable_recovery
WARNINGS
It is extremely important you never reboot after a failure. This will most likely lead to a brick. If recovery is hung, you can use adb shell to run
Code:
killall recovery
to restart it
It is also extremely important to never reboot after wiping /system.
Finally, thanks to everyone who has donated to me.
Changelog and Downloads:
July 7, 2016 - v2 (md5sum: 8f65187cb0cbc190a7d64f512ae3ede2)
This is the updated version with TWRP 3.0.0-7.
July 4, 2016 - TWRP Image 3.0.0-7 (md5sum: cda1a1c1cdd3e25a1caa86f5a5de1eee)
May 20, 2016 - v1 (md5sum: 9208d81fd07cff9952de5be33c62f730)
This is for use by people who have FireOS5 and are rooted.
This includes 2ndinit version a7a48c and TWRP version 3.0.0-6.
May 20, 2016 - TWRP Image (md5sum: 5dc83370046e5b50755ddb55fe8424ad)
This is for use by people who have FireOS3 and CWM and is TWRP version 3.0.0-6.
thanks so much rbox! just tested it and i can confirm that my firetv 1 with fireos3 and fully unlocked bootloader just installed twrp successfully - woot!
i still have the old boot menu though with comic sans..?
mrchrister said:
thanks so much rbox! just tested it and i can confirm that my firetv 1 with fireos3 and fully unlocked bootloader just installed twrp successfully - woot!
i still have the old boot menu though with comic sans..?
Click to expand...
Click to collapse
For unlocked bootloaders, this step JUST installs recovery. You need to install the prerooted rom to get the new bootmenu.
got you, downloading now
Sent from my iPhone using Tapatalk
I successfully dd'ed the recovery image onto my ftv with unlocked bootloader but attempting to boot it causes the TWRP logo to show for a few seconds, then the screen goes black and the cycle repeats. Any idea how to fix this?
ssgelm said:
I successfully dd'ed the recovery image onto my ftv with unlocked bootloader but attempting to boot it causes the TWRP logo to show for a few seconds, then the screen goes black and the cycle repeats. Any idea how to fix this?
Click to expand...
Click to collapse
If you unplug the power and replug it, it should boot normally, then you can see if the recovery log got saved, /cache/recovery/last_log and pastebin it.
The log at /cache/recovery/last_log is from CWM from the last time I flashed a new rom.
ssgelm said:
The log at /cache/recovery/last_log is from CWM from the last time I flashed a new rom.
Click to expand...
Click to collapse
Can't really explain why it would be doing that. Can you connect via adb?
I am not on ethernet right now. When I get a chance I'll do that and see if I can connect. Thanks so much for your work on this!
ssgelm said:
I successfully dd'ed the recovery image onto my ftv with unlocked bootloader but attempting to boot it causes the TWRP logo to show for a few seconds, then the screen goes black and the cycle repeats. Any idea how to fix this?
Click to expand...
Click to collapse
I'm also getting this, what can I do?
here's last_log
gehx said:
I'm also getting this, what can I do?
Click to expand...
Click to collapse
Can you connect via adb?
rbox said:
Can you connect via adb?
Click to expand...
Click to collapse
yep, that's how I pulled last_log
gehx said:
yep, that's how I pulled last_log
Click to expand...
Click to collapse
I meant while recovery is running.
rbox said:
I meant while recovery is running.
Click to expand...
Click to collapse
recovery never fully loads, i just get the twrp splash screen over and over and over again...it's in a loop
gehx said:
recovery never fully loads, i just get the twrp splash screen over and over and over again...it's in a loop
Click to expand...
Click to collapse
Yes. But have you tried using adb...
rbox said:
Yes. But have you tried using adb...
Click to expand...
Click to collapse
I'm not sure what IP to use?
gehx said:
I'm not sure what IP to use?
Click to expand...
Click to collapse
The same one the firetv would be using when it's booted... via ethernet of course.
rbox said:
The same one the firetv would be using when it's booted... via ethernet of course.
Click to expand...
Click to collapse
the connection times out:
adb connect 192.168.1.6
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
unable to connect to 192.168.1.6:5555: Operation timed out
Click to expand...
Click to collapse
gehx said:
the connection times out:
Click to expand...
Click to collapse
Can you pull the log again? It should say the ip in it actually.
rbox said:
Can you pull the log again? It should say the ip in it actually.
Click to expand...
Click to collapse
new last_log
it shows 192.168.1.8; I'm unable to adb connect to that IP too
OK, so I flashed TWRP and now I have sort of a halfway bricked x829- I can load TWRP and Fastboot, that's it. I can't adb sideload anything because I get a "cannot read" error. I also can't Fastboot flash anything because all the ROMs I can find are zip files, and not .img files. What am I doing wrong?
Wagmans said:
OK, so I flashed TWRP and now I have sort of a halfway bricked x829- I can load TWRP and Fastboot, that's it. I can't adb sideload anything because I get a "cannot read" error. I also can't Fastboot flash anything because all the ROMs I can find are zip files, and not .img files. What am I doing wrong?
Click to expand...
Click to collapse
ok why do you even want to flash the rom with adb/fastboot?
even if you forgot to cp the rom onto the sdcard - just flash with twrp from a stick - OTG works fine
Horsebeatsbishop said:
ok why do you even want to flash the rom with adb/fastboot?
even if you forgot to cp the rom onto the sdcard - just flash with twrp from a stick - OTG works fine
Click to expand...
Click to collapse
OTG not working for me either. I have a USB C to standard USB adapter and it doesn't see any flash drives (I can see the drive being accessed- the light flashes, but doesn't mount). Do I need a USB OTG C Y adapter? I'm a bit lost why I can't just adb sideload.
Someone explain it to me like I'm a child. Obviously I'm doing something wrong and I'm missing something.
Wagmans said:
OTG not working for me either. I have a USB C to standard USB adapter and it doesn't see any flash drives. Do I need a USB OTG C Y adapter? I'm a bit lost why I can't just adb sideload.
Someone explain it to me like I'm a child. Obviously I'm doing something wrong and I'm missing something.
Click to expand...
Click to collapse
ok sounds like a toughie - never had a problem with OTG (neither with fat32 nor ntfs both works (twpr 3.0.2.1 myself) )
since i'm just a beginner myself i can only give you ideas where i would look:
-do you even see your device in adb service?
-enabled usb-debug?
-current usb driver?
-current adb version?
-correct adb version (32/64b)?
Horsebeatsbishop said:
ok sounds like a toughie - never had a problem with OTG (neither with fat32 nor ntfs both works (twpr 3.0.2.1 myself) )
since i'm just a beginner myself i can only give you ideas where i would look:
-do you even see your device in adb service?
-enabled usb-debug?
-current usb driver?
-current adb version?
-correct adb version (32/64b)?
Click to expand...
Click to collapse
I flashed TWRP properly- but when I put it into recovery I get half a corrupted screen- after the screen goes off if I press the power button I can access TWRP.
I tried flashing multiple flash drives in different formats- yes, I can see the drive LEDs flash after I insert it, but when I try to mount it says "0" space for all drives.
So, I assume everything is working properly because adb can see the device in sideload mode (Win 10 device mgr shows it as a USB device, when in TWRP (no sideload mode) it sees it as ADB device- but when I try to run ADB it doesn't show any devices):
List of devices attached
17963e29 sideload
No devices listed when sideload in TWRP is off.
I should be able to sideload something, but I get:
loading: 'le_x2_x820-5.9.020S.zip'
* cannot read 'le_x2_x820-5.9.020S.zip' *
Every time- every file.
Bricked?
are you using the official twrp ?
you should... https://twrp.me/devices/leecolemax2.html
or use multirom.
you can also transfer the rom first using mtp (in twrp).and flash afterwards.
Gesendet von meinem LEX820 mit Tapatalk
A.N.Droid said:
are you using the official twrp ?
you should... https://twrp.me/devices/leecolemax2.html
or use multirom.
you can also transfer the rom first using mtp (in twrp).and flash afterwards.
Gesendet von meinem LEX820 mit Tapatalk
Click to expand...
Click to collapse
FlashTools64_20161125.zip
I figured it out. I had to download FlashTools64 from Asus in order to sideload the file without the "cannot read" error. Well, that took me all morning.
This should be posted in the TWRP sticky.
I'm sideloading a rom right now. Let's see what happens...
Wagmans said:
FlashTools64_20161125.zip
I figured it out. I had to download FlashTools64 from Asus in order to sideload the file without the "cannot read" error. Well, that took me all morning.
This should be posted in the TWRP sticky.
I'm sideloading a rom right now. Let's see what happens...
Click to expand...
Click to collapse
looks like the standard 15 sec adb installer to me... seems u had the wrong version
Horsebeatsbishop said:
looks like the standard 15 sec adb installer to me... seems u had the wrong version
Click to expand...
Click to collapse
I don't know- I dowloaded it right from the link in the TWRP thread.
Anyways. now when I'm sideloading a ROM it times out at 46% every time (TWRP stops sideload mode). Any ideas?
Wagmans said:
I don't know- I dowloaded it right from the link in the TWRP thread.
Anyways. now when I'm sideloading a ROM it times out at 46% every time (TWRP stops sideload mode). Any ideas?
Click to expand...
Click to collapse
I had sort of the same problem, your not encrypted are you?
Supertacomonkeyexplosion said:
I had sort of the same problem, your not encrypted are you?
Click to expand...
Click to collapse
Nope. Unless I can sideload a ROM I'm stuck because TWRP won't mount a flash drive for me.
why dont you transfer the zip first with mtp?
Gesendet von meinem LEX820 mit Tapatalk
Wagmans said:
Nope. Unless I can sideload a ROM I'm stuck because TWRP won't mount a flash drive for me.
Click to expand...
Click to collapse
You can't boot the OS at all ?
I flashed twrp, couldn't backup,side load or read any OTG. I ended up booting back into my stock OS, loosing twrp, putting teamspain cm13 on, reflashing twrp from fastboot then immediately booting into twrp and flashing CM zip.
Mine was encryption problem though, cm let me decrypt and twrp started working right
Supertacomonkeyexplosion said:
You can't boot the OS at all ?
I flashed twrp, couldn't backup,side load or read any OTG. I ended up booting back into my stock OS, loosing twrp, putting teamspain cm13 on, reflashing twrp from fastboot then immediately booting into twrp and flashing CM zip.
Mine was encryption problem though, cm let me decrypt and twrp started working right
Click to expand...
Click to collapse
Nope. Just TWRP, that's it. As for MTP it doesn't even show up- just as a Android ADB Device in the drivers when in TWRP, and as a USB Device in TWRP Sideload mode. Remember, I'm stuck in either TWRP or Fastboot mode.
Wagmans said:
Nope. Just TWRP, that's it. As for MTP it doesn't even show up- just as a Android ADB Device in the drivers when in TWRP, and as a USB Device in TWRP Sideload mode. Remember, I'm stuck in either TWRP or Fastboot mode.
Click to expand...
Click to collapse
you have strange issues. are you sure you installed the right twrp version for your device? a link would help.
about adb:
i'm using universal ADB drivers and it just works.
http://adbdriver.com
Gesendet von meinem LEX820 mit Tapatalk
Wagmans said:
Nope. Just TWRP, that's it. As for MTP it doesn't even show up- just as a Android ADB Device in the drivers when in TWRP, and as a USB Device in TWRP Sideload mode. Remember, I'm stuck in either TWRP or Fastboot mode.
Click to expand...
Click to collapse
Strange that you lost your OS just flashing a recovery image, I've never seen that before. My last suggestion would be to fastboot flash a earlier version of TWRP.
Not sure of you seen this..... Last resort if you can't figure it out
https://forum.xda-developers.com/le-max-2/how-to/guide-hard-brick-fix-qualcomm-hs-usb-t3492949
Getting closer- I gave up on sideloading and I was finally able to push a ROM to the phone.
Thanks for all the help guys. Now running Chinese .20s ROM. Took long enough.lol
Wagmans said:
Getting closer- I gave up on sideloading and I was finally able to push a ROM to the phone.
Thanks for all the help guys. Now running Chinese .20s ROM. Took long enough.lol
Click to expand...
Click to collapse
Glad you figured it out.
Your running Chinese 20s on x829?
Lots of people will be interested to know how it runs..... Fingerprint? Language? Band 20? VoLTE?
Supertacomonkeyexplosion said:
Glad you figured it out.
Your running Chinese 20s on x829?
Lots of people will be interested to know how it runs..... Fingerprint? Language? Band 20? VoLTE?
Click to expand...
Click to collapse
Been playing with it a bit:
Shows as X820 with 64GB
Fingerprint still doesn't work for me
Google Voice doesn't work- at least I haven't figured it out (Doesn't recognize "OK Google"- I have to go into the app by hand).
Same problem- no VoLTE on AT&T here in US (didn't think it would work- unsupported phone). On Band 2 with LTE (cycled it- was on band 17 before). Haven't checked the other bands yet.
Lots of bloatware. That I can deal with. If I can't get Google voice recognition working properly I'll probably go to a custom ROM.
Wagmans said:
Getting closer- I gave up on sideloading and I was finally able to push a ROM to the phone.
Thanks for all the help guys. Now running Chinese .20s ROM. Took long enough.lol
Click to expand...
Click to collapse
You should share how did u fix it for helping other people in the future
Enviado desde mi ASUS_Z00TD mediante Tapatalk
So after a while of tinkering with my Honor 9 trying to flash Supersu via TWRP everything got messed up.
Tried doing a clean install, and that made everything worse.
So now i am stuck with no TWRP Recovery and cannot load the Fastboot. Only option available now is Huawei eRecovery through wifi that obviously doesnt work, and forced recovery (vol+ and vol- and powerbutton) which is also not working trying to flash with stockrom.
So what can i do now? am i missing something?
Inisio said:
So after a while of tinkering with my Honor 9 trying to flash Supersu via TWRP everything got messed up.
Tried doing a clean install, and that made everything worse.
So now i am stuck with no TWRP Recovery and cannot load the Fastboot. Only option available now is Huawei eRecovery through wifi that obviously doesnt work, and forced recovery (vol+ and vol- and powerbutton) which is also not working trying to flash with stockrom.
So what can i do now? am i missing something?
Click to expand...
Click to collapse
Do you have your PC connected via USB to your phone when trying to boot to fastboot?
completely power off phone, then hold vol-down and plug in USB cable... this should boot you into fastboot, try and flash TWRP from there, although, if you dont have the required files on your device (or any way to get them onto it) you are not in a good situation.
something similar happened to me the other day, and this got me into fastboot where i could flash a system.img (or use HWOTA or whatever it is), though i had TWRP installed, but no OS.
fregor said:
Do you have your PC connected via USB to your phone when trying to boot to fastboot?
Click to expand...
Click to collapse
Yeah, did that now and it worked. Although my previous attempts doing this nothing happened. But i am in the fastboot now atleast, bad news is that my device doesnt come up when using the apb devices command.
Any tips on what to do now? i suppose my device isnt showing because i cant use debug mode?
Inisio said:
Yeah, did that now and it worked. Although my previous attempts doing this nothing happened. But i am in the fastboot now atleast, bad news is that my device doesnt come up when using the apb devices command.
Any tips on what to do now? i suppose my device isnt showing because i cant use debug mode?
Click to expand...
Click to collapse
There's a lot of options on this forum if you have fastboot access and TWRP. So you should be able to get back to where you were before tinkering.
I recommend an external SD card reader to get necessary files on a SD card.
fregor said:
There's a lot of options on this forum if you have fastboot access and TWRP. So you should be able to get back to where you were before tinkering.
I recommend an external SD card reader to get necessary files on a SD card.
Click to expand...
Click to collapse
Yeah, i have been looking around on the forum alot, but almost every thread with a similiar problem they still have access to TWRP, which i dont sadly :/.
Inisio said:
Yeah, i have been looking around on the forum alot, but almost every thread with a similiar problem they still have access to TWRP, which i dont sadly :/.
Click to expand...
Click to collapse
You should be able to flash it in fastboot though. If your fastboot is locked and frp is locked, you have a problem.
Not sure if recovery in Hisuite might be an option.
Sent from my STF-L09 using Tapatalk
fregor said:
You should be able to flash it in fastboot though. If your fastboot is locked and frp is locked, you have a problem.
Sent from my STF-L09 using Tapatalk
Click to expand...
Click to collapse
yeah, i'm gonna see if i can come up with a way to flash it. Even though i cant find it using ADB anymore, there might some other way.
do you think it's possible doing this using the eRecovery Forced update?
Try this with a sdcard:
https://forum.xda-developers.com/showthread.php?t=3696892
oslo83 said:
Try this with a sdcard:
https://forum.xda-developers.com/showthread.php?t=3696892
Click to expand...
Click to collapse
So another problem, cant move bigger files than 4gb to the SD card. And cant format in NTFS because it seems like the phone wont take it.
but using a tempfile from a failed transfer the install at least starts, and ofcourse fails after a while since its incomplete. But how can i transfer the UPDATE.APP file to the card?
Inisio said:
So another problem, cant move bigger files than 4gb to the SD card. And cant format in NTFS because it seems like the phone wont take it.
but using a tempfile from a failed transfer the install at least starts, and ofcourse fails after a while since its incomplete. But how can i transfer the UPDATE.APP file to the card?
Click to expand...
Click to collapse
Format to exfat
Sent from my STF-L09 using Tapatalk
fregor said:
Format to exfat
Sent from my STF-L09 using Tapatalk
Click to expand...
Click to collapse
That did it, never thought of exfat! New firmware installed, thanks alot for the help!
While I tried to root using TWRP and all the suggested ways i continued to get errors, bootloops, corrupted boot, etc. I downloaded the rooted developers OS Image, then used magisk to patch the boot image. If anyone has any interest in the Boot.img or the developers OS image, let me know i can post links and instructions if needed. This will require the bootloader unlocked (i have read you can unlock with a keyboard, but i never had any luck and used a controller). Please reply with requests if needed.
Just one question: When you install the NEXT developer image, how will you go about retaining Magisk and your boot.img patch? Don't need a step-by-step-- just in simple terms. Curious.
EDIT: Found my answer: https://forum.xda-developers.com/showpost.php?p=77162700&postcount=85
I have a question i dont want create a thread for this so with root its possible to use 2 usb drive ?because for only the one right on the HDMI cable Work
laharl_22 said:
I have a question i dont want create a thread for this so with root its possible to use 2 usb drive ?because for only the one right on the HDMI cable Work
Click to expand...
Click to collapse
I'm not sure, but i think its possible to use 2 USB drives now if you turn off adb debugging or use a hub.
Michajin said:
I'm not sure, but i think its possible to use 2 USB drives now if you turn off adb debugging or use a hub.
Click to expand...
Click to collapse
Thanks it work
This is really good, thanks, so i can use flash this 7.0.2 boot.img on top of the latest "nv-recovery-image-shield-atv-7.1.0-dev_rooted" without any issues?
@Michajin Can you please share your boot.img that is patched with magisk?
samjoandco said:
This is really good, thanks, so i can use flash this 7.0.2 boot.img on top of the latest "nv-recovery-image-shield-atv-7.1.0-dev_rooted" without any issues?
@Michajin Can you please share your boot.img that is patched with magisk?
Click to expand...
Click to collapse
What version are you on? I downloaded the full zip, put the unzipped file on a USB from a computer. Then Took the USB to my Shield ran magisk manager 6.0 and installed, selecting patch boot, selecting the file from the USB. Magisk places the patched boot into my download folder where i pulled back onto my computer the fastboot flash boot boot.img (or patched_boot.img whatever the file is called that got patched).
I have the patched 7.1 boot.img right now. I have the full developers files, with drivers and patch all in it for 7.1 with magisk manager if you want i can put it on my Google drive for the whole thing. It is 1.09 Gb for the full files.
samjoandco said:
This is really good, thanks, so i can use flash this 7.0.2 boot.img on top of the latest "nv-recovery-image-shield-atv-7.1.0-dev_rooted" without any issues?
@Michajin Can you please share your boot.img that is patched with magisk?
Click to expand...
Click to collapse
Guess i Didn't read very well! Here is the Boot.img for magisk 7.1.
fastboot flash boot boot.img
Use 7-zip to unzip, had to make it a tar to upload here (12mbs)
How to fix a bootloader who not boot ? I have only bootloader IS unlocked warning screen and NVIDIA logo but no os and unable to boot bootloader or twrp
laharl_22 said:
How to fix a bootloader who not boot ? I have only bootloader IS unlocked warning screen and NVIDIA logo but no os and unable to boot bootloader or twrp
Click to expand...
Click to collapse
I am assuming you have a nvidia shield 2017
Download the full image from nvidia here
https://developer.nvidia.com/gameworksdownload#?search=SHIELD%20TV%202017%20Developer&tx=$additional,shield
Connect via fastboot (plug in controller press A - B and power on)
From fastboot connect with a computer via A-A usb cable
unzip the file from nvidia into the folder where your fastboot drivers are
run the flash-all.bat file
Michajin said:
Guess i Didn't read very well! Here is the Boot.img for magisk 7.1.
fastboot flash boot boot.img
Use 7-zip to unzip, had to make it a tar to upload here (12mbs)
Click to expand...
Click to collapse
Thanks Michajin, much appreciated, I will try it on the weekend! :highfive::good:
One question:
I am on the latest 7.1.0 but not on developer image, can i just unlock the bootloader and flash the boot image to get root ?
or i need to installed the developer version (nv-recovery-image-shield-atv-7.1.0-dev_rooted)?
I dont want to install everything again.
samjoandco said:
Thanks Michajin, much appreciated, I will try it on the weekend! :highfive::good:
One question:
I am on the latest 7.1.0 but not on developer image, can i just unlock the bootloader and flash the boot image to get root ?
or i need to installed the developer version (nv-recovery-image-shield-atv-7.1.0-dev_rooted)?
I dont want to install everything again.
Click to expand...
Click to collapse
As far as i know Unlocking erases data anyways. You unlock you have to reinstall everything anyways.
The boot image works only on developer image? Thanks
gas80 said:
The boot image works only on developer image? Thanks
Click to expand...
Click to collapse
I don't know what the differences are between the dev image and the regular version. I believe the dev version is just pre-rooted. I think it will work, but i have only tested on the dev image. Flash at your own risk.
Hi there,
I need help. Im looking for a ROM thats flashable with TWRP so i can install it. Previously I had Lineageos installed but it wasnt running smooth enough.
I cant install the rooted recovery file from Nvidia with TWRP.
The reason why im wanting to use TWRP is because i want to use Magisk with the Shield.
Ive allready patched a stock boot image with magisk version 17.1
my current Twrp version is 3.2.1-1
Thank you very much
cheers
[Edit]
I solved the problem by following this post
thanks
Michajin said:
What version are you on? I downloaded the full zip, put the unzipped file on a USB from a computer. Then Took the USB to my Shield ran magisk manager 6.0 and installed, selecting patch boot, selecting the file from the USB. Magisk places the patched boot into my download folder where i pulled back onto my computer the fastboot flash boot boot.img (or patched_boot.img whatever the file is called that got patched).
I have the patched 7.1 boot.img right now. I have the full developers files, with drivers and patch all in it for 7.1 with magisk manager if you want i can put it on my Google drive for the whole thing. It is 1.09 Gb for the full files.
Click to expand...
Click to collapse
Could you please upload it on google drive. That would be greatly appreciated. :good:
gambaaa said:
Could you please upload it on google drive. That would be greatly appreciated. :good:
Click to expand...
Click to collapse
I dont know if it sent, here is a link for the dev image with magisk installed on the boot.img. The original and patched boot.img are in the zip file., along with the magisk app.
Please flash at you own risk, i have the 2017 shield and it worked for me. I ran the flash-all.bat.
Here is a link to the file on my GDrive ( I will be blocking access after the weekend)
Goodluck,
Michajin
Michajin said:
I dont know if it sent, here is a link for the dev image with magisk installed on the boot.img. The original and patched boot.img are in the zip file., along with the magisk app.
Please flash at you own risk, i have the 2017 shield and it worked for me. I ran the flash-all.bat.
Here is a link to the file on my GDrive ( I will be blocking access after the weekend)
https://drive.google.com/open?id=15sJ6YFmwiAZX0mXQk_ANq5Nfvs9E8oJF
Goodluck,
Michajin
Click to expand...
Click to collapse
Great job! I will try it this week-end. So I just plug my nvidia shield via usb and run the flash-all.bat ? Also, do I need to unlock my bootloader before doing anything. I have stock 8.0 oreo
gambaaa said:
Great job! I will try it this week-end. So I just plug my nvidia shield via usb and run the flash-all.bat ? Also, do I need to unlock my bootloader before doing anything. I have stock 8.0 oreo
Click to expand...
Click to collapse
Yes, as far as i know you have to have an unlocked bootloader. You plug in your Sheild VIA a-a USB, you might have to install the sheild drivers. Press AB on your controller and power on. That will get you into fastboot. You have to run the unlock bootloader command WARNING this will wipe your DATA. All the drivers you need will be on this page available to download https://developer.nvidia.com/shield-open-source and for instructions on how-to goto here http://nv-tegra.nvidia.com/gitweb/?...;f=README_NEW_SHIELD;hb=rel-24-uda-r1-partner (the instructions tell how to do flash each file, i found it faster to do the flash-all.bat, but be patient, i think it takes about 30 minutes)
Michajin said:
Yes, as far as i know you have to have an unlocked bootloader. You plug in your Sheild VIA a-a USB, you might have to install the sheild drivers. Press AB on your controller and power on. That will get you into fastboot. You have to run the unlock bootloader command WARNING this will wipe your DATA. All the drivers you need will be on this page available to download https://developer.nvidia.com/shield-open-source and for instructions on how-to goto here http://nv-tegra.nvidia.com/gitweb/?...;f=README_NEW_SHIELD;hb=rel-24-uda-r1-partner (the instructions tell how to do flash each file, i found it faster to do the flash-all.bat, but be patient, i think it takes about 30 minutes)
Click to expand...
Click to collapse
Wonderful! Thanks for the explanation!
Unofficial TWRP Recovery for Moto G7 Power
(XT1955-5/ocean/supra)
I didn't want to wait any longer for an official build of TWRP for the Moto G7 Power (ocean) so I ported it over myself following these directions . So far it appears to work with little to no issue with the exception of decryption of userdata on later rom buids...
I was even able to install fastboot(ed) image to ramdisk & flash Magisk-19.3 via TWRP. Hopefully this can hold some of you off until an official build comes out.
If you guys wish to try it out I have uploaded it to my Android file host here.
Latest attempt HERE
Installation Instructions:
1. You will need to boot image via fastboot initially
Code:
fastboot boot twrp-3.3.1-0-ocean-20190904-0715.img
2. Once TWRP boots push Magisk v19.3 to /tmp/ & flash if not installed or you will bootloop
a.
Code:
adb push Magisk-v19.3.zip /tmp/
b.
Code:
adb shell
c.
Code:
twrp install /tmp/Magisk-v19.3.zip
3. Push twrp-3.3.1-0-ocean-20190904-0715.img to /tmp/
Code:
adb push twrp-3.3.1-0-ocean-20190904-0715.img /tmp/
4. Install recovery to ramdisk via fastboot(ed) TWRP
Code:
Tap Advanced > Install Recovery Ramdisk > Navigate to /tmp/twrp-3.3.1-0-ocean-20190904-0715.img
5. If Magisk is installed prior you may bootloop back to recovery
Code:
Advanced > Fix Recovery Bootloop & Reinstall Magisk
NOTE:
When providing feedback please include the build date of port, carrier, security patch, and rom build number of your G7 Power. The last two items can be found in Settings > System > About phone > tap Android version .
E.g.
20190904-0715
Metro
March 1, 2019
PCO29.114-54-2
good, step 1 is in fastboot mode, the 2,3,4 is the pc? or how can I flash
Yes 1 - 2 PC. 3-4 in TWRP. Pretty simple.
Geofferey said:
Yes 1 - 2 PC. 3-4 in TWRP. Pretty simple.
Click to expand...
Click to collapse
install very well start but not let me do anything on the mobile screen does not respond
Alexhdavila said:
install very well start but not let me do anything on the mobile screen does not respond
Click to expand...
Click to collapse
yes, but when it is installed to the device Ramboot, the screen responds then. Use this image to boot TWRP, then use it to install G's build
---------- Post added at 08:10 PM ---------- Previous post was at 07:49 PM ----------
https://drive.google.com/open?id=1n2YwMJ0CcZU5rze6ibaOM68Ox6bxPL9M
One problem i see here, is that TWRP doesn't decrypt storage when formatting.. GSI systems say it's encrypted still.. isn't it supposed to decrypt when formatting?
Scholeggo said:
One problem i see here, is that TWRP doesn't decrypt storage when formatting.. GSI systems say it's encrypted still.. isn't it supposed to decrypt when formatting?
Click to expand...
Click to collapse
The touch screen works for me when I fastboot it & it works when installed to ramdisk.
I think it worked for me when I used the format data option that requires typing yes. What GSI's are you using? I attempted to install one last night no data/wifi.
@Alexhdavila @Scholeggo
I will need more info. Does touchscreen work when booting via fastboot? Do you have a non US variant? What is output of command lsmod through adb shell in Android?
I can most likely make the screen work for you if you provide that info.
Try the latest one with date appended... Touchscreen should work.
https://drive.google.com/file/d/1Clvwof18aLCF8NQqqjvSCkNEpQAkp6tO/view?usp=sharing
Edit: ^ Touch screen works on initial boot and after for my device. Added driver /vendor/lib/modules/aw8624.ko to /sbin/load_drivers.sh. Though I'm not sure if that is a touch related device and a google of aw8624.ko returns nadda.
Geofferey said:
The touch screen works for me when I fastboot it & it works when installed to ramdisk.
I think it worked for me when I used the format data option that requires typing yes. What GSI's are you using? I attempted to install one last night no data/wifi.
@Alexhdavila @Scholeggo
I will need more info. Does touchscreen work when booting via fastboot? Do you have a non US variant? What is output of command lsmod through adb shell in Android?
I can most likely make the screen work for you if you provide that info.
Try the latest one with date appended... Touchscreen should work.
https://drive.google.com/file/d/14JN1e8OlK_sj-AgpD5i97T-vrB5STOSJ/view?usp=sharing
Click to expand...
Click to collapse
Ok, I did send logs that should indicate that decrypting does not work.. I am using Phhusson's AOSP GSI for this test. My G7 Power is 1955-5 on Metro
If you're on a gsi, go into settings and look into lock screen/security and head down to encryption and credentials, and you will see my point.
This screenshot is in fact taken from my decrypted Moto E5 plus
Scholeggo said:
If you're on a gsi, go into settings and look into lock screen/security and head down to encryption and credentials, and you will see my point.
This screenshot is in fact taken from my decrypted Moto E5 plus
Click to expand...
Click to collapse
Did you update the device to the latest release? I forget where I read but after a certain security update TWRP is no longer able to decrypt user data on some devices. I am still on the OG software that came with device (security patch March 1, 2019), no updates. When I installed magisk on this device and disabled force ecrypt/dm-verity it would no longer boot either. I have yet to try disabling force-encrypt while leaving dm-verity. For me TWRP decrypts my data perfectly when installed to ramdisk but not fastbooting. If you flash a GSI rom in my experience you will have to wipe the data and phone will pretty much force this on you with stock recovery.
Also you didn't answer my question about touch screen. In your post you said to fastboot the test-v1.img then flash mine to ramdisk. Did the touchscreen on my build not work for you when fastbooting?
Edit: Actually I didn't ask lol.
Geofferey said:
Did you update the device to the latest release? I forget where I read but after a certain security update TWRP is no longer able to decrypt user data on some devices. I am still on the OG software that came with device (security patch March 1, 2019), no updates. When I installed magisk on this device and disabled force ecrypt/dm-verity it would no longer boot either. I have yet to try disabling force-encrypt while leaving dm-verity. For me TWRP decrypts my data perfectly when installed to ramdisk but not fastbooting. If you flash a GSI rom in my experience you will have to wipe the data and phone will pretty much force this on you with stock recovery.
Also you didn't answer my question about touch screen. In your post you said to fastboot the test-v1.img then flash mine to ramdisk. Did the touchscreen on my build not work for you when fastbooting?
Edit: Actually I didn't ask lol.
Click to expand...
Click to collapse
huh.. before flashing, i was last on the August build.. and yes, i flashed it to ramdisk and did not have an effect with decrypting the device.
no, touch screen does not work when fastbooting your build.
update: with your newer build (with datestamp), touch still doesn't work on fastboot
@Scholeggo
You tried 20190902-1422? Anything after Jun/July I am
pretty sure can not be decrypted via TWRP currently... that is normal operation. I have this same problem on my Pixel with an official TWRP. Right now my main concern is getting touch working for everyone. If you tried 20190902-1422 and touch doesn't work on fastboot I have some ideas to make it work all around. Do you have Hangouts or something so we can work faster to bring fully functional TWRP together? Since you have a device with the problem. Development via threads is slow.
Geofferey said:
@Scholeggo
You tried 20190902-1422? Anything after Jun/July I am
pretty sure can not be decrypted via TWRP currently... that is normal operation. I have this same problem on my Pixel with an official TWRP. Right now my main concern is getting touch working for everyone. If you tried 20190902-1422 and touch doesn't work on fastboot I have some ideas to make it work all around. Do you have Hangouts or something so we can work faster to bring fully functional TWRP together? Since you have a device with the problem. Development via threads is slow.
Click to expand...
Click to collapse
No Hangouts, but what about Telegram? +561-800-8299
---------- Post added at 12:22 AM ---------- Previous post was at 12:16 AM ----------
Geofferey said:
@Scholeggo
You tried 20190902-1422? Anything after Jun/July I am
pretty sure can not be decrypted via TWRP currently... that is normal operation. I have this same problem on my Pixel with an official TWRP.
Click to expand...
Click to collapse
ok, maybe not decrypt like that, but at least have TWRP not mess up internal storage when wiping system?
On the test-v1 I sent, it does that when wiping system alone, rebooted or not. With yours, it does that only when rebooting recovery; as long as you flash another system right after wiping, internal storage seems to be unaffected with your build.
If not decrypting the storage, it shouldn't mess up internal storage at all when wiping system
I think it's a mechanism of the device. When I flash any GSI on top of any userdata that was created by stock rom it messes up that data, most likely intentionally. That happens with 'fastboot flash system system.img' as well. Can you help me with the touch issues?
Try Me!
LATEST ATTMEPT !
Edit:
My last attempt before I say I don't know what I am doing. I've attempted to include all the kernel modules this recovery should need inside the image. There should be no need for it to load modules from /vendor/lib/modules. Hopefully this fixes the touch screen for most users when fastbooting and installing to ramdisk.
your newest build works touch functions properly
Thank you for the confirmation @OGandroid. Hopefully I can put touch to rest now and find other issues.
Geofferey said:
Thank you for the confirmation @OGandroid. Hopefully I can put touch to rest now and find other issues.
Click to expand...
Click to collapse
In my experience touch works fine booting into TWRP but once installed it's gone
I've tried flashing multiple times. Am I doing something wrong here?
Metro by T-Mobile Variant
Hey man thank you so much for your work! Just wanna triple verify tho! This will work on the metro variant? Also is it possible do you know to flash rims from the other g7 series phones?
yes I have the metropcs variant and it works fine on my device both ways booting or flashing it
---------- Post added at 10:26 PM ---------- Previous post was at 10:21 PM ----------
uHeash said:
In my experience touch works fine booting into TWRP but once installed it's gone
I've tried flashing multiple times. Am I doing something wrong here?
Metro by T-Mobile Variant
Click to expand...
Click to collapse
try the newest build touch works perfectly whether booting into twrp or flashing the ramdisk
OGandroid said:
yes I have the metropcs variant and it works fine on my device both ways booting or flashing it
---------- Post added at 10:26 PM ---------- Previous post was at 10:21 PM ----------
try the newest build touch works perfectly whether booting into twrp or flashing the ramdisk
Click to expand...
Click to collapse
Sick man this is awesome I've been waiting for this! Now for some rims and it'll be smooth sailing!