yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 3 General] lahegry:
I tried pressing the icons on the bottom but that was a no go only floating windows work. Yes I did the buld prop edit flash bar force closes
[Galaxy Tab 3 General] THEDEVIOUS1:
test 7

thx but for some reason your screenshots wont load or download correctly...i've linked to test 7 below. this may kill floating mode but hopefully the flashbar will work again and maybe even multiwindow will function properly now. If the flashbar does not force close...first try to DRAG (not click) some apps to enable splitscreen. Next...go to "system/etc/permissions" and delete "com.sec.feature.multiwindow.phone.xml" and reboot then see if the flashbar still functions

INSTALL INSTRUCTIONS

1. Install "samsung multiwindow manager (note 10.1)" from the play store (do NOT patch anything when i asked...this step is not mandatory but u will want to use this to enable some more apps since the default ones may not work)

2. Edit your build prop by adding the line qemu.hw.mainkeys=0 to the bottom of the file, save then reboot into recovery

3. Flash the Test zip below

4. You should now notice navigation buttons at the bottom...press the up arrow/miniapps tray and try some of the apps (please be aware that the stock samsung apps may force close and will need to be replaced...also launching from the flashbar/left launcher will still probably not work)

https://drive.google.com/file/d/0B7yxeu9x48ILRHNjOWlibDNJakk/edit?usp=sharing

^T21xx TEST 7

[MENTION=2484493]lahegry[/MENTION]

if u can please go back and flash test 5...i'm thinking that maybe the 5 icons/layout modes in the mini apps tray MAY work in that version. This is a superior version of the mod and that way we can actually delete the flashbar altogethor...thx in advance
[Galaxy Tab 3 General] lahegry:
Still a no go on anything but floating windows. Tried both test 5 and 7 with no obvious differences. Hopefully the image shows.
[Galaxy Tab 3 General] THEDEVIOUS1:
thats exactly what i was thinking...those are not actually floating multiwindow apps but are the original miniapps instead which are separate apks. It seems as if your permissions files are either not there or are set with improper perms...could u please check that all of the xml files located in "system/etc/permssions" in the zip are located in the same location on your device and also that the perms are in fact set to 0644 (or "rw--r-r-" which is the same thing). In fact if i recall correctly....u were one of the users who were getting bootloops trying to install the original zip so now i'm wondering if the zip is even flashing anything at all. The miniapps bar comes from only editing the build prop and has NOTHING to do with any of the files in the zip...so the real question is there any way u can prove that the zip actually made any changes to your device? (when u perform the above xml check that would be one way i guess). oh yeah...is the flashbar still force closing? (kinda just realized how dumb my question was when i'm sitting here looking at the pic with the icons i personally added to the systemui :silly:...but my statement still stands about the permissions files)
[Galaxy Tab 3 General] THEDEVIOUS1:
TESTERS?

this thing already could be working but we wouldnt even know...so NOBODY wants to help test?! :confused:
[Galaxy Tab 3 General] jetboss:
i dont mind testing it just tell me what to do :D
[Galaxy Tab 3 General] gagan313:
I wouldn't mind but I am a noooooooooob.....All i can do is re-flash, use cwm and I have a smt-210

And tell me clearly what to do :) videos help :)
[Galaxy Tab 3 General] THEDEVIOUS1:
check post #22 for files and instructions...start with test 5. If u have any questions just post...thx
[Galaxy Tab 3 General] jetboss:
ok how do i edit the build prop? downloaded test 5

---------- Post added at 01:59 PM ---------- Previous post was at 01:50 PM ----------

dont worry reading about it now will post results as soon as possible

---------- Post added at 02:28 PM ---------- Previous post was at 01:59 PM ----------

reading how to do it now will post results soon

---------- Post added at 02:29 PM ---------- Previous post was at 02:28 PM ----------

reading how to do it now will post results soon

---------- Post added at 02:41 PM ---------- Previous post was at 02:29 PM ----------

getting an error everytime i try to save the build.prop

---------- Post added at 02:52 PM ---------- Previous post was at 02:41 PM ----------

didnt get that prop file edited but i noticed when u press the multi window button in my apps the screen gets bigger so i think that means its partially working not sure if app settings from the xposed frame work could fix this or the flash going to back up and flash then post results
[Galaxy Tab 3 General] THEDEVIOUS1:
the specifics on how to do so depend on which app u are using but all of the file explorers will require u to change system mount to

