Hey Everyone recently my device got stuck at android one logo and so after analyzing it I understood that it was in a hard brick condition. so I tried the Xiaomi Flash Tool to flash the original firmware but every time it had some kind issues such as
1. cannot Flash Bluetooth_a error
2. FAILED (remote: Error flashing partition : Write Protected)
Can anyone suggest me how can I remove this Write Protection.
earlier build - HavacOS ,bootloader unlocked.
PS- Also tried the oem edl mode but it showed an error programmer file not found using the MiFlashTool (Beta) and with the latest build
3. error cannot read from com3 (read hello packet)
Any suggestions would be appreciated.
How did you brick the phone?
Anyway, can you boot into fastboot?
If yes, try booting into TWRP (fastboot boot twrp.img) and use the fix boot loop command.
Exxdeea said:
How did you brick the phone?
Anyway, can you boot into fastboot?
If yes, try booting into TWRP (fastboot boot twrp.img) and use the fix boot loop command.
Click to expand...
Click to collapse
Yes, I can boot into fastboot! but every time it got stuck at the TWRP splash screen/Logo. tried with different versions too.
Also using ( fastboot flash boot_a twrp.img ) and ( fastboot flash boot_b twrp.img) gives an error of write protected .
And as far as how I bricked- I don't have any idea , it was working fine but then suddenly it stooped responding.
(As things usually happen suddenly. )
This looks like the solution:
https://forum.xda-developers.com/mi-a2/how-to/fix-twrp-freeze-splash-logo-t4065173
Exxdeea said:
This looks like the solution:
https://forum.xda-developers.com/mi-a2/how-to/fix-twrp-freeze-splash-logo-t4065173
Click to expand...
Click to collapse
Thanks for replying but still no hope.
here is another error.
Allocating group tables: done
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'cache' (56 KB) FAILED (remote: 'Error: Last flash failed : Write Protected')
fastboot: error: Command failed
Write protected. How can I remove This?
Same Problem
Try using 4pda version which is X.X.X.X-5. That worked for me. Also, try switch slot a/b from fastboot
Pandu Ahbar said:
Same Problem
Click to expand...
Click to collapse
What does "fastboot getvar unlocked" say?
If you are sure that you have previously unlocked phone:
1. maybe try to lock and then unlock again with
fastboot flashing unlock
and
fastboot flashing unlock_critical
2. try to flash stock, forget about miflash, use fastboot from latest platform tools
If you have not unlocked phone before, and have not set "OEM unlock" in Settings -> Developer, and rebooting 7+ times does not switch A/B slots into working ROM, then look into TestPoint/EDL guide.
Death_17 said:
Yes, I can boot into fastboot! but every time it got stuck at the TWRP splash screen/Logo. tried with different versions too.
Also using ( fastboot flash boot_a twrp.img ) and ( fastboot flash boot_b twrp.img) gives an error of write protected .
And as far as how I bricked- I don't have any idea , it was working fine but then suddenly it stooped responding.
(As things usually happen suddenly. )
Click to expand...
Click to collapse
Same problam bro how can i solve i don't know and i also use last time havoc os
have you tried test point method?
Death_17 said:
Yes, I can boot into fastboot! but every time it got stuck at the TWRP splash screen/Logo. tried with different versions too.
Also using ( fastboot flash boot_a twrp.img ) and ( fastboot flash boot_b twrp.img) gives an error of write protected .
And as far as how I bricked- I don't have any idea , it was working fine but then suddenly it stooped responding.
(As things usually happen suddenly. )
Click to expand...
Click to collapse
Aerobatic said:
What does "fastboot getvar unlocked" say?
If you are sure that you have previously unlocked phone:
1. maybe try to lock and then unlock again with
fastboot flashing unlock
and
fastboot flashing unlock_critical
2. try to flash stock, forget about miflash, use fastboot from latest platform tools
If you have not unlocked phone before, and have not set "OEM unlock" in Settings -> Developer, and rebooting 7+ times does not switch A/B slots into working ROM, then look into TestPoint/EDL guide.
Click to expand...
Click to collapse
Vishal656 said:
Same problam bro how can i solve i don't know and i also use last time havoc os
Click to expand...
Click to collapse
have you tried test point method?
Same problem for me write protected error
How to fix it
Death_17 said:
Yes, I can boot into fastboot! but every time it got stuck at the TWRP splash screen/Logo. tried with different versions too.
Also using ( fastboot flash boot_a twrp.img ) and ( fastboot flash boot_b twrp.img) gives an error of write protected .
And as far as how I bricked- I don't have any idea , it was working fine but then suddenly it stooped responding.
(As things usually happen suddenly. )
Click to expand...
Click to collapse
Same problem any suggestions how to fix this
same problem someone give solution
try flashing "super_empty.img" file then install your current ROM through pixel experience recovery
blacksrj531 said:
try flashing "super_empty.img" file then install your current ROM through pixel experience recovery
Click to expand...
Click to collapse
Bro you don,t understand it's write protected
Related
I dirty flashed a new version of xiaomi.eu stable build, and it caused TWRP to uninstall itself.
Whenever I hold power on and volume up it just goes to fastboot.
Now I tried reinstalling TWRP like I've done many times before, but it keeps throwing an error. The error I get is when trying to boot without flashing the img. When I do this, I get the error:
Code:
fastboot boot TWRP.img"
downloading 'boot.img'...
OKAY [ 1.609s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.675s
Anyone gotten any ideas on what could be going on here? I'm scared to try anything as my phone currently works, but I need TWRP back to update my phone to a different versions and to install the clock mod again.
Thanks!
Got it to load once, but now back to square one. Throwing same error.
Now when running the command fastboot reboot recovery it's saying
Code:
fastboot: usage: unknown reboot target recovery
And writing 'fastboot boot twrp.img' turns the phone off / makes the screen go black. Fully bricked now as the OS wont load either.
Try on a computer with a USB 2.0 port, or a different usb cable, had the same issue once
Ended up having to reinstall dev rom. Device relocked, so have to wait 15 days again. @BusterBg_18 Thanks, will do when I unlock the device
EDIT: When using Mi Flash tool, make sure to check 'clean all' and not 'clean all and lock' in the bottom right. That's what set me back 2 weeks.
I have the same error. How can I fix this pls?
MrkoZino said:
I have the same error. How can I fix this pls?
Click to expand...
Click to collapse
Flash the latest official rom then start all over again. Follow the post above you about miflash.
Hello, I've had the same problem, then flashed latest dev rom via MiFlash and it booted, but now after I flash any custom ROM in TWRP i have this issue again and need to reflash chinese ROM. How can I flash any custom rom?
i'm stuck in the same issue. stuck in fastboot and it would not load recovery. any fix?
Hi, i fixed the "Failed to load/authenticate boot image: Load Error" by simply restarting the Device.
It seems to appear randomly when flashing partitions and then block all further Transfers.
If the Device loops in Fastboot, the only Solution to me was re flashing the Stock Firmware.
greendra8 said:
And writing 'fastboot boot twrp.img' turns the phone off / makes the screen go black. Fully bricked now as the OS wont load either.
Click to expand...
Click to collapse
I have the same Issue, but reflashing Stock Firmware or making OTA Updates dident helped for me. Ive already tried TWRP and OrangeFox without success. The Screen always turns black and Fastboot stays active in an limited Mode, any Ideas? My host Computer only has 3.0+ Ports only, but ive used an 2.0 Extender so it should be fine?
DJPlaya said:
Hi, i fixed the "Failed to load/authenticate boot image: Load Error" by simply restarting the Device.
It seems to appear randomly when flashing partitions and then block all further Transfers.
If the Device loops in Fastboot, the only Solution to me was re flashing the Stock Firmware.
I have the same Issue, but reflashing Stock Firmware or making OTA Updates dident helped for me. Ive already tried TWRP and OrangeFox without success. The Screen always turns black and Fastboot stays active in an limited Mode, any Ideas? My host Computer only has 3.0+ Ports only, but ive used an 2.0 Extender so it should be fine?
Click to expand...
Click to collapse
long time ago now. but i remember at one point having to flash the stock firmware using the mi unlock tool. i also remember trying every single version of twrp and rom until one finally worked. sorry i can't help much but i believe that's how i eventually fixed it.
hi, I've experienced with the same thing.
this methode help me out from it.
try to reflashing some file image from the rom where youre want to install in hh with adb.
copy this files below from rom image to adb folder
1. system.img (command in adb >> fastboot flash system system.img)
2. boot.img (command in adb like #1, change the name of img file) do till #6
3. vendor.img
4. dtbo.img
5. cust.img
6. misc.img
7. now flashing twrp/recovery.img (choose twrp compatible with rom you want to install) with adb
8. the "fastboot boot recovery.img" with adb
9. flashing the rom by twrp
Marihot said:
hi, I've experienced with the same thing.
this methode help me out from it.
try to reflashing some file image from the rom where youre want to install in hh with adb.
copy this files below from rom image to adb folder
1. system.img (command in adb >> fastboot flash system system.img)
2. boot.img (command in adb like #1, change the name of img file) do till #6
3. vendor.img
4. dtbo.img
5. cust.img
6. misc.img
7. now flashing twrp/recovery.img (choose twrp compatible with rom you want to install) with adb
8. the "fastboot boot recovery.img" with adb
9. flashing the rom by twrp
Click to expand...
Click to collapse
Where do you get these .img files?
iconoclasthero said:
Where do you get these .img files?
Click to expand...
Click to collapse
all img files come from the official rom china stable V12.0.2.0.QEBCNXM (.tgz), download and extract the tgz file then find img files from images folder
Marihot said:
all img files come from the official rom china stable V12.0.2.0.QEBCNXM (.tgz), download and extract the tgz file then find img files from images folder
Click to expand...
Click to collapse
Please tell the details for this method
greendra8 said:
Ended up having to reinstall dev rom. Device relocked, so have to wait 15 days again. @BusterBg_18 Thanks, will do when I unlock the device
EDIT: When using Mi Flash tool, make sure to check 'clean all' and not 'clean all and lock' in the bottom right. That's what set me back 2 weeks.
Click to expand...
Click to collapse
BROOOOOOOOOO HAHAHAHAHAHA I LITERALLY JUST READ YOUR COMMENT AND 10 SECONDS LATER I FLASH THE ROM WITH "CLEAN ALL AND LOCK" Im a f-king dumb bro
Marihot said:
你好，我也经历过同样的事情。
这个方法帮助我摆脱它。
尝试使用 adb 从要在 hh 中安装的 rom 中重新刷新一些文件映像。
将下面的文件从 rom 映像复制到 adb 文件夹
1.system.img（adb >> fastboot flash system system.img中的命令）
2. boot.img（adb 中的命令，如#1，更改 img 文件的名称）直到 #6
3. 供应商.img
4.dtbo.img
5. 自定义.img
6. 杂项.img
7. 现在用adb刷twrp/recovery.img（选择twrp与你要安装的rom兼容）
8. adb 的“fastboot boot recovery.img”
9. twrp刷入rom
Click to expand...
Click to collapse
Thank you, brother
try fastboot set_active a
or fastboot set_active b
Can anyone tell me what this (remote: Flashing is not allowed in Lock State).
What exactly is locked? Is my cell OEM unlocked?
I flashed the wrong TWRP (for the 2017 Red Magic-NX209J) and even though I have been able to unlock my cell via CMD commands; it remains permanently in fastboot mode?
If I send a CMD command to reboot it reboots straight back to fastboot mode.
No form of ADB connect seems to work an my windows PC cannot see/show the cell?
How the hell do I fix this? It's been in this state for a week.
Can anyone help?
Meaby try this?
Then, to unlock your bootloader, enter "fastboot oem nubia_unlock NUBIA_NX629J"
And meaby try the recovery backup instead of TWRP.
xronaldx said:
Meaby try this?
Then, to unlock your bootloader, enter "fastboot oem nubia_unlock NUBIA_NX629J"
And meaby try the recovery backup instead of TWRP.
Click to expand...
Click to collapse
Thanks for the suggestion. I have no recovery back up Is it possible to get past TWRP being locked and use CMD to flash the International or chinese ROM? Or recovery image?
Unless tools are developed to unbrick this device I am scared this problem might be permanent
Download this twrp, and then upload it to google drive or something so the rest of us can download it too .
Password is: 6i3i
https://pan.baidu.com/s/1ZdMPjm2fEwt...06770439204444
Secretcow said:
Download this twrp, and then upload it to google drive or something so the rest of us can download it too .
Password is: 6i3i
https://pan.baidu.com/s/1ZdMPjm2fEwt...06770439204444
Click to expand...
Click to collapse
Thanks but what do i do with it? Its all in an asain language?
Link not open bro
The TWRP does not work
Sorry. That link to the twrp does not result in a bootable twrp recovery for me.
I am starting to think my cell is not fixable.
I did not do that much wrong I just flashed the twrp for 2 models of red magic earlier. It only has a fastboot mode. I either get a boot screen then fastboot mode or a warning about the bootloader being unlocked.
Whatever is wrong with my cell prevents ADB connect an the cell is not able to be seen by windows.
This $1100 New Zealand dollar cellphone may be permanently bricked by my mistake.
I might just need to bin it an buy another one.
Lesson learned.
It confusing....
My cell acts like it has a softbrick (can turn off an on an has fastboot options and I have erased it an OEm an bootloader unlocked it)
And also behaves like a hard brick (resists every method of repair).
I just do not understand it or Nubia products. I am unfamiliar with this phone.
Does anyone have any clue how I can see this cell on my windows pc or ADB connect it an boot into TWRP?
Are there any Nubia repair software tools?
I already share nubia red magic 3 twrp check my all post
sandeepkhatri said:
I already share nubia red magic 3 twrp check my all post
Click to expand...
Click to collapse
Thanks for that. I'm talking about using CMD to totally wipe everything in the cell an reflash the Chinese ROM that came with it. Repair software. Might take months to develop software like that.
sandeepkhatri said:
I already share nubia red magic 3 twrp check my all post
Click to expand...
Click to collapse
Also it isn't a zip. It's some other kind of file. And does not boot into TWRP on my unit
So are you able to unlock your bootloader in its current state?
If you have an older TWRP installed maybe try changing the model on your bootloader command to match it:
fastboot oem nubia_unlock NUBIA_NX209J
If this works then flash the correct TWRP and the boot IMG from your original rom
fastboot flash recovery <new recovery>
fastboot reboot bootloader
Sent from my NX629J using Tapatalk
terrapin4 said:
So are you able to unlock your bootloader in its current state?
If you have an older TWRP installed maybe try changing the model on your bootloader command to match it:
fastboot oem nubia_unlock NUBIA_NX209J
If this works then flash the correct TWRP and the boot IMG from your original rom
fastboot flash recovery <new recovery>
fastboot reboot bootloader
Click to expand...
Click to collapse
Terrapin. Absolutely nothing worked. I am the 3rd person who has had this issue I know of. 2 other xda members had the same issue. One with TWRP like me an the other got stuck in fastboot mode after trying g to flash an apk of Gapps? I think these cells do not like tinkering. But your advice enabled me to be OEM and bootloader unlocked. But always.....straight back to fastboot mode no matter what I flash? My red magic 3 device is currently at a service center with a technician trying to solve the problem. I have 3 repayments left on my Xiaomi Mi9 that has zero flashing issues. O admit i.may be ignorant of the ways of Nubia ?
I did it
I extracted the file system.img
this is what I did ....
starting from the Chinese ROM http://ui.nubia.cn/rom/detail/62
Download download necessary files https://drive.google.com/drive/folders/16in6Jnyi4s5aIIuQwapQ1KK1LjysSfYm?usp=sharing
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash parameter parameter.img
fastboot reboot
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash modem NON-HLOS.bin
fastboot flash system system.img
fastboot reboot
enter recovery, use a FAT32 pendrive format, add Chinese ROM, rename it (update.zip) to OTG flash.
Everything works again.
good luck.
emmegitony said:
I did it
I extracted the file system.img
this is what I did ....
starting from the Chinese ROM http://ui.nubia.cn/rom/detail/62
Download download necessary files https://drive.google.com/drive/folders/16in6Jnyi4s5aIIuQwapQ1KK1LjysSfYm?usp=sharing
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash parameter parameter.img
fastboot reboot
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash modem NON-HLOS.bin
fastboot flash system system.img
fastboot reboot
enter recovery, use a FAT32 pendrive format, add Chinese ROM, rename it (update.zip) to OTG flash.
Everything works again.
good luck.
Click to expand...
Click to collapse
Thank God. Maybe the Chinese service guy I'm paying will get on xda an try your idea. I'm being lazy saying that lol. Thanks very very much. I will show your post to the service guy who has my red magic 3 or try it myself.
There's no way your a junior member working all this out. I'm a junior member listed as a senior member who makes rookie flashing errors with Chinese cellphones lol.
I will share if I can implement your ideas successfully. Thanks buddy my missus really loved this phone I felt really bad when I incapacitated it.
Fingers crossed.....
I have no idea how did you managed to flash the system.img
C:\adb>fastboot flash system system.img
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
LE: After this error, somehow it manages to continue and flash all partitions of the system, but after above tutorial, the phone still reboots in fastboot mode and cannot access recovery
The solution is here:
https://forum.xda-developers.com/re...tboot-mode-t3937527/post79715050#post79715050
sakilxda said:
The solution is here:
https://forum.xda-developers.com/re...tboot-mode-t3937527/post79715050#post79715050
Click to expand...
Click to collapse
Thanks for the help. I do not understand some of the commands an cannot seem to get them right? And I do not understand why the instructions say to cmd flash the image (IMG) via command prompt (which just errors like the strange NON-HLOS command?) Then the instructions say to flash the Chinese rom via otg?
Are you supposed to flash the ROM twice?
Can someone please give me some more detailed instructions as this cell has been non functional about 2 months now.
Planning to fix it an give it to my partner
Bryceicle1971 said:
Thanks for the help. I do not understand some of the commands an cannot seem to get them right? And I do not understand why the instructions say to cmd flash the image (IMG) via command prompt (which just errors like the strange NON-HLOS command?) Then the instructions say to flash the Chinese rom via otg?
Are you supposed to flash the ROM twice?
Can someone please give me some more detailed instructions as this cell has been non functional about 2 months now.
Planning to fix it an give it to my partner
Click to expand...
Click to collapse
Hane you fixed the phone or not?
JerryYin said:
Hane you fixed the phone or not?
Click to expand...
Click to collapse
No still not working. Might try again when I have spare time. Very hard cellphone to fix
Bryceicle1971 said:
No still not working. Might try again when I have spare time. Very hard cellphone to fix
Click to expand...
Click to collapse
My suggestions is, download a full sd card update package, unlock the bootloader temporarily,extract the update file and flash the vbmeta.img to vbmeta partion, then flash the recovery.img to recovery partition, after that, try to boot into recovery through bootloader. You have to make sure that you use all the same file from same package, if you are use a low version vbmeta file to boot a high version system (or recovery ) it will not boot. the vbmeta is very important on this phone.
Can't even fastboot flash boot recovery system...and thats all folks...waste of money.
Failed attempt to unlock the bootloader and instal TWRP ?
Hi guys, visit this link. We had similar problems and we could solved that.
Read all and you would get the solution
https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527/page9
roadworker said:
Failed attempt to unlock the bootloader and instal TWRP ?
Click to expand...
Click to collapse
No I installed Chinese v2.27.... Well it's absolute mess like I never seen Android before. Then attempted to flash global again, problems to the point of corruption. I have fastboot flashed all key elements of working Android phone multiple times. Can only get to fastboot after boot screen that I have to do manually. Recovery system is toast.... Guess it's back to Poco F1.... Learned my lesson from junk.
Just flash the ROM again..It will be back lm
mhex said:
Just flash the ROM again..It will be back lm
Click to expand...
Click to collapse
Trying to NA Global original rom, problem is no recovery at all....I can only flash within fastboot.....which is not a problem, but phone is not taking it flashing all images individually and modem. And I know it's flashing cause fastboot is saying okay and bootloader showing unlocked
SuperDroidMe said:
Trying to NA Global original rom, problem is no recovery at all....I can only flash within fastboot.....which is not a problem, but phone is not taking it flashing all images individually and modem. And I know it's flashing cause fastboot is saying okay and bootloader showing unlocked
Click to expand...
Click to collapse
Every time you restart back to the bootloader you need to do: "fastboot oem nubia_unlock NUBIA_NX629J" first
SuperDroidMe said:
No I installed Chinese v2.27.... Well it's absolute mess like I never seen Android before. Then attempted to flash global again, problems to the point of corruption. I have fastboot flashed all key elements of working Android phone multiple times. Can only get to fastboot after boot screen that I have to do manually. Recovery system is toast.... Guess it's back to Poco F1.... Learned my lesson from junk.
Click to expand...
Click to collapse
So YOU mess up your phone by trying to flash sh!t and you blame the MANUFACTURER? Yeah ok. Lmao. Enjoy the new paperweight that YOU CREATED.
xphyle1971 said:
So YOU mess up your phone by trying to flash sh!t and you blame the MANUFACTURER? Yeah ok. Lmao. Enjoy the new paperweight that YOU CREATED.
Click to expand...
Click to collapse
LMAO if you can't go from stock global to stock Chinese and reverse from the manufacturer with their recovery, you haven't got a prayer for custom roms or mods.
SuperDroidMe said:
LMAO if you can't go from stock global to stock Chinese and reverse from the manufacturer with their recovery, you haven't got a prayer for custom roms or mods.
Click to expand...
Click to collapse
if you stuck in the Device is corrupt. It can't be trusted and will not boot and you are in the Chinese or global rom then flash the stock boot image via adb. well I am using a Chinese v2.27 rom with rooted +gapps and then realized that most of the google apps wont work correctly because of the unlocked bootloader. I tried to lock the bootloader via adb then the message "Device is corrupt. It can't be trusted and will not boot" show up. so I try to use adb to flash the stock boot image then it work. first place the stock boot image to the "Minimal ADB and Fastboot" folder which located in the local drive under program file(x86) then run the command
fastboot flash boot boot.img
fastboot reboot
mswl04 said:
if you stuck in the Device is corrupt. It can't be trusted and will not boot and you are in the Chinese or global rom then flash the stock boot image via adb. well I am using a Chinese v2.27 rom with rooted +gapps and then realized that most of the google apps wont work correctly because of the unlocked bootloader. I tried to lock the bootloader via adb then the message "Device is corrupt. It can't be trusted and will not boot" show up. so I try to use adb to flash the stock boot image then it work. first place the stock boot image to the "Minimal ADB and Fastboot" folder which located in the local drive under program file(x86) then run the command
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
Bud I put so much effort in last 13 hours to no avail....fastboot erased all partitions, reformatted, reflashed to no avail. Right now it just boots loops on Chinese 2.27 boot splash, I do have Chinese recovery though, but the same otg adapter and pen drive that works on 5 different devices, this damn phone won't read it so even that is out of the question. I wipe my hands clean of it, some things just best to put a bullet through it.
SuperDroidMe said:
Bud I put so much effort in last 13 hours to no avail....fastboot erased all partitions, reformatted, reflashed to no avail. Right now it just boots loops on Chinese 2.27 boot splash, I do have Chinese recovery though, but the same otg adapter and pen drive that works on 5 different devices, this damn phone won't read it so even that is out of the question. I wipe my hands clean of it, some things just best to put a bullet through it.
Click to expand...
Click to collapse
btw did you rooted the phone?
mswl04 said:
btw did you rooted the phone?
Click to expand...
Click to collapse
No BS, all I did was flash CN 2.27 over NA Global, after a look at the mess it was I proceeded to flash NA Global back.....no TWRP No Root with SuperSU or Magisk. But in fastboot it does say Root=1, so I guess the CN 2.27 rooted it by default cause I sure as hell didn't. One thing that is bothering me while in fastboot unlock bootloader I can't turn Secure Boot off which I believe is why it won't boot system.
SuperDroidMe said:
No BS, all I did was flash CN 2.27 over NA Global, after a look at the mess it was I proceeded to flash NA Global back.....no TWRP No Root with SuperSU or Magisk. But in fastboot it does say Root=1, so I guess the CN 2.27 rooted it by default cause I sure as hell didn't. One thing that is bothering me while in fastboot unlock bootloader I can't turn Secure Boot off which I believe is why it won't boot system.
Click to expand...
Click to collapse
don't give up I know how do you feel did you download this update from the official red magic website http://ui.nubia.cn/rom/detail/62 after you download the update and it will be in a zip file extract the boot image. then try to follow the root guild https://forum.xda-developers.com/red-magic-3/how-to/red-magic-3-root-guide-t3933148 in the website download the adb and then run the command which I reply earlier
seem to me it is like a soft brick
mswl04 said:
don't give up I know how do you feel did you download this update from the official red magic website http://ui.nubia.cn/rom/detail/62 after you download the update and it will be in a zip file extract the boot image. then try to follow the root guild https://forum.xda-developers.com/red-magic-3/how-to/red-magic-3-root-guide-t3933148 in the website download the adb and then run the command which I reply earlier
seem to me it is like a soft brick
Click to expand...
Click to collapse
I got CN version 2.27 images, am I supposed to be using one of the other versions off the official site?
SuperDroidMe said:
I got CN version 2.27 images, am I supposed to be using one of the other versions off the official site?
Click to expand...
Click to collapse
all you need to do is to fix the corrupt image so later once you finish the first step of booting to the phone then you can flash to global rom. if you have the cn version 2.27 boot.img then you can download the adb and use the command to fix the phone
Shouldn't have messed with something that wasn't broken. Now you have a nice brick to use as a paperweight. Hope you get it fixed tho. Good luck.
Solved Instructions:
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash parameter parameter.img
fastboot reboot bootloader
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash modem NON-HLOS.bin
fastboot flash system system.img
fastboot flash dsp dspso.bin
fastboot oem nubia_lock NUBIA_NX629J
fastboot reboot
*****as soon as boot screen appears hold volume + button, now in recovery...navigate to wipe data and then wipe cache....then plug in otg usb pen drive (formatted FAT32) with Rom package .zip....navigate to update otg in recovery select it let it do its thing and walla your phone is fixed.
*****if you ever go from CN rom to Global rom you must Wipe Data and Cache through recovery, it is not enough to do it in fastboot and your device will remain soft bricked.
SuperDroidMe said:
Solved Instructions:
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash parameter parameter.img
fastboot reboot bootloader
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash modem NON-HLOS.bin
fastboot flash system system.img
fastboot flash dsp dspso.bin
fastboot oem nubia_lock NUBIA_NX629J
fastboot reboot
*****as soon as boot screen appears hold volume + button, now in recovery...navigate to wipe data and then wipe cache....then plug in otg usb pen drive (formatted FAT32) with Rom package .zip....navigate to update otg in recovery select it let it do its thing and walla your phone is fixed.
*****if you ever go from CN rom to Global rom you must Wipe Data and Cache through recovery, it is not enough to do it in fastboot and your device will remain soft bricked.
Click to expand...
Click to collapse
Congrat you finally fix it
Hows your phone?..Did it work.
it says your device is corrupt. it cant be trusted
how to fix it please help me how to start phone , i tryed some solution to flash and all that but nothing worked
I think u also same mistake. Before install cn rom. U not enable oem unlock option in davoloper features
brawlhack said:
it says your device is corrupt. it cant be trusted
how to fix it please help me how to start phone , i tryed some solution to flash and all that but nothing worked
Click to expand...
Click to collapse
Few days before I was in the same situation.
Tried lot of solution but the simplest to solve was using the below 2 command when in fastboot.
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flashing unlock
This should unlock the bootloader and you should be able continue the setup.
All the Best...
it says flashing unlock is not allowed
rajnathr said:
Few days before I was in the same situation.
Tried lot of solution but the simplest to solve was using the below 2 command when in fastboot.
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flashing unlock
This should unlock the bootloader and you should be able continue the setup.
All the Best...
Click to expand...
Click to collapse
it says flashing unlock is not allowed
Same thing happened to me, tried all the recommendations given on this site, none works . Any help will be appreciated, now i have a paper weight
re-flashed the phone using the first version of the Chinese ROM v2.12 now can use the OTG update option. just need to get a usb adapter now
Which files i need to flash
Steffran said:
re-flashed the phone using the first version of the Chinese ROM v2.12 now can use the OTG update option. just need to get a usb adapter now
Click to expand...
Click to collapse
Can you tell full step and i guess i need system.img also where i can get it ...kindly please help sir ?
https://drive.google.com/drive/folders/16in6Jnyi4s5aIIuQwapQ1KK1LjysSfYm
Here is the link to download required file by an XDA member.
But before you flash system image first try with the boot img and recovery img.
I was to getting the message that i cant flash so used the command for oem unlock which reset the counter to 1
After which did flashing of boot .img and then recovery.img
If issue the use the falshboot flashing unlock.
This were the steps used by me to recovery, i didnot do any other flashing.
Hope this helps you
Edit: After the oem unlock command directly try to flash boot and then recovery and then if required flashing unlock command.
its still saying your device is corrupt ...anyone can help me
rajnathr said:
https://drive.google.com/drive/folders/16in6Jnyi4s5aIIuQwapQ1KK1LjysSfYm
Here is the link to download required file by an XDA member.
But before you flash system image first try with the boot img and recovery img.
I was to getting the message that i cant flash so used the command for oem unlock which reset the counter to 1
After which did flashing of boot .img and then recovery.img
If issue the use the falshboot flashing unlock.
This were the steps used by me to recovery, i didnot do any other flashing.
Hope this helps you
Edit: After the oem unlock command directly try to flash boot and then recovery and then if required flashing unlock command.
Click to expand...
Click to collapse
its not booting after doing that please help me if possible can we talk in discord
using cm
fastboot oem nubia_unlock NUBIA_NX629J
fastboot -w
reboot phone done
after this
nil3m1 said:
using cm
fastboot oem nubia_unlock NUBIA_NX629J
fastboot -w
reboot phone done
Click to expand...
Click to collapse
after this i need to flash boot and recovery img ?
Hi,
First of all, I hope this is the correct place to ask for help. I didn't see a better place
I own a honor 9 lite phone. I opened bootloader using PotatoNV and testpoints. Everything worked like a charm
But yesterdayy I tried to update it to Treble and after flashing a rom, I faced this error just after restarting the phone:
ERROR MODE
Attention!
Please update system again
Error!
Func NO : 15 (bl31 image)
Func NO : 1 (security verify failed!)
And it keeps restarting all the time
I tried to flash system image from multiple roms, even stock. Also I tried to flash multiple recovery images, boot images, and so on.. but nothing seems to work
The only way I can use thee phone is via fastboot. NO TWRP and no OFFICIAL RECOVERY using Vol+ and Vol-
Please, I need you help
Thank you in advance
Regards
oloco2 said:
Hi,
First of all, I hope this is the correct place to ask for help. I didn't see a better place
I own a honor 9 lite phone. I opened bootloader using PotatoNV and testpoints. Everything worked like a charm
But yesterdayy I tried to update it to Treble and after flashing a rom, I faced this error just after restarting the phone:
ERROR MODE
Attention!
Please update system again
Error!
Func NO : 15 (bl31 image)
Func NO : 1 (security verify failed!)
And it keeps restarting all the time
I tried to flash system image from multiple roms, even stock. Also I tried to flash multiple recovery images, boot images, and so on.. but nothing seems to work
The only way I can use thee phone is via fastboot. NO TWRP and no OFFICIAL RECOVERY using Vol+ and Vol-
Please, I need you help
Thank you in advance
Regards
Click to expand...
Click to collapse
Hi,
in fastboot mode run commands :
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
Some might fail, so don't worry about it.
Try something from the following:
A) in fastboot mode use command
fastboot erase userdata
reboot and try to flash stock recovery_ramdisk and flash full stock FW via dload
B) try to update your phone via eRecovery - turn off, plug the cabel and press and hold Power + Vol Up. In eRecovery's menu select "Download latest etc etc."
C) fully discharge the battery and try previous methods
(in your case little chance, this method works with error 11/2, you have 15/1)
D) use testpoint method
E) paid services (dc-phoenix etc.)
Thank so much for your help -Alf-
Unfortunally I have to say that now my phone is not able to enter fastboot mode.
What I dd:
The comands you asked for:
fastboot oem get-build-number
(bootloader) :System 8.0.0.046(0JRE)
OKAY [ 0.007s]
Finished. Total time: 0.009s
fastboot oem get-product-model
(bootloader)
OKAY [ 0.006s]
Finished. Total time: 0.009s
fastboot getvar vendorcountry
vendorcountry: hw/eu
fastboot oem oeminforead-CUSTOM_VERSION
FAILED (remote: 'The reason of failed input oem_nv_item error!')
fastboot: error: Command failed
fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :STF-L09C10B100a
OKAY [ 0.008s]
Finished. Total time: 0.009s
As nothing changed, I used testpoints.
I had to enter fastboot oem unlock 5KKK7... in order to unlock bootloader again
But now.. Phone keeps rebooting with the same eror window as before, but I'm still unable to ener not fastboot mode not erecovery.
Now i really feel locked, as I think there's nothin else I can do.
I also unplugged battery multiple times in order to discharge all the circuit, but no news...
Any other idea, please?
Regards
oloco2 said:
Unfortunally I have to say that now my phone is not able to enter fastboot mode
Click to expand...
Click to collapse
oloco2 said:
The only way I can use thee phone is via fastboot.
Click to expand...
Click to collapse
?
Before using potatonv I was able to enter fastoot mode and perform some commands.
Now, after using it, the phone just keeps rebooting showing the errors, but even if I press the buttons, no fastboot/twrp mode...
oloco2 said:
Before using potatonv I was able to enter fastoot mode and perform some commands.
Now, after using it, the phone just keeps rebooting showing the errors, but even if I press the buttons, no fastboot/twrp mode...
Click to expand...
Click to collapse
Try this method - turn off, hold Volume Down and plug the cabel.
oloco2 said:
System 8.0.0.046(0JRE
Click to expand...
Click to collapse
oloco2 said:
fastboot oem get-product-model
(bootloader)
OKAY [ 0.006s]
Click to expand...
Click to collapse
oloco2 said:
failed input oem_nv_item error
Click to expand...
Click to collapse
oloco2 said:
SYSTEM_VERSION
(bootloader) :STF-L09C10B100a
Click to expand...
Click to collapse
Testpoint or dc-phoenix, bro.
-Alf- said:
Testpoint or dc-phoenix, bro.
Click to expand...
Click to collapse
I posted in the previous post that I already used testpoint using potatonv.
I only used testpoint in order to unlock bootloader, and today I used it via potatonv because you seggested it but.... is there any other use I could give to testpoint other than unlocking bootloader? Something that couldhelp in this situation?
Regards
oloco2 said:
I posted in the previous post that I already used testpoint using potatonv.
I only used testpoint in order to unlock bootloader, and today I used it via potatonv because you seggested it but.... is there any other use I could give to testpoint other than unlocking bootloader? Something that couldhelp in this situation?
Regards
Click to expand...
Click to collapse
You have to flash board software using testpoint . Google it, I have no experience with that.
Ok. Thank you -Alf-. I will have a look to google.
But in the meanwhile, if someone else coukd help me a little bit, will be more than welcome
Regards!!
Hi -Alf-
I got good news for me. I got fastboot working again. I need to use potatonv in order to get it, but anywayI think it's good news.
Please, any other idea in order to make it come back, please?
Thank you
oloco2 said:
any other idea in order to make it come back,
Click to expand...
Click to collapse
your phone has an incomplete FW (System 8.0.0.046 (0JRE)),, an unknown model and a problem with oeminfo. Do you even read what I'm writing???
https://forum.xda-developers.com/t/...-security-verify-failed.4453855/post-86982695
Yes I read.
You told me to use testpoint or DC after telling you that I was unable to enter fastmode, but now I'm able to enter again. That's why I asked you for help again, because maybe using fastboot you were able to tell me any other way to test.
Regards
oloco2 said:
Yes I read.
You told me to use testpoint or DC after telling you that I was unable to enter fastmode, but now I'm able to enter again. That's why I asked you for help again, because maybe using fastboot you were able to tell me any other way to test.
Regards
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/i-bricked-my-honor-9-lite.3799176/post-76943641
Hey -Alf- !
I can ay that finally I got it working.
How I did it:
I got a full firmware for my devce and using Huawei Update extractor I extracted all the images to a folder.
Using a little script un batch I createda .txt with multiple lines:
fastboot flash cache cache.img
fastboot flash crc crc.img
fastboot flash curver curver.img
fastboot flash cust cust.img
fastboot flash dts dts.img
fastboot flash eng_system eng_system.img
fastboot flash eng_vendor eng_vendor.img
fastboot flash erecovery_kernel erecovery_kerne.img
fastboot flash erecovery_ramdis erecovery_ramdi.img
fastboot flash erecovery_vbmet erecovery_vbmet.img
fastboot flash erecovery_vendor erecovery_vendo.img
fastboot flash fastboot fastboot.img
fastboot flash fw_hifi fw_hifi.img
fastboot flash fw_lpm3 fw_lpm3.img
fastboot flash hisiufs_gpt hisiufs_gpt.img
fastboot flash boot kernel.img
fastboot flash modemnvm_update modemnvm_update.img
fastboot flash modem_fw modem_fw.img
fastboot flash odm odm.img
fastboot flash package_type.img package_type.img
fastboot flash patch patch.img
fastboot flash preas preas.img
fastboot flash preavs preavs.img
fastboot flash preload preload.img
fastboot flash product product.img
fastboot flash recovery_ramdisk recovery_ramdis.img
fastboot flash recovery_vbmeta recovery_vbmeta.img
fastboot flash recovery_vendor recovery_vendor.img
fastboot flash sensorhub sensorhub.img
fastboot flash sha256rsa sha256rsa.img
fastboot flash system system.img
fastboot flash teeos teeos.img
fastboot flash trustfirmware trustfirmware.img
fastboot flash userdata userdata.img
fastboot flash vbmeta vbmeta.img
fastboot flash vendor vendor.img
fastboot flash verlist verlist.img
fastboot flash version version.img
fastboot flash xloader xloader.img
And I run all the commands.
Some of them gave me some errors like partition lenght or something like that, but at the end, once rebooted, the error was gone.
Then, I updated all the firmware usong dload.
Now I'm facing a little error about oeminfo. I think itis due to the fact that the firmware I used was rusian, and my phone is from EU. I already created another thread in this forum.
I want to thank you for your tme and your ideas.
I hope this post can help someone over there with an error like mine.
Thank you very much for your time and help
Regards
No problem. Btw, why russian FW? I gave you a link with EU FW . Okay, your choice...
oloco2 said:
Now I'm facing a little error about oeminfo
Click to expand...
Click to collapse
Little?
Yes, The russian FW I flashed was yeterday. Now, after you replied to my post, I will try to upgrade FW to the EU version. I hope now everything works as it should
The "litle error" about oeminfo is:
"/preas/xxx" in some parts of the settings. I read somewhere it was due to oeminfo.I'm I wrong?
Thank you!!
I have already tried to fix the /preas/xxx "little error", but it didn't work
After flashing the EU version of lld-l31, I tested it and it seems to be showing the same error in "Compilation Number", in About
lso, in Model it says "unknow". I thing this is why when I tried to find a new OTA version, it didn't find anyone, even if using android 8
Any idea to fix "/preas/xxx"?
Thank you ad regards!!
All fixed!!
I found this oeminfo:
OEMinfo & Dump & CERT Honor 9 Lite (LLD-ALL)
OEMinfo & Dump & CERT Honor 9 Lite (LLD-AL00 / LLD-AL10 / LLD-AL20 / LLD-AL30 / LLD-TL00 / LLD-TL10 / LLD-L21 / LLD-L22 / LLD-L31 / LLD-L32 / LLD-L42). Share File Certificate, File Dump, OE…
azrom.net
After updating it, all info seems to be correct in about. Also, there's a new OTA for me!
What a road gave me this phone
I hope I'mnot comming back to here in a while
Thank you for all your help
Regards!!!
oloco2 said:
I have already tried to fix the /preas/xxx "little error", but it didn't work
After flashing the EU version of lld-l31, I tested it and it seems to be showing the same error in "Compilation Number", in About
lso, in Model it says "unknow". I thing this is why when I tried to find a new OTA version, it didn't find anyone, even if using android 8
Any idea to fix "/preas/xxx"?
Thank you ad regards!!
Click to expand...
Click to collapse
Kindly share your batch script, pls