[RECOVERY][UNOFFICIAL] CWM Recovery for Nvidia Shield Tablet

Do you think this tablet needs recovery and custom ROMs?

  • Yes

    Votes: 19 90.5%
  • No

    Votes: 2 9.5%

  • Total voters
    21
  • Poll closed .
Search This thread

jce2005

Senior Member
Jul 13, 2009
174
27


Hi.
In the backup and restore menu in CWM recovery i can choose between backup to/ sdcard,
or backup to storage/sdcard1.
I always do backup to both, just in case.
Im using v.6.0.5.0.

Thanks
KnieveI

Well, I can't backup to storage/sdcard1 , comes up with an " error mounting /storage/sdcard1" and if I go to "mount" and try it manually, I get the same error.

EDIT :
I rebooted into recovery again and the backup started this time, but stopped by "Backing up system " Error while making a backup of /system!" so I rebooted again into recovery, mounted "System", but get the same error

Any ideas ?

Thx
 
Last edited:

ShrekOpher

Senior Member
May 14, 2013
2,149
1,389
Samsung Galaxy S22 Ultra
Well, I can't backup to storage/sdcard1 , comes up with an " error mounting /storage/sdcard1" and if I go to "mount" and try it manually, I get the same error.

EDIT :
I rebooted into recovery again and the backup started this time, but stopped by "Backing up system " Error while making a backup of /system!" so I rebooted again into recovery, mounted "System", but get the same error

Any ideas ?

Thx

Yeah you need to run the KitKat SD card fix. Then you should have no problem saving to your SD

https://play.google.com/store/apps/details?id=nextapp.sdfix

Sent from my SHIELD Tablet using XDA Free mobile app
 

jce2005

Senior Member
Jul 13, 2009
174
27
Yeah you need to run the KitKat SD card fix. Then you should have no problem saving to your SD

https://play.google.com/store/apps/details?id=nextapp.sdfix

Sent from my SHIELD Tablet using XDA Free mobile app

Thanks for the tip, but I already applied the sdcard fix ! even checked after flashing recovery and it's still active ! Have no trouble writing to my sdcard when system booted up, also all the other CWM "backup-parts" are on the sdcard, backup just cancels when it comes to backing up "system".

Any other ideas ??

Thanks again,

jce
 

ShrekOpher

Senior Member
May 14, 2013
2,149
1,389
Samsung Galaxy S22 Ultra
Thanks for the tip, but I already applied the sdcard fix ! even checked after flashing recovery and it's still active ! Have no trouble writing to my sdcard when system booted up, also all the other CWM "backup-parts" are on the sdcard, backup just cancels when it comes to backing up "system".

Any other ideas ??

Thanks again,

jce

What format is the card? My only other guess is that CWM doesn't like the format.

Sent from my SHIELD Tablet using XDA Free mobile app
 

jce2005

Senior Member
Jul 13, 2009
174
27
It's a SanDisk Ultra 128GB....and I think it's fat.... And CWM starts writing several files, before it stops at "system"....

This happens when I select " backup to storage/sdcard1, however, if I connect via USB, there is no clockworkmod folder on the sdcard.

I am now totally confused about the new Kitkat file structure and the fix for sdcards..... [emoji22]

Any other ideas?

Thx
 

KnieveI

Senior Member
Jul 27, 2012
203
33
Oslo
It's a SanDisk Ultra 128GB....and I think it's fat.... And CWM starts writing several files, before it stops at "system"....

This happens when I select " backup to storage/sdcard1, however, if I connect via USB, there is no clockworkmod folder on the sdcard.

I am now totally confused about the new Kitkat file structure and the fix for sdcards..... [emoji22]

Any other ideas?

Thx

Hi.
Did you try another/smaller sd card?
If thats the same i would try to download and install recovery again.
Thanks
KnieveI
 

jce2005