"r/w" (read/write) before u will be allowed to save the edited file...for example in es file explorer (which is what i use) there will be a "fast access" menu on the left side of the screen (depending on layout) under which u will see "tools" click that then u will see "root explorer" with an on/off switch. just turn it on and wait for the superuser prompt, hit allow, then click the words "root explorer" (right beside the on button u just pressed) and a menu will come up where u will choose mount "r/w" and just place a bubble in r/w beside all of the available partitions and hit ok then go back, edit/save your build prop and continue with the rest of the instructions
[Galaxy Tab 3 General] gagan313:
Hey thanks, and I dont get one thing, can you explain how to edit the buil.prop part. plz

;)
[Galaxy Tab 3 General] jetboss:
thanks very much got it to work just flash the test 5 file got the soft menu to the bottom of the screen working no fc when using home or back buttons :D whats next do i open the multi window manager and enable packages?

---------- Post added at 04:53 PM ---------- Previous post was at 04:41 PM ----------

seems to be working wooot but just a couple apps like task manager music player
[Galaxy Tab 3 General] 4MUSKRAT:
Sprint SM-T217S

The Sprint Samsung Galaxy Tab 3 SM-T217S 7 Inch LTE Version came Stock with Multi Window & Multitasking So if need be I can pull the APK & u guys can try it since it's already setup for a 7 inch screen. I Didn't read every post in this thread so sorry if someone already mentioned this. Let me know if you guys want this apk pulled.

And I was able to Download Multi Window Manager from the Play Store & add whatever app's I wanted to add & use in the Multi Window. Seems to be working great for me so give it a shot mayb.
[Galaxy Tab 3 General] tempdroid:
Yes please,I want to port this to RocketTab :p
[Galaxy Tab 3 General] 4MUSKRAT:
I went into the system folder then into the apps folder & didn't see an apk labeled multi anything so ill look n see what the file name you guys have uploaded & see if I can find it. Unless you can tell me where exactly to look ill do it the above mentioned way. Didn't want you to think I forgot about ya.
[Galaxy Tab 3 General] tempdroid:
Thanks mate. I've downloaded a T217 ROM and will have a look for myself.

Stay tuned...
[Galaxy Tab 3 General] M1k3Carson1369:
Is this what you're looking for? Not a flashable zip, just pulled from /system/app/… and any MW Manager app for phone OR Note 8/10.1 helped me enable basically every app to use it with…

SGT3_SM-T217S

Rooted TW 4.2.2

CWM Recovery
[Galaxy Tab 3 General] M1k3Carson1369:
Aaargh!! Forgot to attach the .Zip… =/

https://drive.google.com/uc?id=0B6IOluMZjWBwdkUwSTEzVVJsbjQ&export=download

SGT3_SM-T217S

Rooted TW 4.2.2

CWM Recovery
[Galaxy Tab 3 General] tempdroid:
Thank you for your help. Basically this is the apk, but there are further modifications needed on other apks, SystemUI should be one example. This file is still odexed, but no problem, I've downloaded and deodexed a complete T217 ROM. T217 is on 4.2.2 so I have to try, if it will work.
[Galaxy Tab 3 General] M1k3Carson1369:
Ah, ok. Lol, sorry

SGT3_SM-T217S

Rooted TW 4.2.2

CWM Recovery
[Galaxy Tab 3 General] gr9nole:
Not working yapani sikim dont flash

SM-T311 cihazımdan Tapatalk kullanılarak gönderildi
[General Questions and Answers] Omegadrive:
Updated OP with solution, many thanks to [MENTION=5110154]fipsy[/MENTION] 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)

CUSTOM RECOVERY FINALLY POSSIBLE!!! Again, many thanks to [MENTION=5110154]fipsy[/MENTION], here is his post:

ROOT for new OTA 4.2.2 update:

New recovery version!

My original question:
[General Questions and Answers] Omegadrive:
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 :D
[General Questions and Answers] Omegadrive:
Update 3:

After trying over 20 generic rooting methods I come back defeated, 6 hours of testing and nothing. :crying:
[General Questions and Answers] Temil2006:
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!
[General Questions and Answers] Masterful1:
also have one of these

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.
[General Questions and Answers] Omegadrive:
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? :D
[General Questions and Answers] revnu:
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
[General Questions and Answers] Omegadrive:
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
[General Questions and Answers] revnu:
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.
[General Questions and Answers] Omegadrive:
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...
[General Questions and Answers] fipsy:
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:

