[RECOVERY] [OFFICIAL] TWRP for Shield Tablet

[D-m-x]

@Steel01: Thank you for the updated TWRP, it seems actually faster
Altough my Adopted Storage isn't recognized, I am only seeing Internal, Micro SD and USB OTG (bith 0MB which is of course right). Not seeing anything in the Logs like failed Mount etc. like how it was in previous Versions. Am I missing something here?

 

[Steel01]

@Steel01: Thank you for the updated TWRP, it seems actually faster
Altough my Adopted Storage isn't recognized, I am only seeing Internal, Micro SD and USB OTG (bith 0MB which is of course right). Not seeing anything in the Logs like failed Mount etc. like how it was in previous Versions. Am I missing something here?

No, you're probably not missing anything. I reapplied an old fix for adopted storage that had been lost, but apparently that wasn't enough. Guess that's back on my list of things to check.

 

[D-m-x]

Ok thanks, just tell me if I can help in any way!

 

[nathan-96]

@Steel01 When flashing a rom with the latest TWRP, I get the error: "this zip is for 'shieldtablet' your device is ' ' "(Empty string). Flashing with older TWRP works fine.

 

[Steel01]

@Steel01 When flashing a rom with the latest TWRP, I get the error: "this zip is for 'shieldtablet' your device is ' ' "(Empty string). Flashing with older TWRP works fine.

Sounds like init didn't detect the device model correctly. Which model do you have? Also, can you paste the contents of /proc/cmdline?

 

[nathan-96]

Sounds like init didn't detect the device model correctly. Which model do you have? Also, can you paste the contents of /proc/cmdline?

I have an K1, it happend when I tried to flash an optimized stock rom.
I dont have an cmdline folder inside my proc folder :/
https://photos.app.goo.gl/fUzHsuvqcNOPlhKh1

 

[Steel01]

I have an K1, it happend when I tried to flash an optimized stock rom.
I dont have an cmdline folder inside my proc folder :/
https://photos.app.goo.gl/fUzHsuvqcNOPlhKh1

It's a file, not a folder. Will look similar to:

androidboot.hardware=tn8 buildvariant=userdebug androidboot.security=unlocked tegraid=40.1.1.0.0 [email protected] memtype=0 vpr_resize [email protected] otf_key=*snip* [email protected] section=256M commchip_id=0 usb_port_owner_info=0 lane_owner_info=0 emc_max_dvfs=0 androidboot.serialno=*snip* androidboot.commchip_id=0 androidboot.modem=none androidboot.touch_vendor_id=0 androidboot.touch_panel_id=9 androidboot.touch_feature=0 androidboot.orientation=0 androidboot.batterytype=1 fiq_debugger.script=reset [email protected] video=tegrafb no_console_suspend=1 console=ttyS0,115200n8 debug_uartport=lsport,3 sku_override=0 usbcore.old_scheme_first=1 [email protected] [email protected] core_edp_mv=1150 core_edp_ma=4000 board_info=0x06e1:0x00ea:0x04:0x00:0x00 tegraboot=sdmmc gpt gpt_sector=41983 modem_id=0 [email protected] android.kerneltype=normal androidboot.bootreason=pmc:power_on_reset,pmic:PwrOnLPK vmalloc=300m androidboot.bootloader=4.00.2016.04-8b2413b7

Might want to scrub the serial and otf_key like I did. But the main part I'm looking for is the second field in the board_info parameter. 0x00ea is the wifi only models.

 

[nathan-96]

It's a file, not a folder. Will look similar to:

