Database Info

[Q] CF-root and install-recovery.sh, need info

Hi,
I tried to receive an answer in the official cf-root thread, but nobody answered to me.
I have a question about the install-recovery.sh in system/etc that is rewrited(?) by the CF-autoroot.
I know that (please correct me if i'm wrong) this file is used to start the daemonsu at startup
Code:
/system/xbin/daemonsu --auto-daemon &
but i have seen that there are also other commands in the original file and if i remember, these commands are
used to restore the stock recovery in the case of a failing checksum at android boot... i'm right?
After rooting, can I append the command above to the other commands just inside the original install-recovery.sh just to keep
also the original functionality of the script and start the daemon at the same time?
I would like to receive OTA, i want to keep anyway the stock recovery because i need root access only.
Thanks very much in advance

I can't remember what the other commands are now but yes, they're for reinstalling recovery. Afaik there's no reason why you can't append the command however there is also no need to
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit

[Q&A] XiaomiTool [WIN] [UNIX}

Q&A for XiaomiTool [WIN] [UNIX}
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for XiaomiTool [WIN] [UNIX}. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

XiaomiTool not working on my PC.
Here a video:
youtu. be/ vzLm7wjHr6A
Sorry, for the link, i have no 10 message yet...
Seems that XiaomiTool can't find /tools/detect-terminal.sh and run.sh
How can i resolve this issue?
Thanks.

I had a quick look into the script. Fun thing is, it tries to access the tools via $TOOLPATH, but this variable is never set.
Just try to add this in line 354 into tools/XTools.sh just after the function is being opened and before the first use of $TOOLPATH
TOOLPATH=`pwd`
so that this:
Code:
init () {
cd $TOOLPATH/tools
chmod +x detect-terminal.sh
should look like this then
Code:
init () {
TOOLPATH=`pwd`
cd $TOOLPATH/tools
chmod +x detect-terminal.sh
Mi4User said:
XiaomiTool not working on my PC.
Here a video:
youtu. be/ vzLm7wjHr6A
Sorry, for the link, i have no 10 message yet...
Seems that XiaomiTool can't find /tools/detect-terminal.sh and run.sh
How can i resolve this issue?
Thanks.
Click to expand...
Click to collapse

Thank toxic_garden
Something has change, but XiaomiTool doesn't start...
youtu .be/jj9 ESBBwhFc

Mi4User said:
Thank toxic_garden
Something has change, but XiaomiTool doesn't start...
youtu .be/jj9 ESBBwhFc
Click to expand...
Click to collapse
i tried to start it myself, but it doesn't work in my machine either. When i try to run the tool manually, i get a few exceptions. Seems like there are still some issues within the linux version....
Code:
[email protected]:~/mi4/tools$ vi XTools.sh
[email protected]:~/mi4/tools$ ./XiaomiTool
QMetaObject::connectSlotsByName: No matching signal for on_pushButton_clicked()
libGL error: failed to load driver: swrast
QXcbConnection: XCB error: 145 (Unknown), sequence: 158, resource id: 0, major code: 140 (Unknown), minor code: 20

Update: got it working now. I started the Tool from a remote SSH-Session and therefore die UI didn't show up because of my crappy X-Server on the windows side. When i launch the tool directly from the Linux-Workstation, it runs perfectly fine. Did you try to launch the Tool as i suggested above?

Mhm...maybe I did not understand...
I'm already launching XiaomiTool directly from a Linux Workstation...

Mi4User said:
Mhm...maybe I did not understand...
I'm already launching XiaomiTool directly from a Linux Workstation...
Click to expand...
Click to collapse
what i meant was: did you try running "XTools.sh" from the tools-directory and looking at it's output?

thanks for the tool, will try it after i finish downloading, and will tell my experience on using this tool on mi4

Ok I have a problem, and I am sure it is all me, but when I try to do anything with the tool it says it cannot find my device. Can anyone please help me fix this.

Install Mi Phone Manager with english patch, it also installs drivers.

[Q&A] terminal emulator initialization

Q&A for terminal emulator initialization
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for terminal emulator initialization. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

terminal emulator initialization
I wanted to have a few custom aliases loaded into the terminal automatically every time it started
so I searched google for some help and found this thread. You helped me on my path. Thank You!
This is what I came up with...
You need root access to do any of this.
mkshrc file is located here:
/system/etc
/etc
is just a link to the /system/etc directory.
I added this code to the mkshrc file at the bottom just above the line where it indicated to add any additional code:
Code:
[ -f /system/etc/.aliases ] && . /system/etc/.aliases
save and exit.
(Code means: Test if file /system/etc/.aliases exists, and only if it does, source that file.)
(.aliases is just a file name I chose, you can use any file name)
I then created the empty file .aliases in the /system/etc directory and set it's permissions to rw-r--r--
Code:
touch /system/etc/.aliases && chmod 644 /system/etc/.aliases
Placed my aliases in the .aliases file saved and reboot.
Code:
c='clear'
xx='exit'
All works.
The file you source can be a sh script with a shabang up top as well.
I have another file I source for custom functions that get auto loaded.
Pretty cool.
Thanks a lot, took me a while to even figure out the file I was looking for was the mkshrc file.
(Most system config options and settings are placed in the etc folder on a unix based system.)
Mission success!
(Make custom script to do all this automatically first time when installing new ROMS. Nice.)

Thank You!
Worked like a charm, Just what I was looking for works perfectly on my I9505.
mkshrc found in /etc/
Thanks again!

[Completed] Unknown Device - Trouble Shooting

I'll try to make this as short and concise as possible as the wall of text may crit readers eyes. The device I have isn't your standard tablet, it has no standard manufacturer so no support or stock roms. I am quite novice.
What we know:
Android Version 4.4.4
Kernel Version 3.0.36+ [email protected] #876
Build Number rk3188-eng 4.4.4 KTU84Q
What it is running(was) is very basic, I rooted it and went to install TWRP via the APK installer which is where it all went wrong. Due to the lack of knowledge of the device I installed what I thought would be a similar enough device to not brick the device. Once the device restarted it would no longer boot into the OS, so I went into recovery mode (Dead android) however there are no options or access here.
Moving into ADB, the device does show with a bogus serial.
Code:
0123456789ABCDEF recovery
I can push and pull data, however other commands such as
Code:
adb reboot sideload-auto-reboot
results in cmd to permanently hang.
Shell commands all return with not being found.
Code:
#ls
/system/bin/sh: ls: not found
#
I would love to either get her back up and running or completely install a new rom. Thoughts comments and concerns are all welcome!

Echeltek said:
I'll try to make this as short and concise as possible as the wall of text may crit readers eyes. The device I have isn't your standard tablet, it has no standard manufacturer so no support or stock roms. I am quite novice.
What we know:
Android Version 4.4.4
Kernel Version 3.0.36+ [email protected] #876
Build Number rk3188-eng 4.4.4 KTU84Q
What it is running(was) is very basic, I rooted it and went to install TWRP via the APK installer which is where it all went wrong. Due to the lack of knowledge of the device I installed what I thought would be a similar enough device to not brick the device. Once the device restarted it would no longer boot into the OS, so I went into recovery mode (Dead android) however there are no options or access here.
Moving into ADB, the device does show with a bogus serial.
Code:
0123456789ABCDEF recovery
I can push and pull data, however other commands such as
Code:
adb reboot sideload-auto-reboot
results in cmd to permanently hang.
Shell commands all return with not being found.
Code:
#ls
/system/bin/sh: ls: not found
#
I would love to either get her back up and running or completely install a new rom. Thoughts comments and concerns are all welcome!
Click to expand...
Click to collapse
Hello,
Thanks for using XDA Assist.
There's no dedicated forum for your device here in XDA.Try posting your query in Android Q&A,Help and Troubleshooting or in one of the noob friendly Q&A thread here->[Ask Any Question][Newbie Friendly] .Experts there may be able to help you
___
v7
XDA Assist

[Samsung] Partition information from Download Mode?

Is there a way to get any information about partitions while a phone is in Download mode?
For example, can I see partition sizes? Can I copy/download images? Generate a hash?
This post shows four useful techniques, but all require ADB (not available to me)
https://android.stackexchange.com/questions/5232/how-can-i-view-the-android-internal-partition-table
df, cat /proc/mounts, cat /proc/partitions, ls -al /dev/block/platform/msm_sdcc.1/by-name
My Galazy A3 (2016) is currently exhibiting a "Custom binary blocked by FRP lock" bootloop, and I am studying how to fix it without any data loss. I've read that I need to flash the stock boot.img and recovery.img
Seems that general techniques regarding partition information should apply to most (all?) current Samsung phones.
I'm curious if I can find any information about what is currently on my phone, before flashing.

ScottHW said:
Is there a way to get any information about partitions while a phone is in Download mode?...
Click to expand...
Click to collapse
I don't have this device but, the following is the dedicated area of the forum for your device.
https://forum.xda-developers.com/samsung-a-series
With that stated...
The following threads may have some information similar to your issue and a possible solution or you can post your issue for some member guidance.
https://forum.xda-developers.com/showthread.php?t=3694816
https://forum.xda-developers.com/showthread.php?t=3619425
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE