Database Develop

Boot-Time Auto-SuperLog! [12 Apr 2013]

Boot-Time Auto-Superlog! [12 Apr 2013]
USERS --- TESTERS --- DEVS​Plumb the depths of Middle Droid with Auto-Superlog!​
So…
Your device doesn't finish booting
It reboots on its own (and you may not know it)
An application or feature crashes (and you may not know it)
Generally speaking, any manually-launched app or tool could miss key events leading to random reboot or application crash.
Problem addressed with Auto-Superlog!​
cm10-auto-superlog-v1.0.zip (3MB): http://www.mediafire.com/?cf5f9rq4z7p6gep
This flashable zip is tested working on my Atrix running CWM Recovery 5.0.2.0 and CM10 SuperLite. It should also work on epinter’s CM10 4.1.x builds and on close relatives. Not sure about 4.2.x yet.
In this exciting age of alpha-beta ROM testing, my lightweight Auto-Superlog, presently built on epinter’s versatile CM10 boot image (for demo purposes), can help just about anyone, whether end-user, tester or developer!
In fact it is already helping me track down abnormal battery drain and shutdown problems!
Alternatively instead of flashing the boot-time version, you can extract “auto-superlog.sh” from the flashable zip and manually execute it at run time.
Features
Automatically launches at boot-time under “class_start core” --- just after ROM filesystems are mounted, thus maximizing the likelihood of capturing key events, even if phone does not finish booting
Comprehensive log set includes: system build properties (getprop), kernel configuration file (from /proc/config.gz), kernel dmesg and system logcat --- all in sync, all in ASCII text format, and all stored in a single gzipped, time-stamped tar file on $EXTERNAL_STORAGE/auto-superlog for easy access and analysis.
Android events are quietly, nimbly and continuously streamed via kernel “dmesg” and system “logcat” commands. The dmesg log is pushed at 2-second intervals (default) with a 1MB ring buffer which is cleared on each pass. Logcat is configured to log “main” and “system” events with a generous 10MB buffer to help in discerning error trends.
Access real-time dmesg and logcat output right on your device by tapping the /data/auto-superlog directory using a (root) file explorer.
Log file contents are time stamped using absolute time ([YYYY-]MM-DD HH:MM:SS), enabling users to correlate Android events with the outside world
Filename timestamps show when your system was rebooted
Self-cleaning feature: On reboot, your most recent superlog is gzipped and archived to $EXTERNAL_STORAGE and then is removed from /data/auto-superlog so only your most recent superlog remains on the /data partition.
Shell script: auto-superlog.sh is stored under /system/bin, enabling users to extract and execute it at run-time and/or customize.
How to kill dmesg and logcat? Use the ps and grep commands: http://stackoverflow.com/questions/3117095/stopping-an-android-app-from-console (It’s a sheepish way of saying “mechanization of this feature is still in work” lol)
Instructions
Nandroid Backup current ROM (security blanket)
Flash zip if running epinter CM10 4.1.x or close relative (e.g. SuperLite)
Reboot and relax.
…OR, if you don’t want to flash the zip, but still want the run-time features of auto-superlog, simply extract /system/bin/auto-superlog.sh from zip and do this…
copy auto-superlog.sh to /system/bin (Tip: mount /system/bin as read-write (rw), then revert to ro when done)
chmod 0755 /system/bin/auto-superlog.sh
sh /system/bin/auto-superlog.sh (using Script Manager or other tool, as root)
Click to expand...
Click to collapse
After launching the script, just tap the Home button to resume other activity as the loggers are now running in background. Then you will have real-time streaming dmesg and logcat (as well as getprop and kernel config) at your fingertips --- literally.
The advantage of flashing the zip (if it’s compatible with your ROM) is that you are more likely to capture key events leading to a failed boot, random reboot or application crash.
Screenshots
​
Boot Image Source Code
This is the only change I made to CM10 boot.img...
Code:
ramdisk/init.olympus.rc ...
# sendust7 (12 Apr 2013)
service auto-superlog /system/bin/sh /system/bin/auto-superlog.sh
class core
# class main
# class late_start
user root
group system
# disabled
oneshot
# sendust7 (12 Apr 2013)
Documentation
dmesg: http://unixhelp.ed.ac.uk/CGI/man-cgi?dmesg+8
logcat: http://developer.android.com/tools/debugging/debugging-log.html#outputFormat
Android Encryption: http://source.android.com/tech/encryption/android_crypto_implementation.html
from Android Encryption…"This magic was accomplished by requiring all services to be in 1 of 3 groups: core, main and late_start. Core services are never shut down after starting. main services are shutdown and then restarted after the disk password is entered. late_start services are not started until after /data has been decrypted and mounted.”
Click to expand...
Click to collapse
Thoughts and Ideas: This has been a fun project so far. Time permitting, I may be able to service bug fixes and add more goodies like event filtering.
Disclaimer: Standard disclaimers apply.
Credits:Emerson Pinter (CM10 for Atrix 4g), Cyanogenmod Team

Very nice!
The OS considers the internal SD as EXTERNAL_STORAGE in assigning the env variable which is perhaps the reason you should too:
Booted without external sd mounted:
Code:
[email protected]:/ $ echo $EXTERNAL_STORAGE
/storage/sdcard0
Booted with external sd mounted:
Code:
[email protected]:/ $ echo $EXTERNAL_STORAGE
/storage/sdcard0
Possibly just tweak this part of your script:
Before
Code:
/system/bin/mount -t vfat /dev/block/mmcblk1p1 $EXTERNAL_STORAGE
After
Code:
/system/bin/mount -t vfat /dev/block/mmcblk0p18 $EXTERNAL_STORAGE
This then sends the archive to a location that will always exist (sdcard0).
I mention as I don't always have external SD mounted.
Sent from my MB860 using Tapatalk 2

Thanks sendust7
Good job !

[Q] Loop in bootanimation after update to CROMi-X 7.0.2

Hi to everyone.
I was updating my tab to the latest version of the ROM of sbdags.
Everything was fine until i reboot the tab to use it for the first time: loop in the boot animation and never come out from it.
I came from the previous version of the rom, the Cromi-x 6.1 with 10.26.1.18 bootloader.
The process i use to update was this:
1) wipe of data/factory reset, wipe with format /boot, wipe with format /system
2) Install the CWM recovery 6.0.5.0 and update the bootloader to 11.4.1.17 by flashing they with the file that you can find in the rom page.
3) repeat point 1
4) install the rom by flashing it from an SD. Complete the Aroma installer and answer to every option that it ask to me.
5) reboot the system and stuck in the bootanimation
I use the WW format cause i'm italian and i check the md5
What's wrong? I can go to recovery everytime i need and i have a backup just in case i need it.
Sdbags, i really want to offer you a beer for your work. I think i will do it in every case, but yes, kitkat on my tab would be great :victory:
Sorry for bad english. For every question, i'm here. Thanks a lot.
M.

