Related
Hi guys
I'm new to deodexing, following a guide for XUltimate.
I copied my system\app dir to a folder called origi_app, and my system\framework to a folder called origi_frame on my int SD card, then copied these two folders to my PC XUltimate dir.
Ran option 3, then 4, both finished with sucessful.
This gave me two new folders in the XUltimate dir...
done_app & done_frame
I copied these back to my int SD card, then following the guide, ran ADB from cmd prompt..
Typed: ADB Shell
Got a $
Typed: SU
This gave me a Permission Denied ??
So as per the guide, I tried Root Explorer...
Selected All the .apps in done_App, selected copy and then tried to paste into the system\app dir.... this then gave me a failed to copy due to lack of space error and the phone started to vibrate and com.android force closing repeatedly...
Were did I go wrong, why did I get permission denied trying to get the SU cmd?
The full adb guide was as follows:
adb shell
su
stop
mount -o rw,remount /dev/block/mmcblk1p21 /system
rm /system/app/*.odex
rm /system/framework/*.odex
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
mount -o ro,remount /dev/block/mmcblk1p21 /system
reboot
As above, got as far as SU then got permission denied!
So thankfully I did a nandroid backup before and am currently restoring it...
EDIT: My Backup has just finished restoring from CWM... rebooted but it is now on original startup setup and getting force closes for lots of apps???
Had to re add my APN settings to re download MY Backup and am currently restoring apps and data from it now! Fingers crossed. I thought the whole point of a cwm back up was to create an exact image of the whole system, files, date and settings etc?
Well, restored via My Backup, but rom manager and Sky news kept force closing, so wiped the whole thing and flash a custom js8 from from Doc's kitchen... glad I did... just miss the cirlce battery mod I had before.
Hi all,
is it possibile to modify the content of the files fills with the content of the partitions read from the Tegra of my LG P990 with nvflash?
I had read the partition from the board with
Code:
nvflash -r --read <-partitionID-> my_partition.img
Unix's command file said to me that the output file is data:
Code:
$ file my_partition.img
my_partition.img: data
But if the correct img file is provided to 'file', for example the file that nvflash returned when we asked it to read the partition 23, the APP partition, 'file' said:
Code:
23_APP.img: Linux rev 1.0 ext4 filesystem data, UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx (needs journal recovery) (extents) (large files)
How i can mount this type of image file ?
Easily with the 'mount' Linux utility
Code:
mount ./my_partition.img ./tmp_directory
Now, if I add the su binary of chains_dd compiled for my platform in the system partition image file and after,
reflash the image file on my O2X I should able to get root, right?
It seems too easy...
Any help is appreciated.
Thanks!
Yes, it is "easy" like that. I made similar staff (extract partition image from official update, mount, extract selected files).
Edit: Only I remember that I need to specify mount parameters related to partition format and mounting access.
Have you really gain root access only by copyng (and launching ) su binary in xbin directory?
tryin said:
Have you really gain root access only by copyng (and launching ) su binary in xbin directory?
Click to expand...
Click to collapse
Y E S . . .
Indeed, if you only want a root prompt, chains_dd's binary is too much...
tryin said:
Y E S . . .
Indeed, if you only want a root prompt, chains_dd's binary is too much...
Click to expand...
Click to collapse
Take a look at this...
http://forum.xda-developers.com/showthread.php?t=2280447
Hey guys Lets get the ball rolling and get some development out into the light.
First you will have to download the OTA from Google.
Google’s OTA(13300): http://cache.pack.google.com/edgedl....1f63ef63d1f43c6222116806e5bea38a47e9f124.zip
Next download “SquashFS Exracter”, this tool is used to extract the System.img.
SquashFS Exracter: https://mega.co.nz/#!oEMFQCrC!JbD_9XeS28xu7vZBDipBzDWqdnF1i9cKMRzq2i_vEDU
When you are ready to go, simply drag system.img onto unsquashfs.exe, and the extraction will do its thing.
A new folder named “squashfs-root” will be where the system.img were located. This folder contains the extracted System.
Have a look around, and please report findings! :fingers-crossed:
Findings
/res/ - Contains some of the images used for the system. The boot animation is placed here.
/netflix/ - Self-explanatory. The Netflix app for the Chromecast.
/chrome/content_shell.pak – Contains a lot of useful information for the right eyes.
/chrome/osd_images/**** - Contains images used for the on-screen-display atm. volume slider.
/chrome/locals/ - Contains language files for the Chromecast.
Thx to ddggttff3 and tchebb for the links etc. :good:
Just FYI guys, here is link for newest OTA, build 19084, so you can check, what's new is inside.
http://cache.pack.google.com/edgedl/googletv-eureka/stable-channel/ota.19084.stable-channel.eureka-b3.0149464816d26917f37cb4a263171183cc00957a.zip
For extract system.img download and use SquashFS Exracter tool from previous post.
bormeth said:
Hey guys Lets get the ball rolling and get some development out into the light.
First you will have to download the OTA from Google.
Google’s OTA(13300): http://cache.pack.google.com/edgedl....1f63ef63d1f43c6222116806e5bea38a47e9f124.zip
Next download “SquashFS Exracter”, this tool is used to extract the System.img.
SquashFS Exracter: https://mega.co.nz/#!oEMFQCrC!JbD_9XeS28xu7vZBDipBzDWqdnF1i9cKMRzq2i_vEDU
When you are ready to go, simply drag system.img onto unsquashfs.exe, and the extraction will do its thing.
A new folder named “squashfs-root” will be where the system.img were located. This folder contains the extracted System.
Have a look around, and please report findings! :fingers-crossed:
Findings
/res/ - Contains some of the images used for the system. The boot animation is placed here.
/netflix/ - Self-explanatory. The Netflix app for the Chromecast.
/chrome/content_shell.pak – Contains a lot of useful information for the right eyes.
/chrome/osd_images/**** - Contains images used for the on-screen-display atm. volume slider.
/chrome/locals/ - Contains language files for the Chromecast.
Thx to ddggttff3 and tchebb for the links etc. :good:
Click to expand...
Click to collapse
I've been playing with unsquash in linux to add stuff to /etc. I realised linux can have a symlinks to a symlincs. So we can rederect /system/etc to /data/etc if we want to. It's probebly not so secure to have several symlincs in a chain, but I wanted ta add stuff like motd and profile to etc without reflasing it evertime I make a change.
First on then Cromecast
-----------------------------
cp -pr /system/ /data
On Debian 7
---------------
su root
apt-get install squashfs-tools
mkdir flash
cd flash
wget http://pdl.team-eureka.com/ota/19084.001.zip
unzip 19084.00.1.zip
unsquashfs system.img
cd squashfs-root
mv etc etc.bk
ln /data/system/etc -s etc
cd ..
rm system.img
mksquashfs squashfs-root system.img
rm -r squashfs-root
zip test1.zip *
And then you flash it with flashcast. Now we got a writable etc catalog. I haven't tryed symlinkc all catalogs in the system dir, but bin and etc are working fine as symlincs to /data/system dir.
Just FYI guys, there is again new build, and here is link for that OTA, build 46278.
http://cache.pack.google.com/edgedl/googletv-eureka/stable-channel/ota.46278.stable-channel.eureka-b3.ef7fdf1f7153dacecc77b7d1a3bb22a97e27ec7e.zip
For extract system.img download and use SquashFS Exracter tool from first post.
Mape0661 said:
I've been playing with unsquash in linux to add stuff to /etc. I realised linux can have a symlinks to a symlincs. So we can rederect /system/etc to /data/etc if we want to. It's probebly not so secure to have several symlincs in a chain, but I wanted ta add stuff like motd and profile to etc without reflasing it evertime I make a change.
First on then Cromecast
-----------------------------
cp -pr /system/ /data
On Debian 7
---------------
su root
apt-get install squashfs-tools
mkdir flash
cd flash
wget (i cant post links... -_-)
unzip 19084.00.1.zip
unsquashfs system.img
cd squashfs-root
mv etc etc.bk
ln /data/system/etc -s etc
cd ..
rm system.img
mksquashfs squashfs-root system.img
rm -r squashfs-root
zip test1.zip *
And then you flash it with flashcast. Now we got a writable etc catalog. I haven't tryed symlinkc all catalogs in the system dir, but bin and etc are working fine as symlincs to /data/system dir.
Click to expand...
Click to collapse
when i try this my CC just hangs at the black screen after the Eureka logo. instead of modifying etc, i just added a text file to etc so i could see if it got flashed. my file is there, and i can use SSH/Telnet and the web controls, it just wont boot past the black screen. Any advise?
casper33 said:
when i try this my CC just hangs at the black screen after the Eureka logo. instead of modifying etc, i just added a text file to etc so i could see if it got flashed. my file is there, and i can use SSH/Telnet and the web controls, it just wont boot past the black screen. Any advise?
Click to expand...
Click to collapse
Were you modifying the image as root? If not, you can have permission issues when rebuilding the squashfs file.
ddggttff3 said:
Were you modifying the image as root? If not, you can have permission issues when rebuilding the squashfs file.
Click to expand...
Click to collapse
well now i feel stupid, indeed i wasn't root, thank you!
Hi I need specific help with the mksquashfs.exe command in Windows to repack system.img to system.sfs
Specifically, if I have the system.img on c:\ temp folder, what is the syntax to end up with system.sfs in same directory.
Can anybody help?
There have been quite a bit of people with issues with Systemless root, there are some apps that are not recognizing root, i had this issue with my Oneplus One on COS 13.1 and now the same thing works with our OnePlus 3 on OxygenOS
I had come across this on another forum, i don't recall where so i don't want to take the credit for this, i just want to provide the fix for people who have this phone and having issues
Download Terminal from app store and type
Code:
su
mount -o remount,rw /system
touch /system/bin/su
mount -o remount,ro /system
reboot
Thank you ! Before I try this , can you tell me what this method is doing ? All I can tell is that it is mounting something as read only instead of read write
I belive it creates a dummy file bc some apps require it to show as a system file
SDMU said:
Thank you ! Before I try this , can you tell me what this method is doing ? All I can tell is that it is mounting something as read only instead of read write
Click to expand...
Click to collapse
Code:
1. su
2. mount -o remount,rw /system
3. touch /system/bin/su
4. mount -o remount,ro /system
5. reboot
1. To get root privileges
2. Remounts /system partition in writable mode
3. Creates an empty file called su to /system/bin/ folder
4. Remounts /system partition to read only mode.
5. reboot
Edit. As stated above, some apps still check root access by looking su file in /system/bin folder
Squabl said:
1. To get root privileges
2. Remounts /system partition in writable mode
3. Creates an empty file called su to /system/bin/ folder
4. Remounts /system partition to read only mode.
5. reboot
Edit. As stated above, some apps still check root access by looking su file in /system/bin folder
Click to expand...
Click to collapse
This defeats the purpose of a system less su, I.e., not modifying the system partition. Step 3 modifies the system partition.
The reason apps are not seeing the su in system less state is because they have been written incorrectly. Chainfire already said these apps should be re written
candiesdoodle said:
This defeats the purpose of a system less su, I.e., not modifying the system partition. Step 3 modifies the system partition.
The reason apps are not seeing the su in system less state is because they have been written incorrectly. Chainfire already said these apps should be re written
Click to expand...
Click to collapse
Yes, it "disables" systemless root and afterwards it is just a root and banking apps and ota updates etc will fail. I don't need systemless root so I have modified my system partition to get some poorly coded apps to function. This method is not recommended if you need systemless root and it's a good thing that you pointed that out!
Dear community,
I installed xposed using the following adk: XposedInstaller_3.0_alpha4.apk then flash, from recovery, the framework for my Oukitel K6000 Pro (Android 6.0): xposed-v86-sdk23-arm64.zip
All worked fine until I have to restore a backup from recovery (backup taken before I flash the framework).
Now, Xposed cannot see the framework, so I tried to uninstall it using xposed-uninstaller-20150831-arm64.zip always from recovery. The uninstallation seems goes ok, so I reboot the device, enter again into recovery to flash again the xposed-v86-sdk23-arm64.zip
Unfortunately I got an error during install process:
chown: /system/bin/dex2oat.orig.gz read only file system
or
cp: can't create '/system/xposed.prop' File esists
And the installation stop there.
Could someone help me to reinstall the framework and come back to working status?
Thank you
Lucas
Lord Spectre said:
Dear community,
I installed xposed using the following adk: XposedInstaller_3.0_alpha4.apk then flash, from recovery, the framework for my Oukitel K6000 Pro (Android 6.0): xposed-v86-sdk23-arm64.zip
All worked fine until I have to restore a backup from recovery (backup taken before I flash the framework).
Now, Xposed cannot see the framework, so I tried to uninstall it using xposed-uninstaller-20150831-arm64.zip always from recovery. The uninstallation seems goes ok, so I reboot the device, enter again into recovery to flash again the xposed-v86-sdk23-arm64.zip
Unfortunately I got an error during install process:
chown: /system/bin/dex2oat.orig.gz read only file system
or
cp: can't create '/system/xposed.prop' File esists
And the installation stop there.
Could someone help me to reinstall the framework and come back to working status?
Thank you
Lucas
Click to expand...
Click to collapse
Try clearing art/dalvik and cache then reboot directly back into recovery and flash Xposed again
Sent from my SCH-R220
Thank you for reply mattzeller, unfortunately, after cleaning art/dalvik and cache and reboot directly into recovery to install sdk I got the same error:
chown: /system/bin/dex2oat.orig.gz read only file system
Lord Spectre said:
Thank you for reply mattzeller, unfortunately, after cleaning art/dalvik and cache and reboot directly into recovery to install sdk I got the same error:
chown: /system/bin/dex2oat.orig.gz read only file system
Click to expand...
Click to collapse
Try mounting system as read/write in recovery before flashing
Sent from my SCH-R220
mattzeller said:
Try mounting system as read/write in recovery before flashing
Click to expand...
Click to collapse
I believe you mean from terminal, could you please share the command to do that? Thx!
However I see from recovery log, during uninstall/install processes:
Mounting /system and /vendor read-write
So, packages already tried to mount system... Maybe fails, I don't know!!!
Lord Spectre said:
I believe you mean from terminal, could you please share the command to do that? Thx!
However I see from recovery log, during uninstall/install processes:
Mounting /system and /vendor read-write
So, packages already tried to mount system... Maybe fails, I don't know!!!
Click to expand...
Click to collapse
In recovery open terminal :
mount -o rw,remount /system
Then try to flash Xposed
Sent from my SCH-R220
DAMN!DAMN!DAMN! This is what I done on terminal:
# mount -o rw,remount /system
Try to flash xposed-v86-sdk23-arm64.zip
Got: cp: can't create '/system/xposed.prop' File esists
Then from terminal:
# rm /system/xposed.prop
rm: can't remove '/system/xposed.prop': Read-only file system
At this point I don't know how can I proceed. Maybe flashing stock rom, then install framework from recovery, and then restore backup
Just to inform that I solved reflashing stock rom, recovery TWRP and SuperSU... Then flash again the Xposed SDK. Unfortunately I cannot use the TWRP backup, and I had to configure my phone from scratch.
Lord Spectre said:
Just to inform that I solved reflashing stock rom, recovery TWRP and SuperSU... Then flash again the Xposed SDK. Unfortunately I cannot use the TWRP backup, and I had to configure my phone from scratch.
Click to expand...
Click to collapse
Sounds like something in your backup got screwed up I would suggest deleting that back up once everything is set up and redoing it
Sent from my SCH-R220