yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] CXZa:
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.
[General Questions and Answers] Torpedroid:
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.
[General Questions and Answers] MikeeBBeats:
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
[General Questions and Answers] steve30x:
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.
[General Questions and Answers] MikeeBBeats:
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...
[General Questions and Answers] taskmann:
A very big Thank You ! :good:
[General Questions and Answers] picasso2489:
where can i find a (OEM) boot or recovery.img for my hannspree hannspad sn12tp1b?

i ve crashed this pad with an magisk-patched.img :(
[General Questions and Answers] steve30x:
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
[General Questions and Answers] carlisu:
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
[General Questions and Answers] Akodub:
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.
[General Questions and Answers] juliovegap:
Hello.

Long time has passed. Does anyone have the mentioned file CM10.1_Hannspad_T71.zip (see http://xdaforums.com/showpost.php?p=58325450&postcount=854)?

Thanks.
[General Questions and Answers] taskmann:
Here you go.

File on MEGA

mega.nz

It was very helpful when I needed this file. At the time I did some serious search before locating it.

I had it still on an SD card just in case someone was in a similar situation.
[General Questions and Answers] juliovegap:
So many thanks! Indeed, I downloaded and found out my tablet is the S74 and not the S71.

However, all the custo ROMs developed I have found are for the S71. On S74 I have only found the root jailbreak.

Does anyone know if there is a customized ROM for S74?

Thanks!
[General Questions and Answers] rabemer:
working or not on hannspree sn1at71

Hi, i am a little confused on this. So eventually, is it possible to root Hannspree SN1AT71, HSG1279, the same way as described as if it were the Ainol Novo 10 Hero???

If noy, is there a way to root it??

Thanks,

RAfa
[General Questions and Answers] Bluze:
Follow the instructions in the very first post on this thread. Worked perfectly.
[General Questions and Answers] JimboJoe:
I got to study a little more the recovery issue. I must say that I'm a beginner in this field.

The recovery partion contains a recovery.img file, which is in a specific format, as detailed here: http://xdaforums.com/showthread.php?t=443994

I tried to use the CWM builder with this file, but unsuccessfully (see log here: http://pastebin.com/sgJjjUs3)

The issue is that the tablet model is unknown from CM source tree. I tried with the (almost working) Ainol recovery, with the same result.

So, I my opinion, the options are:

- mess with compilation of recovery from scratch, figuring out the different configuration options. This would be required anyway to build any CM/AOSP ROM from source,

- unpack the Ainol recovery and modify the different mount points to be adapted to our tablet.

The second option seems like the quickest to a working recovery... What do you think?
[General Questions and Answers] fipsy:
Sometimes it may help to read not only the first page of a thread but also the second. :p
[General Questions and Answers] fipsy:
Thanks a lot for this hint! It is the answer to the first problem.

The processor in this tablet is a mix of a cortex-a5 and cortex-a9. So you would have to obey this hint: "TARGET_CPU_VARIANT not set or set to an unknown value. Possible values are cortex-a5, cortex-a7, cortex-a8, cortex-a9, cortex-a15, krait, scorpion. Use generic for devices that do not have a CPU similar to any of the supported cpu variants."

So you probably should use "generic" as the CPU variant!?

If it's not just the CPU-problem you're probably right. ;)
[General Questions and Answers] fipsy:
I unpacked the Ainol CWM recovery and looked into the recovery.fstab. To my surprise the mounts were all correct:

# mount point	fstype	device

/emmc	auto	/dev/block/actj
/system	ext4	/dev/block/actc
/cache	ext4	/dev/block/acte
/data	ext4	/dev/block/actd
/boot	vfat	/dev/block/actb
/recovery	vfat	/dev/block/acta
/misc	emmc	/dev/block/actb
/sdcard	vfat	/dev/block/mmcblk0p1	/dev/block/mmcblk0

And this is the recovery.fstab of the original recovery image from the HSG1279:

# mount point	fstype	device

/mnt/sdcard	vfat	/dev/block/actj
/system	ext4	/dev/block/actc
/cache	ext4	/dev/block/acte
/data	ext4	/dev/block/actd
/data_bak	vfat	/dev/block/actf
/boot	vfat	/dev/block/actb
/recovery	vfat	/dev/block/acta
/misc	emmc	/dev/block/actb
/mnt/sd-ext	vfat	/dev/block/mmcblk0p1	/dev/block/mmcblk0

So our problems with the Ainol CWM recovery must have another reason. :(

Furthermore the recovery.img within the HANNspree recovery partition (/dev/block/acta) is NOT packed with gzip but just plain and unpacked. The CWM online recovery builder says that it is not able to unzip the recovery because it is not packed with gzip. Maybe we achieve something if we pack it before uploading to the online builder...
[General Questions and Answers] fredobhr:
My Hannspad is bricked

Hello! Please help me!!! I'm not very good in english-writing but I can say my Hannspad SN1AT71WRE is bricked. I need your help so much. It's because I tried to root it before I fell on this post and I used a bad Tablet's dirver or something like that. Please help me, it's my own Xmas' gift and now I'm like a dumb. I don't write english very well but I understand
[General Questions and Answers] fipsy:
If you are able to enter the stock recovery (hold down 'Vol -' and press the power-button for 2 seconds then release it while keep holding down the 'Vol -' until the recovery starts - it may take 10-20 seconds) you can try a factory reset. If this doesn't work there is (for the moment) no other way to unbrick the device. It probably will also be possible to recover it using the Actions PAD product tool which you may download for the Ainol Novo 10 Hero from Ainol. But you would need the stock images for the HSG1279. At the moment I don't have a download source for these images.
[General Questions and Answers] fredobhr:
Thank you

Thank you very very very much!!! It worked and I'm now reply you from my tab :good:
[General Questions and Answers] JimboJoe:
I did extensive tests, unfortunately all unsuccessful

- I tried the TWRP recovery for Ainol devices available on the slatedroid forum (http://www.slatedroid.com/topic/91617-custom-recovery-twrp-v2630/) ; they all boot OK, and all suffer from the unavailable partitions.

- We share the same touch screen as the Ainol Discover, but it has a different resolution. I tried repacking the TWRP recovery by including the right ui.xml (from the Hero 2 recovery), the touch screen responds, but is not correctly calibrated. Running TWRP could help us because it embeds a file manager and basic terminal.

- I tried "porting" the differences from the Hannspree recovery to the CWM recovery for Ainol devices; it boots, but still no mounts

- I tried repacking this CWM recovery with the Hannspree zImage: it doesn't boot (stuck on Hannspree logo)

- I managed to get the CWM recovery builder to work by unzipping the initramfs.cpio.gz (keeping the .gz extension) and repacking it. The building is successful, but the recovery doesn't boot (stuck on the Hannspree logo). Generation log: http://pastebin.com/JP9TdTHG

- I tried the same generated recovery but after unpacking the initramfs.cpio.gz (keeping .gz extension) to the same result

- I tried copying the different files from this generated recovery's ramdisk to the original Hannspree recovery's ramdisk (essentially /sbin, /res): doesn't boot

- I tried the same thing with the file from the Ainol CWM recovery: same result

I couldn't manage to establish an adb connection to my computer on any of the recoveries. Hopefully my computer could be the cause, and someone could try this? Accessing via adb could help us see where the partitions are.

Maybe the probem resides in the kernel itself, and we need to generate one that contains something a bit different from the Ainol CWM's one?

In my opinion, we should contact people from the Ainol slatedroid forums to get help, because I clearly don't have enough knowledge (and time) to solve that...
[General Questions and Answers] peterc18042:
Great Tool

Hello All,

I just wanted to share the tool I used to root my Hannspad HSG1279. It worked flawlessly, didn't even take a minute. If someone else benefits from it please let us know.

www,cydiaimpactor,com
[General Questions and Answers] fipsy:
Seems that you nearly did the same that I did yesterday. ;)

Except that I didn't try TWRP. It's also not a good idea to build a touchscreen recovery. I tried to build a "normal" recovery with the online CWM builder and it ended with success. But the recovery didn't start. The recovery for the Novo 10 started but couldn't mount partitions. I also extracted this image as well as the original image and the one the for Ainol Novo 10 Hero with unpackbootimg on Cygwin. I tried to copy a lot of things from one image to the other and then remade the images with mkbootimg. They all started up but none of them really worked. I think the main problem is the recovery binary (/sbin/recovery). It has to be built exactly for the HSG1279. Every other binary doesn't work. So we probably would have to setup a complete android developers environment under ubuntu linux to compile a new recovery from sources. And it's not certain that the binaries will work after that.

I tried exactly the same. The problem is the recovery binary (see above).

I found out that there need to be the right addresses for kernel and ramdisk in the bootimage header. If I repack an image with mkbootimg the following parameters lead to success (the files in the ramdisk also need to have the ownerid 1003 or 0 and the groupid 0 - when packing with cpio):

find . -path "./dev*" | cpio --owner=0:0 -o -H newc > ../ramdisk.img
find . ! -path "./dev*" | cpio --append --owner=1003:0 -o -H newc -O ../ramdisk.img
gzip ../ramdisk.img
mkbootimg --base 00000000 --pagesize 2048 --kernel_offset 00008000 --ramdisk_offset 01000000 --tags_offset 00000100 --kernel ../kernel.img --ramdisk ../ramdisk.img.gz --output ../recovery.img

The problem is that if adb was started from the recovery the USB VID and PID are different from the IDs expected by the USB drivers. I suppose different USB drivers are necessary for that.

Did you always use the stock kernel when repacking the images? I always used the stock kernel. If you use the online cwm builder it also extracts the stock kernel from the original recovery and uses this one for the CWM recovery.

Same here...
[General Questions and Answers] fipsy:
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:

/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

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
[General Questions and Answers] pedropep:
CWN is perfect

Thanks fipsy for your work. It works perfectly and I have my first backup. Can I change the date of the ClockworkMod folder manually?:good:
[General Questions and Answers] Bluze:
Good job fipsy! Unfortunately, I won't get a chance to try it. I turned mine on yesterday after being on the charger for a few hours and nothing. I get a faint backlight, but that's all. No logo, no battery icon when charging, won't boot into recovery. I bought it from Amazon though, and haven't had it for 30 days yet so back it goes. I guess I'll look at some other brands that have more support for custom roms and stuff.
[General Questions and Answers] JimboJoe:
Many thanks and congrats fipsy!! So, how did you achieve that? I was planning to set-up a build environment :)

And... Has anyone tested a restoration...? :)

---------- Post added at 04:13 PM ---------- Previous post was at 03:53 PM ----------

Yes.
[General Questions and Answers] pedropep:
Yes, I have also tested the restoration successfully
[General Questions and Answers] fipsy:
I got a lot of reports with exactly the same issue in german HSG1279 forums (http://www.android-hilfe.de/hannspree-forum/491077-hannspree-hannspad-sn1at71.html#post6992292). Just in the last two days four people were reporting exactly the same problem. They turned their device off, charged it for a couple of hours and after this it could not be turned on again. There was just a pale backlight. Some are able to enter the recovery and some are not. No one could recover the device by a factory reset. It seems this is an epidemic failure on this devices and has to do with the charging function. Perhaps an overvoltage in the power adapter?!

It would be of strong interest if someone could measure the voltage of the power adapter on a device thats bricked while charging. My power adapter has a voltage of 5.2 Volts. This is okay. A maximum of 5.5 Volts should normally be allowed.

---------- Post added at 05:49 PM ---------- Previous post was at 05:37 PM ----------

As the basic recovery I used the stock one. I adapted the default.prop, init.rc, recovery.fstab and uevent.rc. I copied most sbin-files from the ainol recovery to the sbin folder except the files that have already been there including the recovery binary. I don't know if I did some more things that I can't remember. ;) But somehow it finally worked. :cyclops:

What isn't working at the moment is charging while a PC is connected to the recovery via USB. I don't know if charging worked with the stock recovery.
[General Questions and Answers] Bluze:
For what it's worth, I messed with it for a couple hours yesterday and got no where. So I made arrangements to ship it back but I was concerned about not being able to get my personal information off of it. So I decided to play with it some more today and got it to come back on. I don't know what did the trick though. I plugged the USB and the power adapter into it and started pressing around on the front of the screen Pressing in certain areas made the backlight slightly brighter but I doubt that meant anything.. Unplugged the charger and plugged it back in numerous times. Then all of a sudden the charging icon came on. After a few minutes it booted up with an almost totally dead battery but was charging.

Soon as it did, I removed the modifications and restored the original SU binary and did a factory reset. It seems to be working fine again, but I'm still sending it back. I pulled out my VOM but I haven't used it for so long the battery is dead so I'll get a new one this evening and let you know what the output is before I send it back.
[General Questions and Answers] Bluze:
Just tested it, it's 5.2 volts. I held it on for a few minutes to see if there's any spikes but that got boring real fast. :D
[General Questions and Answers] Omegadrive:
Many thanks again, updated OP with the solution. :highfive:
[General Questions and Answers] fipsy:
:) So the voltage is not the problem. Except there are high frequency spikes from the switching power supply only visible on an oscilloscope. Did you use the quick boot option on your tablet when it bricked?
[General Questions and Answers] foszuled:
I don't know why but I can't download the cwm recovery? Its like the link is dead or something can someone re upload it?
[General Questions and Answers] fipsy:
I just tested it. The link is working faultlessly. What message do you get from your browser if you click on the link?
[General Questions and Answers] fipsy:
If you like to use "Online Nandroid Backup" and "Nandroid Manager" for your nandroid backups you will notice that Online Nandroid will backup everything except the recovery and the boot partition. The reason is that Online Nandroid Backup isn't able to recognize the HSG1279. Furthermore this app isn't able to deal with block devices that are beginning with "act" (meaning "Actions" - the manufacturer of the processor in HSG1279). It only "likes" block devices containing mtd, mmc, bml or nand as you can see in the sources: https://github.com/ameer1234567890/OnlineNandroid/blob/master/onandroid. But knowing how this app internally works it is possible to "fake" such a device and get Online Nandroid to backup all of the partitions including boot and recovery.