aMachi said:
Hi to everyone.
I was updating my tab to the latest version of the ROM of sbdags.
Everything was fine until i reboot the tab to use it for the first time: loop in the boot animation and never come out from it.
I came from the previous version of the rom, the Cromi-x 6.1 with 10.26.1.18 bootloader.
The process i use to update was this:
1) wipe of data/factory reset, wipe with format /boot, wipe with format /system
2) Install the CWM recovery 6.0.5.0 and update the bootloader to 11.4.1.17 by flashing they with the file that you can find in the rom page.
3) repeat point 1
4) install the rom by flashing it from an SD. Complete the Aroma installer and answer to every option that it ask to me.
5) reboot the system and stuck in the bootanimation
I use the WW format cause i'm italian and i check the md5
What's wrong? I can go to recovery everytime i need and i have a backup just in case i need it.
Sdbags, i really want to offer you a beer for your work. I think i will do it in every case, but yes, kitkat on my tab would be great :victory:
Sorry for bad english. For every question, i'm here. Thanks a lot.
M.
Click to expand...
Click to collapse
Don't do step 3. Try it again please.
Try the default options first.

sbdags said:
Don't do step 3. Try it again please.
Try the default options first.
Click to expand...
Click to collapse
If default option are those who are pre-selected on the aroma installer i've already try it.
Also i try to do it without point 3. Nothing
Here a log of the installation of the rom
AROMA INSTALLER version 2.56
(c) 2012 by amarullz xda-developers
ROM Name : CROMi-Xenogenesis KitKat
ROM Version : 7.0.2 DEODEX
ROM Author : sbdags
Device : Asus Transformer TF701T
Start at : Mon Aug 25 20:30:02 2014
Thank you for installing CROMi-Xenogenesis KitKat 4.4.2!
Sit back and relax...
-----------------------------------------------------
This will take a few minutes!
Preparing File System...
about to run program [/sbin/umount] with 3 args
umount: can't umount /system: Invalid argument
run_program: child exited with status 1
about to run program [/sbin/umount] with 3 args
Formatting System....
Creating filesystem with parameters:
Size: 2147483648
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 8192
Label:
Blocks: 524288
Block groups: 16
Reserved block group size: 127
Created filesystem with 11/131072 inodes and 17193/524288 blocks
Tuning System....
about to run program [/tmp/tune2fs.ext4] with 6 args
tune2fs 1.41.12 (17-May-2010)
Tuning Data - Journaling Enabled.....
about to run program [/tmp/tune2fs.ext4] with 6 args
tune2fs 1.41.12 (17-May-2010)
Wiping Cache.....
Installing Core System.....
Installing Options...
Region Specific Files
- TF701 WW Build
Kernel Preparation
- sbdag's 11.4.1.17 Stock Modded Kernel
package_extract_file: no extras/kernel/sbmodded/701sb3.img in package
DPI Preparation
- 320 DPI
Resolution Preparation
- 2560x1600 res
Boot Animation
- Google Android-L
Launcher
- Asus Stock Launcher
Asus Apps 1
- Asus Email
- Asus Desk Clock & Widget
- Asus Weather & Time Widget
- Asus Splendid
- Asus Calculator
- Asus MyDictionary
- Asus Studio
Asus Apps 2
Google Apps 1
- Google Calendar
- Google Now and Voice Search
- Google Music
- News and Weather Genie
- YouTube
- Maps
- Hangouts
Google Apps 2
- Google Chrome
- Google Drive Docs
Misc Apps
- ES File Explorer
- AdAway installed
- Keyboard Manager
- Terminal Emulator
- Polaris Office
Installing CROMi-X System Tweaks.....
about to run program [/tmp/cromix-build-prop.sh] with 1 args
Tweaks and Scripts
- Browser2RAM enabled
- Ad Blocker enabled
- Zip Align Script installed
- Keyboard Dock Remapping installed
Building symlinks.....
Setting permissions.....
Installing BusyBox.....
about to run program [/system/xbin/busybox] with 4 args
Setting ROOT.....
DRM Options
- Google Video & Hulu+ DRM
Installing build.prop
about to run program [/sbin/sh] with 2 args
about to run program [/sbin/sh] with 2 args
Finalising ROM
about to run program [/sbin/umount] with 3 args
---------------------------------------
All Done!
Don't forget to follow @sbdags on Twitter
If you like it please donate to [email protected] on paypal
Enjoy CROMi-X!
script succeeded: result was [Enjoy CROMi-X!]
Installer Sucessfull (Status 0)
I don't know if this can be helpful, but if i restore the backup of the previous version of the rom everything work fine. I'm reading the discussion of the guy with the partition problem and i was wondering if maybe the problem was the same, but i don't think it.
Another time, sorry for bad english and thanks for all your work sdbags.
M.

That log is fine - everything is installed.
Read out the bootloader version from the bootloader screen to double check please.
Also you are rebooting after installing the bootloader and cwm package aren't you?
aMachi said:
If default option are those who are pre-selected on the aroma installer i've already try it.
Also i try to do it without point 3. Nothing
Here a log of the installation of the rom
AROMA INSTALLER version 2.56
(c) 2012 by amarullz xda-developers
ROM Name : CROMi-Xenogenesis KitKat
ROM Version : 7.0.2 DEODEX
ROM Author : sbdags
Device : Asus Transformer TF701T
Start at : Mon Aug 25 20:30:02 2014
Thank you for installing CROMi-Xenogenesis KitKat 4.4.2!
Sit back and relax...
-----------------------------------------------------
This will take a few minutes!
Preparing File System...
about to run program [/sbin/umount] with 3 args
umount: can't umount /system: Invalid argument
run_program: child exited with status 1
about to run program [/sbin/umount] with 3 args
Formatting System....
Creating filesystem with parameters:
Size: 2147483648
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 8192
Label:
Blocks: 524288
Block groups: 16
Reserved block group size: 127
Created filesystem with 11/131072 inodes and 17193/524288 blocks
Tuning System....
about to run program [/tmp/tune2fs.ext4] with 6 args
tune2fs 1.41.12 (17-May-2010)
Tuning Data - Journaling Enabled.....
about to run program [/tmp/tune2fs.ext4] with 6 args
tune2fs 1.41.12 (17-May-2010)
Wiping Cache.....
Installing Core System.....
Installing Options...
Region Specific Files
- TF701 WW Build
Kernel Preparation
- sbdag's 11.4.1.17 Stock Modded Kernel
package_extract_file: no extras/kernel/sbmodded/701sb3.img in package
DPI Preparation
- 320 DPI
Resolution Preparation
- 2560x1600 res
Boot Animation
- Google Android-L
Launcher
- Asus Stock Launcher
Asus Apps 1
- Asus Email
- Asus Desk Clock & Widget
- Asus Weather & Time Widget
- Asus Splendid
- Asus Calculator
- Asus MyDictionary
- Asus Studio
Asus Apps 2
Google Apps 1
- Google Calendar
- Google Now and Voice Search
- Google Music
- News and Weather Genie
- YouTube
- Maps
- Hangouts
Google Apps 2
- Google Chrome
- Google Drive Docs
Misc Apps
- ES File Explorer
- AdAway installed
- Keyboard Manager
- Terminal Emulator
- Polaris Office
Installing CROMi-X System Tweaks.....
about to run program [/tmp/cromix-build-prop.sh] with 1 args
Tweaks and Scripts
- Browser2RAM enabled
- Ad Blocker enabled
- Zip Align Script installed
- Keyboard Dock Remapping installed
Building symlinks.....
Setting permissions.....
Installing BusyBox.....
about to run program [/system/xbin/busybox] with 4 args
Setting ROOT.....
DRM Options
- Google Video & Hulu+ DRM
Installing build.prop
about to run program [/sbin/sh] with 2 args
about to run program [/sbin/sh] with 2 args
Finalising ROM
about to run program [/sbin/umount] with 3 args
---------------------------------------
All Done!
Don't forget to follow @sbdags on Twitter
If you like it please donate to [email protected] on paypal
Enjoy CROMi-X!
script succeeded: result was [Enjoy CROMi-X!]
Installer Sucessfull (Status 0)
I don't know if this can be helpful, but if i restore the backup of the previous version of the rom everything work fine. I'm reading the discussion of the guy with the partition problem and i was wondering if maybe the problem was the same, but i don't think it.
Another time, sorry for bad english and thanks for all your work sdbags.
M.
Click to expand...
Click to collapse

