Database Info

Stock 2.1 rom rooted ROM Manager won't FIX Permissions

I searched and got on IRC and can't get a fix for this. WHen i try to use the Fix permissions option in ROM Manager Premium i get the following error.
"error occurred while attempting to run privelaged commands"
I checked superuser and ROM Manager is in there so i selected "forget" then rebooted and tried "fix permissions" again. I got the promp to allow SU and then the error.
Any idea how i can fix this? Is this a bug or a isolated problem?

Not sure if it is related or not but I had to same problem until I bought the full version off of the market.
Maybe it's part of the extended functionality?

As I noted I have "Rom Manager Premium" I don't think it's related anyway.

Just found the answer to this (as I too was having this problem). See the link below:
http://androidforums.com/899973-post26.html
It has to do with busybox not installed in the correct place.
One more thing: Make sure that busbox is set to "755" so that it can execute.

Thanks
sw99 said:
Just found the answer to this (as I too was having this problem). See the link below:
http://androidforums.com/899973-post26.html
It has to do with busybox not installed in the correct place.
One more thing: Make sure that busbox is set to "755" so that it can execute.
Click to expand...
Click to collapse
Thanks for the link to the fix!

I am unable to get the busybox file to copy from the /data.... directory into the /system/bin/ directory. Any ideas?

jtoole1 said:
I am unable to get the busybox file to copy from the /data.... directory into the /system/bin/ directory. Any ideas?
Click to expand...
Click to collapse
did you mount the system partition prior to trying this?

I'm also having an issue moving the file using root explorer. Any other ideas?

the_grobe said:
I'm also having an issue moving the file using root explorer. Any other ideas?
Click to expand...
Click to collapse
Yeah, same here. My problem is that I've never used Root Explorer before. At the top it says mounted as r/w (in the /system/bin directory) , but it won't copy the file using the Root Explorer program. When I click [Paste] it doesn't give me an error, but when I go and check the directory, the file is not there. I even tried refresh. Any ideas?
UPDATE: I have not solved the problem yet, but I did notice that the /system/bin directory that I am trying to copy to says "0K bytes available," which is probably why it won't copy. So I guess my (no copy) problem is due to my lack of understanding of the file structure of the DI.

UPDATE: I finally got it working. Here is what I did.
1. Boot phone into recovery
2. Push busybox from /sdk/tools folder to sdcard
Code:
adb push busybox /sdcard/busybox
adb shell
3. Installed busybox to /system/xbin
Code:
$ su
#export PATH=$PATH:/system/bin
#cd /system/xbin
# cat /sdcard/busybox > busybox
# chmod 06755 busybox
# busybox --install -s /system/xbin
# rm /sdcard/busybox
# exit
$ exit
4. Booted up phone, and ROM manager fixed permissions as per request.
Hope that helps.

Thanks. I appreciate your feedback. But it looks like I wasted my money again on a useless program like "Root Explorer." I was hoping that I wouldn't have to do all of that command line crap anymore after having rooted.
Does anyone know if there is a file manager out there that will push/pull files via cut/paste rather than using a seperate computer with a command line interface?

I don't think that there is going to be a program like that until we've got full NAND unlock.

the_grobe said:
I don't think that there is going to be a program like that until we've got full NAND unlock.
Click to expand...
Click to collapse
Is someone working on that? I believe the facts are, that the Unrevoked team knows how to do it...but they won't give us the means to do it. Probably because they think we'll shoot ourselves in the foot...and blame them...and they're probably right!

I can not do the cat command it tels me Cant create busybox, read only file system.
Any ideas????????????????

when i was modding widget locker i was using linda file manager free to cut and paste out of the system folder im gonna try it right now to fix this problem ill let u know if it works

[Q] how to edit GPS.conf in system folder ?

I would like to set my phone to europe.pool.ntp.org becouse it's default northamerica.pool.ntp.org
How can I edit this file ? When I try to type adb shell to terminal it gives me an error message.
Thanks
Not development related moved to General

