I've uploaded a new version (v1.2) of the modified RC30 update.
http://rapidshare.com/files/165227766/update_TC4-RC30_full_xda-dev_v1.2.zip
http://android-dls.com/forum/index.php?f=24&t=189&rb_v=viewtopic(see forum post for link to actual file)
You must have the modified recovery image installed before trying to install this.
Install as per usual - copy to sd card, rename to update.zip, reboot, enter recovery mode and hit alt+s.
(here's a guide on how to install in Italian - thanks Deedend!)
The primary new features in this version are
- adb shell now works in recovery mode
- a real su (instead of the setuid copy of sh in the last version)
- lots of new goodies in /system/xbin and /system/modules
Other things that have changed from v1.1
- This version has a kernel compiled by Saurik, with more core stuff "turned on", to support more modules (Specifically, /dev/mem and /dev/kmem are available now)
- new features in init
- support for mounting to loop devices
- move flag for mount
- mknod that can wait for a device
- chdir, chroot, usleep, include, trigger- Changed the init.rc so that it will include /system/init.rc and /data/init.rc, so you can easily add new startup stuff, without having to rebuild/reflash boot.img
- Changed the boot-up recovery flash to look for a file at /data/recovery.img instead of /system/recovery.img, and also to delete recovery.img after a successful flash
- changed the "mount" symlink to be busybox's mount instead of toolbox's mount
- added an /etc/fstab file that busybox's mount can use, that lists the standard system partitions.
- changed the fingerprint back to the official RC30 fingerprint (don't want to let google know you're using a modified build)
- using a newer version of busybox
- moved busybox from /system/bin to /system/xbin
Note: A big thanks to Saurik (the "debian on Android" guy ) for all the changes to init and the kernel, as well as the modules in /system/modules. He also tweaked and recompiled a newer version of busybox. He recently posted his own update that I shamelessly stole this stuff from (with his permission )
It also includes the changes that were made in v1.0 and v1.1. namely
- set ro.secure=0, ro.debugable=1, and persist.service.adb.enable=1 in /default.prop, to enable adb to run as root
- Added the ability to mount to a loop in init
- Mount /system/xbin/xbin.cramfs into /system/xbin in init.rc
- Looks for a recovery image to flash at /data/recovery.img instead of /system/recovery.img, and deletes the recovery image after a successful flash
- added back in the telnetd command from RC29
-----
For those who have installed the stock RC30 update: no, you cannot install this update. You must have a modified recovery image installed to apply the update, and you have to have root access to install a modified recovery image. You can't get root access in stock RC30, so you can't install a modified recovery image, and so you can't install this update.
-----
im gonna try this on my stock rc28... let u know tha good tha bad n tha ugly
JesusFreke said:
.... You should be able to apply it no matter what RC you are on.....
Click to expand...
Click to collapse
My G1 is at RC30, would I be able to update it via SD card again to gain the root access?
-Pramod
pramods said:
My G1 is at RC30, would I be able to update it via SD card again to gain the root access?
-Pramod
Click to expand...
Click to collapse
No. If you're running stock RC30, and don't have my recovery image installed, you're out of luck, until another root exploit is found.
Does this include all the regular upgrades that the rc30 was going to bring like the battery fix ? And So i dont mess up how do i install the modified recovery image correctly ?
What mod we have to install it? since is not signed with google key it will not load on 29 at all.
usmc2k said:
Does this include all the regular upgrades that the rc30 was going to bring like the battery fix ?
Click to expand...
Click to collapse
Yes. It is identical to the stock RC30, except for the specific modifications I mentioned.
tritron777 said:
What mod we have to install it? since is not signed with google key it will not load on 29 at all.
Click to expand...
Click to collapse
You have to have the modified recovery tool on your phone, which has the test keys.
Thank YOU SO MUCH! i was afraid i wasn't going to see you. i try ed someone else's(mod) and I stuck in your recovery because i tryed to format partion md3(system) and restore it with the backup(for some reason i was stuck between RC29-30) the phone froze but i tell you your recovery is the S*** it Saved my A** Where's your donation account?(4real)
Do I still have to install the modified recovery image or is it included in ur version ?
usmc2k said:
Do I still have to install the modified recovery image or is it included in ur version ?
Click to expand...
Click to collapse
You have to have the modified recovery image already installed in order to install my modified update. And it will still be installed after you do the update.
JesusFreke said:
You have to have the modified recovery image already installed in order to install my modified update. And it will still be installed after you do the update.
Click to expand...
Click to collapse
So all i do is get the zip from ur post change it to a update... install it then change ur rc30 to update install it and im good to go ????
Thanks so much! It worked perfectly
humble said:
Thank YOU SO MUCH! i was afraid i wasn't going to see you. i try ed someone else's(mod) and I stuck in your recovery because i tryed to format partion md3(system) and restore it with the backup(for some reason i was stuck between RC29-30) the phone froze but i tell you your recovery is the S*** it Saved my A** Where's your donation account?(4real)
Click to expand...
Click to collapse
Glad I could be of service . If you want to donate, I would be happily surprised, and much appreciative.
usmc2k said:
So all i do is get the zip from ur post change it to a update... install it then change ur rc30 to update install it and im good to go ????
Click to expand...
Click to collapse
Yep . Assuming you have the modified recovery image installed already. If you don't, it will just say something to the effect that it couldn't validate the signature.
JesusFreke said:
Glad I could be of service . If you want to donate, I would by happily surprised, and much appreciative.
Click to expand...
Click to collapse
enjoy my friend, and your welcome
looks like telnetd command didn't survive
jriley60 said:
looks like telnetd command didn't survive
Click to expand...
Click to collapse
Why do you say that?
Code:
# ls /system/bin/t*
ls /system/bin/t*
/system/bin/telnetd
/system/bin/toolbox
/system/bin/top
weird i can't terminal in from the phone anymore.
jriley60 said:
weird i can't terminal in from the phone anymore.
Click to expand...
Click to collapse
You can't run telnetd just by typing it in on the keyboard anymore. You have to open a terminal (terminal emulator, pterminal, or with adb shell), and get root access if needed (su), and then type "telnetd &" (the & at the end tells it to run in the background)
Related
Don't forget to thank me and Radii it means a lot to us!
Click to expand...
Click to collapse
Upon discovering the reason people being given an error trying to flash OTAs in my TWRP recovery image I decided I would come up with a work around while I work out a way to fix it.
The following solution is group work between me and Radii.
If you came here just for OTA links then click HERE
Click below spoiler if you haven't installed TWRP on your device and you want to OTA update and then install TWRP.
First you need to download the version you would like, in theory you could backdate although this hasn't been tested and it may misbehave. For example the latest version as of 16/10/2015, build number cm-12.1-YOG4PAS38J.
On the spread sheet you will need two files, the fastboot and the signed. In the fastboot ZIP there is a file called recovery.img. Copy this to your android SDK platform tools folder. Now with the signed ZIP you either copy that to the same folder (platform-tools). Put your phone into fastboot mode and type.
Code:
fastboot -i 0x2b4c boot recovery.img
Or the name of the recovery if you renamed it.
Your phone will boot into Cyanogen OS Recovery. From there click Apply Update (Top option) and click ADB Sideload. Then type,
Code:
adb sideload cm-12.1-YOG4PAS38J-ham-signed.zip
Or whatever you renamed it to.
Reboot and you're done! Now you'll need to install TWRP to flash things like SuperSU and Xposed.
To install TWRP you need to download the latest TWRP image from HERE move that to platform-tools and type (with your phone in fastboot mode/bootloader mode of course)
Code:
fastboot -i 0x2b4c flash recovery "recovery.img"
Changing the name in the quotations to the name of the recovery and removing the quotes.
Click below spoiler if you have installed TWRP on your device and you want to OTA update and restore/preserve TWRP
Do the same as above, I have discovered it's impossible to preserve because Cyanogen will auto-write it's own recovery to the recovery parition.
Nerdy stuff
If you're wondering why you can't OTA without going through all this then it's because Cyanogen OS will do checks to see if the System has been r/w mounted. If so then it will stop all OTAs from installing. Simple when you think about it.
FAQ
Q: Why isn't TWRP still installed after installing the OTA? A: Because Cyanogen OS will write over the recovery partition with Cyanogen Recovery
Q: Will I lose all my data? A: Don't wipe and no, you can dirty flash to preserve data.
Thanks for your work, really appreciated.
However, it sucks a bit that we have tons of work just for the OTA updates if we want root, i guess we should annoy Cyanogen to add a Superuser option to CyanogenOS...
othe01 said:
Thanks for your work, really appreciated.
However, it sucks a bit that we have tons of work just for the OTA updates if we want root, i guess we should annoy Cyanogen to add a Superuser option to CyanogenOS...
Click to expand...
Click to collapse
It's designed to be shipped with devices like Samsung or LG's ROMs they'll never add that option.
Sent from my Z1 using Tapatalk
Breadcrust said:
It's designed to be shipped with devices like Samsung or LG's ROMs they'll never add that option.
Sent from my Z1 using Tapatalk
Click to expand...
Click to collapse
Why not? root is a normal option in CyanogenMod, why wouldn´t the "commercial" edition not support it? I see no reason they can´t add it to PrivacyGuard.
Here one of the forum admins said hes telling the team to add it -> http://community.cyngn.com/t/reques...-thethering-and-inbuilt-superuser-access/97/2
Breadcrust,
did you try this method used for oneplus one phones with CyanogenOS?
https://forums.oneplus.net/threads/flashable-zip-cm12-enable-integrated-superuser.297089/
https://github.com/julian-klode/bacon-superuser/
From what i´ve read OTA updates are working with it and all we need to do is update the recovery after installing a new ota, the script on github creates the patched boot files automatically, we just have to change the config to use the ZUK files.
All theory tho...as i don´t have my phone yet.
othe01 said:
Breadcrust,
did you try this method used for oneplus one phones with CyanogenOS?
https://forums.oneplus.net/threads/flashable-zip-cm12-enable-integrated-superuser.297089/
https://github.com/julian-klode/bacon-superuser/
From what i´ve read OTA updates are working with it and all we need to do is update the recovery after installing a new ota, the script on github creates the patched boot files automatically, we just have to change the config to use the ZUK files.
All theory tho...as i don´t have my phone yet.
Click to expand...
Click to collapse
I'll look into it at sunrise it currently 3:23AM here so can't do it now
P.s thanks for waking me :3
Sent from my Z1 using Tapatalk
@othe01
No COS device allows you to flash incremental OTA if your /system partition is modified. Your quoted package puts compatible su binary in /system & flashes boot-debuggable kernel so that root can be achieved from both app & ADB. It has nothing to do with OTA. Your only choice is to get the signed zip & flash it manually.
@Breadcrust
It would be nice to put incremental OTA zip links too. My posts regarding OTA links also contain them.
:highfive:
Titokhan said:
@othe01
No COS device allows you to flash incremental OTA if your /system partition is modified. Your quoted package puts compatible su binary in /system & flashes boot-debuggable kernel so that root can be achieved from both app & ADB. It has nothing to do with OTA. Your only choice is to get the signed zip & flash it manually.
@Breadcrust
It would be nice to put incremental OTA zip links too. My posts regarding OTA links also contain them.
:highfive:
Click to expand...
Click to collapse
sounded different here: [FLASHABLE ZIP] [CM12] Enable integrated superuser
But is prolly just a misunderstanding from my side.
How exactly does CyanogenOS check if System is modified and can´t we patch the check with an xposed module?
@othe01
He must used the signed zip to update. Regarding OTA faliure, I've discussed the issue here: http://forums.yuplaygod.com/index.php?threads/15124/
You need to registered in the forum to read, so I've uploaded a PDF of the same: https://drive.google.com/file/d/0B9zZIJPXbMsubkFBYmZ4eGtMQjQ/view?usp=sharing
I personally own OnePlus One & YU Yureka so already have a good experience with these things.
The whole procedure is clearly explained - no 'Xposed' module can bypass it. You can, in theory, deploy a file based OTA (I've already requested it through YU developers) instead of block based OTA or patch the update-binary to return always true (unmodified) value while checking the state of partitions.
:good:
@Titokhan I will post them later
Sent from my Z1 using Tapatalk
@Breadcrust can you please help me if you can, I have problem flashing any ota (increments or full), it return error " this package is for device:Z1 this device is k9", all ota was installed directly till unlocked bootloader and root .
aaswar said:
@Breadcrust can you please help me if you can, I have problem flashing any ota (increments or full), it return error " this package is for device:Z1 this device is k9", all ota was installed directly till unlocked bootloader and root .
Click to expand...
Click to collapse
Issue is noted method is in post
Sent from my Z1 using Tapatalk
@Breadcrust
cm-12.1-20150805-EXPERIMENTAL-YOG4PAP1CG-ham: http://forum.xda-developers.com/showpost.php?p=63390843&postcount=223
@Breadcrust
for clarification:
-isn't "cm-12.1-YOG4PAS38J-ham-signed-fastboot.zip" is the same as "cm-12.1-YOG4PAS38J-ham-signed.zip", but with the recovery image include, can sideload this file using the same process you mentioned?
-if the phone is rooted, boot with the COS recovery and sideload the "cm-12.1-YOG4PAS38J-ham-signed.zip" will not work as the system partition is already been modified by the root process, am I right?
aaswar said:
@Breadcrust
for clarification:
-isn't "cm-12.1-YOG4PAS38J-ham-signed-fastboot.zip" is the same as "cm-12.1-YOG4PAS38J-ham-signed.zip", but with the recovery image include, can sideload this file using the same process you mentioned?
-if the phone is rooted, boot with the COS recovery and sideload the "cm-12.1-YOG4PAS38J-ham-signed.zip" will not work as the system partition is already been modified by the root process, am I right?
Click to expand...
Click to collapse
re: above
if using cos recovery and sideload via abd or from file the full signed version , and your have root, it will work, root will be lost though.
fastboot zip has recovery signed doesn't. you need to flash recovery extracted from the fastboot zip and then flash the signed full zip using cos either using abd or sideload file onto system
I flash the rom, but when I insert CDMA SIM into slot one, there is no signal
and there is no option to choose band from the menu.
would you please instruct on how to get CMDA works?
@taitai
As you can see here, it is not an CDMA device.
As regards technical faults as well we're unable to help in most cases as ROMs are from Cyanogen and unedited.
Sent from my Z1 using Tapatalk
I have a chinese version of Z1 and it has CDMA capability
None of them do. They're the exactly the same under the hood.
Sent from my Z1 using Tapatalk
Hello guys!
I make my own ROOT (systemless, thanks for Chainfire) images for Moto X Style with Marshmallow (build MPH24.49-18). Its use "experimental" systemless SuperSU version 2.56 - more info on http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2. No need replace bootloader or recovery. Still need unlocked booloader.
Because TWRP didn't work in this version of bootloader (0xA048), I cooked "su.img" in a Linux box and used "/data/local/tmp" as bridge (accessible by ADB).
WARNING! I am not responsible for any harm on your phone. When you're not sure if you can do it, leave it!
For use, you need
1) unlocked bootloader.
2) if your bootloader not unlocked, make sure you have copy of your data, because this process will erase your device.
3) install ADB and FASTBOOT on your pc using minimal ADB or Android SDK.
4) install ADB drivers from Motorola or Universal ADB.
5) download provided files.
6) download SuperSU ver. 2.56 from http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344.
Steps:
1) extract files in a folder of your choice (su.img, boot.img).
2) extract Superuser.apk from SuperSU-v2.56-20151030013730.zip from common folder.
3) enable USB debugging on Android.
4) connect your device on pc.
5) open a command prompt in a new folder.
6) type "adb push su.img /data/local/tmp" without quotes.
7) type "adb install Superuser.apk" without quotes.
8) now reboot your device into fastboot mode by typing "adb reboot bootloader".
9) type "fastboot flash boot boot.img" without quotes.
10) type "fastboot reboot" without quotes.
And enjoy!
Now you have a rooted MotoX Style Marshmallow. To apply any OTAs, you only need reflash stock boot.
Ivan
Do I still need to unlock the bootloader in order to root this device
ivcarlos said:
2) write "boot.img" with fastboot.
Click to expand...
Click to collapse
What do you mean? Como assim?
Oh I see thanx partner
How can I copy "su.img"?
If no Root I can not copy into data/local/tmp.
Marccelllorzn said:
How can I copy "su.img"?
If no Root I can not copy into data/local/tmp.
Click to expand...
Click to collapse
Restart in bootloader
1) adb push su.img /data/local/tmp
2) fastboot flash boot boot.img
3) Install SuperSu ver 2.56 apk
would this work on xt1575 us? if not why?..... i mean .. why the indian MM would work 4 any variation and this one would not?
zittorb said:
would this work on xt1575 us? if not why?..... i mean .. why the indian MM would work 4 any variation and this one would not?
Click to expand...
Click to collapse
Yes, work with XT1575.
I dont test on another device, only on XT1572.
After 24h, no errors, work like a charm.
With this approuch you dont need to downgrade bootloader.
assuming that we need a "CLEAN", unrooted system for this as advised by @Chainfire in his instructional post regarding this experimental root method!
Instructions
You must absolutely re-flash your stock /system partition, or the separate root instances will interfere with each other. The installer for this experiment will not clean up old root files.
- Flash stock /system
- Flash the attached boot image
- Flash the attached SuperSU ZIP in TWRP
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2
Also you should probably make a point of mentioning that this method is an experiment.
Aside from this, let me take my "high-visibility" jacket off, along with my "safety helmet" and say thank you very much for taking the time to do this for us all @ivcarlos! You are a gentleman!
Is Android pay confirmed working with this root method?
Sent from my XT1575 using Tapatalk
@bb12489
I dnt know because I dnt use this feature.
@Doktaphex
I dnt mentioned this - clean and unrooted system - because after apply OTA on XT1572, custom recovery (TWRP) didn't work anymore. By the way, I assume no root and clean system.
I know this method is "experimental", but it's best at this time, without downgrade bootloader (not safe).
Thanks for comments! I make this work because I need root and I dnt like to make heavy changes on smart...
In this way, I share for everyone.
ivcarlos said:
@bb12489
I dnt know because I dnt use this feature.
@Doktaphex
I dnt mentioned this - clean and unrooted system - because after apply OTA on XT1572, custom recovery (TWRP) didn't work anymore. By the way, I assume no root and clean system.
I know this method is "experimental", but it's best at this time, without downgrade bootloader (not safe).
Thanks for comments! I make this work because I need root and I dnt like to make heavy changes on smart...
In this way, I share for everyone.
Click to expand...
Click to collapse
Could you please give me the link that how you created modified boot.img ? I want to make it work on Indian XT1572
@gulshanstrider
I make boot image based on post of Chainfire (http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344), with applying steps:
1) unpack stock "boot.img";
2) patch sepolicy;
3) edit "init.rc" and "init.environ.rc";
4) edit "file_contexts";
5) repack "boot.img".
Use Chainfire generated images with model.
Without TWRP, I cooked "su.img" in a Linux box, and use "/data/local/tmp" with bridge.
ivcarlos said:
@gulshanstrider
I make boot image based on post of Chainfire (http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344), with applying steps:
1) unpack stock "boot.img";
2) patch sepolicy;
3) edit "init.rc" and "init.environ.rc";
4) edit "file_contexts";
5) repack "boot.img".
Use Chainfire generated images with model.
Without TWRP, I cooked "su.img" in a Linux box, and use "/data/local/tmp" with bridge.
Click to expand...
Click to collapse
wifi not working now please tell me how to revert everything back pleaseeee help !!!!
Shishir Singhal said:
wifi not working now please tell me how to revert everything back pleaseeee help !!!!
Click to expand...
Click to collapse
Your model is XT1575 or XT1572?
Shishir Singhal said:
wifi not working now please tell me how to revert everything back pleaseeee help !!!!
Click to expand...
Click to collapse
@Shishir Singhal
Whats your model and version?
I make this image for my XT1572 (BR, dual) and wifi working.
To revert back you must write back stock boot.img version. On first post I provided stock of XT1572 RETLA 6.0 (my base).
On my device no issues at all.
Not working on my XT1572
Didn't work on my XT1572 with Android 6.0.
Enable root option is disabled in SuperSU with a message saying that system-less root is currently not supported.
ivcarlos said:
@Shishir Singhal
Whats your model and version?
I make this image for my XT1572 (BR, dual) and wifi working.
To revert back you must write back stock boot.img version. On first post I provided stock of XT1572 RETLA 6.0 (my base).
On my device no issues at all.
Click to expand...
Click to collapse
Thank u for quick reply got it working by flashing NON-HLOS.bin now everything is working fine thank u soo much
roberto.marcal said:
Didn't work on my XT1572 with Android 6.0.
Enable root option is disabled in SuperSU with a message saying that system-less root is currently not supported.
Click to expand...
Click to collapse
What version of SuperSU you was installed?
You put "su.img" into "/data/local/tmp"?
If you enter in shell with ADB, ls command show "su" directory in root? Image was monted successfully?
*****Keep in mind that I or XDA or anyone else is not responsible for what happens to your device make sure you have a nandroid backup before proceeding
This is based on my personal experience I'm not a Dev
How to enable systemless root on mediatek !!!!
Step 1:
Get the booting of your phone via readback using spflashtool or dumping the ROM IMG !!
Step 2:
Unpack the boot IMG using mkbootimg or carliv IMG kitchen or Android kitchen !!!
Step 3:
Open the ramdisk folder and open the init.rc using notepad++
Step 4
Goto the line
Code:
export PATH /sbin:/system/bin:/system/xbin:/vendor/bin
**The line may vary but it will look similar !!!
Add the path of your su file at the end
Like I was t to install it at my data partition so
Add
Code:
:/data/bin
At the end of the line and save !!
Then change the permissions of /data/bin to 644 else apps won't be able to read the path due to insuffient permission !!!
Then repack the boot.img
Flash the bootimg via sp flash tool of flashify or any other method
Step 6:
***note use the su binaries of your CPU only
Like I used arm 7 binaries for my device !!
To know your CPU type
Download terminal emulator or use adb shell and type cat /proc/cpuinfo
Now using adb push copy the su file to the /data/bin folder or make a flashable zip to do the same !!
If you can't push via adb try doing it in adb supported recovery !!!
You might need to create the bin folder manually
And don't forget to set the permission to 0755 and reboot !!
Plz let me know if it works !!!
And also let me know if it doesn't !!!!
I can't post the flashable zip because I'm still new !!!
Can you post some more info for this? What mtk chipset is it tested with? What android version? When you repack the kernel image, do you use android headers or mediatek headers?
AlexZap said:
Can you post some more info for this? What mtk chipset is it tested with? What android version? When you repack the kernel image, do you use android headers or mediatek headers?
Click to expand...
Click to collapse
Carliv Image Kitchen will repack the same way it was unpacked so you do not have to worry.
I also want more info for this because I'm not even finding the first link export .....
kirito9 said:
Carliv Image Kitchen will repack the same way it was unpacked so you do not have to worry.
I also want more info for this because I'm not even finding the first link export .....
Click to expand...
Click to collapse
the point is that the systemless installer is supposed to unpack and repack the kernel... and i dont know/dont think it can handle a mediatek header
AlexZap said:
the point is that the systemless installer is supposed to unpack and repack the kernel... and i dont know/dont think it can handle a mediatek header
Click to expand...
Click to collapse
Ohh, it could be that it doesn't support Mediatek because I tried a systemless SuperSU and it didn't boot the MT6580 device. I had to flash the boot.img to fix.
kirito9 said:
Ohh, it could be that it doesn't support Mediatek because I tried a systemless SuperSU and it didn't boot the MT6580 device. I had to flash the boot.img to fix.
Click to expand...
Click to collapse
There is no reason systemless root shouldn't work on mediatek phones other then the different kernel headers. The OP says he got it working, which is why I posted my questions to him... but he has failed to respond.
AlexZap said:
There is no reason systemless root shouldn't work on mediatek phones other then the different kernel headers. The OP says he got it working, which is why I posted my questions to him... but he has failed to respond.
Click to expand...
Click to collapse
There isn't? Strange, then why when I flashed the SuperSU systemless zip from here it didn't boot but when flashed the SuperSU from here it did but said in SuperSU app, couldn't find the su binary.
Maybe I should push "su" to xbin folder or bin? What are your thoughts?
kirito9 said:
There isn't? Strange, then why when I flashed the SuperSU systemless zip from here it didn't boot but when flashed the SuperSU from here it did but said in SuperSU app, couldn't find the su binary.
Maybe I should push "su" to xbin folder or bin? What are your thoughts?
Click to expand...
Click to collapse
I think you need to read some more on how and why systemless root works and what it is for.
Regular root, the summer you installed, puts a bunch of binaries in the /system partition on your android phone, and while giving you root, it breaks a lot of things because it modifies the stock image, something that android doesn't expect to ever change except for system upgrades.
Systemless root fixes this. It does nothing to the system partition. It creates a mountable image and stores it in the /data partition that contains the su binary and whatever else is needed for root. It then modifies the boot image (the ramdisk that is packed with the kernel) so that on boot, it mounts this su image inside the already mounted system partition. This keeps the system partition stock, but at the same time, gives you root. Things like safetynet are unbroken and you can run things like android pay that check for a modified system image.
In order to do its magic, the systemless root installer has to be able to unpack and repack the boot partition. If you have a mediatek phone, you have about an 80% chance that your boot image is different then the rest of the android world. Mediatek phones have their own header in their images like boot and recovery (except for some very new devices). I am 95% certain that the systemless root installer does not know anything about mediatek headers. So it may unpack something, but clobber the boot image on repack. The author of this thread purports to have it working. I ask how. Is he one of the 20 or so percent without a mediatek header? Or did he do something else
AlexZap said:
.................
Click to expand...
Click to collapse
Yeah lol, first time working with android 6.0 and this systemless root. I know that's what the systemless root does, that's why after flashing the MT6580 device that I have, it didn't boot. Don't think the systemless supports this MT6580 as it uses it's own MTK header and not the standard AOSP.
Seems like OP as disappeared from this thread.
Sorry I took so long to respond
AlexZap said:
There is no reason systemless root shouldn't work on mediatek phones other then the different kernel headers. The OP says he got it working, which is why I posted my questions to him... but he has failed to respond.
Click to expand...
Click to collapse
And yes I got the systemless root working on my Panasonic T41 running CM 12
The SuperSU installer doesn't work on mediatek 'coz in cannot unpack the boot.img with mtk headers so i did it manually but SuperSU tried to fix the placement of the binaries !!
So i used another superuser !!
uttarayan21 said:
And yes I got the systemless root working on my Panasonic T41 running CM 12
The SuperSU installer doesn't work on mediatek 'coz in cannot unpack the boot.img with mtk headers so i did it manually but SuperSU tried to fix the placement of the binaries !!
So i used another superuser !!
Click to expand...
Click to collapse
I have found that magisk works flawlessly on my Jiayu s3... it uses hybrid headers in the images... but magical does the unpack/repack just fine.
Sent from my KFTHWI using XDA Premium 4 mobile app
AlexZap said:
I have found that magisk works flawlessly on my Jiayu s3... it uses hybrid headers in the images... but magical does the unpack/repack just fine.
Click to expand...
Click to collapse
Well but in my case when i tried it on CM 12.1 mtk6582
The phone got bricked !!
The SuperSU installer couldn't even get the boot image from my phone !! :crying: so i tried to modify the installer script with other tools but it was waaaay too complex for me so tried to do this instead with another superuser and it worked !!
I also had to modify the init.rc to start the daemonsu service !!! :good:
uttarayan21 said:
Well but in my case when i tried it on CM 12.1 mtk6582
The phone got bricked !!
The SuperSU installer couldn't even get the boot image from my phone !! :crying: so i tried to modify the installer script with other tools but it was waaaay too complex for me so tried to do this instead with another superuser and it worked !!
I also had to modify the init.rc to start the daemonsu service !!! :good:
Click to expand...
Click to collapse
I think magisk is better at handling boot image formats.
AlexZap said:
I think magisk is better at handling boot image formats.
Click to expand...
Click to collapse
I agree with @AlexZap and i am using it and it is working perfectly
Sent from my Z14 using Tapatalk
Does this work for the newer chipsets? I tried on Android 6.0 / MT6750, but I dont see the path export anywhere in the boot image (grep -nrw 'boot.img-ramdisk' -e "PATH")
MalikDrako said:
Does this work for the newer chipsets? I tried on Android 6.0 / MT6750, but I dont see the path export anywhere in the boot image (grep -nrw 'boot.img-ramdisk' -e "PATH")
Click to expand...
Click to collapse
magisk works flawlessly. no need to muck around, just flash it from twrp
Sent from my KFGIWI using XDA Premium 4 mobile app
AlexZap said:
magisk works flawlessly. no need to muck around, just flash it from twrp
Click to expand...
Click to collapse
I've been having trouble getting TWRP to run on this phone (black screen for a few seconds then it reboots into android), although I just discovered an unmodified repacked boot image wont boot, so either the phone is doing some verification that is failing or the tool I used cant repack it right
MalikDrako said:
I've been having trouble getting TWRP to run on this phone (black screen for a few seconds then it reboots into android), although I just discovered an unmodified repacked boot image wont boot, so either the phone is doing some verification that is failing or the tool I used cant repack it right
Click to expand...
Click to collapse
any chance the boot loader is locked? usually flashing a bad image will brick your phone if the boot loader is locked, but you never know.
have you tried unpacking the boot image with carliv's image kitchen? it throws out a bunch of info on how the image is made. as long as it is repacked the same way (Carliv's tool does this automatically), it should work fine. unless whoever your phone manufacturer is somehow included another signature check... which is really really out of the ordinary.
AlexZap said:
any chance the boot loader is locked? usually flashing a bad image will brick your phone if the boot loader is locked, but you never know.
have you tried unpacking the boot image with carliv's image kitchen? it throws out a bunch of info on how the image is made. as long as it is repacked the same way (Carliv's tool does this automatically), it should work fine. unless whoever your phone manufacturer is somehow included another signature check... which is really really out of the ordinary.
Click to expand...
Click to collapse
I just tried Carliv's image kitchen, and both boot and twrp port worked first try
How to change Permissions?
i could not understand it
can u help me Please?
Steps
Unlock bootloader
Enable adb debugging via developer settings
Push the SuperSU zip onto your watch:
"adb push SuperSU.zip /sdcard/"
"adb reboot bootloader"
Flash or just boot custom recovery:
fastboot boot twrp-3.1.1.0.img
fastboot flash recovery twrp-3.1.1.0.img
Install SuperSU:
In the bootloader menu, select "RECOVERY MODE"
Press "Install", "Install Zip", SuperSU.zip, next, "Reboot after installation is complete", start.
Now you should have root in android wear 2.0 final build number NXH20E
All the files are not mine, i have just build the TWRP for our Smartwatch.
here is the link for download:
https://drive.google.com/drive/folders/0Bzk4DPXefDhrRzl3ckh6Uzhad1k?usp=sharing
If you would like to buy me a bear this is my paypal account [email protected]
zbask said:
Steps
Unlock bootloader
Enable adb debugging via developer settings
Push the SuperSU zip onto your watch:
"adb push SuperSU.zip /sdcard/"
"adb reboot bootloader"
Flash or just boot custom recovery:
fastboot boot twrp-3.1.1.0.img
fastboot flash recovery twrp-3.1.1.0.img
Install SuperSU:
In the bootloader menu, select "RECOVERY MODE"
Press "Install", "Install Zip", SuperSU.zip, next, "Reboot after installation is complete", start.
Now you should have root in android wear 2.0 final build number NXH20E
All the files are not mine, i have just build the TWRP for our Smartwatch.
here is the link for download:
https://drive.google.com/drive/folders/0Bzk4DPXefDhrRzl3ckh6Uzhad1k?usp=sharing
If you would like to buy me a bear this is my paypal account [email protected]
Click to expand...
Click to collapse
Hi, Congratulations for the help and thanks
After doing all the procedure I did the verification of the root and
Tells me it's not root.
It's possible?
Michele
mminfor said:
Hi, Congratulations for the help and thanks
After doing all the procedure I did the verification of the root and
Tells me it's not root.
It's possible?
Michele
Click to expand...
Click to collapse
you can check root trough adb
connect the watch and type this:
"adb shell"
"su"
you must have installed busybox on rails on the watch, you can try only booting the recovery with this command "fastboot boot twrp-3.1.1.0.img"
zbask said:
Steps
Unlock bootloader
Enable adb debugging via developer settings
Push the SuperSU zip onto your watch:
"adb push SuperSU.zip /sdcard/"
"adb reboot bootloader"
Flash or just boot custom recovery:
fastboot boot twrp-3.1.1.0.img
fastboot flash recovery twrp-3.1.1.0.img
Install SuperSU:
In the bootloader menu, select "RECOVERY MODE"
Press "Install", "Install Zip", SuperSU.zip, next, "Reboot after installation is complete", start.
Now you should have root in android wear 2.0 final build number NXH20E
All the files are not mine, i have just build the TWRP for our Smartwatch.
here is the link for download:
https://drive.google.com/drive/folders/0Bzk4DPXefDhrRzl3ckh6Uzhad1k?usp=sharing
If you would like to buy me a bear this is my paypal account [email protected]
Click to expand...
Click to collapse
I can confirm that you are correct that the TWRP does flash correctly and that the normal reboot to recovery works properly and I thank you for that, but the SU does not flash properly I get error 2 which indicates it does not work for the device (through searching) google, I forgot what that error was, I tested through the only app I see on wear that allows root and works, Advanced Settings and anytime I change the processor settings and exit the app, the same standard non-root settings appear again. Indicating that root was un-successful. I will see what I can do for the SU zip, becuase it appears to be related to the updater binary, the updater scirpt is usually more straigt forward, but sometimes harder to figure out. I will try to do what I can in this regard, but power might go out (Harvey) and circumstances might becom unfavorable throught this weekend.
try this supersu
https://drive.google.com/open?id=0Bzk4DPXefDhrUjRLTXpPSkxVT2M
zbask said:
try this supersu
https://drive.google.com/open?id=0Bzk4DPXefDhrUjRLTXpPSkxVT2M
Click to expand...
Click to collapse
I also tried this but nothing to do still gives me "no root"
I will wait for better times.
thank you
MMinfor
Working.
mminfor said:
I also tried this but nothing to do still gives me "no root"
I will wait for better times.
thank you
MMinfor
Click to expand...
Click to collapse
I worked on it over the weekend and figured out what was my problem. After going through the updater binary for the SuperSU I noticed that if you made the kernel insecure within the default.prop the updater thinks you are already root and attempts to go for the regular install instead of the systemless root method required by wear, so I luckily made a backup of the original unmodified kernel, re-flashed that and attempted to flash the SuperSU zip again, I did not use the zip in this thread instead I made a flashable zip of the newest SuperSU 2.82 version that works for wear. I have uploaded both the SuperSU zip I created along with the original kerenel that is unmodified. One thing to note if you flash the original kernel you will have to flash TWRP recovery again as I had to. I am still new to how Android Wear works, but will try to help with what I can.
SuperSU Zip.
Original Kerel.
physicistman said:
I worked on it over the weekend and figured out what was my problem. After going through the updater binary for the SuperSU I noticed that if you made the kernel insecure within the default.prop the updater thinks you are already root and attempts to go for the regular install instead of the systemless root method required by wear, so I luckily made a backup of the original unmodified kernel, re-flashed that and attempted to flash the SuperSU zip again, I did not use the zip in this thread instead I made a flashable zip of the newest SuperSU 2.82 version that works for wear. I have uploaded both the SuperSU zip I created along with the original kerenel that is unmodified. One thing to note if you flash the original kernel you will have to flash TWRP recovery again as I had to. I am still new to how Android Wear works, but will try to help with what I can.
SuperSU Zip.
Original Kerel.
Click to expand...
Click to collapse
This solution seems to work.
Here's the check
thanks
zbask said:
Steps
Unlock bootloader
...
Click to expand...
Click to collapse
How exactly do you unlock the bootloader?
madsc13n41s4 said:
How exactly do you unlock the bootloader?
Click to expand...
Click to collapse
1.Unlock the bootloader if not already unlocked
(Make sure to set up device with phone after unlocking bootloader otherwise no boot!)
Code:
- adb reboot bootloader
- fastboot oem unlock
enjoy!
Is there any way we can pass SafetyNet for Android Pay using SuperSU?
???
Will this work with watch sport as well?
Can we then maybe fix APN settings after its rooted?
Grumps said:
Will this work with watch sport as well?
Can we then maybe fix APN settings after its rooted?
Click to expand...
Click to collapse
APN settings cannot be changed on AW2.0 because SquashFS is read-only. Howerver, if you edit APN settings manually in AW1.5 (using xml file edit from adb root shell, see this forum for tutorial), they remain & work after OTA update to AW2.0. They will be lost, however, if you disconnect your watch from the phone "the official way" (with hard reset). In order to always use APN settings, use this tutorial on how to pair AW watch to new phone without factory reset.
Drakosha said:
APN settings cannot be changed on AW2.0 because SquashFS is read-only. Howerver, if you edit APN settings manually in AW1.5 (using xml file edit from adb root shell, see this forum for tutorial), they remain & work after OTA update to AW2.0. They will be lost, however, if you disconnect your watch from the phone "the official way" (with hard reset). In order to always use APN settings, use this tutorial on how to pair AW watch to new phone without factory reset.
Click to expand...
Click to collapse
Isnt APN settings configured after you install a sim card from the provider? Surely it must then be stored somewhere else?
Did anyone succeed ?
what is about squashfs? is there anyway, to make /system/ writeable?
sebj84 said:
what is about squashfs? is there anyway, to make /system/ writeable?
Click to expand...
Click to collapse
Ok,
sorry wasn't on aw before. so sorry for my last question.
Anyhow. Did somebody managed to get XPosed running?
I've tried, but got an error of not enough place on /system. When i try to delete system apps, i get the same error.
Now using supersu.
before with magisk, got xposed and a few other packsages installed, but they never show up in magisk later
SQUASHFS is read only by default.
sebj84 said:
Ok,
sorry wasn't on aw before. so sorry for my last question.
Anyhow. Did somebody managed to get XPosed running?
I've tried, but got an error of not enough place on /system. When i try to delete system apps, i get the same error.
Now using supersu.
before with magisk, got xposed and a few other packsages installed, but they never show up in magisk later
Click to expand...
Click to collapse
You won't be able to do anything within the /system/ partition while it is mounted. I can't answer the question as to why specifically, because I am not as knowledgeable of it, but here is the wiki SQUASHFS info. and another one that gives more information as to the uses SQUASHFS HOWTO.. If I am correct in order to make any changes to the system one would have to have a backup or original system image unsquash the image make any changes from that then re-squash the image and flash it in custom recovery. I have already unsquashed the image of the original image from the newest update myself and have it on my laptop, but I have not been able to go much further (busy). There are workarounds to the system not being able to write, but those are mostly for other versions of the filesystem and on different devices along with it not being totally writable.
Ok. I see now.
Thanks for the link. I will check those infos first.
physicistman said:
I worked on it over the weekend and figured out what was my problem. After going through the updater binary for the SuperSU I noticed that if you made the kernel insecure within the default.prop the updater thinks you are already root and attempts to go for the regular install instead of the systemless root method required by wear, so I luckily made a backup of the original unmodified kernel, re-flashed that and attempted to flash the SuperSU zip again, I did not use the zip in this thread instead I made a flashable zip of the newest SuperSU 2.82 version that works for wear. I have uploaded both the SuperSU zip I created along with the original kerenel that is unmodified. One thing to note if you flash the original kernel you will have to flash TWRP recovery again as I had to. I am still new to how Android Wear works, but will try to help with what I can.
SuperSU Zip.
Original Kerel.
Click to expand...
Click to collapse
I changed my phone and I have on LG Urban 2 started the Wear Recovery procedure.
after restart, it will start only on TWRP. what can I do??
Thanks in advance
mminfor
As you all know we have been searching for ways to root the Le Pro 3AI but failed. There are even 2 twrp but you can't really do much with them. TWRP 3.1 did not even start for me but 3.0.3 worked but what's the real problem? You can't mount /data and also i found another partition named /custom. It always fails to mount and there is no way to format it.
When you enter TWRP it ask for a password to decrypt. Simply click cancel and go to wipe, advanced wipe and check the data partition. Select repair file system and change it to ext2 and then back to ext4. Reboot to twrp again I don't think this is necessary but better take precautions. Now go to mount and select data you will see that you can actually mount it(~24000mb) .
You can also enable MTP to copy files to your phone in recovery such as .zips. I hope this helps you in way. I hope the devs find a way to make it possible to flash custom ROMs for this phone without any message appearing during boot and that there is no problem with imei. Thanks for reading and don't give up with this phone else it will be money down the drain. If I helped press the thanks button.
how did you install the TWRP?
im a noob in this
okay! so after attempting to install TWRP my phone bricked haha
i had to flash again the rom. geez!
i better not attempt again.
twrp isn't really a problem. it works for the most part, just cant be perma flashed, only booted. you can still flash zips via sideload as it is though, so that was never a *huge issue*. thing is, modifying system partition on official builds (25, 28) will cause security lockup. kernel needs to be patched, and prolly bootloader for this to be bypassed, and it seems its not easy. consequently root will fail too. on 27 though, you can easily boot twrp and flash a custom zip (except root), so there is nothing preventing you from removing bloat. even xposed works. you can even flash 27 kernel on both 25/28 and clean them too using same flashable zips. as far as custom rom goes, yeah, no, mtk device. prolly not gonna happen. be happy if you get root eventually.
sikica133 said:
twrp isn't really a problem. it works for the most part, just cant be perma flashed, only booted. you can still flash zips via sideload as it is though, so that was never a *huge issue*. thing is, modifying system partition on official builds (25, 28) will cause security lockup. kernel needs to be patched, and prolly bootloader for this to be bypassed, and it seems its not easy. consequently root will fail too. on 27 though, you can easily boot twrp and flash a custom zip (except root), so there is nothing preventing you from removing bloat. even xposed works. you can even flash 27 kernel on both 25/28 and clean them too using same flashable zips. as far as custom rom goes, yeah, no, mtk device. prolly not gonna happen. be happy if you get root eventually.
Click to expand...
Click to collapse
can you tell me the procedure on installing twrp?
i really wanted to enable multi window via adb when on recovery mode.
thanks
sikica133 said:
twrp isn't really a problem. it works for the most part, just cant be perma flashed, only booted.
Click to expand...
Click to collapse
I could flash only 3.0.3 . 3.1 never worked for me. Can't even boot.
i never said it could be flashed. it could be booted into. there are plenty of guides around how to boot recovery using fastboot (google fastboot boot recovery.img). once there, you can simply use adb sideload, or integrated file manager to clean system apps and reboot back into os. if you are using 25/28 u'll need to play a bit more to get everything up and running (imei issues), on 27S (multilanguage rom) this is pretty straightforward and no fixing is required
adb devices and uninstall system app
adb devices and uninstall system app
minimal_adb_fastboot_1.4.3_portable --- download androidfilehostcom/?fid=457095661767103465
cmd-here.exe
adb devices
adb shell
pm uninstall -k --user 0 [apk name]
com.letv.agnes
com.icoolme.android.weather
com.letv.android.bugreporter
com.letv.android.carservice
com.letv.android.ecoProvider
com.letv.android.letvyellowpage
com.letv.android.ota
com.letv.android.client
com.letv.android.quicksearchbox
com.letv.android.telextra
com.letv.android.usermanual
com.letv.app.appstore
com.letv.bsp.crashhandler
com.letv.bugpostbox
com.letv.lesophoneclient
com.letv.letvshop
com.singulariti.niapp
com.sohu.inputmethod.sogou.leshi
com.tencent.android.location
sina.mobile.tianqitongletv
com.autonavi.minimap
com.tencent.reading
com.le.share.pro3ai
com.letv.games
com.android.calendar
com.android.noisefield
youtubecom/watch?v=TSwBsw6MgiA
Gapps apk
fex-net/934605209940/246920922 - 4pda
lucky patcher.apk install -- delete all google applications
1-GoogleBackupTransport.apk install and Give all permissions in menu applications
2-GoogleLoginService.apk install and Give all permissions in menu applications
3-GoogleServicesFramework.apk install and Give all permissions in menu applications
4-Phonesky.apk install and Give all permissions in menu applications
5-PrebuiltGmsCore.apk install and Give all permissions in menu applications
İ LOVE TURKEY
Monster 00 said:
As you all know we have been searching for ways to root the Le Pro 3AI but failed. There are even 2 twrp but you can't really do much with them. TWRP 3.1 did not even start for me but 3.0.3 worked but what's the real problem? You can't mount /data and also i found another partition named /custom. It always fails to mount and there is no way to format it.
When you enter TWRP it ask for a password to decrypt. Simply click cancel and go to wipe, advanced wipe and check the data partition. Select repair file system and change it to ext2 and then back to ext4. Reboot to twrp again I don't think this is necessary but better take precautions. Now go to mount and select data you will see that you can actually mount it(~24000mb) .
You can also enable MTP to copy files to your phone in recovery such as .zips. I hope this helps you in way. I hope the devs find a way to make it possible to flash custom ROMs for this phone without any message appearing during boot and that there is no problem with imei. Thanks for reading and don't give up with this phone else it will be money down the drain. If I helped press the thanks button.
Click to expand...
Click to collapse
can you help me enable multi window?
It says that I need to mount system first at the recovery.
Please help me. Thanks a lot.