sbdags said:
That log is fine - everything is installed.
Read out the bootloader version from the bootloader screen to double check please.
Also you are rebooting after installing the bootloader and cwm package aren't you?
Click to expand...
Click to collapse
When i install cwm and bootloader package i reboot from cwm but i stuck in boot animation. The same that happen when i try to reboot after install the rom.
In bootloader screen i read
Android macallan-user BL released by WW_epad-11.4.1.17-20140711

aMachi said:
When i install cwm and bootloader package i reboot from cwm but i stuck in boot animation. The same that happen when i try to reboot after install the rom.
In bootloader screen i read
Android macallan-user BL released by WW_epad-11.4.1.17-20140711
Click to expand...
Click to collapse
Right and then you boot back to CWM, do a full wipe (you may need to wipe your internal sdcard so back it up first) and then flash the rom. After that it should boot fine.
If not please search xda for how to get a logcat and post one of it bootlooping please.

sbdags said:
Right and then you boot back to CWM, do a full wipe (you may need to wipe your internal sdcard so back it up first) and then flash the rom. After that it should boot fine.
If not please search xda for how to get a logcat and post one of it bootlooping please.
Click to expand...
Click to collapse
I try the first thing that you say but nothing, still loop in bootanimation.
I'll do a logcat through adb in the afternoon. Now i had some problem cause i can't mount usb storage through cwm for some reason. Late i'll find drivers or what's missing.
Maybe can help: when i reboot frequently cwm ask me if i want to fix root. It's normal?
Thanks you for your help.

aMachi said:
I try the first thing that you say but nothing, still loop in bootanimation.
I'll do a logcat through adb in the afternoon. Now i had some problem cause i can't mount usb storage through cwm for some reason. Late i'll find drivers or what's missing.
Maybe can help: when i reboot frequently cwm ask me if i want to fix root. It's normal?
Thanks you for your help.
Click to expand...
Click to collapse
That message is normal. Just a bug in CWM.
We need to find why you are bootlooping.

sbdags said:
That message is normal. Just a bug in CWM.
We need to find why you are bootlooping.
Click to expand...
Click to collapse
Ok, logcat is here.
Hope it can help.

aMachi said:
Ok, logcat is here.
Hope it can help.
Click to expand...
Click to collapse
OK You got some serious problems there. It would appear that your internal sdcard doesn't mount:
Code:
D/Vold ( 359): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 359): *********** Success!! "ro.epad.mount_point.sdcard=/mnt/media_rw/sdcard"
D/Vold ( 359): Volume usbdrive state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 359): *********** Success!! "ro.epad.mount_point.usbdrive=/mnt/media_rw/usbdrive"
I/Vold ( 359): opening the sysfs of TF701
E/Vold ( 359): lookupVolume usbdisk1 failed!
E/Vold ( 359): lookupVolume usbdisk2 failed!
E/Vold ( 359): lookupVolume sdreader failed!
D/Vold ( 359): checkUsbdisk sucess.
D/DirectVolume( 359): i:0 minor:48
D/Vold ( 359): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
D/DirectVolume( 359): i:1 minor:49
D/Vold ( 359): Volume sdcard state changing 2 (Pending) -> 1 (Idle-Unmounted)
@lj50036, @_that any suggestions for this one?
@aMachi - what is the SKU of your device? And you can restore a nandroid back to 4.3 and it works fine?

sbdags said:
OK You got some serious problems there. It would appear that your internal sdcard doesn't mount:
Code:
D/Vold ( 359): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 359): *********** Success!! "ro.epad.mount_point.sdcard=/mnt/media_rw/sdcard"
D/Vold ( 359): Volume usbdrive state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 359): *********** Success!! "ro.epad.mount_point.usbdrive=/mnt/media_rw/usbdrive"
I/Vold ( 359): opening the sysfs of TF701
E/Vold ( 359): lookupVolume usbdisk1 failed!
E/Vold ( 359): lookupVolume usbdisk2 failed!
E/Vold ( 359): lookupVolume sdreader failed!
D/Vold ( 359): checkUsbdisk sucess.
D/DirectVolume( 359): i:0 minor:48
D/Vold ( 359): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
D/DirectVolume( 359): i:1 minor:49
D/Vold ( 359): Volume sdcard state changing 2 (Pending) -> 1 (Idle-Unmounted)
@lj50036, @_that any suggestions for this one?
@aMachi - what is the SKU of your device? And you can restore a nandroid back to 4.3 and it works fine?
Click to expand...
Click to collapse
i've some problem to find the SKU code. I search on the box of the tablet but there are too many codes and i don't know what's the right. Can you give me an exemple of it?
Yes, i can restore to 4.3. In this right moment i'm writing with the tab with cromix 6. Everything seems to work fine.
In case like this you really know how much important is to do a backup..

aMachi said:
i've some problem to find the SKU code. I search on the box of the tablet but there are too many codes and i don't know what's the right. Can you give me an exemple of it?
Yes, i can restore to 4.3. In this right moment i'm writing with the tab with cromix 6. Everything seems to work fine.
In case like this you really know how much important is to do a backup..
Click to expand...
Click to collapse
SKU is just your country code - so if you have changed it it could be causing issues with the clean install.
US, WW, TW, CN, JP are the only 5 I know of.
So if you changed the bootloader from US to WW I heard another user reporting some issues.
But in your case I am at a loss as to how you can boot 4.3 but not 4.4.2 as you are apparently on a 4.4.2 compatible bootloader and recovery .......

