yashsingh1/xdaforums huggingface dataset:
[Shield Tablet Android Development] garyd9:
Please be careful with statements like that. We don't know if nvidia has changed the bootloader or not. It's quite common for newer bootloaders to NOT properly boot kernels based on older firmware. (And with L, this TWRP will be based on an older firmware.)

For devices that support fastboot properly, including the "fastboot boot" usage, it's almost always better to verify via "fastboot boot" than to blindly flash a kernel or recovery.

As well, just flashing superSU will not be enough to "root" an L device. With L, the SELinux restrictions have to be loosened as well (which, so far on nexus devices, is being done with a repacked kernel image.)

Gary
[Shield Tablet Android Development] kossiewossie:
thanks for the insight! learn something new every day
[Shield Tablet Android Development] Sh0X31:
cwm creat always a clockwordmod file in /sdcard , sdcard/0/ & sdcard/0/0/. If a delete and fresh, they back again
[Shield Tablet Android Development] Chaleman:
Hi guys... I have CWM installed on my LTE version of the Shield Tablet. I have one question and one note:

- The only way I can figure out to get into CWN is to boot into fastboot mode and the go into recovery with the command "fastboot boot recovery.img". I haven't found a way to directly boot into CWM. Is there a way or am I doing something wrong....

- The note is that today I tried to do a backup into my external 128gb SD Card (Fat32) and got a message :"Error while making a backup image of /system!". So I then proceeded to do the backup in my internal SD Card and it seems to be ok... any ideas? It worked great when I had 4.4.2 installed on the tablet...

Thanks!

Carlos
[Shield Tablet Android Development] Unjustified Dev:
Cwm has an issue with the external sdcard I was unable to resolve it at the moment. If you want the image permanently installed use fastboot flash recovery recovery.img and you will be able to reboot to recovery via the volume and power button method or via adb reboot recovery.
[Shield Tablet Android Development] Chaleman:
Thanks. It worked like a charm...

Carlos
[Shield Tablet Android Development] twistedumbrella:
Was there anything special to the kernel? Link is a 404.

Edit: nevermind, found someone that forked it via Google. Thanks.
[Shield Tablet Android Development] jce2005:
I have exactly the same issue with CWM and my 128GB card.... Can't do a backup to sdcard1... Fails at the system backup....

If I do a cwm backup to "sdcard", backup will be created, however, No apps are backed up... Comes up with some sort of an error like : no android . secure found......

Will there be a solution to this problem eventually?
[Shield Tablet Android Development] eldarerathis:
Couldn't decide if it would be worth starting an entirely separate thread, but I fixed the framebuffer so that it's oriented correctly. I thought about creating a merge request, but I was using NVIDIA's Tegra device tree, which is...really different.

In any case, here's my device tree. The bulk of the fix is in common/recovery/graphics.c, in the gr_flip() method. In the default graphics.c file, this method basically just does a memcpy() from memory to the framebuffer. The modified version is this:

void gr_flip(void)
{
GGLContext *gl = gr_context;

/* swap front and back buffers */
if (double_buffering)
gr_active_fb = (gr_active_fb + 1) & 1;

int buffer = 0;
int fbsize = fi.line_length * vi.yres;

// Copy the in-memory buffer into the buffer we're about to make
// active, but reverse the order of the pixels.
for (buffer = 0; buffer < fbsize; buffer += 4)
{
const char *src = (char *)gr_mem_surface.data;
char *dst = (char *)gr_framebuffer[gr_active_fb].data;

// Since we're reversing the buffer data, we need to flip the order
// of the subpixel values, too. Otherwise they'll be backwards.
dst[(fbsize-(buffer+4))] = src[buffer-PIXEL_OFFSET];
dst[(fbsize-(buffer+3))] = src[buffer+1-PIXEL_OFFSET];
dst[(fbsize-(buffer+2))] = src[buffer+2-PIXEL_OFFSET];
dst[(fbsize-(buffer+1))] = src[buffer+3-PIXEL_OFFSET];
}

/* inform the display driver */
set_active_framebuffer(gr_active_fb);
}

There are a few other smallish adjustments that I had to make in order to get everything lined up correctly. That offset is because without it I was getting some weird padding on the right side of the screen, for example. Anyway, I've got it running on my LTE Shield and haven't had any issues. Did a backup, performed a partial restore, flashed SuperSu, etc.