Senior Member
Jul 13, 2009
174
27
O.K., so I re-downloaded the recovery image, booted into recovery , inserted a different, smaller MicroSD ( 32GB ) and selected the backup option to sdcard1......

Same happen as with my 128GB card...... it does write several backup files, but aborts by /system with a "Failed" message.

I can do a backup to internal and then afterwards copy it to my sdcard, but it's an extra step... ohhh well...

EDIT : When doing an internal backup to sdcard, the ext. apps don't get backed up due to a " no .android_secure on sdcard1"....... I also cannot manually mount the sdcard1 ! Just seems like clockworkmod backup is not seeing or recognizing the sdcard1 !!!

PS: I will attach the log file from clockworkmod in the morning !

Thanks again.....

jce
 
Last edited:

kossiewossie

Senior Member
Sep 17, 2013
521
499
London
Just wanted to confirm to anyone with the LTE tablet, that this recovery works perfectly. I was able to flash it via the flashly and flash superSU, and then flash back to stock recovery without any problems.

So when lollipop hits, you can flash this recovery via adb by unlocking your bootloader and then flash SuperSU v2.22 to root your device.
 
Last edited:

garyd9

Inactive Recognized Developer
Sep 13, 2006
2,643
2,732
51
Pittsburgh, PA
So when lollipop hits, you can flash this recovery via adb by unlocking your bootloader and then flash SuperSU v2.22 to root your device.
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
 

kossiewossie

Senior Member
Sep 17, 2013
521
499
London
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

thanks for the insight! learn something new every day
 

Chaleman

Senior Member
Sep 3, 2009
177
32
Panama
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
 

Unjustified Dev

Recognized Developer
Oct 21, 2012
7,181
13,078
24
Memphis , TN
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
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.
 
  • Like
Reactions: Chaleman

jce2005

Senior Member
Jul 13, 2009
174
27
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
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?
 

eldarerathis

Senior Member
Jun 21, 2010
159
316
Current issues:
It appears to be rotated 180 degrees the wrong way. It's rotated that way due to the framebuffer. Don't worry it does not effect the performance in any way.

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:

Code:
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.
 

Attachments

  • recovery.zip
    9.5 MB · Views: 243

Top Liked Posts

  • There are no posts matching your filters.
  • 19
    I am not responsible for anything that happens while installing this recovery



    Installation:

    Download the attached recovery.img. You must have your bootloader unlocked before following this guide please refer HERE . You do not have to root your device to complete this installation.

    To permanently flash to recovery partition

    Code:
    fastboot flash recovery recovery.img

    To test the recovery image use

    Code:
    fastboot boot recovery.img

    To install SuperSu/Root your device use the flashable zip from Chainfire's thread. No direct links let's give him credits
    http://forum.xda-developers.com/showthread.php?t=1538053

    Current issues:
    It appears to be rotated 180 degrees the wrong way. It's rotated that way due to the framebuffer. Don't worry it does not effect the performance in any way.

    Source:

    device https://github.com/C457/android_device_nvidia_wx_na_wf

    kernel https://github.com/C457/android_kernel_nvidia_ardbeg

    If you want to build the recovery to fix the 180 degree rotated issue you will need one patch from google

    http://gerrit.vanir.co:8080/#/c/324/

    Thanks

    Huge thanks to @Keithn for testing all my bad images

    If you would like to help me purchase this tablet follow the link below
    http://www.gofundme.com/dbb08k
    8
    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
    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.

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

    or

    Code:
    fastboot flash recovery recovery.img
    8
    How can i flash the new 5.0.1 update using this recovery or do i have to go back to stock?
    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://forum.xda-developers.com/shi.../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
    4
    Uploaded new recovery.img it's using normal layout as nvidia kernel makes it go that direction I decided to just swap volume up and down keys.
    4
    Current issues:
    It appears to be rotated 180 degrees the wrong way. It's rotated that way due to the framebuffer. Don't worry it does not effect the performance in any way.

    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:

    Code:
    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.