sbdags said:
SKU is just your country code - so if you have changed it it could be causing issues with the clean install.
US, WW, TW, CN, JP are the only 5 I know of.
So if you changed the bootloader from US to WW I heard another user reporting some issues.
But in your case I am at a loss as to how you can boot 4.3 but not 4.4.2 as you are apparently on a 4.4.2 compatible bootloader and recovery .......
Click to expand...
Click to collapse
Ah, right, i understand. I am WW, and i use it in every installation that i've done on my eee pad, from the rooting process and the unlocking of bootloader to the change of the rom.
Now that i am on the previous version of your rom those are infos of kernel, firmware, ecc.
Android Version 4.3
Kernel Version 3.4.57-g47dbe4d [email protected]#1
Tue Dec 17 23.26.15 CST 2013
Build Number TF701T_CROMi-Xenogenesis-6.1-WW_DEODEX-ORIGINAL-10.26.1.18 020115_201310210002
In ROM Manager i can see that my Recovery still is the 6.0.5.0 version.
In bootloader i can see that it is "WW_epad-11.4.1.17-20140711"
Hope that this might be helpful and hope that i don't write anything of unsafe.
M.

aMachi said:
Ah, right, i understand. I am WW, and i use it in every installation that i've done on my eee pad, from the rooting process and the unlocking of bootloader to the change of the rom.
Now that i am on the previous version of your rom those are infos of kernel, firmware, ecc.
Android Version 4.3
Kernel Version 3.4.57-g47dbe4d [email protected]#1
Tue Dec 17 23.26.15 CST 2013
Build Number TF701T_CROMi-Xenogenesis-6.1-WW_DEODEX-ORIGINAL-10.26.1.18 020115_201310210002
In ROM Manager i can see that my Recovery still is the 6.0.5.0 version.
In bootloader i can see that it is "WW_epad-11.4.1.17-20140711"
Hope that this might be helpful and hope that i don't write anything of unsafe.
M.
Click to expand...
Click to collapse
NO that is expected but hat is not expected is why you can't boot 4.4.2. Let's wait for _that and lj50036 to cast their expert eyes over your issues.

sbdags said:
@lj50036, @_that any suggestions for this one?
Click to expand...
Click to collapse
This seems to be the core of the problem:
Code:
E/dalvikvm(13002): JNI posting fatal error: Native registration unable to find class 'com/android/internal/os/RuntimeInit'; aborting...
Check that the framework is correctly installed and the BOOTCLASSPATH is set correctly:
Code:
adb shell echo $BOOTCLASSPATH > bootclasspath.txt
adb shell ls -l /system/framework > framework.txt

_that said:
This seems to be the core of the problem:
Code:
E/dalvikvm(13002): JNI posting fatal error: Native registration unable to find class 'com/android/internal/os/RuntimeInit'; aborting...
Check that the framework is correctly installed and the BOOTCLASSPATH is set correctly:
Code:
adb shell echo $BOOTCLASSPATH > bootclasspath.txt
adb shell ls -l /system/framework > framework.txt
Click to expand...
Click to collapse
Ok, so maybe now i need some help.
I run adb in my pc then i type adb shell to run the remote shell interactively.
Then what i need to type?
Anyway if i type "ls -l /system/framework > framework.txt" the response is "No such file or directory"
Sorry for my n00b questions. Really hope to learn something here, and give a chance to reward everyone for the help.

aMachi said:
Ok, so maybe now i need some help.
I run adb in my pc then i type adb shell to run the remote shell interactively.
Then what i need to type?
Anyway if i type "ls -l /system/framework > framework.txt" the response is "No such file or directory"
Sorry for my n00b questions. Really hope to learn something here, and give a chance to reward everyone for the help.
Click to expand...
Click to collapse
The commands were supposed to be typed as is on your computer. However I think I missed to quote the "echo $BOOTCLASSPATH" - I want the bootclasspath of your device, not of your PC.
Anyway, if you type "adb shell" first and then "ls -l /system/framework" and you get back "No such file or directory" that's strange...

_that said:
The commands were supposed to be typed as is on your computer. However I think I missed to quote the "echo $BOOTCLASSPATH" - I want the bootclasspath of your device, not of your PC.
Anyway, if you type "adb shell" first and then "ls -l /system/framework" and you get back "No such file or directory" that's strange...
Click to expand...
Click to collapse
Ok so tomorrow i'll give you the result of this test. I hope that i learn how to right use this command.
Any other thing that i can do?

aMachi said:
Ok so tomorrow i'll give you the result of this test. I hope that i learn how to right use this command.
Any other thing that i can do?
Click to expand...
Click to collapse
Post screenshots of your cmd window so that they can see the actual input/output

berndblb said:
Post screenshots of your cmd window so that they can see the actual input/output
Click to expand...
Click to collapse
No need for a graphical screenshot - you can copy the text from the console window.

[RECOVERY][sprout] TWRP 2.8.0.0 touch recovery [2014-09-26]

Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
{
"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"
}
Tablet look:
CHANGELOG for 2.8.0.0:
-Add MTP support to recovery thanks mostly to bigbiff with a little help from Dees_Troy
-Add command line capabilities - you can now execute various TWRP features via adb instead of the touchscreen
-Add support for color in the console and give error, warning, and highlight lines different colors
-Track backup and restore progress based on file sizes to provide a much more accurate indication of progress
-Improve handling of /misc thanks to mdmower
-Improve setting of time on Qualcomm devices thanks to [NUT]
-Allow using images on slidervalue GUI objects thanks to Tassadar
-Allow using variables and addition and subtraction in variables for easier theming
-Add support for 1440x2560, 280x280, and 320x320 resolutions and update 240x240
-Allow ui.xml file to include additional xml files to help break up the theme and make TWRP easier to maintain
-Other minor fixes and improvements
Over the course of the last year or so, bigbiff has worked to migrate various Java functions from Android's MTP implementation to bring you a fully C++ based MTP implementation that allows you to transfer files to both emulated storage and Micro SD cards. It's confirmed to work on various Nexus devices but we may have to make some changes on other devices to keep Windows happy. Windows is very picky about USB IDs and its drivers. We have tested it on Windows 7 and 8 as well as Ubuntu 14.04 Trusty. MTP is enabled by default, but we do toggle it off and on automatically during certain operations such as if you choose to wipe a storage partition. You can enable or disable MTP under the mount menu in TWRP. For more about what MTP is here.
Note: Due to a weird bug with our MTP setup, you cannot copy a zip file to the root of storage with Windows. You can change the .zip to something else like .txt and then copy it to the root and rename the file back to .zip once it's copied to the device. You can also copy the zip into any subfolder.
Command line support is also now available. You can perform various OpenRecoveryScript commands via the adb shell. Depending on what you are doing you may wish to do a "twrp set tw_mtp_enabled 0" and then reboot to prevent the MTP auto toggle from killing your adb interface. You can use this option to create and restore backups, wipe, install zips, and more. Via adb shell, type twrp followed by a space then enter the OpenRecoveryScript command and hit enter. Find more OpenRecoveryScript commands here.
CHANGELOG for 2.7.1.0:
-Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
-Various bugfixes to backup and restore
-Improvements to USB storage handling
-Added a class to search for files to make finding the correct brightness file automatic in most cases
-Various other bugfixes and tweaks
CHANGELOG for 2.7.0.0:
-Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
-Allow sideloading from /tmp on encrypted devices
-Check for a crypto footer before asking for a password to prevent user confusion
-Additional checks for validity to auto generated backup names
-Text wrap in the console output
-Proper caps lock support in the keyboard
-Mouse support via USB OTG for devices with a broken digitizer
-Improve scanning of storage locations for OpenRecoveryScript
-Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions thanks to Samer Diab
-Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
-Update SuperSU to 1.93 and improve installation process
-Added selinux contexts restoration to fix permissions
-Load RTC offset on Qualcomm devices to fix the date/time in recovery
-USB Mass Storage fixes Add SELinux support checking
-Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
-Add 4.4 decrypt support
-Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
-Various SELinux fixes and bug fixes
DOWNLOAD:
You can download the image here
INSTRUCTIONS:
Same as CWM
XDA:DevDB Information
Team Win Recovery Project, a Recovery for Android One devices
Contributors
varun.chitre15
Version Information
Status: Testing
Created 2014-09-26
Last Updated 2014-09-26