androidboot.hardware=tn8 buildvariant=userdebug androidboot.security=unlocked tegraid=40.1.1.0.0 [email protected] memtype=0 vpr_resize [email protected] otf_key=*snip* [email protected] section=256M commchip_id=0 usb_port_owner_info=0 lane_owner_info=0 emc_max_dvfs=0 androidboot.serialno=*snip* androidboot.commchip_id=0 androidboot.modem=none androidboot.touch_vendor_id=0 androidboot.touch_panel_id=9 androidboot.touch_feature=0 androidboot.orientation=0 androidboot.batterytype=1 fiq_debugger.script=reset [email protected] video=tegrafb no_console_suspend=1 console=ttyS0,115200n8 debug_uartport=lsport,3 sku_override=0 usbcore.old_scheme_first=1 [email protected] [email protected] core_edp_mv=1150 core_edp_ma=4000 board_info=0x06e1:0x00ea:0x04:0x00:0x00 tegraboot=sdmmc gpt gpt_sector=41983 modem_id=0 [email protected] android.kerneltype=normal androidboot.bootreason=pmc:power_on_reset,pmic:PwrOnLPK vmalloc=300m androidboot.bootloader=4.00.2016.04-8b2413b7

Might want to scrub the serial and otf_key like I did. But the main part I'm looking for is the second field in the board_info parameter. 0x00ea is the wifi only models.

androidboot.hardware=tn8 buildvariant=eng androidboot.security=unlocked tegraid=40.1.1.0.0 [email protected] memtype=0 vpr_resize [email protected] otf_key=*scrubbed* [email protected] section=256M commchip_id=0 usb_port_owner_info=0 lane_owner_info=0 emc_max_dvfs=0 androidboot.serialno=*scrubbed* androidboot.commchip_id=0 androidboot.modem=none androidboot.touch_vendor_id=0 androidboot.touch_panel_id=9 androidboot.touch_feature=0 androidboot.orientation=0 androidboot.batterytype=1 fiq_debugger.script=reset [email protected] video=tegrafb no_console_suspend=1 console=ttyS0,115200n8 debug_uartport=lsport,3 sku_override=0 usbcore.old_scheme_first=1 [email protected] [email protected] core_edp_mv=1150 core_edp_ma=4000 board_info=0x06e1:0x00ea:0x04:0x00:0x00 tegraboot=sdmmc gpt gpt_sector=41983 modem_id=0 [email protected] android.kerneltype=recovery androidboot.bootreason=pmc:software_reset,pmic:NoReason vmalloc=300m androidboot.bootloader=4.00.2016.04-8b2413b7

Thanks, here it is

 

[Steel01]

androidboot.hardware=tn8 buildvariant=eng androidboot.security=unlocked tegraid=40.1.1.0.0 [email protected] memtype=0 vpr_resize [email protected] otf_key=*scrubbed* [email protected] section=256M commchip_id=0 usb_port_owner_info=0 lane_owner_info=0 emc_max_dvfs=0 androidboot.serialno=*scrubbed* androidboot.commchip_id=0 androidboot.modem=none androidboot.touch_vendor_id=0 androidboot.touch_panel_id=9 androidboot.touch_feature=0 androidboot.orientation=0 androidboot.batterytype=1 fiq_debugger.script=reset [email protected] video=tegrafb no_console_suspend=1 console=ttyS0,115200n8 debug_uartport=lsport,3 sku_override=0 usbcore.old_scheme_first=1 [email protected] [email protected] core_edp_mv=1150 core_edp_ma=4000 board_info=0x06e1:0x00ea:0x04:0x00:0x00 tegraboot=sdmmc gpt gpt_sector=41983 modem_id=0 [email protected] android.kerneltype=recovery androidboot.bootreason=pmc:software_reset,pmic:NoReason vmalloc=300m androidboot.bootloader=4.00.2016.04-8b2413b7

Thanks, here it is

That looks fine. Weird... Was is the output of the following two commands:
getprop ro.hardware
getprop ro.product.name

 

[nathan-96]

That looks fine. Weird... Was is the output of the following two commands:
getprop ro.hardware
getprop ro.product.name

tn8 & wx_na_wf


Is it possible that it happens because I formatted every partition in twrp?

 

[Steel01]

tn8 & wx_na_wf


Is it possible that it happens because I formatted every partition in twrp?

Eh? If those are set, then why is it failing?? How about
getprop ro.product.device
getprop ro.product.name

Also, what are you trying to flash? And no, wiping won't break things like this.

 

[nathan-96]

Eh? If those are set, then why is it failing?? How about
getprop ro.product.device
getprop ro.product.name

Also, what are you trying to flash? And no, wiping won't break things like this.

