Question switch un to cn - Red Magic 8 pro

is there any opportunity to do this like in red magic 7 pro thread?

vadizzi said:
is there any opportunity to do this like in red magic 7 pro thread?
Click to expand...
Click to collapse
If you refer to changing the payload_properties.txt in the CN rom and flash it using the local update then it does not work. I did try it.

[email protected] said:
If you refer to changing the payload_properties.txt in the CN rom and flash it using the local update then it does not work. I did try it.
Click to expand...
Click to collapse
anyway, I made it. I used the instructions from the topic on red magic 7

vadizzi said:
anyway, I made it. I used the instructions from the topic on red magic 7
Click to expand...
Click to collapse
I tried that but my sideload mode does not work. It displays two errors at the bottom screen and when I tried to sideload it failed at the installation steps. Do you have error message at the bottom of your phone screen?

[email protected] said:
I tried that but my sideload mode does not work. It displays two errors at the bottom screen and when I tried to sideload it failed at the installation steps. Do you have error message at the bottom of your phone screen?
Click to expand...
Click to collapse
i use my 3 dots manual update on phone with modifyed cn and wipe with stock recovery and it works with locked bootloader

vadizzi said:
i use my 3 dots manual update on phone with modifyed cn and wipe with stock recovery and it works with locked bootloader
Click to expand...
Click to collapse
I tried that but it did not work for me. How do you modified the cn rom?

[email protected] said:
I tried that but it did not work for me. How do you modified the cn rom?
Click to expand...
Click to collapse
i used 7zip and wrote "nx729j_un" for "NUBIA_SUBVERSION"

vadizzi said:
i used 7zip and wrote "nx729j_un" for "NUBIA_SUBVERSION"
Click to expand...
Click to collapse
That what I did but it did not work for me. I do not understand why? When I get into fastbootd I received the following messages:
ERROR recovery Failed to load bitmap fastbootd (error -1)
ERROR recovery Failed to load bitmap een/cant_find_OTG_en (error -1)
I received the same errors when I get into sideload mode. Thanks for your reply.

[email protected] said:
That what I did but it did not work for me. I do not understand why? When I get into fastbootd I received the following messages:
ERROR recovery Failed to load bitmap fastbootd (error -1)
ERROR recovery Failed to load bitmap een/cant_find_OTG_en (error -1)
I received the same errors when I get into sideload mode. Thanks for your reply.
Click to expand...
Click to collapse
I had these errors on stock. They do not interfere with the work of the sideload, because I just press enter recovery, leave the phone alone and flash everything I need. Sideload is only needed to get root and vice versa. Everything was done according to the instructions from the rm 7 pro topic through a manual update and three dots

For me the NUBIA_SUBVERSION option not worked, the update is interrupted and a message say:
"The package and the actual OS version do not mismatch, can't update".
{
"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"
}

nathandrake said:
For me the NUBIA_SUBVERSION option not worked, the update is interrupted and a message say:
"The package and the actual OS version do not mismatch, can't update".
View attachment 5856517
Click to expand...
Click to collapse
The NUBIA_SUBVERSION option did not work for my 512 GB (void) magic 8 pro but it did work for my 256 GB (Matte) magic 8 pro.

[email protected] said:
The NUBIA_SUBVERSION option did not work for my 512 GB (void) magic 8 pro but it did work for my 256 GB (Matte) magic 8 pro.
Click to expand...
Click to collapse
i have 512gb void and it works

vadizzi said:
i have 512gb void and it works
Click to expand...
Click to collapse
It did not work for my 512 GB Void so I unlocked the bootloader and used fastboot enhance to flash the payload bin of the CN rom. In the process I messed up the phone and have not been able to boot it up. Now I have a working Matte and a non-working Void.

i used to do this at first time. My sideload said "total xfer 1.00" and this means that the process is not completed in my case. later I did everything clearly according to the INSTRUCTIONS

I had the same problem with Red Magic 8 (cannot goback Global rom to CN rom). Any idea?