Thanks...!!

Really looking forward to twrp, love twrp more than cwm though
Sent from my Micromax AQ4501 using XDA Free mobile app

Thank You!

Flashed twrp, looks good now.
Can I backup my stock ROM now? @varun.chitre15
Sent from my Micromax AQ4501 using XDA Free mobile app

I am unable to backup my current rom using twrp.it works only a few times.sometimes the backup file is about 10 MB which is corrupted.
Other than that its rocking

official twrp 2.8.1.0 is out now..
official twrp is out now version 2.8.1.0 .. chk it out

problems after backuping stock unrooted and bootloader locked rom
hi all.
i backuped the stock rom on my dream uno without rooting or unlocking the bootloader and got 13 files some with .tar extension some with .tar.a and 1 with .tar.b extension and 2 files with .img extension
now the problem is.
1. if i try to open any file using winrar i get a error the archive is ither in unknown format or is damaged.
2. if i use 7zip to open .tar files i get error there are no trailing 0filled records if i open .tar.a files the files open properly but when i go to extract the contents i get error unable to open output file when i open data.ext4.tar.a i get error unexpected end of archive.tar and if i click on ok i can see the files in the archive but if i go to extract it again the same error unable to open output file comes if i open data.ext4.tar.b i get error 7zip cannot open data.ext4.tar.b as archive what is the problem?
how can i extract the files?
hear is my recovery.log file.
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Starting recovery on Sat Nov 8 14:38:30 2014
No /etc/extra.fstab
recovery filesystem table
=========================
0 /boot emmc /dev/block/platform/mtk-msdc.0/by-name/boot 0
1 /recovery emmc /dev/block/platform/mtk-msdc.0/by-name/recovery 0
2 /system ext4 /dev/block/platform/mtk-msdc.0/by-name/system 0
3 /data ext4 /dev/block/platform/mtk-msdc.0/by-name/userdata 0
4 /cache ext4 /dev/block/platform/mtk-msdc.0/by-name/cache 0
5 /external_sd auto /dev/block/mmcblk1p1 0
6 /tmp ramdisk ramdisk 0
I:Connected to Vold..
I:200 0 Volumes listed.
I:skiping get_bootloader_message: no /misc
I:skiping set_bootloader_message: no /misc
Checking arguments.
stage is []
can't open /dev/tty0: No such file or directory
framebuffer: fd 5 (480 x 854)
PhilZ Touch 6.57.9
ClockworkMod v6.0.5.1
Ievice target: sprout
I:Touch GUI revision: 1.41
I:device_recovery_start()
I:auto_restore_settings set to default (true)
I:check_root_and_recovery set to default (true)
I:compression_value set to default (low)
I:twrp_backup_mode set to default (false)
I:enable_md5sum set to default (1)
I:show_nandroid_size_progress set to default (1)
I:use_nandroid_simple_logging set to default (1)
I:nand_prompt_on_low_space set to default (1)
I:signature_check_enabled set to default (0)
I:install_zip_verify_md5 set to default (0)
I:brightness_user_path=/sys/class/leds/lcd-backlight/brightness
I:set_brightness set to default (160)
I:menu_height_increase set to default (24)
I:show_virtual_keys set to default (true)
I:min_log_rows set to default (3)
I:background_image set to default (default)
I:background_image set to default
Iefault stitch background loaded.
I:show_background_icon set to default (false)
I:show_battery set to default (true)
I:show_clock set to default (true)
I:menu_text_color set to default (8)
I:menu_background_color set to default (1)
I:menu_highlight_color set to default (7)
I:normal_text_color set to default (0)
I:menu_separator_color set to default (6)
I:header_text_color set to default (8)
I:batt_clock_color set to default (2)
I:menu_background_transparency set to default (102)
I:menu_highlight_transparency set to default (102)
I:menu_separator_transparency set to default (102)
I:show_menu_separation set to default (true)
I:dim_timeout set to default (60)
I:blank_timeout set to default (180)
I:scroll_sensitivity set to default (48)
I:touch_accuracy set to default (7)
I:touch_to_validate set to default (true)
I:enable_vibrator set to default (true)
I:boardEnableKeyRepeat set to default (true)
I:wait_after_install set to default (true)
I:slide_left_action set to default (5)
I:slide_right_action set to default (3)
I:double_tap_action set to default (2)
Iress_lift_action set to default (4)
Iress_move_action set to default (1)
I:t_zone set to default (0)
I:t_zone_offset set to default (0)
I:use_dst_time set to default (false)
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT0!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
I:Current time: 2014-11-08 14:38:32 (UTC 0:00)
I:use_qcom_time_daemon set to default (0)
I:use_qcom_time_data_files set to default (0)
I:use_qcom_time_offset set to default (0)
Command: "/sbin/recovery"
ro.cm.device=sprout
ro.cm.display.version=11-20140925-UNOFFICIAL-sprout
ro.cm.version=11-20140925-UNOFFICIAL-sprout
ro.cm.releasetype=UNOFFICIAL
ro.com.google.clientidbase=android-google
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.com.android.wifi-watchlist=GoogleGuest
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.boot.emmc=0
ro.boot.hardware=sprout
ro.boot.serialno=Mi498HA14090035
ro.boot.bootloader=0.5.17
ro.emmc=0
ro.wifi.channels=
ro.allow.mock.location=0
ro.board.platform=mt6582
ro.build.id=KTU84Q
ro.build.date=Thu Sep 25 13:18:39 EDT 2014
ro.build.date.utc=0
ro.build.host=ketan
ro.build.tags=test-keys
ro.build.type=userdebug
ro.build.user=root
ro.build.display.id=cm_sprout-userdebug 4.4.4 KTU84Q b75c7a7c94 test-keys
ro.build.product=sprout
ro.build.selinux=1
ro.build.version.sdk=19
ro.build.version.release=4.4.4
ro.build.version.codename=REL
ro.build.version.incremental=b75c7a7c94
ro.build.description=cm_sprout-userdebug 4.4.4 KTU84Q b75c7a7c94 test-keys
ro.build.fingerprint=Micromax/cm_sprout/sprout:4.4.4/KTU84Q/b75c7a7c94:userdebug/test-keys
ro.build.characteristics=default
ro.config.ringtone=Orion.ogg
ro.config.alarm_alert=Hassium.ogg
ro.config.notification_sound=Argon.ogg
ro.secure=1
ro.carrier=unknown
ro.cmlegal.url=http://www.cyanogenmod.org/docs/privacy
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.name=cm_sprout
ro.product.board=
ro.product.brand=Micromax
ro.product.model=A1
ro.product.device=sprout
ro.product.locale.region=US
ro.product.locale.language=en
ro.product.manufacturer=Micromax
ro.baseband=unknown
ro.bootmode=unknown
ro.hardware=sprout
ro.revision=0
ro.serialno=Mi498HA14090035
ro.bootloader=0.5.17
ro.debuggable=1
ro.modversion=11-20140925-UNOFFICIAL-sprout
ro.rommanager.developerid=cyanogenmod
ro.factorytest=0
ro.setupwizard.enterprise_mode=1
net.bt.name=Android
net.change=net.bt.name
init.svc.adbd=running
init.svc.vold=running
init.svc.healthd=running
init.svc.ueventd=running
init.svc.recovery=running
init.svc.setup_adbd=stopped
dalvik.vm.lockprof.threshold=500
dalvik.vm.stack-trace-file=/data/anr/traces.txt
persist.sys.dun.override=0
persist.sys.usb.config=adb
persist.sys.dalvik.vm.lib=libdvm.so
persist.sys.dalvik.multithread=false
persist.sys.root_access=1
persist.sys.recovery_update=false
service.adb.root=1
keyguard.no_require_sim=true
I:Checking for extendedcommand & OpenRecoveryScript...
I:Ignoring 'extendedcommand' boot-script: file not found
I:Ignoring 'openrecoveryscript' boot-script: file not found
I:Checking for recovery lock...
I:skiping set_bootloader_message: no /misc
I:skiping set_bootloader_message: no /misc
I:skiping set_bootloader_message: no /misc
I:skiping set_bootloader_message: no /misc
I:blank_timeout was set to 300
I:blank_timeout was set to 600
I:blank_timeout was set to 900
I:blank_timeout was set to 1800
I:blank_timeout was set to 0
I:dim_timeout was set to 120
I:dim_timeout was set to 180
I:dim_timeout was set to 240
I:dim_timeout was set to 300
I:dim_timeout was set to 0
I:skiping set_bootloader_message: no /misc
No files found.
I:ro.modversion set to default (noname)
I:ro.romversion set to default (noname)
I:ro.build.display.id=KPW53
I:Checking needed space for backup '/external_sd/clockworkmod/backup/2014-11-08.14.40.12_KPW53'
I:found device mmcblk link: '/dev/block/platform/mtk-msdc.0/by-name/recovery' -> '/dev/block/mmcblk0p8'
I:/recovery backup size (/proc)=10Mb
I:found device mmcblk link: '/dev/block/platform/mtk-msdc.0/by-name/boot' -> '/dev/block/mmcblk0p7'
I:/boot backup size (/proc)=10Mb
I:/system backup size (stat)=692Mb
I:/cache backup size (stat)=4Mb
I:/data: tot size=2322Mb, free=730Mb, backup size=1538Mb, used=1538Mb, media=0Mb
I:/external_sd/.android_secure backup size=5Mb
>> Free space: 6875Mb (90%)
>> Needed space: 2260Mb
>> Backing up /boot...
Backing up boot image...
Backup of boot image completed.
>> Backing up /recovery...
Backing up recovery image...
Backup of recovery image completed.
>> Backing up /system...
Press Back to cancel.
Backup of system completed.
>> Backing up /data...
Press Back to cancel.
Backup of data completed.
>> Backing up /external_sd/.android_secure...
Press Back to cancel.
Backup of .android_secure completed.
>> Backing up /cache...
Press Back to cancel.
Backup of cache completed.
I:No sd-ext found. Skipping backup of sd-ext.
>> Generating md5 sum...
> .android_secure.vfat.tar.a
> .android_secure.vfat.tar
> boot.img
> cache.ext4.tar
> cache.ext4.tar.a
> data.ext4.tar.a
> data.ext4.tar.b
> data.ext4.tar
> recovery.img
> system.ext4.tar.a
> system.ext4.tar

