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

Omegadrive · Dec 4, 2013

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)

fipsy said:
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:

fipsy said:
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://xdaforums.com/showpost.php?p=49835135&postcount=283
Edit (05/04/2014): There is a new version 6.0.3.3.a. Look here: http://xdaforums.com/showpost.php?p=52416205&postcount=492

ROOT for new OTA 4.2.2 update:

fipsy said:
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!

fipsy said:
: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://xdaforums.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

Omegadrive · Dec 4, 2013

Omegadrive said:
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 1:
More info on the tablet...
Model name: SN1AT71
Hardware (According to CPU-Z): gs702a
Board: full_gs702a

Update 2:
Found that this tablet is practically the same as the Ainol Novo 10 Hero (don't know if version 1 or 2 thou)
So looking in Google found a thread that has modded ADB drivers and following the instructions managed to get ADB to find the device.
Now to keep experimenting

Omegadrive · Dec 4, 2013

Omegadrive said:
Update 2:
Found that this tablet is practically the same as the Ainol Novo 10 Hero (don't know if version 1 or 2 thou)
So looking in Google found a thread that has modded ADB drivers and following the instructions managed to get ADB to find the device.
Now to keep experimenting

Update 3:
After trying over 20 generic rooting methods I come back defeated, 6 hours of testing and nothing. :crying:

Temil2006 · Dec 5, 2013

I also have picked up 2 of these devices (1 for me and 1 for my wife). I have tried every method I can find to root this, inclicking mutliple one click solutions, apps that are suposted to root, etc. and none of them seem to work, I think the reason why is because the device is being reconized as allready being rooted, SuperOneClick, Framaroot, and Kingo all stated that it was allready rooted ..but apps will not install as if the device was truly rooted. Also geting "access denied" when trying to access the root folder..

Applications that require root will install because they think it has root, they also will prompt stating to give root access/permissions, but when accepting, they simply lock up because they can't access the root correctly.

anyways, I'm done trying for now.. if anyone has any other ideas, please speak up and let us know. thanks!

Masterful1 · Dec 6, 2013

also have one of these

Temil2006 said:
I also have picked up 2 of these devices (1 for me and 1 for my wife). I have tried every method I can find to root this, inclicking mutliple one click solutions, apps that are suposted to root, etc. and none of them seem to work, I think the reason why is because the device is being reconized as allready being rooted, SuperOneClick, Framaroot, and Kingo all stated that it was allready rooted ..but apps will not install as if the device was truly rooted. Also geting "access denied" when trying to access the root folder..

Applications that require root will install because they think it has root, they also will prompt stating to give root access/permissions, but when accepting, they simply lock up because they can't access the root correctly.

anyways, I'm done trying for now.. if anyone has any other ideas, please speak up and let us know. thanks!

I picked up one of these also, I tried a few of the rooting methods you guys listed before finding this post. also no sucess, Would love to get this working bit better,because stock rom is a bit sluggish when it shouldn't be given the specs.

Omegadrive · Dec 8, 2013

OK, kept trying and found some interesting stuff, first of all a screenshot with the tablet info:

Second, it seems the tablet is already rooted but the root is just dummy or the interface has been disabled with deny set as default for any application.

So the trick to root it must be a way to replace de su binary or change the default permission to allow.

Any experts have any idea how to achieve this?

Sent from my HSG1279 using xda app-developers app

revnu · Dec 8, 2013

I thought about buying this Tab. But if there is no working root-methode or costumROM ability thats a dealbreaker for me.

You told that this tab should be identical to the "Ainol Novo 10 Hero". I dont know if that is true, because in one forum some guy told, that the HannSpee is chargeable via the USB-Port, and afaik the Ainol is not. You have the Hannspee, can you tell me if it is chargeable via USB ?

Anyway, on the german Amazon-site there is a guy that claims that costum-ROMs are working on the Ainol

I will ask him how he managed that and perhaps you can try that on you device. But I dont know if he answers, because responds on Amazon-rewievs are not like those in forums (often never answered)

hope some nerd comes up with a nice plan to break into this device......non-rooted devices are s**t!

greetz gerd

Omegadrive said:
OK, kept trying and found some interesting stuff, first of all a screenshot with the tablet info:

Second, it seems the tablet is already rooted but the root is just dummy or the interface has been disabled with deny set as default for any application.

So the trick to root it must be a way to replace de su binary or change the default permission to allow.

Any experts have any idea how to achieve this?

Sent from my HSG1279 using xda app-developers app

Omegadrive · Dec 9, 2013

revnu said:
I thought about buying this Tab. But if there is no working root-methode or costumROM ability thats a dealbreaker for me.

You told that this tab should be identical to the "Ainol Novo 10 Hero". I dont know if that is true, because in one forum some guy told, that the HannSpee is chargeable via the USB-Port, and afaik the Ainol is not. You have the Hannspee, can you tell me if it is chargeable via USB ?

Anyway, on the german Amazon-site there is a guy that claims that costum-ROMs are working on the Ainol

I will ask him how he managed that and perhaps you can try that on you device. But I dont know if he answers, because responds on Amazon-rewievs are not like those in forums (often never answered)

hope some nerd comes up with a nice plan to break into this device......non-rooted devices are s**t!

greetz gerd

Well, I deduced it was identical to the Ainol Novo cause at least the hardware specs are identical and the board and CPU are reported by CPU - Z to be the same one. Tablet layout is a little different thou.

Anyway yes, this one charges through the USB port, but really slowly, good enough to have the USB connected while using it and will not drain the battery, but on my last test it barely charged 5% in 3 to 4 hours of while using it.

Crossing my fingers you can get in contact with that guy and we can figure out how to root this ****er lol

Sent from my XT910 using Tapatalk

revnu · Dec 9, 2013

Omegadrive said:
Well, I deduced it was identical to the Ainol Novo cause at least the hardware specs are identical and the board and CPU are reported by CPU - Z to be the same one. Tablet layout is a little different thou.

Anyway yes, this one charges through the USB port, but really slowly, good enough to have the USB connected while using it and will not drain the battery, but on my last test it barely charged 5% in 3 to 4 hours of while using it.

Crossing my fingers you can get in contact with that guy and we can figure out how to root this ****er lol

Sent from my XT910 using Tapatalk

He answered me, that his Hero came rooted when he bought it and that he simply had to install CWM. He posted a link with iinstructions but I bet it wont help, because the HANNSpree cames with kind of a fakeroot.

Omegadrive · Dec 9, 2013

revnu said:
He answered me, that his Hero came rooted when he bought it and that he simply had to install CWM. He posted a link with iinstructions but I bet it wont help, because the HANNSpree cames with kind of a fakeroot.

Unfortunately it didn't worked, kept failing at validating files when it was installing from default recovery.
Anyway, going to try another method, these are the steps I followed:

1) Get ADB working and recognized.
a) Download these modded drivers and extract them.
b) Do this to install them since the drivers are not signed:
run CMD as admin
bcdedit -set TESTSIGNING ON
reboot
install driver from device manager
bcdedit -set TESTSIGNING OFF
reboot
c) Go to %userprofile%\.android folder and if it doesn't exist create a text file named "adb_usb.ini" (no quotes and make sure INI is the extension, not TXT), open it and just add "0x10D6" (no quotes), save it
d) open CMD as admin
adb devices