If anyone wants to try the recovery, I've attached a zipped copy of the image. This is NOT a zip that you can flash from your current recovery, I just zipped it because the raw image exceeds XDA's file upload limit apparently. Unzip the image, then flash it or boot it via fastboot or Flashify or whatnot, just like any other recovery image. MD5 for the image (not the zip) should be 7959f08d9266b60da46f44ab4333c92a. I make no promises, but as I said, it's working fine on my Shield.
[Shield Tablet Android Development] Unjustified Dev:
Nice! I will implement this when nvidia finally releases the lollipop tree. They are taking an extended amount of time I may go ahead and just bring up the device without them.
[Shield Tablet Android Development] eldarerathis:
Yeah, I was waiting for their Lollipop source to land, too, but got impatient. Since I only wanted to build the recovery I decided that using the KK device tree/kernel would suffice for now, and would be quicker than putting together a device tree from scratch.
[Shield Tablet Android Development] Unjustified Dev:
Well there are trees available already

https://github.com/TeamRegular/android_device_nvidia_wx_na_wf

https://github.com/TeamRegular/android_device_nvidia_shieldtablet

https://github.com/TeamRegular/android_kernel_nvidia_shieldtablet

https://github.com/TeamRegular/proprietary_vendor_nvidia

Haven't you seen the ROMs already?

I plan on redoing those in a week or so hopefully lollipop source is out by then. Only problem roms have is touch screen issues I have not finished the update to latest code and gps does not work that issues persist on their aosp builds as well. I don't have the device but it seems you have the device and skills. :good: make some people happy
[Shield Tablet Android Development] eldarerathis:
I thought it might be easier to debug the framebuffer weirdness if I was starting with the vanilla tree as a base, to make sure there was nothing going on in the other trees that was causing it. In reality, I don't think it would have mattered because the issue was lower than that, but once I started I didn't feel like moving everything into another tree.

I was also considering trying an AOSP Lollipop build, but I base my builds on AOSP, not CM, so I wanted to try to stick closer to NVIDIA's "AOSP" tree. If I have some time this weekend I might try making the same framebuffer changes in a fork of the TeamRegular tree, though, and then submit a proper merge request, just to make things easier.

I had really awful battery life when I did an AOSP KK build, though, so I'm not sure if I'll spend much time on Lollipop. Plus I can't decide if I want to keep the NVIDIA apps or not.
[Shield Tablet Android Development] twistedumbrella:
In case you were wondering, it also works fine on the WiFi only version.
[Shield Tablet Android Development] twistedumbrella:
Honestly, there haven't been any changes to the part of the kernel that is relevant to a recovery since Jellybean as far as the Nvidia source goes. Rebasing for the newer kernel for a recovery only would be a waste of time.
[Shield Tablet Android Development] Unjustified Dev:
I actually used the aosp tree I just merged it all into one and took some stuff like sensors etc and use them as prebuilts. Other than that my tree is identical to Nvidia with cm support . You should be able to do a pure aosp lp build with minor patches from cm if any needed at all and of course set up the tree to use aosp configuration.

I only needed two which I pushed to cm from nvidia. I really didn't want to change the wifi configurations since the tree is close to aosp as possible I didn't want many changes.

http://review.cyanogenmod.org/71802

http://review.cyanogenmod.org/71804
[Shield Tablet Android Development] jce2005:
Hi eldarerathis,

flashed your "recovery.img" with Flashify and here are the results :

1. Flashed without any troubles on Shield Tablet 4G/LTE ( Rooted with Lollipop )

2. Orientation is correct

3. Backup to sdcard ( internal ) partially works......

BACKED UP : boot image / recovery image / system / data / cache, Generated MD5 checksum

NOT BACKED UP : applications ( ERROR : No .android_secure found. Skipping backup of applications on external storage)

4. Backup to /storage/sdcard1 failed ( ERROR : E: Unable to state backup path )

Any ideas or possibilities to get this fixed ?

Thanks, Great job from you and Unjustified Dev

JCE
[Shield Tablet Android Development] eldarerathis:
Do you actually have apps installed on your SD card? The message isn't saying that it can't back up your apps, it's saying that it doesn't see any apps installed on your SD card. Anything on internal memory is backed up with the /data partition.

Dunno about the second message. Haven't seen it myself.
[Shield Tablet Android Development] jce2005:
Hi,

Thanks for responding... Well, I moved several apps to the sdcard1.... I am a bit confused how Kitkat and lollipop handling a Microsd card... But for sure, the cwm backup to sdcard1 doesn't work in Kitkat or in lollipop....
[Shield Tablet Android Development] Keithn:
The recovery issue isn't the same as while booted. Starting with KitKat apps are only allowed to access specific folders on the SD. You can disable that easily with the sdfix app. Recovery was having issues with mounting the SD properly if I remember correctly.

