[Resolved] HANNSpree HSG1279 root and recovery!!! [Updated 01/28/14]

Search This thread

Omegadrive

Senior Member
Sep 26, 2012
333
77
Vega Baja
omegadrivers.net
Updated OP with solution, many thanks to @fipsy for the final solution, here is his post for those that need help rooting this device: (UPDATE: Root for 4.2.2 at the end of the post)
Last week I investigated a lot of days to solve the problem: (I'm sorry for not being able to post working links in this forum because I didn't write enough here. :( So you have to reconstruct my links yourself into your browser)

As omegadrive supposed you just have to exchange the su binary, give the right permissions and the Superuser App from the Playstore will immediately work.

The necessary USB drivers for the device are found here: http://yadi.sk/d/54lX5c2O386XU

They only work with Windows 7!

After starting the "adb shell" you can gain root permissions on the device by typing "su". The su distributed with the device in /system/xbin is not compatible with common superuser apks. So it has to be exchanged with the version 3.1.1 binary: http://downloads.androidsu.com/superuser/su-bin-3.1.1-arm-signed.zip

Copy it to your /sdcard. Then continue with adb shell:

Code:
$ su
# cd /system/xbin

Mount the system partition read/write:

Code:
# mount -o remount,rw -t rfs /dev/block/st19 /system

Rename the original binary for later use (if something fails):

Code:
# mv su su-orig

Copy the binary to the xbin folder:

Code:
# busybox cp /sdcard/su ./su

Change the permissions:

Code:
# chmod 6755 su

Mount the system partition read-only and exit:

Code:
# mount -o remount,ro -t rfs /dev/block/st19 /system
# exit
$ exit

Now install the Superuser App from the Playstore - and have fun! Do *NOT* Update the su binary from within the Superuser App or it will be overwritten with a non-working version!

Cheers, Volker

CUSTOM RECOVERY FINALLY POSSIBLE!!! Again, many thanks to @fipsy, here is his post:
I finally made it! :laugh: Here is a working CWM Recovery for the HANNspree HANNSpad SN1AT71 (HSG1279).

I didn't fully test it but the backup function works. Also mounting and unmounting partitions works as well as the adb shell which is very important if the device is bricked and doesn't boot anymore.
Before connecting to the device via adb shell it is necessary to mount the /system partition (menu "mounts and storage") because otherwise /system/bin/sh cannot be found by adb shell.

The CWM recovery by default stores it's backups on the external SD-Card. The benefit is that the backup can easily be plugged out and stored apart from the device. But the recovery is also able to restore backups from the internal sdcard. Those backups can be made online on a running android system by using apps like "Online Nandroid Backup" and "Nandroid Manager". The benefit is that it's not necessary to reboot the device before backing up and you can keep on working.

There is one problem when creating backups in CWM Recovery: The date/time of the backup is always set to 1st of January 1970 due to a missing backup battery in this device. Look here: http://tau.shadowchild.nl/attn1/?p=341. So if you want to make backups with accurate timestamps you would have to set the actual time of the device using adb shell: Start adb shell and enter:

Code:
/system/xbin/busybox date -s "YYYY-MM-DD hh:mm:ss"

before making the backup.

To cut a long story short: Download the CWM-Recovery here: http://yadi.sk/d/ArprqzfFFWvy4 and flash it to your (rooted) device. How to do this:

  • Copy the file cwm-recovery.ima to your internal sdcard.
  • Either connect via adb shell and enter su
  • or run a Terminal Emulator and enter su
  • then enter
    Code:
    cat /sdcard/cwm-recovery.ima > /dev/block/acta
and you're done! Have fun! Comments are appreciated!
Perhaps someone likes to create an update.zip from it?

Edit (01/28/2014): There is a new version 6.0.3.3. Look here: http://forum.xda-developers.com/showpost.php?p=49835135&postcount=283
Edit (05/04/2014): There is a new version 6.0.3.3.a. Look here: http://forum.xda-developers.com/showpost.php?p=52416205&postcount=492

ROOT for new OTA 4.2.2 update:
Good news for germany: The rollout began tonight! I just got the update to Android 4.2.2! :laugh:

Some people asked for the upgrade file to manually update from the recovery. Here it is: http://yadi.sk/d/igsBGsAjFpLsL
Edit (01/13/2014): Seems this update only works on devices with special G-Sensor hardware (KIONIX 3-axis Accelerometer).

@ig6677: There you will also find the META-INF you wanted.

For your information: After my update to Android 4.2.2 root has gone on my device! I expected this. All Apps that need root don't work anymore. I don't know what you did that root was still there after the update...

Furthermore in /system/xbin there is no su file anymore. Also my CWM Recovery has gone and was replaced by the Stock HANNspree recovery!

But whats new: If you connect to the device via adb shell you immediately have superuser rights! No su is needed for this anymore. So it's possible to restore the CWM Recovery using cat.

If you adb push the 3.1.1 su binary from your pc to the /sdcard on your device and after this execute my commands in the first posting of this thread the apps have su rights with superuser.apk again. But you will not be able to add new programs to the superuser app (if a new app requests superuser rights there is no popup). So this is no solution.

The Superuser App is not able to grant superuser rights on android systems > 4.1.1, but the App SuperSu is! So download the SuperSU ZIP from here: http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip

Then copy it to your sdcard and install it using the Recovery. Voila! Everything works again!

Another issue: The Huawei E1750 Surfstick is not detected anymore. On 4.1.1 it was no problem to surf using this stick. But I think this is one of the "great features" of the new android versions...

New recovery version!
:victory: Here it is: The new version 6.0.3.3 of CWM Recovery for the HANNspree HANNSpad SN1AT71 (HSG1279)

Beside some minor bugfixes the main benefit of this release is that there are no more errors when trying to restore the .android_secure folder. So the "dirty" workaround to restore this folder is not necessary anymore.

The .android_secure folder is also automatically restored together with the data partition when selecting "data" from the "advanced restore" options.

http://yadi.sk/d/OmsYk6TIGsBsB

Information on how to install you will find here: http://forum.xda-developers.com/showpost.php?p=49166546&postcount=133

Cheers, Volker

My original question:
Just bought this tablet on Cybermonday for a really good price, but can't find a way to root it for the life of me...
Main problem has been I can't see it using ADB (v1.0.31), always list no devices even with the latest generic Google ADB driver, which shows fine on device manager.
Tablet comes with Android 4.1.1 and no extras, is just a plain version of android with Play market and ES File Explorer pre installed and have access to android stock recovery.

Any ideas?

Also, just in case I start messing with the tablet, Any way I can backup the stock system just in case?

Thanks.

Update:
More info on the tablet...
Model name: SN1AT71
Hardware (According to CPU-Z): gs702a
Board: full_gs702a
 
Last edited:

akxdadev

New member
Aug 13, 2010
2
1
I'm the same. The T71 is terrible. I hated the thing and the so called IPS screen had horrible colour reproduction. I gave the tablet to my sister and she loves it too. This Hannspree Titan 13.3" tablet is a whole lot better though. I compared it to my Samsung Galaxy tab 4 last night and this tablet is slightly faster. If you are looking for a good big screen tablet I highly recommend the Hannspad Titan T72 2015 model once you don't mind being stuck with android 4.4.4.

Hi,

I have ressurected the T71 to give it to my daughter (rooted, CWM last stock ROM), and not a surprise, the stock ROM sucks.
Reading through this thread, it looks like AOKP 4.2 ROM is the most suitable for this tablet. There is a download link for it (CWM backup file) in post #915, but it is dead. Does someone still have it and can reuploat the ROM CWM backup?

Thanks
 

steve30x

Senior Member
Aug 16, 2011
276
66
If there is one bit of advice I would give anybody is don't buy Hannspree tablets. I have a Hannspree Titan tablet from 2015 and they refuse to upgrade its os to KitKat. Theres nobody working on an OS for it and I've broken the damn thing a few times just reinstalling the OS that came with it because after a few months the thing slows to a crawl and the only thing that makes it run at a semi decent pace again is a clean install. Then to reflash the tablet after it soft bricks I need to install windows 7 which is a complete pain to do with this new motherboard and CPU I got three months ago. Theres no windows 10 drivers for the tablet. I even tried running the windows 7 driver in compatibility mode but that doesn't work. So it would be a pain to try and create a new OS on the tablet when I use it every day. I would need a second tablet to work on.

They also brought a Titan 2 last year (2016) with Lolipop on it and they are not upgrading it to Marshmallow which is a 2016 OS. They make tablets with an old OS and never upgrade them. When I can I am buying a Yoga Tab 13.3" tablet which is far better (I know its only marshmallow but it is a much better tablet)
 

tamelion

New member
Feb 11, 2017
3
0
Is there please anyone who can post a dump of the recovery partition of the T74 model? I have screwed my recovery (white screen) and don't have a backup :(

Something like this should do the trick:
Code:
cat /dev/block/acta > /sdcard/recovery.img

Would really appreciate it if anyone can help!
 

CXZa

Senior Member
Apr 9, 2013
787
269
cxzstuff.blogspot.com
Is there please anyone who can post a dump of the recovery partition of the T74 model? I have screwed my recovery (white screen) and don't have a backup :(

Something like this should do the trick:
Code:
cat /dev/block/acta > /sdcard/recovery.img

Would really appreciate it if anyone can help!

The firmware for T74 can be found from my blog. (And for T71 too.)
http://cxzstuff.blogspot.com/2016/11/some-of-firmware-and-tool-packages-i.html

You can split the firmware using the Pad Modify Tool (see my signature).
Find the img under C:\ProgramData\PadModify or use its command line tool
like this: ExtractFWData.exe "thebigfirmwarefwfile.fw" "outdir"


edit: or you also just copy files from the misc partition if recovery.img or its bak is ok.
Copy everything except the boot and modules.
 
Last edited:

tamelion

New member
Feb 11, 2017
3
0
The firmware for T74 can be found from my blog. (And for T71 too.)

You can split the firmware using the Pad Modify Tool (see my signature).
Find the img under C:\ProgramData\PadModify or use its command line tool
like this: ExtractFWData.exe "thebigfirmwarefwfile.fw" "outdir"

edit: or you also just copy files from the misc partition if recovery.img or its bak is ok.
Copy everything except the boot and modules.

Wow, thanks CXZa! I had indeed totally lost the recovery.img and bak. I had previously found that firmware and was put off by the naming of the file ("jellybean" etc.), but since you seem to be well respected around here I gave it a go -- recovery.img now back where it belongs! :D

My outstanding (and actually original) issue now is that when I rooted it seems to have broken bluetooth. Would love to be able to flash the whole firmware without using that pad tool (I have been running it in a VM and it's crazy slow, I'm quite worried about using it to flash).
edit: Just tried - my VM can't handle the USB device directly anyway, so it is definitely not possible for me to use the pad tool

I was thinking I could do something similar to this, with the system.img and OTA.zip I've extracted from the .fw -- but I don't think this tab lets me load to bootloader for fastboot?

Code:
fastboot flash system system.img
fastboot flash misc misc.img
adb sideload OTA.zip

Any other suggestions would be greatly appreciated!

P.S. -- not sure what the PAD.fw is -- would I need that too?
 
Last edited:

CXZa

Senior Member
Apr 9, 2013
787
269
cxzstuff.blogspot.com
when I rooted it seems to have broken bluetooth.
With what you rooted that? My package uses the edify script which has code from the ota.zip.
Done lazy way - I admit - but it should not mess the rights and such.

>Would love to be able to flash the whole firmware without using that pad tool
Are you using linux? There is also a version for linux.

>I was thinking I could do something similar to this, with the system.img and OTA.zip I've extracted from the .fw --
The edify script inside is for traditional update.zip. But the update-binary (and recovery) tend to develop in these.
Basically you could try flash it in recovery and it might write the img files put to /mnt/sdcard/burn/ folder.
Check update-binary with a hex editor for more info, also stock recovery gives some clues what's might work.

I have done some experimental packages for Actions' SOCs having kitkat firmwares but that was before I ported
KK to 7029. And I haven't really tested them in kitkat myself yet. Like my Images2partitions tool which is made
for 7029 might work in this case too. But it needs keys file changer flashed before. It needs some testing.

You can also just cat the system and misc to their partitions by hand. Just simg2img that system file first.

> I don't think this tab lets me load to bootloader for fastboot?
Your thinking is correct, AFAIK.

>not sure what the PAD.fw is -- would I need that too?
Nope if you are just pushing img files to partitions.
 

tamelion

New member
Feb 11, 2017
3
0
>With what you rooted that?
Totally nothing you've done at all. Unfortunately I used KingoRoot when I was feeling particularly lazy -- no idea what it did to my system, which is why I'm keen to start fresh!

> Are you using linux? There is also a version for linux.
Yes -- however it uses python script (for python2 as far as I can tell) and it just segfaults before it can even do anything. No idea how to debug.

> Basically you could try flash it in recovery and it might write the img files put to /mnt/sdcard/burn/ folder. Check update-binary with a hex editor for more info, also stock recovery gives some clues what's might work.
The burn folder is referenced, but not for those images. I tried it anyway, but it flags the OTA.zip as not being signed, so it wouldn't use it -- any way around that?

> You can also just cat the system and misc to their partitions by hand. Just simg2img that system file first.
Are you sure about that? Via ADB on a running system, I can just wipe the system partition??

I've also made a diff of the system and misc partitions in case I can copy/remove files manually, but I have the same reservations about doing this on a running system (and it'll be quite a convoluted task).