Your device should be recognized at this point, this is what I got:
C:\>adb devices
List of devices attached
0123456789ABCDEF device

2) Will update post with new findings here...

fipsy · Dec 9, 2013

How to root the device

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

Temil2006 · Dec 9, 2013

Omegadrive said:
Unfortunately it didn't worked, kept failing at validating files when it was installing from default recovery.
Anyway, going to try another method, these are the steps I followed:

1) Get ADB working and recognized.
a) Download modded drivers and extract them.
b) Do this to install them since the drivers are not signed:
run CMD as admin
bcdedit -set TESTSIGNING ON
reboot
install driver from device manager
bcdedit -set TESTSIGNING OFF
reboot
c) Go to %userprofile%\.android folder and if it doesn't exist create a text file named "adb_usb.ini" (no quotes and make sure INI is the extension, not TXT), open it and just add "0x10D6" (no quotes), save it
d) open CMD as admin
adb devices

Your device should be recognized at this point, this is what I got:
C:\>adb devices
List of devices attached
0123456789ABCDEF device

2) Will update post with new findings here...

umm, instead of using custom drivers, why not simply use the newest android Drivers? confirmed they work and device is reconized correctly, as long as you "install official droid drivers" then change the "adb_usb.ini" to only include 0x10D6 device, same as your last steps, but using official drivers, instead of custom ones. Maybe it has something to do with the failures?

---------- Post added at 08:00 PM ---------- Previous post was at 07:53 PM ----------

fipsy said:
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

thanks for this info. I'll test it out tonight, and let you know.
one question though.. so are you saying that future updates of SU will not work? if we do this, should we also disable auto-updates? If the software does update, will it break our system.. or simply that we need to reload the SU over again, but the OS will open, just limited to "non-rooted" ? ??

Omegadrive · Dec 9, 2013

fipsy said:
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

OMG!!! IT WORKED!!!
MANY THANKS!!!
Now have full root privileges woot!!! Tested with Titanium backup and ES File explorer they accepted root and got permission prompts :highfive:
I will update the OP with your instructions, they worked beautifully, MANY THANKS AGAIN!!!

Btw, Do you have any idea on which custom recovery may work and if the bootloader can be unlocked? (if it is locked, I can't see anything when booting into fastboot mode and Windows doesn't recognize the tablet at that moment, only shows unknown device)
I want to make a backup of the stock rom and start testing CM builds on it.

Omegadrive · Dec 9, 2013