You need to copy a special patch file to the /system folder for achieving this. I created one and you may download it here: http://yadi.sk/d/RN0Op8c8FZupM and extract the file partlayout4nandroid to your /sdcard.

Now connect via adb shell or Terminal Emulator to your device and enter the following commands:

$ su
# mount -o remount,rw -t rfs /dev/block/st19 /system
# busybox cp /sdcard/partlayout4nandroid /system/partlayout4nandroid
# chmod 644 /system/partlayout4nandroid
# mount -o remount,ro -t rfs /dev/block/st19 /system
# exit
$ exit

If you now make a backup with Online Nandroid Backup you will notice that all of the partitions (there are six) will be backed up. But the boot and recovery partitions will be backed up as image files (*.img) not as tar-files and thus can neither be restored from Nandroid Manager nor directly from CWM recovery. You just can restore them in the CWM recovery using adb shell (the well known "cat"-procedure). So if you don't change boot or recovery too often it is enough to make one CWM backup and just renew it when you changed something in recovery or boot.
[General Questions and Answers] foszuled:
Ok I tried again this am worked.. I don't know last night it just said web page not working I even tried a different download just to see if it was my internet and downloaded the other thing whatever thanks fipsy for all your hard work
[General Questions and Answers] Bluze:
As best as I can remember, I completely shut it down before I put it on the charger. What's funny is the next day when I DID finally get it to boot again, I had to let it charge for about 10 minutes after the charging indicator finally came back on again before it would boot. The icon showed it had only a 4 percent charge. So it seems something totally drained the battery while it was shut off. Then it would not charge. Then it would charge. Confusing huh? LOL! I have it running right now, and it seems totally fine again. But it's still going back. Especially knowing it seems to be a common problem. I'm quite sure if I keep it, it will most likely happen again.
[General Questions and Answers] tonza012:
I don't know why but I can't download the cwm recovery? Its like the link is dead or something can someone re upload it?
[General Questions and Answers] fipsy:
Seems something has deeply discharged the battery. So that the Pad thought the battery is broken and would not recharge it. The problem with all this new devices is that batteries cannot be exchanged anymore. And because a lot of batteries give out long before their estimated lifetime this concept is real trash. It's like buying a new car if the old one ran out of fuel...

---------- Post added at 07:14 PM ---------- Previous post was at 07:09 PM ----------

foszuled primarily had the same problem but a short time later it was working. Maybe Yandex.Disk every now and then has problems with downloads from some countries. It's located in russia. Maybe the intercontinental connections to america sometimes lag. Here in germany it's no problem.

So try again! :)
[General Questions and Answers] djport1973:
installing and testing. Copy to internal memory and microsd