EDIT: I managed to use ADB in recovery (pretty sure I couldn't do this before, perhaps it's enabled in the new recovery?!) and used busybox to cat the (raw) system and misc partitions over! :D SOOOO happy right now! Thanks for all your support CXZa. Would love to understand -- is there a reason why people don't/wouldn't use this technique? And are we "lucky" here that the system partition is ext4 instead of yaffs?
 
Last edited:

CXZa

Senior Member
Apr 9, 2013
787
269
cxzstuff.blogspot.com
>the OTA.zip as not being signed, so it wouldn't use it -- any way around that?

> You can also just cat the system and misc to their partitions by hand. Just simg2img that system file first.
Are you sure about that? Via ADB on a running system, I can just wipe the system partition??

I've also made a diff of the system and misc partitions in case I can copy/remove files manually, but I have the same reservations about doing this on a running system (and it'll be quite a convoluted task).

EDIT: I managed to use ADB in recovery (pretty sure I couldn't do this before, perhaps it's enabled in the new recovery?!) and used busybox to cat the (raw) system and misc partitions over! :D SOOOO happy right now! Thanks for all your support CXZa. Would love to understand -- is there a reason why people don't/wouldn't use this technique? And are we "lucky" here that the system partition is ext4 instead of yaffs?

The ota.zip is signed with Actions' keys (soc maker) .
I guess Hannspad have their own then.