Sent from my One M8
[Shield Tablet Android Development] jce2005:
Hi Keithn,

thanks for the reply. Well, I do know of and use the "NextApp SDFix" app. Did so in KitKat as well as in Lollipop ! However, the CWM Recovery works basically before the OS is booted, so it seems to me, that somewhere in CWM the path to sdcard is not properly working ( or as you stated it can't mount the sdcard )........ I am a pretty handy guy when it comes to PC's but not technically inclinded on Android, but it seems ( and I say seems !!! ) to me, that would be a easy fix since it must be the CWM and not the Android OS what causes the problem.

But heyyyyyy, maybe it's more difficult than my understanding. I never had any trouble by all my phones using CWM to mount or access the external sdcard for backup purposes.... So I am uncertain and don't understand why this ( to me ) small issue can't be addressed and fixed.

Unjustified Dev could probably answer why this can't b e fixed easily, otherwise I am sure he would have fixed it by now already.

Maybe someone could give me step-by-step directions on how I could do and ADB ( Nandroid ???? ) Backup on My Shield LTE Tablet until the CWM backup to sdcard works. I am sooooooo not familiar with the ADB commands and how to do a full backup/restore with ADB !!

Thanks in advance,

JCE
[Shield Tablet Android Development] twistedumbrella:
It's a square peg round hole mess with recovery wanting sdcard1 to fit a set design that no system seems to follow anymore.

Btw [MENTION=2676559]eldarerathis[/MENTION] and [MENTION=4911249]Unjustified Dev[/MENTION], I believe you were waiting on http://nv-tegra.nvidia.com/gitweb/?...a=blob_plain;f=README;hb=rel-st8-l-r1-partner which hasn't been updated on the official Nvidia development site yet but is available if you happen to dig through their source for whatever reason ;)
[Shield Tablet Android Development] Keithn:
Tried digging before and didn'y see that, did it pop up in the last few days?

I'll try a quick build of the source and see if the kernel will actually support GPS or resolve any other issues this time. I really doubt it suddenly will work, but it's worth a try.

Sent from my One M8

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

I was just playing around with mine and backing up to sd1 seems to work on mine. What are you using for an sd card? model, size, format etc? I was playing with formats on mine so I can't remember if it's FAT32 or EXFAT, I will check. I can Backup and restore on sdcard1 just fine.

Mine is a 32GB Sandisk Extreme Plus formatted in FAT32. I
[Shield Tablet Android Development] twistedumbrella:
~ 9 days ago. Not sure what good GPS will do in CWM but it's updated to almost the same day as the update released, if not newer.
[Shield Tablet Android Development] Keithn:
DIdn't mean for cwm. I guess it's not entirely relevant to cwm development, but there were somethings not functioning properly in Nvidia's source code and gps was one of the big things noticed so I figured I'd give it a try.
[Shield Tablet Android Development] twistedumbrella:
I always forget how serious xda is...
[Shield Tablet Android Development] Keithn:
Yeah I guess I should've caught that but you know how it goes :silly:
[Shield Tablet Android Development] jce2005:
[QUOTE

I was just playing around with mine and backing up to sd1 seems to work on mine. What are you using for an sd card? model, size, format etc? I was playing with formats on mine so I can't remember if it's FAT32 or EXFAT, I will check. I can Backup and restore on sdcard1 just fine.

Mine is a 32GB Sandisk Extreme Plus formatted in FAT32. I[/QUOTE]

Mine is a Sandisk Ultra 128GB FAT32

I cannot mount sdcard1.... I think I tried everything.... Any other ideas ?
[Shield Tablet Android Development] twistedumbrella:
Some of the extra high capacity cards have issues with Android even if the device claims to be compatible.

If formatting the card in recovery doesn't work and it works on other devices, little can be done. If it's not mounting on any device, SanDisk will replace it if you contact them.
[Shield Tablet Android Development] eldarerathis:
I did some work on getting my CWM changes working in the TeamRegular device tree, and it boots and is oriented fine, but the font rendering looks terrible (albeit readable). It's all blocky and has this odd striping, with vertical lines of transparent (?) pixels in every letter. That's my guess at least, because the background is bleeding through.

I'm not sure what's causing it yet. Building with the tree I put together doesn't have this problem, so there's seemingly something that's a little different. Not sure if anyone else might have an idea off the top of their head.
[Shield Tablet Android Development] Unjustified Dev:
Is it the custom font?
[Shield Tablet Android Development] jemail:
Is this recovery compatible with UK LTE version?

jemail
[Shield Tablet Android Development] leviatus:
I had issues with not being able to mount, write to sdcard1, tried formatting to NTFS, ExFat to no avail.

(Tested this on 2 64GB class 10 Samsung card)

Formatted to Fat32 using guiformat & it backups with the

Android Secure error so it doesn't work fully.
[Shield Tablet Android Development] bill0405:
I've been having the same issue, and also when I attempt to make a backup to SD card, It is only reading my card as 905MB (out of 64 gig), and gives me an error within seconds that says it cant make a backup. Anyone else have this issue or know how to remedy it?
[Shield Tablet Android Development] WarRaven:
The same, 905mb showing on my 64gb NTFS card.

When I back up internally or try to, it does not save anywhere that disk into can find, so no back up at all.

I'm stumped.

WR

Edit,

Its apparently backing up on internal, just not sure where yet.

Would be nicer on ext though something better then nothing at all.
[Shield Tablet Android Development] jce2005:
The backup folder is in mnt/shell/emulated/clockworkmod/backup
[Shield Tablet Android Development] Gs0230:
How can i flash the new 5.0.1 update using this recovery or do i have to go back to stock?
[Shield Tablet Android Development] ailima:
I think this version of cwm sometimes mistakes sdcard1 and sdcard0
[Shield Tablet Android Development] jim380:
You don't have to go back to stock. All you need to do is:

1. Flash the full update package in recovery, as in the 700+MB one for that very device (Wifi, or LTE), not the 80ish MB one. Find them here:

wifi: http://ota.nvidia.com/ota/rom/productionBL-droid-signed-wx_na_wf-full_ota-29082_493.9700.zip

US-LTE: http://ota.nvidia.com/ota/rom/productionBL-droid-signed-wx_na_do-full_ota-29082_493.9700.zip

2. Once this is flashed, reboot the device. You are probably gonna lose recovery at this point. You can find CWM here (

http://xdaforums.com/shield-tablet/development/recovery-cwm-recovery-nvidia-shield-t2848064

), and supersu here (

http://download.chainfire.eu/641/SuperSU/UPDATE-SuperSU-v2.40.zip

put it somewhere on your tablet). Then Flash them following this procedure:

-adb reboot bootloader

-fastboot flash recovery recovery.img

-don't do "fastboot reboot" yet. I found CWM won't stick on the tablet for some reason. What you

need to do instead is to go to recovery mode by directly choosing the "recovery mode" option on

the tablet while it's still in bootloader mode.

-Once you're in recovery mode, flash supersu zip file

- Reboot, and profit
[Shield Tablet Android Development] An Droid:
Even easier - after installing the correct full update .zip for your device through CWM, DON'T reboot immediately and instead also install the latest stable SuperSU .zip (v.2.40 as of this post) through CWM as a second step to gain root.

CWM survived the update on my device and I had root on the initial boot (this boot will take longer than usual, and a second reboot afterward helps stabilize the unit).
[Shield Tablet Android Development] xabierd:
I dont know if t was the OTA to 5.0.1 or the factory reset with CWM but my 32gb shield turned into 16gb. Is there any way to solve it and format it back tl 32gb??
[Shield Tablet Android Development] gomax:
Success!

Worked a treat.

Thanks for the info.
[Shield Tablet Android Development] jce2005:
Anyone has a working link for the OTA for the LTE ( US ) ???
[Shield Tablet Android Development] ailima:
Seriously? It's only 4 posts ago that jim380 shared that link! :)
[Shield Tablet Android Development] slimfady:
Anyone knows where I can find the EU ota files? LTE version in particular
[Shield Tablet Android Development] ailima:
I would assume that another factory reset and this time install the lte version should fix it. Maybe. :)
[Shield Tablet Android Development] jce2005:
Hi guys,

if I try in CWM to flash the " productionBL-droid-signed-wx_na_do-full_ota-29082_493.9700.zip " file it aborts with this error : " This Package is for "shieldtablet" devices; this is a "ardbeg"

Anyone knows what the problem might be ?

Thx,

jce
[Shield Tablet Android Development] ailima:
Huh. Did you flash anything else (another rom) previously? Maybe try backing up and explicitly wiping the system partition before installing again?
[Shield Tablet Android Development] jce2005:
Nope, did not install anything else via CWM, besides the initial rooting ( recovery, SuperSU ) !

I am a bit worried about the "wiping" since I only can use CWM to backup to internal..........CWM Backup does not work to backup to my 128GB Sandisk Ultra SdCard for some reason..... ( no one knows why ! )

Do you know the adb command for installing a .zip via adb ? Might try this way.....

Thx
[Shield Tablet Android Development] ailima:
You can pull the backup off your tablet so you don't have to worry about it "adb pull <dirname>"

What your looking for is "adb sideload <zipfile>"

---------- Post added at 06:57 PM ---------- Previous post was at 06:55 PM ----------

Also, can we move this to the q/a thread?
[Shield Tablet Android Development] jce2005:
Thx, will try it this way....

Sure, just post the link where it was moved too.. ;)