leequan2009 said:
I had the same problem with Red Magic 8 (cannot goback Global rom to CN rom). Any idea?
Click to expand...
Click to collapse
You can extract all the images from the payload bin and try to flash them yourself. I attach the list of the files you will have when you extract the images. You can use fastboot enhance, load the payload bin and extract the files or you can use payload dumper to do it. You can change the red8.txt to red8.bat and run it under command windows with all the images, adb and fastboot files in the same folder. However you will run the risk of not being able to boot your phone.

[email protected] said:
You can extract all the images from the payload bin and try to flash them yourself. I attach the list of the files you will have when you extract the images. You can use fastboot enhance, load the payload bin and extract the files or you can use payload dumper to do it. You can change the red8.txt to red8.bat and run it under command windows with all the images, adb and fastboot files in the same folder. However you will run the risk of not being able to boot your phone.
Click to expand...
Click to collapse
i won't try it

Related

Question HELP - Realmeflash.exe "cannot find central directory"

Hello everyone !
I am French and my English is very bad so I will use Google translation to communicate with you!
This is what is happening.
Without doing it on purpose, I flashed the original boot with the unofficial TWRP one!
Since then, I can no longer use my phone and I no longer enter the RUI3 interface.
I used Realmeflash.exe to reinstall the firmware and it gives me an error message "cannot find central directory".
{
"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"
}
Do you know how to solve this problem?
Thank you for your help !
I had the same problem you gotta get the MCT OFP extractor tool and QFIL, you extract everything with the MCT tool and then use QFIL to flash but the super.img is broken up into multiple files which I Have no clue how to merge so I'm stuck for now but if I get it working I'll be sure to tell you
kamubendi said:
I had the same problem you gotta get the MCT OFP extractor tool and QFIL, you extract everything with the MCT tool and then use QFIL to flash but the super.img is broken up into multiple files which I Have no clue how to merge so I'm stuck for now but if I get it working I'll be sure to tell you
Click to expand...
Click to collapse
Thank you very much friend
@kamubendi
I posted the problem on this page too !
https://c.realme.com/in/post-details/1525231625514856448
If it can help for the future
I share the extraction of the firmware : RMX3363GDPR_12_C.06_2022042721590000
https://drive.google.com/drive/folders/1QpeyOBuavwC3gq25jfKnNaXqmVBMAwt-?usp=sharing
use this flash tool. put the ofp file in same folder run exe & select region start flash https://github.com/italorecife/OppoRealme-OFP-Flash
urstrulynaveen said:
use this flash tool. put the ofp file in same folder run exe & select region start flash https://github.com/italorecife/OppoRealme-OFP-Flash
Click to expand...
Click to collapse
I already tried !
According to Google the .exe is infected with a virus, but I used it anyway, because I know it can be a false positive.
During use, the flash does a lot of "Success" but also "Failed", because of data protection on certain files!
Arrived at "service.img", the flash stops and nothing advances!
I recently unbricked my GT ME using this flash tool only. Realme flash tool doesn't support AB partition & dynamic partition table. It is the only working tool to flash through fastboot. After flashing completion change slot
fastboot getvar current-slot
fastboot --set-active=a or b
fastboot reboot
urstrulynaveen said:
I recently unbricked my GT ME using this flash tool only. Realme flash tool doesn't support AB partition & dynamic partition table. It is the only working tool to flash through fastboot. After flashing completion change slot
fastboot getvar current-slot
fastboot --set-active=a or b
fastboot reboot
Click to expand...
Click to collapse
I choose slot A to do the flashing and then I have to activate slot B ?
Yup after flashing success
urstrulynaveen said:
Yup after flashing success
Click to expand...
Click to collapse
Hi, I got my phone back from this scam repairman!
He damaged my phone even more than I left him!
Could you send me a screenshot of your c:\adb\dir please!
I no longer have recovery mode and the repairman told me a lot of things that I supposedly did during the flashing to get rid of his bull****!!
Thank you.
@urstrulynaveen Otherwise I tried what you told me and I got this!
ToutanVrac said:
@urstrulynaveen Otherwise I tried what you told me and I got this!
View attachment 5618219
Click to expand...
Click to collapse
Ur already in slot a change it to b. Firmware may flashed in slot b
urstrulynaveen said:
Ur already in slot a change it to b. Firmware may flashed in slot b
Click to expand...
Click to collapse
I already did, I have this command line that appears instead !
When I launch the program for slot A, it's very random when it blocks !
On the image, it's xb1_config_a which bug !
And when I close the window, it gives me success before it disappears !
In general, I have 50% success and 50% failed !
The furthest file that gave me the bug is the "super" file !
Apparently it is cut into 5 parts with the OFP extractor.
ToutanVrac said:
I already did, I have this command line that appears instead !
View attachment 5618873
When I launch the program for slot A, it's very random when it blocks !
On the image, it's xb1_config_a which bug !
And when I close the window, it gives me success before it disappears !
View attachment 5618879
In general, I have 50% success and 50% failed !
The furthest file that gave me the bug is the "super" file !
Apparently it is cut into 5 parts with the OFP extractor.
Click to expand...
Click to collapse
Every partition flashes in both slots except super partition. Super partition only flashes in inactive slot, that's why u need to change the slot. Super partition flashing takes around 25 to 30 minutes you need to be patient. & After flashing check slot and change it
urstrulynaveen
Thank you very much for helping me, it motivates me not to give up !
Did you receive a lot of failed during flashing ?
@urstrulynaveen
Problem solved...everything works! !
I'm in the interface and everything seems fine at the moment.
The flashing problem was what you said for the "super" file, but the main problem was above all the fact that I wasn't using a USB port on the motherboard !
Were you able to root the phone ?
ToutanVrac said:
@urstrulynaveen
Problem solved...everything works! !
I'm in the interface and everything seems fine at the moment.
The flashing problem was what you said for the "super" file, but the main problem was above all the fact that I wasn't using a USB port on the motherboard !
Were you able to root the phone ?
Click to expand...
Click to collapse
Can you explain to me how to do it with pictures and writing and I will be very thankful to you
nighetspy said:
Can you explain to me how to do it with pictures and writing and I will be very thankful to you
Click to expand...
Click to collapse
It's very easy !
1. You download the latest firmware
2. You put your phone in fastboot mode
3. You connect your phone with the original cable to an available port on your motherboard
4. You open the "OppoRealme-OFP-Flash_1.0.exe"
5. You choose the "most logical" options
The files will install one by one and you may get a lot of errors!
Leave it, the program will continue and at some point there will be a "super" file which will take a long time to install (30 minutes), you wait and then you will see your phone restart as if it were brand new !
ToutanVrac said:
It's very easy !
1. You download the latest firmware
2. You put your phone in fastboot mode
3. You connect your phone with the original cable to an available port on your motherboard
4. You open the "OppoRealme-OFP-Flash_1.0.exe"
5. You choose the "most logical" options
The files will install one by one and you may get a lot of errors!
Leave it, the program will continue and at some point there will be a "super" file which will take a long time to install (30 minutes), you wait and then you will see your phone restart as if it were brand new !
Click to expand...
Click to collapse
Finally, after two weeks of trouble, the problem was solved, thank you very much

