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

[Completed] irulu 10.1 root/remount problems solved

I own an irulu K1001L1 10.1 (build number A20_K1001_K1001L1.20130713), a cheap one.
Many people complain about "partial rooting" and being unable to remount system in rw mode. Clueless as I was, I had tried several times with Uberizer, z4root and SRSroot, to no avail (the problem is not in the root, in my tablet su came by default in xbin directory).
D_rex (http://forum.xda-developers.com/showthread.php?t=2606510&page=2) found an effective solution which also helped in my situation: I think my tablet came with "su" application by default (notice overclocking worked) but due to /dev/block/nandd ext4 partition (I think /system starts at some offset) containing some errors (seen in dmesg) and due to this partition having the "s_errors" flag (behavior when errors detected) set to "mount read-only (02)", the partition is ALWAYS mounted read only, and remount as root doesn't change anything. More info on this ext4 option can be found here
For me, the solution that worked was changing that flag s_errors to continue (01). I wasn't able to run e2fsck as the partition is already mounted; and I wasn't able to do a fsck in recovery mode since the recovery mode of this tablet lacks seems to lack both shell and e2fsck.
Tune2fs (old version precompiled here) can change that flag in the partition. Using adb shell I pushed it to de device, set attribute as executable and run it, successfuly changing that "behavior when errors detected" in both partitions.
It has been suggested filesystem errors are linked to stability and realiability problems. Unfortunately this tablet lacks a version of CWM o TWRP as a recovery custom rom. I also adjusted the "max-mount-counts" value via tune2fs -c hoping it forces Android to run e2fsck, but it seems dmesg keeps displaying errors. I can only hope this problem is given more attention by developers.
After this I used the usual tools to root the device, noticing I had spent many hours in this cheap tablet.
On a side note, the adb driver setup tool found here didnt work for me (it seems &USER_PROFILE% in the .bat file should be replaced by "%USER_PROFILE%" and Desktop should be replaced according to the language of your operating system. Nevertheless the tool didn't work for me and I had to install another driver found in Uberizer distribution as the official "android_winusb.inf" didn't work in my Windows XP computer.
Thanks to the creators of tune2fs, to D_rex and other people/programs mentioned here. This is my experience with this problem; I'm not responsible if anyone tries this and bricks his device. All brands are property of their owners.
edition: should also mention by default now my tablet mounts in read-only mode (which is of course safer) but lets me change to rw whenever I want

Hi there,
Sorry but this forum is not for guide and tutorials.
The mission of XDA Assist is to provide basic help to those who have tried searching but can't find what they are looking for and need assistance. This is not a "helpdesk" providing technical assistance but more to point you in the correct direction with your problem. Perhaps you can't find posts on how to root your phone, install custom recovery or maybe you have questions about how to navigate and use features on the site.
Click to expand...
Click to collapse
You can post your thread, in this forum:
> Android Development and Hacking > Android Q&A, Help & Troubleshooting
Good luck
Thread closed

[Q&A] [XT925][XT926][CWM Advanced Edition] PhilZ Touch

Q&A for [XT925][XT926][CWM Advanced Edition] PhilZ Touch
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 [XT925][XT926][CWM Advanced Edition] PhilZ Touch. 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!

excuse me phil..or everyone else, may ask yours xt926 'scatter' file? if you don't mind, please generated it and post here (the generated file isn't big).
how to generate scatter:
1. plug device
2. open adb, and type:
adb shell
Code:
cat /proc/mtd
or
Code:
cat /proc/emmc
to save it into yours sd-card, type :
Code:
cat /proc/mtd > /sdcard/firmware.info
or
Code:
cat /proc/mtd > /sdcard/firmware.info
i need the file for some research
tvm

I have to admit, I'm curious. Never heard of a "scatter" file. What does this do? I understand the shell commands but not why the data is important.
EDIT: OK, I googled it. Is this a MediaTek only thing? It appears to be. The HD isn't a MediaTek SoC. Seems the scatter file is used in de-bricking devices. And there's no /proc/mtd or /proc/emmc on my HD.

i'm so sorry if mt question make you admit
but if you don't mind, would you like to try
Code:
cat /proc/sys/kernel/modprobe
and your guess was correct, it flash for mtdk. please post you result after typing above command on my thread instead of reply here. we won't blame a thread with defferent content
thanks

[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

Need to flash a TWRP backup with fastboot

Hi. I have to flash a TWRP backup and can't do it thorugh custom recovery due I have a Yotaphone (the phone with a LCD screen by one side and a eInk screen by the other side) and the LCD screen is broken, so I have to use fastboot or adb (as far I know). I cannot even install a ROM because it needs the LCD screen for the first start.
The question if I can do it, cause I know it could be problems with formats.
(I asked this on Yotaphone specific xda forum but no one answered)
Thanks

eReader Fan said:
Hi. I have to flash a TWRP backup and can't do it thorugh custom recovery due I have a Yotaphone (the phone with a LCD screen by one side and a eInk screen by the other side) and the LCD screen is broken, so I have to use fastboot or adb (as far I know). I cannot even install a ROM because it needs the LCD screen for the first start.
The question if I can do it, cause I know it could be problems with formats.
(I asked this on Yotaphone specific xda forum but no one answered)
Thanks
Click to expand...
Click to collapse
You would probably have better luck flashing the stock firmware or have someone with the same device create an adb backup then restore it via adb.
Or if you know which individual .img files you need, have them pull a copy of whichever individual .img files you need(for example: system, boot, etc) then fastboot flash them or use adb shell to dd the .imgs back onto your device in the partitions they belong in.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

@Droidriven ,you are right about it would be easy to fash a stock rom, but the LCD screen is necessary for that due the first boot. Maybe I am a little lucky 'cause I live with person who has the same device as me.
I tried the adb backup -all but it seems to just make a backup of the personal data.
Making a dd backup patition would be the better, but for some reason my device isn't recognized as a MTP device and can only connect in PTP. Tried to change the configuration on the phone but still only works with PTP, and I think in PTP mode doesn't have a mounted folder where I can make this stuff.
What I don't know how to do is the dd within the adb shell. It will work connected in PTP mode?

eReader Fan said:
@Droidriven ,you are right about it would be easy to fash a stock rom, but the LCD screen is necessary for that due the first boot. Maybe I am a little lucky 'cause I live with person who has the same device as me.
I tried the adb backup -all but it seems to just make a backup of the personal data.
Making a dd backup patition would be the better, but for some reason my device isn't recognized as a MTP device and can only connect in PTP. Tried to change the configuration on the phone but still only works with PTP, and I think in PTP mode doesn't have a mounted folder where I can make this stuff.
What I don't know how to do is the dd within the adb shell. It will work connected in PTP mode?
Click to expand...
Click to collapse
Is USB debugging enabled?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Yes, debuggind mode is on. In PTP mode, adb sees my device correctly, in MTP mode appears like ???????

I think maybe the answer is where that you mentioned about "adb shell". As long as I can't see the phone mounted in MTP mode it's the only way I see. Now I am searching for the way on pointing the dd output file outside the adb shell. So the process is:
BACKUP:
-adb shell > dd partitions saving them outside the phone
FLASHING:
-fastboot partition by partition
Another problem I have is to know which partion is each, 'cause with "mount" I don't get so much information and with "cat /proc/partitions" only have 13 partitions with their size and no more info. I am looking what to "adb push" that can help me. Maybe install busybox.
Trying to backup&restore without MTP, without access to the recovery nor SDcard... Harder is impossible!!!

eReader Fan said:
I think maybe the answer is where that you mentioned about "adb shell". As long as I can't see the phone mounted in MTP mode it's the only way I see. Now I am searching for the way on pointing the dd output file outside the adb shell. So the process is:
BACKUP:
-adb shell > dd partitions saving them outside the phone
FLASHING:
-fastboot partition by partition
Another problem I have is to know which partion is each, 'cause with "mount" I don't get so much information and with "cat /proc/partitions" only have 13 partitions with their size and no more info. I am looking what to "adb push" that can help me. Maybe install busybox.
Trying to backup&restore without MTP, without access to the recovery nor SDcard... Harder is impossible!!!
Click to expand...
Click to collapse
This command in adb shell or Terminal Emulator should give you your partitions and names(obviously you'd type "su" then press enter then run this command)
ls -l /dev/block/platform/msm_sdcc.1/by-name/
The part with "msm.sdcc.1" might be different for your device. If that command doesn't work I'll help you find what needs to go in that part of the command for your device.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

su is not found inside the adb shell, and I found this is cause is not rooted. I have to do it through TWRP in android 6.
As I said, I have two devices of my model so I hope I find time tomorrow for doing it. I also hope to can flashing it to the other device in fastboot mode or some way it doesn't need the main screen (remember I have a LCD screen and a eInk)
I will say something when I do the root. Thanks

Finally did it!
It appears each partitions clearly with the "ls" command you give to me. The question now is how to dd outside the phone. Have I to mount the pc inside the shell or what?

eReader Fan said:
Finally did it!
It appears each partitions clearly with the "ls" command you give to me. The question now is how to dd outside the phone. Have I to mount the pc inside the shell or what?
Click to expand...
Click to collapse
adb shell should work to dd, you just need to make absolutely certain that you are dd-ing the correct .img to the correct partition(mmcblk0xx), the partition number would go where the xx is.
For example, my recovery.img would be flashed to mmcblk018(the number of my recovery partition.
If you dd an .img to the wrong partition, you'll brick the device, the command has to be exactly correct, no margin for error or easy fix if you get it wrong.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

I know all this stuff, but first I need to make the .img of each partition, and I though with adb shell I could do a dd to outside the phone. The TWRP backup I have isn't .img files, they are .win files.
I searched again if its possible to do that and all I found is the xda thread about doing a workaround with adb forward and busybox. If there is no more options I will do that.
What I thought to do is create a backup of the needed partitions and save them in the userdata free space. I think this have to be possible, but as I cannot use the LCD screen I have to do the backup where I do not have to pass thorugh the first boot configuration, cause it is did in the LCD screen. Which partitions have I to backup? Only system and boot? Or there is another tool for creating .img backups?
EDIT: Also found the twrp adb possibilities (http://www.pocketables.com/2014/10/using-twrps-new-adb-interface.html) but have the same problems than with dd

I frequently modify boot and recovery partitions from within terminal app. Here's what I do to grab the boot partition for example(you likely want BusyBox installed first)
cat /dev/block/bootdevice/by-name/boot >boot.img
or
dd if=/dev/block/bootdevice/by-name/boot of=boot.img
Make changes, then reverse the commands to write back. I think cat gives you a more verbatim copy for initially cloning a partition. I have had success with both.
The question that brought me here is what happens if i flash all partitions from a firmware archive and attempt to upgrade a whole system this way from twrp recovery.....