Temil2006 said:
umm, instead of using custom drivers, why not simply use the newest android Drivers? confirmed they work and device is reconized correctly, as long as you "install official droid drivers" then change the "adb_usb.ini" to only include 0x10D6 device, same as your last steps, but using official drivers, instead of custom ones. Maybe it has something to do with the failures?

The original Android drivers never worked for me, used latest version 8.0 and the device was not recognized for some reason, only the modded drivers worked to recognize the ADB device. Btw, I'm using Windows 8.1 Pro and had to turn off driver signature to get the ADB drivers installed, maybe the issue was Win8.1 itself, but oh well, at least now we have a solution. :laugh:

Omegadrive · Dec 9, 2013

fipsy said:
Do *NOT* Update the su binary from within the Superuser App or it will be overwritten with a non-working version!

Cheers, Volker

Update: After giving permissions with Superuser I went ahead and installed my SuperSU Pro license, gave it root rights (told it NOT to uninstall the other root app on prompt) and installed as a system app from within the app itself, reboot and voila! still fully rooted and binary updated (it replaced the other Superuser on reboot). So yeah, su binary updates are possible now :victory:

saciorlux · Dec 9, 2013

is there any custom recovery to install on this tablet?

fipsy · Dec 10, 2013

Temil2006 said:
umm, instead of using custom drivers, why not simply use the newest android Drivers?

This also was my first attempt but it failed.

So I went the same way as Omegadrive did: I identified the device as a clone of the "Ainol Novo 10 Hero" and searched for appropriate drivers. I found the same ones as Omegadrive did.

And they seem to be the only ones that are working.

Temil2006 said:
one question though.. so are you saying that future updates of SU will not work? if we do this, should we also disable auto-updates? If the software does update, will it break our system.. or simply that we need to reload the SU over again, but the OS will open, just limited to "non-rooted" ? ??

I don't know if future binaries will work. When I manually updated the su-binary within the Superuser App it definitely didn't work anymore. Maybe because the su was exchanged with an older version (3.0.*). But Omegadrive said that updates are possible. So I don't know at the moment. Be careful anyway! Normally there is no reason for updating fully working binaries. The su binary is never updated automatically. So you don't have to deactivate any auto-updates.

Cheers, Volker

---------- Post added at 03:34 AM ---------- Previous post was at 03:04 AM ----------

Omegadrive said:
Btw, Do you have any idea on which custom recovery may work and if the bootloader can be unlocked?

The recovery mode is activated by pressing "Volume down -" and at the same time pressing the on/off key for about 3 seconds. Then releasing it while keep on holding down the "Volume -" until the recovery menu appears.

I think it will be possible to adapt the CWM Recovery. Perhaps we can investigate together on that!? Here the recovery file system table (for nandroid etc.). I just sent it to Ameer Dawood, the developer of "Online Nandroid Backup", so that he may integrate it into his App.

recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /mnt/sdcard vfat /dev/block/actj (null) 0
2 /system ext4 /dev/block/actc (null) 0
3 /cache ext4 /dev/block/acte (null) 0
4 /data ext4 /dev/block/actd (null) 0
5 /data_bak vfat /dev/block/actf (null) 0
6 /boot vfat /dev/block/actb (null) 0
7 /recovery vfat /dev/block/acta (null) 0
8 /misc emmc /dev/block/actb (null) 0
9 /mnt/sd-ext vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0 0

Omegadrive · Dec 10, 2013

Oh nice, thanks for the help, I'm no programmer, just a tinkerer, I'm willing to test anything you throw this way lol
My main priority right now is to make a backup of the current rom and then look for a way to repartition the /data cause 1Gb for apps is way too low, specially when there are 13Gb free on /sdcard, as want to make it 4Gb for /data and rest internal. I'm assuming I have to install custom recovery for that, or can ir be done right now from ADB?

Sent from my HSG1279 using Tapatalk

fipsy · Dec 10, 2013

If you want to store parts of the filesystem (like /data/app, /data/app-private, /data/dalvik-cache and libs) to the sd-card you probably will have to install a custom rom like cyanogenmod which supports additional partitions / filesystems on the sd-card (like ext2).

But you're right. The first thing to do before making any experiments is to make a full backup (nandroid) and be able to restore it from a recovery. So we first should investigate on that...

fipsy · Dec 10, 2013

I just installed the CWM recovery for the Ainol Novo 10 Hero 2 for testing. The device started into the CWM recovery screen but then failed to mount some folders. The menu was working but most features were not functional. This means that the HSG1279 is *not* fully compatible with the Ainol Hero 2.

So we have to find another solution. I suppose it will be quite a lot of work to adapt the CWM recovery to this device...

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

Senior Member

Senior Member

Senior Member

New member

New member

Senior Member

Attachments

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

New member

Senior Member

Senior Member

Senior Member

New member

Senior Member

Senior Member

Senior Member

Senior Member

Similar threads

Top Liked Posts