Redmi Note 5 pro stuck on mi logo screen ( possibly hard bricked ) FLASH XBL ERROR

Hello, when i woke up today i found my phone had switched off ( possibly battery drained overnight ), but the LED light on it was still blinking continuously. I tried to switch it on but it got stuck on the mi logo.
Current situation : I can only access fastboot mode, TWRP recovery altough installed won't open up and just freezes on the introduction screen ( not accessible ) , and as previously mentioned I'm stuck on the MI logo screen.
ROM used : I was on pixel experience android 11 custom rom
What I tried so far : a) I tried to flash the global stable miui rom using the miflash tool, but i get this error. ( FAILED (remote: 'Error flashing partition : Write Protected')
{
"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"
}
a point to note is that I have verified that my bootloader is unlocked. ( Also tried the same with a different version of the global stable miui rom , still the same error )
b) I also tried to flash the ROM using the XiaMiTool V2 but I get the same "flash xbl error".
I have tried everything I knew and yet my phone is as useless as a rock right now. Any help would be greatly appreciated. Thanks!
have disabled dm verity with vbmeta.img for your phone?
you probably have a flashall script in the firmware archive, try commenting out xbl and repeat flash.
LR7875 said:
have disabled dm verity with vbmeta.img for your phone?
Click to expand...
Click to collapse
no I don't have any idea about this. Can you please tell me the steps on how to do it.
NextGenMagisk said:
you probably have a flashall script in the firmware archive, try commenting out xbl and repeat flash.
Click to expand...
Click to collapse
I did that, but then the next command in the flash_all.bat returns the error.
StickyFingers28 said:
I did that, but then the next command in the flash_all.bat returns the error.
Click to expand...
Click to collapse
Have you reflashed twrp?
Or try this twrp replacement :
Xiaomi Redmi Note 5 / 5 Pro (whyred) build releases | OrangeFox Recovery Downloads
Orangefox recovery for Xiaomi Redmi Note 5 / 5 Pro (whyred)
orangefox.download
Extract the downloaded zip and the recovery.img should be flashed like twrp.img.
LR7875 said:
Have you reflashed twrp?
Or try this twrp replacement :
Xiaomi Redmi Note 5 / 5 Pro (whyred) build releases | OrangeFox Recovery Downloads
Orangefox recovery for Xiaomi Redmi Note 5 / 5 Pro (whyred)
orangefox.download
Extract the downloaded zip and the recovery.img should be flashed like twrp.img.
Click to expand...
Click to collapse
Hi I tried flashing the orange fox recovery through fastboot but it gives me the following error. Any ideas
StickyFingers28 said:
Hi I tried flashing the orange fox recovery through fastboot but it gives me the following error. Any ideasView attachment 5620087
Click to expand...
Click to collapse
you made a typo, it's supposed to be "recovery" and not "recover"
hxudsh said:
you made a typo, it's supposed to be "recovery" and not "recover"
Click to expand...
Click to collapse
ah i see, now that i corrected the typo, it gives the error that is the same as i got with the miflash tool. How do i fix this.
You made sure you have your phone bootloader unlocked?
execute
fastboot getvar unlocked
LR7875 said:
You made sure you have your phone bootloader unlocked?
execute
fastboot getvar unlocked
Click to expand...
Click to collapse
yes i verified again by using MI unlock tool which then confirms that my phone is already unlocked.
StickyFingers28 said:
yes i verified again by using MI unlock tool which then confirms that my phone is already unlocked.View attachment 5620475
Click to expand...
Click to collapse
you download the official fastboot rom and under images folder find system.img and boot.img, move to c drive not under any folder, then
fastboot flash system C:\system.img
fastboot flash boot C:\boot.img
fastboot reboot
if these still give you write protected, you may have hardware fail
Fastboot - write protected
Today my cell phone got stuck on the android one logo. I was using the cell phone when it suddenly fired, so I forced a restart with the power button and from that moment on it never turned on again. I have the bootloader unlocked and I was...
forum.xda-developers.com

