Develop Bugs

How to Root Desire EYE [Simple Guide]

Rooting your device may cause loss of warranty.
1. Check your device model - This guide is for HTC Desire Eye and its variants including AT&T Model and International Unlocked Model only.
2. Backup - Backup is mandatory since bootloader unlock will erase your device to factory.
Requirentments- First you should have bootloader unlocked device. (Please visit "http://www.htcdev.com/bootloader" to unlock your bootloader)
Installed ADB Drivers and files - tool can found here, link - https://drive.google.com/file/d/0B9SWmcUAdoOnOVpITTVtcFZUZUk/view?usp=sharing
Download your recovery.img here, link - https://drive.google.com/file/d/0B9SWmcUAdoOnc3hOLXpWVVFIc2c/view?usp=sharing
Super SU & binary here, link - http://download.chainfire.eu/593/SuperSU/BETA-SuperSU-v2.19.zip?retrieve_file=1
Put recovery.img to your ADB folder in PC, and super su to your mobile.
3. Now start command line in the ADB folder where your files located in the PC (Right click + hold down Shift) then "Open command window here"
Guide - http://www.tech-recipes.com/rx/232/right-click-to-open-a-command-prompt/
4. Run following commands to flash recovery.img to your device ( this will replace your original recovery)
fastboot flash recovery recovery.img
Simple.. Now reboot into recovery by pressing power+vol down, then select recovery in the loading screen (if you have any issues rebooting into loader screen please try after disable quick boot in power settings).
5. Now flash your Super SU (Zip) transferred to your mobile by selecting in the recovery.
Everything good to go after reboot.....!!!!

I flashed the recovery image and it keeps coming up with a little screen with a red triangle,any ideas? thanks

pimpsuprazx said:
I flashed the recovery image and it keeps coming up with a little screen with a red triangle,any ideas? thanks
Click to expand...
Click to collapse
Bootloader unlocked?

Can you post a screenshot (PIC) ?

That what happened after flashing the recovery.img and booting into recovery:
{
"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"
}

johnyboo said:
That what happened after flashing the recovery.img and booting into recovery:
Click to expand...
Click to collapse
Same problem here.. Really sad.. Was the recovery image working???

jolishj said:
Same problem here.. Really sad.. Was the recovery image working???
Click to expand...
Click to collapse
Odd that there a few having problems. I s-off'd and had this recovery installed very easily. Are you all still having problems?

unforseenenemy said:
Odd that there a few having problems. I s-off'd and had this recovery installed very easily. Are you all still having problems?
Click to expand...
Click to collapse
the same issue here
like the recovery is not compatible

Try using the recovery found here: http://forum.xda-developers.com/desire-eye/development/recovery-twrp-2-8-4-0-htc-desire-eye-t3008442

I have rooted my phone, But when I uninstall any system app using system app remover after restarting app will be back, and I can't uninstall them.
What's the problem??

karo222 said:
I have rooted my phone, But when I uninstall any system app using system app remover after restarting app will be back, and I can't uninstall them.
What's the problem??
Click to expand...
Click to collapse
System write protection.
There is a mod to disable that here: http://forum.xda-developers.com/des...e-disable-write-protection-v1-0-tool-t2966850
Or use a custom ROM, those have it disabled already.

I went through all the necessary steps. Only thing/issue now is the actual flashing of the root file. It will not take. Anyone else have this issue? Is there a way to get the necessary binary or whatever it's asking for? Thank you in advance.
-Carlos

I have exactly the same issue

hondalude89 said:
I went through all the necessary steps. Only thing/issue now is the actual flashing of the root file. It will not take. Anyone else have this issue? Is there a way to get the necessary binary or whatever it's asking for? Thank you in advance.
-Carlos
Click to expand...
Click to collapse
Only you have to Download BETA-SuperSU-v2.71-20160331103524.zip and flash it. Issue Solved

I did all the steps and everythign went fine, but then I downloaded a RootChecker app and it says I dont have root access. How can I make sure everything worked? NVM I GOT IT FIXED THANX ALOT FOR THIS POST!!!

