Related
people help with compiling the kernel for hydrogen. at the end it gives an error
Code:
make [1]: *** No rule to make target «arch / arm64 / boot / dts / hydrogen-msm8956-mtp.dtb», required for «arch / arm64 / boot / Image.gz-dtb». Stop.
make: *** [/ home / ilya / kernel / Xiaomi_Kernel_OpenSource / arch / arm64 / Makefile: 84: Image.gz-dtb] Error 2 [/ code]
why there is this error that I do not?
Caelcorlon said:
people help with compiling the kernel for hydrogen. at the end it gives an error
Code:
make [1]: *** No rule to make target arch / arm64 / boot / dts / hydrogen-msm8956-mtp.dtb, required for arch / arm64 / boot / Image.gz-dtb. Stop.
make: *** [/ home / ilya / kernel / Xiaomi_Kernel_OpenSource / arch / arm64 / Makefile: 84: Image.gz-dtb] Error 2 [/ code]
why there is this error that I do not?[/QUOTE]
You have to repo the source exactly as is. If you downloaded it as zip you are missing linked folders and that is the error you get. Missing these linked folders:
[url]https://github.com/MiCode/Xiaomi_Kernel_OpenSource/blob/hydrogen-m-oss/arch/arm64/boot/dts/qcom[/url]
[url]https://github.com/MiCode/Xiaomi_Kernel_OpenSource/blob/hydrogen-m-oss/arch/arm64/boot/dts/include/dt-bindings[/url]
Also don't use source from MiCode... It is missing a lot of stuff... Use source from:
[url]https://github.com/TheStrix/android_kernel_xiaomi_msm8956[/url]
Or
[url]https://github.com/zhaochengw/android_kernel_xiaomi_hydrogen[/url]
Or
[url]https://github.com/karthick111/android_kernel_xiaomi_hydrogen[/url]
Click to expand...
Click to collapse
Source code
nijel8 said:
Use source from:
Click to expand...
Click to collapse
some of these source code suitable for the drain firmware?
just copy hydrogen-msm8956-mtp.dtb at arch / arm64 / boot / dts /
Good news for joyuse devices owner, I admit that we can flashing custom rom android 10 curtana on joyuse as long as we be aware and inspected first:
It is what inside custom rom curtana only allow if inside contain: boot, system, product, and vendor, don't try to flash from curtana rom if it contain firmware update it will break your phone
You are as long as using curtana custom recovery you can flash curtana custom rom, and format data partition after flashing
You only replace folder camera on lib and lib64 on vendor from extracted vendor joyeuse in order camera working properly, use root and fx file explorer to access vendor
If you want to come back to joyeuse custom rom you need to flash joyeuse custom recovery again and flash original vendor image belongs to joyeuse again
Have enjoy flashing curtana custom rom on joyeuse devices
All are working perfecly accept bugs from custom rom itself.
Use with carefully and I am not responsible for your damage devices
hendibudi said:
Good news for joyuse devices owner, I admit that we can flashing custom rom android 10 curtana on joyuse as long as we be aware inspected first:
It is what inside custom rom curtana only allow if inside contain: boot, system, product, and vendor, don't try to flash from curtana rom if it contain firmware update it will break your phone
You are as long as using curtana recovery rom you can flash curtana custom rom
You only replace folder camera on lib and lib64 on vendor from extracted vendor joyeuse in order camera working properly
Have enjoy flashing curtana custom rom on joyeuse devices
All are working perfecly accept bugs from custom rom itself.
Click to expand...
Click to collapse
Have You Tried it?
Please attach some Screenshots:fingers-crossed:
!
OGHyperion said:
Have You Tried it?
Please attach some Screenshots:fingers-crossed:
!
Click to expand...
Click to collapse
Almost all rom working accept evolution x curtana rom
This is good news from the rom developers, to know that they would be able to quite easily adapt their versions to work on the joyeuse version.
Though I think that this way you fake all software,... to believe the phone is another version.
Which could conflict in the future.
I would rather try the following:
Start from a joyeuse rom (with correct firmware, vendor, ... data)
And only copy/overwrite the required partitions (data/system/....) with those of a curtana rom.
So keeping the correct firmware, vendor, ...
That would leave you only to adapt the build.prop file to set model, ... (check with the joyeuese rom)
Just a thought, I have not much knowledge here.
But also trying to learn and try.
Would someone be able to explain me the partition layout and where to find the system?
I am confused not to find the system partition.
How do I for example also remount the system partition on these phones to make it writable?
adb shell "su -c 'mount -o rw,remount /system'"
I'm trying to understand how this works, sorry for being noob.
C:\Users\kheno>adb shell
joyeuse:/ $ su
joyeuse:/ # ls /dev/block
bootdevice loop1 loop4 ram1 ram4 sda11 sda3 sdb2 sde1 sde18 sde26 sde34 sde42 sde50 sde9
by-name loop10 loop5 ram10 ram5 sda12 sda4 sdc sde10 sde19 sde27 sde35 sde43 sde51 sdf
dm-0 loop11 loop6 ram11 ram6 sda13 sda5 sdc1 sde11 sde2 sde28 sde36 sde44 sde52 sdf1
dm-1 loop12 loop7 ram12 ram7 sda14 sda6 sdc2 sde12 sde20 sde29 sde37 sde45 sde53 sdf2
dm-2 loop13 loop8 ram13 ram8 sda15 sda7 sdd sde13 sde21 sde3 sde38 sde46 sde54 sdf3
dm-3 loop14 loop9 ram14 ram9 sda16 sda8 sdd1 sde14 sde22 sde30 sde39 sde47 sde55 sdf4
dm-4 loop15 mapper ram15 sda sda17 sda9 sdd2 sde15 sde23 sde31 sde4 sde48 sde6 sdf5
dm-5 loop2 platform ram2 sda1 sda18 sdb sdd3 sde16 sde24 sde32 sde40 sde49 sde7 vold
loop0 loop3 ram0 ram3 sda10 sda2 sdb1 sde sde17 sde25 sde33 sde41 sde5 sde8 zram0
joyeuse:/ # ls /dev/block/by-name/
ALIGN_TO_128K_1 catecontentfv devinfo hyp mdtpsecapp qupfw spunvm vbmeta_system
ALIGN_TO_128K_2 catefv dip hypbak mdtpsecappbak qupfwbak ssd vbmeta_systembak
abl cateloader dsp imagefv metadata recovery storsec vbmetabak
ablbak cdt dspbak imagefvbak minidump recoverybak super xbl
aop cmnlib dtbo keymaster misc sda toolsfv xbl_config
aopbak cmnlib64 dtbobak keymasterbak modem sdb tz xbl_configbak
apdp cmnlib64bak exaid keystore modembak sdc tzbak xblbak
bluetooth cmnlibbak ffu limits modemst1 sdd uefisecapp
bluetoothbak cust frp logdump modemst2 sde uefisecappbak
boot ddr fsc logfs multiimgoem sdf uefivarstore
bootbak devcfg fsg mdtp multiimgqti secdata userdata
cache devcfgbak gsort mdtpbak persist splash vbmeta
joyeuse:/ # df -h
Filesystem Size Used Avail Use% Mounted on
tmpfs 2.7G 1.0M 2.7G 1% /dev
tmpfs 2.7G 0 2.7G 0% /mnt
tmpfs 2.7G 0 2.7G 0% /apex
/dev/block/sda12 11M 72K 11M 1% /metadata
tmpfs 2.7G 6.3M 2.7G 1% /sbin
/sbin/.magisk/block/system_root 2.2G 2.2G 7.2M 100% /sbin/.magisk/mirror/system_root
none 2.7G 0 2.7G 0% /sys/fs/cgroup
/dev/block/sda13 344M 940K 343M 1% /cache
/dev/block/sde4 256M 127M 128M 50% /vendor/firmware_mnt
/dev/block/sde9 27M 20M 7.3M 74% /vendor/dsp
/dev/block/sda2 27M 1.3M 26M 6% /mnt/vendor/persist
/dev/block/sde5 64M 848K 63M 2% /vendor/bt_firmware
/dev/block/sda7 976M 914M 62M 94% /cust
/dev/block/loop2 836K 808K 28K 97% /apex/[email protected]
/dev/block/loop3 5.2M 5.2M 32K 100% /apex/[email protected]
/dev/block/loop4 1.6M 1.6M 28K 99% /apex/[email protected]
/dev/block/loop5 5.0M 5.0M 32K 100% /apex/[email protected]
/dev/block/loop6 96M 96M 36K 100% /apex/[email protected]
/dev/block/loop7 232K 36K 196K 16% /apex/[email protected]
/dev/block/loop8 21M 21M 32K 100% /apex/[email protected]
/sbin/.magisk/block/product 1.0G 1.0G 3.3M 100% /sbin/.magisk/mirror/product
/sbin/.magisk/block/vendor 1.1G 1.1G 3.8M 100% /sbin/.magisk/mirror/vendor
/sbin/.magisk/block/data 105G 6.7G 98G 7% /sbin/.magisk/mirror/data
/data/media 105G 6.7G 98G 7% /mnt/runtime/default/emulated
Have no clue, still noob when it comes to these things
This seems great! Can someone else confirm that this approach works?
did you test on your own? and its success?
nickadsy said:
did you test on your own? and its success?
Click to expand...
Click to collapse
All custom rom curtana i try it working accept evolution x not working because inside rom there is no vendor image content
So it's supposed to be easy to build a patch to flash after flashing a curtana rom to bring it back to joyeuse
Going to download some ROMs and try this
ahked.ragab said:
So it's supposed to be easy to build a patch to flash after flashing a curtana rom to bring it back to joyeuse
Going to download some ROMs and try this
Click to expand...
Click to collapse
If it really works, it's possible to make patch..
eng4r said:
So it's supposed to be easy to build a patch to flash after flashing a curtana rom to bring it back to joyeuse
Going to download some ROMs and try this
Click to expand...
Click to collapse
Let us know how your patch goes
Do we need to flash curtana recovery on joyeuse? By the way can you give me joyeuse vendor I will try to make a zip that replace lib and lib64
anyone tried this if it works or not ?
Doesn't sound very reliable to me. Sorry.
Sent from my Redmi Note 9 Pro using XDA Labs
What about NFC?
Edit - I have just read your post #13 on the Havoc-OS-3.7 thread which seems to answer all my questions below, except "which Curtana recovery did you use". Thanks
@hendibudi - thank you for this post, I am really interested. I don't know enough to jump straight in and try it but hope I can get enough info to feel confident enough to have a go.
You say not to flash (on Joyeuse) if the Curtana rom contains firmware update.
So, looking inside the miui_JOYEUSEEEAGlobal_V11.0.3.0.QJZEUXM zip the first folder I see is "firmware-update". Is this the "firmware-update" you say to avoid? Would it only be in it's own folder or could there be (in different roms) firmware-updates in other folders? Does the absence of a firmware-update folder mean that I am safe to flash on my EEA joyeuse (without any further checks)?
Looking inside the Curtana Havoc-OS-v3.7-20200725-curtana-Official-GApps zip, there are 2 folders ("install" and "meta-inf") and I cannot see anything (in any of the folders) that looks (to me) like firmware-update.
Both the above zips contain folders called META-INF which both contain a folder called com\google\android. In both cases the android folder contains 2 files called "update-binary" and "updater-script". Looking through both update_binary files, they both seem to have a mention of "firmware" but it looks to me like it is mentioned in part of an error message (seems to be the same two 2 mentions in each).
Looking at the updater-script, the MIUI one really does seem to be updating about 30 objects from the "firmware-update" folder and even starts with a message saying "Patching firmware images..."
The Havoc updater script also prints a message saying "Patching firmware images..." which is followed by the last 3 lines of the script which are "package_extract_file" lines for dtbo.img , vbmeta.img and vbmeta_system.img. Would these update firmware or are they something else?
I will try looking these up in Google but I'm not confident I would understand the answer :0))
I understand that I and I alone am responsible for what I do/flash with my phone but from what I have seen in the above, it looks like I can safely use the Curtana Havoc rom on my EEA joyeuse phone. Would you agree or tell me not to try it?
Also, you mention (point 2) that we can use curtana custom recovery to flash the rom and format data partition - which curtana custom recovery have you used for this and is my EEA Joyeuse Note 9 pro different to your model (is it likely to be a problem).
I have rooted & flashed roms on several other phones in the past but all have had official TWRP's and the only thing to sort out was if they had MTK or SD cpu's – even I managed that quite easily. The Note 9 pro and all its variations seem to be in a whole new (& complicated) league.
https://forum.xda-developers.com/redmi-note-9-pro/themes/dolby-sound-mod-100-t4081933 Is this Firmware ?
mura20 said:
Let us know how your patch goes
Click to expand...
Click to collapse
Someone already did it http://forum.xda-developers.com/red...gisk-joyeuse-camera-fix-roms-curtana-t4142663
Does anyone know how I can get my Note 9 Pro Global back to the "brick" state?
Unfortunately I flashed a curtana image, because I always got Error 7 on the joyeuse image.
Now the device only boots up to the Redmi logo and restarts immediately.
I can't get into the Fastboot Mode anymore.
Can someone save my device or is there a possibility to flash it by myself?
Can i use miui 12 curtana rom for my joyeuse phone?
What? Want a brick? Lets do it!
Enviado desde mi Redmi Note 9S mediante Tapatalk
While i was looking for a way to change boot animations, (which i may have found, it looks like the bootanimation zip file is under "root/product/media") i went to change the name and paste the new file in there but it wouldnt allow me, it looks like you cant mount the root as read/write because its read only, is there a way to mount it? maybe through adb or termux?
edit: i was running the app as root still didnt seem to allow changes
No.
[Closed] Universal SystemRW / SuperRW feat. MakeRW / ro2rw (read-only-2-read/write super partition converter)
Welcome to the one and only, the original, universal, System-RW / Super-RW feat. Make-RW / ro2rw (read-only-2-read/write super partition converter) by lebigmac Also known as: THE-REAL-RW, FULL-RW, EXT4-RW, EROFS-RW, EROFS-2-RW, F2FS-RW...
forum.xda-developers.com
Mar-cel said:
[Closed] Universal SystemRW / SuperRW feat. MakeRW / ro2rw (read-only-2-read/write super partition converter)
Welcome to the one and only, the original, universal, System-RW / Super-RW feat. Make-RW / ro2rw (read-only-2-read/write super partition converter) by lebigmac Also known as: THE-REAL-RW, FULL-RW, EXT4-RW, EROFS-RW, EROFS-2-RW, F2FS-RW...
forum.xda-developers.com
Click to expand...
Click to collapse
yeah, gave tha a shot last night, flashed it through twrp but onl 2 lines showed up 1 saying it was running the script and another saying that it was complete then it just flashed back into twrp, and when i booted it up and tried to rename files it didnt work, i might have to try that superrepack tool tough i didnt see that thanks man! did you try it?
Hello.
I know that since Android 10, system rights are read-only.
How to make the system even write?
I have twrp, root magisk 23.0, stock rom 12.5.1.0, magisk module - magiskhide props config.
Rw privileges are visible in any file manager, but after modifying buildprop and then saving, it writes a save error.
Thanks
Not possible at the moment due to dynamic partitions.
[Closed] Universal SystemRW / SuperRW feat. MakeRW / ro2rw (read-only-2-read/write super partition converter)
Welcome to the one and only, the original, universal, System-RW / Super-RW feat. Make-RW / ro2rw (read-only-2-read/write super partition converter) by lebigmac Also known as: THE-REAL-RW, FULL-RW, EXT4-RW, EROFS-RW, EROFS-2-RW, F2FS-RW...
forum.xda-developers.com
ApexPrime said:
[Closed] Universal SystemRW / SuperRW feat. MakeRW / ro2rw (read-only-2-read/write super partition converter)
Welcome to the one and only, the original, universal, System-RW / Super-RW feat. Make-RW / ro2rw (read-only-2-read/write super partition converter) by lebigmac Also known as: THE-REAL-RW, FULL-RW, EXT4-RW, EROFS-RW, EROFS-2-RW, F2FS-RW...
forum.xda-developers.com
Click to expand...
Click to collapse
Via twrp or manual installation via terminal. I can't get it to work but other people with Poco f3 did it.
Greenspoof said:
Via twrp or manual installation via terminal. I can't get it to work but other people with Poco f3 did it.
Click to expand...
Click to collapse
Idk bro i havent tried it myself yet. It would be great if someone tries it and posts a tutorial as well.
Thanks, but I'd rather not try it either.
jkmaxfli said:
Thanks, but I'd rather not try it either.
Click to expand...
Click to collapse
Well, if you have twrp, the script is automatic so it's not really complicated
ApexPrime said:
Idk bro i havent tried it myself yet. It would be great if someone tries it and posts a tutorial as well.
Click to expand...
Click to collapse
There is a guide on the page, and for manual installation it's just 2 commands line. Of course if there are errors, it's more complicated. But if everything goes right, well it's very quick
When someone tries it and it is without complications, I will be happy to try it. I want to avoid problems like bootloop, brick.
The important thing is that there is a way.
jkmaxfli said:
When someone tries it and it is without complications, I will be happy to try it. I want to avoid problems like bootloop, brick.
The important thing is that there is a way.
Click to expand...
Click to collapse
Somewhere on the post there is a command line to recover the original super partition to fix possible bootloop. With this command, you can fix any possible bootloop
Youtube Tutorial Video:
Since Android partitions are no longer writable EVEN with root, you'll need to use special tools available online in order to mount a system as Read/Write.
I used this technique from another XDA thread and it is confirmed working!
What you'll Need:
*ROOT*
A File Explore with root tools (I used Solid Explorer)
A Terminal Application (Termux or Terminal Emulator should work just fine)
Computer with FASTBOOT installed
XDA Thread for reference:
[Closed] Universal SystemRW / SuperRW feat. MakeRW / ro2rw (read-only-2-read/write super partition converter)
Welcome to the one and only, the original, universal, System-RW / Super-RW feat. Make-RW / ro2rw (read-only-2-read/write super partition converter) by lebigmac Also known as: THE-REAL-RW, FULL-RW, EXT4-RW, EROFS-RW, EROFS-2-RW, F2FS-RW...
forum.xda-developers.com
Here are the steps:1. Download zip folder from either of these links:
Yandex
Finds everything
disk.yandex.com
17.63 MB file on MEGA
mega.nz
2. Extract systemrw_BUNDLE_proper and you'll see two zip files.
You'll only need systemrw_1.32_flashable.zip so delete the other ZIP file!
3. Inside that ZIP, there is META and systemrw_1.32. Extract folders to this directory: /data/local/tmp
4. Open up a terminal emulator and type "su" to give the emulator root rights.
5. Type cd /data/local/tmp/systemrw_1.32 to navigate to the tmp directory.
6. Now we are going to execute the file "systemrw.sh" BUT FIRST we need to make the file executable! Type: chmod 755 systemrw.sh
7. Now time to execute! Type: ./systemrw.sh size=15 (Size 15 is needed for it to work or else the phone will brick!)
8. WAIT PATIENTLY! It will take some time! Once it's finished there should be a folder in the /data/local/tmp/systemrw_1.32 directory called img.
9. Only copy super_fixed.bin to the root of your sdcard. Rename it to super.img.
10. Now copy super.img to your computer and flash the img with fastboot by typing: fastboot flash super super.img
DONE! Your System is now r/w!
Sorry for the noobie question... what are the advantages of make my system r/w?
8bitcode said:
Sorry for the noobie question... what are the advantages of make my system r/w?
Click to expand...
Click to collapse
Removing unwanted applications, bring able to modify build.prop to your liking, etc.
chocolote4444 said:
Removing unwanted applications, bring able to modify build.prop to your liking, etc.
Click to expand...
Click to collapse
Thanks, i think ill be doing this tonight, btw doing this procedure erases al phone data? and i dont need to do it every OTA?
8bitcode said:
Thanks, i think ill be doing this tonight, btw doing this procedure erases al phone data? and i dont need to do it every OTA?
Click to expand...
Click to collapse
It will not wipe phone data. You should be safe with that. But make a backup just in case if you have twrp.
@chocolote4444
Out of curiosity, will this work on the 6S Pro (No.Amer.) variant?
does this support android 12? mine is not working
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
chocolote4444 said:
Youtube Tutorial Video:
Since Android partitions are no longer writable EVEN with root, you'll need to use special tools available online in order to mount a system as Read/Write.
I used this technique from another XDA thread and it is confirmed working!
What you'll Need:
*ROOT*
A File Explore with root tools (I used Solid Explorer)
A Terminal Application (Termux or Terminal Emulator should work just fine)
Computer with FASTBOOT installed
XDA Thread for reference:
[Closed] Universal SystemRW / SuperRW feat. MakeRW / ro2rw (read-only-2-read/write super partition converter)
Welcome to the one and only, the original, universal, System-RW / Super-RW feat. Make-RW / ro2rw (read-only-2-read/write super partition converter) by lebigmac Also known as: THE-REAL-RW, FULL-RW, EXT4-RW, EROFS-RW, EROFS-2-RW, F2FS-RW...
forum.xda-developers.com
Here are the steps:1. Download zip folder from either of these links:
Yandex
Finds everything
disk.yandex.com
17.63 MB file on MEGA
mega.nz
2. Extract systemrw_BUNDLE_proper and you'll see two zip files.
You'll only need systemrw_1.32_flashable.zip so delete the other ZIP file!
3. Inside that ZIP, there is META and systemrw_1.32. Extract folders to this directory: /data/local/tmp
4. Open up a terminal emulator and type "su" to give the emulator root rights.
5. Type cd /data/local/tmp/systemrw_1.32 to navigate to the tmp directory.
6. Теперь мы собираемся исполнить файл " systemrw.sh ", НО СНАЧАЛА нам нужно сделать файл исполняемым! Тип: chmod 755 systemrw.sh
7. Теперь время выполнять! Введите: ./systemrw.sh size=15 (Для работы необходим размер 15, иначе телефон зависнет!)
8. ТЕРПЕЛИВО ЖДИТЕ! Это займет некоторое время! После завершения в каталоге /data/local/tmp/systemrw_1.32 должна появиться папка с именем img.
9. Скопируйте только super_fixed.bin в корень вашей SD-карты. Переименуйте его в super.img.
10. Теперь скопируйте super.img на свой компьютер и прошейте img с помощью fastboot, набрав: fastboot flash super super.img
ВЫПОЛНЕНО! Ваша система теперь r/w!:ковбой:
Click to expand...
Click to collapse
chocolote4444 said:
Youtube Tutorial Video:
Since Android partitions are no longer writable EVEN with root, you'll need to use special tools available online in order to mount a system as Read/Write.
I used this technique from another XDA thread and it is confirmed working!
What you'll Need:
*ROOT*
A File Explore with root tools (I used Solid Explorer)
A Terminal Application (Termux or Terminal Emulator should work just fine)
Computer with FASTBOOT installed
XDA Thread for reference:
[Closed] Universal SystemRW / SuperRW feat. MakeRW / ro2rw (read-only-2-read/write super partition converter)
Welcome to the one and only, the original, universal, System-RW / Super-RW feat. Make-RW / ro2rw (read-only-2-read/write super partition converter) by lebigmac Also known as: THE-REAL-RW, FULL-RW, EXT4-RW, EROFS-RW, EROFS-2-RW, F2FS-RW...
forum.xda-developers.com
Here are the steps:1. Download zip folder from either of these links:
Yandex
Finds everything
disk.yandex.com
17.63 MB file on MEGA
mega.nz
2. Extract systemrw_BUNDLE_proper and you'll see two zip files.
You'll only need systemrw_1.32_flashable.zip so delete the other ZIP file!
3. Inside that ZIP, there is META and systemrw_1.32. Extract folders to this directory: /data/local/tmp
4. Open up a terminal emulator and type "su" to give the emulator root rights.
5. Type cd /data/local/tmp/systemrw_1.32 to navigate to the tmp directory.
6. Now we are going to execute the file "systemrw.sh" BUT FIRST we need to make the file executable! Type: chmod 755 systemrw.sh
7. Now time to execute! Type: ./systemrw.sh size=15 (Size 15 is needed for it to work or else the phone will brick!)
8. WAIT PATIENTLY! It will take some time! Once it's finished there should be a folder in the /data/local/tmp/systemrw_1.32 directory called img.
9. Only copy super_fixed.bin to the root of your sdcard. Rename it to super.img.
10. Now copy super.img to your computer and flash the img with fastboot by typing: fastboot flash super super.img
DONE! Your System is now r/w!
Click to expand...
Click to collapse
hey, before i try this method to r/w my super partition, do you know if this method still works on Android 12? i have a red magic 6 pro with 5.12 version. Thx!
(even if you know other methods that are not downgrading to 4.12 or 4.15)
Confirmed working in Lenovo Legion Duel 2 Android 11.
Thanks.
Anyone in red magic 6R?
chocolote4444 said:
Youtube Tutorial Video:
Since Android partitions are no longer writable EVEN with root, you'll need to use special tools available online in order to mount a system as Read/Write.
I used this technique from another XDA thread and it is confirmed working!
What you'll Need:
*ROOT*
A File Explore with root tools (I used Solid Explorer)
A Terminal Application (Termux or Terminal Emulator should work just fine)
Computer with FASTBOOT installed
XDA Thread for reference:
[Closed] Universal SystemRW / SuperRW feat. MakeRW / ro2rw (read-only-2-read/write super partition converter)
Welcome to the one and only, the original, universal, System-RW / Super-RW feat. Make-RW / ro2rw (read-only-2-read/write super partition converter) by lebigmac Also known as: THE-REAL-RW, FULL-RW, EXT4-RW, EROFS-RW, EROFS-2-RW, F2FS-RW...
forum.xda-developers.com
Here are the steps:1. Download zip folder from either of these links:
Yandex
Finds everything
disk.yandex.com
17.63 MB file on MEGA
mega.nz
2. Extract systemrw_BUNDLE_proper and you'll see two zip files.
You'll only need systemrw_1.32_flashable.zip so delete the other ZIP file!
3. Inside that ZIP, there is META and systemrw_1.32. Extract folders to this directory: /data/local/tmp
4. Open up a terminal emulator and type "su" to give the emulator root rights.
5. Type cd /data/local/tmp/systemrw_1.32 to navigate to the tmp directory.
6. Ahora vamos a ejecutar el archivo " systemrw.sh " ¡PERO PRIMERO necesitamos hacer que el archivo sea ejecutable! Tipo: chmod 755 systemrw.sh
7. ¡Ahora es el momento de ejecutar! Escriba: ./systemrw.sh size=15 (¡Se necesita el tamaño 15 para que funcione o el teléfono se bloqueará!)
8. ¡ESPERA PACIENTE! ¡Tomará un poco de tiempo! Una vez que haya terminado, debería haber una carpeta en el directorio /data/local/tmp/systemrw_1.32 llamada img.
9. Solo copie super_fixed.bin a la raíz de su tarjeta SD. Cámbiele el nombre a super.img.
10. Ahora copie super.img a su computadora y actualice el img con fastboot escribiendo: fastboot flash super super.img
¡HECHO! ¡Su sistema ahora es r/w!:vaquero:
Click to expand...
Click to collapse
Hello, I did the whole process correctly as indicated in the tutorial, but I had the Bootloader Blocked and an error came out in the flashing, my headache just started, now I am bricked and although I try to solve it by flashing the roms that are in the forums, it is still successful flashing process still does not go past the logo. Do you know what I can do to recover my mobile?
Hello, I did the whole process correctly as indicated in the tutorial, but I had the Bootloader Blocked and an error came out in the flashing, my headache just started, now I am bricked and although I try to solve it by flashing the roms that are in the forums, it is still successful flashing process still does not go past the logo. Do you know what I can do to recover my mobile?
Jarligton said:
Hello, I did the whole process correctly as indicated in the tutorial, but I had the Bootloader Blocked and an error came out in the flashing, my headache just started, now I am bricked and although I try to solve it by flashing the roms that are in the forums, it is still successful flashing process still does not go past the logo. Do you know what I can do to recover my mobile?
Click to expand...
Click to collapse
hi, are you in the redmagic group? You could try to deepflash the phone using the unbrick tutorial in the group files.
Here the link: t.me/RedMagic6
is work.. but why after install with fastboot mode got bootloop?