How To Guide [Oneplus 9 Pro] Extract partitions on unrooted or locked phone.

This manual will be useful for phones with Oxygen firmware, because very often they are get incremental updates and many users cannot install update with root, cannot find a stock boot, etc.
Also for those who want to unlock the bootloader at the first time and can save the persist patririon.
What are we need:
* MSMTools
* working fastboot
Let's start:
* reboot your phone in fastboot mode
* enter in cmd console
Code:
fastboot getvar current-slot
in that step we determine the current slot to extract the correct partitions
* start MSMTool program
{
"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"
}
* press F8 and you will see this windows
* choose right partitions (if your current slot are b, then choose for example boot_b, etc)
* in Password: field enter oneplus and press Ok
* if you make all right you will see that new button
* press on it, connect your phone and wait.
* selected images are saved on C:\
* profit
P.S. sorry for my english
Are you able to expand this tutorial on how to change partitions or on how to "update" msm so it uses a later version of OOS to unbrick the device?
The actual msm tool for OP9 Pro would install OOS11. But can it be changed to flash OOS12?
this tutorial only for how to extract partitions. android 11, 12, coloros, no matter.
for others can't help you
This part was empty for me:
Command "Fastboot devices" was working..
The tutorial in the first post is somewhat misleading. Fastboot is needed to flash back the partitions. In order for the partitions to be secured with the MSM tool, the phone must be in the EDL mode.
1. that means shutdown the phone
2. Start the MSM tool and press F8 on the keyboard
3. Press both volume keys at the same time and then connect the USB cable
4. Now the tool would have to recognize your phone and the partitions can be selected
The rest is well described in the first post.
I have a question, Im new in xda and I want to backup modest 1/2 and persist. In this post you can do it in MSM but I cannot see modemst1 or 2 in the partitions checkbox. They have another name? Or I cannot backup those partitions via MSM?
Cris092 said:
I have a question, Im new in xda and I want to backup modest 1/2 and persist. In this post you can do it in MSM but I cannot see modemst1 or 2 in the partitions checkbox. They have another name? Or I cannot backup those partitions via MSM?
Click to expand...
Click to collapse
Try Partitions Backup in the play store
TheGhost1951 said:
Try Partitions Backup in the play store
Click to expand...
Click to collapse
Do I need root or unlocked bootloader? Im unroot and with locked bootloader, that's why Im trying to do it like this post
Cris092 said:
Do I need root or unlocked bootloader? Im unroot and with locked bootloader, that's why Im trying to do it like this post
Click to expand...
Click to collapse
You don't need root to backup, but you do to restore the backup.
This is what my phone says when I open partitions backup
So that's why I want to do it via MSM like this post, but I don't know what partitions do I have to check in MSM. I can see persist but modest 1/2 I cant
Cris092 said:
This is what my phone says when I open partitions backupView attachment 5830269
So that's why I want to do it via MSM like this post, but I don't know what partitions do I have to check in MSM. I can see persist but modest 1/2 I cant
Click to expand...
Click to collapse
Sorry for misleading you, other than that not sure how to get the images you want.
Ok so I made backups using this method like 2 days ago, if we ever need to restore them, how do we do it?
immortalwon said:
Ok so I made backups using this method like 2 days ago, if we ever need to restore them, how do we do it?
Click to expand...
Click to collapse
With partitions backup?
TheGhost1951 said:
With partitions backup?
Click to expand...
Click to collapse
No, using the MSM tool to do a flash readback, which saves most of the firmware to the C: drive
If your phone is already on, you can also use the following command in command prompt to use ADB to reboot into EDL.
adb reboot edl
Still waiting for an answer from OP or anyone else: After we have made a flash read-back via MSM, how are these firmware files restored????
immortalwon said:
Still waiting for an answer from OP or anyone else: After we have made a flash read-back via MSM, how are these firmware files restored????
Click to expand...
Click to collapse
Flashed via Fastboot. For example if you extract boot.img from read-back and you want to restore the boot.img. Reboot your device into Fastboot and enter the following command in command prompt on your computer:
fastboot flash boot boot.img.
Depending on what you are flashing, you need to change the command accordingly. e.g vendor_boot.img
fastboot flash vendor_boot vendor_boot.img