Yes, use recovery mode what I forgot to say. But it wasn't needed, was it...
If you are interested you could try my now updated portable custom recovery packages.
As your recovery doesn't use the test keys file (nor Actions' ) you have to extract the keys file from
the package and push it into stock's res folder before flashing.
http://www.slatedroid.com/topic/107...-of-custom-recoveries-cwm-and-twrp/?p=1280178

I don't know if there is much difference what fs is used. Haven't really though it much.
 
Last edited:

Torpedroid

New member
Nov 27, 2016
4
0
Hi, everyone. Few days ago I installed TWRP 2.6.3.0. in my Hannspree SN1AT71 (HGS1279) tablet. The installation was successful but I can't access to the "swipe bar" because a failure in the position of the screen. I tried flashes from the SD and ADB unsuccessfully. Here is a pic of my disaster, LOL. I need help :confused: Thanks.
 

MikeeBBeats

New member
Jun 20, 2018
2
0
I also had a Hannspree Hanbspad T71 which badly needed a ROM update because the stock ROM was terribly optimized so I ported CyanogenMod 11 on to it which made it run better. Since I ported that ROM to the T71 it hasn't broken once and its being used multiple times on a daily basis.

Hi Steve, just wondering how you ported CyanogenMod 11 to the T71 as I would like to get Android 4.4 onto this device, (need 4.4 for certain apps)
EDIT: tablet is android 4.1.1 and is rooted & also has fipsys CWM v6.0.3.3.a installed.
Also any tips for resizing the system partition?
Thanks in advance
Mike
 
