Related
Good news for this guide:
I've done it already so you just need to download the files and follow these simple instructions:
YouTube Video of earlier stages of me running Fedora 12
0) make sure your Android Device is rooted (added so I get less nonsensical "It doesn't work!!!!!" and more "I followed everything I get an <insert error here> error! HELP!"
1) download files from http://zornco.net/androfedora/
2) extract fedora_scripts.rar and place all four files (bootfedora, unmountfedora, fedora.sh, fedora.img) in /sdcard/fedora/
3) open android terminal emulator
4) run command "su" (you might have to press allow in the Superuser App)
5) run command "cd /sdcard/fedora"
6) run command "sh fedora.sh"
7) run command "bootfedora" If that returns "not found" run "sh /sdcard/fedora/bootfedora"
8) now you're in fedora (should now see [[email protected] /]#)
OPTIONAL:
9) run "service sshd start" - to run an SSH server
P.S.: I set the root password to password
P.S.S.: I'm pretty sure it's impossible to screw up your Android OS doing this unless you terribly, terribly mess up this guide
Run the scripts and post your errors <- this will help me immensely to make this available on all Android Devices! please, thank you, and have fun!
N4melessS0ldier said:
Good news for this guide:
I've done it already so you just need to download the files and follow these simple instructions:
0) make sure your SGS4G is rooted (added so I get less nonsensical "It doesn't work!!!!!" and more "I followed everything I get an <insert error here> error! HELP!"
1) download files from http://anonymouslyacquired.info/fedoraonsgs4g/
2) place all three files in /sdcard/fedora/
3) open android terminal emulator
4) run command "su" (you might have to press allow in the Superuser App)
5) run command "sh /sdcard/fedora/fedora.sh"
6) run command "bootfedora" If that returns "not found" run "sh /sdcard/fedora/bootfedora"
7) now you're in fedora (should now see [[email protected] /]#)
8) run "startvnc" (my automated vncserver script)
AND/OR
9) run "service sshd start"
If you want to see your newly installed Fedora 12 OS:
android-vnc-client to localhost:5901 with password = password
P.S.: I set the root password to password
P.S.S.: I'm pretty sure it's impossible to screw up your Android OS doing this unless you teriibly, terribly mess up this guide
P.S.S.S: I'm running a rooted Bionix Frost SGS4G ROM with Bali KERNEL (don't think that matters but I do know being rooted matters!)
edit: apparently this isn't working for anyone but myself so far sooooo:
To Moderators: You may delete this thread and move the thread in Galaxy S 4G General: [Guide] Installing Fedora 12 on SGS4G to Galaxy S 4G Android Development (I only posted in General because I didn't have permissions to post here yet and posting here (I hope) will increase my ability to make this available to all SGS4G owners!)
Click to expand...
Click to collapse
forgive me for asking because im usually one to read to learn, but since you made this
what BENEFITS are gained from fedora?
i just dont know exactly what it is? thank you
I suppose mainly for developing. If you have fedora installed on a phone with a kernel that supports adding kernel modules and the kernel headers then you can build new modules for your phone on your phone. Also, it's sortof fun to show off, and it can potentially do some neat things (potentially aircrack-ng if it supports the WiFi device - maybe unlocking some features by allowing you to add linux tools and binaries - adding new media players - converting different media files to things accessible by Android Apps (or just playing them from Fedora) - extracting weird archives - and I'm sure if you take them time you can probably think of cool things you can do with an extremely portable, extremely customizable Linux Operating System Distribution (whether "legit" or less than))
edit: also, most things are already precompiled on a Fedora 12 ARM repo but if they aren't you can easily compile them from your phone (I suggest plugging it in and compiling/installing so you don't waste battery life (also I suggest doing that from your computer to your phone through SSH for easier typing, quicker command entering, etc.) and it may take some time depending on how overclocked the phone is)
Thanks for the explanation brotha!
sent from my sgs4g 2.3.3, finally
So I would be able to modify the frameworkres.apk and other things of that nature?
Sent from my SGH-T959V using XDA Premium App
I got it!
http://forum.xda-developers.com/showpost.php?p=8755526&postcount=7
If bootubuntu gets executed before Android loads all app2sd applications, it is possible solves the loop device busy error even with App2SD applications installed. It requires a very perfect timing, today after few experiments on my phone, I worked out a process which can always boot up Ubuntu on my phone:
1. Reboot phone
2. as soon as you enter lock screen, unlock screen
3. quickly go to terminal emulator
4. become su by typing su and enter
5. type bootubuntu and wait (type it fast... practice )
Click to expand...
Click to collapse
So apparently it's apps2sd causing this problem. I used the ubuntu guide but I'm sure fedora will work now, since it was just a mounting issue.
What I did to type this quickly was change the bootubuntu (or bootfedora in this case) script to just b so i could just do su, press enter, then b, press enter
EDIT
This means that it's possible to boot it as an init.d script to make sure it loads before the phone is done scanning the SD card. I think I'll wind up doing that... It's easier to kill the script when you don't need it than boot it when you want it.
Oh gosh, thank you so much I was just about to give up on public releases. Now that I know the problem I can fix my scripts to get arpund it. Thanks so much!
Sent from my SGH-T959V using XDA App
Just wanted to post again to express my gratitude I will definitely post a new script that will mount regardless of app2sd. Thank you! Thank you! Thank you!
Sent from my SGH-T959V using XDA App
Hey man I'm as happy as you are... Just spent the last few hours messing with ubuntu on the phone. Piece of work that is. You said fedora has sound support when booting on the phone?
Yeah I managed to get sound working.... sad part is my (granted I forgot to make a backup) version of the filesystem image became corrupt.... oops. Well, I'm buying a larger sd card in about 30 mins and I'm going to redo it so soon I'll upload the new img and scripts aswell as a kernel module for you and others using a different linux distro than fedora
Sent from my SGH-T959V using XDA App
Sounds great. Just a heads up, I was messing with the bootscript and I added the lines that mount the sdcard to the other OS's filesystem. Twice I got the phone freezing up so I did a hard reboot (battery pull) and when the phone rebooted it seems as if the /data partition got wiped (except for my background image which got saved, go figure). Weird, not even sure how that could've happened.
Very odd. If this forum has private messaging, PM me exactly what you added so I can make sure that or something more serious doesn't happen to others. Thanks
Sent from my SGH-T959V using XDA App
I just updated the script to mount whether or not you have App2SD installed on your phone.
It turns out App2SD uses a separate loop device for each app you have moved to your SD Card.
I've set the script "bootfedora" to create a "/dev/loop99"
So, unless you have 99 or more Apps moved to your SD Card it should work!
Re-download "bootfedora" from:
http://anonymouslyacquired.info/fedoraonsgs4g/
edit: currently working on new version of my Fedora 12 filesystem (should include a lot more (including working sound for a "nicer" feel) but it sucks if you have less than 2GB of freespace on your SD Card)
I'm completely in the dark when it comes to Fedora but I find it very interesting. It is going to be a Big Development for our phone I'm sure.
Wish I could help you but this is way out of my league.
I'm definitely following your progresses closely. Keep up the Great Work fellas!
Thanks
N4melessS0ldier said:
I just updated the script to mount whether or not you have App2SD installed on your phone.
It turns out App2SD uses a separate loop device for each app you have moved to your SD Card.
I've set the script "bootfedora" to create a "/dev/loop99"
So, unless you have 99 or more Apps moved to your SD Card it should work!
Re-download "bootfedora" from:
http://anonymouslyacquired.info/fedoraonsgs4g/
edit: currently working on new version of my Fedora 12 filesystem (should include a lot more (including working sound for a "nicer" feel) but it sucks if you have less than 2GB of freespace on your SD Card)
Click to expand...
Click to collapse
Alright man, I got it to boot perfectly without doing this at boot startup! Aww yeah, it's on!
One thing though, the scripts you've been posting lately have windows line endings insteads of Unix, so I had to convert them before they worked.
FBis251 said:
Alright man, I got it to boot perfectly without doing this at boot startup! Aww yeah, it's on!
One thing though, the scripts you've been posting lately have windows line endings insteads of Unix, so I had to convert them before they worked.
Click to expand...
Click to collapse
I'm not sure what I'm doing wrong but I keep getting the error
chroot: notfound
: not found
Shutting down Fedora
: not found
glt0404 said:
I'm not sure what I'm doing wrong but I keep getting the error
chroot: notfound
: not found
Shutting down Fedora
: not found
Click to expand...
Click to collapse
What rom/kernel are you using?
FBis251 said:
What rom/kernel are you using?
Click to expand...
Click to collapse
Stock rom with Bali 3.3UV
I'm pretty sure that's not the problem cause I've successfully booted Ubuntu (without gui).
Post up the whole list of commands you ran, plus the errors. Just copy the whole command line text
FBis251 said:
Post up the whole list of commands you ran, plus the errors. Just copy the whole command line text
Click to expand...
Click to collapse
This is what I got.
Code:
export PATH=/data/local/bin:$PATH
# #cd /sdcard/fedora/
# su
# sh fedora.sh
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Usage: mount [-r] [-w] [-o options] [-t type] device directory
rm failed for -f, No such file or directory
: not found
: not found
: not found
: not found
: not found
: not found
Fedora Chroot Bootloader v0.1
Fedora Bootloader is now installed!
This process does NOT damage Android OS!
Original Installer by Charan Singh
Modified for Fedora Chroot by N4melessS0ldier
To enter the Fedora Linux console just type 'bootfedora'
: not found
: not found
# sh bootfedora
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Usage: mount [-r] [-w] [-o options] [-t type] device directory
: No such file or directoryxtcard2
': Read-only file systemctory '/mnt/extcard2
'knod: invalid number '0
losetup: not found
failed: No such file or directory/extcard2
': No such file or directoryy '/mnt/extcard2/rootfs-f12
failed: No such file or directoryp1 on /mnt/extcard2/rootfs-f12
': No such file or directoryy '/mnt/extcard2/rootfs-f12
failed: No such file or directoryard2/rootfs-f12
': No such file or directoryrd2/rootfs-f12
': No such file or directoryrd2/rootfs-f12
failed: No such file or directoryrd2/rootfs-f12
failed: No such file or directoryxtcard2/rootfs-f12
failed: No such file or directoryrd2/rootfs-f12
failed: No such file or directoryrd2/rootfs-f12
Setting /etc/resolv.conf to Google Open DNS 8.8.8.8 and 8.8.4.4
: directory nonexistentte /mnt/extcard2/rootfs-f12
: directory nonexistentte /mnt/extcard2/rootfs-f12
Setting localhost on /etc/hosts
: directory nonexistentte /mnt/extcard2/rootfs-f12
Operation complete!
Courtesy N4melessS0ldier!
chroot: not found
: not found
Shutting down Fedora
: not found
#
I went on and ported from scratch (not using work done for the i9000) Ubuntu Touch for our magic samsung captivate! The port itself is just the base of CyanogenMod to be able to support the binary blobs (drivers) of various devices without having to rewrite them (source code is usually not avaliable). Mine is the i897 ATT variant.
I wanted to post the link to the rom from my google drive, but since i just registered here to post this I cannot post external links. PM me and i will send the link to you ASAP!!
Installation instructions:
1- Copy the CM_BASE_UBUNTU_TOUCH zip file to the phone (internal or external sd doesn't matter)
2- Download the latest image of Ubuntu Touch from the ubuntu website. The current filename is quantal-preinstalled-phablet-armhf.zip (This will change once the builds are based on Raring - 13.04 - and not Quantal - 12.10): PM ME FOR LINK OR SEARCH GOOGLE FOR "UBUNTU TOUCH DAILY"
3- Copy the Ubuntu Touch image to the phone
4- Reboot into recovery
5- Install CM_BASE_UBUNTU_TOUCH.zip from sd
6- Wipe Cache
7- Wipe Data partition
8- Install Ubuntu Touch zip from sd card
9- Patiently wait
10- Reboot and Enjoy!
EDIT--> Now you have the system 90% ready, but for the resolution of our device and the size of our screen we will have to change some parameters to fix the dpi and scaling:
EDIT 2 --> All these steps are unneccessary if you flash http://goo.im/devs/pawitp/galaxysmtd...x-20130223.zip after everything else. Thanks go to Citrit who pointed out the post in the i9000 ubuntu touch thread http://forum.xda-developers.com/showthread.php?t=2162534
If you want to go through how it is done, or if you want to play with the settings, follow on. If not, jump past the F.
11- While the device is on, connect to your computer via usb
12- From a terminal, run the following commands
A- adb root (necessary to be able to enter directly into a root adb shell)
B- adb shell (we are based on cyanogen, so our lovely adb commands still work)
C- ubuntu_chroot shell (to enter a linux command prompt, since ubuntu is a layer on top of the android linux kernel)
D- vi /usr/bin/ubuntu-session (edit the session configuration. I used vi but feel free to do however you like)
E- Here near the beginning you will find a series of preconfigurations for some devices and a generic one at the end: this is the one we have to edit. The GRID_UNIT_PX parameter with 18 as a value has to be changes to 11 or 12 (test and see how you like it), and the QTWEBKIT_DPR parameter with 2.0 has to be changed to 1.1 or 1.2
F- you can reboot directly from the chroot session typing "reboot" (without the quotes)
Taken from the Ubuntu Touch porting guide:
you can use adb port forwarding to easily connect to the container via SSH over USB. To do so, run the following commands:
adb forward tcp:8888 tcp:22
ssh [email protected] -p 8888
Currently the power button does not work with recent kernels, so one of the following options must be run:
remove the battery and replace it
run "reboot -p" from the adb shell
adb root
adb shell reboot -p
If you appreciate my work, leave feedback! If you don't, leave feedback! All feedback is welcome! I'd like to know your thoughts, experiences and what bugs or annoyances you encounter!
P.S If the mods could give me permission to post ouside links (or if they could post it themselves if i pm it to them) we would all be very grateful
What works and what doesnt
Sent from my SGH-I897 using xda app-developers app
What works and what doesn't
No cellular connection (no calls, no sms, no data)
Basic wifi works (password free and wpa network tested, but wep should too)
Camera works
Gpu accelleration works
All the rest is untested
but after installing it will i be able to flash back to android 4.2.2????
Reflash to android
n205des said:
but after installing it will i be able to flash back to android 4.2.2????
Click to expand...
Click to collapse
Sure! All you have to do is reboot into recovery (sending an adb command or using the usual button combination) and reflash your favourite rom from there! I tested with the nightly CyanogenMod and with SlimBean, both 4.2.2, and all went well
krissetto said:
Sure! All you have to do is reboot into recovery (sending an adb command or using the usual button combination) and reflash your favourite rom from there! I tested with the nightly CyanogenMod and with SlimBean, both 4.2.2, and all went well
Click to expand...
Click to collapse
okkkayy!
will try and tell you soon
---------- Post added at 10:01 PM ---------- Previous post was at 09:01 PM ----------
i installed it but i couldnt understand how to change the dpi or the resolution to my phones size.
so can you explain me how to do it correctly?
Adjusting dpi scaling
n205des said:
okkkayy!
will try and tell you soon
---------- Post added at 10:01 PM ---------- Previous post was at 09:01 PM ----------
i installed it but i couldnt understand how to change the dpi or the resolution to my phones size.
so can you explain me how to do it correctly?
Click to expand...
Click to collapse
What we have to do is change a couple of lines in the ubuntu-session configuration file. It is located, in ubuntu, in /usr/bin/ubuntu-session. The way i chose to edit this file was via chroot from my pc.
With the phone powered on, connect it to a computer with ADB installed (install the android sdk if you haven't, i personally use linux but you can on windows and osx too). Then from a terminal run the following commands:
adb root
adb shell
ubuntu_chroot shell
After you have inserted these commands, you will find youself in a chroot session, basically any command you now write executes on the phone as if you ran it from there. So i used a terminal text editor (vi, to be precise, but i assume you can use whatever you prefer) and opened the file with this command:
vi /usr/bin/ubuntu-session
vi was designed decades ago, for keyboards without arrow keys, so to move around read a bit on the page i PM'd you.
What you now have to do is scroll down to where you see the following code:
export GRID_UNIT_PX=18
grep -q QTWEBKIT_DPR /home/phablet/.bashrc
[ $? -ne 0 ] && echo "export QTWEBKIT_DPR=2.0" >> /home/phablet/.bashrc
export QTWEBKIT_DPR=2.0
export FORM_FACTOR="phone"
What you have to change is the 18 and the 2.0, repectively in 11 and 1.1 (play around with slightly different settings to get the feel you prefer).
Save the file and type "reboot" in the terminal.
Your phone will now restart, and load up the UI with the settings you just changed
Let me know if you have problems, when I find some time I'll get back to you
anyone?
Has anybody tried this yet?
Looks good
Everything installed fine, had no issues with that. Only issue I'm having is I can't seem to change the resolution by following the above steps. Ubuntu touch looks good though . WORKS: Wifi, Camera. Will provide more feedback once I get into it more.
Resolution scaling
mitchelldavis said:
Everything installed fine, had no issues with that. Only issue I'm having is I can't seem to change the resolution by following the above steps. Ubuntu touch looks good though . WORKS: Wifi, Camera. Will provide more feedback once I get into it more.
Click to expand...
Click to collapse
What problems do you encounter? I noticed that trying to edit the file with nano wouldn't let me save it, as if the command just wouldn't go through, but maybe that was just me.
Everything worked great for me, and the latest build fixes the need for an open Wifi. It now prompts for a password. Here is a fix for the layout, it was taken from this thread:
http://forum.xda-developers.com/showthread.php?t=2162534
Grab the file http://goo.im/devs/pawitp/galaxysmtd_ubuntu/ubuntu-aries-layout-fix-20130223.zip and install this last.
citrit said:
Everything worked great for me, and the latest build fixes the need for an open Wifi. It now prompts for a password. Here is a fix for the layout, it was taken from this thread:
http://forum.xda-developers.com/showthread.php?t=2162534
Grab the file http://goo.im/devs/pawitp/galaxysmtd_ubuntu/ubuntu-aries-layout-fix-20130223.zip and install this last.
Click to expand...
Click to collapse
An easier way to fix it, thanks! I'll edit the orig post with these instructions
When I try to edit the settings using vi it doesnt let me input anything. I get all of the information but cannot edit it.
Editing with vi
mitchelldavis said:
When I try to edit the settings using vi it doesnt let me input anything. I get all of the information but cannot edit it.
Click to expand...
Click to collapse
Have you read the information on how to use vi? There are certain commands to use to edit text, it was built for computer from ages ago, that didn't have many things we're now used to. Excuse me if you are experienced enough to know how to use vi ^^
mitchelldavis said:
When I try to edit the settings using vi it doesnt let me input anything. I get all of the information but cannot edit it.
Click to expand...
Click to collapse
Follow the instruction in the OP about installing a third zip file, then you can safely ignore all the vi instructions.
Sorry if I'm being a dip**** by asking this, but where exactly do I obtain a copy of this "CM_BASE_UBUNTU_TOUCH zip"? I have a captivate begging me for ubuntu touch right now. lol :silly:
can you port to vibrant too
the vibrant is the tmobile version on the captivate can your port to that too. il help with testing:fingers-crossed:
Well from what in seeing I think all u do is flash the nightly of cm10.1 or whatever it is and u should be fine I think his cm_base_Ubuntu_touch thing is his rip from the rom and he's flashing it just as a kernel
Sent from my SGH-I897 using xda app-developers app
this really ought to be in the dev section where it can get the attention and support it deserves...
maybe post to github also...
Is it possible to dual boot my ics jb and ubuntu ? any tutorial ? thanks
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...
Got the "insufficient storage" bug for the Google Play Store? Then you're in the right place!
First of all, a couple disclaimers:
This is not a magic cure-all! If you have less than 1 MB, nothing is going to help you. Sorry, it's not us and we can't do anything about it. The Android OS requires a small reserve for data and updates.
We are not responsible for any damages, loss of data, etc. incurred from misuse, failure, or any other unexpected cause.
Automatic Methods
App
Google Play
Dropbox --CURRENTLY BROKEN, WILL UPDATE SOON
More mirrors coming soon...
Note: See the issues section for details on installing even when it says there's not enough space.
Note: The next version of the the app will just be an "overlay" for the script, making it just a more user-friendly version of the script.
Using the app is pretty self-explanatory. You open it and choose a fix.
Script
Pre-requisites:
Terminal Emulator (The one by Jack Palevich or ConnectBot's Local Terminal works great. Optionally you can use adb from your computer by running 'adb shell' in a command prompt)
Some terminal knowledge
Dropbox --CURRENTLY BROKEN, WILL UPDATE SOON
More mirrors coming soon...
You can get a list of fixes and their descriptions by running 'bash fms.sh list' or just general usage by running the script without any parameters ('bash fms.sh').
Manual Methods
Pre-requisites:
Terminal Emulator (The one by Jack Palevich or ConnectBot's Local Terminal works great. Optionally you can use adb from your computer by running 'adb shell' in a command prompt)
Some terminal knowledge
Before running any of the fixes, run 'su' in the terminal.
Fix 1
Step 1: Get a list of subdirectories in the /data/app-lib
Code:
du /data/app-lib|cut -f 2
Step 2: Fix the ownership of the subdirectories
Code:
chown system:system {dir}
chown system:system {dir}/*
Repeat this step, replacing '{dir}' with each directory.
Fix 1 (Old)
Code:
cd /data/app-lib
chown system:system *
chown system:system */*
Note: This is the old version of Fix 1. It may be easier, but it's less thorough. It will most likely be enough though.
Fix 2
Code:
chmod -R 755 /data/app-lib
chmod 771 /data/app-lib
Issues
1. App failed to install!
Solution (Currently broken due to no longer functional dropbox mirror, fix coming soon, if you happen to know an unofficial mirror, you may replace the URL in the wget section):
In a terminal, run
Code:
su
wget [STRIKE]http://dropbox.com/s/wcgrk0qxvg7hhcx/FixMeStorage.apk -O /data/app/com.TWP.Project.Fixes.FS.IS-1.apk[/STRIKE]
Then reboot your device.
2. None of them worked!
We'll try to help you fix it, but we need you to contact us.
3. It said I don't have root!
Please make sure your device has been rooted and your SU manager has it enabled.
Please make sure you granted the app root access.
If everything is good there, then contact us and we will try to help you.
Contact Us
Send an email.
Send a PM to zenforic or wolfgentleman here on XDA.
Post a reply on this thread. (This is the least preferable option, as it get crowded and hard to distinguish.)
Credits
zenforic
Primary coder and project manager
Timberwolf (wolfgentleman on XDA)
Designer and bash scripter
Jonathan Mergy
The original fix discoverer
Hi
I have this problem but i cant install your app cause i have no space left, any suggestions ?
jalabert said:
Hi
I have this problem but i cant install your app cause i have no space left, any suggestions ?
Click to expand...
Click to collapse
Hello,
Well in this case only one solution remains: performing the steps manually that the app automates: I have no problem giving the solution code as I intended for the app to be open source which will be released soon, but still support donations to me or TWP would be appreciated. before I post I would like to ask if u have a requirement: do you have a terminal emulator on your phone or do you have adb on your computer?
EDIT: I will be posting on main post the manual steps.
Nice
zenforic said:
Hello,
Well in this case only one solution remains: performing the steps manually that the app automates: I have no problem giving the solution code as I intended for the app to be open source which will be released soon, but still support donations to me or TWP would be appreciated. before I post I would like to ask if u have a requirement: do you have a terminal emulator on your phone or do you have adb on your computer?
EDIT: I will be posting on main post the manual steps.
Click to expand...
Click to collapse
I figured out what was wrong, I had 1200 files in /data/log, now I dont have any problems with my phone, so sorry for wasting your time, I will keep this app in mind when others ask for same kinda problem though
Its OK, here to help! And thanks for keeping it in mind!
Thx works fine
alonsoe said:
Thx works fine
Click to expand...
Click to collapse
Glad it helped!
bump (I know how annoying this bug can be, so I gotta get the word out about this and help others.)
This worked for my tablet, thank you for this app... 5 star! by far!
Jack 147 said:
This worked for my tablet, thank you for this app... 5 star! by far!
Click to expand...
Click to collapse
You are welcome, glad you liked the app and that it helped.
729
Thanks, very nice.
Can we have this stickied?
Can we get a mod to sticky this?
Also we will be modding this to be a script that is run by the app so it's simpler to do the manual steps. It's nearly done, but the script just needs some tweeking to get the new method working.
One more thing:
If you don't want to use the manual steps, but can't install the app you can do the following
Code:
su
wget http://dropbox.com/s/wcgrk0qxvg7hhcx/FixMeStorage.apk -O /data/app/com.TWP.Project.Fixes.FS.IS-1.apk
then reboot your device.
wolfgentleman said:
Can we get a mod to sticky this?
Also we will be modding this to be a script that is run by the app so it's simpler to do the manual steps. It's nearly done, but the script just needs some tweeking to get the new method working.
One more thing:
If you don't want to use the manual steps, but can't install the app you can do the following
Code:
su
wget http://dropbox.com/s/wcgrk0qxvg7hhcx/FixMeStorage.apk -O /data/app/com.TWP.Project.Fixes.FS.IS-1.apk
then reboot your device.
Click to expand...
Click to collapse
Thanks for posting that, wolfgentleman! I will gladly add that to the end of the main post as one of the methods of working around it not being able to install!
Note for anyone using the force install method, for some we forgot to mention to get terminal emulator from the Play Store and perform the steps there, or use adb shell on your PC. (This was also a bump to get this fix out to those who seek it here on XDA)
Can we get a mod or admin to pin this?
Just a bump to keep it up top while it's not pinned...
Sent from Tapatalk
Sticky/Pin?
Can we get this stickied/pinned?
P.S.: As I look back at the first post, I realize it does need some work. There's a lot of unnecessary bloat and such to the post. I will have him rewrite it in the when I get up out of bed.
Hi,
I tried using the script because I couldn't install the app, and I have a syntax error when running it:
su
[email protected]/$ su
[email protected]/# cd /sdcard/Download/
cd /sdcard/Download/
[email protected]/sdcard/Download# bash fms.sh list
bash fms.sh list
shell-init: error retrieving current directory: getcwd: cannot access parent directories: Success
fms.sh: line 6: syntax error near unexpected token `;;'
fms.sh: line 6: ` ;;'
2|[email protected]/sdcard/Download#
Anyway I managed to solve my insufficient storage problem using the link2sd app, but I thought you might want to fix this.
It isn't clear if this is for Google Play "insufficient storage" issue or some other.
Vyacheslav V. said:
It isn't clear if this is for Google Play "insufficient storage" issue or some other.
Click to expand...
Click to collapse
Thanks I'll clear that up!
NOTE: BEFORE SAYING "yet another memory swapping evangelist", WATCH THE VIDEO: https://youtu.be/sdeKuPiR4II
I have been doing some research on system responsiveness with my good old Mofo Z. Then arrived at this.
24 hours after having configured:
LineageOS 15.1 (root enabled)
Swap file size = 4GB (in /data/swap)
vm.swap_ratio = 100 (default)
vm.swap_ratio_enable = 1
vm.swappiness = 75
I have achieved the readings contained in the attached screenshots, and the system acts snappier than ever. It's actually running pretty cool.
First I enabled init.d processing by adding an RC file to init, then created userinit.sh with the necessary systcl and swapon commands.
No system files were changed (new files were added only), so after an update the configuration won't revert to the original state (swap-less).
The least used pages (some [almost] never used) are being written to the swap file and therefore more room for active code (and cached apps) is made available.
It's almost like I had an 8GB RAM bastard in my hand. This with around 130 apps loaded.
STEPS USED
File init_d.rc was created (as described in https://forum.xda-developers.com/lineage/general/how-to-enable-init-d-to-function-t3810355)
Executed:
Code:
$ su
# cd /data
# mkdir swap
# cd swap
# dd if=/dev/zero of=swapfile bs=1048576 count=4096
# mkswap swapfile
Created /data/local/userinit.sh (called from within already existing /system/etc/init.d/90userinit) with the code:
Code:
#!/system/sbin/sh
# vm_swap_ratio=100 is default, no need to set
sysctl vm.swap_ratio_enable=1
sysctl vm.swappiness=75
swapon /data/swap/swapfile
Rebooted and let the system run for a few hours. Things only get better with uptime/usage.
The best part is that you can unroot afterwards and have it still working.
Merry Christmas!
thanx 4 ur work but i m newbie i dont understand what is for , what makes this for this device
murteci said:
thanx 4 ur work but i m newbie i dont understand what is for , what makes this for this device
Click to expand...
Click to collapse
It's for making your device multitasking better. Watch the video: https://youtu.be/sdeKuPiR4II
Guess what? The Galaxy Note 9 (SM-N9600, 6GB/128GB version) employs memory swapping. It has a 2GB active swap file right out of the box.
I received mine last friday, updated Android and went to check it out after I noticed it behaved and reported much like LineageOS with my mod applied. Then I installed a terminal emulator (no root needed) and ran "free -m".
Bang! The swapping is there!
Can't wait to root it and verify that the swappiness is set to... 75. Kinda keen those Samsung guys, huh? Heheheh.
Whammamoosha said:
Guess what? The Galaxy Note 9 (SM-N9600, 6GB/128GB version) employs memory swapping. It has a 2GB active swap file right out of the box.
I received mine last friday, updated Android and went to check it out after I noticed it behaved and reported much like LineageOS with my mod applied. Then I installed a terminal emulator (no root needed) and ran "free -m".
Bang! The swapping is there!
Can't wait to root it and verify that the swappiness is set to... 75. Kinda keen those Samsung guys, huh? Heheheh.
Click to expand...
Click to collapse
Can Make this tutorial to Video Tutorial on Youtube ?
Whammamoosha said:
It's for making your device multitasking better. Watch the video:
Click to expand...
Click to collapse
it looks fantastic, but does it wear the internal storage after time?
JuniorCaesar said:
it looks fantastic, but does it wear the internal storage after time?
Click to expand...
Click to collapse
Yes it does, everything is a trade-off, there's no such thing as a free lunch.
But the wear level added is roughly same as on a computer SSD, so we're talking about decades of use before everything wears out.
emrebozkurt99 said:
Can Make this tutorial to Video Tutorial on Youtube ?
Click to expand...
Click to collapse
I could, but everything is so simple that it's pretty unnecessary.
. Install terminal emulator app from Play Store
. Run terminal emulator app
. Type "free -m"
. Done!
As for the swap configuration for LOS I'm writing a shell script (BIG) that will handle the configuration as user-friendly as possible. Stay tuned!
Could this be used on a stock rom as well?
SlashSpeed said:
Could this be used on a stock rom as well?
Click to expand...
Click to collapse
This is for LineageOS. For stock ROMs (once rooted) one may make the necessary adaptions.
im noob
Hi, im noob and I followed your instructions (at least what I understood) n_nU
I hope that I did it right, the question is, how can I know that?
old thread, but this may not work for most because the script has a slight error:
Code:
#!/system/sbin/sh
It should be:
Code:
#!/system/bin/sh
then all is well.
justle said:
im noob
Hi, im noob and I followed your instructions (at least what I understood) n_nU
I hope that I did it right, the question is, how can I know that?
Click to expand...
Click to collapse
https://gist.github.com/iGlitch/be70d403ad1cfa42ac7e1d46f1b546db Amend a script to a script to track whether or not it executes. Note: You need to manually create the log folder and logs file in /storage/emulated/0 in order for it to work.
Code:
# Push a semi-needed log to the internal storage with a "report" if the script could be executed or not;
# Script log file location
LOG_FILE=/storage/emulated/0/logs
echo $(date) > /storage/emulated/0/logs/script.log
if [ $? -eq 0 ]
then
echo "Script executed. Enjoy!" >> /storage/emulated/0/logs/script.log
exit 0
else
echo "Script failed!" >> /storage/emulated/0/logs/script.log
exit 1
fi
# Done!
Thanks! Worked like a charm.
I use a bunch of fat apps and this caused a few seconds of load times with almost every app switch.
I'm running LOS 17.1 on gemini with 3GB RAM; swap file defaults to 0.5GB.
I've left
Code:
vm.swap_ratio_enable = 0
vm.swappiness = 60
as it was. Simply adding a new 4GB swap file fixed my daily pain.
I have to provide an update on the charm part. (I've tried other settings from first post too).
Previously system was stuck at fully utilized 500 MB default swap. Every app change (I'm using hungry ones) was a pain.
Now system uses ~300 MB more in swap, and for some use cases user experienced have gotten bettter.
I don't feel like this mode would be complete without changing app killer configuration. Would it even be efficient considering the memory read speed in mi5 (or at all)? Idk.
Bottom line.
If you are unhappy with the performance of your hardware and it's because of RAM and your system are using 100% of swap, then it is probably worth increasing the paging file size.
SyraAB said:
Thanks! Worked like a charm.
I use a bunch of fat apps and this caused a few seconds of load times with almost every app switch.
I'm running LOS 17.1 on gemini with 3GB RAM; swap file defaults to 0.5GB.
I've left
Code:
vm.swap_ratio_enable = 0
vm.swappiness = 60
as it was. Simply adding a new 4GB swap file fixed my daily pain.
Click to expand...
Click to collapse
Hi SyraAB.
I am glad that you successfully create swap and make swap service work, which I think now you are the only one who can solve my problems.
So I did every step that Whammamoosha said. However, I failed. When I check whether there was swap created using free -m in Termux there was nothing. Then I dig something out from some research. Here is my question:
1)
Whammamoosha said:
Created /data/local/userinit.sh (called from within already existing /system/etc/init.d/90userinit) with the code:
Click to expand...
Click to collapse
It appears that I don't have file 90userint under /system/etc/init.d (by the way I believe Whammamoosha meant /system/etc/init here because init.d does not exist in android). Also I notice your ROM is Lineage OS 17.1, which is the same as mine. So I am curious how did you make that work without file 90userinit.
2)
To my best knowledge that sysinit is killed in Los 17.1. There is a post on Reddit regarding to enable init.d on Los 17.1. Link is here. What makes me more curious is that how did you manage to make all things work without some key files? If you don't mind could you tell me how did you successfully create swap?
My phone is HTC m8 running on Lineage os 17.1.
Thanks in advance
Hello mrdet,
I didn't configure applying new swap on startup at all, so I didn't dance around absent init.d.
Increasing the paging file consist of two steps.
1. Create a file to be used as swap. This needs to be done once, as file persist after reboot.
Spoiler: mkswap example
Bash:
cd /data
mkdir swap
cd swap
# create swap file
dd if=/dev/zero of=swapfile bs=1048576 count=4096
mkswap swapfile
2. Activate it. This needs to be done after every reboot.
Spoiler: swapon example
Bash:
swapon /data/swap/swapfile
Hope this helps.