mount:failed to mount /dev/block/bootdevice/by- name/system at /system: device or resource busy.
..,
please help
We don't support your device, go to the YU forum
Related
Hi,
I've built a ROM from source for my device but when I flash it on my device, it says:
Code:
blkdiscard failed: Invalid argument
E: Error /stoage.../RR.zip (Status 7)
How should I fix it?
Hi there,
You can start from reading this guide for beginner: [GUIDE]**Beginners guide to programming-C,C++,Bash,Python,java**[GUIDE], or ask your question in the general forum related to your concern:
> Android Development and Hacking > Android Software Development
Good luck
Hello everyone !
I am new to the world of Android (former Windows Phone user) and begin to explore the ins and outs of this marvelous device
I got a OnePlus X recently and decided to root it.
I Installed TWRP for recovery 2.8.7.0 [1] and installed SuperSU and it worked like a charm.
I then crypted the device and began to have fun w/ it !
Now, the new version of OxygenOS (2.1.3 with SD Card support!) is out and I would like to upgrade my phone. But My instance of TWRP does not support encryption[2]. TWRP (j50036 indeed) released a patch for it but it is not yet implemented for OnePlus X obviously.
Code:
~ # twrp decrypt 002932839239230
Attempting to decrypt data partition via command line.
E:No crypto support was compiled into this build.
I tried to install it through ADB side load without success, and via TWRP without data.
Code:
~ # twrp install /external_sd/uc.zip
E:Unable to mount '/data'
command is: 'decrypt' and there is no value
E:No password provided.
Done processing script file
Can someone explain me how to upgrade my firmware ? Or is it possible to rebuild TWRP for OnePlus X ? I don't have enough posts to get into these dev topics...
Thank you !
[1]: http://forum.xda-developers.com/one...ry-twrp-2-8-7-0-touch-recovery-t3252840/page1
[2] : http://forum.xda-developers.com/shi...recovery-twrp-2-8-7-0-touch-recovery-t3257172
I flash android 12 beta Google gsi from the link below, I flashed it with twrp and I am facing bootloop in my z2 plus, any solution??
Generic System Image releases | Android Developers
Generic System Image releases | Platform | Android Developers
developer.android.com
I flashed the arm64
Exactly same problem here. If you find a solution please please please give a message on [email protected]
I am busy in fixing my sim card not working
If you flash a GSI image ( read: Vanilla ROM - AOSP ) then Android's OEM-created /vendor & /modem partitions gets lost. Probably /esf partition, too.
Hence you must not be surprised that phone is bootlooping
jwoegerbauer said:
If you flash a GSI image ( read: Vanilla ROM - AOSP ) then Android's OEM-created /vendor & /modem partitions gets lost. Probably /esf partition, too.
Hence you must not be surprised that phone is bootloop
Click to expand...
Click to collapse
jwoegerbauer said:
If you flash a GSI image ( read: Vanilla ROM - AOSP ) then Android's OEM-created /vendor & /modem partitions gets lost. Probably /esf partition, too.
Hence you must not be surprised that phone is bootlooping
Click to expand...
Click to collapse
This shouldn't be the case because earlier I have formatted my device using so flash tool. Each and every system partition got lost including efs(nvdata and nvram in my case). I actually found another reason: Kernel is 32 bit which doesn't support 64 bit gsi. I tried finding a 64 bit firmware for my device but there's none.
Hi,
I wanted to root my samsung galaxy a20s (NOT A20) but there is almost no info about my model (there is other that i am not very optimistic about.)
There is a twrp (https://twrp.me/samsung/samsunggalaxya20s.html) but it says something about that the system uses system-as-root in the A-only partition configuration and that it is problematic and i should install magisk first then preroot a twrp, I have absolutelly no idea.
Can someone explain what i should do?
Thanks, have a nice day.
A phone's Android OS is rooted when SU binary is present in Android's filesystem and is made executable.
Disclaimer: I'm not responsible for any result of these operations. Please be careful and well prepared. Always have your important data backed up safely on other place.
Hello everyone!
As far as 2022 and Xiaomi gets their new phones updated to MIUI13 and Android 12, they implement the new read-only filesystem "EROFS" on the logical partitions inside super partition. EROFS is a filesystem initial developed by Huawei and then Google select it as a new standard to use in read only logical partition inside super partition from Android 12. The "EROFS", is the short for "Extendable (or Enhanced?) Read-Only Filesystem", conveying that this filesystem is a one-time cooked filesystem and cannot be changed without extracting and re-cooking. With erofs we cannot modify the logical partition anymore so I found a new way to unlock these partitions.
I just faced and managed to solve the "lock" and I would like to share the solution, which may help more people.
My device: Xiaomi 12 (cupid).
System: Stock MIUI13 (Android 12).
Logical partitions with read-only lock inside super partition: system, vendor, product, system_ext, odm, vendor_dlkm. All of them are erofs filesystem.
Before we start: This guide is for power users that wish to make their read-only system/vendor.... partitions with EROFS filesystem inside super read-writeable again to remove the bloatware and do more customizations to their device.
Credits:
@Yuki1001 - EROFS Guide, research, new rw discoveries.
@lebigmac - a couple of rw slogans, some binaries, inspiration.
Requirements:
1. Your phone must be unlocked as you must flash your new super.img through fastboot command. Root is required to run any command in adb shell or a terminal.
2. 20GB+ free space on your phone and PC.
3. The toolkit needed.
4. A clever brain and courage.
Steps in short:
(1) Dump and extract your super image.
(2) Pull the folder with partition images extracted from super image to the PC.
(3) Convert these erofs images to ext4 images (Extract and Rebuild). These new images are in the same folder.
(4) Push the folder to the phone and fix any errors of new generated ext4 images.
(5) Merge them into a new single sparse super image and pull it to the PC.
(6) Flash the new image through fastboot command.
(7) Check the rw capability of the logical partitions and do anything you want!
View my full guide here: https://forum.xda-developers.com/t/...ons-inside-super-read-writable-again.4483933/
For mods: In theory, this method is universal over all new Android12+ phones shipped with partitions using erofs inside super. So I post the content in the general android software/hacking subforum. In this subforum I preserve a thread hoping more users can see it and be benefited.
Feedbacks are always welcome!
If you think it's useful, please click the "Like" button. Thanks!
Reserved floor #2.
Reserved floor #3.
Hi Yuki. You did some great erofs research there. Congratulations! Keep up the good work!
And thanks for adding me to your credits!
If you want to integrate your erofs discoveries into new version of my script please contact me! Thanks! Of course you would be properly credited
lebigmac said:
Hi Yuki. You did some great erofs research there. Congratulations! Keep up the good work!
And thanks for adding me to your credits!
If you want to integrate your erofs discoveries into new version of my script please contact me! Thanks! Of course you would be properly credited
Click to expand...
Click to collapse
You both can kill erofs