Hi everyone,
I've unlocked my mi 9t pro (8gb version) today (purchased from Hong Kong sent to Melbourne/Australia) and tried to flash TWRP. When I finally got into TWRP I deleted everything through advanced wipe (this is probably where I stuffed up). I rebooted and now I'm forever stuck in the fastboot screen.
I can use the cmd fastboot to re-load the twrp.img successfully. If I do that, I hold UP+PWR and it just returns me to fastboot screen. However, when I try to use 'fastboot boot twrp.img' I get the following error;
Code:
downloading 'boot.img'...
OKAY [ 1.398s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.408s
I can't go anywhere from here. I've attempted to use the miflash tool, but it's just throwing errors at me.
Any help here would be great.
If you have any questions, please don't hesitate to ask.
Thanks,
Raddest
raddest said:
Hi everyone,
I've unlocked my mi 9t pro (8gb version) today (purchased from Hong Kong sent to Melbourne/Australia) and tried to flash TWRP. When I finally got into TWRP I deleted everything through advanced wipe (this is probably where I stuffed up). I rebooted and now I'm forever stuck in the fastboot screen.
I can use the cmd fastboot to re-load the twrp.img successfully. If I do that, I hold UP+PWR and it just returns me to fastboot screen. However, when I try to use 'fastboot boot twrp.img' I get the following error;
I can't go anywhere from here. I've attempted to use the miflash tool, but it's just throwing errors at me.
Any help here would be great.
If you have any questions, please don't hesitate to ask.
Thanks,
Raddest
Click to expand...
Click to collapse
Needs flashing images manually from adb
EpickBroVlad said:
Needs flashing images manually from adb
Click to expand...
Click to collapse
I've flashed boot.img logo.img dtbo.img vbmeta.img through fastboot. Haven't done anything through ADB though. Can you give more details please?
edit: I've just tried adb reboot tw.img (tw being the TWRP) and I got this;
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot tw.img
adb server version (32) doesn't match this client (36); killing...
* daemon started successfully *
error: no devices/emulators found
edit 2: Also worth noting, I'm pretty sure I never enabled USB debugging before all of this...
raddest said:
I've flashed boot.img logo.img dtbo.img vbmeta.img through fastboot. Haven't done anything through ADB though. Can you give more details please?
edit: I've just tried adb reboot tw.img (tw being the TWRP) and I got this;
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot tw.img
adb server version (32) doesn't match this client (36); killing...
* daemon started successfully *
error: no devices/emulators found
Click to expand...
Click to collapse
I've messed my Mi9t by wiping presist and system partitions and as a cherry on top I've flashed stable of xiaomi.eu miui 11 based on android 10 on beta xiaomi.eu miui 10 based on android 9. Partition table was messed and phone was done... Even miflash didn't helped.
raddest said:
Hi everyone,
I've unlocked my mi 9t pro (8gb version) today (purchased from Hong Kong sent to Melbourne/Australia) and tried to flash TWRP. When I finally got into TWRP I deleted everything through advanced wipe (this is probably where I stuffed up). I rebooted and now I'm forever stuck in the fastboot screen.
I can use the cmd fastboot to re-load the twrp.img successfully. If I do that, I hold UP+PWR and it just returns me to fastboot screen. However, when I try to use 'fastboot boot twrp.img' I get the following error;
Code:
downloading 'boot.img'...
OKAY [ 1.398s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.408s
I can't go anywhere from here. I've attempted to use the miflash tool, but it's just throwing errors at me.
Any help here would be great.
If you have any questions, please don't hesitate to ask.
Thanks,
Raddest
Click to expand...
Click to collapse
If you have access to fastboot then you haven't killed it. You need to use MiFlash and try different official fastboot ROMS until you get the same as it came with (same rom not neccessarily same version number). Make sure you flash using "clean all and flash" and DON'T select lock.
Eventuallly one will work, you may have to try diffent versions of MiFlash and different ROMS but stick with it.
Also put the IMIE from the box it came in, into the Xiaomi authenticator site and if it's in Chinese, stick to chinese roms.
Your phone's only bricked if you can't access fastboot... something I once did to a Mi8 Pro.
reboot on fastboot
download first FASTBOOT ROM for your china version (Miui 10)
download miflash
install this rom throough miflash
regards
pjcarrmole said:
If you have access to fastboot then you haven't killed it. You need to use MiFlash and try different official fastboot ROMS until you get the same as it came with (same rom not neccessarily same version number). Make sure you flash using "clean all and flash" and DON'T select lock.
Eventuallly one will work, you may have to try diffent versions of MiFlash and different ROMS but stick with it.
Also put the IMIE from the box it came in, into the Xiaomi authenticator site and if it's in Chinese, stick to chinese roms.
Your phone's only bricked if you can't access fastboot... something I once did to a Mi8 Pro.
Click to expand...
Click to collapse
Is there any particular version of miflash that will work? When I try to run the latest (MiFlash20181115) I get the messages to 'Please install driver'. I click install, and it gives me errors. I'll attach what I'm seeing. I'll try different versions of miflash.
edit: Ok I've tried a different version of Miflash which doesn't throw driver errors at me when I install it. It can detect my phone in fastboot mode. I guess I need a list of mi 9t pro global fastboot roms. I'm looking for that. I've downloaded miui_RAPHAELGlobal_V10.3.3.0.PFKMIXM_67fb825970_9.0.zip but I'm pretty sure that's a regular ROM. I'm going to google 'mi 9t pro global fastboot rom' and see what I can find. Thanks!
Hopefully this works. Will it re-lock my bootloader if I select 'clean all' only?
raddest said:
Is there any particular version of miflash that will work? When I try to run the latest (MiFlash20181115) I get the messages to 'Please install driver'. I click install, and it gives me errors. I'll attach what I'm seeing. I'll try different versions of miflash.
edit: Ok I've tried a different version of Miflash which doesn't throw driver errors at me when I install it. It can detect my phone in fastboot mode. I guess I need a list of mi 9t pro global fastboot roms. I'm looking for that. I've downloaded miui_RAPHAELGlobal_V10.3.3.0.PFKMIXM_67fb825970_9.0.zip but I'm pretty sure that's a regular ROM. I'm going to google 'mi 9t pro global fastboot rom' and see what I can find. Thanks!
Hopefully this works. Will it re-lock my bootloader if I select 'clean all' only?
Click to expand...
Click to collapse
I'm guessing you may have a China rom if it's an 8gb version and definitely if it's 8gb/256gb. Latest fastboot roms can be found here:
https://xiaomifirmwareupdater.com/miui/raphael/
I'd try the latest of any rom with clean all. DO NOT SELECT CLEAN ALL AND LOCK unless you're sure its' the original rom variant that came with the phone.
PS I have the China rom, debloated and with all google goodness and it's easy to do, if you ever wanted to relock the bootloader in the future for google play.
Probably disable driver signature in Windows or an older version of me flash ( can't recall what i have since my laptop is semi dead ) , and make sure you actually install those drivers ( about 5 of them ) .
SOLVED
Ok, here's the fix that worked for me.
The latest Miflash didn't work, it's the portable version (I think) so it didn't come with the drivers and didn't run. I downloaded the next miflash which was MiFlashSetup_eng.msi. I can't find the download link at the moment, but it was an install package not the .zip with the contents.
Next, I found the global fastboot rom, which was called raphael_eea_global_images_V10.3.1.0.PFKEUXM_20190723.0000.00_9.0_eea_f70f6415ea.tgz (3.2gb).
From fastboot I ran the XiaoMiFlash.exe. I moved the fastboot rom to the same root folder of the flash program. Pointed it to the folder the fastboot rom was in, and clicked flash. Don't forget to select 'clean all' not 'clean all and lock' from the app.
That was it, and it worked. After it flashed everything (took a bit of time) I unlocked my phone again using mi unlock app. Installed TWRP, and DID NOT do advance flash, just left it on the default stuff. Did that, and am now using pixelexperience 9.0.
Again, thanks to everyone for replying, I'll be clicking thanks. I hope this helps anyone else in the same situation as I was. If you need any more information, please don't hesitate to post here.
Thanks,
Raddest
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.
Hello. When I decided I wanted to revert to the stock MIUI rom, I used the miflash tool to try and flash the fastboot rom for my device (K20 pro Chinsese variant). However, I'm facing a problem where miflash seemingly does nothing, and is stuck on this message:
$for /F tokens = 2 =: "%i in (fastboot -s b2cf370 getvar anti 2 > $1 | findstr/r/c: "anti" do (set...
Any help would be appreciated
Mmm, Miflash is really finicky, everything has to be perfect for it to flash fastboot roms. Just to clarify, have you got the latest drivers updated? Device in fastboot mode? Tried different usb ports and cable? What version Miflash? Fastboot and Miflash files in C: drive?
If all that fails then you could try going into the fastboot rom itself and their should be a option 'flash all' and it'll flash the rom in command instead. Not recommended but usually works for me.
untitledprotocol said:
Hello. When I decided I wanted to revert to the stock MIUI rom, I used the miflash tool to try and flash the fastboot rom for my device (K20 pro Chinsese variant). However, I'm facing a problem where miflash seemingly does nothing, and is stuck on this message:
$for /F tokens = 2 =: "%i in (fastboot -s b2cf370 getvar anti 2 > $1 | findstr/r/c: "anti" do (set...
Any help would be appreciated
Click to expand...
Click to collapse
Here's the fastboot flashing guide from the official Mi forums
https://c.mi.com/oc/miuidownload/detail?guide=2
On a mobile browser you will need to view it in desktop mode.
There is a link to the latest Mi Flash Tool. If you didn't get your copy from here, then download it and try that.
With the phone connected and in fastboot mode, try the 'fastboot devices' command before flashing, and make sure you get a valid response.
For my new Redmi 9T (EEA ROM, 2010j19sy) i wanted to install an unofficially twrp recovery but i was not able to boot any non-stock recovery out on the web. I also found that other people in this forum have the same problem.
The unlock and everything else worked without problems.
This qoute from GrandTouqe describes my problem exactly:
Rename the file change nothing to me.
As information, when I try in try
Bash:
fastboot boot recovery.img
i get :
Code:
Bash:
FAILED (remote: unknown command)
in fastboot
and
Bash:
FAILED (remote: Unrecognized command boot)
in fastbootd
I've test lineage recovery and that's the same : impossible to boot on other recovery except the stock MI-Recovery 3.0 .
Click to expand...
Click to collapse
My OS is Windows 10 on an x64 intel CPU.
The ADB Fastboot binaries are like 3 weeks old, may they cause this strange behavior?
I figured out that my product is not lime, its lemon now. Can anybody tell me what to do?
Hey !
I've found this one who works in this topic.
But after, I can't install the unofficial ROM that I find here.