Develop Bugs

please help my phone stuck on samsung logo

hello guys
my phone can't boot when i turn on my phone stuck on samsung logo
please i need help i download the official firmware and i try to install this firmware "N7100XXUFND4_N7100OJVFND3_N7100XXUFND3_HOME.tar.md5" by odin but nothing happen
and i can't access recovery mode
can any one help me please

suirs said:
hello guys
my phone can't boot when i turn on my phone stuck on samsung logo
please i need help i download the official firmware and i try to install this firmware "N7100XXUFND4_N7100OJVFND3_N7100XXUFND3_HOME.tar.md5" by odin but nothing happen
and i can't access recovery mode
can any one help me please
Click to expand...
Click to collapse
Boot your phone to download mode by pressing vol down+home+power buttons together. Then plug in the usb cable, run odin and select the md5 file. Click on start. Be patient it should automatically reboot within a few minutes. If it doesn't try flashing a custom recovery like TWRP through odin and do a full wipe before flasing. Hope it helps!!

joy854 said:
Boot your phone to download mode by pressing vol down+home+power buttons together. Then plug in the usb cable, run odin and select the md5 file. Click on start. Be patient it should automatically reboot within a few minutes. If it doesn't try flashing a custom recovery like TWRP through odin and do a full wipe before flasing. Hope it helps!!
Click to expand...
Click to collapse
i trying to install custom recovery TWRP by odin but when i finished nothing happen
and i try to install custom recovery PhilZ Touch but when i finished nothing happen
i wanna some help pleaseeeeee

suirs said:
i trying to install custom recovery TWRP by odin but when i finished nothing happen
and i try to install custom recovery PhilZ Touch but when i finished nothing happen
i wanna some help pleaseeeeee
Click to expand...
Click to collapse
What error do you get in odin when flashing stock firmware?Is your phone being detected by odin in the first place?Is the ID:COM port lighting up blue which means successful connection has been established between phone and odin.If ID:COM doesn't light up then you need to change your USB CABLE (if you are not using stock samsung cable ,if you are then use another stock samsung usb cable)Screenshot the error if any you get in ODIN and upload it for us.

singhpratik87 said:
What error do you get in odin when flashing stock firmware?Is your phone being detected by odin in the first place?Is the ID:COM port lighting up blue which means successful connection has been established between phone and odin.If ID:COM doesn't light up then you need to change your USB CABLE (if you are not using stock samsung cable ,if you are then use another stock samsung usb cable)Screenshot the error if any you get in ODIN and upload it for us.
Click to expand...
Click to collapse
firstly i use the stock samsung cable
and when i connect my phone in odin i got lighting up blue in port ID:COM
and i got this problem when i press start
this before press start
{
"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"
}
and i got this problem after press start
please i need some help

when i install TWRP custom recovery i got in ID:COM port this
but when i try to enter to recovery mode i can't
please i need help

now i download the N7100XXUFNE1_N7100VFGFNE2_N7100BUUFND2_HOME.tar firmware
but when i try to install via odin i got Fail
i need some one help me to found solution for this problem

i need some help from anyone pleaseeeee

suirs said:
when i install TWRP custom recovery i got in ID:COM port this
but when i try to enter to recovery mode i can't
please i need help
Click to expand...
Click to collapse
What happens when you press VolUp+Home+Powerbutton?
Release buttons as soon as Samsung font appears. and then?

Androidwizzard said:
What happens when you press VolUp+Home+Powerbutton?
Release buttons as soon as Samsung font appears. and then?
Click to expand...
Click to collapse
nothing happen
just i see samsung galaxy note 3 gt-n7100 and the phone restart and stuck on the samsung logo
can anyone help me pleaseee and tell me what can i do ??

i try this firmware N7100XXALJ3_N7100OJVALJ2_N7100XXALJ2_HOME.tar
and when odin finish give me "Pass"
and when my mobile restart still stuck on samsung logo and still can't access recovery mode

Definatly seems like there was an issue with Odin, but you need to get it into download mode to return to stock then try again.

