Related
Hey guys,
My uncle works for Motorola and gave me a prototype phone (which I believe will be called the Motorola Sage, and it's model number is MB508. This thread isn't really about that, I can't post pictures because I don't want to get anyone in trouble). This phone is an AT&T phone, complete with AT&T startup screen, uninstallable AT&T apps and of course the inability to install non-market apps. Also it's running Android 2.1.
Now, I seem to have default root access to this phone. I'm assuming the file system is very similar to that of the Backflip (which I was previously using until I received this one). From what I've read and learned from poking around in /system/etc, non-market apps are blocked by two config files. These are:
/system/etc/motorola/com.android.providers.settings/secure.mkitso
Code:
# cat secure.mkitso
cat secure.mkitso
location_providers_allowed=network,gps
wifi_on=0
data_roaming=1
bluetooth_on=0
install_non_market_apps=0
usb_mass_storage_enabled=1
and
/system/etc/motorola/com.motorola.android.providers.settings/settings.mkitso
Code:
# cat settings.mkitso
cat settings.mkitso
mms_maximum_message_size=614400
auto_scan_on_flip=true
sms_pref_key_emailgateway_num=121
Single_Digit_Dial_Enabled=True
roaming_icon=0
dun_enable=1
force_only_market_apps=1
Bluetooth_Dun_Enabled=true
mms_x_wap_profile_url=http://uaprof.motorola.com/phoneconfi/MotoMB51/profile/MotoMB511.rdf
sms_pref_key_to_email=1
Okay, now it would seem that it's a simple matter of changing the values for "force_only_market_apps" to 0, and "install_non_market_apps" to 1. I did this, and let me quickly tell you how I did it.
- Make /system writable: mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
- Copy mkitso files to sdcard
- Edit mkitso files using Notepad++, changing the values as stated above
- Copy mkitso files back to their original directories
- chmod 644 to the files in order to keep their original permissions
- Make /system read only again: mount -o remount,ro -t yaffs2 /dev/block/mtdblock4 /system
- Restart the phone
However, this did not work, as I still get the warning when I try to install a non-market app.
I was wondering if anyone had any ideas on this, as when the Backflip gets rooted this is one thing that I'm sure we would like to know.
Have you tried adb install? I've heard that works on Backflops. You could download the app to your PC,and install it using "adb install PATH/TO/APP.APK"
Thanks, I know that I can use adb to install non market apps, but I was looking at how to change this setting on the phone. Since I have root on my phone, I figured it was possible.
Check out some of these terminal apps found in /system/bin/ directory of the backflip.Maybe they will help you.
Code:
modemlog
chown
check_prereq
dumpsys
qmuxd
rild
dd
port_bridge
installd
minipadut
vmstat
vold
ioctl
mm-audio-native-test
lsmod
id
mm-adec-omxamr-test
notify
getevent
hciattach
dhcpcd
service
cat
system_server
linker
mm-vdec-omxh264-test
mm-adec-omxevrc-test
wpa_supplicant
netstat
mm-adec-omxmp3-test
ls
wipe
iwpriv
stop
log
mm-vdec-omxmp4-test
top
bt_init
app_process
kill
dumpcrash
iwspy
tcmd_engine
sleep
port-bridge
input
chmod
flash_image
wfa_dut
monkey
dmesg
umount
dalvikvm
sh
sync
ptf
mm-jpeg-dec-test
ime
diag_klog
route
ln
batch
fuel_gauge
iwlist
bugreport
insmod
hcid
svc
rmmod
servicemanager
iwgetid
debuggerd
test_diag
am
renice
applypatch
ps
watchprops
sendevent
reboot
mount
mm-adec-omxQcelp13-test
pm
start
ping
busybox
toolbox
df
touchpad
mediaserver
setconsole
loc_api_app
setprop
logwrapper
rm
dvz
hd
ifconfig
rmdir
printenv
getprop
mm-venc-omx-test
fsck_msdos
iwconfig
iftop
bt_downloader
akmd2
sdptool
disp_util
mm-aenc-omxamr-test
newfs_msdos
gzip
cmp
iwevent
mv
smd
mmclog
mknod
mm-adspsvc-test
bt_test_exec
dexopt
date
set_grp_id
i2c
tcmd_sql
recovery
dumpstate
netcfg
surfaceflinger
mkdir
dbus-daemon
mm-adec-omxaac-test
schedtest
mm-jpeg-enc-test
logcat
mm-aenc-omxaac-test
schedtop
fmradio
EDIT:Also there does not seem to be a com.android.providers.settings in /system/etc/motorola/ only com.motorola.android.providers.settings and the file located in that directory is named secure.mkitso and the market app setting is set up like this:install_non_market_apps=0
So there is a slight difference in how the devices are set up and maybe a bit less security on the backflip =)
Thanks for your suggestion, but if you read above I changed the mkitso files without any changes in the behavior of the phone .
I was thinking that since I changed the settings files and they didn't do anything, maybe they will be applied during a hard reset. I'll try that sometime this weekend and report on the results.
The reason I'm asking for help is because I believe that once the Backflip gets rooted, we will need to know how to disable this setting.
I doubt you have root unless it came already rooted (you did make up some **** about a prototype) I honestly think this wont be a hard issue to tackle or work around when root is achieved on the Lackflip...yes I did Lackflip on purpose because of how crippled it is..so spend your time ANNONYMOUSLY sending www.endgadget.com some nice shiney pics of your supposed prototype codnamed:
"Motorola Sage"
I'm not sure why you're so aggressive, Honestly77. I'm able to "su" in shell and I'm able to modify files in the /system folder, so unless I'm mistaken (which I very well might be), then I believe I have root on the phone.
It is a prototype phone for testing, so it coming rooted isn't too farfetched at all.
When the Backflip does get rooted yes, this will be an easier issue to solve, but I'm trying now. If we're able to figure it out now then no time will have to be devoted to it when the Backflip is rooted.
Alright, I just did a hard reset and it activated a menu toggle under Settings -> Applications -> "Unknown Sources: Allow install of non-Market applications" which can be checked or unchecked.
To summarize, if you have root on your phone, edit secure.mkitso and settings.mkitso and change the variables, then you need to hard reset the phone.
hey met3ora, I too have a backflop, I am currently trying to sell my soul to obtain some sort of root or even simple control over the device, I have 2 questions for you...
1: using the config files and other software availible on this forum, would it be possible to obtain a workaround to be able to install apps from sd? I'm sure you are well aware that the backflip has no memory and won't even allow market apps to be installed via sd.
my second question (its ok if you don't want to answer as we will find out soon enough)
is: the moto sage, how does it compare to the backflip? no specifics needed just, is it better?
Iv'e seen the photos of the sage that appeared a couple weeks ago and it looks good, just incase we need it you should copy the system files as I'm sure the one AT&T will give us will be on lockdown as well. Thanks!
Honestly77 said:
I doubt you have root unless it came already rooted (you did make up some **** about a prototype) I honestly think this wont be a hard issue to tackle or work around when root is achieved on the Lackflip...yes I did Lackflip on purpose because of how crippled it is..so spend your time ANNONYMOUSLY sending www.endgadget.com some nice shiney pics of your supposed prototype codnamed:
"Motorola Sage"
Click to expand...
Click to collapse
THis thread is old but it still helped me with a bravo. Thanks OP.
And to this guy above, wtf, why be such a douche? You are also clearly an idiot or you would know that engineering models always have root.
Calling the OP a liar was way out of line and you should apologize.
This is another of the projects I have done that was restricted to the Thunderbolt forum, but is actually compatible with quite a few devices, if not all. Some features only work for the Thunderbolt, but the script and application verify compatibility themselves.
I do not place any restriction on use of the script, components, or functions. All I ask is that the script is not used in the development of similar applications. Whether or not I am credited is at the discretion of the developer and their personal moral obligations. While this project does not include any GPL code, the theory is still relevant:
The GPL imparts great freedom for GPL end users. It ensures innovation is never stifled and no project is dependent upon any single developer.
Click to expand...
Click to collapse
Full Explanation / FAQs
Original Thunderbolt Thread
ScriptFusion AutoBot
Available on Twisted Sandbox and Android Market
This application will install the script, and if purchased from market, or unlocked with the Twisted Sanbox Shovel, it will also provide an online database of tweaks and scripts that can be run, or linked together and run, from directly inside the application.
DOWNLOADS:
AUTOUPDATE - Once the full package is installed, it will update itself (if needed) whenever it is launched. The only time the script alone needs to be reinstalled is when a new ROM is installed.
Busybox Binaries
http://twisted.dyndns.tv/BusyboxBin/
Right click / long click - Save as / save link
Script ONLY
Live script install
http://db.tt/u2gCqNO
Open terminal
Code:
su
bash /sdcard/location of script/speedtweak.sh fusion
This is the live equivalent of flashing ScriptFusion in recovery and would be considered a full install.
Once fully installed
Open terminal
Code:
su
speedtweak.sh
Live script removal
Open terminal
Code:
su
speedtweak.sh guilty
This is the live equivalent of flashing Guilty Verdict in recovery and would be considered a full removal.
Sent from my ADR6400L using Tapatalk
Just a quick breakdown for anyone asking "What about 98kickasskernel? Or "what about juwe RAM optimization?" "Don't they do the same thing?" In theory, sure... For RAM and sysctl values. Ever wonder why there are two versions of the 98kernel script to prevent bootloops? That is one key difference. This system doesn't just throw values at your device, or follow an "if you bootloop" methodology. Sure some things may cause loops because there is no reliable check (See odex/dalvikvm), but nothing is just hard-coded.
Another big difference is that those scripts cannot change screen density, tweak the CPU, change the scheduler, profile frequencies, and fix broken WiFi all in one run.
Complete means complete, simple as that. Customization means user determined customization, not what one developer recommends. Recommendations will help through the process, but they remain exactly that. There are no rules. Have some fun...
Sent from my ADR6400L using Tapatalk
Hi. Thanks for sharing.
I first read, re-read the OP and decided to download and try the trial app from the market: https://market.android.com/details?id=com.twisted.zero&feature=search_result. But the app just crashes every time when i try to launch(it gives the error: Data and sdcard required!). I am on custom ROM Froyo 2.2.2 with apps on ext2 using data2sd(both apps were on phone memory).
Then i re-re-read the OP and decided to try the script way first via Script Manager and then(if not lucky) via terminal. I had no luck with Script Manager(runing root mode). The script dont install and gives the errors:
wget: bad address '64.121.156.138:8080'
wget: can't connect to remote host (64.121.156.138:8080)
Unnable to chmod /system/xbin/wget: No such file
Invalid binaries. Please retry.
Edit: Checking the filesystem i see that at least one thing the script/app have done. Has deleted all my previous scripts on /system/etc/init.d and now there are 3 new files: 00twist_override, 01vdd_levels and 02sched_choice. Same files are now on /etc/init.d.
Same error with terminal emulator. Maybe i am very dumb and i miss something. What i am doing wrong?
Thanks in advance!
f1ng3r said:
Hi. Thanks for sharing.
I first read, re-read the OP and decided to download and try the trial app from the market: https://market.android.com/details?id=com.twisted.zero&feature=search_result. But the app just crashes every time when i try to launch(it gives the error: Data and sdcard required!). I am on custom ROM Froyo 2.2.2 with apps on ext2 using data2sd(both apps were on phone memory).
Then i re-re-read the OP and decided to try the script way first via Script Manager and then(if not lucky) via terminal. I had no luck with Script Manager(runing root mode). The script dont install and gives the errors:
wget: bad address '64.121.156.138:8080'
wget: can't connect to remote host (64.121.156.138:8080)
Unnable to chmod /system/xbin/wget: No such file
Invalid binaries. Please retry.
Edit: Checking the filesystem i see that at least one thing the script/app have done. Has deleted all my previous scripts on /system/etc/init.d and now there are 3 new files: 00twist_override, 01vdd_levels and 02sched_choice. Same files are now on /etc/init.d.
Same error with terminal emulator. Maybe i am very dumb and i miss something. What i am doing wrong?
Thanks in advance!
Click to expand...
Click to collapse
Your previous scripts are safe. They will be in data/data/scriptfusion if install didn't complete (in which case you may want to move them so a new install doesn't overwrite them) or in SDcard/ScriptFusion/backup
Alright, so a couple things happened all at once that caused your error, but to keep it simple... My server takes on the traffic of a corporate sized one packed into two computers. Occasionally I have to reboot. Your download happened during the 15 minutes or so it went down. Give it another try and let me know if it doesn't fix itself.
Sent from my ADR6400L using Tapatalk
twistedumbrella said:
Your previous scripts are safe. They will be in data/data/scriptfusion if install didn't complete (in which case you may want to move them so a new install doesn't overwrite them) or in SDcard/ScriptFusion/backup
Alright, so a couple things happened all at once that caused your error, but to keep it simple... My server takes on the traffic of a corporate sized one packed into two computers. Occasionally I have to reboot. Your download happened during the 15 minutes or so it went down. Give it another try and let me know if it doesn't fix itself.
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
I keep getting this error
$ export PATH=/data/local/bin:$PATH
$su
# bash /sdcard/speedtweak.sh fusion
unknown option -- cBusyBox v1.16.2androidfull (2010-08-01 14:57:25 EDT) multi-call binary.
Usage: stat [OPTIONS] FILE...
Display file (default) or filesystem status
Options:
-f Display filesystem status
-L Follow links
-t Display info in terse form
unknown option -- cBusyBox v1.16.2androidfull (2010-08-01 14:57:25 EDT) multi-call binary.
Usage: stat [OPTIONS] FILE...
Display file (default) or filesystem status
Options:
-f Display filesystem status
_ _ ...
___ \\-//` o,*,(o o)
(o o) (o o) 8(o o)(_)Ooo
ooO--(_)--Ooo-ooO--(_)--Ooo-ooO-(_)---Ooo
____ __ __ ___ ____ _____ _ _
( ___)( )( )/ __)(_ _)( _ )( \( )
)__) )(__)( \__ \ _)(_ )(_)( ) (
(__) (______)(___/(____)(_____)(_)\_)
Android user detected! Inverting reality...
cp: can't stat '/system/customize/speedtweak.sh': No such file or directory
/sdcard/speedtweak.sh: line 332: wget: command not found
chmod: speedtweak.sh: No such file or directory
unknown option -- cBusyBox v1.16.2androidfull (2010-08-01 14:57:25 EDT) multi-call binary.
AutoUpdate Complete. Restarting...
Restart by pressing <Up>, <Enter>
sh: Can't open /system/customize/speedtweak.sh
#
Sent from my GT540 using XDA Premium App
eoghan2t7 said:
I keep getting this error
$ export PATH=/data/local/bin:$PATH
$su
# bash /sdcard/speedtweak.sh fusion
unknown option -- cBusyBox v1.16.2androidfull (2010-08-01 14:57:25 EDT) multi-call binary.
Usage: stat [OPTIONS] FILE...
Display file (default) or filesystem status
Options:
-f Display filesystem status
-L Follow links
-t Display info in terse form
unknown option -- cBusyBox v1.16.2androidfull (2010-08-01 14:57:25 EDT) multi-call binary.
Usage: stat [OPTIONS] FILE...
Display file (default) or filesystem status
Options:
-f Display filesystem status
_ _ ...
___ \\-//` o,*,(o o)
(o o) (o o) 8(o o)(_)Ooo
ooO--(_)--Ooo-ooO--(_)--Ooo-ooO-(_)---Ooo
____ __ __ ___ ____ _____ _ _
( ___)( )( )/ __)(_ _)( _ )( \( )
)__) )(__)( \__ \ _)(_ )(_)( ) (
(__) (______)(___/(____)(_____)(_)\_)
Android user detected! Inverting reality...
cp: can't stat '/system/customize/speedtweak.sh': No such file or directory
/sdcard/speedtweak.sh: line 332: wget: command not found
chmod: speedtweak.sh: No such file or directory
unknown option -- cBusyBox v1.16.2androidfull (2010-08-01 14:57:25 EDT) multi-call binary.
AutoUpdate Complete. Restarting...
Restart by pressing <Up>, <Enter>
sh: Can't open /system/customize/speedtweak.sh
#
Sent from my GT540 using XDA Premium App
Click to expand...
Click to collapse
Seems wget may have corrupted. All issue reports relate to bad download ( which once it is installed don't happen) time to look into it...
Sent from my ADR6400L using Tapatalk
twistedumbrella said:
Seems wget may have corrupted. All issue reports relate to bad download ( which once it is installed don't happen) time to look into it...
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
Stupid mistake. Switched the server port on the server, but never updated the new value to the script. Download updated. Install should now update wget and proceed normally. Sorry.
Sent from my ADR6400L using Tapatalk
twistedumbrella said:
Stupid mistake. Switched the server port on the server, but never updated the new value to the script. Download updated. Install should now update wget and proceed normally. Sorry.
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
Im still getting invaild binarys error.
Sent from my GT540 using XDA Premium App
eoghan2t7 said:
Im still getting invaild binarys error.
Sent from my GT540 using XDA Premium App
Click to expand...
Click to collapse
Alright, let me look into something that might avoid having to update busybox
Sent from my ADR6400L using Tapatalk
Alright, with all the recent edits, it should work to get a system with busybox 1.6.1 and up updated and running. A lot of other scripts stay at 1.6.2, but this uses 1.9 much like newer ROMs. I plan to drop back busybox, see if all the commands work, and make that part optional, but a lot of ROMs use truncated versions, so I am still working out a failsafe.
Sent from my ADR6400L using Tapatalk
Can I have a few people do the following command and post the output? Getting a baseline for a new verify
busybox | busybox head -n 1 | busybox awk '{ print $2 }'
Sent from my ADR6400L using Tapatalk
Removed the necessity of having certain versions of busybox, but with that it is fair warning that ROMs with truncated versions will not work.
Changed up the tweak menu option to be a little easier understood. While the +/- were fully explained, on smaller text sizes they were impossible to differentiate.
Sent from my ADR6400L using Tapatalk
Removed. All good now.
I got it up and running. I have a few questions. I purchased the autobot off one of the links you provided. I got working. I made a slight yet big mistake. I was looking through the speedtweak menu and somehow changed the voltages on something by mistake. I couldn't read what was on the bottom of the terminal emulator and screwed something up good. After that, the phone was really crawling and scriptfusion wouldnt open up. I just restored my old backup and then reinstalled my new rom. I got scriptfusion back on my phone but is there supposed to be an app that takes you directly into scriptfusion? I know I can get there from the terminal emulator but i was able to click on an app before to get in. Now if I click on it, it just force closes. Second question is, if I am going to be playing around with a kernel, is it best to just back it up first before I modify? I'm on gingeritis 3D that has Ziggy's latest baked in. It would be nice if I screwed something up that I could just reflash the kernel but he doesn't have the kernel by itself floating around. It seems like the backup and restore worked. I backed it up, played around a bit and tested my results then I restored and it seemed to take the kernel back to its normal state. Is this the way I should do it? Also, can you backup more than one file at a time?
I also don't know what happened to my min/max frequencies. I now only have :
1) 192000
2) 245760
3) 368640
4) 768000
5) 806400
6) 883200
7) 960000
8) 1036800
This is all I have available. I had more before I had to reflash my rom. I'm sure its my fault. How can I get the other options back? I also have enabled swap and I can see if on there but it is not being used.
ercDROID said:
I got it up and running. I have a few questions. I purchased the autobot off one of the links you provided. I got working. I made a slight yet big mistake. I was looking through the speedtweak menu and somehow changed the voltages on something by mistake. I couldn't read what was on the bottom of the terminal emulator and screwed something up good. After that, the phone was really crawling and scriptfusion wouldnt open up. I just restored my old backup and then reinstalled my new rom. I got scriptfusion back on my phone but is there supposed to be an app that takes you directly into scriptfusion? I know I can get there from the terminal emulator but i was able to click on an app before to get in. Now if I click on it, it just force closes. Second question is, if I am going to be playing around with a kernel, is it best to just back it up first before I modify? I'm on gingeritis 3D that has Ziggy's latest baked in. It would be nice if I screwed something up that I could just reflash the kernel but he doesn't have the kernel by itself floating around. It seems like the backup and restore worked. I backed it up, played around a bit and tested my results then I restored and it seemed to take the kernel back to its normal state. Is this the way I should do it? Also, can you backup more than one file at a time?
I also don't know what happened to my min/max frequencies. I now only have :
1) 192000
2) 245760
3) 368640
4) 768000
5) 806400
6) 883200
7) 960000
8) 1036800
This is all I have available. I had more before I had to reflash my rom. I'm sure its my fault. How can I get the other options back? I also have enabled swap and I can see if on there but it is not being used.
Click to expand...
Click to collapse
From everything you said, it sounds like the restore may have given you a different kernel. The kernel frequencies are read right from system. The force close should fix itself by clearing data for the app and letting it reinstall the script. You don't necessarily need to back up anything if you are near a computer because the kernel itself is never actually edited. Restore is as easy as using adb to remove /system/init.e/00twist_override Editing on the go, a recent backup of system only will revert any changes. If you enabled swap and your getting zeros either you need to reboot or the system hasn't needed the space yet.
Sent from my ADR6400L using Tapatalk
Wow that's one intense script.
It's a huge compliment you gave me when you said I motivated you in some way.
Thanks man... I'm practically speechless
zeppelinrox said:
Wow that's one intense script.
It's a huge compliment you gave me when you said I motivated you in some way.
Thanks man... I'm practically speechless
Click to expand...
Click to collapse
Thanks. It was very true. Reading over your work made me realize I was focusing too much on single items and not the whole process.
Sent from my ADR6400L using Tapatalk
Well... looks like you did it in spades
Lots of ideas floating around. New concepts for better cooperation between the app and the script. Better methods for quick scripts. New menus and graphic interface plans. It's slowly building up.
Sent from my ADR6400L using Tapatalk
This is for CyanogenMod and its derivates. Stock ROMs should be fine.
If you are inrested in editing your MAC address, there's a guide linked below. I don't know if stock ROMs will automcatically correct the MAC. In this case I think you have to edit /efs/imei/.nvmac.info (read more something about /efs before playing with it!)
Click to expand...
Click to collapse
The easiest way to do the calibration is:
Turn wifi ON and run
Code:
tiwlan_plts -n
This is the script called from a oneshot init service in my init.latona.rc if someone is interested. It will calibrate and correct the MAC automatically, even after a data wipe:
Code:
#!/system/bin/sh
if [ ! -f /data/misc/wifi/nvs_map.bin ]; then
insmod /system/lib/modules/tiwlan_drv.ko
/system/bin/tiwlan_loader -i /system/etc/wifi/tiwlan.ini -f /system/etc/wifi/firmware.bin
/system/bin/tiwlan_plts -n
rmmod tiwlan_drv
fi
____________________________________
Older method
Click to expand...
Click to collapse
UPDATE: I found an easy way to get the real MAC.
Download the apk attached or run the following commands:
Code:
su
mount -o remount,rw /system
ln -s /system/lib/modules/tiwlan_drv.ko /system/etc/wifi/tiwlan_drv.ko
#Make sure wifi is off
./mfgloader -l #Take the binary from a stock ROM
./mfgloader -u
rm /system/etc/wifi/tiwlan_drv.ko
mount -o remount,ro /system
After that your MAC address shoud begin with D0:C1:B1 and not 08:00:28.
To see your current MAC: System Settings > About phone > Status (turn wifi on)
Click to expand...
Click to collapse
____________________________________
This is the first post with some more informations about the calibration
Click to expand...
Click to collapse
While I was reading some logs, I noticed these lines
Code:
TIWLAN: 1089.979242: Starting to process NVS...
TIWLAN: 1089.983698: No Nvs, Setting default MAC address
TIWLAN: 1089.989007: pHwInit->uEEPROMCurLen: 1c
TIWLAN: 1089.993462: ERROR: If you are not calibating the device, you will soon get errors !!!
...
TIWLAN: 1094.726827: Station ID : 08-00-28-12-03-58
...
You can see that the device is not calibrated and that the default MAC address is assigned.
Each device should have a unique MAC address, two devices with the same MAC address in the same network will give problems.
________
UPDATE
I made two flashable files:
wlan_calibration.zip will only do the calibration
wlan_calibration_rand.zip will do the calibration and will randomize the last three octets of the address
Click to expand...
Click to collapse
If you still want to do it on your own, here the guide:
_______________
WLAN Calibration
Here the steps you need to follow (taken from: WLAN Calibration):
1) Turn wifi off
2) From ADB/terminal emulator run the following commands [1]:
Code:
$ su
# cd /data/misc/wifi
# insmod /system/lib/modules/tiwlan_drv.ko
# start wlan_loader
# ifconfig tiwlan0 up
# tiwlan_cu -b
/ w p 1 l 2 f 2
/ t b v 21
/ t b t 1 0 0 0 0 0 0 0
/ q
# rmmod tiwlan_drv
This will create this file: /data/misc/wifi/nvs_map.bin. If it's not there, you did something wrong.
After that you should not get the error while turning wifi ON.
________
MAC address fix
Even after the calibration, you'll still have the default MAC address (Station ID : 08-00-28-12-03-58). But no problem, you can 'easly' change it: Editing the MAC Address.
You need to get the newly created /data/misc/wifi/nvs_map.bin and edit it with an hex editor as described in the guide linked above.
I still don't know if the calibration will improve anything, but it surely won't hurt:
For optimal Wi-Fi performance it is mandatory to calibrate the Wi-Fi hardware
Click to expand...
Click to collapse
NOTE: nvs_map.bin is in /data, so if you do a factory reset you have to do this again.
___
[1]
ADB: System settings > Developers options (ON) > Root access > Apps and ADB
Wow...good solution buddy. I think u shouldpost this in development thread. People dont look much in general thread.
this should be added to the cm9/10 instalation .zip file
I did flash the zip file, ran the other commands thru terminal and see the file /data/misc/wifi/nvs_map.bin.
I don't understand the next step to be done.
I cannot open the bin file using hexeditor, I gave it root access.
And, in case i open it what mac address should i use? Is some address hard coded to each phone?
Hetalk said:
I did flash the zip file, ran the other commands thru terminal and see the file /data/misc/wifi/nvs_map.bin.
I don't understand the next step to be done.
I cannot open the bin file using hexeditor, I gave it root access.
And, in case i open it what mac address should i use? Is some address hard coded to each phone?
Click to expand...
Click to collapse
I don't know how MAC are assigned, I simply randomized the last part of the address (I kept the first part: 80:00:28).
Anyway I just uploaded a new zip file to make things even simpler. It will automatically randomize the last four three groups. If you want to use it, you need to delete /data/misc/wifi/nvs_map.bin first. EDIT: I changed the script, now you can do the calibration without removing the file.
Anyway I don't know what's wrong with your editor, I did it from my computer.
I tried using hex editor from play store.
I'll try the new zip tomorrow..
As I wrote in the OP, today I found the way to get the original MAC.
I don't know what is needed to make the commands work while in recovery (services needed etc...), so I made a dummy app (I simply adapted the code of an app I made few days ago to do a similar thing).
No fancy icon (it's the default one), no checks, ugly etc... It simply does the job (my Java knowledge is almost zero)
EDIT:
I almost forgot to say that the real MAC is in /efs/imei/.nvmac.info. It was the first place where I looked, but it's an hidden file an I didn't see at first.
bam....
Dear @loSconosciuto
I following this guide to solve the problem that actually I have in my phone with CM 11. In the Status menu, "non available" appears in my device WIFI mac. I following the guide step by step and I couldn't change it.
Could you help me?
carniman78 said:
Dear @loSconosciuto
I following this guide to solve the problem that actually I have in my phone with CM 11. In the Status menu, "non available" appears in my device WIFI mac. I following the guide step by step and I couldn't change it.
Could you help me?
Click to expand...
Click to collapse
This guide is for the kernel 2.6.35 which uses a completely different driver, it's quite an old thread. The calibration is done in a different way and I don't think that's the problem.
I'm not using CM11, so it's quite hard for me to know exactly what's wrong.
loSconosciuto said:
This guide is for the kernel 2.6.35 which uses a completely different driver, it's quite an old thread. The calibration is done in a different way and I don't think that's the problem.
I'm not using CM11, so it's quite hard for me to know exactly what's wrong.
Click to expand...
Click to collapse
Ok, sir. Thank you for your help.
Hi there
trying to fix Samsung s4 active i9295 wifi problem. at least got the MAC address showing (was 02:lots of zeroes) still unable to start wifi. is there anything else I should search for? tiwlan_drv.ko was not there so I downloaded it sepparately. do I need some more modules to be added? using stock 4 file engineering FW Android 5.0.1
Any suggestions on how to regain root after the OTA ICS update using Linux? I've read through various posts scattered about the innerwebs regarding how using Windows but I'm a stubborn Linux user. I've downloaded the A2_ICS_Root Zip and explored the contents but not sure how to properly utilize them. I've rooted the phone in the past manually using Android SDK, Linux Terminal, push/adb shell commands and Motofail but of course lost root with the ICS update. If I don't get an answer I may attempt to follow some of the scripting used for Droid/Razors post ICS, of course tailored a bit. Although my Superuser app is still showing it's pretty much useless, like others with the same issue I've read about, it's still written into the system but no longer rooted. I've tested phone access in terminal but get the R/W error message ... no permission, etc. So ... I thought maybe folks here may have an answer for us semi skilled Linux users.
You should be able to just run the root.bat if you have the folder with all contents extracted to desktop.
Sent from my MB865 using xda premium
Aimless Rambler said:
Any suggestions on how to regain root after the OTA ICS update using Linux? I've read through various posts scattered about the innerwebs regarding how using Windows but I'm a stubborn Linux user. I've downloaded the A2_ICS_Root Zip and explored the contents but not sure how to properly utilize them. I've rooted the phone in the past manually using Android SDK, Linux Terminal, push/adb shell commands and Motofail but of course lost root with the ICS update. If I don't get an answer I may attempt to follow some of the scripting used for Droid/Razors post ICS, of course tailored a bit. Although my Superuser app is still showing it's pretty much useless, like others with the same issue I've read about, it's still written into the system but no longer rooted. I've tested phone access in terminal but get the R/W error message ... no permission, etc. So ... I thought maybe folks here may have an answer for us semi skilled Linux users.
Click to expand...
Click to collapse
Use the process and scripts I created for the leak/OTA. All you need to do is step 6 in the following link, and use the shell not the bat as others noted... if you are running linux, I am sure you already knew that.
Link:
http://forum.xda-developers.com/showthread.php?t=1779968
6) Boot into ICS, and root using the zip below, you will connect the phone to your computer and use the root.bat (unzip this folder to your desktop) for windows and root.sh for linux/mac.
The script and root files:
http://www.androidfilehost.com/main/Motorola_ATRIX_2_Developers/jimbridgman/A2_ICS_root.zip
Re-Rooted!
jimbridgman said:
Use the process and scripts I created for the leak/OTA. All you need to do is step 6 in the following link, and use the shell not the bat as others noted... if you are running linux, I am sure you already knew that.
Link:
http://forum.xda-developers.com/showthread.php?t=1779968
6) Boot into ICS, and root using the zip below, you will connect the phone to your computer and use the root.bat (unzip this folder to your desktop) for windows and root.sh for linux/mac.
The script and root files:
http://www.androidfilehost.com/main/Motorola_ATRIX_2_Developers/jimbridgman/A2_ICS_root.zip
Click to expand...
Click to collapse
Thanks Jim! I actually figured it out on my own, of course using the same zip file you provided which I had found in another thread.
I extracted the file into it's own folder, put the phone into debug mode and made sure MTP (media device) was checked, hooked to USB then ran a few checks in Terminal to make sure the device was recognized. Then I dragged "a2_ics_root.sh" into the open Terminal window and let it do its thing. I already had Superuser installed in earlier root (prior to ICS) so maybe that's why I got the "cannot stat 'su': No such file or directory cannot stat 'Superuser.apk': No such file or directory" error but then it said "You are rooted!". So to check to make sure I was actually rooted I ran the adb shell command and got this "[email protected]:/ $" then entered su, and got this "[email protected]:/ #"
Success!!
Hmm
Aimless Rambler said:
Thanks Jim! I actually figured it out on my own, of course using the same zip file you provided which I had found in another thread.
I extracted the file into it's own folder, put the phone into debug mode and made sure MTP (media device) was checked, hooked to USB then ran a few checks in Terminal to make sure the device was recognized. Then I dragged "a2_ics_root.sh" into the open Terminal window and let it do its thing. I already had Superuser installed in earlier root (prior to ICS) so maybe that's why I got the "cannot stat 'su': No such file or directory cannot stat 'Superuser.apk': No such file or directory" error but then it said "You are rooted!". So to check to make sure I was actually rooted I ran the adb shell command and got this "[email protected]:/ $" then entered su, and got this "[email protected]:/ #"
Success!!
Click to expand...
Click to collapse
Well I don't have root after all? Once unplugged from computer I ran a terminal emulator app on the phone and tried to access root but it says I don't have permission, as well as a few other apps I tried to install. Strangeness. As it looks above in quote is it just a temporary root? One thing I did notice after the OTA ICS update is that the superuser app remained. I tried a factory data reset thinking it would take it off but it didn't. Is my original rooting (GB Motofail) SU somehow stuck in perpetuity within some system file somewhere which is fouling up this root? So how would I go about a clean install of Superuser? I updated Superuser on Play Store but no difference. Hmm
update on strange problem
Aimless Rambler said:
Well I don't have root after all? Once unplugged from computer I ran a terminal emulator app on the phone and tried to access root but it says I don't have permission, as well as a few other apps I tried to install. Strangeness. As it looks above in quote is it just a temporary root? One thing I did notice after the OTA ICS update is that the superuser app remained. I tried a factory data reset thinking it would take it off but it didn't. Is my original rooting (GB Motofail) SU somehow stuck in perpetuity within some system file somewhere which is fouling up this root? So how would I go about a clean install of Superuser? I updated Superuser on Play Store but no difference. Hmm
Click to expand...
Click to collapse
First of all I apologize for all this confusion with replies to my own questions but I don't know any other way to relay the information. I'm troubleshooting as I go and hope it helps define what the issue may be and maybe a fix haha! Okay!! So I get root access easy as pie in terminal, no issues whatsoever, so I did a little searching and this is what I've found. The problem seems to be su is listed twice within my system folder (see below).
PROBLEM
[email protected]:/system/app # ls
Superuser.apk <<< is listed in the right location
# cd ..
[email protected]:/system #
[email protected]:/system/bin #
su <<< is listed here
[email protected]:/system/xbin #
su <<< is also listed here?
That can't be right? Shouldn't it only be in the /bin folder? Having downloaded the A2 ICS Root zip file I explored the Windows root.bat file in a text editor and saw that SU is suppose to install to /bin. So how the heck did it get in 2 different locations? ha!!! I'm guessing this would cause some issue but before I go deleting the extra file I thought I should inquire first. Haha!
Doh!!!! I know it's got to be something I did!
Aimless Rambler said:
First of all I apologize for all this confusion with replies to my own questions but I don't know any other way to relay the information. I'm troubleshooting as I go and hope it helps define what the issue may be and maybe a fix haha! Okay!! So I get root access easy as pie in terminal, no issues whatsoever, so I did a little searching and this is what I've found. The problem seems to be su is listed twice within my system folder (see below).
PROBLEM
[email protected]:/system/app # ls
Superuser.apk <<< is listed in the right location
# cd ..
[email protected]:/system #
[email protected]:/system/bin #
su <<< is listed here
[email protected]:/system/xbin #
su <<< is also listed here?
That can't be right? Shouldn't it only be in the /bin folder? Having downloaded the A2 ICS Root zip file I explored the Windows root.bat file in a text editor and saw that SU is suppose to install to /bin. So how the heck did it get in 2 different locations? ha!!! I'm guessing this would cause some issue but before I go deleting the extra file I thought I should inquire first. Haha!
Doh!!!! I know it's got to be something I did!
Click to expand...
Click to collapse
That is completely correct. The su in /system/xbin is a link to /system/bin/su. And that is correct, and how it should be.
Please explain your issue in more detail as I am not fully understanding what is not working.
Rooted again??
jimbridgman said:
That is completely correct. The su in /system/xbin is a link to /system/bin/su. And that is correct, and how it should be.
Please explain your issue in more detail as I am not fully understanding what is not working.
Click to expand...
Click to collapse
The issue was my phone was not actually rooted after running a2_ics_root.sh in Terminal (computer). I got the "cannot stat 'su': No such file or directory cannot stat 'Superuser.apk': No such file or directory" error message in terminal and also checked root by running a terminal emulator app within the phone and received the no permission message after entering su at the prompt. Once I reconnected the phone to the computer and ran the sh file again I gained temporary root. That's when I noticed su was in two different locations as I mentioned above and you subsequently replied was normal. Of course before I saw your response I had already removed (rm command) the extra su ha! After removing the su file from /xbin it alone did not fix the problem. I still could not access root. So I reran the a2_ics_root.sh in terminal (computer) and got root with no error messages and verified it with my phone's terminal app (also got the Superuser root access permission check, which I hadn't got before). No idea why this worked if su was suppose to be in two locations. As I was in the phones terminal emulator app I checked the /xbin folder and did not see it reappear yet it all seems rooted now! Ha! Gosh my brain hurts.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
remount succeeded
492 KB/s (22372 bytes in 0.044s)
3434 KB/s (397229 bytes in 0.112s)
You are rooted!
Aimless Rambler said:
The issue was my phone was not actually rooted after running a2_ics_root.sh in Terminal (computer). I got the "cannot stat 'su': No such file or directory cannot stat 'Superuser.apk': No such file or directory" error message in terminal and also checked root by running a terminal emulator app within the phone and received the no permission message after entering su at the prompt. Once I reconnected the phone to the computer and ran the sh file again I gained temporary root. That's when I noticed su was in two different locations as I mentioned above and you subsequently replied was normal. Of course before I saw your response I had already removed (rm command) the extra su ha! After removing the su file from /xbin I reran the a2_ics_root.sh in terminal (computer) and got root with no error messages and verified it with my phone's terminal app (also got the Superuser root access permission check, which I hadn't got before). No idea why this worked if su was suppose to be in two locations. As I was in the phones terminal emulator app I checked the /xbin folder and did not see it reappear yet it all seems rooted now! Ha! Gosh my brain hurts.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
remount succeeded
492 KB/s (22372 bytes in 0.044s)
3434 KB/s (397229 bytes in 0.112s)
You are rooted!
Click to expand...
Click to collapse
Did you by chance try and use some sort of root keeper before trying to do the OTA, then had these problems after the OTA was completed?
We have seen this before, and the reason you got the stat errors is because the wrong versions of the files were in /system/bin and /system/xbin. Yeah we have found that trying to use any OTA root keepers are BAD on this phone. Motorola is so anal about updates. That is why we mention to do an fxz before doing any OTA, then using the root scripts afterwards.
If you still have any more issues you might think about using the new ICS fxz in the development section and using/redoing the script from there.
P.S. I saw that you said you dragged the script into the terminal, that is a bad way to run it, BTW.... Try and open a terminal and cd into the dir that you unzipped the script in, and then into the ics_root dir and type ./root.sh and see if that works a little better next time, that might be why you only got temp root, because it was not able to find the proper su and superuser.apk to copy over with adb, I use relative paths in the script just for ease.
jimbridgman said:
Did you by chance try and use some sort of root keeper before trying to do the OTA, then had these problems after the OTA was completed?
We have seen this before, and the reason you got the stat errors is because the wrong versions of the files were in /system/bin and /system/xbin. Yeah we have found that trying to use any OTA root keepers are BAD on this phone. Motorola is so anal about updates. That is why we mention to do an fxz before doing any OTA, then using the root scripts afterwards.
If you still have any more issues you might think about using the new ICS fxz in the development section and using/redoing the script from there.
P.S. I saw that you said you dragged the script into the terminal, that is a bad way to run it, BTW.... Try and open a terminal and cd into the dir that you unzipped the script in, and then into the ics_root dir and type ./root.sh and see if that works a little better next time, that might be why you only got temp root, because it was not able to find the proper su and superuser.apk to copy over with adb, I use relative paths in the script just for ease.
Click to expand...
Click to collapse
Thanks! I'm sure I did something to cause the troubles but can't recall exactly what it was I did wrong! My brain is getting old. Ha! But to answer your question ... other than my original root (using Motofail) I've hesitated to do anything until after the ICS update. I recently bought the phone 2nd hand to replace my Samsung Captivate so I could experiment with a Lapdock (in my line of work portability and multi-role is a plus). The phone was stock when I got it. Also, I had moved the root.sh file and superuser.apk into my Android/Platform_Tools folder which is in my system path (android rules,etc), so there was some forethought prior to dragging the script into terminal. Next time I'll 'cd it like ya recommend!
Could it be there was an issue with how I did the original GB motofail root?
In any case all seems to be good now.
Thanks again!
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...