Last edited:

steve30x

Senior Member
Aug 16, 2011
276
66
Hi Steve, just wondering how you ported CyanogenMod 11 to the T71 as I would like to get Android 4.4 onto this device, (need 4.4 for certain apps)
EDIT: tablet is android 4.1.1 and is rooted & also has fipsys CWM v6.0.3.3.a installed.
Also any tips for resizing the system partition?
Thanks in advance
Mike
I just looked up on other forums and websites on how to port over custom roms. I can't remember how I done it now because its been three and a half years ago. My Titan tablet is apaperweight now though. I wanted to reinstall the OS but no matter what I do I can't get the tablet to accept the reflash. When I turn on the tablet I just get a blank screen and it loads to bootloader. I've tried many many different methods to reflash the tablet but nothing worked.
 
  • Like
Reactions: MikeeBBeats

MikeeBBeats

New member
Jun 20, 2018
2
0
I just looked up on other forums and websites on how to port over custom roms. I can't remember how I done it now because its been three and a half years ago. My Titan tablet is apaperweight now though. I wanted to reinstall the OS but no matter what I do I can't get the tablet to accept the reflash. When I turn on the tablet I just get a blank screen and it loads to bootloader. I've tried many many different methods to reflash the tablet but nothing worked.

Ah ok, think I remember getting Cyanogen 11 to port over to the hannspad at one stage but cant remember how i did it either! It might have been via the pad product tool or a through a backup restore, will keep trying it anyways, cheers Steve
Edit: probably a display driver issue :/ maybe there's a way to integrate the touchscreen driver into the CM11 package? I see over on Slatedroid it was mentioned that there is a build for KitKat, but that it just needs a recovery restore to install...
 