At first U must root R phone and then install Root Explorer. After that go to SYSTEM/ETC/
Here u need to edit GPS.CONF file and change NTP Server from northamerica.pool.ntp.org to europe.pool.ntp.org.
I hope that I help U m8.

Get write acces in system folder
I used the post I've quoted down here. After you have gained write acces in the system folder you can edit gps.conf!
octy said:
By default the /system is mounted in read-only mode.
With 'root' access you can change this.
First 'root' your phone with tutorial 'slumpolo' has provided at
the begining of this thread.
Then open a shell on your phone with adb
Code:
adb shell
Grant 'root' access with 'su' command and have a look of memory partitions
Code:
su
mount
In 'mount' command output, identify the partition on which /system was mounted.
In my phone it was '/dev/block/stl6'
Finally you can remount it to get read-write permissions on it.
But before be sure to be outside /system in the shell (by typing 'cd /' for example).
Code:
mount -o remount,rw /dev/block/stl6 /system
Do the modification you want..... BECAREFUL of want you do, you can damage your phone.
Set read-only mode again
Code:
mount -o remount,ro /dev/block/stl6 /system
Sorry I cannot made any snapshot for the moment, I can't use my phone.
Hope it can help you.
Click to expand...
Click to collapse

By the way, for Slovakia I think you can better change to sk.pool.ntp.org
Complete list of European NTP servers:
http://www.pool.ntp.org/zone/europe
Other area's:
http://support.ntp.org/bin/view/Servers/NTPPoolServers

LeoApollo said:
By the way, for Slovakia I think you can better change to sk.pool.ntp.org
Complete list of European NTP servers:
http://www.pool.ntp.org/zone/europe
Other area's:
http://support.ntp.org/bin/view/Servers/NTPPoolServers
Click to expand...
Click to collapse
I see, probably I can use also CZ, HU, AT, DE or SK or EU .. I've red that the best is with more sites.
"After you have gained write acces " How can I gain write access ? I have rooted - but Adb shell doesn't work, did I missed something ? Thaks

nastyba said:
"After you have gained write acces " How can I gain write access ? I have rooted - but Adb shell doesn't work, did I missed something ? Thaks
Click to expand...
Click to collapse
i think yes adb is for the PC. it is part of the android sdk tools.

i did that on my desire (it should be same) but i have problem i edit and save file and now i cant see it
i can see that backup file but how do i restore it?
i tried create new file it wont work i cant see it (it says file created sucessfuly)

aantdesign said:
At first U must root R phone and then install Root Explorer. After that go to SYSTEM/ETC/
Here u need to edit GPS.CONF file and change NTP Server from northamerica.pool.ntp.org to europe.pool.ntp.org.
I hope that I help U m8.
Click to expand...
Click to collapse
U can use adb on Win or linux or qtadb.
Give these commands on adb shell..
su
mount -o remount,rw /dev/block/stl6 /system
exit
exit
adb pull /system/etc/gps.conf
Edit the gps.conf the way u like.
Then mount again in rw mode.
adb push gps.conf /system/etc/gps.conf
adb reboot
Done.

moved
new post @sgs2

nastyba said:
I would like to set my phone to europe.pool.ntp.org becouse it's default northamerica.pool.ntp.org
How can I edit this file ? When I try to type adb shell to terminal it gives me an error message.
Thanks
Not development related moved to General
Click to expand...
Click to collapse
U can use the apo "FasterFix" from market.

arunmcops said:
U can use the apo "FasterFix" from market.
Click to expand...
Click to collapse
Thanks for the tip much easier to change with this application done in seconds

[FOR CHEFS] xpad/cifs/hfs/squashfs/btrfs modules for stock kernel ICS v9.2.1.11