Shameera_N said:
Rooting your device may cause loss of warranty.
1. Check your device model - This guide is for HTC Desire Eye and its variants including AT&T Model and International Unlocked Model only.
2. Backup - Backup is mandatory since bootloader unlock will erase your device to factory.
Requirentments- First you should have bootloader unlocked device. (Please visit "http://www.htcdev.com/bootloader" to unlock your bootloader)
Installed ADB Drivers and files - tool can found here, link - https://drive.google.com/file/d/0B9SWmcUAdoOnOVpITTVtcFZUZUk/view?usp=sharing
Download your recovery.img here, link - https://drive.google.com/file/d/0B9SWmcUAdoOnc3hOLXpWVVFIc2c/view?usp=sharing
Super SU & binary here, link - http://download.chainfire.eu/593/SuperSU/BETA-SuperSU-v2.19.zip?retrieve_file=1
Put recovery.img to your ADB folder in PC, and super su to your mobile.
3. Now start command line in the ADB folder where your files located in the PC (Right click + hold down Shift) then "Open command window here"
Guide - http://www.tech-recipes.com/rx/232/right-click-to-open-a-command-prompt/
4. Run following commands to flash recovery.img to your device ( this will replace your original recovery)
fastboot flash recovery recovery.img
Simple.. Now reboot into recovery by pressing power+vol down, then select recovery in the loading screen (if you have any issues rebooting into loader screen please try after disable quick boot in power settings).
5. Now flash your Super SU (Zip) transferred to your mobile by selecting in the recovery.
Everything good to go after reboot.....!!!!
Click to expand...
Click to collapse
It is not working on my HTC DESIRE EYE
Error: The code execution cannot proceed because RAPI.DLL was not found.
Troubleshooting steps:
1. Make sure the downloaded file is unzipped
2. USB Debugging enabled
3. On my phone i selected the option, USE USB FOR: "usb file transfer"
4. On my phone I also tried selecting the option, USE USB FOR: "CD Installer"
5. Restart Phone, Mobile and the downloaded file

Please please please help!

So I recently flashed a self made ROM for my watch and it totally bricked it, it cannot boot into a system (just bootloops), Cannot access recovery mode (just turns off and bootloops) and last but not least PC Companion will not detect it. All I have now is fastboot mode so if someone can please help me flash each partition via fastboot that would amazing. I do how ever all of the correct drivers so I am guessing that it will not detect is due to the fact my device has no build.prop.
I really DON'T want to call sony support unless I really have to, so any help would be beyond amazing.
Screenshot from PC Companion:
{
"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"
}
If you need ANYTHING, Video's Pictures, etc feel free to ask as I will try my best to help.

Grab the stock recovery (or the version of twrp) which is appropriate for your build.
Put the watch in fastboot and on your computer in a terminal window type
Code:
fastboot boot <recovery.img>
Then in recovery, install the Os you want.
You have two options. Use stock recovery and then factory reset. Or, use twrp and go all the way back to the 5.0.1 image. If nothing else works. The later will. Do not forget to factory reset after you roll back.

lekofraggle said:
Grab the stock recovery (or the version of twrp) which is appropriate for your build.
Put the watch in fastboot and on your computer in a terminal window type
Code:
fastboot boot <recovery.img>
Then in recovery, install the Os you want.
You have two options. Use stock recovery and then factory reset. Or, use twrp and go all the way back to the 5.0.1 image. If nothing else works. The later will. Do not forget to factory reset after you roll back.
Click to expand...
Click to collapse
Tried it, just reboots

Then you are using the wrong recovery. What did you build?

lekofraggle said:
Then you are using the wrong recovery. What did you build?
Click to expand...
Click to collapse
Well I think what happened is all of the partitions got messed up, does this watch use system.img? Because then I could flash that through FASTBOOT
UPDATE: I got twrp to boot but... It cannot mount any partitions

1619415 said:
Well I think what happened is all of the partitions got messed up, does this watch use system.img? Because then I could flash that through FASTBOOT
UPDATE: I got twrp to boot but... It cannot mount any partitions
Click to expand...
Click to collapse
The closest thing I have seen to a system.img is the roll back zip file of 5.0.1 in this thread
http://forum.xda-developers.com/smartwatch-3/general/guide-roll-watch-to-previous-software-t3176801

I also can't access my SDCard/Internal Storage
UPDATE: I just think I have no OS installed, nothing installed at all actually. So I think I just need to reinstall system and other important data