Trying to install Kali Nethunter on OnePlus 7T unable to mount partitions error

Hello thanks for reading,
I've spent about 2 days trying to figure this one out so any help would be greatly appreciated.
I've flashed it back to stock rom "hotdogb_14_O.22_210127.ops" with the MSM tool and flashed recovery TWRP to it, but I am consistently receiving the error
" Failed to mount '/system_ext' (Block device required)" in TWRP when i'm trying to write zip files and disable encryption.
when it comes to install anything, I get this same message and it fails - where am I going wrong? i've tried wiping it and repair as ext4 but nothing, same deal... any ideas?
Thanks in advance
tehnooks said:
Hello thanks for reading,
I've spent about 2 days trying to figure this one out so any help would be greatly appreciated.
I've flashed it back to stock rom "hotdogb_14_O.22_210127.ops" with the MSM tool and flashed recovery TWRP to it, but I am consistently receiving the error
" Failed to mount '/system_ext' (Block device required)" in TWRP when i'm trying to write zip files and disable encryption.
when it comes to install anything, I get this same message and it fails - where am I going wrong? i've tried wiping it and repair as ext4 but nothing, same deal... any ideas?
Thanks in advance
Click to expand...
Click to collapse
Use twrp v1 on twrp.me ?
Download TWRP for hotdog
Download TWRP Open Recovery for hotdog
dl.twrp.me
HueyT said:
Use twrp v1 on twrp.me ?
Download TWRP for hotdog
Download TWRP Open Recovery for hotdog
dl.twrp.me
Click to expand...
Click to collapse
Giving it a try right now, fingers crossed, I used a different version that boots before but not this one it seems. I'll let you know
Thanks for your time replying
Use twrp v1 on twrp.me ?
HueyT said:
Download TWRP for hotdog
Download TWRP Open Recovery for hotdog
dl.twrp.me
Click to expand...
Click to collapse
Didn't work, same issues, i'm at my wits end someone help me pretty please! Here's a screenshot
{
"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"
}
Does this no matter what I install, even if I go to format and wipe data always fails at that point, what command or trick am I missing guys? *begs*
Bootloader unlocked?
HueyT said:
Bootloader unlocked?
Click to expand...
Click to collapse
Yeah, all unlocked and ready to go else wouldnt let me boot into twrp without that first. I tried it with the latest version of android 11 and it didn't have the same message but still gave me a cant mount /opm (or something close to this) error message.... I feel like its something simple that I just lack the knowledge of
tehnooks said:
Yeah, all unlocked and ready to go else wouldnt let me boot into twrp without that first. I tried it with the latest version of android 11 and it didn't have the same message but still gave me a cant mount /opm (or something close to this) error message.... I feel like its something simple that I just lack the knowledge of
Click to expand...
Click to collapse
Did u "mount data" while in twrp before formatting data?
Morning Huey, No I did not, I am about to try it again right now just restoring via MSM and i'll give it a go
I've been following the guide at https://www.kali.org/docs/nethunter/installing-nethunter-on-the-oneplus-7/
but it's not for the 7T so maybe theres something missing, ive even tried using the older versions they suggest on there with no luck so far
HueyT said:
Did u "mount data" while in twrp before formatting data?
Click to expand...
Click to collapse
doesn't let me mount data before formatting data ;(
tehnooks said:
doesn't let me mount data before formatting data ;(
Click to expand...
Click to collapse
Remove screenlock before rebooting into twrp as your twrp is not decrypting data on 11.0.9.1
I'm downgraded to the last android 10 version as the guide says (but for hotdog) but always get the same error no matter what, I never set a screenlock or password or even a fingerprint, will update to 11 and latest update and try it again but it said can't mount /opm or something similar doing it that way. I feel like i'm just missing something really simple about the whole thing but i've followed the guides to a T