$ su
# cd /system/xbin

Mount the system partition read/write:

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

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

# mv su su-orig

Copy the binary to the xbin folder:

# busybox cp /sdcard/su ./su

Change the permissions:

# chmod 6755 su

Mount the system partition read-only and exit:

# 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
[General Questions and Answers] Temil2006:
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 ----------

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" ? ??
[General Questions and Answers] Omegadrive:
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.
[General Questions and Answers] Omegadrive:
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:
[General Questions and Answers] Omegadrive:
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:
[General Questions and Answers] saciorlux:
is there any custom recovery to install on this tablet?
[General Questions and Answers] fipsy:
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.

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 ----------

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
[General Questions and Answers] Omegadrive:
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?
[General Questions and Answers] fipsy:
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...
[General Questions and Answers] fipsy:
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...
[General Questions and Answers] Sparkrite:
SU Binary Details:-

Size: 93.66KB (95,912 Bytes)

Permissions: -rwsr-sr-x

Modified: 1 Aug 2008 13:00

MD5: b24b18194c1a2f1461e273a035684a78
[General Questions and Answers] fipsy:
So my assumption was correct. This is not the su binary 3.1.1 but a custom version from the manufacturer. The 3.1.1 has a size of 380,532 bytes. It's so much more astonishing that it works anyway with the superuser app. :eek:
[General Questions and Answers] pedropep:
I am from Spain. I have updated to 4.2, after it, I have rooted it with an automatic method, and finally I have installed the CWM recovery successfully. I have got fipsy recovery file put in both cards.
[General Questions and Answers] piaaf31:
Hello,

First I'd like to thank all developers for their great work.

Since I have my tab, I already had to do two factory resets to solve issues.

First, the screen turned black and I often had to press power button for a long time to have it restart.

A few days later, at boot, the screen was stuck on hannspree logo.

I have a few questions :

-Do you think a custom ROM will be able to solve these problems ?

Can you still get the update jb 4.2.2 ?

It seems to be no longer available for me. It was available to download this morning, but after a factory reset, I can no longer see it...

Thank you for your answers...
[General Questions and Answers] fipsy:
Have all partitions been backed up? Should be six:

recovery

boot

system

data

cache

android_secure
[General Questions and Answers] Sparkrite:
Did you check to see that you are still on 4.1.1 and that it did not update to 4.2.2?
[General Questions and Answers] pedropep:
What do you mean to tell me?. I only want to tell you that I have installed your recovery successfully after have updated to 4.2
[General Questions and Answers] fipsy:
I had the same issue on Android 4.1.1 when I was using the "quick boot" option that corrupted the filesystem. After waiting about 10-20 minutes on the HANNspree-Logo (system-check) the tablet comes back again but a lot of memory will be lost. So on Android 4.1.1 you must not use quick boot! I don't know if this issue still exists on android 4.2.2. Would have to test it...

Probably it will. But I don't know if anyone will sometime bother to make a custom ROM.

Your factory reset should have restored the 4.2.2. So it's no wonder that you can't see it as an update, right?

---------- Post added at 07:32 PM ---------- Previous post was at 07:29 PM ----------

Okay. I thought you also made a backup with my recovery. :)

Would be nice to know if that works fine...
[General Questions and Answers] piaaf31:
Yes, I'm still on 4.1.1 :(
[General Questions and Answers] fipsy:
Perhaps HANNspree noticed some servere errors after the rollout and so they cancelled it temporarily? Or their servers are overloaded? Don't know...
[General Questions and Answers] piaaf31:
I didn't make the update. I only checked... and the system now says he device is up to date...... with 4.1.1 :(

---------- Post added at 07:50 PM ---------- Previous post was at 07:41 PM ----------

Ok I'll wait...

I just would like to know if some people who didn't make the update yet have the same problem...
[General Questions and Answers] pedropep:
ok, all six are right
[General Questions and Answers] fipsy:
Thank you for testing! Very nice - also the tablecloth. :D
[General Questions and Answers] JimboJoe:
Thanks to everyone for the tests ! No OTA on my side in France. Maybe someone can find the OTA file in /cache ? I guess the firmware contains every language files.