---------- Post added at 08:27 PM ---------- Previous post was at 07:58 PM ----------

Did not work via adb sideload either.... still the same error....

Made a backup, which is located in : mnt/shell/emulated/clockworkmod/backup

Could not use adb pull <dirname> ( whatever I put in dirname, it says "

object does not exist" !!!

Grrrrrrrrrrrrr LOL
[Shield Tablet Android Development] stanglx:
Is this cwm recovery compatible with lte version?

Does the first post have the most stable version for the lte version?
[Shield Tablet Android Development] ailima:
yes, it's compatible ... in most ways. I think that people are having a hard time making it access the sdcard, regardless of version.
[Shield Tablet Android Development] tecnoworld:
Hello, I'm with a locked bl and rooted with 5.0.0.

May I follow the procedure reported here, w/o loosing data?

Thx.
[Shield Tablet Android Development] ailima:
You have to unlock to install a new recovery. Unlocking the bootloader will erase your data. If you are rooted already, Just back up with tb or similar.
[Shield Tablet Android Development] tecnoworld:
I see. So there is currently no way to upgrade with locked bl w/o loosing data? I'd like to avoid to reinstall everything.
[Shield Tablet Android Development] jce2005:
If you are rooted and use the paid version of Titanium Backup, you just run the batch restore.... you don't have to install everything this way.... !!!
[Shield Tablet Android Development] BlackDave:
I'm guessing from the previous posts I'm reading that this recovery is having trouble seeing bigger size micro sd cards. I have a 64gb and it fails to see it when I need to flash something. I'm seeing other people having issues with their card not being seen as the correct size when backing up. My memory card can be seen just fine on TWRP but for some reason that recovery fails to properly install the 2.1 update so I'll stick with this one and either use the internal memory or my spare 16gb one as it seems to work.
[Shield Tablet Android Development] romracer:
I had this problem too. I'm using the recovery from a few pages back that fixes the upside-down issue, so maybe you're using the same one? The "ro.product.device" in that one says "ardbeg" instead of shieldtablet. I recompiled it to use shieldtablet and then was able to flash the full OTA fine through CWM.

Here's the updated recovery. You'll need to unzip it and flash through fastboot or adb.

adb shell
su
dd if=/data/media/0/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS

or

fastboot flash recovery recovery.img
[Shield Tablet Android Development] jce2005:
Hi,

thanks for responding. Yes, I also use the recovery that fixed the up-side-down issue..,..

Cool, got the fixed recovery.zip from you and try to install on Monday ( day off ). Also got the instructions.

Thanks a bunch.

Ohhhhh, BTW...... do you know where the sound files for notifications are located on the Shield tablet ? I looked in /System/Media/Audio, but cannot find the one file I look for ( Cairo.ogg ) ..... Is there another place where this and/or other sound files are located >?

Thanks again

jce
[Shield Tablet Android Development] stanglx:
I flashed my LTE US (unlocked) with the reocovery.img from the 1st page and when I reboot into recovery i get the android guy that looks like he is dying... everything seemed to flash fine (no errors)..

Any suggestions?
[Shield Tablet Android Development] ErichMoraga:
Yes, use romracer's .img from the previous page. I just flashed it and it worked great.
[Shield Tablet Android Development] stanglx:
Unfortunately its not working with the LTE !!

Windows will not recognize the device at all in CWM Recovery...

CWM starts and everything looks good until I try to sideload. The USB device in the device manager is unloaded. The only way I can get ADB to work is when booted into the android OS.

Any ideas?
[Shield Tablet Android Development] ErichMoraga:
I have the 32GB NA LTE tablet too, and it worked fine, but I flashed recovery via fastboot in bootloader mode from my PC...

fastboot flash recovery recovery.img
[Shield Tablet Android Development] stanglx:
Yea that works... I suspect this has nothing to do with the recovery image.

I just tried PhilZ recovery and same issue... It looks like windows does not recognize ADB in the recovery??? Fastboot works fine but that is a different driver I can see in the device manger.. the ADB interface driver does not load in CWM or in Philz.

Any ideas?