ro.product.name & shieldtablet
I tried flashing last official lineage

---------- Post added at 01:41 PM ---------- Previous post was at 01:40 PM ----------

Eh? If those are set, then why is it failing?? How about
getprop ro.product.device
getprop ro.product.name

Also, what are you trying to flash? And no, wiping won't break things like this.

shieldtablet & wx_na_wf

 

[s2berto]

Yet Another Bootloader Unknown Issue (aka, YABUI)

I am stuck here, folks. Samsung devices are more my comfort zone, so figure I have hit something unique on the Shield Tablet. I am trying to install LOS 14.1 on my wife's ST K1 via TWRP 3.1.1-0 and I get the 'supports bootloader 4.00.x ... bootloader unknown ... error 7' issue. I have flashed boot.img from the LOS zip and a stock boot.img from nvidia, but still come up with differen bootloader versions.

I have ADB, fastboot & TWRP at my disposal, but no bootable OS. Any suggestions on installing the real 4.00.x bootloader?

TIA, s2

 

[Steel01]

@s2berto Bootloader is not what's in boot.img. You want the file linked in the opening post to my Lineage thread, the one labelled firmware. Flash that in twrp and reboot once. You'll have to let it try to boot android normally for the update to actually apply. At that point, you can go back to twrp and flash lineage as expected. The check is there to prevent issue with firmware/bootloader incompatibilities.

 

[Steel01]

@s2berto Bootloader is not what's in boot.img. You want the file linked in the opening post to my Lineage thread, the one labelled firmware. Flash that in twrp and reboot once. You'll have to let it try to boot android normally for the update to actually apply. At that point, you can go back to twrp and flash lineage as expected. The check is there to prevent issue with firmware/bootloader incompatibilities.

 

[s2berto]

My fault

@s2berto Bootloader is not what's in boot.img. You want the file linked in the opening post to my Lineage thread, the one labelled firmware. Flash that in twrp and reboot once. You'll have to let it try to boot android normally for the update to actually apply. At that point, you can go back to twrp and flash lineage as expected. The check is there to prevent issue with firmware/bootloader incompatibilities.

Thank you for your quick reply, Steel01. I think I had two problems: 1 ) I was thinking boot.img covered the bootloader, not the boot partition. 2 ) I did not fully read the MOP. My familiarity with Galaxy stuff, LINUX & UNIX probably made me go 'Yep, yep, got it'. Very bad procedure for an IT guy...

I will start afresh in the morning and heed your instructions.

 

[Steel01]

Thank you for your quick reply, Steel01. I think I had two problems: 1 ) I was thinking boot.img covered the bootloader, not the boot partition. 2 ) I did not fully read the MOP. My familiarity with Galaxy stuff, LINUX & UNIX probably made me go 'Yep, yep, got it'. Very bad procedure for an IT guy...

I will start afresh in the morning and heed your instructions.

So, Nvidia does handle things differently. It's not hard to assume it'll work like all the Qcom stuff out there, but it's not true. QCom stuff (which covers the US Galaxy variants) has multiple firmware partitions you directly flash to update stuff. Nvidia instead using a staging partition. You flash a blob to the staging partition and during boot, the system checks to see if the blob is valid and if so, applies it to all relevant partitions and reboots. So, it is an extra step, but it does allow for better sanity checks and prevent simple bricks.

 

[skorpiodav]

I tried the latest version twrp-3.2.3-0-shieldtablet.img but the adopted storage is not detected, is this right? I'm looking for a versione higher than 3.1.0.0 to use with TWRP backup tool to backup directly to PC. I found a modified 3.1.0.2 version that works but I would like to use an official and updated version.

 

[Son-j]

I tried using TWRP 3.2.3.0 bit it seems that it can't write to SD card so I cant put my back up there. Any suggestion?

 

[Adai0]

I tried using TWRP 3.2.3.0 bit it seems that it can't write to SD card so I cant put my back up there. Any suggestion?

I have this problem too. I formatted the sd card as internal storage which does encrypt it. TWRP sees the sd card. However it looks like it cannot encrypt the card.
@Steel01: Is there any chance you can have a look into this soon?