yashsingh1/xdaforums huggingface dataset:
[Motorola Edge 20 Pro] Harry Haller:
Hello, how can I decompile the rom of this Motorola to delete pre-installed applications, what programs are used?
[Windows Mobile Development and Hacking General] vberruyer:
I need some help to understand the way Microsoft is numbering Windows Mobile 6.1.

We usually see for WM6.1 numbers like for exemple OS 5.2.19971 B.19971.1.2.6.

5.2 seems to be some sort of internal and official version number for wm6.1 and 19971 to be the build number.

Then there is an obscur 1.2.6 (is it a sub-build number ?).

Moreover regarding the HyperDragon Roms each new version does not always follow a growing build number (from Oct. 22th the wm6.1 base build numbers were in the order 19581.1.1.1, 19212.1.0.3, 20757.1.4.0, 19974.1.2.8, 19974.1.2.8 and then now 19971.1.2.6 :confused:

I understand the HyperDragon Rom depend of the initial phone extract (blackstone, jade, opal...) but how to choose the best one ?

Last question, I'm looking for the Windows Mobile 6.1.4 version because it is supposed to solve a big issue regarding the SMTP use in Pocket Outlook :D. But how to recognize a 6.1.4 version (base on a particular build or other usual numbering).

Thanks for your great help.
[Realme X7 Max 5G] Ritesh varshu:
I need a perfect Gcam for my realme X7 max
[Android Q&A, Help & Troubleshooting] Esgrimidor:
I don't want data connection in my mobile.

Contstantly the operating system ask me with two buttons if I wish data connection. I don't want data connection.

How can I avoid these messages.

I only want to connect via wifi.

i have deactivated the internet connection via paid data.

But The system ask me for a connection I don't want. And is easy to miss in the action inadvertedly.

How can I be free ?

Best Regards
[Android Q&A, Help & Troubleshooting] Oswald Boelcke:
@Esgrimidor

Prior to your next posting please read the guidances that are stuck on top of every forum like

Note: Questions go in Q&A Forum

If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...

xdaforums.com

and the others. I've moved the thread to Android Q&A.

Thanks for your cooperation!

Regards

Oswald Boelcke

Senior Moderator
[Android Q&A, Help & Troubleshooting] Esgrimidor:
Thanks moderator. Now I hope I receive an answer is possible. Best regards.
[Wear OS Q&A, Help & Troubleshooting] ophiry:
Preferably am so that allows syncing listening status with the phone
[General Questions and Answers] alecxs:
README.md

## Flash in Magisk Manager ONLY
[General Questions and Answers] fermi6-626:
It was an example. I flashed self-modified nethunter kernel twrp-only flashable zip. and the errors are the same. the flashing shows successful, then those errors pop up. device boots up normally, and kernel shows "4.14.186-nethunter". i am worried if the flashing didn't correctly succeed.
[General Questions and Answers] alecxs:
So what's the question here? You don't know what the error means?

LOGERR("Unable to unlock %s for flashing: %s\n", block_device.c_str());

Does your device have mmcblk0 emmc flash memory at all, sure it's not your MicroSD Card?

MediaTek Helio G80 (MT6769V/CU) looks like support both eMMC 5.1 and UFS 2.1

https://www.gsmarena.com/compare.php3?&idPhone1=10996&idPhone2=10948&idPhone3=10429
[General Questions and Answers] fermi6-626:
the question is the flashing shows successful when there are errors. what does the error mean and did my kernel install correctly?
[General Questions and Answers] alecxs:
you are the creator of that flashable zip, only you can know what you're doing.

all I can see from the incomplete log you provided you're trying to install v4afx_v2.7.2.1.zip from TWRP regardless it must flashed from Magisk. you said this is just example, so I am not spending time in analyzing v4afx_v2.7.2.1.zip and figuring out what it does.

if you get similar error about Unable to unlock mmcblk0 for flashing for each and every flashable zip, it's probably not an issue with the zip itself.

the error means some operation was unable to unlock partition for flashing. it's lacking context, so you should provide recovery.log at least
[General Questions and Answers] fermi6-626:
twrp log and dmesg log
[General Questions and Answers] alecxs:
regarding kernel:

that one failed, probably because (1) device is dynamic partitions read-only, or (2) script is not handling /system_root/system correctly

- Target Image: /dev/block/mmcblk0p36
- Copying firmware to /system/etc/firmware

that part succeed, unrelated to the below error messages

- Flashed new bootimage
- Boot image patching complete

This looks like a bug in TWRP, please claim it to TWRP maintainer, or just ignore it

E:Unable to unlock /dev/block/mmcblk0p42 for flashing: (null)
[General Questions and Answers] fermi6-626:
---Magisk Logs---
24.3 (24300)

05-23 09:38:42.264 602 602 I : Magisk 24.3(24300) daemon started
05-23 09:38:42.265 602 602 I : * Device API level: 30
05-23 09:38:42.275 602 604 I : ** post-fs-data mode running
05-23 09:38:42.275 602 604 E : unlock mmcblk0p42 failed with 13: Permission denied
05-23 09:38:42.276 602 604 E : unlock mmcblk0p11 failed with 13: Permission denied
05-23 09:38:42.276 602 604 E : unlock mmcblk0p4 failed with 13: Permission denied
05-23 09:38:42.277 602 604 E : unlock mmcblk0p18 failed with 13: Permission denied
05-23 09:38:42.277 602 604 E : unlock mmcblk0p6 failed with 13: Permission denied
05-23 09:38:42.278 602 604 E : unlock mmcblk0boot0 failed with 13: Permission denied
05-23 09:38:42.278 602 604 E : unlock mmcblk0p15 failed with 13: Permission denied
05-23 09:38:42.279 602 604 E : unlock mmcblk0p5 failed with 13: Permission denied
05-23 09:38:42.279 602 604 E : unlock mmcblk0p7 failed with 13: Permission denied
05-23 09:38:42.279 602 604 E : unlock mmcblk0p14 failed with 13: Permission denied
05-23 09:38:42.279 602 604 E : unlock mmcblk0p10 failed with 13: Permission denied
05-23 09:38:42.280 602 604 E : unlock mmcblk0p8 failed with 13: Permission denied
05-23 09:38:42.280 602 604 E : unlock mmcblk0p13 failed with 13: Permission denied
05-23 09:38:42.286 602 604 E : unlock mmcblk0 failed with 13: Permission denied
05-23 09:38:42.292 602 604 E : unlock mmcblk0p12 failed with 13: Permission denied
05-23 09:38:42.292 602 604 E : unlock mmcblk0p9 failed with 13: Permission denied
05-23 09:38:42.297 602 604 I : * Mounting mirrors
05-23 09:38:42.297 602 604 I : link: /dev/hmrL/.magisk/mirror/metadata
05-23 09:38:42.297 602 604 I : mount: /dev/hmrL/.magisk/mirror/vendor
05-23 09:38:42.297 602 604 I : mount: /dev/hmrL/.magisk/mirror/product
05-23 09:38:42.297 602 604 I : link: /dev/hmrL/.magisk/mirror/cache
05-23 09:38:42.297 602 604 I : mount: /dev/hmrL/.magisk/mirror/data
05-23 09:38:42.297 602 604 I : link: /dev/hmrL/.magisk/mirror/system
05-23 09:38:42.297 602 604 I : mount: /dev/hmrL/.magisk/mirror/system_root
05-23 09:38:42.297 602 604 I : link: /dev/hmrL/.magisk/mirror/system_ext
05-23 09:38:42.297 602 604 I : * Initializing Magisk environment
05-23 09:38:42.350 602 604 I : * Running post-fs-data.d scripts
05-23 09:38:42.353 602 604 I : * Running module post-fs-data scripts
05-23 09:38:42.353 602 604 I : * Loading modules
05-23 15:23:43.917 602 604 I : ** late_start service mode running
05-23 15:23:43.917 602 604 I : * Running service.d scripts
05-23 15:23:43.917 602 604 I : * Running module service scripts
05-23 15:24:05.509 602 604 I : ** boot_complete triggered

---Manager Logs---
24.3 (24300)
[General Questions and Answers] fermi6-626:
During flahing of magisk.zip in twrp it showed same errors but magisk is installed successfully. If it's a bug in twrp, do i need to worry about it?

twrp maintainer is not responding
[General Questions and Answers] fermi6-626:
please take a look if you want full log. Thank you
[General Questions and Answers] fermi6-626:
this is the kernel i've managed to flash successfully but with errors demonstrated above, which is completely out of my comprehension. Can you check it for errors? any help will be greatly appreciated.
[General Questions and Answers] alecxs:
that error is in Magisk for same partitions as in TWRP, therefore it's not a bug in TWRP. maybe it's not even an error at all, can be ignored

E : unlock mmcblk0p42 failed with 13: Permission denied
E : unlock mmcblk0p11 failed with 13: Permission denied
E : unlock mmcblk0p4 failed with 13: Permission denied
E : unlock mmcblk0p18 failed with 13: Permission denied
E : unlock mmcblk0p6 failed with 13: Permission denied
E : unlock mmcblk0boot0 failed with 13: Permission denied
E : unlock mmcblk0p15 failed with 13: Permission denied
E : unlock mmcblk0p5 failed with 13: Permission denied
E : unlock mmcblk0p7 failed with 13: Permission denied
E : unlock mmcblk0p14 failed with 13: Permission denied
E : unlock mmcblk0p10 failed with 13: Permission denied
E : unlock mmcblk0p8 failed with 13: Permission denied
E : unlock mmcblk0p13 failed with 13: Permission denied
E : unlock mmcblk0 failed with 13: Permission denied
E : unlock mmcblk0p12 failed with 13: Permission denied
E : unlock mmcblk0p9 failed with 13: Permission denied
[General Questions and Answers] alecxs:
regarding /system/etc/firmware

you are using anykernel wrong, I think it should be $SYSTEM/etc/firmware at least (not sure about the read-only ext4-dedup/logical partitions, though)

maybe @osm0sis will help you out

edit: unrelated to anykernel
[General Questions and Answers] fermi6-626:
Because I don't know how to use it. I left it the way it was modified by nethunter-kernel-builder. May be it is a samsung device's problem? If so how do I mount them as read/write? Or mount symlinks etc, like magisk did?

Sorry for asking stupid question, but I saw that the /system/etc/firmware from the zip is being copied to $SYSTEM/etc/firmware to the phone which was given variable as /system. Isn't that what you mean?

There are another errors:

cp: can't create '/system/etc/firmware/*': No space left on device
cp: can't create '/system_root/init.nethunter.rc': Read-only file system
grep: /system_root/init.rc: No such file or directory
sed: /system_root/init.rc: No such file or directory
chown: /tmp/nethunter/boot-patcher/ramdisk/*: No such file or directory
find: /tmp/nethunter/boot-patcher/ramdisk/*: No such file or directory

Thanks for the help!
[General Questions and Answers] alecxs:
in case there exist /system symlink, bind mount might fail. you could rename it by adding setup_mountpoint above this line (it probably would also work if set SYSTEM=/system_root/system, not quite sure what's intended for that variable)

setup_mountpoint /system;
$BB mount -o bind /system_root$system /system;

for rw access you need TWRP with dynamic partitions support. or re-create super.img with this script

https://xdaforums.com/t/script-andr...w-superrw-featuring-makerw-read-write.4247311
[General Questions and Answers] fermi6-626:
There are 3 update-binary files. Not sure which one to edit. and I checked all three but didn't find that exact line.

update-binary files

But i found these lines. Should i edit like this?:

if is_mounted /system_root; then
mount_apex;
if [ -f /system_root/build.prop ]; then
$BB mount -o bind /system_root /system;
else
setup_mountpoint /system;
$BB mount -o bind /system_root/system /system;
fi;
fi;

Thanks!
[General Questions and Answers] alecxs:
No clue what this warning means

[ 140.819754] (0)[460:recovery]Start 0x6000 of disk mmcblk0 not write group aligned
[ 140.819794] (0)[460:recovery]End 0x6000 of disk mmcblk0 not write group aligned
[ 140.820304] (0)[460:recovery]0x140000 ~ 0x144000 of mmcblk0 is partially write protected

might be related to that

[ 140.467184] (1)[278:teegris rpmb]TZDEV ERR tzdev_teec_connect(60): Failed to connect to root_task socket after 20 retries
[ 140.467211] (1)[278:teegris rpmb]TZDEV ERR TEEC_InitializeContext(208): Failed to connect to root task, context = 0000000000000000 ret = -111

my guess these are only QSEE related partitions somehow protected by kernel. you can check partition names by resolving the by-name symlinks.

ls -l $(find /dev/block -name by-name)/*
[General Questions and Answers] fermi6-626:
Thanks @aIecxs, i think these errors aren't in the way of flashing, because i flashed magisk successfully(working!) despite of the same errors. My main concern is getting the problem you stated fixed, that is, /system/etc/firmware isn't getting copied, /system_root being Read-only file system

cp: can't create directory '/system_root/sbin': Read-only file system
find: ak_patches/: No such file or directory

Please look at my latest recovery.log. It maybe different and provide hints.

Thanks!
[General Questions and Answers] fermi6-626:
Regardless how the flashing went, The kernel seems to be installed. Because I checked that the Stock kernel doesn't support either NFS Client or nfs-kernel-server, and HID interfaces. Another noticeable change was, before flashing my kernel, I could not set my SELinux to permissive(I did not modify this intentionally, I followed a documentation.)

After i installed the kernel, Both of them are working without problems. SELinux is now modifiable.

After each reboot, I get notification:

Android System

There's an internal problem with your device. Contact your manufacturer for details.
[General Questions and Answers] alecxs:
kernel issue. same for mmcblk0 is partially write protected

I don't know what this installer tries to modify on /system on systemless-root, but script is buggy
[General Questions and Answers] fermi6-626:
I'm sorry, I didn't quite understand what you mean. Aren't those logs and kernel.zip sufficient? Do you require any other logs or files?

Despite the kernel issue, why is everything including the changes i made in the kernel is working normally?

Please explain what you meant at your convenience. Thanks!
[General Questions and Answers] alecxs:
your dmesg is sufficient log. it shows some errors caused by kernel (post #18)

you could flash stock ROM and see if the errors are gone.
[General Questions and Answers] fermi6-626:
That log was after the error during flashing, E:Unable to unlock /dev/block/mmcblk0 for flashing: (null).

This is the dmesg with modified kernel generated from TWRP without flashing anything and with everything in the TWRP options mounted.

There aren't any error which were in the previous dmesg log

Will there be any problems like unexpected behavior, heating, malfunction... if i keep this kernel installed in the long run? If there's no problem at all, i'd like to leave it as it is, and come back later.
[General Questions and Answers] jprimero15:
I have the same problem on my twrp build with using prebuilt kernel,any possible fix for this ??
[General Questions and Answers] fermi6-626:
If you're talking about the E:Unable to unlock /dev/block/mmcblk0 for flashing: (null) error

I don't find it getting in the way of flashing, the installation is successful regardless of the error. We will probably find some fix for this in XDA someday.
[General Questions and Answers] Zillion:
Got the same issue on Galaxy A31

Galaxy-MT6768/teamwin_device_samsung_a31

A device tree to compile custom recoveries for SM-A315G, SM-A315F & SM-A315N - Samsung Galaxy A31 - Galaxy-MT6768/teamwin_device_samsung_a31

github.com
[General Questions and Answers] alecxs:
I don't own this device, can you provide partition names (post #18)
[General Questions and Answers] Zillion:
Got no partition names as my fstab uses /dev/block/by-name/ and not /dev/block/
[General Questions and Answers] alecxs:
so ls -l did not work for you?
[General Questions and Answers] Zillion:
Ok looks like now it worked - https://pastebin.com/9kAKwDx9
[General Questions and Answers] alecxs:
Figures it's Mediatek SoC lol.. so most of that are Mediatek Secure Boot related partitions. I think Samsung has protected it with TEEGRIS

E : unlock mmcblk0p42 (uh) failed with 13: Permission denied
E : unlock mmcblk0p11 (nvdata) failed with 13: Permission denied
E : unlock mmcblk0p4 (sec_efs) failed with 13: Permission denied
E : unlock mmcblk0p18 (misc) failed with 13: Permission denied
E : unlock mmcblk0p6 (param) failed with 13: Permission denied
E : unlock mmcblk0boot0 (preloader_a) failed with 13: Permission denied
E : unlock mmcblk0p15 (seccfg) failed with 13: Permission denied
E : unlock mmcblk0p5 (bota) failed with 13: Permission denied
E : unlock mmcblk0p7 (up_param) failed with 13: Permission denied
E : unlock mmcblk0p14 (protect2) failed with 13: Permission denied
E : unlock mmcblk0p10 (nvcfg) failed with 13: Permission denied
E : unlock mmcblk0p8 (expdb) failed with 13: Permission denied
E : unlock mmcblk0p13 (protect1) failed with 13: Permission denied
E : unlock mmcblk0p12 (metadata) failed with 13: Permission denied
E : unlock mmcblk0p9 (frp) failed with 13: Permission denied
[General Questions and Answers] ansh_/:
Do you know a way to unlock these partitions for mediatek device so that i can flash something using twrp we have been trying to fix
[General Questions and Answers] Zillion:
Could someone send a logcat and look for avc denials where permissive=0?
[General Questions and Answers] tumesson:
Hi, is there a solution to this problem? For my phone Samsung A22 brought a new TWRP where this error is present, I successfully flashed Magisk with this error, but I can not get NicGapps, the error is the same, but it is not installed.
[Redmi Note 11 Pro+ 5G (peux)/POCO X4 Pro 5G (veux)] Silent14725:
Hi, everyone I'm looking for persist.img for the redmi note 11 pro 5G global.

Virtual proximity sensor stopped working after the custom rom installation
[Redmi Note 11 Pro+ 5G (peux)/POCO X4 Pro 5G (veux)] liggerz87:
I have the phone I'm in uk how would I go about getting that image for you I'm not rooted or anything I could get the android update version download to phone and upload that for you if that would help
[Redmi Note 11 Pro+ 5G (peux)/POCO X4 Pro 5G (veux)] Silent14725:
Thank you for replying, yes it will be great if you that actually I have flashed custom rom by fastboot method and unfortunately the persist.img is corrupted by that. Let me know if you can.
[Redmi Note 11 Pro+ 5G (peux)/POCO X4 Pro 5G (veux)] Silent14725:
You can give it a try I have downloaded the latest stock rom and recovery both yet the persist.img was missing in both roms.
[Redmi Note 11 Pro+ 5G (peux)/POCO X4 Pro 5G (veux)] liggerz87:
I just downloaded straight from my phone not sure if it will help you
[Wing, P4350 Herald Upgrading] kizzyg:
when i restart phone it says smart mobility and wont go past that screen.

when i enter bootloader it says IPL 4.26.0002

spl 4.7 yang

started with touchflo 7.3

then tried to flash touch it final

let me know if any other info is needed and i will try to find it
[Wing, P4350 Herald Upgrading] zeheres:
Have you already tried installing another ROM? That might solve your problem.

Cheers.
[Wing, P4350 Herald Upgrading] kizzyg:
i am unsure of how to install another rom, the activesync cannot connect

so the installers cannot connect to my phone.
[Wing, P4350 Herald Upgrading] akademik_acheeba:
are you using vista or xp?
[Android Head-Units] Magus17:
I'm trying to figure out how to dual boot my rooted Atoto s8 ultra plus gen 2 head unit, any advice?
[Redmi Note 9 Questions & Answers] NOSS8:
there are not several models with the code name merlin, redmi note 9 or redmi 10x.

The x surely refers to the redmi 10x.
[Redmi Note 9 Questions & Answers] shadowstep:
THREAD LOCKED

As per the Forum Rules:

For continuing discussion, kindly use the original thread that you created: https://xdaforums.com/t/i-want-to-i...am-unsure-if-this-is-the-correct-rom.4448177/

Regards,

shadowstep

Forum Moderator
[Redmi Note 8 Questions & Answers] Rocker_2102:
Redmi note 8 (unlocked bootloader) stuck on "Your system has been destroyed" (I was trying to install PixelExperience 12, but was not able to boot into the PitchBlack recovery itself). Unable to boot to recovery or fastboot (no button combination is working).

If connected via USB (while just charging too), it just keeps rebooting & shows "Your system has been destroyed".

When disconnected from external power supply, it shuts down automatically after a few seconds, but when I try to boot into the bootloader (or try to turn it on), it again goes to the system destroyed screen.

Here are the set of commands I ran just after unlocking the bootloader:

PS D:\Android\ADB> ./fastboot flash recovery ginkgo_recovery.img

Sending 'recovery' (65536 KB) OKAY [ 1.404s]

Writing 'recovery' OKAY [ 0.385s]

Finished. Total time: 1.824s

PS D:\Android\ADB> ./fastboot boot ginkgo_recovery.img

Sending 'boot.img' (65536 KB) OKAY [ 1.391s]

Booting OKAY [ 0.148s]

Finished. Total time: 1.591s

PS D:\Android\ADB> ./fastboot devices

97900a40 fastboot

PS D:\Android\ADB> ./fastboot flash recovery ginkgo_recovery.img

Sending 'recovery' (65536 KB) OKAY [ 1.414s]

Writing 'recovery' OKAY [ 0.381s]

Finished. Total time: 1.808s

PS D:\Android\ADB> ./fastboot reboot recovery

Rebooting into recovery OKAY [ 0.001s]

Finished. Total time: 0.003s

PS D:\Android\ADB> ./adb devices

* daemon not running; starting now at tcp:5037

* daemon started successfully

List of devices attached

PS D:\Android\ADB> ./fastboot devices

PS D:\Android\ADB> ./fastboot devices

What I believe is that I forgot to disable vbeta verification before flashing the new recovery (when I tried flashing a new recovery in my POCO, I got an error regarding this, but this time none of that happened). Is there any way to do it now? without having to go into EDL mode & stuff?
[Redmi Note 8 Questions & Answers] loopypalm:
to avoid problems on ginkgo you have to flash VBMETA then TWRP then the recovery you want

now try to flash the attached VBMETA using :

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

it will fix "System destroyed", if not you have to use EDL
[Redmi Note 8 Questions & Answers] Rocker_2102:
Umm.. that's where the problem is for me, I am unable to boot into fastboot mode. It juts goes back to the system destroyed screen no matter what button combination I try 😓.
[Redmi Note 8 Questions & Answers] loopypalm:
did you try the comand while "system destroyed" is displayed ?
[Redmi Note 8 Questions & Answers] Rocker_2102:
No.. but I tried connecting using adb and it did not work. I think I event tried "fastboot devices" which too didn't show anything 🥲.

But I'll try again now to confirm this.
[Redmi Note 8 Questions & Answers] Rocker_2102:
Hi,

Thank you @loopypalm , I was able to boot into fastboot somehow. Now the device is working fine on MIUI 12.
[Redmi Note 8 Questions & Answers] loopypalm:
I think you should try some custom roms

miui is not the optimal choice unfortunately ...
[Redmi Note 8 Questions & Answers] Rocker_2102:
It wasn't my phone so just bringing it back to working condition is pretty awesome for me 🙂. On my phone I keep trying new ROMS (just tried Projet Elixir) 🤓
[Redmi Note 8 Questions & Answers] Techue:
bro how did you booted into fastboot i also in same situation
[Redmi Note 8 Questions & Answers] Techue:
how did you fixed i also in same situation
[Redmi Note 8 Questions & Answers] Rocker_2102:
Just keep trying pressing the fastboot button combination.. It took me around 2 days 😖
[Redmi Note 8 Questions & Answers] Jyothis Jayanth:
same here, it's not booting to fastboot even tho I tried the combination when "Your system has been destroyed" was displayed ;-;
[Redmi Note 8 Questions & Answers] Rocker_2102:
I got it to working condition this way only, unfortunately.
[Redmi Note 8 Questions & Answers] lee435:
Hi, I tried this but am still getting "your system has been destroyed" :(

I am stuck in fastboot mode despite flashing recovery images successfully, and sometimes I receive a "system destroyed" message.
[Redmi Note 8 Questions & Answers] loopypalm:
make sure it's not RN8 ver2021

try the guide and the Vbmeta i attached here
[Xiaomi Poco X3 Pro] K-BOX2022:
Hey. I run different systems through LIMBO PC EMULATOR. Windows XP,7,8 ETC. The systems run very slowly. I found this KVM function. When clicked it crashes the emulator. I read on the internet that it helps supposedly in OS emulation. Is it possible to run KVM option on this smartphone? Is there any add command to build prop to run it???

Greetings