Question Red Warning and UnWorking Lockscreen. HELP

{
"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"
}
Hello, dear owners of this beautiful device.
After an unsuccessful attempt to get root, such a warning appeared, plus the ability to lock the screen disappeared. As a result, I didn't get root either and problems arose)
Could you show the instructions how to fix everything step by step and get root? Thanks)
Hey, so I have the same problem as you. I was installing the patched boot.img file when I rebooted, but there was no magsik app. After I tried to flash the same file again, except I put in some vbmeta file because some website said so, now my phone's files are corrupted. I got into fastboot mode and put through recovery mode, and did a data wipe and one final reboot, but even that did work because it said my phone is corrupt. The last thing I will try is to install TWRP, remove the old data, and install the update to restore the previous ROM files. I'll let you know if anything works. Just try ur methods and let me know if they worked. Sure is an expensive paperweight if it doesn't work...
redmgicUSER8 said:
Hey, so I have the same problem as you. I was installing the patched boot.img file when I rebooted, but there was no magsik app. After I tried to flash the same file again, except I put in some vbmeta file because some website said so, now my phone's files are corrupted. I got into fastboot mode and put through recovery mode, and did a data wipe and one final reboot, but even that did work because it said my phone is corrupt. The last thing I will try is to install TWRP, remove the old data, and install the update to restore the previous ROM files. I'll let you know if anything works. Just try ur methods and let me know if they worked. Sure is an expensive paperweight if it doesn't work...
Click to expand...
Click to collapse
did anything happen?
Stusick said:
Did anything happen?
Click to expand...
Click to collapse
Nothing yet... I'm trying to contact the support team. They can only do so much remotely
i have this error also what should i do?
the phone not boot up
the red warning are stuck
yakir150 said:
i have this error also what should i do?
the phone not boot up
the red warning are stuck
Click to expand...
Click to collapse
Your boot loader must be unlock
Reboot to recovery, choose English when you see "Wipe data" type
adb reboot sideload
Once your phone boots into sideload mode (When you see the two error line at the bottom of the screen) type
adb sideload NX729J-update.zip
When the transfer is successful ( with a transfer of 2.0 display) you can wipe the data twice with the first and second options and reboot the phone. If you are lucky, the phone will boot
[email protected] said:
Your boot loader must be unlock
Reboot to recovery, choose English when you see "Wipe data" type
adb reboot sideload
Once your phone boots into sideload mode (When you see the two error line at the bottom of the screen) type
adb sideload NX729J-update.zip
When the transfer is successful ( with a transfer of 2.0 display) you can wipe the data twice with the first and second options and reboot the phone. If you are lucky, the phone will boot
Click to expand...
Click to collapse
okay i try it and still no luck the same problem
yakir150 said:
okay i try it and still no luck the same problem
Click to expand...
Click to collapse
Download global V3.19 rom from: https://rom.download.nubia.com/Europe&Asia/NX729J/V319/NX729J.zip
Download QPST and QFIL flash tool from: https://www.mediafire.com/file/220h5xaxi1gd55m/QPST_2.7.496.zip/file. Install the driver (provided in the download) and these two programs.
You could then flash this rom V3.19 using QFIL flash tool. If you can flash this rom successfully your phone will work.
[email protected] said:
Download global V3.19 rom from: https://rom.download.nubia.com/Europe&Asia/NX729J/V319/NX729J.zip
Download QPST and QFIL flash tool from: https://www.mediafire.com/file/220h5xaxi1gd55m/QPST_2.7.496.zip/file. Install the driver (provided in the download) and these two programs.
You could then flash this rom V3.19 using QFIL flash tool. If you can flash this rom successfully your phone will work.
Click to expand...
Click to collapse
my phone is eu and using 4.18
can i use 3.19?
it's ok?
yakir150 said:
okay i try it and still no luck the same problem
Click to expand...
Click to collapse
For QFIL, use Flat Build and in the configuration use ufs. Good luck!
yakir150 said:
my phone is eu and using 4.18
can i use 3.19?
it's ok?
Click to expand...
Click to collapse
Your version V4.18 will be replaced by V3.19. This V3.19 version can be flashed through edl mode. I could not find V4.18 in this format. The two roms are very similar. They are both global roms.
[email protected] said:
Your version V4.18 will be replaced by V3.19. This V3.19 version can be flashed through edl mode. I could not find V4.18 in this format. The two roms are very similar. They are both global roms.
Click to expand...
Click to collapse
okay i will try and let you know
thank you very much
yakir150 said:
okay i try it and still no luck the same problem
Click to expand...
Click to collapse
If QFIL does not work, you need to do side load the rom multiple times again then it might work!
turn off the red rm8 notification (Your device is broken. It is unreliable and may not work)
- enter command on PC: adb reboot "dm-verity enforcing"
- on phone for rooted device with termux: reboot "dm-verity enforcing"
izsdeaman said:
turn off the red rm8 notification (Your device is broken. It is unreliable and may not work)
- enter command on PC: adb reboot "dm-verity enforcing"
- on phone for rooted device with termux: reboot "dm-verity enforcing"
Click to expand...
Click to collapse
The command on PC shows "Too many arguments." The Termux one works. Thanks!
[email protected] said:
Your boot loader must be unlock
Reboot to recovery, choose English when you see "Wipe data" type
adb reboot sideload
Once your phone boots into sideload mode (When you see the two error line at the bottom of the screen) type
adb sideload NX729J-update.zip
When the transfer is successful ( with a transfer of 2.0 display) you can wipe the data twice with the first and second options and reboot the phone. If you are lucky, the phone will boot
Click to expand...
Click to collapse
Tahnk you very very very much.

Categories

Resources