austinpinto said:
hi all.
i backuped the stock rom on my dream uno without rooting or unlocking the bootloader...............
Click to expand...
Click to collapse
you have to root and unlock the bootloader first.

Swapnil Solanki said:
you have to root and unlock the bootloader first.
Click to expand...
Click to collapse
hi.
i read somewhare that you can backup the entire rom without unlocking the bootloader and without rooting the phone by downloading the recovery.img file.
putting it into the platform tools folder opening the command prompt booting your phone into fast boot mode and typing fastboot boot recovery then once the recovery boots i can use the backup to sd card feature is this right? can i do this? the entire size of the backup folder is about 2.6gb but the only problem is i cannot open some tar files and tar.b files and extract data from all files is not working

:good:

Touch not working on my a1, i installed it through sp.. Where im going wrong?? No inputs from the touch.. Please help

terroboy k9 said:
Touch not working on my a1, i installed it through sp.. Where im going wrong?? No inputs from the touch.. Please help
Click to expand...
Click to collapse
try installing using fastboot...

Twrp 2.8.4.0
terroboy k9 said:
Touch not working on my a1, i installed it through sp.. Where im going wrong?? No inputs from the touch.. Please help
Click to expand...
Click to collapse
Try the stable build twrp 2.8.4.0 from the official website.

Not working yet

really awesome recovery for android one....:good::good::good:

Please help I'm not able to use touch with twrp

terroboy k9 said:
Please help I'm not able to use touch with twrp
Click to expand...
Click to collapse
Use Flashify to flash the recovery img. I did just that and it worked in the first trial.