Okay so that is my guide. Use the 5.0.1 image. I think the issue is precisely that you have no system. A normal flash does not usually touch the boot loader or partition map. So, do not jump to that conclusion yet. If twrp does not work for you, try using the fast boot flash of the 5.0.1 Recovery image.
Which version of twrp worked for you?

lekofraggle said:
Okay so that is my guide. Use the 5.0.1 image. I think the issue is precisely that you have no system. A normal flash does not usually touch the boot loader or partition map. So, do not jump to that conclusion yet. If twrp does not work for you, try using the fast boot flash of the 5.0.1 Recovery image.
Which version of twrp worked for you?
Click to expand...
Click to collapse
The 5.0.1 twrp would not boot but, the 5.1.1 one does just does not mount anything and the stock recovery does not boot either. I did however try to adb sideload stuff but could not find a system.img.

So, what you should try to do is adb push the 5.01 file while booted in the 5.1.1 twrp.
Did you try the 5.1.1 stock recovery? I am not sure it will help even if you get it to boot.

lekofraggle said:
So, what you should try to do is adb push the 5.01 file while booted in the 5.1.1 twrp.
Did you try the 5.1.1 stock recovery? I am not sure it will help even if you get it to boot.
Click to expand...
Click to collapse
I already tried twrp, it can't mount any partitions

Did you try pushing from the computer?
Code:
adb push <originalsystem.zip> /sdcard
If so, what was the exact error you received?

lekofraggle said:
Did you try pushing from the computer?
Code:
adb push <originalsystem.zip> /sdcard
If so, what was the exact error you received?
Click to expand...
Click to collapse
Twrp can't mount anything at all, im guessing that it cannot create a folder on my internal storage. Adb sideload wont work either because it cannot mount

Again, what is the specific error you receive trying adb push (not sideload) after you boot to the somewhat working twrp?

lekofraggle said:
Again, what is the specific error you receive trying adb push (not sideload) after you boot to the somewhat working twrp?
Click to expand...
Click to collapse
error: device not found

Okay, so try adb devices and see if it shows up. If it does, you are correct and need to repartition. That is neither easy nor unrisky. It is easy to brick your device.
If it does not show up, you need to install the drivers. Twrp uses different adb drivers than the watch Os for some reason.

I think this is my main problem...
@lekofraggle

Potentially. What happened when you ran adb devices? You need to do that on your computer.
---------- Post added at 10:16 PM ---------- Previous post was at 10:15 PM ----------
Adb has different permissions than twrp.

Do a format of the system, recovery, userdata and then reinstall from a custom rom online
****************
* SENT FROM *
* A *
* MOD KING *
* DEVICE *
****************

lekofraggle said:
Potentially. What happened when you ran adb devices? You need to do that on your computer.
---------- Post added at 10:16 PM ---------- Previous post was at 10:15 PM ----------
Adb has different permissions than twrp.
Click to expand...
Click to collapse
Either it does not show up or... it just says "error: device not found"

Question Help with recovery installation in POCO F3

Hello everyone, a week ago I just bought a POCO F3, I came from using a Xiaomi Mi 8, the point is that I installed the recovery without problems, however it does not recognize the internal memory, so I cannot install any ROM, I tried deleting data from the recovery (since the internal memory appeared with 0) and the PC did recognize the device, however nothing can be copied to the internal memory.
I leave image of the internal memory, I hope your help, thank you.
{
"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"
}

Dhallex said:
Hello everyone, a week ago I just bought a POCO F3, I came from using a Xiaomi Mi 8, the point is that I installed the recovery without problems, however it does not recognize the internal memory, so I cannot install any ROM, I tried deleting data from the recovery (since the internal memory appeared with 0) and the PC did recognize the device, however nothing can be copied to the internal memory.
I leave image of the internal memory, I hope your help, thank you.
View attachment 5481067
Click to expand...
Click to collapse
Hi, what rom are you using?
Which recovery are you using?
Can't see the memory when you are in recovery or even when the system is booted?
Do you have a password \ pin \ fingerprint as a lock screen?
If you format the data before flashing the rom the recovery does not decrypt the data partition so to flash you have to use the adb sideload method.