I took a vanilla 2.6.39.4 linux source tree, copied in the .config from /proc from my running ICS v9 build. And compiled it.
After that, turned on CIFS and XPAD support in the config and compiled them as modules.
These modules load fine if I insmod them, and I can confirm that after loading ff_memless and xpad I now have my xbox360 pad working on the home screen (I can move through screens and icons).
edit: Just played a round of Riptide GP, works fine .
edit: I updated the cifs module and included the md4 crypto module, and they now work! I manually 'insmodded' md4.ko and then cifs.ko, and from the command line and / or from cifsmanger I can now mount a share.
As I said, these modules load fine, but in dmesg there is a notion that the version magic isn't perfect yet. So I might make updated ones with proper versionmagic set. But for now it seems to be working.
Might be handy for ROM chefs who are working with the stock ICS kernel for which we have no sources yet.
TUN module is _builtin_ by default on ICS stock kernel, so no need for it anymore.
EDIT v2 zips: I recompiled them with the correct version info, so they give no more warnings when loaded through insmod. I added them to my stock rom to auto-load during boot (created a simple /system/etc/install-recovery.sh) and all seems fine so far.
For voodoo sound to work, is it a simple module which I can get anywhere? I only see 2.6.36 kernel trees on Project Voodoo website
----------------------------------------------------------
hfs @ http://forum.xda-developers.com/showpost.php?p=23018909&postcount=19
squashfs + btrfs @ http://forum.xda-developers.com/showpost.php?p=23019453&postcount=20

good for those complaining about cifs

dipje said:
I took a vanilla 2.6.39.4 linux source tree, copied in the .config from /proc from my running ICS v9 build. And compiled it.
After that, turned on CIFS and XPAD support in the config and compiled them as modules.
These modules load fine if I insmod them, and I can confirm that after loading ff_memless and xpad I now have my xbox360 pad working on the home screen (I can move through screens and icons).
edit: Just played a round of Riptide GP, works fine .
edit: I updated the cifs module and included the md4 crypto module, and they now work! I manually 'insmodded' md4.ko and then cifs.ko, and from the command line and / or from cifsmanger I can now mount a share.
As I said, these modules load fine, but in dmesg there is a notion that the version magic isn't perfect yet. So I might make updated ones with proper versionmagic set. But for now it seems to be working.
Might be handy for ROM chefs who are working with the stock ICS kernel for which we have no sources yet.
TUN module is _builtin_ by default on ICS stock kernel, so no need for it anymore.
For voodoo sound to work, is it a simple module which I can get anywhere? I only see 2.6.36 kernel trees on Project Voodoo website
Click to expand...
Click to collapse
in case you want to try that too because its faster than cifs
nfs support is in the kernel, no additional modules required
to get it working with cifsmanager mountings nfs shares i did the following
(it also works with commandline)
### as su and /system readwrite mounted
### remove symlink to toolbox
rm /system/bin/mount
### and use busybox instead
ln -s /system/xbin/busybox /system/bin/mount
mount options: rw,intr,soft,nolock

the modules are already working.
NFS support is nice for people with linux boxes but most windows users don't have a use for it , that's why they want cifs .
I don't care much for overclocking, so with cifs support + xbox360 support I'm more than happy with rooted stock now . And rom chefs can include the modules in their optimized ROMs until we have proper kernel source

Care to share how to get this loaded into the current ics roms. I have copied to /system/lib/modules and tried to load using mount manager and cifs manager with no luck.

comfort69 said:
Care to share how to get this loaded into the current ics roms. I have copied to /system/lib/modules and tried to load using mount manager and cifs manager with no luck.
Click to expand...
Click to collapse
you can e.g. create a script (like I believe OP did) in /etc/system/install-recovery.sh with
#!/system/bin/sh
insmod cifs.ko
insmod md4.ko
or you can mount it by hand in terminal (with insmod)

or you can simply create init.d script and call it 91modules:
#!/system/bin/sh
sleep 1
insmod /system/lib/modules/cifs.ko
echo "CIFS support activated";
and place it in system/etc/init.d if custom ROM supports init.d support.