Hi
I'm having a problem on my Micromax AQ4501.
Whenever I'm in recovery, and I try to reboot, the phone goes dead. Even a hard reboot (using the power button) doesn't work. I have to do a battery pull each time.
Even if I do a power off within recovery, and try to restart using the power button, the same thing. Have to do a battery pull.
I'm on 2.8.6.0 - downloaded from official TWRP site.
Any help would be appreciated!

alfavictor said:
Hi
I'm having a problem on my Micromax AQ4501.
Whenever I'm in recovery, and I try to reboot, the phone goes dead. Even a hard reboot (using the power button) doesn't work. I have to do a battery pull each time.
Even if I do a power off within recovery, and try to restart using the power button, the same thing. Have to do a battery pull.
I'm on 2.8.6.0 - downloaded from official TWRP site.
Any help would be appreciated!
Click to expand...
Click to collapse
Is the recovery meant for your device or you're using some other device's recovery?

root MEDION Life P5006 Lenovo B5032 failed

I tried to install in said mobile phone in TWRP SuperSU-v2.82-201705271822.zip. Unfortunately this fails - see log.
(adb logcat -d | find /i "installer" > logcat.txt has only Zero logcat.txt. "adb logcat" only -> logcat read failure)
The attempt to install systemmode (SR5-SuperSU-v2.82-SYSTEMMODE.zip) was successful in TWRP but after that the smartphone does not start anymore - it hangs in the bootlogo.
I would like to install SuperSU-v2.82-201705271822.zip - Please help!!!
TWRP is Port from Unofficial_TWRP_v3.1.1-0_For_MT6735_64-bit_3.18.19+_Kernel.img and the original recovery.bin (Tutorial: www.chinaphonearena.com/forum/Threa...752-MT6753-MT6795-MT6797-TWRP-MT67xx-tutorial) TWRP is running and backup in TWRP is ok.
Hardware & Software
-CPU-
SoC Modell: MediaTek MT6735
Kern Architektur: 4xARM Cortex-A53 @ 1300MHz
Befehlssatz: 64-bit ARMv8-A
CPU Kerne: 4
Unterstützte ABIs : (32-bit) armeabi-v7a, armeabi (64-bit) arm64-v8a
AES NEON SHA1 SHA2 : Unterstützt
Build ID : L1288.6.02.05
Baseband : MOLY.LR9.W1444.MD.LWTG.MP.V79.P7,2017/03/27 17:07
Kernel Vision : Linux version 3.18.19+ ([email protected]) (gccversion 4.9.x-google 20140827 (prerelease) (GCC))#1 SMP PREEMPT Mon Jul 10 17:31:07 CST 2017
-SYSTEM-
Hersteller : Lenovo
Modell/Gerät/Produkt : B5032
Marke : MEDION
Hardware/Platform : mt6735
SerienNr.: 11250061740012590
Android ID : 2d76aadb59596ab1
-OS-
Version : 6.0 Marshmallow
API Level : 23
Android Security Patch LVL : 2017-05-05
Fingerprint : MEDION/B5032/B5032:6.0/MRA58K/L1288.6.02.05:user/release-keys
Build ID : MRA58K

card0384 said:
I tried to install in said mobile phone in TWRP SuperSU-v2.82-201705271822.zip. Unfortunately this fails - see log.
(adb logcat -d | find /i "installer" > logcat.txt has only Zero logcat.txt. "adb logcat" only -> logcat read failure)
The attempt to install systemmode (SR5-SuperSU-v2.82-SYSTEMMODE.zip) was successful in TWRP but after that the smartphone does not start anymore - it hangs in the bootlogo...
Click to expand...
Click to collapse
I don't have this device but, the following thread may be helpful to you.
https://forum.xda-developers.com/showthread.php?t=3337484
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Hello, thanks for your Support. This link cannot fixed my Problem, sorry

Maybe chainfire can look at the logs, I've uploaded all the needed ones

card0384 said:
Maybe chainfire can look at the logs, I've uploaded all the needed ones
Click to expand...
Click to collapse
ChainFire has retired from SuperSU development/support.

as is great, I found the mistake and the solution. The TWRP I used was executable but somehow not right. I have another TWRP used as the basis for porting, so read SuperSu install fine. Class - I have rooted my first cell phone without instructions - I put the instructions for this for other interested in the net

[EvolutionX (3.5) Erfan GSIs] [Android 10 ]

New v3.5 port from Oneplus 6 https://forum.xda-developers.com/showpost.php?p=81186001&postcount=6
port from Redmi 4A https://forum.xda-developers.com/showpost.php?p=81186219&postcount=7
From Base Firmware : EvolutionX_3.3_violet-10.0-20191112-1125-OFFICIAL.zip
Raw Image Size: 2.86 GiB
Thank to TeamGSI
======================
Download:
GSI : https://drive.google.com/drive/folders/1-7N6Z9NUb-9ut8Zz8M51FAwUC11AKTaa
File Name : EvolutionX-Aonly-10-20191119-GSI.img-1621.z7 (extracted before flashing)
TWRP : https://mega.nz/#!sHoXlaDK!ZIfuRrtl7IGsruGMIWDrbvudKgxcYdiEd-6iQS2YFNg
File Name : TWRP-20191001-3.3.1.0-clover.img
Vendor & boot : Pie ( Treble ) https://mega.nz/#!xaolTKoS!pdfjw02cw3dImfB4vlyXwINALQUewQ5lJBBjSUDKxcM
File Name : vendor_197.zip
Latest Official Clover Firmware https://mega.nz/#!QDplSYab!mrB5f8875VghQHfrrGvid4iJICMopkq3anZCipLWzqo
File Name : fw_clover_miui_MIPAD4_9.8.29_6647b25a58_8.1.zip
Erfan tools : https://mega.nz/#!xXpViC4Y!UsRgGMYNtiaLvfdXSuzamfaxsM_FOs-9xrZrPu5QCP8
File Name : allzygotefix2.zip
Phh Magisk : Magisk-v20.2-b29f0ca4-phh.zip
https://mega.nz/#!tKxngSaD!jdDHi4-QFMX2bNgQVPi50ZrpovbNRuD61aAeIt02lCI
GMS : https://mega.nz/#!cOhmgIoY!cTYxxYpc36tMl0QnndRcaPUDQ6BpO7tG0yiPQ2i7QXo
=================
Step
-wipe--Format Data
-wipe--Advanced wipe---Dalvik , Cache , Data , System , Vendor
-Option wipe--Advanced wipe---tick Data menu----Repair or change file System-----Change File System and select F2FS
-flash Firmware
-flash Vendor
-flash GSI as System Image
-flash allzygotefix2.zip (for A-only GSI when work with Android 10)
-Reboot to System
Don't worry about " Android System error message , its only one warning --we will fix at the end.
click "OK"
-Setting menu --Display---Smallest width = set to 540 dp or more than that , Icon shape = up to you
-Setting menu --Evolution settings---enable Users and Logout ( Multi user )
Don't forgotten to setup SD Card ===(Support exFAT) for me use as removable.
-Setting menu -- About phone ===changes device name from POCO F1 to anything you like or Mipad4
==============
-Flash Magisk (phh Magisk) https://sourceforge.net/projects/expressluke-gsis/files/Extras/phh-magisk-ten/
-Reboot--update it if need
-Magisk manager --install belows modules from here ---> https://github.com/ElderDrivers/EdXposed
1. Magisk-riru-core-v19.5.zip ( save)
2. Magisk-EdXposed-YAHFA-v0.4.6.0_beta.....xxxx.zip
-Reboot
-install Edxposed Manager.apk
open it set active status
-Reboot by granted Magisk super user permission
-Add & activated eXposed modle--com.cofface..ivader
=======================================
-install updated GMS ( Google Services)
-Reboot
-Setup and login your google account
Now your Play Protect is certified. and all green Safetynet check success.
======================================
-Check your FingerPrint.
-Check your BlueTooth
-Check your Mobile Data ( VoTLE )
-Check your Auto rotate
-Your Camera
All working
=========================
Fix error " Android System: your vendor image does not match the system......."
-edit (system/vendor----> bulid prop)
change line " ro.vendor.build.fingerprint = xxx to ro.build.fingerprint=xxx
and/or
-edit (system ---> bulid prop)
change " ro.treble.enabled=true" to " ro.treble.enabled=false"
- reboot
=========================
Viper4Android FX from magisk'repo
v.2.7.1.0
-install with Magisk manager
-reboot and open program-- follow suggestion from screen
==========================
Supported Youtube Vanced.
++++++++++++++++++++++++++++++++++++++++++++++++++
GCAM
https://www.celsoazevedo.com/files/android/google-camera/dev-parrot043/#apk1213
+++++++++++++++++++++++++++++++++++++++++++++++++

