Related
Here is a small script that toggle force usb charging option from pershoot kernel :
Code:
#!/system/bin/sh
export STATE=`cat /sys/class/power_supply/battery/force_usb_charging`
if [ $STATE == 0 ]
then echo 1 > /sys/class/power_supply/battery/force_usb_charging
echo "Enable USB Charging"
else echo 0 > /sys/class/power_supply/battery/force_usb_charging
echo "Disable USB Charging"
fi
It needs root permission and a suitable kernel such as pershoot's.
PS: first step in the XDA community
It will be nice if you could explain how to use this script (one of the several ways).
Sorry to forgot the documentation part, here it is :
It can be used with any terminal apps with root access, just copy the content into a file (toggle_usb.sh for instance) and launch it in root terminal with :
Code:
sh toggle_usb.sh
A more user friendly way is to use Script Manager with SMWidget to add it on your homescreen. I use it this way so I could disable charging when the tab is plugged only for a file transfert.
Will this work on other devices? Like say the acer a100 or acer a500. Considering getting one of those but don't like that neither will charge usb.
If this only works for galaxy tab, how come? Just curious why force usb works on galaxy tab and not other devices.
It might work on other devices if the charging chipp support it and if the kernel has driver for. For the Galaxy Tab,The stock kernel and many others shipped with custom rom don't allow usb charging.
If supported by your hardware the script should work, it only use standard script and kernel related configuration.
EDIT:
The Acer a100 et a500 have a dedicated charger wich deliver 12V which is far more than a USB port can deliver (5V), I seriously doubt they put a dc-dc converter to connect the usbport to the charging chip.
Envoyé depuis mon GT-P7500 avec Tapatalk
Widget Apps
Hello,
I've tried to make it more user friendly, so I created a small widget apps using my previous script. It's my first real apps for Android, it still has some flaws.
Known Issues :
when adding the widget the file is at unknown state, need to hit the refresh button
Design is perfectible especially icons...
I would like to thanks the authors of the android-widget-development-tutorials availlable on google code.
not on tab 3
ebolalex said:
Here is a small script that toggle force usb charging option from pershoot kernel :
Code:
#!/system/bin/sh
export STATE=`cat /sys/class/power_supply/battery/force_usb_charging`
if [ $STATE == 0 ]
then echo 1 > /sys/class/power_supply/battery/force_usb_charging
echo "Enable USB Charging"
else echo 0 > /sys/class/power_supply/battery/force_usb_charging
echo "Disable USB Charging"
fi
It needs root permission and a suitable kernel such as pershoot's.
PS: first step in the
Well so far as I can see the folder called battery here apears as a file that is un openable to root explorer, the terminal will go in but there is no editing allowance as the files are locked, command chmod return a bad mode eror, since force_usb_charging does not exist I thought np ill creat on... long story short I made a file by that name in storage then used cp to copy that file to the destination mentioned (after chmod the sys class power_supply to write for all, ) battery would not as I mention take such command. All in all I still have not created the file force_usb_charging with a 1 as cat. So question........ how can I create the file in the directory. I am rooted, all my work in terminal has been su, I see the # show me as rooted, and I can alter the permissions. (Ps sorry dude with svsfsswitch.apk did absolutly nothing as the file did not exist, nor did the script above) is the smt 210r that different from othet machines? Lol retorical q, sorry . Tyvm for the help in advance. With time ill learn this linux /android stuff out.... summery how to creat a file in the sys/class/power_supply/battery called force_usb_charging containing the number 1.....
Click to expand...
Click to collapse
grummbunger said:
ebolalex said:
Here is a small script that toggle force usb charging option from pershoot kernel :
Code:
#!/system/bin/sh
export STATE=`cat /sys/class/power_supply/battery/force_usb_charging`
if [ $STATE == 0 ]
then echo 1 > /sys/class/power_supply/battery/force_usb_charging
echo "Enable USB Charging"
else echo 0 > /sys/class/power_supply/battery/force_usb_charging
echo "Disable USB Charging"
fi
It needs root permission and a suitable kernel such as pershoot's.
PS: first step in the
Well so far as I can see the folder called battery here apears as a file that is un openable to root explorer, the terminal will go in but there is no editing allowance as the files are locked, command chmod return a bad mode eror, since force_usb_charging does not exist I thought np ill creat on... long story short I made a file by that name in storage then used cp to copy that file to the destination mentioned (after chmod the sys class power_supply to write for all, ) battery would not as I mention take such command. All in all I still have not created the file force_usb_charging with a 1 as cat. So question........ how can I create the file in the directory. I am rooted, all my work in terminal has been su, I see the # show me as rooted, and I can alter the permissions. (Ps sorry dude with svsfsswitch.apk did absolutly nothing as the file did not exist, nor did the script above) is the smt 210r that different from othet machines? Lol retorical q, sorry . Tyvm for the help in advance. With time ill learn this linux /android stuff out.... summery how to creat a file in the sys/class/power_supply/battery called force_usb_charging containing the number 1.....
Click to expand...
Click to collapse
Hi grummbunger,
The /sys folder is a special filesystem handled by the linux kernel itself (by the means of its drivers), it provide information and control on peripheral. So If you do not have a specific fil in your /sys you could not create it. My Script was intended to work with Pershoot kernel, if you do not use it, the driver may not be loaded or might use a different file.
I would asked you which ROM and Kernel you are using to test it, but unfortunately i don't have access to a galaxy tab anymore...
Could you post me the list of file availlable in your battery folder ?
Welcome in the community, I hope you'll find the way to hack into your device to suit your needs
Click to expand...
Click to collapse
samsung usb charge enabling
ebolalex said:
grummbunger said:
Hi grummbunger,
The /sys folder is a special filesystem handled by the linux kernel itself (by the means of its drivers), it provide information and control on peripheral. So If you do not have a specific fil in your /sys you could not create it. My Script was intended to work with Pershoot kernel, if you do not use it, the driver may not be loaded or might use a different file.
I would asked you which ROM and Kernel you are using to test it, but unfortunately i don't have access to a galaxy tab anymore...
Could you post me the list of file availlable in your battery folder ?
Welcome in the community, I hope you'll find the way to hack into your device to suit your needs
Click to expand...
Click to collapse
android version 4.1.2 (could not find a pershoot rom to run on a 7 inch samsung tab3, and before flashing at all i wanna make sure that the setting can't be applied without flashing as that is really a last resort.) but i am totally ok with flashing if it is nessesary. i have rockettab ready to go, but have no idea if that would help at all with this situation.
kernel 3.4.5-1304745-user
found that the link "battery" goes to sys/devices/platform/sec-battery/power_supply/battery there are many files there that report status of power and such i found, some of the files names are like:
batt_charging_source batt_lp_charging Charge_now charge_type soip_activated soip_level status talk_gsm wc_enable wc_status. etc...
tyvm for your interest in helping my problem!
Click to expand...
Click to collapse
grummbunger said:
ebolalex said:
android version 4.1.2 (could not find a pershoot rom to run on a 7 inch samsung tab3, and before flashing at all i wanna make sure that the setting can't be applied without flashing as that is really a last resort.) but i am totally ok with flashing if it is nessesary. i have rockettab ready to go, but have no idea if that would help at all with this situation.
kernel 3.4.5-1304745-user
found that the link "battery" goes to sys/devices/platform/sec-battery/power_supply/battery there are many files there that report status of power and such i found, some of the files names are like:
batt_charging_source batt_lp_charging Charge_now charge_type soip_activated soip_level status talk_gsm wc_enable wc_status. etc...
tyvm for your interest in helping my problem!
Click to expand...
Click to collapse
In fact the kernel you need to install must support charging from any sources. It should be specified in the kernel feature list. Stock kernel won't let you do this or it would work out of the box.
Be aware that your Usb port must provide enough power to charge your device.
You're welcome.
Click to expand...
Click to collapse
ebolalex said:
grummbunger said:
In fact the kernel you need to install must support charging from any sources. It should be specified in the kernel feature list. Stock kernel won't let you do this or it would work out of the box.
Be aware that your Usb port must provide enough power to charge your device.
You're welcome.
Click to expand...
Click to collapse
Well it is a dell usb with power share at 1.2 a a wall charger is 2, the battery is 4000ma, I digress though I have in fact found the battery lasts for well over the time I need so I am all good. Thanks again for the responce!
Click to expand...
Click to collapse
If your kernel supports init.d scripts you can save script to /system/etc/init.d and it will be automatically launched on device boot. You have to delete extension from script name and prefix is number from 00 to 99
Hi,
Any way to get this working on kitkat rom (carbon kk)?
Phone is photon q, in the original sprint rom burried under hidden menu's the is a app to do it, so it must be possible in some way....any ideas?
Thanks!
hi there.
one of the issues of dual booting android with ubuntu touch is not being able to access your files in the other OS.
in ubuntu :
the android files (or /sdcard/ content) are located at /userdata/media/0 while your files are at ~/. make a mount point and bind these two directories: (i used adb for this)
Code:
$adb shell
#su - phablet
$cd ~
$sudo mkdir android
$sudo mount --bind /userdata/media/0 ~/android
$sudo chmod 775 android
$sudo chown phablet:phablet android
after this you'll be able to access your data with ubuntu's file manager
in android :
ubuntu files are at /data/user-data/phablet/ while your files are at /data/media/0. unfortunately only the app that performs the mount (for me terminal emulator) can see the files i don't know why... more info @ http://forum.xda-developers.com/showthread.php?t=2065856
and as you can see stickmount doesn't support nexus 4. so if you've got something else give it a try
Code:
mount -o bind /data/user-data/phablet /data/media/0/ubuntu
you can always access your ubuntu files using a file explorer with root permissions.
notes:
i've got a nexus 4 but it should work for all supported devices.
Tasssadar said:
If you're using MultiROM, update to the latest version and replace /userdata/media/0 with /android/realdata/media/0
Click to expand...
Click to collapse
MTN_HD2 said:
hi there.
one of the issues of dual booting android with ubuntu touch is not being able to access your files in the other OS.
in ubuntu :
the android files (or /sdcard/ content) are located at /userdata/media/0 while your files are at ~/. make a mount point and bind these two directories: (i used adb for this)
Code:
$adb shell
#su - phablet
$cd ~
$sudo mkdir android
$sudo mount --bind /userdata/media/0 ~/android
$sudo chmod 775 android
$sudo chown phablet:phablet android
after this you'll be able to access your data with ubuntu's file manager
in android :
ubuntu files are at /data/user-data/phablet/ while your files are at /data/media/0. unfortunately only the app that performs the mount (for me terminal emulator) can see the files i don't know why... more info @ http://forum.xda-developers.com/showthread.php?t=2065856
and as you can see stickmount doesn't support nexus 4. so if you've got something else give it a try
Code:
mount -o bind /data/user-data/phablet /data/media/0/ubuntu
you can always access your ubuntu files using a file explorer with root permissions.
notes:
i've got a nexus 4 but it should work for all supported devices.
Click to expand...
Click to collapse
hi
i have a problem doing this it says that the directory /userdata/media/0 does not exist
line that the command does give out : mount : special device /userdata/media/0 does not exist
btw i am using stable saucy but i will try the newes version now
any suggestions with that ?
chris1005 said:
hi
i have a problem doing this it says that the directory /userdata/media/0 does not exist
line that the command does give out : mount : special device /userdata/media/0 does not exist
btw i am using stable saucy but i will try the newes version now
any suggestions with that ?
Click to expand...
Click to collapse
It's "/host/media/0"
woernsn said:
It's "/host/media/0"
Click to expand...
Click to collapse
This gave me same error as before
what i forgot to say is that i am using Multiboot for the Teamwin recovery / this app to install Ubuntu Touch
https://play.google.com/store/apps/details?id=com.tassadar.multirommgr
Also i tried to find the folder with cd and ls but i couldnt find it.
but thanks for your support
chris1005 said:
This gave me same error as before
what i forgot to say is that i am using Multiboot for the Teamwin recovery / this app to install Ubuntu Touch
https://play.google.com/store/apps/details?id=com.tassadar.multirommgr
Also i tried to find the folder with cd and ls but i couldnt find it.
but thanks for your support
Click to expand...
Click to collapse
mmmh.. did you try searching for something, that is on the SD with 'find' via adb shell?
helped me
Sent from my Nexus 4 using Tapatalk
chris1005 said:
This gave me same error as before
what i forgot to say is that i am using Multiboot for the Teamwin recovery / this app to install Ubuntu Touch
https://play.google.com/store/apps/details?id=com.tassadar.multirommgr
Also i tried to find the folder with cd and ls but i couldnt find it.
but thanks for your support
Click to expand...
Click to collapse
MultiROM uses a different partition layout. Maybe @Tasssadar can tell you more about that. (I would be interested as well.)
nikwen said:
MultiROM uses a different partition layout. Maybe @Tasssadar can tell you more about that. (I would be interested as well.)
Click to expand...
Click to collapse
Ok thanks you for the support
chris
chris1005 said:
Ok thanks you for the support
chris
Click to expand...
Click to collapse
If you get any information on that topic, please share it here.
nikwen said:
If you get any information on that topic, please share it here.
Click to expand...
Click to collapse
I wrote Tasssadar if he has a solution for the problem i will post this
chris1005 said:
I wrote Tasssadar if he has a solution for the problem i will post this
Click to expand...
Click to collapse
Thank you very much.
@chris1005: Install MultiROM v22b, go to recovery -> Advanced -> MultiROM -> List ROMs -> *ubuntu* -> Re-patch init and boot to Ubuntu. The "real" /data will be mounted under /android/realdata, so use folder /android/realdata/media/0/ instead of /userdata/media/0.
Tasssadar said:
@chris1005: Install MultiROM v22b, go to recovery -> Advanced -> MultiROM -> List ROMs -> *ubuntu* -> Re-patch init and boot to Ubuntu. The "real" /data will be mounted under /android/realdata, so use folder /android/realdata/media/0/ instead of /userdata/media/0.
Click to expand...
Click to collapse
Thanks for the support
but i still get the same error
I installed Multirom v22 i could not find v22b i searched on the offical forum thread and the Multirom manager.
Sorry if i am blind >.<
Tried it several times to Re-patch init and install the latest available Multirom and recovery
I will try different Ubuntu release see what this does
chris1005 said:
Thanks for the support
but i still get the same error
I installed Multirom v22 i could not find v22b i searched on the offical forum thread and the Multirom manager.
Sorry if i am blind >.<
Tried it several times to Re-patch init and install the latest available Multirom and recovery
I will try different Ubuntu release see what this does
Click to expand...
Click to collapse
This one is v22b: http://d-h.st/djy
The changelog says that it's just been implemented in v22b: http://forum.xda-developers.com/showthread.php?p=48508468#post48508468
@Tasssadar: What's about the Nexus 4? Will we be able to mount the partition in Ubuntu as well?
Why did I think this is in N5 section? Oo Anyway, it's v22a for mako and flo and v22b for grouper and hammerhead.
@MTN_HD2: Can you please add info about MultiROM to the first post? Something along the lines of "If you're using MultiROM, update to the latest version and replace /userdata/media/0 with /android/realdata/media/0". Thank you.
Tasssadar said:
Why did I think this is in N5 section? Oo Anyway, it's v22a for mako and flo and v22b for grouper and hammerhead.
@MTN_HD2: Can you please add info about MultiROM to the first post? Something along the lines of "If you're using MultiROM, update to the latest version and replace /userdata/media/0 with /android/realdata/media/0". Thank you.
Click to expand...
Click to collapse
Thank you very much.
Thank you very much just saw the update in multirom manager
Sent from my Nexus 4 using xda app-developers app
nexus 7 2013 LTE (4.4.2)
Hi
I have nexus 7 4g (v4.4.2 )
I install multiROM v22b with Ubuntu touch r206(default)
But phone not active (3g/4g)
Can you help me?
mohammadhossein said:
Hi
I have nexus 7 4g (v4.4.2 )
I install multiROM v22b with Ubuntu touch r206(default)
But phone not active (3g/4g)
Can you help me?
Click to expand...
Click to collapse
This is normal. Its still in a testing phase. I have had the same issue, even on the latest versions still. You're not doing anything wrong.
-wardawgmalvicious
Rooted N5/N7 2nd Gen
MultiROM TWRP
Franco Kernel
Stock 4.4.2 infused with GB
Ubuntu Touch
-Sent using Tapatalk
Have a look at this post in the Nexus 4 thread: http://forum.xda-developers.com/nex...ouch-14-10-utopic-unico-t2324683/post53850263
You can now finally use your Android music and pictures in Ubuntu.
Do you know how to get the folders mount at each boot ?
Hey guys, gals, I recently downloaded the Viper v3.0.1 Android 4.4 Sense 5 rom, viperhttp://forum.xda-developers.com/showthread.php?t=2629211. With the Sense kernel edited by zarbov, says sweep2wake is enabled but doesnt work. Attempted to activate using Kconrol and Kernel tuner. Can anyone educate me on what is missing or give any advice. All would be appreciated!!
You need to set the start button and end button files
Sent from my HTC6435LVW using XDA Premium HD app
hey Torrented, attempted this with kernel tuner...no go. Recommended method of setting this?
.torrented said:
You need to set the start button and end button files
Sent from my HTC6435LVW using XDA Premium HD app
Click to expand...
Click to collapse
fastguy82 said:
hey Torrented, attempted this with kernel tuner...no go. Recommended method of setting this?
Click to expand...
Click to collapse
AHH! Figured it out after playing with permissions thanks
fastguy82 said:
AHH! Figured it out after playing with permissions thanks
Click to expand...
Click to collapse
Hey fastguy82 can u post your fix and does it stick after reboot? thanks
mopartonyg said:
Hey fastguy82 can u post your fix and does it stick after reboot? thanks
Click to expand...
Click to collapse
Navigate to /sys/android_touch/
Look for the sweep2wake files and edit them, I found that after you enter what you want press enter to add a second blank like to the file and then save and exit
I use root explorer and this is what I needed to do.
.torrented said:
Navigate to /sys/android_touch/
Look for the sweep2wake files and edit them, I found that after you enter what you want press enter to add a second blank like to the file and then save and exit
I use root explorer and this is what I needed to do.
Click to expand...
Click to collapse
thanks torrent still cany get settings to stick. u mean a space right after the entry?
mopartonyg said:
thanks torrent still cany get settings to stick. u mean a space right after the entry?
Click to expand...
Click to collapse
Well I somehow made it work last night, but after rebooting today. Not working again. So without "holding my hand",jk. What do I change exactly? Iam using Root Browser, I am going to permissions and editing them, correct? I have also tried using Kernel tuner to edit but this does nothing useful. All input once again is appreciated.d
fastguy82 said:
Well I somehow made it work last night, but after rebooting today. Not working again. So without "holding my hand",jk. What do I change exactly? Iam using Root Browser, I am going to permissions and editing them, correct? I have also tried using Kernel tuner to edit but this does nothing useful. All input once again is appreciated.d
Click to expand...
Click to collapse
not sure what to tell u, I have tried all different ways and still no luck
Settings do not seem to stick upon reboot, not sure why.
mopartonyg said:
thanks torrent still cany get settings to stick. u mean a space right after the entry?
Click to expand...
Click to collapse
Inside the sweep2wake file
Code:
1
<----Needs an extra blank line
Startbutton file
Code:
BACK
Endbutton file
Code:
MENU
fastguy82 said:
Well I somehow made it work last night, but after rebooting today. Not working again. So without "holding my hand",jk. What do I change exactly? Iam using Root Browser, I am going to permissions and editing them, correct? I have also tried using Kernel tuner to edit but this does nothing useful. All input once again is appreciated.d
Click to expand...
Click to collapse
No don't mess with perms, there in no need to just change the values inside the file (I recommend removing kernel tuner or just disable its SU access)
.torrented said:
Settings do not seem to stick upon reboot, not sure why.
Inside the sweep2wake file
Code:
1
<----Needs an extra blank line
Startbutton file
Code:
BACK
Endbutton file
Code:
MENU
No don't mess with perms, there in no need to just change the values inside the file (I recommend removing kernel tuner or just disable its SU access)
Click to expand...
Click to collapse
Make a init.d script to setup buttons
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Zarboz said:
Make a init.d script to setup buttons
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ill make some scripts later tonight when I get home from work.
.torrented said:
Settings do not seem to stick upon reboot, not sure why.
Inside the sweep2wake file
Code:
1
<----Needs an extra blank line
Startbutton file
Code:
BACK
Endbutton file
Code:
MENU
No don't mess with perms, there in no need to just change the values inside the file (I recommend removing kernel tuner or just disable its SU access)
Click to expand...
Click to collapse
I can them to work until reboot, hopefully Z will figure it out. Thanks
.torrented said:
Ill make some scripts later tonight when I get home from work.
Click to expand...
Click to collapse
you can also use cmdline.. i THINK i enabled that
you would set in cmdline
s2w_start=%value s2w_end=%value s2w=%value
and insert your values for %value
mopartonyg said:
I can them to work until reboot, hopefully Z will figure it out. Thanks
Click to expand...
Click to collapse
Considering the config files are spawned by the kernel and are rewritten upon boot ... that is why it wont stick
you can just add some edit lines to any init.d script in /system/etc/init.d/
just add
echo "WHATEVERKEY" > /sys/android_touch/sweep2wake_startbutton
echo "WHATEVERKEY" > /sys/android_touch/sweep2wake_endbutton
echo "WHATEVERSETTING" > /sys/android_touch/sweep2wake
Zarboz said:
Considering the config files are spawned by the kernel and are rewritten upon boot ... that is why it wont stick
you can just add some edit lines to any init.d script in /system/etc/init.d/
just add
echo "WHATEVERKEY" > /sys/android_touch/sweep2wake_startbutton
echo "WHATEVERKEY" > /sys/android_touch/sweep2wake_endbutton
echo "WHATEVERSETTING" > /sys/android_touch/sweep2wake
Click to expand...
Click to collapse
Yeah I know, I've done scripting for chris' kernel a while ago.
.torrented said:
Yeah I know, I've done scripting for chris' kernel a while ago.
Click to expand...
Click to collapse
since you compile source enable CMDLINE functions in defconfig
then you can use the s2w_start= s2w_end= s2w= in cmdline
Fixed the issue
Edit* Found the problem why S2W doesn't work, DT2W needs to also be enabled, I will look at the code and see if I can fide where its causing the issue.
If anybody wants this, all you will need to do is add two files to the sdcard called
torrented-s2w-start
torrented-s2w-end
inside these files add the button of choice using all caps like
1 of these: BACK MENU HOME
also this will enable S2W by default if it is not.
then flash the kernel attached, and then you should be good to go!
to debug this, there will be a file called torrented.log on the sdcard after my script executes
@Zarboz When I enabled cmdline in defconfig I got build errors in the /arch/arm/mach-msm/build-in.o
I didn't look into in a lot, but I can check it out later.
Also my 99torrented script will only execute if you are on my kernel, if you flash back to z's kernel this will no longer work! <---- the way @crpalmer's scripts work (you can only use them on his kernel)
source: https://www.github.com/torrented/Monarudo_GPU_M7
scripts:
"99torrented"
Code:
#!/system/bin/sh
(
if grep torrented /proc/version > /dev/null
then
echo "** torrented's Sweep2Wake configuration:"
for script in /system/etc/torrented/*
do
$script
done
else
echo "!! torrented's Sweep2Wake configuration not running, this isn't my kernel !!"
fi
)2>&1 | tee /sdcard/torrented.log
"sweep2wake.sh"
Code:
#!/system/bin/sh
F=/sdcard/torrented-s2w-
S2W=/sys/android_touch/sweep2wake_
echo "Enabling Sweep2Wake"
echo 1 > /sys/android_touch/sweep2wake
for which in start end
do
Fwhich=$F"$which"
if [ -r $Fwhich ]
then
s2w=`cat $Fwhich`
echo $s2w > "$S2W$which""button"
echo "Setings $S2W$which""button to $s2w"
else
echo "Leaving $S2W$which""button alone"
fi
done
This is what the log should output on success
Code:
Enabling Sweep2Wake
Setings /sys/android_touch/sweep2wake_startbutton to BACK
Setings /sys/android_touch/sweep2wake_endbutton to MENU
hi torrent, in an attempt to get this to work on my device , I flashed your kernel, and did the above steps. I kept getting an internet crash, so I reflashed your kernel, and rebooted. device soon froze and is now stuck looping on the DNA screen. Hardware keys to get into recovery are not working. i have been trying for over a half hour now. i am on viper 3.0, twrp .6 beta. phone is not recognized in adb. will pulling battery get me a reboot? or is that dangerous? any input would be appreciated. thanks
---------- Post added at 05:09 AM ---------- Previous post was at 05:06 AM ----------
.torrented said:
Fixed the issue
Edit* Found the problem why S2W doesn't work, DT2W needs to also be enabled, I will look at the code and see if I can fide where its causing the issue.
If anybody wants this, all you will need to do is add two files to the sdcard called
torrented-s2w-start
torrented-s2w-end
inside these files add the button of choice using all caps like
1 of these: BACK MENU HOME
also this will enable S2W by default if it is not.
then flash the kernel attached, and then you should be good to go!
to debug this, there will be a file called torrented.log on the sdcard after my script executes
@Zarboz When I enabled cmdline in defconfig I got build errors in the /arch/arm/mach-msm/build-in.o
I didn't look into in a lot, but I can check it out later.
Also my 99torrented script will only execute if you are on my kernel, if you flash back to z's kernel this will no longer work! <---- the way @crpalmer's scripts work (you can only use them on his kernel)
source: https://www.github.com/torrented/Monarudo_GPU_M7
scripts:
"99torrented"
Code:
#!/system/bin/sh
(
if grep torrented /proc/version > /dev/null
then
echo "** torrented's Sweep2Wake configuration:"
for script in /system/etc/torrented/*
do
$script
done
else
echo "!! torrented's Sweep2Wake configuration not running, this isn't my kernel !!"
fi
)2>&1 | tee /sdcard/torrented.log
"sweep2wake.sh"
Code:
#!/system/bin/sh
F=/sdcard/torrented-s2w-
S2W=/sys/android_touch/sweep2wake_
echo "Enabling Sweep2Wake"
echo 1 > /sys/android_touch/sweep2wake
for which in start end
do
Fwhich=$F"$which"
if [ -r $Fwhich ]
then
s2w=`cat $Fwhich`
echo $s2w > "$S2W$which""button"
echo "Setings $S2W$which""button to $s2w"
else
echo "Leaving $S2W$which""button alone"
fi
done
This is what the log should output on success
Code:
Enabling Sweep2Wake
Setings /sys/android_touch/sweep2wake_startbutton to BACK
Setings /sys/android_touch/sweep2wake_endbutton to MENU
Click to expand...
Click to collapse
hi torrent, in an attempt to get this to work on my device , I flashed your kernel, and did the above steps. I kept getting an internet crash, so I reflashed your kernel, and rebooted. device soon froze and is now stuck looping on the DNA screen. Hardware keys to get into recovery are not working. i have been trying for over a half hour now. i am on viper 3.0, twrp .6 beta. phone is not recognized in adb. will pulling battery get me a reboot? or is that dangerous? any input would be appreciated. thanks
findinghomer said:
hi torrent, in an attempt to get this to work on my device , I flashed your kernel, and did the above steps. I kept getting an internet crash, so I reflashed your kernel, and rebooted. device soon froze and is now stuck looping on the DNA screen. Hardware keys to get into recovery are not working. i have been trying for over a half hour now. i am on viper 3.0, twrp .6 beta. phone is not recognized in adb. will pulling battery get me a reboot? or is that dangerous? any input would be appreciated. thanks
---------- Post added at 05:09 AM ---------- Previous post was at 05:06 AM ----------
hi torrent, in an attempt to get this to work on my device , I flashed your kernel, and did the above steps. I kept getting an internet crash, so I reflashed your kernel, and rebooted. device soon froze and is now stuck looping on the DNA screen. Hardware keys to get into recovery are not working. i have been trying for over a half hour now. i am on viper 3.0, twrp .6 beta. phone is not recognized in adb. will pulling battery get me a reboot? or is that dangerous? any input would be appreciated. thanks
Click to expand...
Click to collapse
So holding down the power button and vol down button isnt working? <- this usually 99% will work if not
try this
plug in the device to the pc and run
Code:
adb wait-for-device reboot recovery
either restore the stock viper boot.img or grab this kernel http://www.androidfilehost.com/?fid=23329332407576625
I personally don't recommend opening the device to disconnect the battery, unless you really know what you are doing because the internals are very sensitive.
hi folks, thanks to @joesnose we can now enter the yoga book's bios/uefi. you might say 'thank you' to him for this!!!
more about his tries can be found here: https://forum.xda-developers.com/thi...ncept-t3565366
to do so just follow the following steps:
1. start adb shell
2. type the following commands
(alternatively you can also enter the commands in TWRP's terminal)
Code:
mount -t efivarfs efivarfs /sys/firmware/efi/efivars
Code:
printf "\x07\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\x00" > /sys/firmware/efi/efivars/OsIndications-8be4df61-93ca-11d2-aa0d-00e098032b8c
Code:
reboot
!!!as always, be very careful what you do in the bios - the chance for creating a stylish and expensive chopping board is quite high!!!
unfortunately, it seems like you always have to type those commands to enter the bios.
danjac said:
hi folks, thanks to @joesnose we can now enter the yoga book's bios/uefi. you might say 'thank you' to him for this!!!
more about his tries can be found here: https://forum.xda-developers.com/thi...ncept-t3565366
to do so just follow the following steps:
1. boot twrp
2. go to advanced and open the terminal
3. type the following commands
Code:
mount -t efivarfs efivarfs /sys/firmware/efi/efivars
Code:
printf "\x07\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\ x00" > /sys/firmware/efi/efivars/OsIndications-8be4df61-93ca-11d2-aa0d-00e098032b8c
Code:
reboot
!!!as always, be very careful what you do in the bios - the chance for creating a stylish and expensive chopping board is quite high!!!
unfortunately, it seems like you always have to type those commands to enter the bios.
Click to expand...
Click to collapse
About entering the bios. On my YT3P after entering this command just once I am then able to boot bios from twrp reboot screen. This is not working for you danjac?
Also if you make the changes in the bios to get usb keyboard working you can also disable fast boot which allows you to press f7 at boot which allows entry to bios. gets you to boot device selection and pressing esc will take you to other bios options.
And everyone should give thanks to @danjac for trying this on the yogabook.
Sent from my Nexus 6P using Tapatalk
really tnx @danjac , helpful i will try this later
how ever did you flash twrp as your default recovey?
Code:
mount -t efivarfs efivarfs /sys/firmware/efi/efivars
Code:
printf "\x07\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\ x00" > /sys/firmware/efi/efivars/OsIndications-8be4df61-93ca-11d2-aa0d-00e098032b8c
Code:
reboot
Not working for me (Yoga book android WiFi only).
What means printf symbols? Unicode characters? If yes, space between "\x00\ x00" is needed?
I tried to insert commands three times, and tried to use "Reboot BIOS" in TWRP. No profit. Device booting in android.
razielvamp said:
Code:
mount -t efivarfs efivarfs /sys/firmware/efi/efivars
Code:
printf "\x07\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\ x00" > /sys/firmware/efi/efivars/OsIndications-8be4df61-93ca-11d2-aa0d-00e098032b8c
Code:
reboot
Not working for me (Yoga book android WiFi only).
What means printf symbols? Unicode characters? If yes, space between "\x00\ x00" is needed?
I tried to insert commands three times, and tried to use "Reboot BIOS" in TWRP. No profit. Device booting in android.
Click to expand...
Click to collapse
try entering commands from adb shell with tablet on android.
Then on your pc copy and paste
printf "\x07\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\ x00" > /sys/firmware/efi/efivars/OsIndications-8be4df61-93ca-11d2-aa0d-00e098032b8c
Sent from my Nexus 6P using Tapatalk
razielvamp said:
Code:
mount -t efivarfs efivarfs /sys/firmware/efi/efivars
Code:
printf "\x07\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\[COLOR="Red"] x00[/COLOR]" > /sys/firmware/efi/efivars/OsIndications-8be4df61-93ca-11d2-aa0d-00e098032b8c
Code:
reboot
Not working for me (Yoga book android WiFi only).
What means printf symbols? Unicode characters? If yes, space between "\x00\ x00" is needed?
I tried to insert commands three times, and tried to use "Reboot BIOS" in TWRP. No profit. Device booting in android.
Click to expand...
Click to collapse
no 'space'!!!!
there is/was one in the original thread (see the last x00) ...so it also was the reason why it didn't work for me from adb shell. presumably i just ignored the space when typing it manually in twrp...
now it also works from pc/adb...
I corrected the OP! thanks for reporting back!
Ok. I get BIOS but OTG keyboard not working. Halo keyboard too.
I can use only vol up, vol down and power buttons. But I need "ESC" button too, in other case I can not escape submenus.
I got!
long press VolUP = return.
But still do not understand how select usb device in boot order. It seems like BIOS not support OTG function, so how can I change for boot from USB drive when it not detected?
razielvamp said:
Ok. I get BIOS but OTG keyboard not working. Halo keyboard too.
I can use only vol up, vol down and power buttons. But I need "ESC" button too, in other case I can not escape submenus.
I got!
long press VolUP = return.
But still do not understand how select usb device in boot order. It seems like BIOS not support OTG function, so how can I change for boot from USB drive when it not detected?
Click to expand...
Click to collapse
Device manager......
System setup........
android.......
Uefi secure BOOT=disable.
South cluster configuration.......
Usb configuration.....
default drd CONFIG=hostmode
Usb VBUS=on.
that's it save changes and exit. Next time you boot to bios you can use keyboard connected via otg to use bios. You can also select next boot device in bios boot manager.
If you want to be able to interupt boot process to select boot device also disable fast boot under boot category in bios . This will mean you get a black screen with progress bar on power on but allows use f7 to select boot device.
After booting another os from usb it often takes 3 boots to get back to android, don't panic.
Sent from my Nexus 6P using Tapatalk
joesnose said:
Device manager......
System setup........
android.......
Uefi secure BOOT=disable.
South cluster configuration.......
Usb configuration.....
default drd CONFIG=hostmode
Usb VBUS=on.
that's it save changes and exit. Next time you boot to bios you can use keyboard connected via otg to use bios. You can also select next boot device in bios boot manager.
If you want to be able to interupt boot process to select boot device also disable fast boot under boot category in bios . This will mean you get a black screen with progress bar on power on but allows use f7 to select boot device.
After booting another os from usb it often takes 3 boots to get back to android, don't panic.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Hello Guys and Girls,
Sorry for my english, which is not my mother tongue.
Just to say that after reading a lot in XDA folder (thanks to the people who provided how to root/use TWRP and access Bios)
I managed to boot from USB key but I have a acpi-bios-error ( no matter what I changed in the bios related to acpi) while intalling windows 10 32/64 bits.
I would like to know if someone met this issue and solved it somehow ?
By any chance, is there someone (who was able to boot to W10) who can tell which software they use to make their usb bootable ?
I gave up for the moment (I spent too much time on it, need to rest lol)
Thank you for reading my post,
Sweetgeex said:
Hello Guys and Girls,
Sorry for my english, which is not my mother tongue.
Just to say that after reading a lot in XDA folder (thanks to the people who provided how to root/use TWRP and access Bios)
I managed to boot from USB key but I have a acpi-bios-error ( no matter what I changed in the bios related to acpi) while intalling windows 10 32/64 bits.
I would like to know if someone met this issue and solved it somehow ?
By any chance, is there someone (who was able to boot to W10) who can tell which software they use to make their usb bootable ?
I gave up for the moment (I spent too much time on it, need to rest lol)
Thank you for reading my post,
Click to expand...
Click to collapse
With windows I always get the acpi bios error! I have tried many bios options but obviously with caution. Always the error. I keep trying with my "win to go" usb stick.
This error is also quite generic so its hard to know what is causing it.
Sent from my Nexus 6P using Tapatalk
Many Thanks for the answer,
I guess this will be a blocking issue for everyone.
I "heard" on other forums that we might need to upgrade the bios, I don't think it will be possible from Android side.
(I saw there is a tool on Lenovo support site)
Sweetgeex said:
Many Thanks for the answer,
I guess this will be a blocking issue for everyone.
I "heard" on other forums that we might need to upgrade the bios, I don't think it will be possible from Android side.
(I saw there is a tool on Lenovo support site)
Click to expand...
Click to collapse
Or possibly the current bios needs dumping and editing to allow "hidden options". I did see some pics during searching of a similar cherry view bios but there was a "select os" option that does not show in mine.
Sent from my Nexus 6P using Tapatalk
joesnose said:
Or possibly the current bios needs dumping and editing to allow "hidden options". I did see some pics during searching of a similar cherry view bios but there was a "select os" option that does not show in mine.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Wooh, maybe we are almost there !
I guess the time has come to wait and see....
---------- Post added 25th April 2017 at 12:09 AM ---------- Previous post was 24th April 2017 at 11:56 PM ----------
Sweetgeex said:
Wooh, maybe we are almost there !
I guess the time has come to wait and see....
Click to expand...
Click to collapse
Just a check, did you go under system-setup >> south cluster configuration >> SCC configuration >> SCC eMMC Support & SCC SD Card Support (internal and SDcard)
here we can set ACPI mode/PCI Mode or disable
I'm afraid that it will remove android, but it might be a key issue.
Sweetgeex said:
Wooh, maybe we are almost there !
I guess the time has come to wait and see....
---------- Post added 25th April 2017 at 12:09 AM ---------- Previous post was 24th April 2017 at 11:56 PM ----------
Just a check, did you go under system-setup >> south cluster configuration >> SCC configuration >> SCC eMMC Support & SCC SD Card Support (internal and SDcard)
here we can set ACPI mode/PCI Mode or disable
I'm afraid that it will remove android, but it might be a key issue.
Click to expand...
Click to collapse
Sorry missed your post there.
I have tried many things in bios so its hard to remember them all. I think i tried pci mode and also disabled.
Also it might be good if people post what they are trying which could be then added to the first post.
And, i was changing one option at a time then reverting the changes after failed boot, there is a possibility that multiple changes are needed.
Sent from my Lenovo YT3-X90F using Tapatalk
No worries,
Are we agreed that if the installation succeed, it will remove android, right ?
Sweetgeex said:
No worries,
Are we agreed that if the installation succeed, it will remove android, right ?
Click to expand...
Click to collapse
agreed.
Like I said I was mostly trying with my "win to go" usb drive. That is a complete win 10 os on a usb stick, boots just fine on other pc's I have.
I would not recommend full install at the moment for two reasons. 1) who knows what kind of driver issues/problems there will be. 2) would returning to android work if whole device was overwritten, losing bootloader etc.
Sent from my Nexus 6P using Tapatalk
Alright, thank for clearing this up.
I guess that for the moment, we need to set the issue with ACPI, I will keep looking to other topics and forums here and there.
If I found anything, I will post it here.
Many thanks for your answers.
Boot with linux??
Good morning, has anyone tried doing this but with any linux distro? i'm not sure which one is compatible with our device
joao1979 said:
Good morning, has anyone tried doing this but with any linux distro? i'm not sure which one is compatible with our device
Click to expand...
Click to collapse
I have booted several versions of linux and android x86 on my yogatab3pro.
Would like to hear your findings.
on yt3p all need the nomodeset flag in order to boot. This of course means no hardware accelleration.
for me no touch , no sound and no hardware accelleration but they will boot.
Oh and there is some cherrytrail targeted distros. One by linuxium and another called xjubutab.
For reference.
https://forum.xda-developers.com/th.../ubuntu-yoga-tab-3-pro-proof-concept-t3565366
Sent from my Nexus 6P using Tapatalk
unfortunately i didn't find anything useful for us but i´ll keep searching for a solution, i don´t know if it´s possible to update or downgrade an android bios (i´m not an expert on this matter)
First time posting and I wanted to say thank you to all the excellent talent here on XDA! None of this would have been done without the work of so many people.
I have a Moto G Play (2021) (XT2093-4) that I recently purchased (Best Buy - $159 US/Carrier Unlocked) and I wanted to document my adventure in to rooting, making '/system' RW, and fixing the missing LED notification light (hint: I used the charging light) (hint^2: It's not required to make '/system' RW in order to fix the LED notification light - I just wanted more control over my phone).
First, "OEM unlocking" was greyed out for me, but became available after several days of having the phone online with a SIM card.
I followed the instructions here to unlock the bootloader and root with Magisk (Non-TWRP). Along with these instructions.
Once bootloader is unlocked, you will need the 'boot.img' file from your stock firmware. I used the "Rescue and Smart Assistant" utility to grab a copy of the stock firmware (GUAMNA_RETAIL_QZAS30.Q4_39_35_9_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml) and extracted the "boot.img" file for the next steps.
Continue installing Magisk (Filenames may be different! Don't just copy and paste.):
Code:
adb install Magisk-v23.0.apk
adb push boot.img /sdcard/Download
(Follow the instruction on your phone to patch 'boot.img' in Magisk)
adb pull /sdcard/Download/magisk_patched-23000_aKKMt.img
adb reboot bootloader
fastboot flash boot_a magisk_patched-23000_aKKMt.img
fastboot flash boot_b magisk_patched-23000_aKKMt.img
You should now have a working, rooted Moto G Play. You can just stop here and have fun with your phone, but I noticed that even with root, the system partition was not RW.
I followed these instructions to make '/system' writable (Note: you will need the 'sysrw_repair.zip' that's included in the bundle and a Linux system):
Code:
adb push systemrw_1.32_flashable.zip /data/local/tmp/
adb shell
su
cd /data/local/tmp/
unzip systemrw_1.32_flashable.zip
cd systemrw_1.32/
chmod +x systemrw.sh
./systemrw.sh in=`ls -l /dev/block/by-name/super | awk '{print $NF}'` out=/data/local/tmp/systemrw_1.32/img/super_original.bin size=50
The phone doesn't have enough space to complete 'lpmake' on the device and will end with an "Error 73" code. Running the "sysrw_repair_v1.32" tool on a Linux machine was a workaround because it pulls the '*.img" files to your local machine then combines them in to a single '.bin' file. But, before I did that, and because it's really annoying, I made some room to stop the phone from complaining about a lack of space:
(Still on the phone's adb)
Code:
rm ./img/super_original.bin
Now, on the Linux machine, I unzipped 'sysrw_repair_v1.32_proper.zip' then commented out line 39 (where it calls the "flash()" function) of the script (sysrw_repair.sh) because I wanted to flash the "super" partition myself.
(On another Linux terminal)
Code:
cd /path/to/unzipped/sysrw_repair/dir/
chmod +x sysrw_repair.sh
./sysrw_repair.sh
This results in a new folder (img) with a rather large bin file (super_original.bin).
(Back on the phone adb)
Code:
exit # Exit root
exit # Exit adb
adb reboot bootloader
Now it's time to flash the fixed bin file to the "super" partition:
Code:
cd /path/to/unzipped/sysrw_repair/dir/
fastboot flash super ./img/super_original.bin
fastboot reboot
You should be able to login and have a writable '/system':
Code:
adb shell
su
mount -o rw,remount /
No errors should appear.
Last, I like having an LED indicator that tells me that I have an SMS/MMS notification waiting. Motorola thought it would be wise to eliminate that feature altogether instead of having the option to enable it. So, I forced it back on using a startup script that dumps the notifications and greps for some key words. And, if it finds something, it "breaths" the charging LED. The script loops until the notification is gone, then keeps checking for new notifications every 30 seconds. (Note: the "/data/adb/service.d/" directory is used by Magisk like an INIT service):
(Still root on the phones adb)
Code:
cd /data/adb/service.d/
cat <<EOF > ledfix.sh
#!/bin/sh
while true; do
if dumpsys notification | egrep NotificationRecord | egrep sms > /dev/null
then
if [[ $(cat /sys/class/leds/charging/breath) == 0 ]]
then
echo 1 > /sys/class/leds/charging/breath
sleep 2
continue
else
sleep 2
continue
fi
elif egrep 'Charging' /sys/class/power_supply/battery/status > /dev/null
then
if [[ $(cat /sys/class/leds/charging/breath) -ne 0 && $(cat /sys/class/leds/charging/brightness) -ne 0 ]]
then
echo 0 > /sys/class/leds/charging/breath
echo 255 > /sys/class/leds/charging/brightness
elif [[ $(cat /sys/class/leds/charging/breath) == 0 && $(cat /sys/class/leds/charging/brightness) == 0 ]]
then
echo 255 > /sys/class/leds/charging/brightness
else
continue
fi
else
echo 0 > /sys/class/leds/charging/breath
echo 0 > /sys/class/leds/charging/brightness
fi
sleep 30
done
EOF
chown 0.0 ledfix.sh
chmod 0755 ledfix.sh
reboot
Now, the charging light will fade off and on about every 2 seconds if there's an SMS/MMS notification waiting. And will check for notifications every 30 seconds. I'm sure someone can come up with a better way of doing this, but this was a nice quick-and-dirty way to get what I wanted.
Hope this helps!
I created an account to say thank you for this, I have already done a good portion, having unlocked the bootloader, the problem is the Rescue Smart Assistant, it won't let me log in, it keeps telling me it can't connect, and the GUI is different because of an update, there is no download button inside the program, only a greyed out rescue button. How did you manage to make the backup Boot.img? Maybe you are using a different OS, and/or version of the program (Not the app, that is already auto-installed), I'm using Windows 10, are you on Linux? I might just need to try from Linux, maybe in a VM.
I was trying to do this before I found this post, and have already installed ADB, the SDK, fastboot, and Motorola Drivers, I just need a way to get the Boot.img, and to patch it, also figure out how to flash it. The last android I rooted with a custom rom was the HTC EVO 4G with Oreo/Jellybean, so I'm a little rusty, but am able to understand technical jargon.
If anyone could help, that would be awesome. I've reinstalled different versions of Rescue Smart Assistant as well, they always upgrade on boot, same problem. I've added exceptions to my firewall and everything.
UPDATE: Was about to post this when I had updated from android 10 to 11 and decided to try logging in again a little closer to my router, to see if the connection was timing out, I think that was the cause, as I can now sign in, and the GUI seems correct from the first appearance. I don't see why I should have any trouble following the rest of the guide, but feel I should share my trials and frustrations anyways, for anyone else experiencing the same,
Thanks again.
PROFSLM said:
I created an account to say thank you for this, I have already done a good portion, having unlocked the bootloader, the problem is the Rescue Smart Assistant, it won't let me log in, it keeps telling me it can't connect, and the GUI is different because of an update, there is no download button inside the program, only a greyed out rescue button. How did you manage to make the backup Boot.img? Maybe you are using a different OS, and/or version of the program (Not the app, that is already auto-installed), I'm using Windows 10, are you on Linux? I might just need to try from Linux, maybe in a VM.
I was trying to do this before I found this post, and have already installed ADB, the SDK, fastboot, and Motorola Drivers, I just need a way to get the Boot.img, and to patch it, also figure out how to flash it. The last android I rooted with a custom rom was the HTC EVO 4G with Oreo/Jellybean, so I'm a little rusty, but am able to understand technical jargon.
If anyone could help, that would be awesome. I've reinstalled different versions of Rescue Smart Assistant as well, they always upgrade on boot, same problem. I've added exceptions to my firewall and everything.
UPDATE: Was about to post this when I had updated from android 10 to 11 and decided to try logging in again a little closer to my router, to see if the connection was timing out, I think that was the cause, as I can now sign in, and the GUI seems correct from the first appearance. I don't see why I should have any trouble following the rest of the guide, but feel I should share my trials and frustrations anyways, for anyone else experiencing the same,
Thanks again.
Click to expand...
Click to collapse
You can also get the firmware from
Lolinet Mirrors
https://t.me/MotoUpdatesTracker
Search for Firmware by codename, software channel, Software Version, and build #
So I wasn't going crazy when I could swear a LED notification light in the upper right side above the screen blinked once whenever I rebooted the phone?
Why would Motorola include such a thing and not utilize it for more than merely a boot up indicator? Like I dont even get to see it come on while charging, it literally only blinks once during boot and that's it.
mario0318 said:
So I wasn't going crazy when I could swear a LED notification light in the upper right side above the screen blinked once whenever I rebooted the phone?
Why would Motorola include such a thing and not utilize it for more than merely a boot up indicator? Like I dont even get to see it come on while charging, it literally only blinks once during boot and that's it.
Click to expand...
Click to collapse
I know!
I don't know what triggers that light to come on. I even waited until the battery was at 6% and the light still never came on.
So, I updated the script above to make the light go full brightness if the battery is charging. The order matters, so if a notification comes in while charging, it'll "breath" the LED. Also, if the battery is full, then the light will turn off. Kind of telling you that it's time to unplug.
I followed these steps and my touch screen stopped working. I had previously installed twrp already on it while trying to learn how to root it, and when i boot into fastboot it goed through twrp, i also used the boot.img file from lolinet, not sure which of these caused the issue. Interestingly though, the touch screen does work whilst in twrp. any suggestions on how to fix or what would be causing it? Phone does work with usb mouse over OTG
jorduino said:
I followed these steps and my touch screen stopped working. I had previously installed twrp already on it while trying to learn how to root it, and when i boot into fastboot it goed through twrp, i also used the boot.img file from lolinet, not sure which of these caused the issue. Interestingly though, the touch screen does work whilst in twrp. any suggestions on how to fix or what would be causing it? Phone does work with usb mouse over OTG
Click to expand...
Click to collapse
Are you absolutely sure you used the correct boot.img from an image version exactly matching your phone variant version?
mario0318 said:
Are you absolutely sure you used the correct boot.img from an image version exactly matching your phone variant version?
Click to expand...
Click to collapse
Im not completely sure how to get the right file, but I think the first time it was the wrong one, but then when i got what i thought was the right one, it just didn't work at all and I had to recovery flash it. I had just updated so maybe the correct image wasn't available yet. Im going to try again though
Oh! Hello @latentspork. Thanks for your interest in my SystemRW project. I just came across this thread randomly...
I'm happy you got my script to work on your Motorola device by using the included sysrw_repair script
Please feel free to send me your log files from script folder. Thanks. It's useful for further development of the script
latentspork said:
The phone doesn't have enough space to complete 'lpmake' on the device and will end with an "Error 73" code. Running the "sysrw_repair_v1.32" tool on a Linux machine was a workaround because it pulls the '*.img" files to your local machine then combines them in to a single '.bin' file. But, before I did that, and because it's really annoying, I made some room to stop the phone from complaining about a lack of space:
Click to expand...
Click to collapse
That's not 100% accurate. Lpmake error 73 means CAN'T_CREATE and has nothing to do with error 70 (insufficient space).
To this day I still don't know exactly what causes error 73 on some devices (mostly Motorola and others) but it looks like some kind of kernel panic. If anyone knows how to avoid this error 73 in Android please let me know! Thanks!
Yes that's true the included sysrw_repair script (Linux only) pulls the image files from the phone to your computer and attempts to run the same lpmake command with the same arguments that just failed with error 73 on the phone itself and now all of a sudden it just works in Linux. Go figure.
latentspork said:
(Still on the phone's adb)
Code:
rm ./img/super_original.bin
Click to expand...
Click to collapse
Why would you delete the super_original.bin ? That's your stock read-only super image which by default is automatically dumped by script for backup purposes in case you ever get a bootloop.
And if you launch the script by specifying a custom input value (in=x) like in your example above then you won't even have a super_original.bin file to begin with because script will skip the whole dumping of original super image process.
latentspork said:
This results in a new folder (img) with a rather large bin file (super_original.bin).
Click to expand...
Click to collapse
I think you mean super_fixed.bin
latentspork said:
Now it's time to flash the fixed bin file to the "super" partition:
Code:
cd /path/to/unzipped/sysrw_repair/dir/
fastboot flash super ./img/super_original.bin
fastboot reboot
Click to expand...
Click to collapse
Here in your instructions you are manually flashing the wrong file. Shouldn't you be flashing super_fixed.bin to your super partition?
Usually I only flash the super_original.bin to get back out of a bootloop...
latentspork said:
Now, on the Linux machine, I unzipped 'sysrw_repair_v1.32_proper.zip' then commented out line 39 (where it calls the "flash()" function) of the script (sysrw_repair.sh) because I wanted to flash the "super" partition myself.
Click to expand...
Click to collapse
See that's why I included that automatic flash() function in the repair script. Then you don't have to worry about manually flashing the wrong file to your super partition
Enjoy a fully read/write-able device!
Great news! New SystemRW version coming soon!
@lebigmac
I really appreciate the reply and the tool! It did work really well on my model (XT2093-4).
That's not 100% accurate. Lpmake error 73 means CAN'T_CREATE and has nothing to do with error 70 (insufficient space).
To this day I still don't know exactly what causes error 73 on some devices (mostly Motorola and others) but it looks like some kind of kernel panic. If anyone knows how to avoid this error 73 in Android please let me know! Thanks!
Click to expand...
Click to collapse
I only assumed that "Error 73" was caused by insufficient space, because the phone really did run out of space. I noticed that the phone was out of space because I got a home screen notification warning, asking me to free up space. I confirmed it with a "df -h" at the shell. Apparently, the OS takes up almost 15GB. When you add the ".img" files, there's only about 5GB left. There wasn't enough room to complete the ".bin" file. Maybe I could have used an SD card or something.
You're probably correct in that "Error 70" is the correct error for that, but on my phone, I never saw that error. I did notice that the tool was still trying to write data as the phone ran out of space, then it would throw the "Error 73". Maybe it didn't register the lack of space, or just an oddity with my model? No idea.
Why would you delete the super_original.bin ?
Click to expand...
Click to collapse
This is the file that was created when I initially ran the "./systemrw.sh" command on the phone. The result of running the command on the phone were several ".img" files and a very large "super_original.bin", but it was incomplete because the command threw an "Error 73". I was following your instructions, and I noticed that the output name of the file was "original" instead of "fixed". I probably could of outputted it to a new name to reduce confusion, but I didn't really care too much about the name as long as I had a working file.
I think you mean super_fixed.bin
...
Shouldn't you be flashing super_fixed.bin...
Click to expand...
Click to collapse
Normally, yes. But the Linux script also outputted the filename "super_original.bin". Again, as long as it worked, I was okay with it. The commands I used above were the exact commands that I ran at the time. I copied them from the terminal consoles I was using. So I don't know why it wasn't outputting the correct filename (again, I was following your instructions and was a little confused that the names came out differently - I just figured I was doing something wrong like not use the proper output command or something).
Then you don't have to worry about manually flashing the wrong file to your super partition...
Click to expand...
Click to collapse
I was really just being cautious because my previous phone broke and I didn't have a fallback.
But, at no point were there two bin files (original and fixed), so there wasn't much confusion. Where I originally had just ".img" files before running the script, I now had a single ".bin" file. I knew that was the file I needed.
But again, thank you for all the hard work on this tool! I was reading that it's worked on lots of different model phones, and it's always good to see the open source community doing things that help all kinds of people.
For moto notification for this phone at least use https://play.google.com/store/apps/details?id=br.com.itsmeton.motoledreborn or moto led reborn from the play store it just works
Hi, sorry. This can be removed. I put it in place because I was having issues with the xda app. For whatever reason, every time I tried to share this particular post, it would share a link for the post which I used originally, rather than the current post. I knew that if I commented I could get back here easily on my PC.
So what is the place holder for