RollDload said:
Hi, what rom are you using?
Which recovery are you using?
Can't see the memory when you are in recovery or even when the system is booted?
Do you have a password \ pin \ fingerprint as a lock screen?
If you format the data before flashing the rom the recovery does not decrypt the data partition so to flash you have to use the adb sideload method.
Click to expand...
Click to collapse
Hi
1. Currently I am with the EU ROM, installed via fastboot.
2. I am using the recovery from this link: https://forum.xda-developers.com/t/recovery-11-official-teamwin-recovery-project.4272625/
3. I cannot see the memory only when it is in recovery mode, when I start the system and connect it to the PC, if I can see the internal memory and I can copy and paste files without problems.
4. If I have a password to lock the screen, however when I start the recovery, I do the format data, I don't know if that is right or wrong.
5. The ADB Sideload method is the fastboot method? Since my intention is to install the ROMs by Recovery, since through fastboot I am currently doing it, but some previous ROMs from Xiaomi.eu are not available for Fastboot, especially stable ROMs.
I would greatly appreciate your support. Thanks.

mtp not working in twrp could be a driver issue so try changing the driver.however sometimes its best to just use the usb otg option if you have a flash drive or adapter for one to connect to the phone while in the recovery.
with some roms like lineageos its best to use their recovery and then adb sideload the rom zip.
formating data and then trying to trasnfer a file before booting a rom might also be a virtual a/b issue check vassi twrp thread for notes on these issues

Dhallex said:
Hi
1. Currently I am with the EU ROM, installed via fastboot.
2. I am using the recovery from this link: https://forum.xda-developers.com/t/recovery-11-official-teamwin-recovery-project.4272625/
3. I cannot see the memory only when it is in recovery mode, when I start the system and connect it to the PC, if I can see the internal memory and I can copy and paste files without problems.
4. If I have a password to lock the screen, however when I start the recovery, I do the format data, I don't know if that is right or wrong.
5. The ADB Sideload method is the fastboot method? Since my intention is to install the ROMs by Recovery, since through fastboot I am currently doing it, but some previous ROMs from Xiaomi.eu are not available for Fastboot, especially stable ROMs.
I would greatly appreciate your support. Thanks.
Click to expand...
Click to collapse
Try if you can see the internal memory before formatting the data, (if you don't see it that way either it could be a driver problem as he rightly said @metalspider) after formatting it is normal not to be able to see the internal memory from both twrp and pc.
Anyway, I flashed the stable eu.rom zips by formatting the data after flashing the rom and it works.
Adb sideload is not fastboot, they are two different things and it is used when you format data before flashing the rom and to do so you have to do this:
Put the zip file of the rom in the folder where you have adb and fastboot.
In twrp go to advanced then activate adb sideload
Then on the pc open a cmd window in the folder where you have adb and fastboot and type the command: adb sideload filename.zip

metalspider said:
mtp not working in twrp could be a driver issue so try changing the driver.however sometimes its best to just use the usb otg option if you have a flash drive or adapter for one to connect to the phone while in the recovery.
with some roms like lineageos its best to use their recovery and then adb sideload the rom zip.
formating data and then trying to trasnfer a file before booting a rom might also be a virtual a/b issue check vassi
Click to expand...
Click to collapse
Thanks, I will try to install some MTP driver to see if my device is recognized
Any specific controller that you recommend?

RollDload said:
Try if you can see the internal memory before formatting the data, (if you don't see it that way either it could be a driver problem as he rightly said @metalspider) after formatting it is normal not to be able to see the internal memory from both twrp and pc.
Anyway, I flashed the stable eu.rom zips by formatting the data after flashing the rom and it works.
Adb sideload is not fastboot, they are two different things and it is used when you format data before flashing the rom and to do so you have to do this:
Put the zip file of the rom in the folder where you have adb and fastboot.
In twrp go to advanced then activate adb sideload
Then on the pc open a cmd window in the folder where you have adb and fastboot and type the command: adb sideload filename.zip
Click to expand...
Click to collapse
Thanks, I will test if it works for me and I will be communicating the result. Maybe if none works for me, I will have to take the advice to buy a USB OTG for the process.

the microsoft win 11 driver seems to be working fine for me in twrp-3.6.0_11-0-alioth-Nebrassy for mtp transfers
version 10.022000.1 for both portable devices-->poco F3 and the adb interface driver too

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

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.