Related
Hi, first of all sorry for my english.
I'm S-off, rooted, using TWRP touch and android 5.0 (from ivanich).
I went out of memory on my internal storage, so I had a pop-up that says lower your storage (my sd card couldn't be mounted). Then i went in recovery to wipe cache and data for it would free some space, but I got theses issue:
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: No such device
unmount of /data failed; no such volume
script succeeded: result was [0,200000]
updating partition details...
E:Unable to mount '/cache'
E:Unable to mount '/data'
...done
I also tried by advanced wipe> wipe Data and I went stuck on this :
"Formatting Data using make_ext4fs function"
If i try to reboot on the rom it's bootloop
I tried a few command in the terminal command that I've found here http://forum.xda-developers.com/showthread.php?t=2683787
mke2fs -T ext4 /dev/block/mmcblk0p8
I get this :
filesystem too small for a journal
writing superblocks and lifesystem accounting information : done
This filesystem will be automatically checked every 37 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override.
So I have no idea how to fix this I never had this error before and I can't find anything about it, only Odin but correct me if I'm wrong but Odin doesn't work for Sensation ?
Thanks for any help I appreciate
you are facing probably the same issue with others that faced with twrp
those partitions corrupted after using the wipe options
the only thing i can suggest you is to use this solution
http://forum.xda-developers.com/htc-sensation/help/recovering-data-mount-issues-t2859588
best wishes
So yeah, i've try so many things, and none of them is fixing my problem.
First i've installed 4ext recovery and i had still the same issue, not able to wipe cache or data or factory reset.
I've tried to install adb but it doesn't recognize my phone, even with SDK tools, i can't tell the program what my phone is.
now i've tried to install the RUU (dl the .exe, found the rom.zip, and put on my phone renamed it "PG58IMG.zip" now when i'm on the fastboot it loads the file and then it get stuck at the userdata part....
If i try to boot the normal way i get the black screen with the red triangle and exclamation mark ....
I'm going to keep looking but it's getting harder than expected
(still sorry for my english)
ni4rkx said:
So yeah, i've try so many things, and none of them is fixing my problem.
First i've installed 4ext recovery and i had still the same issue, not able to wipe cache or data or factory reset.
I've tried to install adb but it doesn't recognize my phone, even with SDK tools, i can't tell the program what my phone is.
now i've tried to install the RUU (dl the .exe, found the rom.zip, and put on my phone renamed it "PG58IMG.zip" now when i'm on the fastboot it loads the file and then it get stuck at the userdata part....
If i try to boot the normal way i get the black screen with the red triangle and exclamation mark ....
I'm going to keep looking but it's getting harder than expected
(still sorry for my english)
Click to expand...
Click to collapse
I can't help with issue but userdata is not mmcblk0p8, it's mmcblk0p23 on our device.
hinxnz said:
I can't help with issue but userdata is not mmcblk0p8, it's mmcblk0p23 on our device.
Click to expand...
Click to collapse
Hmm thanks for this info, I will try to do again all this but on an other computer tomorrow maybe it will work... I hope!
So after hours of trying to repair it, it still doesn't work.
But i've found something that might be intersting.
In recovery 4ext but now I'm twrp so I don't have the exact information again but when I went in storage information, it was written that the internal storage was --mb, and --mb free, so I guess it means that my partition doesn't exist anymore.. Anyway I've found that I'm not the only one with this but I still didn't find any solution to fix it..
ni4rkx said:
Hi, first of all sorry for my english.
I'm S-off, rooted, using TWRP touch and android 5.0 (from ivanich).
I went out of memory on my internal storage, so I had a pop-up that says lower your storage (my sd card couldn't be mounted). Then i went in recovery to wipe cache and data for it would free some space, but I got theses issue:
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: No such device
unmount of /data failed; no such volume
script succeeded: result was [0,200000]
updating partition details...
E:Unable to mount '/cache'
E:Unable to mount '/data'
...done
I also tried by advanced wipe> wipe Data and I went stuck on this :
"Formatting Data using make_ext4fs function"
If i try to reboot on the rom it's bootloop
I tried a few command in the terminal command that I've found here http://forum.xda-developers.com/showthread.php?t=2683787
mke2fs -T ext4 /dev/block/mmcblk0p8
I get this :
filesystem too small for a journal
writing superblocks and lifesystem accounting information : done
This filesystem will be automatically checked every 37 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override.
So I have no idea how to fix this I never had this error before and I can't find anything about it, only Odin but correct me if I'm wrong but Odin doesn't work for Sensation ?
Thanks for any help I appreciate
Click to expand...
Click to collapse
I decided to try TWRP yesterday and Im having a similar issue. However when i flash roms I have no issues at all. However i get stuck at the HTC logo forever when i try and boot. I have manually flashed boot.img so that isnt the issue. I even tried doing some mkfs.ext4 executions and i still have the same issue. Im going back to my E63 to see if i can still repair this. However looks like another device is looking likely.
Can anyone tell me if you can run some error logs for when the device is in the boot stage, and by that i mean when the HTC logo so showing? I dont think ADB will work in that mode.
When you try to mount data from recovery does it fail?
Can you tell me which twrp your using? I mean which r stands at the end of the filename?
little_lerroyy said:
I decided to try TWRP yesterday and Im having a similar issue. However when i flash roms I have no issues at all. However i get stuck at the HTC logo forever when i try and boot. I have manually flashed boot.img so that isnt the issue. I even tried doing some mkfs.ext4 executions and i still have the same issue. Im going back to my E63 to see if i can still repair this. However looks like another device is looking likely.
Can anyone tell me if you can run some error logs for when the device is in the boot stage, and by that i mean when the HTC logo so showing? I dont think ADB will work in that mode.
Click to expand...
Click to collapse
What do you mean "some mkfs.ext4 executions" ? I wanted to try that but I couldn't find how to do it, I tried in ADB it didn't work & terminal from twrp neither maybe I didn't type correctly.
I'll suggest you to re flash it, or wipe & flash. (but it's not the point of my thread tho ...)
Sajito said:
When you try to mount data from recovery does it fail?
Can you tell me which twrp your using? I mean which r stands at the end of the filename?
Click to expand...
Click to collapse
Yes I can't mount it..
openrecovery-twrp-2.8.4.0-pyramid.img that i've flash by ADB
ni4rkx said:
What do you mean "some mkfs.ext4 executions" ? I wanted to try that but I couldn't find how to do it, I tried in ADB it didn't work & terminal from twrp neither maybe I didn't type correctly.
I'll suggest you to re flash it, or wipe & flash. (but it's not the point of my thread tho ...)
Yes I can't mount it..
openrecovery-twrp-2.8.4.0-pyramid.img that i've flash by ADB
Click to expand...
Click to collapse
Where did you download that image?
That sounds like you just experienced the brick bug.
Sajito said:
Where did you download that image?
That sounds like you just experienced the brick bug.
Click to expand...
Click to collapse
http://techerrata.com/browse/twrp2/pyramid from http://teamw.in/project/twrp2/66 the recovery img method.
Well I'm not sure because It booted the rom (cm12 from ivanich) but yeah bootloop on the CM logo
ni4rkx said:
http://techerrata.com/browse/twrp2/pyramid from http://teamw.in/project/twrp2/66 the recovery img method.
Well I'm not sure because It booted the rom (cm12 from ivanich) but yeah bootloop on the CM logo
Click to expand...
Click to collapse
I'm sorry to say, but that's definitely the brick bug. Only the link rzr86 posted might help you using your phone. Ivanich made twrp builds, which use his kernel and device trees, so we're pretty sure his twrp is not affected by that bug (that just as an info for anyone using the twrp from the official site. So if anyone reads this and is using twrp newer than 2.6 from official site, get ivanich's build).
The problem is that your data partition is corrupt, not the system partition. But you need the data partition, to use any rom, which is now not mountable anymore. So your able to flash roms and get until bootanimation, but without data partition working it won't boot.
@little_lerroyy did you use ivanich's twrp or the one from official site too?
Sajito said:
I'm sorry to say, but that's definitely the brick bug. Only the link rzr86 posted might help you using your phone. Ivanich made twrp builds, which use his kernel and device trees, so we're pretty sure his twrp is not affected by that bug (that just as an info for anyone using the twrp from the official site. So if anyone reads this and is using twrp newer than 2.6 from official site, get ivanich's build).
The problem is that your data partition is corrupt, not the system partition. But you need the data partition, to use any rom, which is now not mountable anymore. So your able to flash roms and get until bootanimation, but without data partition working it won't boot.
@little_lerroyy did you use ivanich's twrp or the one from official site too?
Click to expand...
Click to collapse
So you're saying that TWRP didn't do their job good enough and bricked my phone ? =/ that's pretty sad
thanks for the info tho but maybe there is a way to re create the data partition, since I think I'm not the only one who has this issue
ni4rkx said:
So you're saying that TWRP didn't do their job good enough and bricked my phone ? =/ that's pretty sad
thanks for the info tho but maybe there is a way to re create the data partition, since I think I'm not the only one who has this issue
Click to expand...
Click to collapse
The problem is not caused by twrp, but the faulty device/kernel trees which were used for that image. Unfortunately nobody knows who built these images, nor do we know which sources were used.
I had that too, I know that sucks.
Sajito said:
The problem is not caused by twrp, but the faulty device/kernel trees which were used for that image. Unfortunately nobody knows who built these images, nor do we know which sources were used.
I had that too, I know that sucks.
Click to expand...
Click to collapse
Alright then.... I have an old motorola defy yeahhhh :good:
ni4rkx said:
Alright then.... I have an old motorola defy yeahhhh :good:
Click to expand...
Click to collapse
You can still try to mount your sdcard as data partition, as explained in the link posted on page 1, it seems to work for some.
ni4rkx said:
What do you mean "some mkfs.ext4 executions" ? I wanted to try that but I couldn't find how to do it, I tried in ADB it didn't work & terminal from twrp neither maybe I didn't type correctly.
I'll suggest you to re flash it, or wipe & flash. (but it's not the point of my thread tho ...)
Yes I can't mount it..
openrecovery-twrp-2.8.4.0-pyramid.img that i've flash by ADB
Click to expand...
Click to collapse
Connect phone to pc, boot into recovery, open terminal and type 'adb devices', your device should show.
To try mount data enter 'adb shell mount /data'.
To check structure enter 'adb shell /sbin/e2fsck -n -f /dev/block/mmcblk0p23'.
Maybe this could help?
Sajito said:
You can still try to mount your sdcard as data partition, as explained in the link posted on page 1, it seems to work for some.
Click to expand...
Click to collapse
Hm I've take a look but it looks complicated :s
hinxnz said:
Connect phone to pc, boot into recovery, open terminal and type 'adb devices', your device should show.
To try mount data enter 'adb shell mount /data'.
To check structure enter 'adb shell /sbin/e2fsck -n -f /dev/block/mmcblk0p23'.
Maybe this could help?
Click to expand...
Click to collapse
Well I'll give it a try when I can work on an other computer because I also have an issue with windows 8.1, it doesn't recognize my phone, so I can't use adb to work with the phone. It worked on windows 7 on an other computer but I can't use it for now.. Thanks anyway I'll keep you in touch
ni4rkx said:
What do you mean "some mkfs.ext4 executions" ? I wanted to try that but I couldn't find how to do it, I tried in ADB it didn't work & terminal from twrp neither maybe I didn't type correctly.
I'll suggest you to re flash it, or wipe & flash. (but it's not the point of my thread tho ...)
Yes I can't mount it..
openrecovery-twrp-2.8.4.0-pyramid.img that i've flash by ADB
Click to expand...
Click to collapse
Follow this link, the process is done in ADB
http://android-revolution-hd.blogspot.com.au/2013/10/fix-data-htc-one.html
Just make sure where it says "mmcblk0p37" in step number 10, you put in "mmcblk0p23" which is your data partition, but i doubt you will have much access doing this.
little_lerroyy said:
Follow this link, the process is done in ADB
http://android-revolution-hd.blogspot.com.au/2013/10/fix-data-htc-one.html
Just make sure where it says "mmcblk0p37" in step number 10, you put in "mmcblk0p23" which is your data partition, but i doubt you will have much access doing this.
Click to expand...
Click to collapse
Thanks but as I said, I can't use ADB on my computer. I'll still try when I can use an other one !
Hello,
first of all my idol has locked bootloader.
I just resized /data partition to 16GB, and it is working no problem, but I can not root it ( install supersu.zip).
After installing supersu.zip, on the /system partition are su binaries and SuperSu apk etc. so the zip file is flashed right way but, after rebooting the device I can reach the device only via adb shell, and do whatever, but It is not booting
Is there any special supersu.zip package for our device? or Do I need bootloader unlocked?
Thanks for help )
howpathetic said:
Hello,
first of all my idol has locked bootloader.
I just resized /data partition to 16GB, and it is working no problem, but I can not root it ( install supersu.zip).
After installing supersu.zip, on the /system partition are su binaries and SuperSu apk etc. so the zip file is flashed right way but, after rebooting the device I can reach the device only via adb shell, and do whatever, but It is not booting
Is there any special supersu.zip package for our device? or Do I need bootloader unlocked?
Thanks for help )
Click to expand...
Click to collapse
What is the problem with the supersu from the recovery? Why you don't use it ? No additional .zip .bin or other files are needed to root your phone. I have described already here how the prompt for the supersu installation can be seen if it has been discarded once. The bootloader is not necessary to be unlocked.
petrov.0 said:
What is the problem with the supersu from the recovery? Why you don't use it ? No additional .zip .bin or other files are needed to root your phone. I have described already here how the prompt for the supersu installation can be seen if it has been discarded once. The bootloader is not necessary to be unlocked.
Click to expand...
Click to collapse
I forgot to write it, but I tried the TWRP supersu as well, and it did nothing I tried it now again, removed .twrps, allowed modifications on /system, pressed reboot, system then it asked for installing supersu, so I swiped for install. It intalled and rebooted, after reboot there is not root nor supersu apk.
howpathetic said:
I forgot to write it, but I tried the TWRP supersu as well, and it did nothing I tried it now again, removed .twrps, allowed modifications on /system, pressed reboot, system then it asked for installing supersu, so I swiped for install. It intalled and rebooted, after reboot there is not root nor supersu apk.
Click to expand...
Click to collapse
I fully unrooted my device, and then rooted it again, just to see that it works. After the installation of supersu from the recovery, root access is not available right away. In the applications menu you must have SuperSU installer. Start it, and choose Play. It will open the play store. Choose Update and that's all.
When i install twrp supersu and then reboot to the system I really do not have anything related to supersu installed.... It seems like it is not mounting my /system as readwrite but i have set twrp to mount it as rw
I will try to dig some logs from recorvery
The logs are in /cache/recovery. Which recovery you use by the way?
petrov.0 said:
The logs are in /cache/recovery. Which recovery you use by the way?
Click to expand...
Click to collapse
I am using this one -> Recovery
howpathetic said:
I am using this one -> Recovery
Click to expand...
Click to collapse
What the logs say ? Can I see one ?
petrov.0 said:
What the logs say ? Can I see one ?
Click to expand...
Click to collapse
http://pastebin.com/dDt8hss1
I installed the supersu via twrp but nothing in log -.-
howpathetic said:
http://pastebin.com/dDt8hss1
I installed the supersu via twrp but nothing in log -.-
Click to expand...
Click to collapse
This is not the log from the installation. There should be others.
petrov.0 said:
This is not the log from the installation. There should be others.
Click to expand...
Click to collapse
There is the second one http://pastebin.com/PpHZ0HsF
mount: mounting /dev/block/mmcblk0p25 on /system failed: Device or resource busy
mount: mounting /dev/block/mmcblk0p37 on /data failed: Device or resource busy
howpathetic said:
There is the second one http://pastebin.com/PpHZ0HsF
mount: mounting /dev/block/mmcblk0p25 on /system failed: Device or resource busy
mount: mounting /dev/block/mmcblk0p37 on /data failed: Device or resource busy
Click to expand...
Click to collapse
These two lines are not a problem. The partitions are mounted already and that's why mount complains. After this, the script remounts them as rw (no complains from this, so the remount is successful). The rest looks OK, so the 'su' binary and the '.apk' should be installed. Can you list /system/xbin/ and /system/app/ through adb and also to execute cat /system/etc/install-recovery.sh
Sure,
http://pastebin.com/9xmQ8ppH
This script /system/etc/install-recovery.sh does not exist
howpathetic said:
Sure,
http://pastebin.com/9xmQ8ppH
This script /system/etc/install-recovery.sh does not exist
Click to expand...
Click to collapse
There is something unclean in your system path. These lines from your log
Code:
- Removing old files
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
indicate that you have either /system/etc/install-recovery.sh or /system/bin/install-recovery.sh, prior the start of the installation (there is no other way they to be shown). What else you've done with the phone ... except to resize the data partition ? Also you have saved settings and the recovery loads them at the start. Remove them all. Start with clean settings. But first check in which of these two paths is your install-recovery.sh and what's inside. If all this does not help, probably a manual installation can do it.
... and just before to send this I saw it ... what's wrong with your data partition ?!?
Code:
/data | /dev/block/mmcblk0p37 | Size: 12143MB Used: 2732MB Free: 4602MB Backup Size: 2732MB
mine looks like this resized
Code:
/data | /dev/block/mmcblk0p37 | Size: 12195MB Used: 2505MB Free: 9690MB Backup Size: 2505MB
So the main question is what exactly you did with the device ?
petrov.0 said:
There is something unclean in your system path. These lines from your log
Code:
- Removing old files
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
indicate that you have either /system/etc/install-recovery.sh or /system/bin/install-recovery.sh, prior the start of the installation (there is no other way they to be shown). What else you've done with the phone ... except to resize the data partition ? Also you have saved settings and the recovery loads them at the start. Remove them all. Start with clean settings. But first check in which of these two paths is your install-recovery.sh and what's inside. If all this does not help, probably a manual installation can do it.
... and just before to send this I saw it ... what's wrong with your data partition ?!?
Code:
/data | /dev/block/mmcblk0p37 | Size: 12143MB Used: 2732MB Free: 4602MB Backup Size: 2732MB
mine looks like this resized
Code:
/data | /dev/block/mmcblk0p37 | Size: 12195MB Used: 2505MB Free: 9690MB Backup Size: 2505MB
So the main question is what exactly you did with the device ?
Click to expand...
Click to collapse
I just resized the partition, tried to flash supersu from zip ( official ) and the twrp supersu thats all.
http://pastebin.com/6G75XVmQ
Should I remove it?
and I will check the data partition, I have everything backuped so I can revert, but I think i resized it well I will check.
EDIT:
I have it repartitioned good.
I printed list of partition and
37 5000400 30535546 12.2 GiB FFFF userdata
38 30535548 30535646 49.5 KiB 0700 userdatabak
Looks exactly same as you have in your topic.
It has to be false value read by twrp.
look
from mount command
/dev/block/mmcblk0p37 12435084 7722388 4696312 62% /sdcard
howpathetic said:
I just resized the partition, tried to flash supersu from zip ( official ) and the twrp supersu thats all.
http://pastebin.com/6G75XVmQ
Should I remove it?....
Click to expand...
Click to collapse
No, leave the file (for now). It will be moved by the install-supersu.sh script (obviously he doesn't do it for some reason at the moment). Let's assume that the repartitioning is okay. From where you have these /system/bin/install-recovery.sh and /system/recovery-from-boot.p ? You have some official update probably ? I don't have such files in my backup.
petrov.0 said:
No, leave the file (for now). It will be moved by the install-supersu.sh script (obviously he doesn't do it for some reason at the moment). Let's assume that the repartitioning is okay. From where you have these /system/bin/install-recovery.sh and /system/recovery-from-boot.p ? You have some official update probably ? I don't have such files in my backup.
Click to expand...
Click to collapse
I really do not know, I installed once update.. Now I have 5.0.2-010 02010 02 version. Btw. could you please help me on for example google hangouts? I will post solution here later.
Solved
We had to run e2fsck over /system partition.
/system partition was somehow corrupted
Hello,
I have rooted my pixel 3 by using Magisk,
my version is still Android pie,
it has successfully rooted but then when I type "adb root" it returns adbd cannot run as root in production builds,
I found out it might because I need to disable the verity, but when I type adb disable-verity it shows "verity cannot be disabled/enabled - USER build",
I have tried to follow the steps from https://android.stackexchange.com/q...dm-verity-on-android-with-user-build-type-rom but I don't quite understand how to do it,
I was wondering if anyone have more specific steps that will be able to disable the verity.
Thanks!
Skylar514 said:
Hello,
I have rooted my pixel 3 by using Magisk,
my version is still Android pie,
it has successfully rooted but then when I type "adb root" it returns adbd cannot run as root in production builds,
I found out it might because I need to disable the verity, but when I type adb disable-verity it shows "verity cannot be disabled/enabled - USER build",
I have tried to follow the steps from https://android.stackexchange.com/q...dm-verity-on-android-with-user-build-type-rom but I don't quite understand how to do it,
I was wondering if anyone have more specific steps that will be able to disable the verity.
Thanks!
Click to expand...
Click to collapse
In magisk advanced settings untick preserve adb verity and reinstall.
wangdaning said:
In magisk advanced settings untick preserve adb verity and reinstall.
Click to expand...
Click to collapse
Hello,
Thank you for your respond.
I have done that and it still doesnt let me disable the verity.
Is there any other way I can disable the verity?
Thanks!
Skylar514 said:
Hello,
Thank you for your respond.
I have done that and it still doesnt let me disable the verity.
Is there any other way I can disable the verity?
Thanks!
Click to expand...
Click to collapse
Use proton kernel!
pheco said:
Use proton kernel!
Click to expand...
Click to collapse
Hello,
I just installed the proton kernel,
and I checked my kernel version it is "Linux version 4.9.191-Proton-v19-g225054cc ([email protected]) (GCC 9.1.0) #20 SMP PREEMPT Sun Sep 8 21:50:57 PDT 2019",
but when I tried adb dm-verity it still shows verity cannot be disabled/enabled - USER build.
I was wondering if you have any idea?
Thank you.
I think you might have to do it to both slots. If it is still enabled on one of them I think it still checks.
Hello,
I upgrade my phone to android 10, and I can't flash the proton kernel,
I have done it to both slots and its still unable to disable.
Any idea?
Thank you!
Skylar514 said:
Hello,
I upgrade my phone to android 10, and I can't flash the proton kernel,
I have done it to both slots and its still unable to disable.
Any idea?
Thank you!
Click to expand...
Click to collapse
As far as I know you cannot do it in 10. I have never updated and tried, but that is what I have heard. There is no way to modify system except systemlessly with magisk modules. What exactly are you trying to do, might help get more suggestions if you tell us.
wangdaning said:
As far as I know you cannot do it in 10. I have never updated and tried, but that is what I have heard. There is no way to modify system except systemlessly with magisk modules. What exactly are you trying to do, might help get more suggestions if you tell us.
Click to expand...
Click to collapse
I am trying to run python script on the phone, so I have found this website https://medium.com/swlh/python-on-android-root-4aa56f22070a
and I was trying to follow the step to install python on the phone, but I am stuck at the adb remount command step.
It shows that I need to type adb root, but when I typed adb root it shows "adbd cannot run as root in production builds",
and I have try mount -o rw,remount /system, it gave me error "mount: '/system' not in /proc/mounts".
I checked mount and for some reason it shows system_root instead of system for "/sbin/.magisk/block/system_root on /sbin/.magisk/mirror/system_root type ext4 (ro,seclabel,relatime,block_validity,delalloc,barrier,user_xattr)", so I did some research and found out that I need to disable the verity, but when I tried to disable it it gave me the error which is "verity cannot be disabled/enabled - USER build".
Skylar514 said:
I am trying to run python script on the phone, so I have found this website https://medium.com/swlh/python-on-android-root-4aa56f22070a
and I was trying to follow the step to install python on the phone, but I am stuck at the adb remount command step.
It shows that I need to type adb root, but when I typed adb root it shows "adbd cannot run as root in production builds",
and I have try mount -o rw,remount /system, it gave me error "mount: '/system' not in /proc/mounts".
I checked mount and for some reason it shows system_root instead of system for "/sbin/.magisk/block/system_root on /sbin/.magisk/mirror/system_root type ext4 (ro,seclabel,relatime,block_validity,delalloc,barrier,user_xattr)", so I did some research and found out that I need to disable the verity, but when I tried to disable it it gave me the error which is "verity cannot be disabled/enabled - USER build".
Click to expand...
Click to collapse
System partition is under /system_root on Pie. I wonder if you could create a magisk module to install the app systemlessly.
wangdaning said:
System partition is under /system_root on Pie. I wonder if you could create a magisk module to install the app systemlessly.
Click to expand...
Click to collapse
Hi,
So now I am trying to unpack the boot.img file that I downloaded from google firmware website in order to try the method that provided by https://android.stackexchange.com/q...dm-verity-on-android-with-user-build-type-rom.
But I was wondering instead of editing boot.img, should I just edit the magisk_patched.img?
Thanks!
Skylar514 said:
Hi,
So now I am trying to unpack the boot.img file that I downloaded from google firmware website in order to try the method that provided by https://android.stackexchange.com/q...dm-verity-on-android-with-user-build-type-rom.
But I was wondering instead of editing boot.img, should I just edit the magisk_patched.img?
Thanks!
Click to expand...
Click to collapse
You are going to need root so better to modify the magisk boot image.
wangdaning said:
You are going to need root so better to modify the magisk boot image.
Click to expand...
Click to collapse
Hello,
Thank you for your respond!
Do I need to modify boot.img as well?
Or just the magisk_patched.img?
Thank you!
I think there is a way to disable verity before installing the magisk boot img, but you would have to look at the magisk github information.
Sounds good!
Thanks for your advice!
Beside that I was wondering if you know that is there anyway we can access the battery data through abd command?
I know that we can gather cpu frequency info, but I am not sure if we can get the battery data as well.
Thanks in advance!
Maybe check this thread about battery
https://forum.xda-developers.com/pixel-3-xl/themes/looking-mod-to-make-battery-indicator-t3913080
Here's where I'm at. I've got the system to give me the Mount /System option in recovery, now i just need assistance getting the build.prop pulled to my PC. What's the procedure for pulling the build.prop from the Android to PC via ADB while the system is mounted in recovery? Why am I getting one of these two ADB errors?
Error 1: Connect failed: closed.
error 2: Failed to get feature set: no devices or emulators
OR, am I approaching it wrong?
Thanks in advance,
K0mraid3
you dont need to be in recovery to do it via adb....
adb pull /system/build.prop
that will pull it to where evr you run the adb command
which would be
C;\adb more than likely
or you can choose a destination with
adb pull /system/build.prop c:\buildprop
if you create a folder called "buildprop" in the root directory of c:\
at least thats how i remember doing it many years ago, ive been away for a while at her majesties pleasure, so i cant try it currently as im not rooted
gav83collins said:
you dont need to be in recovery to do it via adb....
adb pull /system/build.prop
that will pull it to where evr you run the adb command
which would be
C;\adb more than likely
or you can choose a destination with
adb pull /system/build.prop c:\buildprop
if you create a folder called "buildprop" in the root directory of c:\
at least thats how i remember doing it many years ago, ive been away for a while at her majesties pleasure, so i cant try it currently as im not rooted
Click to expand...
Click to collapse
Thanks, so far, its still for some reason denying me permission when OS is booted. So i just cant quite figure out where im supposed to execute these commands, is my issue. I can boot directly to BL from recovery menu, but i can also mount system. i think maybe i need sto send command for r/w.. will try that now.
Another question, when i mount /system in recovery, does that carry over on boot?
no you can re mount system via adb though
Code:
$ adb shell
$ su
# mount -o rw,remount /system
gav83collins said:
no you can re mount system via adb though
Code:
$ adb shell
$ su
# mount -o rw,remount /system
Click to expand...
Click to collapse
1.Needs root for this command. If he have rooted device then why so much trouble needed. Simply use root explorer to copy
2.Since long Samsung have removed system from proc/mounts still magisk system_root can be used
3.Even with system in mounts you can't do system rw on S22 because of Samsung have implemented extra layer of protection. Even not with magisk system_root too
Indeed as of now there is no method available to make stock system/vendor/product/odm rw on S22 even with root access.
4.To copy file from system rw mount not needed, ro is fine
dr.ketan said:
1.Needs root for this command. If he have rooted device then why so much trouble needed. Simply use root explorer to copy
2.Since long Samsung have removed system from proc/mounts still magisk system_root can be used
3.Even with system in mounts you can't do system rw on S22 because of Samsung have implemented extra layer of protection. Even not with magisk system_root too
Indeed as of now there is no method available to make stock system/vendor/product/odm rw on S22 even with root access.
4.To copy file from system rw mount not needed, ro is fine
Click to expand...
Click to collapse
im yet to root my device so i cant test but what about
Code:
adb root
adb disable-verity
adb reboot
Then
Code:
adb root
adb remount
gav83collins said:
im yet to root my device so i cant test but what about
Code:
adb root
adb disable-verity
adb reboot
Then
Code:
adb root
adb remount
Click to expand...
Click to collapse
Do you got what I meant?
leave it.
dr.ketan said:
WTF
Do you got what I meant?
leave it.
Click to expand...
Click to collapse
look, there is no need for condescension and bad language, a simple "no" would have sufficed
Lol not meant to hurt you! but on which planet WTF is bad language
Here search WTF on xda
dr.ketan said:
1.Needs root for this command. If he have rooted device then why so much trouble needed. Simply use root explorer to copy
2.Since long Samsung have removed system from proc/mounts still magisk system_root can be used
3.Even with system in mounts you can't do system rw on S22 because of Samsung have implemented extra layer of protection. Even not with magisk system_root too
Indeed as of now there is no method available to make stock system/vendor/product/odm rw on S22 even with root access.
4.To copy file from system rw mount not needed, ro is fine
Click to expand...
Click to collapse
So my device is strange. It doesn't have root, but it indeed shows options in recovery to apply updates from ADB, SD Card aswell as boot directly to BL and to Mount /System, but when I'm booted, the OS is denying me permission to "Su" . I have verified that USB debugging is activated. So I'm trying to see if there's a way to pull the build.prop from Recovery since the Mount /System option is available, but my computer refuses to recognize the device in while in recovery, but easily finds it in Download, BL mode. No FRP lock. No accounts on device. But also no option to unlock bootloader. This device in particular is/was a development sample so I have no clue what the current state of the bootloader etc is in terms of being unlocked prior to me working on it.
It'd also worth noting that this device was loaded with Android 11 when I received it. I'm not kidding. So idk what's going on with this FrankenGalaxy
K0mraid3 said:
It'd also worth noting that this device was loaded with Android 11 when I received it. I'm not kidding. So idk what's going on with this FrankenGalaxy
Click to expand...
Click to collapse
K0mraid3 said:
So my device is strange. It doesn't have root, but it indeed shows options in recovery to apply updates from ADB, SD Card aswell as boot directly to BL and to Mount /System, but when I'm booted, the OS is denying me permission to "Su" . I have verified that USB debugging is activated. So I'm trying to see if there's a way to pull the build.prop from Recovery since the Mount /System option is available, but my computer refuses to recognize the device in while in recovery, but easily finds it in Download, BL mode. No FRP lock. No accounts on device. But also no option to unlock bootloader. This device in particular is/was a development sample so I have no clue what the current state of the bootloader etc is in terms of being unlocked prior to me working on it.
Click to expand...
Click to collapse
These options are normal in stock recovery and can be used only for flashing official zip (OTA), To have root access on your recovery, you needs custom one (TWRP) which is in development stage on S22
Without twrp, You needs to root device (must have oem unlock option in development option) to access system files while you are booted to android.
Android 11 on S22? Can you show me screenshot of settings - about phone - software info?
dr.ketan said:
These options are normal in stock recovery and can be used only for flashing official zip (OTA), To have root access on your recovery, you needs custom one (TWRP) which is in development stage on S22
Without twrp, You needs to root device (must have oem unlock option in development option) to access system files while you are booted to android.
Android 11 on S22? Can you show me screenshot of settings - about phone - software info?
Click to expand...
Click to collapse
Thanks for the clear answer, that's kind of what I'm working on is trying to gain root access, but like you said, I need oem unlocking, which isn't on this device. So I'm trying to find a backdoor/vulnerability that will take me even one step closer to atleast finding a way to set ro.secure. prop. Something VERY interesting I did find, is that if you put the device to Debug medium or high via device keystring activity, and play with the key combos, you can get booted into a mode called RDX, if you plug it into your dev system with the right drivers, it's treats the phone as if it were a Disk and shows a bunch of VZW upgrade software ment for PCs. I've installed it but haven't got it working quite yett.
No idea what you have shown in screenshot, I'd asked something else.
dr.ketan said:
No idea what you have shown in screenshot, I'd asked something else.
Click to expand...
Click to collapse
Maybe Heindall will give me better results. I just refuse to believe the manufacturers have outsmarted us all on this.
in TRWP also i cant mount Data so i cant flash any SystemRW script.
i tried a script to flash and after that could change only permissions of folders or files, but dont open them (says is read only)
i used several explorers. Also any root apps trying changing build prop come up with a failure.
But i have root access.
i used the script from here Link but it came up with try manuallayy flash via TWRP...but TRWP cant mount Data...
AiTakako said:
in TRWP also i cant mount Data so i cant flash any SystemRW script.
i tried a script to flash and after that could change only permissions of folders or files, but dont open them (says is read only)
i used several explorers. Also any root apps trying changing build prop come up with a failure.
But i have root access.
i used the script from here Link but it came up with try manuallayy flash via TWRP...but TRWP cant mount Data...
Click to expand...
Click to collapse
Flash the script via adb command under TWRP or use microSD card or USBOTG.
pl1992aw said:
Flash the script via adb command under TWRP or use microSD card or USBOthx
Click to expand...
Click to collapse
thx i tried but apsways say cant mount data
AiTakako said:
in TRWP also i cant mount Data so i cant flash any SystemRW script.
i tried a script to flash and after that could change only permissions of folders or files, but dont open them (says is read only)
i used several explorers. Also any root apps trying changing build prop come up with a failure.
But i have root access.
i used the script from here Link but it came up with try manuallayy flash via TWRP...but TRWP cant mount Data...
Click to expand...
Click to collapse
you need to modify the flashable zip to be compatibe to android 12 and you may use a beta version of orangefox for data partition to be mounted and decrypted