Last edited:

steve30x

Senior Member
Aug 16, 2011
276
66
The only thing I can think of is saerch the web or ask Hannspree but Hannspree in my experience are of no help. I can't tell you where to get the proper files for that tablet
 

carlisu

Member
Jul 6, 2019
9
1
Hi, I think I hard-bricked my tablet because I can't access recovery. I was doing some tweaks and I installed Cwm but after reboot my tablet was stuck at Hannspree logo, and I can't access recovery( I think I broke the partition) and I can't use fastboot in this tablet. Have this tablet something like edl of Snapdragon to restore system? I have an sn1at71
 

Akodub

Member
Apr 21, 2021
14
0
Hello guys,
I know this is an old thread but am having trouble flashing Hannspree SN1AT4, I have tried the rims here but getting the below error each time. Have tried the Pad tool and got successful message but still the pad not loading


storage intergrality checking, please wait...
checking failed, error=-1
finding update package...
opening update package...
verifying update package...
e: failed to verify whole-file signature
e : signature vérification failed
e: unknown volume for pâyh [/mnt]
installation aborted.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 10
    CWM-Recovery for the HANNspree HANNSpad SN1AT71 (HSG1279)

    I finally made it! :laugh: Here is a working CWM Recovery for the HANNspree HANNSpad SN1AT71 (HSG1279).

    I didn't fully test it but the backup function works. Also mounting and unmounting partitions works as well as the adb shell which is very important if the device is bricked and doesn't boot anymore.
    Before connecting to the device via adb shell it is necessary to mount the /system partition (menu "mounts and storage") because otherwise /system/bin/sh cannot be found by adb shell.

    The CWM recovery by default stores it's backups on the external SD-Card. The benefit is that the backup can easily be plugged out and stored apart from the device. But the recovery is also able to restore backups from the internal sdcard. Those backups can be made online on a running android system by using apps like "Online Nandroid Backup" and "Nandroid Manager". The benefit is that it's not necessary to reboot the device before backing up and you can keep on working.

    There is one problem when creating backups in CWM Recovery: The date/time of the backup is always set to 1st of January 1970 due to a missing backup battery in this device. Look here: http://tau.shadowchild.nl/attn1/?p=341. So if you want to make backups with accurate timestamps you would have to set the actual time of the device using adb shell: Start adb shell and enter:

    Code:
    /system/xbin/busybox date -s "YYYY-MM-DD hh:mm:ss"

    before making the backup.

    To cut a long story short: Download the CWM-Recovery here: http://yadi.sk/d/ArprqzfFFWvy4 and flash it to your (rooted) device. How to do this:

    • Copy the file cwm-recovery.ima to your internal sdcard.
    • Either connect via adb shell and enter su
    • or run a Terminal Emulator and enter su
    • then enter
      Code:
      cat /sdcard/cwm-recovery.ima > /dev/block/acta
    and you're done! Have fun! Comments are appreciated!
    Perhaps someone likes to create an update.zip from it?

    Edit (01/28/2014): There is a new version 6.0.3.3. Look here: http://forum.xda-developers.com/showpost.php?p=49835135&postcount=283
    Edit (05/04/2014): There is a new version 6.0.3.3.a. Look here: http://forum.xda-developers.com/showpost.php?p=52416205&postcount=492
    7
    New CWM Recovery v6.0.3.3

    :victory: Here it is: The new version 6.0.3.3 of CWM Recovery for the HANNspree HANNSpad SN1AT71 (HSG1279)

    Beside some minor bugfixes the main benefit of this release is that there are no more errors when trying to restore the .android_secure folder. So the "dirty" workaround to restore this folder is not necessary anymore.

    The .android_secure folder is also automatically restored together with the data partition when selecting "data" from the "advanced restore" options.

    http://yadi.sk/d/OmsYk6TIGsBsB

    Information on how to install you will find here: http://forum.xda-developers.com/showpost.php?p=49166546&postcount=133

    Cheers, Volker

    BTW: Thank you wyelkins and Sparkrite for the comments! Following your suggestions I still omitted the sd-ext option which could have been used for the sdcard-backup.
    6
    Updated OP with solution, many thanks to @fipsy for the final solution, here is his post for those that need help rooting this device: (UPDATE: Root for 4.2.2 at the end of the post)
    Last week I investigated a lot of days to solve the problem: (I'm sorry for not being able to post working links in this forum because I didn't write enough here. :( So you have to reconstruct my links yourself into your browser)

    As omegadrive supposed you just have to exchange the su binary, give the right permissions and the Superuser App from the Playstore will immediately work.

    The necessary USB drivers for the device are found here: http://yadi.sk/d/54lX5c2O386XU

    They only work with Windows 7!

    After starting the "adb shell" you can gain root permissions on the device by typing "su". The su distributed with the device in /system/xbin is not compatible with common superuser apks. So it has to be exchanged with the version 3.1.1 binary: http://downloads.androidsu.com/superuser/su-bin-3.1.1-arm-signed.zip

    Copy it to your /sdcard. Then continue with adb shell:

    Code:
    $ su
    # cd /system/xbin

    Mount the system partition read/write:

    Code:
    # mount -o remount,rw -t rfs /dev/block/st19 /system

    Rename the original binary for later use (if something fails):

    Code:
    # mv su su-orig

    Copy the binary to the xbin folder:

    Code:
    # busybox cp /sdcard/su ./su

    Change the permissions:

    Code:
    # chmod 6755 su

    Mount the system partition read-only and exit:

    Code:
    # mount -o remount,ro -t rfs /dev/block/st19 /system
    # exit
    $ exit

    Now install the Superuser App from the Playstore - and have fun! Do *NOT* Update the su binary from within the Superuser App or it will be overwritten with a non-working version!

    Cheers, Volker

    CUSTOM RECOVERY FINALLY POSSIBLE!!! Again, many thanks to @fipsy, here is his post:
    I finally made it! :laugh: Here is a working CWM Recovery for the HANNspree HANNSpad SN1AT71 (HSG1279).

    I didn't fully test it but the backup function works. Also mounting and unmounting partitions works as well as the adb shell which is very important if the device is bricked and doesn't boot anymore.
    Before connecting to the device via adb shell it is necessary to mount the /system partition (menu "mounts and storage") because otherwise /system/bin/sh cannot be found by adb shell.

    The CWM recovery by default stores it's backups on the external SD-Card. The benefit is that the backup can easily be plugged out and stored apart from the device. But the recovery is also able to restore backups from the internal sdcard. Those backups can be made online on a running android system by using apps like "Online Nandroid Backup" and "Nandroid Manager". The benefit is that it's not necessary to reboot the device before backing up and you can keep on working.

    There is one problem when creating backups in CWM Recovery: The date/time of the backup is always set to 1st of January 1970 due to a missing backup battery in this device. Look here: http://tau.shadowchild.nl/attn1/?p=341. So if you want to make backups with accurate timestamps you would have to set the actual time of the device using adb shell: Start adb shell and enter:

    Code:
    /system/xbin/busybox date -s "YYYY-MM-DD hh:mm:ss"

    before making the backup.

    To cut a long story short: Download the CWM-Recovery here: http://yadi.sk/d/ArprqzfFFWvy4 and flash it to your (rooted) device. How to do this:

    • Copy the file cwm-recovery.ima to your internal sdcard.
    • Either connect via adb shell and enter su
    • or run a Terminal Emulator and enter su
    • then enter
      Code:
      cat /sdcard/cwm-recovery.ima > /dev/block/acta
    and you're done! Have fun! Comments are appreciated!
    Perhaps someone likes to create an update.zip from it?

    Edit (01/28/2014): There is a new version 6.0.3.3. Look here: http://forum.xda-developers.com/showpost.php?p=49835135&postcount=283
    Edit (05/04/2014): There is a new version 6.0.3.3.a. Look here: http://forum.xda-developers.com/showpost.php?p=52416205&postcount=492

    ROOT for new OTA 4.2.2 update:
    Good news for germany: The rollout began tonight! I just got the update to Android 4.2.2! :laugh:

    Some people asked for the upgrade file to manually update from the recovery. Here it is: http://yadi.sk/d/igsBGsAjFpLsL
    Edit (01/13/2014): Seems this update only works on devices with special G-Sensor hardware (KIONIX 3-axis Accelerometer).

    @ig6677: There you will also find the META-INF you wanted.

    For your information: After my update to Android 4.2.2 root has gone on my device! I expected this. All Apps that need root don't work anymore. I don't know what you did that root was still there after the update...

    Furthermore in /system/xbin there is no su file anymore. Also my CWM Recovery has gone and was replaced by the Stock HANNspree recovery!

    But whats new: If you connect to the device via adb shell you immediately have superuser rights! No su is needed for this anymore. So it's possible to restore the CWM Recovery using cat.

    If you adb push the 3.1.1 su binary from your pc to the /sdcard on your device and after this execute my commands in the first posting of this thread the apps have su rights with superuser.apk again. But you will not be able to add new programs to the superuser app (if a new app requests superuser rights there is no popup). So this is no solution.

    The Superuser App is not able to grant superuser rights on android systems > 4.1.1, but the App SuperSu is! So download the SuperSU ZIP from here: http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip

    Then copy it to your sdcard and install it using the Recovery. Voila! Everything works again!

    Another issue: The Huawei E1750 Surfstick is not detected anymore. On 4.1.1 it was no problem to surf using this stick. But I think this is one of the "great features" of the new android versions...

    New recovery version!
    :victory: Here it is: The new version 6.0.3.3 of CWM Recovery for the HANNspree HANNSpad SN1AT71 (HSG1279)

    Beside some minor bugfixes the main benefit of this release is that there are no more errors when trying to restore the .android_secure folder. So the "dirty" workaround to restore this folder is not necessary anymore.

    The .android_secure folder is also automatically restored together with the data partition when selecting "data" from the "advanced restore" options.

    http://yadi.sk/d/OmsYk6TIGsBsB

    Information on how to install you will find here: http://forum.xda-developers.com/showpost.php?p=49166546&postcount=133

    Cheers, Volker

    My original question:
    Just bought this tablet on Cybermonday for a really good price, but can't find a way to root it for the life of me...
    Main problem has been I can't see it using ADB (v1.0.31), always list no devices even with the latest generic Google ADB driver, which shows fine on device manager.
    Tablet comes with Android 4.1.1 and no extras, is just a plain version of android with Play market and ES File Explorer pre installed and have access to android stock recovery.

    Any ideas?

    Also, just in case I start messing with the tablet, Any way I can backup the stock system just in case?

    Thanks.

    Update:
    More info on the tablet...
    Model name: SN1AT71
    Hardware (According to CPU-Z): gs702a
    Board: full_gs702a
    6
    I have had the best luck with AOKP for a daily driver on this tablet. CM10 seemed to lag more than the stock ROM, and had some stability issues as well IIRC. Recommend you start reading on page 86 of this thread and read it through, don't just skim it.

    What ever you do to this tablet, it will always be a work mule, never a thoroughbred.
    Thanks for your reply, kevinthefixer. I have read this thread more throughly. Because things can be confusing and it's hard to gather all relevant information, I have created a small step-by-step guide how to replace stock ROM with Cyanogenmod 10.1. Here it is:

    1. Download BNMGUYs_CWM_based_recovery_v6.0.3.3_for_ATM7029_portable_[cxz].zip (see http://www.slatedroid.com/topic/107...e-versions-of-custom-recoveries-cwm-and-twrp/) and copy the zip file to a microSD card.
    2. Create a folder called clockworkmod on the microSD card with a backup folder inside that folder.
    3. Download CM10.1_Hannspad_T71.zip (see http://forum.xda-developers.com/showpost.php?p=58325450&postcount=854) and extract the folder CM10.1_Hannspad_T71 to clockwordmod/backup/ on the microSD card.
    4. Insert the microSD card in your tablet (tablet turned off).
    5. Press Vol- + Power button to boot the recovery system.
    6. Select "apply update from sdcard", then sd-ext and then BNMGUYs_CWM_based_recovery_v6.0.3.3_for_ATM7029_portable_[cxz].zip. This will boot CWM once without replacing the recovery partition.
    7. In CWM select "wipe data/factory reset" and confirm with Yes.
    8. After wiping the tablet select "backup and restore", then "restore" and "CM10.1_Hannspad_T71" and confirm with Yes.
    9. Done. Reboot.

    CM 10.1 runs pretty smooth on my tablet, definitely better than stock ROM. Maybe I will try AOKP later, but I am already fairly satisfied.

    Thank you very much Christian Troy, steve30x, CXZa and everybody else who contributed to the creation of custom ROMs for this tablet!
    5
    Hey great news guys. Got a CM 10.2 ROM working like a charm on this thing fast too puts the buggy 4.2.2 stock ROM to shame.
    Does have a few issues but its a great start.
    Follow the steps on this thread except step 1 if you already have fipsy's excellent CWM 6.0.3.3

    All credit goes to the people who made this possible with their hard work like Christian Troy

    http://www.slatedroid.com/topic/102857-compatibility-zip-maker-and-cwm-recovery-maker/#entry1173257