comfort69 said:
Care to share how to get this loaded into the current ics roms. I have copied to /system/lib/modules and tried to load using mount manager and cifs manager with no luck.
Click to expand...
Click to collapse
jerry was close. Module auto-loading won't work, so you have to do it by hand.
Through an 'adb shell' or with a terminal emulator app from the market, type the following:
su -
insmod /system/lib/modules/md4.ko
insmod /system/lib/modules/cifs.ko
cifsmanager should work, until you reboot, you'll have to do the lines again.
Creating a file /system/etc/install-recovery.sh will do it auto on boot:
Code:
#!/system/bin/sh
insmod /system/lib/modules/md4.ko
insmod /system/lib/modules/cifs.ko
Make sure to create the file executable (permissions 777 will do ).
I hope rom chefs will use them and make them auto-load at boot until we have the sources from Asus.
edit: What mike said works, IF you have init.d support. Most custom ROMs have this, stock rom has not I believe.

dipje said:
jerry was close. Module auto-loading won't work, so you have to do it by hand.
Through an 'adb shell' or with a terminal emulator app from the market, type the following:
su -
insmod /system/lib/modules/md4.ko
insmod /system/lib/modules/cifs.ko
cifsmanager should work, until you reboot, you'll have to do the lines again.
Creating a file /system/etc/install-recovery.sh will do it auto on boot:
Code:
#!/system/bin/sh
insmod /system/lib/modules/md4.ko
insmod /system/lib/modules/cifs.ko
Make sure to create the file executable (permissions 777 will do ).
I hope rom chefs will use them and make them auto-load at boot until we have the sources from Asus.
Click to expand...
Click to collapse
Keep in mind that install-recovery.sh is executed from ramdisk (init.ventana.rc or init.rc, don't remember now) and some chefs (including me) removed that execution line. So much easier to add init.d script I think. Just a suggestion
EDIT:
yeah, for those on stock ROMs install-recovery.sh method is good, for those using custom ROMs it's better to use init.d

I tried to get it to run manually using terminal emulator and get
failed file exists
Sent from my Transformer TF101 using Tapatalk

comfort69 said:
I tried to get it to run manually using terminal emulator and get
failed file exists
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
my guess is you're trying to load them double or something.
If you give the command 'lsmod' you get a listed of loaded modules. Check if they're there or not.

Anyone got Junos working with the builtin tun.ko ?

comfort69 said:
Care to share how to get this loaded into the current ics roms. I have copied to /system/lib/modules and tried to load using mount manager and cifs manager with no luck.
Click to expand...
Click to collapse
cifsmanager - preferences:
check "load with insmod"
if its not already, adjust path to cifs.ko and other modules
btw: as rmmod tries to remove /lib/modules/cifs.ko instead of /system/lib/modules/cifs.ko there's no way to unload the module other than rebooting.

just sharing how I did manage cifs to work
I've installed Revolution HD 3.00 (ICS 4.0.3), installed CifsManager, didn't work, tried to copy cifs.ko and md4.ko in /system/lib/modules with File Expert or Root Explorer, couldn't because of a read-only system files, plugged my tablet on a PC, launched an adb session and typed:
$ adb shell
$ su
$ mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
pushed through adb cifs.ko and md4.ko in /system/lib/modules
changed the permission to 777 using File Expert
launched cifs and md4 using terminal emulator:
insmod /system/lib/modules/cifs.ko
insmod /system/lib/modules/md4.ko
in cifsmanager settings, didn't check load modules on boot and load through insmod
tried to connect my shares: succeed
Hope it will help somebody

jeanvdr said:
$ mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
hmm strange
my /system is mounted elsewhere
/dev/block/mmcblk0p1 on /system type ext4
anyway
another method without terminal (and.revol hd 3.0.0 only)
adb shell sysrw
adb push cifs.ko /system/lib/modules
adb push md4.ko /system/lib/modules
adb shell chmod 644 /system/lib/modules/*.ko
adb shell insmod /system/lib/modules/cifs.ko
adb shell insmod /system/lib/modules/md4.ko

If the modules don't cause problems, they will likely be in the next ARHD version.
Remounting goes like this: busybox mount -o remount,rw /system
Yaffs2 filesystem isn't used anymore, and 'remount ' ignores these parameters anyway .
Please keep it readable for people on stock ics, custom roms will get these modules somehow anyway.
Adb sysrw will not work without modified bootdisk AFAIK.
Wat is Janos? ? Maybe it needs more than the tun module, like crypto modules?
Btw, my tablet still working fine. Never had a Sleep of Death. Actually, never EVER had a SOD with my tablet, and I can't seem how any cifs module can cause it like some people are saying.

woti23 said:
cifsmanager - preferences:
check "load with insmod"
if its not already, adjust path to cifs.ko and other modules
Click to expand...
Click to collapse
The problem is this cifs.ko module required md4.ko, and AFAIK cifsmanager doesn't try to load it.

dipje said:
The problem is this cifs.ko module required md4.ko, and AFAIK cifsmanager doesn't try to load it.
Click to expand...
Click to collapse
actually it does, if you
check "load cifs module at start"
check "load per insmod"
fill out "path to cifs.ko":
/system/lib/modules/cifs.ko:/system/lib/modules/md4.ko:/system/lib/modules/nls_iso8859_1.ko
[email protected]:/~# >lsmod
nls_iso8859_1 3107 0 - Live 0xbf066000
cifs 218286 0 - Live 0xbf12a000
md4 3007 0 - Live 0xbf003000
it is a little work to type the pathes, and you surely are right that for most people its easier if it is loaded in the rom (init.d or somewhere else) automagically
btw: if you once compile modules again would you mind compiling the hfsplus module en passant? it should compile without any troubles and dependencies and allows manually (command line) mounting a mac os x external harddisk?

woti23 said:
btw: if you once compile modules again would you mind compiling the hfsplus module en passant? it should compile without any troubles and dependencies and allows manually (command line) mounting a mac os x external harddisk?
Click to expand...
Click to collapse
I haven't tested them (as in, didn't even try if they would load OK).
I just noticed I screwed up the vermagic again, so you'll get a warning in dmesg while loading. Should load ok though.
edit: Ok I've redone them. Proper cpu + vermagic now

And if people wanna experiment, mess with stuff:
squashfs
btrfs

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

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
Click to expand...
Click to collapse
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://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
Click to expand...
Click to collapse
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...
Click to expand...
Click to collapse
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://forum.xda-developers.com/showpost.php?p=49166546&postcount=133
Cheers, Volker
Click to expand...
Click to collapse
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
Click to expand...
Click to collapse

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
Click to expand...
Click to collapse
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 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
Click to expand...
Click to collapse
Update 3:
After trying over 20 generic rooting methods I come back defeated, 6 hours of testing and nothing. :crying:

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!

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!
Click to expand...
Click to collapse
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.

OK, kept trying and found some interesting stuff, first of all a screenshot with the tablet info:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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

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
Click to expand...
Click to collapse

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
Click to expand...
Click to collapse
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

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
Click to expand...
Click to collapse
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.

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.
Click to expand...
Click to collapse
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...

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

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...
Click to expand...
Click to collapse
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
Click to expand...
Click to collapse
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" ? ??

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
Click to expand...
Click to collapse
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.

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?
Click to expand...
Click to collapse
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:

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
Click to expand...
Click to collapse
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:

is there any custom recovery to install on this tablet?

Temil2006 said:
umm, instead of using custom drivers, why not simply use the newest android Drivers?
Click to expand...
Click to collapse
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" ? ??
Click to expand...
Click to collapse
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?
Click to expand...
Click to collapse
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

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

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

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

"No such file or directory" if tried run binary file in TWRP

I need to run a binary file, dalvikvm which located in /system/bin from TWRP terminal, but no matter what, it says, "No such file or directory found", and then I found that this is link file located another directory, I cd'd there and tried, but still the same result
I can be able to run the same file in Termux without any issues
Can anybody please help me on this?
Thanks

Hi, I think you need to mount the system partition before being able to access it. It's not mounted by default on TWRP, but when the phone is on it is (otherwise Android wouldn't work)
If you need help on how to mount partitions on TWRP, ring me (or google it, it's actually pretty simple)

Raiz said:
Hi, I think you need to mount the system partition before being able to access it. It's not mounted by default on TWRP, but when the phone is on it is (otherwise Android wouldn't work)
If you need help on how to mount partitions on TWRP, ring me (or google it, it's actually pretty simple)
Click to expand...
Click to collapse
Thanks for replying, it wasn't mounted at first, so I had mounted, still it didn't work, while some of the files in bin do work, some don't.
Then I copied the file to /sdcard and /tmp, and tried execute from these folders, still
Well, if when you're free, can you confirm if it's running on yours?
File: /system/bin/dalvikvm
Thanks once again

mizzunet said:
Thanks for replying, it wasn't mounted at first, so I had mounted, still it didn't work,
...
Thanks once again
Click to expand...
Click to collapse
I didn't found it inside, but it may be because I'm not rooted.
While searching around I've found this :
No such file or directory while running dalvikvm
I built AOSP Android and push the dalvik virtual machine in my device just to see if my built dalvik vm runs properly. I pushed it my device /opt directory but when I run dalvikvm, I get the error...
stackoverflow.com
It might get you out of trouble

Raiz said:
I didn't found it inside, but it may be because I'm not rooted.
While searching around I've found this :
No such file or directory while running dalvikvm
I built AOSP Android and push the dalvik virtual machine in my device just to see if my built dalvik vm runs properly. I pushed it my device /opt directory but when I run dalvikvm, I get the error...
stackoverflow.com
It might get you out of trouble
Click to expand...
Click to collapse
I looked into it.
I had no opt folder in root directory. So I made one, and moved dalvikvm to there and tried execute this time, it said permission denied, so I gave it chmod 755. But after that, it says "there no such file or directory".
Well, do you telegram account, so I could contact you there.
Thanks

Raiz said:
I didn't found it inside, but it may be because I'm not rooted.
While searching around I've found this :
No such file or directory while running dalvikvm
I built AOSP Android and push the dalvik virtual machine in my device just to see if my built dalvik vm runs properly. I pushed it my device /opt directory but when I run dalvikvm, I get the error...
stackoverflow.com
It might get you out of trouble
Click to expand...
Click to collapse
And even "file" binary, it says, there no file.

mizzunet said:
I looked into it.
I had no opt folder in root directory. So I made one, and moved dalvikvm to there and tried execute this time, it said permission denied, so I gave it chmod 755. But after that, it says "there no such file or directory".
Well, do you telegram account, so I could contact you there.
Thanks
Click to expand...
Click to collapse
This is really curious, tbh I'm not an expert around that subject, idk what's wrong with this binary...
Hopefully someone who knows more may help you with that. Have a nice day

This is because the binary you are trying to execute was compiled to run in the Android context, but you're trying to execute it in the TWRP one. Each binary has a path to a linker used during execution. The problem is that it refers to a linker that doesn't exist in TWRP.
Suppose we want to execte a binary file and obviously we can't:
Bash:
x00h:/ # /system/bin/awk
/sbin/sh: /system/bin/awk: No such file or directory
Let's take a look to its linker:
Bash:
x00h:/ # strings /system/bin/awk | head -n 1
/system/bin/linker64
Then, you will actually discover that it's sym linked to a linker that is available only when Android is running:
Bash:
x00h:/ # ls -ald /system/bin/linker64
lrwxr-xr-x 1 root shell 38 2009-01-01 00:00 /system/bin/linker64 -> /apex/com.android.runtime/bin/linker64
Since TWRP comes with its linker in /sbin/linker64, we can sym link it to /system/bin/linker64.
So, the hack:
Bash:
x00h:/ # mkdir -p /apex/com.android.runtime/bin/
x00h:/ # ln -s /sbin/linker /apex/com.android.runtime/bin/linker
x00h:/ # ln -s /sbin/linker64 /apex/com.android.runtime/bin/linker64
Retry, and it works:
Bash:
x00h:/ # /system/bin/awk
usage: /system/bin/awk [-F fs] [-v var=value] [-f progfile | 'prog'] [file ...]
Pray to God the TWRP's linker will be compatible and do the job (most binaries works fine), but sometimes you may get CANNOT LINK EXECUTABLE.