As I say in the tittle, my phone has not slot b. It means that when I try to flash any .img or .zip I have an error message telling my that "XXX_b not accesible".
How can I create the partition? I have android one and everything locked as I flashed the stock image vía COM because I have no idea how to solve the partition problem.
gfpablo_ said:
As I say in the tittle, my phone has not slot b. It means that when I try to flash any .img or .zip I have an error message telling my that "XXX_b not accesible".
How can I create the partition? I have android one and everything locked as I flashed the stock image vía COM because I have no idea how to solve the partition problem.
Click to expand...
Click to collapse
You say you are trying to flash something but then you also say that everything is locked. You can't flash anything other than the stock firmware (in EDL mode) if your bootloader is locked.
Catsonvi said:
You say you are trying to flash something but then you also say that everything is locked. You can't flash anything other than the stock firmware (in EDL mode) if your bootloader is locked.
Click to expand...
Click to collapse
I tried to flash it when i have everything unlocked. I tried to flash ASOP v6.6 and the result was a bricked phone. However I flashed the android one stock ROM and locked everything with the Xiaomi flash program.
You need to flash stock through EDL
Nebrassy said:
You need to flash stock through EDL
Click to expand...
Click to collapse
That's what i've done. Although, if I try to flash TWRP from fastboot I have an error message telling me that I have no slot b
gfpablo_ said:
That's what i've done. Although, if I try to flash TWRP from fastboot I have an error message telling me that I have no slot b
Click to expand...
Click to collapse
You can't flash the TWRP image from fastboot, since our phone does not have a seperate recovery partition and you also cannot flash ANYTHING (other than stock via EDL) if your phone's bootloader is locked.
Now since it seems that your bootloader is locked, you need to enable developer options first and then in developer options enable the "OEM unlocking" option. After that you need to go to fastboot in order to unlock the bootloader and use these commands one at the time:
fastboot flashing unlock
fastboot flashing unlock_critical
Keep in mind that after using these commands you will get a prompt on your phone to confirm that you want to unlock the bootloader and doing so will erase everything (basically like doing a factory reset).
After you fully unlock the bootloader, in order to flash TWRP with stock you need to go to the official TWRP website and find the .img and the .zip installer for the Mi A2. You need to boot the .img via fastboot with fastboot boot *location to the .img* (without the asterisks) and then transfer and flash the TWRP .zip installer with TWRP. After that you can boot into TWRP normally without fastboot booting.
If you want to flash a custom ROM you will still need to fastboot boot into the TWRP .img because the .zip you flashed is tied to the system, and since you need to wipe the system before flashing a custom ROM you will also wipe the flashed TWRP.
I still recommend reading this guide: https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375
[SOLVED]
Catsonvi said:
You can't flash the TWRP image from fastboot, since our phone does not have a seperate recovery partition and you also cannot flash ANYTHING (other than stock via EDL) if your phone's bootloader is locked.
Now since it seems that your bootloader is locked, you need to enable developer options first and then in developer options enable the "OEM unlocking" option. After that you need to go to fastboot in order to unlock the bootloader and use these commands one at the time:
fastboot flashing unlock
fastboot flashing unlock_critical
Keep in mind that after using these commands you will get a prompt on your phone to confirm that you want to unlock the bootloader and doing so will erase everything (basically like doing a factory reset).
After you fully unlock the bootloader, in order to flash TWRP with stock you need to go to the official TWRP website and find the .img and the .zip installer for the Mi A2. You need to boot the .img via fastboot with fastboot boot *location to the .img* (without the asterisks) and then transfer and flash the TWRP .zip installer with TWRP. After that you can boot into TWRP normally without fastboot booting.
If you want to flash a custom ROM you will still need to fastboot boot into the TWRP .img because the .zip you flashed is tied to the system, and since you need to wipe the system before flashing a custom ROM you will also wipe the flashed TWRP.
I still recommend reading this guide: https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375
Click to expand...
Click to collapse
Thank you! I have to admit that I have no idea of whats wrong earlier. This guide solved the problem tho.
Related
Any help appreciated here, I have been searching the forums all morning, but haven't found the same issue as mine (lots of stuck at google ?'s but none from failed upgrade) last night I decided to take the plunge and update my N6 from build 6.0.1 (MOB31H, Oct 2016) to 7.0.0 (NBD90Z, Oct 2016)
I typically use the WugFresh NRT to upgrade via factory image. Last night I decided to give the OTA images a try.
Everything was going smoothly until I bumped my keyboard tray and my phone became disconnected while still flashing. It was almost done too.....it was at the point of flashing the system image and was interrupted at 83% and it failed install.
I then attempted to recover from this by flashing entire factory image for 7.0 but it doesn't seem to want to mount my device. I then tried to go back and flash 6.01 to device using the softbrick/bootloop function from the NRT toolkit. It seemed to partially work as the size of the word google on the screen changed during boot went smaller (so I assume the boot.img was able to flash?) but I am still stuck at the google logo with the unlock at the bottom. Bright side is device is bootloader unlocked.
If I try the recover from bootloop function on the NRT it seems to have trouble sending files to phone (goes through all the process just doesn't take it looks like it sending files but before each at beginning it doesn't seem to connect to device.
I can access bootloader, and recovery. In recovery I tried to wipe/cache (wipes but doesn't help), tried factory reset (wipes but still stuck at Google), tried to mount system through selecting via recovery and it fails.
Not sure which image I should try to flash now to recover 6.01 or 7.0 or if I can even recover from this? Any suggestions are appreciated.
When I first got my phone I did create a backup using the NRT but that was on I think 5.0 or 5.01 and I no longer have twrp installed, should I try putting twrp on it and restoring that back up? It was a long time ago and I am not sure if it will cause radio or boot img issues...since I have upgraded so far past without making another backup with a newer version.
I have read that some others with similar issues that were told to use the N beta to get a clean flash.....only issue is there is no longer a N beta for Nexus 6......it now only shows 7.01 for 6p, 5x, and pixel.
Should I try flashing twrp and a ROM? And after see if I can get to load that way then go back and flash stock image?
Any help or suggestions are appreciated.
On PC:
Download most recent from Google factory images page.
Download most recent twrp
Unzip file
Unzip image-shamu-______.zip
From phone:
Boot to bootloader (power+vol down)
Plug in phone
From PC:
Fastboot flash bootloader <name of bootloader file>.IMG
Fastboot reboot bootloader
Fastboot flash radio <name of radio>.IMG
Fastboot reboot bootloader
Fastboot flash recovery twrp.img
Fastboot flash system system.img
Fastboot flash boot boot.img
Boot into twrp recovery and wipe cache and dalvik
Reboot
Profit
Dirty_Jerz said:
On PC:
Download most recent from Google factory images page.
Download most recent twrp
Unzip file
Unzip image-shamu-______.zip
From phone:
Boot to bootloader (power+vol down)
Plug in phone
From PC:
Fastboot flash bootloader <name of bootloader file>.IMG
Fastboot reboot bootloader
Fastboot flash radio <name of radio>.IMG
Fastboot reboot bootloader
Fastboot flash recovery twrp.img
Fastboot flash system system.img
Fastboot flash boot boot.img
Boot into twrp recovery and wipe cache and dalvik
Reboot
Profit
Click to expand...
Click to collapse
just a silly question really , can this work on on a locked bootloader /not rooted device ?
touns_j said:
just a silly question really , can this work on on a locked bootloader /not rooted device ?
Click to expand...
Click to collapse
This requires you unlock your bootloader. You will be installing a custom recovery. Root is not needed though.
wavechapter said:
This requires you unlock your bootloader. You will be installing a custom recovery. Root is not needed though.
Click to expand...
Click to collapse
alright , i thought twrp could be replaced with stock recovery
Dirty_Jerz said:
On PC:
Download most recent from Google factory images page.
Download most recent twrp
Unzip file
Unzip image-shamu-______.zip
From phone:
Boot to bootloader (power+vol down)
Plug in phone
From PC:
Fastboot flash bootloader <name of bootloader file>.IMG
Fastboot reboot bootloader
Fastboot flash radio <name of radio>.IMG
Fastboot reboot bootloader
Fastboot flash recovery twrp.img
Fastboot flash system system.img
Fastboot flash boot boot.img
Boot into twrp recovery and wipe cache and dalvik
Reboot
Profit
Click to expand...
Click to collapse
Thank You Dirty_Jerz! I really appreciate the help.
I am now back up and running on 7.0!
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 all.
Here is my problem
I successfully unlocked my bootloader and I flashed latest maunofrio twrp v35
In TWRP, I did a full wipe in TWRP and formatted data partition to remove encryption
But now, I can't boot again in twrp and I'm stucked in fastboot.
Vol UP + power does not boot in twrp but still in fastboot..
When I hit the command : fastboot flash recovery recovery.img, it says OK
But fastboot boot recovery.img no longer workos now, failed
( before wiping and formatting all it worked )
I don't know what to do now to access twrp..
Any help is very appreciated
Greetings
Try another recovery and if it failed try full flash latest stable rom
Well, I have been warning so many times that use any TWRP in MI9:
1. format data partition
2. reboot TWRP and then enter twrp. Make twrp mount data partition
3. wipe everything BUT please keep system partition only
4. reboot twrp and then enter twrp again
5. Now wipe system partition and then flash any rom you want
6. reboot
How to save your phone now ? Please try fastboot ROM and use miflash app to save your phone !
Kris
ManuBBXX said:
Hello all.
Here is my problem
I successfully unlocked my bootloader and I flashed latest maunofrio twrp v35
In TWRP, I did a full wipe in TWRP and formatted data partition to remove encryption
But now, I can't boot again in twrp and I'm stucked in fastboot.
Vol UP + power does not boot in twrp but still in fastboot..
When I hit the command : fastboot flash recovery recovery.img, it says OK
But fastboot boot recovery.img no longer workos now, failed
( before wiping and formatting all it worked )
I don't know what to do now to access twrp..
Any help is very appreciated
Greetings
Click to expand...
Click to collapse
@Kris Chen I am in similar situation here... Can you please help?
First of all - which TWRP should we use for Mi9T? IS this one good? https://mifirm.net/model/davinci.ttt#other-twrp
After flashing recovery-TWRP-3.3.1-0607-REDMI_K20-CN-wzsx150.img - fastboot boot twrp.img goes okay
And then after "fastboot boot twrp.img" the phone restarts and is just stuck on the "semitransparent" MI logo...
I can press Vol+- and power buttons and boot into Mi 3 recovery, wipe data, set up the phone again. And then it is all over again. I am new to this and probably making some basic mistake?
EDIT. I think the mistake was to trying to use a wrong TWRP...
Some questions here:
1. Is Redmi K20 CN the same as Mi9T?
If yes, that twrp is correct and the best one
2.After flashing twrp, can you enter twrp by general
method : power + volume up to enter twrp?
If yes, I think the problem is coming from your data
partition. Please format your data partition first and
then reboot to Twrp again. Then copy your rom in your
phone and then wipe cache/ dalvik cache/system. Next
to flash rom. Always Remeber not to reboot your
phone if you haven't flashed rom under twrp after
flashing system partition.
Kris
Ardysan said:
@Kris Chen I am in similar situation here... Can you please help?
First of all - which TWRP should we use for Mi9T? IS this one good? https://mifirm.net/model/davinci.ttt#other-twrp
After flashing recovery-TWRP-3.3.1-0607-REDMI_K20-CN-wzsx150.img - fastboot boot twrp.img goes okay
And then after "fastboot boot twrp.img" the phone restarts and is just stuck on the "semitransparent" MI logo...
I can press Vol+- and power buttons and boot into Mi 3 recovery, wipe data, set up the phone again. And then it is all over again. I am new to this and probably making some basic mistake?
EDIT. I think the mistake was to trying to use a wrong TWRP...
Click to expand...
Click to collapse
Thank you Kris!
Download the fastboot rom (Google it )then flash it with miflashtool just make sure the archive of the ROM is "tgz"before you unzip it .
Failykun said:
Download the fastboot rom (Google it )then flash it with miflashtool just make sure the archive of the ROM is "tgz"before you unzip it .
Click to expand...
Click to collapse
This is what I had to do both times this happened.
I have the same exact problem
I used the same TWRP and I also wiped system.
Did you fixed it already?
RebornCheiko said:
I have the same exact problem
I used the same TWRP and I also wiped system.
Did you fixed it already?
Click to expand...
Click to collapse
As i understand, you wiped system and then restarted? And now you can enter only fastboot?
When you wipe system you must flash a ROM without restart or after restart, only fastboot available. TWRP version has nothing to do with this.
Now you must use mi flash or adb and fastboot utility. Download fastboot version of ROM, then open archive and flash it using mi flash or flash_all.bat script. flash_all_lock.bat will also lock your bootloader and mi flash has that option too, so check twice what option you choose
After flashing ROM you can flash TWRP again and it will be available, because by flashing ROM you restored system
I had the same problem.
Try to flash vbmeta.img via fastboot (fastboot --disable-verity flash vbmeta vbmeta.img) and then flash recovery then boot recovery.
Or try to flash boot.img (fastboot flash boot boot.img) then flash recovery.
ManuBBXX said:
Hello all.
Here is my problem
I successfully unlocked my bootloader and I flashed latest maunofrio twrp v35
In TWRP, I did a full wipe in TWRP and formatted data partition to remove encryption
But now, I can't boot again in twrp and I'm stucked in fastboot.
Vol UP + power does not boot in twrp but still in fastboot..
When I hit the command : fastboot flash recovery recovery.img, it says OK
But fastboot boot recovery.img no longer workos now, failed
( before wiping and formatting all it worked )
I don't know what to do now to access twrp..
Any help is very appreciated
Greetings
Click to expand...
Click to collapse
I got you chief. Make sure you have adb and fastboot installed.
No you don't need Mi flash tool for this. All you need is a computer.
Go to fastboot mode, plug in your device and expand cepheus.tgz file you downloaded. Link below
https://xiaomifirmwareupdater.com/
Now open the folder. You have the flash_all files in there. Any .bat file is for Windows only. Any .sh files are for Mac and Linux.
Make sure the device is recognized in fastboot via cmd or terminal
WINDOWS ONLY: Open Command prompt and drag flash_all.bat into the cmd window and press enter
MAC/LINUX: Open terminal and drag flash_all.sh into the terminal window and press enter.
This part requires some patience. Wait until everything is finished.
Reboot using power button and it should be back to normal.
Hello everyone!
I have a huge problem with my Mi9 and I need your help.
I tried to install magisk, but once I flashed it any version of magisk (19.3, 20 etc...) the phone was rebooting in recovery mod insted of rebooting normaly. I have the version 10.2.30 PFAEUXM.
I've downloaded this ROM (zip) and extracted it. I then flashed the boot.img file thanks to the command "fastboot flash boot boot.img" but the phone stay stuck in fastboot mod and can't restart anymore!
I tried to re-flash the entire ROM via "fastboot flash system ROM.zip" but it didn't work. I also tried to flash TWRP-3.3.1-0601 via command "fastboot flash recovery TWRP-3.3.1-0601.7z".
I hope you guys will be able to help me...
Thanks in advance and have a good day.
tom1909 said:
"fastboot flash system ROM.zip" "fastboot flash recovery TWRP-3.3.1-0601.7z"
Click to expand...
Click to collapse
О_о
Seeing this i must ask you how flashed magisk? fastboot flash boot magisk.tgz ?)))) And how you even managed to boot to recovery?
g_seva said:
О_о
Seeing this i must ask how flashed magisk? fastboot flash boot magisk.tgz ?)))) And how you even managed to boot to recovery?
Click to expand...
Click to collapse
First, thanks for your answer
I tried to flash magisk.zip by TWRP
I tried to reboot in recovery mod by "vol+" + "power" and "adb reboot bootlaoder, but it doesn't work, it is written "error: no devices/emulators found"
"fastboot reboot" reboot my device in fastboot mod. But when i try "adb devices" it's written "List of devices attached"
tom1909 said:
First, thanks for your answer
I tried to flash magisk.zip by TWRP
I tried to reboot in recovery mod by "vol+" + "power" and "adb reboot bootlaoder, but it doesn't work, it is written "error: no devices/emulators found"
"fastboot reboot" reboot my device in fastboot mod. But when i try "adb devices" it's written "List of devices attached"
Click to expand...
Click to collapse
By fastboot flash recovery TWRP-3.3.1-0601.7z you flashed twrp in archive i didn't know it even possible You must extract the archive and in archive must be file "twrp name".img or recovery.img. Then you can flash TWRP with fastboot flash recovery recovery.img or for example fastboot flash recovery twrp-3.3.1-42-cepheus-mauronofrio.img.
If after this you will manage to boot into twrp, you can flash a ROM in TWRP using install option. I don't know what you did before so before flashing ROM wipe cache/dalvik cache and format data all this in TWRP. After flashing ROM you can flash magisk, same as ROM.
If you can't enter TWRP, you must download fastboot ROM, extract it and flash it via Mi flash. Don't use flash all and lock or you will lock your bootloder.
g_seva said:
By fastboot flash recovery TWRP-3.3.1-0601.7z you flashed twrp in archive i didn't know it even possible You must extract the archive and in archive must be file "twrp name".img or recovery.img. Then you can flash TWRP with fastboot flash recovery recovery.img or for example fastboot flash recovery twrp-3.3.1-42-cepheus-mauronofrio.img.
If after this you will manage to boot into twrp, you can flash a ROM in TWRP using install option. I don't know what you did before so before flashing ROM wipe cache/dalvik cache and format data all this in TWRP. After flashing ROM you can flash magisk, same as ROM.
If you can't enter TWRP, you must download fastboot ROM, extract it and flash it via Mi flash. Don't use flash all and lock or you will lock your bootloder.
Click to expand...
Click to collapse
Unfortunately, I tried to install TWRP-3.3.1-42-cepheus-mauronofrio.img. too but it doesn't work. My phone reboot in fastboot mod. :crying:
I found a fastboot rom but in 10.2.22 not in 10.2.30. I'm going to try with this, and update the rom after.
I'll tell you back soon. Thanks for all.
tom1909 said:
Unfortunately, I tried to install TWRP-3.3.1-42-cepheus-mauronofrio.img. too but it doesn't work. My phone reboot in fastboot mod. :crying:
I found a fastboot rom but in 10.2.22 not in 10.2.30. I'm going to try with this, and update the rom after.
I'll tell you back soon. Thanks for all.
Click to expand...
Click to collapse
Have you wiped system?
g_seva said:
By fastboot flash recovery TWRP-3.3.1-0601.7z you flashed twrp in archive i didn't know it even possible You must extract the archive and in archive must be file "twrp name".img or recovery.img. Then you can flash TWRP with fastboot flash recovery recovery.img or for example fastboot flash recovery twrp-3.3.1-42-cepheus-mauronofrio.img.
If after this you will manage to boot into twrp, you can flash a ROM in TWRP using install option. I don't know what you did before so before flashing ROM wipe cache/dalvik cache and format data all this in TWRP. After flashing ROM you can flash magisk, same as ROM.
If you can't enter TWRP, you must download fastboot ROM, extract it and flash it via Mi flash. Don't use flash all and lock or you will lock your bootloder.
Click to expand...
Click to collapse
I'm sorry, but I finaly didn't find a link to download the fastboot rom. I only find recovery rom .zip. Can you help me and send me a link pleeease.
tom1909 said:
I'm sorry, but I finaly didn't find a link to download the fastboot rom. I only find recovery rom .zip. Can you help me and send me a link pleeease.
Click to expand...
Click to collapse
Download Mi Flash tool pro: https://jumpmobile.ru/download/miflashpro-3-3-1212-88/?wpdmdl=286&refresh=5da2215f6f9e21570906463
Enter with your account choose "ROM packages", search for your device, and choose one of available fastboot ROMs, tap on copy and paste the download link in browser or download manager.
g_seva said:
Have you wiped system?
Click to expand...
Click to collapse
Yes, when my phone rebooted in recovery I tried to wipe system and reflash the rom. It worked but when I reinstalled magisk the bug came back
tom1909 said:
Yes, when my phone rebooted in recovery I tried to wipe system and reflash the rom. It worked but when I reinstalled magisk the bug came back
Click to expand...
Click to collapse
You sure that you reinstalled ROM after wiping system? Because if you just wiped system and flashed magisk that's the problem You must flash a ROM after wiping system without reboot or you will stuck in fastboot after reboot And there is no need in system wipe, don't touch it
g_seva said:
Download Mi Flash tool pro: https://jumpmobile.ru/download/miflashpro-3-3-1212-88/?wpdmdl=286&refresh=5da2215f6f9e21570906463
Enter with your account choose "ROM packages", search for your device, and choose one of available fastboot ROMs, tap on copy and paste the download link in browser or download manager.
Click to expand...
Click to collapse
I tried to flash the fastboot rom 10.2.15 by Miflash and it works ! I upraged this just after :fingers-crossed:
Yes, I remote system just before flash a rom but maybe I forgot.
My problem is solve ! Thanks for all (sorry for my bad english, I'm french)
How can I get my topic "Solved" ?
Cordialy
tom1909 said:
I tried to flash the fastboot rom 10.2.15 by Miflash and it works ! I upraged this just after :fingers-crossed:
Yes, I remote system just before flash a rom but maybe I forgot.
My problem is solve ! Thanks for all (sorry for my bad english, I'm french)
How can I get my topic "Solved" ?
Cordialy
Click to expand...
Click to collapse
Just add to the thread name [SOLVED]. Edit first post and then you can edit thread name.
Greetings from Israel.
This is maximum stupid. I need the xiaomi flash tool to repair it and the tool wants to verify my telephone number by sending me a code by SMS...