Related
guYs,
check out this awesome package manager BotBrew. mostly of use to software developers. works like a charm on SGY (at least the debug version, which is attached)
http://forum.xda-developers.com/attachment.php?attachmentid=978569&d=1333376821
http://botbrew.com/manual.htm
use on PC: winSCP, PuTTY
on android: SSHDroid, botbrew, terminalIDE
then you have bbsh (from botbrew) & bash (terminalIDE)
run botbrew app (root required), then
install "hello"
adb shell botbrew hello
or equivalent
adb shell
su
cd /botbrew/bin
./hello
asf.
directories used:
/data/botbrew --------------- you may need to delete manually here to regain space after apk uninstall
/botbrew
/etc/opkg
/system/share/opkg
see also portal news on botbrew and the tag botbrew below for link to release thread.
{
"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"
}
mai77 said:
guYs,
check out this awesome package manager BotBrew. mostly of use to software developers. works like a charm on SGY (at least the debug version, which is attached)
http://forum.xda-developers.com/attachment.php?attachmentid=978569&d=1333376821
see also portal news on botbrew and the tag botbrew below for link to release thread.
Click to expand...
Click to collapse
@mai77, for what use is this thing mai77? hehe dont know what is this
I thought its used to see all installed packages in our device. including the apk's, jar, and binary file...isn't it mai?
well it installs all the GNU binaries, for starters.
gives you regular LINUX shell environment.
I thought busybox is already more than enough for a mid user like me (lol)
Thanks for making this thread, mai77. Thought I'd chime in
Indeed, the busybox that comes with your rooted ROM is probably more than enough for most users. BotBrew also depends heavily on busybox, but comes with a more complete build that has almost all of busybox (we try to include applets rather than exclude them). There are also tools that aren't in busybox, such as dropbear and rsync.
You're right that most casual Android users would probably not use these command line tools, but BotBrew really wants to be a tool for community developers to distribute scripts/enhancements/whatnot, and for users to find all these offerings in one place. The native tools currently in the repositories serve to support package management and to show off the dependency resolution functions (i.e. to install A, you need B and C, so all three pieces of software get installed).
I hope that clears it up a bit.
$0.00 Apple
with this package manager in place, APPLE stock prices will drop like a ******* stone
Hey, any chance you can bring in package Apache and it's dependencies?
I have an idea for a cool episode of XDATV sometime in the far future. I'd like to have apache to remote control the device.
Would lighttpd do? If not, I'll look into getting Apache; dependencies included, of course.
inportb said:
Would lighttpd do? If not, I'll look into getting Apache; dependencies included, of course.
Click to expand...
Click to collapse
I've never used that one. It probly would. I need something that can run scripts on the phone.
What kind of scripts? Shell scripts? PHP scripts?
If you need Python or Ruby, I've already seen django- and rails-based Web servers (which could run shell scripts too, using subprocesses) working.
/edit:
Okay, here's a basic demo of running shell scripts remotely using a Python-based Web server: https://gist.github.com/2373824
You will need bottle.py, which you could obtain from http://pypi.python.org/pypi/bottle/0.10.9 (all you need is bottle.py from the archive)
Anyway. Put both files in the directory, make (chmod) webctrl.py executable, and run `botbrew ./webctrl.py`. Now navigate to http://ip-address-of-android:8080/ps to get a process listing, and so on. If you want, you could make a runit script to start this service at boot. But before you go any further with this, be aware of the security implications -- you're exposing a root interface to the world, so it would be a good idea to lock it down somehow and/or drop root privileges.
Yeah. Just shell scripts. If you check out developer.adamoutler.com and go to the hackaday santapede repository ive set up, im basically going to reincarnate that. It is a web server that communicates with a serial device that controls another device. I think it would be pretty cool to set up a phone as a project brain to leverage its wifi capabilities... amongst other things.
Im mobile on a stock nook tablet now so i cant copy pasta but you can see a video of the desktop linux webserver controlling a robotic dancing, walking santa with a machine gun and rocket launcher on my youtube channel.. youtube.com/outleradam this is along the line sof my idea.
I think that's doable; I updated the script so that it does essentially the same thing as Apache+CGI. Just clone that gist, add bottle.py, and run webctrl.py
But are you able to get a connection from your Android device to Santa? I'm guessing that if you could get your Android device to act as a USB host, and it has /dev/ttyUSB0, the script would work unmodified.
think could you port wget or aptitude? not sure about the dependencies but that would be a little easier to use then subversion. does botbrew have repo support?
Wget, aptitude, and subversion are three totally different tools. Busybox has a wget applet, so all you need is a symlink. Aptitude would not be very useful without dpkg. Subversion is already available, and so is git. What do you mean by repo support?
inportb, you're a hero...
inportb, I've been following your work for about 4 months (repo.bash and even more opkg & botbrew...), and I've been amazed...!
i ****ing love botbrew, but i flashed a rom (cleanblank) on my sgs2 (i9100) and i can't find botbrew on the market..
can you fix that? or it's not your fault?
also, please, i'm begging you... i want PHP 5! please! i can't compile it! compiling windows is easier!!!
is there any possibility of compiling PHP for ex. on my device (autoconf+gcc+make)?
how can i create an opk after compiling?
a detailed version of setting up the toolchain on Arch linux?
thank you for your time!!
keep up the good work!
edit: may you compile bash too?
Not to worry... all this is coming soon because BotBrew+1 will use dpkg instead of opkg (so you could install Debian packages, or a complete Debian if you wanted to). This is taking some time because the GUI needs to be redone, but the minimal dpkg core is available as a tech demo "PengDroid". I have yet to figure out how to translate the "service manager" concept, but I'm thinking. Also, the toolchain is not going away; in addition, I have built an NDK that runs on PengDroid but generates binaries for stock Android/ARM, in an effort to support onboard development.
I know that documentation is lacking... for now, please feel free to ping me (Pinako) on IRC (#botbrew on irc.freenode.net) about that. I'm currently mobile, but I'll pass on the instructions when I find a good desk for my netbook. Thanks for your continued support!
Regarding BotBrew support for your ROM: it should be compatible with systems based on Android 2.2+. If you navigate to the app page using your Web browser, does it say that it's incompatible?
btw, I think Arch is an excellent distro; even though I mostly use Debian, I took hints from Arch while designing the cross-building tools.
I tried to use botbrew to install the "lighttpd" package.. this is what was returned on my Infuse4G.. Otherwise botbrew works fine.
For some reason it's reporting that it is out of space. It is not. There is plenty of space. You can see that at the bottom where I ran the "df" command.
Code:
1|[email protected]:/ $ opkg install lighttpd
Package android-framework-pdroid-v6 version 1.3.2-4 has no valid architecture, ignoring.
Package android-framework-pdroid version 1.3.2-6 has no valid architecture, ignoring.
Package android-framework-pdroid version 1.3.2-6 has no valid architecture, ignoring.
Package android-framework-pdroid version 1.3.2-4 has no valid architecture, ignoring.
Package android-framework-pdroid version 1.3.2-2 has no valid architecture, ignoring.
Package android-framework-pdroid version 1.3.2-7 has no valid architecture, ignoring.
Package android-framework-services-v6 version 0.0.4-6 has no valid architecture, ignoring.
Package v6-supercharger version 8.8.1-2 has no valid architecture, ignoring.
Installing lighttpd (1.4.30-1) to root...
Copying /botbrew/var/tmp/opkg/archives/lighttpd_1.4.30-1_armeabi.opk.
Installing libbz2 (1.0.6-3) to root...
Copying /botbrew/var/tmp/opkg/archives/libbz2_1.0.6-3_armeabi.opk.
Collected errors:
* copy_file: unable to preserve ownership of `/botbrew/var/tmp/opkg/tmp/opkg-Nn3447/lighttpd_1.4.30-1_armeabi.opk': Operation not permitted.
* copy_file: unable to preserve ownership of `/botbrew/var/tmp/opkg/tmp/opkg-Nn3447/libbz2_1.0.6-3_armeabi.opk': Operation not permitted.
* pkg_get_installed_files: Failed to make temp file /botbrew/var/tmp/opkg/tmp/opkg-Nn3447/libbz2.list.Uo3447.: No space left on device.
* pkg_get_installed_files: Failed to make temp file /botbrew/var/tmp/opkg/tmp/opkg-Nn3447/libbz2.list.WD3447.: No space left on device.
* wfopen: /botbrew/lib/libbz2.so: Permission denied.
* wfopen: /botbrew/lib/libbz2.so.1.0.6: Permission denied.
* wfopen: /botbrew/lib/libbz2.so.1.0: Permission denied.
* pkg_write_filelist: Failed to open //botbrew/var/lib/opkg/info/libbz2.list: No space left on device.
* opkg_install_pkg: Failed to extract data files for libbz2. Package debris may remain!
* opkg_install_cmd: Cannot install package lighttpd.
* opkg_prep_intercepts: Failed to make temp dir /botbrew/var/tmp/opkg/tmp/opkg-Nn3447/opkg-intercept-qk3447: No space left on device.
255|[email protected]:/ $ df
Filesystem Size Used Free Blksize
/dev 221M 32K 221M 4096
/mnt/asec 221M 0K 221M 4096
/mnt/obb 221M 0K 221M 4096
/mnt/.lfs: Function not implemented
/system 273M 227M 46M 4096
/cache 26M 4M 22M 4096
/data 1G 406M 1G 4096
/efs 5M 819K 5M 1024
/mnt/sdcard 13G 5G 7G 32768
/mnt/secure/asec: Permission denied
/mnt/asec/com.outfit7.talkingtom-1 13M 8M 4M 4096
/botbrew 1G 406M 1G 4096
/botbrew/run 221M 0K 221M 4096
/mnt/asec/com.ValhallaStudiosBifrost.Photon-2 14M 12M 2M 4096
/mnt/asec/com.inertsoap.fingerzilla-1 27M 25M 1M 4096
/mnt/emmc 7G 749M 6G 32768
1|[email protected]:/ $
p
Do you have superuser privileges? It seems that it was not able to access some files.
inportb said:
Do you have superuser privileges? It seems that it was not able to access some files.
Click to expand...
Click to collapse
Yeah. Botbrew is installed and working.. maybe it has system dependencies that are incompatible with Android 4.0? I am having a problem with my Galaxy Nexus and my Infuse 4g. The infuse4g is running CM9. The galaxy Nexus is running 4.0.2 AOSP stock. Both devices are rooted. Is there some way to increase logging levels?
I have a feeling it has to do with the way 4.0 handles storage.
IMP NOTE : Use " python-2.7.xx" ,latest version otherwise extractor will led to undesired output like this one https://forum.xda-developers.com/showpost.php?p=72165633&postcount=295 and extractor supports android 7.1.2(updated on 18-May-2017)
Extractor of system.new.dat of Marshmallow and Lollipop ROM's
{
"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"
}
DOWNLOAD
OLD
Extractor 1.0
or
Mirror
Extractor 2.0
Extractor 3.0
UPDATED
Extractor 4.8 (Updated on 18-May)
SOURCE
$GIT-HUB Contribute!
Changelog -> https://github.com/matriex/System_Extractor-WIN/commit/4b94cde74f63f6f1ff21b8c745b306326b15cb5a
Alternative of repack, if the repack script doesn't works with your system folder then try this script SCRIPT / GUIDE
How to
Extract ext4-Image files
Download Imgextractor.exe binary from the link
https://github.com/matriex/System_Extractor-WIN/blob/master/bin/Imgextractor.exe
1. Create a folder named ext and copy the binary to ext folder
2. Copy your image file ,say "system_1.img" to ext folder
3. Select the ext folder , hold the shift (right) click RMB
4. Select "Open command window here"
5. Then type this command on CMD
Code:
Imgextractor.exe system_1.img -i
6. The files will be in "system_" named folder.
NOTE:You should rename IMG file to system_1.img before doing anything
Extract *.DAT files
Users, The extractor works with nought 7.0.0 and 7.1.1 perfectly (tested with CM14.1-2016-12-12 & aosp_7.0_2016-09-19), If you encounter errors then please install python and then try extracting again
Method I
Download and run the extractor .
METHOD II (command line)
Use python 2.7.xx
1. Download zip and extract sdat2img.py binary from the link
https://github.com/xpirt/sdat2img/archive/master.zip
2. Create a folder "ext"
3. copy "sdat2img.py", "system.transfer.list" and "system.new.dat" to ext folder
4. Open cmd on "ext", (by selecting and holding shift , you will find "Open command window here")
5.Type this on command window
Code:
python sdat2img.py system.transfer.list system.new.dat system.img
6. After that you'll find system.img on that folder, that image file is ext4 image file and can be extracted by this guide
http://forum.xda-developers.com/showthread.php?t=2285831
END OF SUPPORT I DON'T HAVE ANY METHODS LEFT AND PLESE ASK PROBLEMS RELEATED TO ANDROID 6.0 ONLY
Repack *.DAT
/*Repack will or will not work, Don't panic if it not worked, You can still use folder =) */
For flashing xyz_ROM.zip with dat files , you need to modify updater-script
Script, "of some roms" , b'coz some roms contains a link b/w updateR-script
and system.transfer.list. The link includes following : There is a line in
updateR-script script called
Code:
if range_sha1("/dev/block/platform/msm_sdcc.1/by-name/system", "36,0,32770,......,307199") == "0b20303394271424267e36a0ce7573f1b62ddc0d" then
if you found this in
updateR-script then from here follow the guide Repack_INFO.txt otherwise
directly copy system.new.dat and system.transfer.list to ROM folder and
repack/zip it and flash it.
Repack ,select from script, then choose manually (option 1)
Copy all your ROM files/subfolders(bin ,app ,build.prop etc) to system folder
Everything is expalined in extractor, read it carefully
If you found "range_sah1()" on your updateR-script then continue below, else only you have to replace system.new.dat and system.transfer.list of "xyz_ROM"
CONTINUE ONLY IF YOU FOUND RANGE RANGE_SHA1
After repack a SHA1_VALUE of system.new.dat is generated and file is created as "SHA1_VALUE.txt" with "system.new.dat" & "system.transfer.list"
And follow this guide Repack_INFO.txt (attached end of this POST)
OR GIT ATTACHEDhttps://github.com/matriex/System_Extractor/blob/master/Repack_INFO.md
That's all if you need help feel free to comment
Thanks for using this method I can't say it will work , but what's wrong in trying , I tried 10 to 20 times to make it work
A LITTLE ADVICE
1. If the script failed to work ,please take a look at this post again I'm sure I've posted enough resource which will help you out in extracting and repacking .DAT files .
2. Please keep this thread clean.
3. Please don't quote whole thread(use tags).
4. I take no responsibility of repacking system.img!
5. For Linux users :https://github.com/matriex/System_Extractor-Linux/blob/master/README.md
6. Use Python 2.7.x or otherwise extractor will not work Do not use python 3.0 or update sdat2img.py binary!
Thanks to @xpirt for sdt2img
Repack_INFO.txt (GIT-HUB, clear view)
Any possible way to put it back?
? if possible Or why don't you flash it directly by folder
matrixex said:
Wait comming soon if possible
Or why don't you flash it directly by making some changes in updater-script
Click to expand...
Click to collapse
I am in no dire need of it right away, I am just asking for any future need.
nicesoni_ash said:
I am in no dire need of it right away, I am just asking for any future need.
Click to expand...
Click to collapse
Hi
I have successfully created repack script for system to dat , download it and reply worked or not
Deleted
Deleted
Works well on new Nutella OTA images. Thx
tweakradje said:
Works well on new Nutella OTA images. Thx
Click to expand...
Click to collapse
Cool please give me the link to android N OTA
Sure. Here you go http://developer.android.com/preview/download-ota.html
Cheers
tools not working broo
Source
Tools not working bro
Thanks. Tested and it worked.
v3ndul said:
Tools not working bro
Click to expand...
Click to collapse
Impossible i have tried it with marshmallow and Lollipop system.new.dat files several times(truly 4-5 ROMS more than 10times) it worked without any issues please be sure that you have copied your files as stated and also match the names as stated in extractor.
Don't copy whole post just use HIDE
v3 doesnt work. when I open it (with admin rights) I see the copyright and warnings then it closes and opens a new windows. it does that again and again sort of like a loop
Abaddon said:
v3 doesnt work. when I open it (with admin rights) I see the copyright and warnings then it closes and opens a new windows. it does that again and again sort of like a loop
Click to expand...
Click to collapse
same here
edit: solved using this version
View attachment 3692066
kenzolo said:
same here
edit: solved using this version
View attachment 3692066
Click to expand...
Click to collapse
Abaddon said:
v3 doesnt work. when I open it (with admin rights) I see the copyright and warnings then it closes and opens a new windows. it does that again and again sort of like a loop
Click to expand...
Click to collapse
I am really sorry this is because i converted bat file to exe file
Just uploaded a new version of v3.0 just download it
And you will get two things
1 bin
2 system_extractor.bat
Just run system_Extractor and enjoy
v3ndul said:
Tools not working bro
Click to expand...
Click to collapse
Don't quote the op.
Hi,
I've managed to extract, but repacking is giving the following error:
Found System FOLDER
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
error: ext4_allocate_best_fit_partial: failed to allocate 584 blocks, out of space?
Click to expand...
Click to collapse
I double checked, and I haven't ran out of disk nor RAM.
Can you help me?
Thanks
pacacc said:
Hi,
I've managed to extract, but repacking is giving the following error:
I double checked, and I haven't ran out of disk nor RAM.
Can you help me?
Thanks
Click to expand...
Click to collapse
No bro you haven't ran out of disk or RAM :silly:
This problem persist due to size of your system folder i.e it must be greater than 2GB
Right?
Don't worry jusy edit my batch file code using notepad ++
Here which line you have to edit
Search this line
bin\make_ext4fs.exe -s -l 2048M system.img system
Now replace 2048M with 4096M
After that the line will look like
bin\make_ext4fs.exe -s -l 4096M system.img system
And after that save it.
Done
Reply it worked or not
EDIT ON 30/5/2016
Use new version 4.0 IT CAN CALCULATE SIZE AUTOMATICALLY NO NEED TO EDIT SCRIPT
thanks for sharing this
i'm done the following
1. unpack
2. editing system file content(replace & delete)
3. repack (without error)
4. copy 2 file (system.new.dat & sistem.transfer.list) through 7zip
is that the correct steps? i mean, after that i can flash it like other rom zip
I present to you
Project ROC - Remix OS Custom
{
"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"
}
I spend countless nights developing roms, awesome mods, and scripts, if you wish to support my work and future developments you can donate to me via the link here!
Features:
1. XposedFramework V86 X86
2.Pre-rooted with SuperSU 2.76
3.Busybox
4.CM File Manager (root access to files)
5.Deodexed
6.Debloat
7.Adaway
8.GAPPS
Changelog for Project ROC
V3.0.207
Updated to version 3.0.207
Updated GAPPS
Updated SuperSU
V3.0.206
Xposed Framework V86 X86
SuperSU 2.76
Busybox
CM File Manager
Deodex
Adaway
Changelog for Remix OS 3.0.207 by Jide
Remix OS version: 3.0.207
Release date: November 25, 2016
Remix OS Build Number - 64-bit: B2016112101
Remix OS Build Number - 32-bit: B2016112201
Release notes:
1. Added Verbose mode to save log files for easier debugging.
Guidelines: https://github.com/JideTechnology/Remix-OS-For-PC/wiki
2. Updated Linux kernel to 4.4.30
3. Added "Never sleep option" to be seen in languages other than English
4. Fixed a bug there was an issue remembering the last selected system in your boot menu
__________________________________________________ _____________
If you experience any bugs or issues, report it through our Verbose mode!
Changelog for Remix OS 3.0.206 by Jide
Release date: October 11, 2016
Release notes:
- Houdini update resolved issues with apps like Snapchat and Candy Crush
- Fixed most dual GPU issues
- Fixed keyboard input issues when key-mapping is activated
- Fixed conflicts between mouse and keyboard input when key-mapping is activated
- Added Wi-Fi drivers for Realtek wireless cards - rtl8723bs, rtl8723bu, rtl8812au
- Updated Gaming Toolkit to v.1.2.1
- Improved boot menu
- Added touchscreen drivers from Next Window (touchscreen manufacturer)
- Ads have been removed from the 'My apps' section of your app drawer
Click to expand...
Click to collapse
Install Instructions:
LEGACY
1. Extract Project ROC
2. Run Remix OS Installation Tool
3. Select Project ROC with the corresponding version number for the ISO
4. Select desired install location: Hard Disk or USB
5. Select target drive and partition
6. Press OK and allow the installer to finish
7. Close the installer and navigate to the installer location (Since I installed to my C: partition, it was located at C:\RemixOS\)
8. Open menu.lst with your favourite text editor (I used Notepad++)
9. Add this: REMOUNT_RW=1 after SRC=RemixOS/
Make sure the red code is added like this:
Example:
Code:
default 0
timeout 10
title Resident mode - All your data and apps are saved
find --set-root /RemixOS/kernel
kernel /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86 androidboot.selinux=permissive quiet SERIAL=random logo.showlogo=1 SRC=RemixOS/[B][COLOR="Red"] REMOUNT_RW=1 [/COLOR][/B]DATA= CREATE_DATA_IMG=1
initrd /RemixOS/initrd.img
boot
10. Save and reboot to Project ROC
11. All versions from .205 will have the Xposed Framework files included, but must be manually installed to be able to use. If you want to install and use Xposed Framework then follow these steps!
Boot Remix OS with Debugging
To do this add the flag: "DEBUG=1" just like earlier with the "REMOUNT_RW=1" flag! (You can remove it once you have installed Xposed!)
When it asks you to type exit do not type exit, instead follow this: 1. "su" (allow su permission 2. "cd /system/xposed" 3. "sh flash-script.sh" 4. "exit" 5. "exit"
e.g.
>su
>cd /system/xposed
>sh flash-script.sh
>exit
>exit
12. Update all apps via Google Play Store
UEFI
Thanks to @Vioner for letting me use his instructions!
Now you need to make the change persistent:
For Remix OS installed on hard drive:
LEGACY BOOT:Apply adequate changes to grub.cfg or menu.lst file in your Remix OS installation folder. Editing both files won't hurt
UEFI BOOT: Apply adequate changes to EFI:/boot/grub/grub.cfg file in your ESP (EFI System Partition) - example path Z:/boot/grub/grub.cfg
Instruction on how to access grub.cfg file on Windows
BEWARE, ACCIDENTALLY REMOVING OR MODIFYING SOME FILES FROM ESP PARTITION WILL RENDER SYSTEMS NOT BOOTABLE - WILL REQUIRE RECOVERY TOOLS.
To access ESP, you need to:
start cmd.exe as administrator
Kill Explorer -> Mount the ESP -> Start the Explorer as admin using below commands:
Code:
taskkill /f /im explorer.exe
mountvol Z: /s
explorer.exe
If you fail to mount the system partition then it's probably already mounted. Start notepad as administrator then browse My computer and you should find a SYSTEM drive - that's ESP.
Edit & save the EFI:/boot/grub/grub.cfg file
Reboot and test if the changes worked(if you reboot into Windows, the ESP should be inaccessible again - it automatically unmounts upon restart)
For Remix OS installed on a USB stick:
You will need to access USB partition labeled REMIXOSSYS.
Filesystem of this partition is not supported by Windows, so without any 3rd party apps you won't be able to modify the needed files.
You will need to either use a Linux distribution or edit from Remix OS on other device. Be dexterous
LEGACY BOOT:Apply adequate changes to REMIXOSSYS:/SYSLINUX.CFG
UEFI BOOT: Apply adequate changes to REMIXOSSYS:/boot/grub/grub.cfg
Add a post with your results after using the guide and hit Thanks it it worked for you List your device brand and model & GPUs models + Remix OS version
Downloads:
Google Drive
32-bit: V3.0.207
V3.0.207 (XPOSED INCLUDED BUT MUST BE INSTALLED USING STEP 11) https://drive.google.com/open?id=0B-mpriMWe2WUX1RkaWhGTXFxQlU
V3.0.207 GAPPS (XPOSED INCLUDED BUT MUST BE INSTALLED USING STEP 11) https://drive.google.com/open?id=0B-mpriMWe2WUZm04R2o2U3lIR00
64-bit: V3.0.207
V3.0.207 (XPOSED NOT INCLUDED, IT CAUSED BOOT PROBLEMS https://drive.google.com/open?id=0B-mpriMWe2WUUWtVVW5hLXdYUkk
V3.0.207 GAPPS (XPOSED NOT INCLUDED, IT CAUSED BOOT PROBLEMS) https://drive.google.com/open?id=0B-mpriMWe2WUaFVUS0JBVGZGN3M
32-bit: V3.0.206
V3.0.206 (XPOSED INCLUDED BUT MUST BE INSTALLED USING STEP 11)https://drive.google.com/open?id=0B-mpriMWe2WUclVMWUZnZ1dIY0E
V3.0.206 GAPPS (XPOSED INCLUDED BUT MUST BE INSTALLED USING STEP 11) https://drive.google.com/open?id=0B-mpriMWe2WUNk5ZWDUxTU9ralE
64-bit: V3.0.206
V3.0.206 (XPOSED INCLUDED BUT MUST BE INSTALLED USING STEP 11) https://drive.google.com/open?id=0B-mpriMWe2WUUTl1ZDlRN3BZLWs
V3.0.206 GAPPS (XPOSED INCLUDED BUT MUST BE INSTALLED USING STEP 11) https://drive.google.com/open?id=0B-mpriMWe2WUR2JiVmZKelRKdU0
Credits:
Jide for providing us with an awesome OS
@rovo89 for Xposed Framework
@Chainfire for SuperSU
@Stericson for Busybox
@mrRobinson for Adaway
@HypoTurtle You are the real MVP, you quite literally made this possible, from creating modified files, to helping my stubborn brain understanding what to do!
@[email protected] You are just awesome bro, Giving me all the information I need!
@PizzaG for linking me to the the right places! You saved me so much time!
Android (Google) for Android
CyanogenMod Team for the apps
Donations
ORIOL BLADE RADUA - Thanks for the first donation; It means a lot to me!
I spend countless nights developing roms, awesome mods, and scripts, if you wish to support my work and future developments you can donate to me via the link here!
....is there any chance for a 64bit system support?
<<<New World Order (NWO)>>>
[email protected] said:
....is there any chance for a 64bit system support?
<<<New World Order (NWO)>>>
Click to expand...
Click to collapse
Yes there is, it will probably be done by tomorrow!
moman2000 said:
Yes there is, it will probably be done by tomorrow!
Click to expand...
Click to collapse
Any news on 64 version?
Ota2501 said:
Any news on 64 version?
Click to expand...
Click to collapse
It is done! Uploading now!
moman2000 said:
It is done! Uploading now!
Click to expand...
Click to collapse
...great news!
<<<New World Order (NWO)>>>
[email protected] said:
...great news!
<<<New World Order (NWO)>>>
Click to expand...
Click to collapse
MEGA is being slow right now, so instead, I will upload to Google Drive first then MEGA later!
ETA 4 MINS
V3.0.203 x64 is out now!
moman2000 said:
V3.0.203 x64 is out now!
Click to expand...
Click to collapse
And off course, thank you very much, sire.
Ota2501 said:
And off course, thank you very much, sire.
Click to expand...
Click to collapse
My pleasure!
moman2000 said:
My pleasure!
Click to expand...
Click to collapse
Did all the things in instructions. Installed it on NTFS hard disk partition. It shows unknown file system and grub rescue mode.
pra27 said:
Did all the things in instructions. Installed it on NTFS hard disk partition. It shows unknown file system and grub rescue mode.
Click to expand...
Click to collapse
Can you get into Windows, or this error happening when you boot Remix OS? This seems to be related to the menu.lst file, did you edit it like shown in the picture?
moman2000 said:
Can you get into Windows, or this error happening when you boot Remix OS? This seems to be related to the menu.lst file, did you edit it like shown in the picture?
Click to expand...
Click to collapse
Yes I can boot into Windows. This error only appears whenever I install remix os and I just copy pasted and saved carefully all what you have posted in first post.
And that is same as the picture I think.
pra27 said:
Yes I can boot into Windows. This error only appears whenever I install remix os and I just copy pasted and saved carefully all what you have posted in first post.
And that is same as the picture I think.
Click to expand...
Click to collapse
Go to the remixOS folder and open the uninstaller, then reinstall it, open the menu.lst file and just add this: REMOUNT_RW=1 after SRC=RemixOS/
eg
default 0
timeout 10
title Resident mode - All your data and apps are saved
find --set-root /RemixOS/kernel
kernel /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86 androidboot.selinux=permissive quiet SERIAL=random logo.showlogo=1 SRC=RemixOS/ REMOUNT_RW=1 DATA= CREATE_DATA_IMG=1
initrd /RemixOS/initrd.img
boot
Is this version working in Ubuntu?
SM-N920C cihazımdan Tapatalk kullanılarak gönderildi
matomik said:
Is this version working in Ubuntu?
SM-N920C cihazımdan Tapatalk kullanılarak gönderildi
Click to expand...
Click to collapse
Yes it will work, just use grub-customizer to add an entry for remix os!
But I have realised that it wont work instantly, you will need to use windows, install it (follow the instructions),and then boot it (not from ubuntu's grub but windows), let it boot up then restart and boot from grub! If you have skype I could tell you how to do it easily! Just PM me!
you can fix playback 1080p problem
pra27 said:
Did all the things in instructions. Installed it on NTFS hard disk partition. It shows unknown file system and grub rescue mode.
Click to expand...
Click to collapse
Your problem is with the grub; not sure which grub @moman2000 added but if it's the one jide included then hopefully the ntfs grub module was also included and it just needs to be insmod'ed in grub.cfg/menu.lst
For me 64bit version don't start. Bootloop on remixos. With official version no problem.
framir said:
For me 64bit version don't start. Bootloop on remixos. With official version no problem.
Click to expand...
Click to collapse
I suspect it is Xposed not being comaptible with x64, I will need to ask @rovo89 where the files go for x64!
{
"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"
}
I present to you: Kali NetHunter for the Huawei Nexus 6P LOS17.1
Kali NetHunter is an Android ROM overlay that turns an ordinary phone into the ultimate Mobile Penetration Testing Platform.
The overlay includes a custom kernel, a Kali Linux chroot, an accompanying Android application, which allows for easier interaction with various security tools and attacks, as well as a client to the Kali NetHunter App Store.
Beyond the penetration testing tools arsenal within Kali Linux and the Kali NetHunter App Store, NetHunter also supports several additional classes, such as HID Keyboard Attacks, BadUSB attacks, Evil AP MANA attacks, and much more. For more information about the moving parts that make up NetHunter, check out our NetHunter Components page.
NetHunter is an open-source project developed by Offensive Security and the community.
~ Prerequisites ~
- TWRP - https://drive.google.com/open?id=1axm3GVbTKypUdQAuYubNknJX4wKRFIec
- Stock components - vendor, radio, & bootloader img's from the stock oreo 8.1 OPM7.181205.001 Dec 2018 factory image - https://androidfilehost.com/?w=files&flid=286833
- Magisk – https://forum.xda-developers.com/apps/magisk
~~ Downloads ~~
- NetHunter installer (find the latest release for Nexus 6P): https://www.kali.org/get-kali/#kali-mobile
- fstab with disabled forceencrpyt - https://www.androidfilehost.com/?fid=4349826312261764572
- vendor image with patched fw for nexmon - https://www.androidfilehost.com/?fid=8889791610682949885
EDIT: Use the following if there's no mirror on the link above: https://github.com/yesimxev/nethunter_files/raw/main/angler/vendor.squashfs.zip
- nexmon zip with nexutil and libs - https://www.androidfilehost.com/?fid=8889791610682951480
- Bootanimation TWRP flasher - https://www.androidfilehost.com/?fid=10763459528675571003
~~ How to Install ~~
- Assuming you have flashed stock radio, vendor, bootloader, TWRP, and Lineage 17.1 (using the steps from https://forum.xda-developers.com/ne...t/rom-lineageos-17-0-nexus-6p-angler-t4012099)
- Plug in to PC if you haven't done that yet
- Reboot into TWRP
- Format data
- Copy Magisk, NetHunter image, and fstab to USB-C drive or adb push to /sdcard
- Reboot into bootloader and flash vendor which was unzipped from zip
Code:
fastboot flash vendor vendor.squashfs
- Reboot into TWRP
- Copy fstab to /system_root/
Code:
adb push fstab.angler /sdcard/
adb shell "twrp mount /system_root && twrp remountrw /system_root && cp /sdcard/fstab.angler /system_root/"
- Format data
- Reboot to system & do Android setup
- Reboot into TWRP
- Install Nexmon files through adb, from the zip above
Code:
twrp mount /system_root && twrp remountrw /system_root && cp /sdcard/libnexmonkali.so /system_root/system/lib64/kalilibnexmon.so && cp /sdcard/libnexmon.so /system_root/system/lib64/ && cp /sdcard/nexutil /system_root/system/xbin/ && chmod a+x /system_root/system/xbin/nexutil
- Flash NetHunter image
- Flash Magisk
- Reboot
- Run NetHunter app, update from NH Store
- Reboot
~~~ Notes & Updates ~~~
Nexmon is finally working with injection in Kali Chroot , although EAPOL data is still not (or malformed) in the captures.
- copy Nexmon libs over to /system/lib64/ from the nexmon.zip (not in TWRP):
Code:
adb push libnexmon* /sdcard/ && adb push nexutil /sdcard/
- and copy using androidsu terminal:
Code:
mount -o rw,remount / && cp /sdcard/libnexmonkali.so /system/lib64/kalilibnexmon.so && cp /sdcard/libnexmon.so /system/lib64/ && cp /sdcard/nexutil /system/xbin/ && chmod a+x /system/xbin/nexutil
For devices which have no space left on system: you need to copy those files before flashing NetHunter. I didn't have this problem, maybe due to GApps pico. Then use the following commands in TWRP:
Code:
twrp mount /system_root && twrp remountrw /system_root && cp /sdcard/libnexmonkali.so /system_root/system/lib64/kalilibnexmon.so && cp /sdcard/libnexmon.so /system_root/system/lib64/ && cp /sdcard/nexutil /system_root/system/xbin/ && chmod a+x /system_root/system/xbin/nexutil
Thanks @JaK3sT for discovering this!
You have to make sure that wifi is on but you're not connected to an AP.
Enable in AndroidSU terminal, I created a custom command with
Code:
nexutil -m2
Export LD_PRELOAD for faking ioctl in every Kali Chroot terminal window you open
Code:
export LD_PRELOAD=/system/lib64/kalilibnexmon.so
Hijacker is not fully supported as I've built one with aarch64 tools, but it randomly stops airodump although it's working. Will give it a shot in the future.
- Mana is being replaced, for the time being you can downgrade iptables in chroot with the following :
Code:
wget http://old.kali.org/kali/pool/main/i/iptables/iptables_1.6.2-1.1_arm64.deb
wget http://old.kali.org/kali/pool/main/i/iptables/libip4tc0_1.6.2-1.1_arm64.deb
wget http://old.kali.org/kali/pool/main/i/iptables/libip6tc0_1.6.2-1.1_arm64.deb
wget http://old.kali.org/kali/pool/main/i/iptables/libiptc0_1.6.2-1.1_arm64.deb
wget http://old.kali.org/kali/pool/main/i/iptables/libxtables12_1.6.2-1.1_arm64.deb
dpkg -i *.deb
apt-mark hold iptables
apt-mark hold libip4tc0
apt-mark hold libip6tc0
apt-mark hold libiptc0
apt-mark hold libxtables12
Credits: The Offensive Security Team and the NetHunter community, huge thanks to Re4son & kimocoder for patching the wlan1 insert reboot issue! Long time mystery.
Another extremely big thanks for @draco42 for patching libnexmon and kalilibnexmon!
Android Version: 10.0
XDA: DevDB Information
Kali Nethunter, Kernel & ROM for the Huawei Nexus 6P
Contributors
@Re4son, @kimocoder, @yesimxev, @draco42
Source Code: https://gitlab.com/kalilinux/nethunter/
Kernel Source: https://github.com/Re4son/android_kernel_huawei_angler
**RESERVED**
Omg ...?????
**RESERVED**
Thank you!
Before your post went up, I had been trying for DAYS to install Nethunter on PE10.
Everytime I lost root (Magisk) on reboot and the Nethunter app never showed up.
I KNEW I was missing some important steps (which were not documented).
Now that official instructions are available I'm going to try and install it the proper way.
@Re4son @kimocoder
@yesimxev
Wow, you guys are on fire.
Congratulations to this great updates and foremost the long outstanding release for the Angler!
Which under Oreo flawlessly works now.
No nasty reboots while attempting to set your nic into monitor mode for sure. :good:
Kimocoder did an amazing job with the port of the new driver.
I could basically use every adapter. Especially the ac ones.
You accidentally mixed up some of the links.
This is the Angler (Huawei Nexus 6P) sub-forum and you posted a link for the installer to the Shamu (Motorola Nexus 6).
Also did I try to look over the source and compiled it for myself, but after everything was set up, my kernel and chroot & everything else, the usb adapter plug in/out bug occurred again.
Re4son worked on flair's source 16days ago.
Where can I find the one you used in the new release?
Here is the link to the correct one - >
https://build.nethunter.com/contrib...er-2020.2-pre3-angler-los-ten-kalifs-full.zip
For the user who aren't comfortable to use Android ten for other reasons, here the recommended stable release for Android Oreo stock - >
https://build.nethunter.com/contrib...unter-2020.2-pre3-angler-oreo-kalifs-full.zip
I had no time the last week(s), but I did see a couple of issues who need to be addressed.
One of the main problems with the new Oreo kernel neither Nexmon or the new QUALCOMM patch from kimocoder and Co. are working.
I will come back to this when I have the time..
Firstly great work to the entire team and big thanks for this great contribution
wow:laugh:awosome!
Could you explain to less experienced user how someone are going to be modify the last twrp version for the Angler wit fstab accordingly?
Thanks for mentioning the link, replaced with the correct one. To do fstab:
Copy fstab to eg. Internal storage
Boot into TWRP
In terminal, type
Code:
mount -o rw,remount /vendor
cp /sdcard/fstab.angler /vendor/etc/
yesimxev said:
Thanks for mentioning the link, replaced with the correct one. To do fstab:
Copy fstab to eg. Internal storage
Boot into TWRP
In terminal, type
Click to expand...
Click to collapse
Thanks a bunch, @yesimxev!
As you saw in both threads for LOS 17 and PE, do they come with specific TWRP versions.*
Are they some what of relevant, or is the official release by twrp.me sufficient?
*LOS 17.1
https://forum.xda-developers.com/showpost.php?p=81059545&postcount=3
*Pixel Experience 10.0
https://forum.xda-developers.com/showpost.php?p=80290619&postcount=3
Thanks for this it works perfect but my Question is how to survive a System update?
For example a new Version of los 17 Comes out, i Flash it, so the nethunter kernel is gone.
When i Flash the whole nethunter Image then all works fine but the chroot Environment will be wiped and replaced with the one from the Image. Thats not so good because all of the Manual Things are wiped also, like compiled Software and post updated and installed Software.
So whats the best way to Keep the chroot Environment after an Android System update?
Create a backup of your rootfs via the Chroot Manager is probably the best option. You could just reflash the kernel too
Thanks for your fast reply.
How to Flash the kernel only? I looked into the Archive but there are too many scripts for all the Little nice Things during the installation and there isnt a single zip file for the kernel or i missed something. Sorry i m not that great developer…
I thought i could comment out the chroot extraction in the installer script, its the last step. Is this a possibility?
---------- Post added at 11:50 AM ---------- Previous post was at 11:46 AM ----------
And the possibility to backup the chroot in the chroot Manager i never saw, thats great and probably the best Option yes. Thanks for that hint!
yesimxev said:
Thanks for mentioning the link, replaced with the correct one. To do fstab:
Copy fstab to eg. Internal storage
Boot into TWRP
In terminal, type
Code:
mount -o rw,remount /vendor
cp /sdcard/fstab.angler /vendor/etc/
Click to expand...
Click to collapse
When I tried copy fstab.anger from my /usb_otg to /vendor/etc/ via file manager in TWRP, a received error ERROR status code 1.
So I tried mount command, which is mentioned above, via terminal in TWRP. /vendor was mounted succesfully but when I used cp command a received error again, that target is in read-only filesystem. And yes I definitely mount it with "-o rw" (read write).
What can I do wrong?
SalyczeQ said:
When I tried copy fstab.anger from my /usb_otg to /vendor/etc/ via file manager in TWRP, a received error ERROR status code 1.
So I tried mount command, which is mentioned above, via terminal in TWRP. /vendor was mounted succesfully but when I used cp command a received error again, that target is in read-only filesystem. And yes I definitely mount it with "-o rw" (read write).
What can I do wrong?
Click to expand...
Click to collapse
Forgot to mention that vendor has to be mounted first. Use
Code:
mount /vendor
Nick_Speed said:
How to Flash the kernel only? I looked into the Archive but there are too many scripts for all the Little nice Things during the installation and there isnt a single zip file for the kernel or i missed something. Sorry i m not that great developer…
Click to expand...
Click to collapse
Probably because they were just released and for now as complete installer by Offensive being offered. ;/
I build both of the newly released kernel for LOS 17.1 and 8.1 Stock Oreo with the python installer.
Ten
https://mega.nz/file/hUBHxSyT#HJRVnp_uH1hosPfsDClSiG9hzO54eQkM24ONG48b3Fc
Oreo
https://mega.nz/file/AVZxFIDC#SQG_X6yfmwb3cjmO8bzYqo5RhTJ7hjmWEOrk-c97f2o
Best regards
---------- Post added at 09:47 PM ---------- Previous post was at 09:43 PM ----------
SalyczeQ said:
Thanks for mentioning the link, replaced with the correct one. To do fstab:
Copy fstab to eg. Internal storage
Boot into TWRP
In terminal, type
When I tried copy fstab.anger from my /usb_otg to /vendor/etc/ via file manager in TWRP, a received error ERROR status code 1.
So I tried mount command, which is mentioned above, via terminal in TWRP. /vendor was mounted succesfully but when I used cp command a received error again, that target is in read-only filesystem. And yes I definitely mount it with "-o rw" (read write).
What can I do wrong?
Click to expand...
Click to collapse
Did you use the official version, or the ones supported by the the according rom developer?
yesimxev said:
Forgot to mention that vendor has to be mounted first. Use
Code:
mount /vendor
Click to expand...
Click to collapse
View attachment 4996285
as you can see I tried, but the same error still occurs
UsPdSr said:
---------- Post added at 09:47 PM ---------- Previous post was at 09:43 PM ----------
[/COLOR]
Did you use the official version or the ones supported by the according to rom developer?
Click to expand...
Click to collapse
I used TWRP provided beside according rom, not the official version. View attachment 4996289
But If you will check the screenshot which I attached, I notice something weird, that in mount TWRP page I see vendor partition twice. Can It be a problem?
Is there any big difference between TWRP provided for LOS17.1 and PE10? Because the last thing I can think of is that I may swap it and use PE10 TWRP for install LOS17.1 rom.
SalyczeQ said:
I used TWRP provided beside according rom, not the official version.
But If you will check the screenshot which I attached, I notice something weird, that in mount TWRP page I see vendor partition twice. Can It be a problem?
Is there any big difference between TWRP provided for LOS17.1 and PE10? Because the last thing I can think of is that I may swap it and use PE10 TWRP for install LOS17.1 rom.
Click to expand...
Click to collapse
I tried the installation with LOS.
I had countless error messages primarily because of the vendor, too.
I have seen this weird entry before, after another user botched his installation as well.
I would definitely erase the recovery with fastboot, or try to flash the official one over.
Since the Nexus 6p received support for Pie am I very sceptical of the usage as daily driver.
I have no desire to flash these funny FBEwhatever recoveries and and see my device commit suicide. - _-
So.
I am definitely going to try it again, especially Pixel Experience is interesting, but I would like to ask the Nethunter team ( @yesimxev, @Re4son), if it would be possible to write a more detailed instructions on how to get this work, or perhaps assemble something to flash without modification by the user..
Many heaps
UsPdSr said:
I tried the installation with LOS.
I had countless error messages primarily because of the vendor, too.
I have seen this weird entry before, after another user botched his installation as well.
I would definitely erase the recovery with fastboot, or try to flash the official one over.
Since the Nexus 6p received support for Pie am I very sceptical of the usage as daily driver.
I have no desire to flash these funny FBEwhatever recoveries amd and see me device commit suicide.
So.
I am definitely going to try it again, especially Pixel Experience is interesting, but I would like to ask the Nethunter team ( @yesimxev, @Re4son), if it would be possible to write a more detailed instructions on how to get this work, or perhaps assemble something to flash without modification by the user..
Many heaps
Click to expand...
Click to collapse
Hey there,
So for ten i installed ExtendedUI OFFICIAL and PixelDust with the twrp fbe 10, reboot to recovery, rooted with magisk, set all up, install busybox within magisk, reboot to recovery, then installed the nethunter zip, rebooted to recovery,
rooted with magisk, reboot to System.
All is fine, the kernel etc. but no nethunter apps are showing. So i extracted the apps from the zip file, installed all and updated the nethunter app throught fdroid because the nethunter store app isnt working with extensions but fdroid did and the source for the nethunter repo you can copy from the store app.
Then fire up the nethunter up, set up chroot and tata, all is working great.
and btw thanks for the flashable kernel ;o)
Android 13 ( QPR 1,2,3)
{
"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"
}
☆ In QPR2 A13 GSI, you can't uses "Google Assistant make a call from your contact list."
> It's works only in QPR1 such as " Elixir 3.6" " SparkOS 13.5.5" " lineage-20.0-20230218" etc.,
□○●○●○●○●○●□
¤ Build Custom kernel (KernelSU) with a Linux subsystem within Windows 10 By yourself is the best way if you are interested in new root management.
Why?
On Android 10+, system partitions might no longer be able to remount as read-write. For devices use dynnamic partition, it is nearly impossible to modify system partiton as there is no space left.
Click to expand...
Click to collapse
Why Read Only? Can't make R/W (vndk lite).Almost GSIs builds are RO now. Because R/W are so big not suitable for... (Most devices have small system partition which might even be less than 3GB.)
Howto install "KernelSu (0.5.7) A13 for SM-T225 (kernel source T225XXS3CWC2)" ?
Thank to kernel-patched from DEV "zillion".
This method does not require you to have TWRP, nor does it require your phone to have root privileges; it is suitable for your first installation of KernelSU.
Click to expand...
Click to collapse
1. Download: 3in1-KernelSu_0.5.7-FastbootD_A13_CWA2.tar (Attachment)
( my mod for works with Odin + FM T225XXU1CWA2 )
2. Download: KernelSU Manager. https://github.com/tiann/KernelSU/releases/download/v0.5.7/KernelSU_v0.5.7_10866-release.apk
3. CLEAN install with Stock Firmware, + 3in1_kernelsu_fastbootD with Odin.
》 AP Slot: AP_xxx.tar.md5
》 BL Slot: BL_xxx..tar.md5
》 CP slot: CP_xxx.tar.md5
》 CSC slot: CSC_<not home>_xxx.tar.md5
* USERDATA slot: 3in1-KernelSu_0.5.7-FastbootD_A13_CWA2.tar
*( All slot are required , don't omit except USERDATA slot.)
4. Reboot.
5. Connect internet & Enable USB Debugging.
6. Now you can use "Fastboot Mode" to install any GSI.
Code:
adb devices
adb reboot fastboot
fastboot erase system
fastboot flash system ProjectElixir_3.6_gsi-13.0-20230223-1108-OFFICIAL.img
-------> If founded "No spaces to resize partition error"
fastboot erase product
fastboot resize-logical-partition product 0x0
fastboot getvar all
-----> (bootloader) partition-size:product:0x0
#At FastbootD Menu select
-Enter Recovery
#At Recovery Menu select
-Wipe data/Factory reset
confirm
-Reboot system now
7. install " KernelSU Manager APK"
8. Download: magic_overlayfs module. https://github.com/HuskyDG/magic_overlayfs/releases
Flash with kernelSU manager.
Setup & Configure
》install root file manager (Mixplore).
- give root (superuser) permission to your root file manager in KernelSU Manager.
》Open and edit " /data/adb/modules/magisk_overlayfs/mode.sh"
Change "export OVERLAY_MODE=1"
" export DO_UNMOUNT_KSU=true "
reboot
Opem termux or any terminal
Code:
su -mm -c magic_remount_rw
Look at the line "remounted [/system] (overlay)
》If you see, this means "/system partition mounted as RW."
Now Super partition member were Read / Write.
"remounted [/system] (overlay)
"remounted [/odm] (overlay)
"remounted [/vendor] (overlay)
------------edit any things you want---------
When finished all editing system files.
Return Read only to super partition with below set of command.
Code:
su -mm -c magic_remount_ro
DOC: https://github.com/HuskyDG/magic_overlayfs
-How2 extract boot.img
Code:
adb shell
su
dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.img
□○●○●○●○●○●□
Touch working ?
May be I can build custom based stock rom
Difficul said:
May be I can build custom based stock rom
Click to expand...
Click to collapse
Make kernelSU for 225 A13 better. ()SM-T225_CIS_13_Opensource.zip)
tom.android said:
Make kernelSU for 225 A13 better. ()SM-T225_CIS_13_Opensource.zip)
Click to expand...
Click to collapse
Ok , how to make and may be i reinstall linux ?
May be i am research later
Definitely correct about the 3in1 - not a chance! And also definitely do not use the decryption files! And, true, the stock or any other pre-existing recovery will not go away! Unfortunately, if you are using a simple magisk patched rom, it won't do the backup because it does not seem to ever recognize the data. The Fastboot works but, for the moment, it is as easy to use a FastbootD patched recovery. Finally, I was only able to reboot to system just once after flashing the twrp. I think that might have been because I did not try to decrypt after the initial flash. Been at this for 4 days. It's given me a new appreciation for how difficult this is! As a non developer (I am a lawyer), I got used to the TWRP process taking no more than 20 minutes!
It's exhausting. And I was going through this process (not root, I need that), to be more able to make the device do what it is advertised to do: make calls. I might give up on that!
EBRJR said:
It's exhausting. And I was going through this process (not root, I need that), to be more able to make the device do what it is advertised to do: make calls. I might give up on that!
Click to expand...
Click to collapse
uses gsi A13(QPR-1) such as elixer 3.6 etc. Assistant can make a call from your contact.
You were never supposed to post this, considering the github source code wasn't updated according to this twrp image.
edit: Thanks for removing the twrp image from your post, I'll be updating twrp when things get more stable.
3in1 kernelSU + FastbootD_A13_CWA2 for Odin. ( SM-T225)
https://forum.xda-developers.com/attachments/3in1_kernelsu_10866_a13_cwa2-tar.5925489/
Make "YAAP 20230604 unofficial GSI " R/W super partition with KernelSU".
YAAP is a project founded by Adhitya Mohan (@poad42) and Ido Ben-Hur (@idoybh) with the goal of staying close to AOSP in design goals, offer a clean interface, do as much as original development as possible and avoid becoming a kitchen sink and cherry picked mess.
Whats New?
Synced with latest sources of YAAP.
Synced with latest Trebledroid patches.
All builds are RO now (sorry every build so huge now that i had to. Otherwise it wouldnt fit in anyone's devices)
Example ( Features)
Update kernelsu v.0.6.0
Download: new attachment.
Is working for one ui ?
Difficul said:
Is working for one ui ?
Click to expand...
Click to collapse
Kernelsu is supported for one ui, but one ui no need to use overlayfs module cause super partition of one ui are rw.
Update OverlayFS v3.1.2
Releases · HuskyDG/magic_overlayfs
Make system partition become read-write (it is also possible without Magisk) - HuskyDG/magic_overlayfs
github.com
Install with kernelsu manager without uninstall old one.