Related
I'm working on a project that requires an android port of the USB/IP project. I managed to build the required modules for the phone kernel (using the NDK) and build the user space application (using crosstool-ng for glibc requirements) but I cannot find any information on the net how to set the correct permissions for the usbip userland application. When I execute the usbip binary I get "sh: usbip: permission denied" although I'm logged in on the phone as root (su) and the permissions are correct.
Any help will be appreciated.
Hey guys,
I need help testing CASUAL. I've been working on CASUAL for almost a year now. Currently I'm working on bringing real-time updates and a kill-switch in the event the GNote2 unlock starts bricking devices. I need tesing on the ability to push a new revision, and the "kill-switch".
Intent
I need help testing new features on your computer because they work on mine. The tests will do nothing except reboot your device. The update system is pretty critical and potentially show-stopping. It will be in every CASUAL, including the GNote2 Unlock (for safety reasons) as soon as this test is complete.
Scripts
Here is what I need tested:
1. Kill Switch -- If you are connected to the internet, it will shutdown CASUAL, display a message, then open a browser and take you somewhere where you can get more information.
2. Update Required -- Will download the latest versions of the "Update Required" script and files ONLY one time per run. These files come from the CASUAL Subversion repository located here, then your device will reboot.
3. Update Not Required -- Will reboot your device. This is the "control" subject.
Download CASUAL R180 Build2,846
Obtaining a log
If you see a problem, Click About>Show Log>Copy to Clipboard then paste it into a code box here on XDA. Or if you wish to copy the terminal output from "java -jar path_to/casual.jar" that's fine too.
Privacy
No information is sent from your computer. CASUAL determines if it needs an update by looking at the online version and pulling required files off the internet.
SVN Revision: 169
CASUAL Build Number: 2,792
Problems known at release: none
Problems Identifed:
Kill Switch/update downloaded message contains no spaces.
SVN Revision 180
CASUAL Build Number:2846
Corrected killswitch/update messages, removed unused imports, cleaned up and relicensed code under GPL instead of MIT
Problems known at release: none
Problems Identifed: none
AdamOutler said:
Hey guys,
I need help testing CASUAL. I've been working on CASUAL for almost a year now. Currently I'm working on bringing real-time updates and a kill-switch in the event the GNote2 unlock starts bricking devices. I need tesing on the ability to push a new revision, and the "kill-switch".
Intent
I need help testing new features on your computer because they work on mine. The tests will do nothing except reboot your device. The update system is pretty critical and potentially show-stopping. It will be in every CASUAL, including the GNote2 Unlock (for safety reasons) as soon as this test is complete.
Scripts
Here is what I need tested:
1. Kill Switch -- If you are connected to the internet, it will shutdown CASUAL, display a message, then open a browser and take you somewhere where you can get more information.
2. Update Required -- Will download the latest versions of the "Update Required" script and files ONLY one time per run. These files come from the CASUAL Subversion repository located here, then your device will reboot.
3. Update Not Required -- Will reboot your device. This is the "control" subject.
Download CASUAL R169 Build2,792
Obtaining a log
If you see a problem, Click About>Show Log>Copy to Clipboard then paste it into a code box here on XDA. Or if you wish to copy the terminal output from "java -jar path_to/casual.jar" that's fine too.
Privacy
No information is sent from your computer. CASUAL determines if it needs an update by looking at the online version and pulling required files off the internet.
Click to expand...
Click to collapse
How long does it take to update? I have the "Script is out of date" message. Says updating...then the Youshouldseethismessagebecauseitsimportant message".....but so far no reboot...it's been about four minutes.
Here's the log -
Code:
Created Folder:C:\Users\User\AppData\Local\Temp\UserTEMPCASUAL232BF7BD\
Control Change requested but Statics.MasterLock is set.
OMFGWOOT
This is a test of CASUAL's new update system. Please leave feedback.
Deploying ADB
Searching for scripts
null
Picking Jar File:/D:/Download/CASUAL-Revision169b.jar
Found Windows Computer
Attempting to write C:\Users\User\AppData\Local\Temp\UserTEMPCASUAL232BF7BD\Elevate.exe
File verified.
Attempting to write C:\Users\User\AppData\Local\Temp\UserTEMPCASUAL232BF7BD\adb.exe
Found: Kill-Switched
Found: Update Not Required
Found: Update Required
From Resource: true
--Kill-Switched--
Exiting comboBoxUpdate()
File verified.
Attempting to write C:\Users\User\AppData\Local\Temp\UserTEMPCASUAL232BF7BD\AdbWinApi.dll
File verified.
Attempting to write C:\Users\User\AppData\Local\Temp\UserTEMPCASUAL232BF7BD\AdbWinUsbApi.dll
File verified.
Attempting to write C:\Users\User\AppData\Local\Temp\UserTEMPCASUAL232BF7BDadb_usb.ini
File verified.
###executing: C:\Users\User\AppData\Local\Temp\UserTEMPCASUAL232BF7BD\adb.exe###
State Change Detected, The new state is: 1
State Connected
device
Device List:List of devices attached 014E5ABE06004016 device
Controls Enabled status: true
StartButtonActionPerformed() Script Activated
Script known as Kill-Switched is running
Controls Enabled status: false
Script Kill-Switched returned #0Kill-Switched
Selected resourceKill-Switched
Lines in Script 4
Executing Scripted [email protected]
CASUAL has initiated a multithreaded execution environment
Script Kill-Switched returned #0Kill-Switched
Script is out of date. See http://forum.xda-developers.com/search.php?do=finduser&u= for more information. Updating.
Youshouldseethismessagebecauseitsimportant--AdamOutler
Okay...re-read your instructions again...Chose "Kill Switch" and the above happens.
Chose "Update required" and it give the "Cool" message.
Chose "Update not required" and it rebooted.
I think those were the expected results, yes? FYI - I have a Mot. Razr Maxx....
just4sc said:
How long does it take to update? I have the "Script is out of date" message. Says updating...then the Youshouldseethismessagebecauseitsimportant message".....but so far no reboot...it's been about four minutes.
Here's the log -
Code:
Created Folder:C:\Users\User\AppData\Local\Temp\UserTEMPCASUAL232BF7BD\
Control Change requested but Statics.MasterLock is set.
OMFGWOOT
This is a test of CASUAL's new update system. Please leave feedback.
Deploying ADB
Searching for scripts
null
Picking Jar File:/D:/Download/CASUAL-Revision169b.jar
Found Windows Computer
Attempting to write C:\Users\User\AppData\Local\Temp\UserTEMPCASUAL232BF7BD\Elevate.exe
File verified.
Attempting to write C:\Users\User\AppData\Local\Temp\UserTEMPCASUAL232BF7BD\adb.exe
Found: Kill-Switched
Found: Update Not Required
Found: Update Required
From Resource: true
--Kill-Switched--
Exiting comboBoxUpdate()
File verified.
Attempting to write C:\Users\User\AppData\Local\Temp\UserTEMPCASUAL232BF7BD\AdbWinApi.dll
File verified.
Attempting to write C:\Users\User\AppData\Local\Temp\UserTEMPCASUAL232BF7BD\AdbWinUsbApi.dll
File verified.
Attempting to write C:\Users\User\AppData\Local\Temp\UserTEMPCASUAL232BF7BDadb_usb.ini
File verified.
###executing: C:\Users\User\AppData\Local\Temp\UserTEMPCASUAL232BF7BD\adb.exe###
State Change Detected, The new state is: 1
State Connected
device
Device List:List of devices attached 014E5ABE06004016 device
Controls Enabled status: true
StartButtonActionPerformed() Script Activated
Script known as Kill-Switched is running
Controls Enabled status: false
Script Kill-Switched returned #0Kill-Switched
Selected resourceKill-Switched
Lines in Script 4
Executing Scripted [email protected]
CASUAL has initiated a multithreaded execution environment
Script Kill-Switched returned #0Kill-Switched
Script is out of date. See http://forum.xda-developers.com/search.php?do=finduser&u= for more information. Updating.
Youshouldseethismessagebecauseitsimportant--AdamOutler
Okay...re-read your instructions again...Chose "Kill Switch" and the above happens.
Chose "Update required" and it give the "Cool" message.
Chose "Update not required" and it rebooted.
I think those were the expected results, yes? FYI - I have a Mot. Razr Maxx....
Click to expand...
Click to collapse
I'm pushing out the kill switch now. http://code.google.com/p/android-casual/source/list
AdamOutler said:
Hey guys,
I need help testing CASUAL. I've been working on CASUAL for almost a year now. Currently I'm working on bringing real-time updates and a kill-switch in the event the GNote2 unlock starts bricking devices. I need tesing on the ability to push a new revision, and the "kill-switch".
Intent
I need help testing new features on your computer because they work on mine. The tests will do nothing except reboot your device. The update system is pretty critical and potentially show-stopping. It will be in every CASUAL, including the GNote2 Unlock (for safety reasons) as soon as this test is complete.
Scripts
Here is what I need tested:
1. Kill Switch -- If you are connected to the internet, it will shutdown CASUAL, display a message, then open a browser and take you somewhere where you can get more information.
2. Update Required -- Will download the latest versions of the "Update Required" script and files ONLY one time per run. These files come from the CASUAL Subversion repository located here, then your device will reboot.
3. Update Not Required -- Will reboot your device. This is the "control" subject.
Download CASUAL R169 Build2,792
Obtaining a log
If you see a problem, Click About>Show Log>Copy to Clipboard then paste it into a code box here on XDA. Or if you wish to copy the terminal output from "java -jar path_to/casual.jar" that's fine too.
Privacy
No information is sent from your computer. CASUAL determines if it needs an update by looking at the online version and pulling required files off the internet.
Click to expand...
Click to collapse
This is revolutionizing android and fast. i love you.
Everything appears to be working great Adam.
Thanks.
I've just relesed the following build. All previous scripts should be killswitched. Please test this and verify that there are no errors.
SVN R180
CASUAL Build Number:2846
Corrected killswitch/update messages, removed unused imports, cleaned up and relicensed code under GPL instead of MIT
Problems known at release: none
Problems Identifed: none
Sorry, I uploaded the wrong file. Correct file is up now. There should be no problems now.
Please let me know if this works and what OS you are using.
Windows 7 here, everything looks good, but it did not reboot after I got the "cool" message when doing the update required choice.
B-Mod said:
Windows 7 here, everything looks good, but it did not reboot after I got the "cool" message when doing the update required choice.
Click to expand...
Click to collapse
Could you please grab the log from about>show log>copy to clipboard.. Then paste it here in
Code:
tags?
Created Folder:C:\Users\HTPC\AppData\Local\Temp\HTPCTEMPCASUAL59652B83\
Control Change requested but Statics.MasterLock is set.
OMFGWOOT
Testing CASUAL's ability to update
Deploying ADB
Searching for scripts
null
Found Windows Computer
Picking Jar File:/C:/Users/HTPC/Desktop/CASUAL-Revision180b(1).jar
Attempting to write C:\Users\HTPC\AppData\Local\Temp\HTPCTEMPCASUAL59652B83\Elevate.exe
File verified.
Attempting to write C:\Users\HTPC\AppData\Local\Temp\HTPCTEMPCASUAL59652B83\adb.exe
Found: Kill-Switched
Found: Update Not Required
Found: Update Required
Updating Scripts for UI
From Resource: true
--Kill-Switched--
Exiting comboBoxUpdate()
File verified.
Attempting to write C:\Users\HTPC\AppData\Local\Temp\HTPCTEMPCASUAL59652B83\AdbWinApi.dll
File verified.
Attempting to write C:\Users\HTPC\AppData\Local\Temp\HTPCTEMPCASUAL59652B83\AdbWinUsbApi.dll
File verified.
Attempting to write C:\Users\HTPC\AppData\Local\Temp\HTPCTEMPCASUAL59652B83\adb_usb.ini
File verified.
###executing: C:\Users\HTPC\AppData\Local\Temp\HTPCTEMPCASUAL59652B83\adb.exe###
State Change Detected, The new state is: 1
device
State Connected
Device List:List of devices attached 42f73b16cf4d9f95 device
Controls Enabled status: true
From Resource: true
--Update Required--
Exiting comboBoxUpdate()
StartButtonActionPerformed() Script Activated
Script known as Update Required is running
Controls Enabled status: false
Script Update Required returned #2Update Required
Selected resourceUpdate Required
Lines in Script 4
Executing Scripted [email protected]
CASUAL has initiated a multithreaded execution environment
Script Update Required returned #2Update Required
Script is out of date. See http://forum.xda-developers.com/showthread.php?t=2105263 for more information. Updating.
CASUAL was updated to the latest greatest version of this script. Cool huh? --AdamOutler
---------- Post added at 07:52 PM ---------- Previous post was at 07:51 PM ----------
Code:
Created Folder:C:\Users\HTPC\AppData\Local\Temp\HTPCTEMPCASUAL59652B83\
Control Change requested but Statics.MasterLock is set.
OMFGWOOT
Testing CASUAL's ability to update
Deploying ADB
Searching for scripts
null
Found Windows Computer
Picking Jar File:/C:/Users/HTPC/Desktop/CASUAL-Revision180b(1).jar
Attempting to write C:\Users\HTPC\AppData\Local\Temp\HTPCTEMPCASUAL59652B83\Elevate.exe
File verified.
Attempting to write C:\Users\HTPC\AppData\Local\Temp\HTPCTEMPCASUAL59652B83\adb.exe
Found: Kill-Switched
Found: Update Not Required
Found: Update Required
Updating Scripts for UI
From Resource: true
--Kill-Switched--
Exiting comboBoxUpdate()
File verified.
Attempting to write C:\Users\HTPC\AppData\Local\Temp\HTPCTEMPCASUAL59652B83\AdbWinApi.dll
File verified.
Attempting to write C:\Users\HTPC\AppData\Local\Temp\HTPCTEMPCASUAL59652B83\AdbWinUsbApi.dll
File verified.
Attempting to write C:\Users\HTPC\AppData\Local\Temp\HTPCTEMPCASUAL59652B83\adb_usb.ini
File verified.
###executing: C:\Users\HTPC\AppData\Local\Temp\HTPCTEMPCASUAL59652B83\adb.exe###
State Change Detected, The new state is: 1
device
State Connected
Device List:List of devices attached 42f73b16cf4d9f95 device
Controls Enabled status: true
From Resource: true
--Update Required--
Exiting comboBoxUpdate()
StartButtonActionPerformed() Script Activated
Script known as Update Required is running
Controls Enabled status: false
Script Update Required returned #2Update Required
Selected resourceUpdate Required
Lines in Script 4
Executing Scripted [email protected]
CASUAL has initiated a multithreaded execution environment
Script Update Required returned #2Update Required
Script is out of date. See http://forum.xda-developers.com/showthread.php?t=2105263 for more information. Updating.
CASUAL was updated to the latest greatest version of this script. Cool huh? --AdamOutler
Adam, did you figure out why the phone did not reboot?
Try this one. This includes all my latest changes..
Added Fastboot support
Added Killswitch support
Added Automatic Downloads
Added MD5 integrity checks
--Also-- Added "double-click-enable" on status button. If you really want to use a fastboot-only script but your device isn't capable of adb reboot bootloader, double-click the "device status" and it will enable things as though a device were connected.
Download Here: http://d-h.st/JlJ
AdamOutler said:
Try this one. This includes all my latest changes..
Added Fastboot support
Added Killswitch support
Added Automatic Downloads
Added MD5 integrity checks
--Also-- Added "double-click-enable" on status button. If you really want to use a fastboot-only script but your device isn't capable of adb reboot bootloader, double-click the "device status" and it will enable things as though a device were connected.
Download Here: http://d-h.st/JlJ
Click to expand...
Click to collapse
Sorry, but I won't be able to test it till Thursday night, as I am working out of town and not near my PC.
AdamOutler said:
Try this one. This includes all my latest changes..
Added Fastboot support
Added Killswitch support
Added Automatic Downloads
Added MD5 integrity checks
--Also-- Added "double-click-enable" on status button. If you really want to use a fastboot-only script but your device isn't capable of adb reboot bootloader, double-click the "device status" and it will enable things as though a device were connected.
Download Here: http://d-h.st/JlJ
Click to expand...
Click to collapse
All seems to run well here.
--Test Script--
Testing Testing Revision 1
Script is out of date. See http://xda-developers.com for more information. Updating.
OMFG TESTING meta information
Downloading Updates
Test Script.scr...4kb Test Script.zip...1880kb Test Script.txt...4kb ... Update Sucessful! MD5s verified!
rebooting with ADB
rebooting with Fastboot
Running Windows 7.
I will test this tonight when I get home.
Since the unnofical thread of TWRP is now closed decided to create my own thread
of my TWRP builds. started this for quite some long.
This TWRP make backup of EFS and can handle firmware files properly.
For more features you can read the change logs, you will fint all there.
All this would not be possible without Omnirom Team guys that work on the recovery part of Omnirom, yes, my TWRP is build based on Omnirom recovery tree.
As for the device tree, the one used its the one from CM13 to our device. To see the changes go to is gerrit / github of Omnirom and CyanogenMod.
Big thanks to all of you guys.
Also would thanks to @ketut.kumajaya and @katinatez , because on my device before starting to make my own builds of TWRP was using is builds for quit long time on my device.
Latest build: ( check seconf post for older builds )
https://www.androidfilehost.com/?w=files&flid=50417
Reserved
TWRP 3.2.1-1-TugaPower 2017-12-10 ( testing )
ADB Backup: Fixup
adds /persist/time/ as Qualcomm time fix source
Process AOSP wipe commands prior to encryption check
Please report some problems if you find since its first release.
Nandroid restore should be working since its fixed on TWRP source
Stuff that need to be tested:
wipe cache and dalvik and see if its slower then before or same as before, test restoring nandroid, test nandroid backup, test flash rom, see how aroma its working, test encryption
If someone go trough this tests please report how its working. ( doing nandroid as we speak and going to restore an older nandroid)
Wipe cache and dalvik for me it seems fast enought but more opinions its welcome.
https://www.androidfilehost.com/?fid=817906626617951858
TWRP 3.1.1-5-TugaPower 2017-09-19
Fixed encryption
https://www.androidfilehost.com/?fid=961840155545597147
TWRP 3.1.1-4-TugaPower 2017-09-17
Fixed slow format of cache
https://www.androidfilehost.com/?fid=673368273298986645
TWRP 3.1.1-3-TugaPower 2017-09-17
Remove duplicate entries & Improve Chinese translation
Fix typos / inconsistencies in German language
SHA2: Enable in landscape and watch xml
Show scrollbar on TWRP Settings
twrpTar: Fix uninitialized current_archive_type
TWRP 3.1.1-2-TugaPower 2017-07-09
backup: fix return handling when no digest is being created
libtar: Fix restore of e4crypt policies
TWRP 3.1.1-1-TugaPower
Fix incorrect 'unlink' return value check
twrpDigest refactor
Fix minui issues for some build trees
ors: Update doc
Improve decrypted partition logging
adbbackup: write smaller reads less than 512 bytes
Fix various memory errors
cryptfs: Remove dm-crypt device on failed table load
TWRP 3.1.1-0-TugaPower
fix logic of TW_USE_MINUI_CUSTOM_FONTS
etc: remove "." from LD_LIBRARY_PATH
mtdutils: Fix mounting partitions by-name
gui: fix line wrapping in terminal, issue #876
3.1.1
TWRP 3.1.0-5-TugaPower
Fix reboot when no OS is present
Complete support for project pathmap
Improve automatic detection of QCOM RTC fix
Adopted Storage: backup keys but do not wipe them
ADB Backup: fix adb restore issues
TWRP 3.1.0-4-TugaPower
Fixed slow formating
Fixed encryption
TWRP 3.1.0-3-TugaPower
Fixed make_ext4fs formatting partitions
TWRP 3.1.0-2-TugaPower
Fixed aroma graphics
TWRP 3.1.0-1-TugaPower
Revert "Fix adb shell in 7.0 tree"
file_contexts: remove symlink to binary file and use text version instead
vold_decrypt: Add back missing xml and get rid of compiler warning
Add TWRP app install to landscape and watch themes
crypto: Use system's vold for decryption
Fix missing libf2fs.so needed by mkfs.f2fs
ADBBU: Cleanup string usage/namespace
Timeout for decrypt
gui: preserve order of gui_print vs gui_msg
languages: update chinese translation
Update Hungarian localization
Tweak MTP startup routine
Fix handling of USB config during MTP switching
twrpDigest: don't crash when zip.md5 file is empty
logd: add seclabel so that service runs in 7.1 tree builds
Use LOGI/LOGE for non-EVENT_LOGGING events
Run language_helper.py from inside languages dir
Update MTP debugging tags
Do not unconditionally remove MTP storage on unmount
Only change USB mode to mtp when ready for MTP
build: [FIXUP] Addendum for BusyBox get/setprop & API 24 vs 25
Fix "ordered comparison between pointer and zero".
Update Russian localization
cryptfs: Fix encryption issue due to stack corruption.
Add a listxattr tool for listing xattrs
libtar: support backing up and restoring new Android user.* xattr
Partition: Remove unused has_data_media variable
GUI: Fix typo in warning message
Symlink file_contexts --> file_contexts.bin
Fix bldr msg file open mode when offset specified
DE language update
Gottardo - languages: update italian translation
Update ru.xml for TWRP ver. 3.0.3.0
Improve backup display names with emulated storage
Fix crash during check for TWRP app
Fill uid/gid for screenshots at compile time
GUI: Improve automatic determination of TW_THEME
Allow custom bootloader msg offset in block misc
gui: Fix Android.mk for TW_CUSTOM_THEME
recovery: adjust mkfs.f2fs location
orscmd: add minimal getcap and setcap tools
Support power key on slideout
Whitespace cleanup in Themes
Disable relocations on orscmd to fix compile error in Omni 7.1
ifdef overlay graphics
Try mounting different filesystems during decryption
Add another license header
Fix detection of TWRP app in /data
gui: bump theme version to 2
bldrmsg: Only emmc /misc is supported
gui: Initialize button render position
HardwareKeyboard: Update event logging
GUI: Mark local flip() function as static
fb2png: Update/Cleanup headers
init: Remove duplicate trigger of load_system_props_action
Add missing file descriptor closes
Restore TW_BACKUP_AVG_IMG_RATE handling
Move sh selection out of GUI makefile
Move pigz symlinks out of GUI makefile
Add missing license headers
flashutils: additional emmc check
gui: Actions: Toggle backlight on power key
SELinux can be assumed for Android 4.4+
Restore file system type logline on restore
Do not disable performance mode too early for backup
Unused variable cleanup
Very minor code cleanup
Whitespace cleanup
gui: remove old unmaintained 2.x theme
libtar: backup and restore posix capabilities
ADBbackups: Fix wrong owner on binary backups.
Include symlink size (path length) in Get_Folder_Size()
gui: Detect device resolution with TARGET_SCREEN_HEIGHT/WIDTH
TWRP device version string
build: AOSP/CM14 fixes (API 24/25, mainly BusyBox-less environment)
updater: link libcrypto_utils_static if it exist
libtar: Use relative path for crypto/ext4crypt include
bootloader_message: Allow TWRP to ignore wipe-data command into misc
Support theme width and height offsets
build: Consolidate the crypto_utils presence tests
Fix compile error on 4.4 tree
Adjust & Improve Chinese translations for zh_CN/TW again
TWRP 3.0.3-5-TugaPower
Fixed bug intruduced on -4 on handling busybox callings
TWRP 3.0.3-4-TugaPower
Change version to 3.0.x to support the app release
Update Ukraine language translation
Add TWRP app install via TWRP recovery ( you can disable the prompt on settings )
TWRP Language Update
Change handling of /cache due to AB devices not having cache
Support backup/restore of FBE policies
Support File Based Encryption
Add boot slot support
Support new AB OTA zips
Improve backup & wipe exclusion handling
To the ones that have problem before on -3 report if all its fine on your side now....
TWRP 3.0.3-3-TugaPower 20-11-2016
Check if mount point is dir during startup
MD5 verification sanity
Fix libcrypto dependency in 6.0 trees
Clean up PartitionSettings
Fix compressed backups with split archives
twrp: Use the correct lib name
MD5 checking: fix issues introduced with adb backup patchset
Make naming scheme more meaningful
Fix compatibility across the board
Fix compatibility with 5.1
Make it backwards compatible with 4.4
TWRP 3.0.3-2-TugaPower 30-10-2016
Fixed the bug intruduced on 3.0.3-0 and 3.0.3-1 formating partitions.
Fixed log error on flashing Nougats ROMs
Added kernels logs as option to copy Logs options
Aroma support
Added Chinese/Japanese as availables languages
Improved image file flas
TWRP 3.0.3-1-TugaPower
Fixed/tweacked little more aroma bug intruduced on TWRP 3.0.3-0-TugaPower
TWRP 3.0.3-0-TugaPower
Fixed log error flashing Android N ROMs
updater: link libcrypto_utils_static if it exist
Copy Kernel Logs
libminiadbd: fix libadbd undefined reference to 'android_pubkey_decode' functions when build in cm-14.0
link libcrypto_utils.so to libminiadbd.so
Fix libcrypto dependency in 6.0 trees
twrp: Use the correct lib name
TWRP 3.0.2-6-TugaPower
Fixed bug introduced on 3.0.2-5 that will fail flashing boot and recovery images files from built in option on TWRP
If you are on 3.0.2-5 you will need to flash with fastboot or use some thirdy app.
TWRP 3.0.2-5-TugaPower
Fixed EFS backup/restore ( tested )
Removed recovery from backup list
Give another go at aroma zips
Clean up PartitionSettings
Fix compressed backups with split archives
Fix restore of subpartitions
MD5 checking: fix issues introduced with adb backup patchset
Added Chinese/Japanese as availables languages
TWRP 3.0.2-4-TugaPower
Added modem and recovery also as backup partitions
minui: Fix gr_set_font() build issue on cm-13.0 tree
NTFS-3g: migrate to PLATFORM_SDK check instead
Gui: replace pow() function
wait for cryptfs device node to come up
Add git revision to startup message in recovery.log
GUI: Use standard routine for auto-reboot
Fixup reboot after install variables
GUI: Add countdown & cancel to install auto-reboot
Finish creating disable_free_space_check variable
Allow running of a custom script after factory reset
Add build flag for forcing single buffer mode
Make input whitelist and blacklist work for mouse devices too
recovery: allow usage of TARGET_CRYPTFS_HW_PATH
bigbiff - Fix md5 creation from adb backup patch
adbbu: fix include path
Optimize and reduce size of PNG files
Add typecode to sgdisk for proper detection in Android
Remove curtainClose() remnants
Remove unused identifier from NotifyTouch
Move cursor after appending date to backup name
gui: fix Enter key in terminal
ADB: Add adb backup for TWRP
Increase EIO retry count
Check the results from applypatch
applypatch: Don't call inflate() when it expects zero-length output
Log source/target build version to last_install
Black screen patch for some HiSilicon devices (FBIOPAN_DISPLAY)
recovery: Make wear recovery more customizable
TWRP 3.0.2-3-TugaPowe
GUI: Use standard routine for auto-rebot
GUI: Add countdown & cancel to install auto-reboo
HACK: Fix AROMA Graphic
updater: Add LZMA support to blockim
Allow restore to read-only partition, part 2
Move force_rgb_565 up
crypto: remove redundant convert_key_to_hex_ascii call
TWRP 3.0.2-2-TugaPower
Fix flash of img files introduced on 3.0.2-1 ( boot / recovery )
Revert: Fixup reboot after install variables
revert: libenc: migrate to android_system_core
revert: ADB: Add adb backup for TWRP
revert: twrp: remove liblz4-static dependency
Wait to mount until after fstab processed
Remove char/string conversions in fstab processing
Rewrite FS fstab flag processing
Rewrite TWRP fstab flag processing
For the ones that have problems before ( backup/restore/openrecoveryscript) , try 3.0.2-2 please and report if its fixed...
Changed slightly the way things are handled
TWRP 3.0.2-1-TugaPower
Fixup reboot after install variables
libenc: migrate to android_system_core
ADB: Add adb backup for TWRP
Note how to use ADB backup:
Using adb backup on the client side you can backup the partitions TWRP knows about.
On the client side you can do the following:
adb backup -f --twrp where options are
--compress: compress data
system: backup system
cache: backup cache
data: backup data
boot: backup boot
etc for each partition.
You can string multiple options,
i.e. adb backup -f --twrp --compress cache system data
To restore the backup use the following convention:
adb restore
twrp: remove liblz4-static dependency
Improve greek translation
Languages: Add font for Japanese
Languages: Update Japanese translation
Restore TW_SCREEN_BLANK_ON_BOOT functionality.
Fix decrypt of odd number length PIN on hardware crypto
Partition: Fix parsing of several twrp fstab flags
Update spanish translation
Update hungarian translation
translate install reboot option to dutch
Greek Translation from the updated en.xml
TWRP 3.0.2-0-TugaPower
Revert: Qualcomm hardware decrypt: Use block device softlink
gui: don't mix up display value with actual value
language: add 2 new strings in it.xml
languages: add 2 new strings for RU
fix typo
TWRP 3.0.1-2-TugaPower
gui: add portrait_ldpi
Redefine yres_virtual only once
Qualcomm hardware decrypt: Use block device softlink
twrp: Unmount firmware partition on boot
Really remove all old SP* flags and code
TWRP 3.0.1-1-TugaPower
Fixed slow format intruduced on 3.0.1-0-TugaPower ( my bad )
Added again EFS and Firmware as Backup Option
TWRP 3.0.1-0-TugaPower
fix missing string Reboot Option
Removed EFS and Firmware Backup
language: add 2 new strings to DE
languages: add Reboot Option translation
HACK: fix input focus on terminal
progress: Initialize display percentage variable
Improve progress bar handling for backup / restore / image flash
DataManager Updates
languages: fix and improve german translation
languages: add Polish translation
twrp: update Dutch translations
Update & Fix ru.xml
recovery: update italian translation
gui: add italian translation
TWRP: hungarian translation
Add language_helper.py
Flashutils: detect /dev/block/sd* as emmc
Stop loading languages for the splash screen
Stop trying to load /script/ui.xml
recovery: czech translation
Improve input box text handling
Detect and install custom themes as part of zip installs
gui: rewrite theme loading code
TWRP 3.0.0-6-TugaPower
TWRP Reboot Option after zip flash 5seconds
Removed slb1 from firmware list as backup
Merge code from upstream libtar + bug fixes
Revert: Update libtar with changes from cm-13.0
SplashScreen less time
TWRP 3.0.0-5-TugaPower
Fixed double restore of firmware backup
Allow setting backup file system from recovery fstab
Don't add subpartitions in firmware to restore list
Unix file endings and remove execute permission
Fix verifier_test build
Revert: WIP: use toolbox for ln instead of busybox
TWRP 3.0.0-4-TugaPower
Include firmware in ramdisk to avoid touching /firmware
Backup firmware re-added
Github for your changes?
Sent from my A0001 using Tapatalk
Awesome, love your ROM and now you've got your own recovery! :good:
Thanks!
Wisiwyg said:
No credit to @katinatez and @ketut.kumajaya for their work for the last year or two?
Click to expand...
Click to collapse
He has written that he is not finished with the original post. Give him some time and I'm sure he'll give credit to whomever credit belongs.
Thank you @danieldmm , I've always been using your version of twrp with your fixed and I'm glad you're carrying on the work for our devices.
Please guide, currently I have official TWRP 2.8.6.0 installed. So can I just flash this over it through TWRP image option or through Flasify or do I need to use adb commands.
[email protected] said:
Please guide, currently I have official TWRP 2.8.6.0 installed. So can I just flash this over it through TWRP image option or through Flasify or do I need to use adb commands.
Click to expand...
Click to collapse
Flashify works fine to install it
love your browser!!!
Sent from my A0001 using XDA-Developers mobile app
*Tuga HI5*
Does fix AROMA graphic mean that aroma installer fully works? Or does it just give the ability to see AROMA graphics but the installer is non functional?
oh yeah... following and subscribed immediately...
f41lbl0g said:
Does fix AROMA graphic mean that aroma installer fully works? Or does it just give the ability to see AROMA graphics but the installer is non functional?
Click to expand...
Click to collapse
id like to know this too :good:
@danieldmm AROMA installer works for me, only problem is that debug log shows on top of the installer making view difficult. I noticed also that in latest build the firmware backup is gone, showing only EFS, is that normal/volunteer?
Lisko said:
@danieldmm AROMA installer works for me, only problem is that debug log shows on top of the installer making view difficult. I noticed also that in latest build the firmware backup is gone, showing only EFS, is that normal/volunteer?
Click to expand...
Click to collapse
Yes, few builds back remove the firmware part because of the risk of restoring goes wrong or corrupt relative to aboot, if this happen phone will not boot, you will not have fastboot, you cannot boot to recovery. Only way to fix it's using qualcomm diag mode to flash bootloader again. Although on my next version will make the option to backup only modem as firmware. Its more then enough nowadays. Relative to aroma what zip did you tried? Tested with open gapps aroma and the debug log will not show. At least with open gapps aroma package.
Wisiwyg said:
No credit to @katinatez and @ketut.kumajaya for their work for the last year or two?
Click to expand...
Click to collapse
The only credits can give to both Devs was back on the time before making my own build of twrp, was using is recovery on my device. My credits on this goes all to Omnirom team that work with the recovery part. My TWRP is build based on Omnirom recovery tree and device tree of bacon from CM13. All this will be written on OP. Just did not managed to have time to that. Sorry
danieldmm said:
Yes, few builds back remove the firmware part because of the risk of restoring goes wrong or corrupt relative to aboot, if this happen phone will not boot, you will not have fastboot, you cannot boot to recovery. Only way to fix it's using qualcomm diag mode to flash bootloader again. Although on my next version will make the option to backup only modem as firmware. Its more then enough nowadays. Relative to aroma what zip did you tried? Tested with open gapps aroma and the debug log will not show. At least with open gapps aroma package.
Click to expand...
Click to collapse
opengapps (tried different builds) and aromafm, latest and previous recovery builds. I have materialized theme installed, may be a theme issue?
Lisko said:
opengapps (tried different builds) and aromafm, latest and previous recovery builds. I have materialized theme installed, may be a theme issue?
Click to expand...
Click to collapse
It could be, just in case be sure you are using my lattest build of TWRP, delete .twrps file inside twrp folder and theme. Then try again.
Enviado do meu A0001 através de Tapatalk
danieldmm said:
It could be, just in case be sure you are using my lattest build of TWRP, delete .twrps file inside twrp folder and theme. Then try again.
Enviado do meu A0001 através de Tapatalk
Click to expand...
Click to collapse
Without materialized theme aroma works as it should be. Sadly was a nice theme.):
Do you guys have any idea as to why kumajaya's TWRP builds seem to read and write nand much faster than these Tuga builds or the official builds? Especially kumajaya's 3.0.0 and 2.8.7 ones perform a significantly faster backup and restore, all other variables same.
Hello,
I have a device called RATEL CELL R1020 with OS android 8.0 oreo.
I tried some applications for rooting this smartphone like kingroot, kingoroot, etc but failed. This device can't unlock bootloader, so I see rooting with exploit in youtube like thomasking. Please anyone here help me to rooting my smartphone?
4.4.78perf+ kernel
this attachment is screenshot of the system
Thankyou
j4nn said:
@arifincaesar, do you have your phone's firmware in a downloadable form? Can you obtain linux kernel source code for your phone?
I could imagine adapting this (exploit source code here) for your phone, but the kernel binary that is running on the phone is a must pre-requisite. Obviously it would be only a temp root.
Click to expand...
Click to collapse
arifincaesar said:
there is no way to get firmware of this phone sir..
and there's no way to unlock bootloader..
i think the only way to backup firmware this device is exploit and getting root access without ubl..
there is just said 4.4.78-perf+
Click to expand...
Click to collapse
In my opinion, there is no exploit that would not need offsets within kernel image in advance.
Because of that you need a copy of kernel binary that is running on the phone.
Obviously it is not possible to back up kernel partition from the phone, so you would need the original fw (the same version that is running on the phone) and a way to extract the kernel from the fw package.
Without that you are out of luck, sorry...
Since there is linux kernel running on the phone (android uses linux kernel) you have legal options to request corresponding kernel source code, because linux kernel is distributed under gpl license.
But even if you obtained the kernel source, you would still need the binary, because most likely the new build from source would not be binary identical. The source code would just make it easy to decide which exploit could work, so it would make sense to adapt it for the kernel binary.
j4nn said:
In my opinion, there is no exploit that would not need offsets within kernel image in advance.
Because of that you need a copy of kernel binary that is running on the phone.
Obviously it is not possible to back up kernel partition from the phone, so you would need the original fw (the same version that is running on the phone) and a way to extract the kernel from the fw package.
Without that you are out of luck, sorry...
Since there is linux kernel running on the phone (android uses linux kernel) you have legal options to request corresponding kernel source code, because linux kernel is distributed under gpl license.
But even if you obtained the kernel source, you would still need the binary, because most likely the new build from source would not be binary identical. The source code would just make it easy to decide which exploit could work, so it would make sense to adapt it for the kernel binary.
Click to expand...
Click to collapse
is that bug when i had activated oem unlock in dev options but cannot unlock with fastboot mode?
j4nn said:
In my opinion, there is no exploit that would not need offsets within kernel image in advance.
Because of that you need a copy of kernel binary that is running on the phone.
Obviously it is not possible to back up kernel partition from the phone, so you would need the original fw (the same version that is running on the phone) and a way to extract the kernel from the fw package.
Without that you are out of luck, sorry...
Since there is linux kernel running on the phone (android uses linux kernel) you have legal options to request corresponding kernel source code, because linux kernel is distributed under gpl license.
But even if you obtained the kernel source, you would still need the binary, because most likely the new build from source would not be binary identical. The source code would just make it easy to decide which exploit could work, so it would make sense to adapt it for the kernel binary.
Click to expand...
Click to collapse
can you help me please?
arifincaesar said:
can you help me please?
Click to expand...
Click to collapse
Interesting. Getting kernel space R/W primitives is a nice first step.
But without kernel binary, that still may be difficult - with kernel 4.4.78 version, KASLR would be there for sure.
j4nn said:
Interesting. Getting kernel space R/W primitives is a nice first step.
But without kernel binary, that still may be difficult - with kernel 4.4.78 version, KASLR would be there for sure.
Click to expand...
Click to collapse
hehe i keep watching your work for exploit sir
if there something new exploit i'll try to my phone
thx before
@arifincaesar, try this please:
Code:
cd /data/local/tmp
echo -e '#!/system/bin/sh\ncase "$1" in\n*model) echo G8441 ;;*) echo 47.1.A.8.49 ;;esac' > getprop
chmod 755 getprop
PATH=`pwd`:$PATH ./bindershell
That should try the offsets defined for xz1c. It's a blind try, but let's see.
Please post the log in a text form (copy it via clipboard from the terminal), using the CODE tags in the message (can be used with the # icon in advanced post).
Code:
cd /data/local/tmp
echo -e '#!/system/bin/sh\ncase "$1" in\n*model) echo G8441 ;;*) echo 47.1.A.8.49 ;;esac' > getprop
chmod 755 getprop
PATH=`pwd`:$PATH ./bindershell
i can't believe, it work bro i swear :v
is that my phone rooted?
nope i think my phone is not rooted yet..
i check from root checker it say "sorry root access is not properly installed on this device."
@j4nn heres the output
bindershell - temp root shell for xperia XZ1c/XZ1/XZp using CVE-2019-2215
https://github.com/j4nn/renoshell/tree/CVE-2019-2215
MAIN: starting exploit for devices with waitqueue at 0x98
PARENT: Reading leaked data
PARENT: leaking successful
MAIN: thread_info should be in stack
MAIN: parsing kernel stack to find thread_info
PARENT: Reading leaked data
PARENT: Reading extra leaked data
PARENT: leaking successful
MAIN: task_struct_ptr = ffffffcfe0d68000
MAIN: thread_info_ptr = ffffffd04aa3c000
MAIN: Clobbering addr_limit
MAIN: should have stable kernel R/W now
kernel slide invalid (0x4ffabc7b50)
kaslr slide 0x0
selinux set to permissive
current task credentials patched
got root, start shell...
Cell:/data/local/tmp # id
uid=0(root) gid=0(root) groups=0(root),1004(input),1007(log),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats),3009(readproc) context=u:r:shell:s0
Cell:/data/local/tmp # cd
Cell:/ # ls
ls: ./cache: Permission denied
ls: ./init: Permission denied
ls: ./init.environ.rc: Permission denied
ls: ./init.rc: Permission denied
ls: ./init.recovery.qcom.rc: Permission denied
ls: ./init.usb.configfs.rc: Permission denied
ls: ./init.usb.rc: Permission denied
ls: ./init.zygote32.rc: Permission denied
ls: ./init.zygote64_32.rc: Permission denied
ls: ./postinstall: Permission denied
ls: ./ueventd.rc: Permission denied
ls: ./verity_key: Permission denied
acct bt_firmware bugreports charger config d data default.prop dev dsp etc firmware lost+found mnt oem persist proc res root sbin sdcard storage sys system vendor
1|Cell:/ #
@arifincaesar, well, as expected, detecting KASLR slide failed, therefore selinux could not be disabled and security context has not been patched either.
Without a kernel binary, it is difficult to implement a full temp root exploit.
I guess it could be doable, unfortunately I do not have the time for it.
j4nn said:
@arifincaesar, well, as expected, detecting KASLR slide failed, therefore selinux could not be disabled and security context has not been patched either.
Without a kernel binary, it is difficult to implement a full temp root exploit.
I guess it could be doable, unfortunately I do not have the time for it.
Click to expand...
Click to collapse
hehe thanks for information sir..
@arifincaesar, see PM please...
j4nn said:
@arifincaesar, see PM please...
Click to expand...
Click to collapse
ok sir, thank you very much for helping me.. T_T
pm sent
cve-2019-2215 based temp root exploit for ratel cell r1020
Here is a temp root exploit tailored specifically for RATEL CELL r1020 phone as described in the OP (Android 8.0 with security patch level of January 5, 2018). The exploit uses CVE-2019-2215, which can get you a temporal root shell very quickly and reliably (it's nearly instant).
Unfortunately RATEL CELL r1020 firmware is not publicly available, so it had not been possible to get a kernel image for analysis.
Luckily the first stage of the exploit designed for sony xperia xz1/xz1/xz1c worked, providing kernel space R/W primitives.
Eventually kernel memory dump has been retrieved (after KASLR bypass done in a generic way), so implementation of the final stage to bypass selinux and patch credentials to get root could be done.
Please find the result of my work attached here, it obviously is not tested as I do not have that phone, but I assume it would work as using similarly calculated stuff worked with my xz1c phone.
Please see the xperia phones exploit here for usage howto, including possibility to setup magisk from the exploit (modified script without sony specific stuff is already included). Just download the Magisk-v19.3-Manager-v7.1.2.zip from the linked post and use together with stuff from ratel-cell-temp-root.zip attached here.
EDIT: Updated ratel cell temp root with v2, supposed to work also with ratel cell having May 1, 2018 security patch level.
Please post the log (in [ CODE ] tags) and/or screenshots from your testing, possibly including even magisk setup, if bindershell exploit worked.
If you like my work, you can donate to me via paypal (including card payment) or bitcoin - for details just follow the "Donate to Me" button please. Thank you.
Thread closed per OP request.
MOD ACTION:
Thread reopened per OP's request
j4nn said:
Here is a temp root exploit tailored specifically for RATEL CELL r1020 phone as described in the OP (Android 8.0 with security patch level of January 5, 2018). The exploit uses CVE-2019-2215, which can get you a temporal root shell very quickly and reliably (it's nearly instant).
Unfortunately RATEL CELL r1020 firmware is not publicly available, so it had not been possible to get a kernel image for analysis.
Luckily the first stage of the exploit designed for sony xperia xz1/xz1/xz1c worked, providing kernel space R/W primitives.
Eventually kernel memory dump has been retrieved (after KASLR bypass done in a generic way), so implementation of the final stage to bypass selinux and patch credentials to get root could be done.
Please find the result of my work attached here, it obviously is not tested as I do not have that phone, but I assume it would work as using similarly calculated stuff worked with my xz1c phone.
Please see the xperia phones exploit here for usage howto, including possibility to setup magisk from the exploit (modified script without sony specific stuff is already included). Just download the Magisk-v19.3-Manager-v7.1.2.zip from the linked post and use together with stuff from ratel-cell-temp-root.zip attached here.
Please post the log (in [ CODE ] tags) and/or screenshots from your testing, possibly including even magisk setup, if bindershell exploit worked.
Click to expand...
Click to collapse
yes, it work sir thank you so much here is the log
but i think there other problem i will posting it later here
Code:
Cell:/data/local/tmp $ ./bindershellnew
bindershell - temp root shell using CVE-2019-2215, tailored for RATEL CELL R1020
https://github.com/j4nn/renoshell/tree/CVE-2019-2215
MAIN: starting exploit for devices with waitqueue at 0x98
PARENT: Reading leaked data
PARENT: leaking successful
MAIN: thread_info should be in stack
MAIN: parsing kernel stack to find thread_info
PARENT: Reading leaked data
PARENT: Reading extra leaked data
PARENT: leaking successful
MAIN: task_struct_ptr = ffffffd4316e9b00
MAIN: thread_info_ptr = ffffffd471268000
MAIN: Clobbering addr_limit
MAIN: should have stable kernel R/W now
attempting kaslr bypass: leaked ptr 0xffffff8a82608658
kernel base=0xffffff8a81480000 slide=0xa79400000
selinux set to permissive
current task credentials patched
got root, start shell...
Cell:/data/local/tmp # getenforce
Permissive
Cell:/data/local/tmp # id
uid=0(root) gid=0(root) groups=0(root),1004(input),1007(log),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats),3009(readproc) context=u:r:toolbox:s0
Cell:/data/local/tmp # uname -a
Linux localhost 4.4.78-perf+ #1 SMP PREEMPT Tue Mar 6 11:00:11 CST 2018 aarch64
Cell:/data/local/tmp #
Hi there sir @j4nn .
I'm yusuv, ratel cell user. I've been following this thread.
And lately seems the exploit works as intended.
The things is, ratel cell not only have the January patch on all the devices. I've tried the exploit and its stuck on the build number prop and it won't go any further.
Afaik, ratel have 2 ROM builds, one patch is January which is you build the exploit for, the other one is May 1, 2018 patch. With also different build number.
On behalf Ratel Cell user with the may patch. I'm here to ask you, is there any way for us with the May patch being able to root our device?
Thanks in advance.
Dear sir @j4nn.
can you help us on how to install custom recovery in Ratel Cell, if you are willing to help, we will be very grateful.
I tried to root my infinix note 10. Plz guide me
Rooting your phone's Android 11 is done by adding a superuser- AKA root ( read: user with elevated rights ) to Android.
This can get achieved by
either
adding SU binary to Android's filesystem
or
replacing the pre-installed Toybox binary - what is a restricted version by defaut - by Toybox version 0.8.5 what comes with SU implemented.