Had the same ****; Please check if your internal storage is available. Mine has the exact same problem and it could be due to faulty hardware (emmc).
To check if the internal storage is mounted check your recovery. it will indicate that it couldn't mount system and a range of other mounting errors. You could use adb to see which volumes are mounted.
(Check my thread http://forum.xda-developers.com/showthread.php?t=2716444 it has detailed info about how to check your volumes)

Gamebytes said:
Had the same ****; Please check if your internal storage is available. Mine has the exact same problem and it could be due to faulty hardware (emmc).
To check if the internal storage is mounted check your recovery. it will indicate that it couldn't mount system and a range of other mounting errors. You could use adb to see which volumes are mounted.
(Check my thread http://forum.xda-developers.com/showthread.php?t=2716444 it has detailed info about how to check your volumes)
Click to expand...
Click to collapse
hey bro can you tell me how to check internal storage
and if i wanna to use any program can you give me this program

can anyone please give me That's factory firmware
N7100XXALJ3_N7100OJVALJ2_N7100XXALJ2_HOME.tar
i mean i need stock firmware with repartition capability because this only firmware work on my mobile but i need the best pit file to see whats happened

i need the pit file compatible with this firmware
N7100XXALJ3_N7100OJVALJ2_N7100XXALJ2_HOME.tar
can any one give me the pit file pleaseeee

i download this pit file
PIT_N7100_16GB_20121102.pit
and when i use this i get fail
but if i remove pit file i got pass in ID:COM

Mi A2 lite suddenly damaged???

Hello,
I have a very big problem which i'm not able to solve. So here is my story (i have already tried a lot). First of all, my device worked fine for the first month.
First I installed several gsis. At first I didn't know how to do it but now i know. So I flashed my device a lot…
Then, I installed a gsi and wanted to install gapps. Because of the fact, that twrp isn't really able to install zips yet I tried to unpack the zip and run the sh script with root and fx file explorer.
After that the whole s*** began.
My device freezes so I needed to force a reboot. But then it didn't boot anymore. So I flashed the stock rom again with MiFlash.
After a reboot the device freezes at Bootanimation and reboots. the second boot it reboots correctly and the start screen with "Hi there" pops up. But after a few clicks my device freezes again and reboots again.
After that I decided to install a GSI with Android 9 which worked before this Problem without ones. But same issue here: freezes and reboots.
I thought it is an emmc Problem so I tried something and the Phone was completely Bricked. Only EDL mode worked. Flashing back to stock rom with Miflash wasn't possible in edl mode. Idon't know why. So I decided to download qualcomm's flash tool and reflash the whole emmc in edl mode (nothing else was possible). After flash was completed and the phone rebooted successfully I put it into fastboot and flashed the normal images (stock os) again. Now Miflash worked again.
BUT:
The same problem described before happens again and again:
First boot after flashing stock: reboot in Boot Animation
Second boot: Boot to welcome screen, after around 10 seconds phone freezes and reboots
Following boots are same as second boot.
Can anyone please help me?

That doesn't sound good.. have you tried factory reset in recovery? I would try that after a fresh install with miflash.
Hope you get it sorted

Thank for the reply,
I also did an factory reset.
I have news (I think that they are not really good):
I installed PHH's AOSP 8.1 GSI without gapps to prevent the whole setup stuff.
Now I can use the phone for around ten seconds.
Here is everything I noticed:
Wifi not working -> freeze and reboot if I want to activate it
BT not working -> same here (freeze and reboot if I want to activate it)
Camera not working -> also same
Seems like all devices won't work.
Some other advices?
Edit: after reflashing vendor.img problem is still there.

Ok, now I have another problem:
I cannot enter edl mode again.
How can I do that?
Bootloader is locked and i cannot unlock anymore
it just sys:
Code:
FAILED (remote: oem unlock is not allowed)
and entering edl over fastboot also does not work. I only get:
Code:
FAILED (remote: device is locked! no edl)
But i cannot unlock the bootloader.
Is there an other way to enter EDL Mode?
EDIT:
Ok I think the only way to enter edl mode is to open the device and short the two test points.
I will write if I have news.

Seems like there are other Posts with different problems at the beginning which are now facing the same problem as we do, after some flashing:
https://forum.xda-developers.com/mi-a2-lite/how-to/xiaomi-mi-a2-lite-hard-brick-t3861576
https://forum.xda-developers.com/mi-a2-lite/help/destroyed-t3860080

TJ1999 said:
Hello,
I have a very big problem which i'm not able to solve. So here is my story (i have already tried a lot). First of all, my device worked fine for the first month.
First I installed several gsis. At first I didn't know how to do it but now i know. So I flashed my device a lot…
Then, I installed a gsi and wanted to install gapps. Because of the fact, that twrp isn't really able to install zips yet I tried to unpack the zip and run the sh script with root and fx file explorer.
After that the whole s*** began.
My device freezes so I needed to force a reboot. But then it didn't boot anymore. So I flashed the stock rom again with MiFlash.
After a reboot the device freezes at Bootanimation and reboots. the second boot it reboots correctly and the start screen with "Hi there" pops up. But after a few clicks my device freezes again and reboots again.
After that I decided to install a GSI with Android 9 which worked before this Problem without ones. But same issue here: freezes and reboots.
I thought it is an emmc Problem so I tried something and the Phone was completely Bricked. Only EDL mode worked. Flashing back to stock rom with Miflash wasn't possible in edl mode. Idon't know why. So I decided to download qualcomm's flash tool and reflash the whole emmc in edl mode (nothing else was possible). After flash was completed and the phone rebooted successfully I put it into fastboot and flashed the normal images (stock os) again. Now Miflash worked again.
BUT:
The same problem described before happens again and again:
First boot after flashing stock: reboot in Boot Animation
Second boot: Boot to welcome screen, after around 10 seconds phone freezes and reboots
Following boots are same as second boot.
Can anyone please help me?
Click to expand...
Click to collapse
Hello, the solution is VERY simple, however it requires a certain knowledge of mobile maintenance (I believe that almost everyone has knowledge in opening and storing certain things in a mobile device) go for me ...
Download the latest version of MiFlashTool, and download the V9.6.4.0.ODLMIFF version, open the device, and with CAUTION place a tweezers or something like this in the image and place the USB cable in the phone after the procedure. pin the device and put the USB cable, click Refresh, and the device will appear in EDL mode, flash the system and in 5 minutes the system opens, worked for me !!
But proceed with care, I do not take responsibility for people without knowledge of disassembling of devices to cause some damage in the own device.
{
"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"
}

OK I was able to enter edl mode with the testpoint Methode.
I erased the whole flash storage with QFIL from Qualcomm and also reflashed the emmc.
But it did not work.
After that I entered edl mode again and tried to flash via miflash. ( I also downloaded the New Version available now from the miui site).
BUT:
Linke it was with QFIL, after exit edl mode the phone tries to Boot, but it get stuck in bootanimation. It seems Like it boots to infinity. No Matter what I do. I also tried to change partition with fastboot set active x.
BUT Still No Success

no ideas?

[Solved] Can't boot into TWRP on Samsung Galaxy A5 (2017) "No command" Error

[Solved] Can't boot into TWRP on Samsung Galaxy A5 (2017) "No command" Error
So I'm trying to root my A5 2017 and I flashed TWRP with Odin but as soon as I boot into recovery mode I get a message saying: "Installing system update..." and then I get a "No command".
Shortly after I get redirected to the normal android recovery screen.
This is what's on there:
Android Recovery
samsung/a5y17ltexx/a5y17lte
8.0.0/R16NW/A520FXXU7CRJ3
user/release-keys
Use volume up/down and power.
Reboot system now
Reboot to bootloader
Apply update from ADB
Apply update from SD card
Wipe data/factory reset
Wipe cache partition
Mount /system
View recovery logs
Run graphics test
Power off
#fail to open recovery_cause(No such file or directory)#
#Reebot Recovery Cause is [UNKNOWN]#
No Support SINGLE-SKU
File-Based OTA
Supported API: 3
# MANUAL MODE V1.0.0#
Successfully verified dmverity hash tree
E:Failed to clear BCB message: failed to find /misc partition
Click to expand...
Click to collapse
Can someone help me with this? I tried to flash other TWRP versions but with the same results

Disable auto reboot before flashing TWRP. When PASS is displayed on Odin, hold all of the hardware buttons on the phone, vol up, vol down, home (the one on the middle), power. When the download mode disappears release volume down and continue holding the rest.

Bryan48765 said:
Disable auto reboot before flashing TWRP. When PASS is displayed on Odin, hold all of the hardware buttons on the phone, vol up, vol down, home (the one on the middle), power. When the download mode disappears release volume down and continue holding the rest.
Click to expand...
Click to collapse
Thanks that actually worked! But another problem emerged. The SuperSU file that I'm trying to flash makes my phone reboot in the middle of the installation.

Hyai said:
Thanks that actually worked! But another problem emerged. The SuperSU file that I'm trying to flash makes my phone reboot in the middle of the installation.
Click to expand...
Click to collapse
Fixed it by flashing a different TWRP version and a different SuperSU version!

Bryan48765 said:
Disable auto reboot before flashing TWRP. When PASS is displayed on Odin, hold all of the hardware buttons on the phone, vol up, vol down, home (the one on the middle), power. When the download mode disappears release volume down and continue holding the rest.
Click to expand...
Click to collapse
It worked for me too on galaxy a5 2016 a510m from brazil, using Odin3 v3.13.1 and twrp-3.2.3-0-a5xelte.img.
After hours looking for a solution, u saved me

Only official released binaries are allowed to be flashed (recovery)
Hi,
Just tried flashing TWRP to my A5 2017, it got PASS with my first attempt but then gave me the No Command screen, from there I did a factory reset as per the instructions of the tutorial I was using and now, not only can I still not access TWRP and had my phone wiped but I can't even flash the TWRP as now it gives me the "Only official released binaries are allowed to be flashed (recovery)" error. Are there any suggestions?

I have a Samsung Galaxy A5 2017 and I cannot install TWRP recovery in order to restore the backup of the different partitions, it gives me error = fail to open recovery_cause (no such file or directory) or custom binary (RECOVERY) blocked by FRP Lock.
If you install the firmware the phone always restarts up to the screen with No command, and if I press the power and vol + keys it gives the list of errors of the partitions / EFS, / System, etc. and error couldn't create verity device.
Can I do something to solve it? Can I recreate the original Recovery?
my problem is slightly different, at the no command screen, I press the power button and the volume + button, a screen appears with some writing, I attach photos, if I try to install twrp from the download screen I get the message: custom binary ( RECOVERY) blocked by FRP Lock.
If I could install twrp I have the backup of the partitions of the entire mobile phone.
So I don't know what to do.
{
"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"
}

Hey short question.
I reseted my Samsung Galaxy A5 (2017) back to factory mode.
Few hours later, I charged my phone at my friends place.
I realize after a while that my phone wasn't charging fast enough.
I plug the calbe which belongt too my friend out of my phone.
Suddenly a Screen came up, which showed a notification .
It was telling me
something like : ,, Failed to Install program."
,, Build info: a5y17ltexx-user 8.0.0 R16NW A520FXXUGCTKA release-keys
Serial number: 52103d1dfcb0c391 ."
I forgot too make a screenshot of the notification, before closing the window. I saved the fail repot in my Mail-Acc .
So my question is now,
Is the reason for this report a problem, which came because of me doing the Factory-Reset (pherhaps a problem by updating the software or application)?
Or could it be possible that my friend tried to Install some kind of programmes onto my phone,
which failed downloading because of me unplugging my phone.

Bryan48765 said:
Disable auto reboot before flashing TWRP. When PASS is displayed on Odin, hold all of the hardware buttons on the phone, vol up, vol down, home (the one on the middle), power. When the download mode disappears release volume down and continue holding the rest.
Click to expand...
Click to collapse
Hi everyone and thank you Bryan48765 for you solution. I flashed a twrp version and on the first restart it worked, but the next re-start it reverted back to the custom recovery. I'll try to flash a different twrp and see how it goes. also hoping to flash magisk & see how it goes. Thank you again. Forgot to add that this solution worked on a samsung Note 4 SM-N910f chinese motherboard.
​

Hi everyone,
Can you help with shedding light on what's on here and suggesting what could be done next? I have just bought another A5 2017.
Initially I started it, installed my email account, some applications, all seemed fine. After restarting I got a black screen with red letters indicating bypass FRP lock. Impossible to reboot the phone. So I installed Odin and I tried to reinstall the system. It worked.
The system was downloading updates when suddenly I got a "no command screen." Impossible to reach the boot, it's been 10 minutes or so that the phone just tries and restarts all the time, initiating with a "installing phone updates" to eventually show again the "no command" screen and so on.
Do you have any clue on what's going on ? What could be done at all from now on?

[GUIDE/TIP]Failed fastboot flashing of stock ROM

I was on stock ROM (12.0.8.0 QJSEUXM) and noticed that v12.0.9.0 is out for some time already, but not offered by system to be installed. In the past with my previous phones when I wanted to "force" the update, I simply downloaded fastboot ROM, flashed it and re-rooted the phone. In a matter of few minutes I had up-to-date and working phone again. Today I tried the same with Mi 10T lite and it failed miserably.
Observed issues:
1. flashing script (flash_all_except_storage.bat) comes with CRCLIST and SPARECRCLIST commands which are either not understood by phone (fastbootd), or fail verification (fastboot)
2. after modification of script and removal of beforementioned lines, flashing completes, however phone stays in bootloop showing just Mi logo
3. using different PC, USB port, USB cable, fastboot version, fastbootd/fastboot mode, driver version, Mi flash,.. result always in the same non-functional phone
4. after booting to TWRP (fastboot boot twrp.img), internal data gets decrypted correctly, but TWRP reports issue mounting /odm
5. flashing different ROM version results in the very same issue
Fix:
1. Flash stock ROM (in my case 12.0.8.0)
2. If you receive an CRC error, remove 2 lines from flashing script containing words CRCLIST and SPARECRCLIST and re-run it again
3. Download recovery ROM (12.0.9.0) and put it to internal SD (you can do it in advance or through TWRP when the phone is already "soft-bricked")
4. Flash recovery ROM from TWRP & reboot to functional system
I noticed that fastboot ROM uses super.img, which for some reason isn't flashed properly. Recovery ROM flashes /system, /vendor and /odm partitions directly, which overcomes this limitation. If anyone knows why it happens and especially how to use fastboot ROM directly with no extra steps, please share it.

_mysiak_ said:
I was on stock ROM (12.0.8.0 QJSEUXM) and noticed that v12.0.9.0 is out for some time already, but not offered by system to be installed. In the past with my previous phones when I wanted to "force" the update, I simply downloaded fastboot ROM, flashed it and re-rooted the phone. In a matter of few minutes I had up-to-date and working phone again. Today I tried the same with Mi 10T lite and it failed miserably.
Observed issues:
1. flashing script (flash_all_except_storage.bat) comes with CRCLIST and SPARECRCLIST commands which are either not understood by phone (fastbootd), or fail verification (fastboot)
2. after modification of script and removal of beforementioned lines, flashing completes, however phone stays in bootloop showing just Mi logo
3. using different PC, USB port, USB cable, fastboot version, fastbootd/fastboot mode, driver version, Mi flash,.. result always in the same non-functional phone
4. after booting to TWRP (fastboot boot twrp.img), internal data gets decrypted correctly, but TWRP reports issue mounting /odm
5. flashing different ROM version results in the very same issue
Fix:
1. Flash stock ROM (in my case 12.0.8.0)
2. Download recovery ROM (12.0.9.0) and put it to internal SD (you can do it in advance or through TWRP when the phone is already "soft-bricked")
3. Flash recovery ROM from TWRP & reboot to functional system
I noticed that fastboot ROM uses super.img, which for some reason isn't flashed properly. Recovery ROM flashes /system, /vendor and /odm partitions directly, which overcomes this limitation. If anyone knows why it happens and especially how to use fastboot ROM directly with no extra steps, please share it.
Click to expand...
Click to collapse
I tried to flash firmware rom with mi flash tool, but there error too, maybe i am errorman
i will try one more time, keep your fingers to me

NeverMind._. said:
I tried to flash firmware rom with mi flash tool, but there error too, maybe i am errorman
Click to expand...
Click to collapse
What error? You might need to modify your flashing script and remove lines mentioning CRCLIST and SPARECRCLIST.

_mysiak_ said:
What error? You might need to modify your flashing script and remove lines mentioning CRCLIST and SPARECRCLIST.
Click to expand...
Click to collapse
I will do it on my notebook, if it will show error i will show you it, btw thx for helping me

wtf, i flashd with mi flash tool, after 6 minutes, it shows error, phone is showing redmi lol
btw it works, but now i have redmi 10t lite
{
"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"
}

try this program QPST_2.7.496

i need help. After a failed attempt of flash. My phone stuck on fast boot screen not found in MI flash too. i installed adb again still not appear in mi flash tool. I can enter recovery mode but still not appear in mi flash tool. I only have stock recovery

kammgl said:
i need help. After a failed attempt of flash. My phone stuck on fast boot screen not found in MI flash too. i installed adb again still not appear in mi flash tool. I can enter recovery mode but still not appear in mi flash tool. I only have stock recovery
Click to expand...
Click to collapse
For flashing you need to be in fastboot mode. If your phone is not detected correctly, most probably you have incorrect drivers installed (ADB instead of fastboot). Check from command line "fastboot devices" - you should see your phone connected. If it's missing, check your drivers in Windows device manager.

Can you attach picture , of how many lines did you remove? I have 4 lines with spare and crc

tze_vitamin said:
Can you attach picture , of how many lines did you remove? I have 4 lines with spare and crc
Click to expand...
Click to collapse
Might be easier for you to show the lines.. I removed only 2 lines, but maybe there are more with more recent ROMs.

_mysiak_ said:
Might be easier for you to show the lines.. I removed only 2 lines, but maybe there are more with more recent ROMs.
Click to expand...
Click to collapse
I remove 4 lines but still have the same issue. I reopen MI flash tools, upload ROM again,and still showing the same error, I will upload pics later

I was using my phone normally, I left it charging and when I looked at it again, it would restart non-stop. It's a Xiaomi Mi 10T Lite, I held the power button, but it didn't turn on, it just came back to the bootloader screen, I didn't try to format it as I was trying to recover my files.
So I thought about unlocking the bootloader to get access to my files, I used Mi Unlock Tool, but it doesn't work. I still have access to my account phone number and email address. But I couldn't unlock by this method.
Please I need your help. Thank you

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.