New & Update from ExpressLuke GSI ( compiled from source)
=============================
ROM Name: Evolution X 3.3 ( EvolutionX_3.3_ARM64A-10.0-20191202-0048-UNOFFICIAL.img)
ROM Version: 10
ROM Security Patch: 5 November 2019
Architecture: ARM64
Partition Layout: A
GSI Patch Base: phh v204
Built in GApps?: Yes
Changelog: https://pastebin.com/raw/0SwBzV6e
MEGA: Download
( https://mega.nz/#!QJkF3KxY!-trp3Q9NJDqtKoTddxeg3yn-bu6JU_6XuokZs-ri7B4)
SourceForge: Download
(https://sourceforge.net/projects/ex...191202-0048-UNOFFICIAL.img.xz/download)Google
Drive: Download (https://drive.google.com/a/turbox.uk/uc?id=1U0Nhpow2IMXUTV_ZQIfC9JAEocPc3Qik&export=download)
####Please use magisk-phh
Note !!!!!!
1. you must flash "Permissiver_v5.zip" cause GSI image not included. ( if not will Boot Fastboot Mode )
2. No need to install new update GMS apk.
3. Default Camera not working. use GCAM instead
4. Chrome crash.
-----> Please test wifi speed. mine very low 30 Mbit/Sec
-----> Evolution setting--->Power menu --->ERROR

EVOLUTIONX 3.4 (Recommended)
Download A-Only: Google Drive (https://drive.google.com/uc?export=download&id=16_3QYEeq8DnLI92xQvY6u4hSNpZ4-sYj)
File name: EvolutionX-Aonly-10-20191210-ErfanGSI.img.gz
Information:
Android Version: 10
Brand: Xiaomi
Model: MI 8
Codename: dipper
Build Type: aosp_dipper-user
Build Number: QQ1A.191205.011
Incremental: eng.DarkAn.20191207.000600
Tags: test-keys
Security Patch: 2019-12-05
Fingerprint: Xiaomi/dipper/dipper:8.1.0/OPM1.171019.011/V9.5.5.0.OEAMIFA:user/release-keys
Description: dipper-user 8.1.0 OPM1.171019.011 V9.5.5.0.OEAMIFA release-keys
Raw Image Size: 2.60 GiB

Many thanks for your contributions to our device!
it works great , everything works except the auto rotate, is always in vertical

UPDATE EvolutionX v3.5
Information:
Android Version: 10
Brand: OnePlus
Model: ONEPLUS A6003
Codename: OnePlus6
Build Type: aosp_enchilada-userdebug
Build Number: QQ1B.191205.011
Incremental: eng.bliss.20191212.000302
Tags: test-keys
Security Patch: 2019-12-05
Fingerprint: OnePlus/OnePlus6/OnePlus6:8.1.0/OPM1.171019.011/06140300:user/release-keys
Description: OnePlus6-user 8.1.0 OPM1.171019.011 273 release-keys
Raw Image Size: 2.81 GiB
====================================
Download A-Only: Google Drive (https://drive.google.com/uc?export=download&id=13OJZ6ABa5zLMdCGAGaW3nuNczGV8VAuE)
<<<<<<<< Not boot with my vendor for mipad >>>>>>>>>>>>>

Update EvolutionX 3.5
Information:
Android Version: 10
Brand: Xiaomi
Model: Redmi 4A
Codename: rolex
Build Type: aosp_rolex-userdebug
Build Number: QQ1B.191205.011
Incremental: eng.ubuntu.20191212.104649
Tags: test-keys
Security Patch: 2019-12-05
Fingerprint: Xiaomi/rolex/rolex:7.1.2/N2G47H/V9.2.6.0.NCCMIEK:user/release-keys
Description: rolex-user 7.1.2 N2G47H V9.2.6.0.NCCMIEK release-keys
Raw Image Size: 2.35 GiB
=====================================
Download A-Only: Google Drive (https://drive.google.com/uc?export=download&id=1jxyN2uiNo8rk2o4az6r8BR3nfqxqHfF6)
Bug: Evolution setting---power menu (crash) but can use advanced boot with power button.

I tried several times and always get the same problem : the autorotate not works,
I installed other Roms and in every rom I have the same probem with the autorotate
I also tried the roms from https://forum.xda-developers.com/mi-pad-4 and is the same, Im afraid my autorotate die...
I tried the sensors app in google play and says all my sensors not works...
Any idea to try to solve giroscopie?
I tried various roms and I think this one works very well :
https://forum.xda-developers.com/mi-pad-4/development/rom-lineageos-17-0-t3989187

Fix error " Android System: your vendor image does not match the system......."
-edit (system/vendor----> bulid prop)
change line " ro.vendor.build.fingerprint = xxx to ro.build.fingerprint=xxx
and/or
-edit (system ---> bulid prop)
change " ro.treble.enabled=true" to " ro.treble.enabled=false"
- reboot
Click to expand...
Click to collapse
Everything works fine except the error every bootup is not fixed. I cannot find "ro.vendor.build.fingerprint" in build prop. I managed to set this "ro.treble.enabled=false". However, the error persists.
Also, how do I prevent the screen from turning off when I close the flip cover?