Related
my device came with unlocked bootloader, so I tried to flash twrp but every time i type "fastboot flash recovery C:\adb\twrp-3.2.1-3-whyred.img" and hit enter, the device seems to disconnect from pc and there is "press any key to reboot" in fastboot on my phone.
How can I solve this issue?`
Phone gets detected by adb/fastboot tool so its not a driver problem. I tried different cables and usb ports aswell.
Firmware is latest global stable.
Nazukii said:
my device came with unlocked bootloader, so I tried to flash twrp but every time i type "fastboot flash recovery C:\adb\twrp-3.2.1-3-whyred.img" and hit enter, the device seems to disconnect from pc and there is "press any key to reboot" in fastboot on my phone.
How can I solve this issue?`
Phone gets detected by adb/fastboot tool so its not a driver problem. I tried different cables and usb ports aswell.
Firmware is latest global stable.
Click to expand...
Click to collapse
try upgrade your android sdk on your pc
Nazukii said:
my device came with unlocked bootloader, so I tried to flash twrp but every time i type "fastboot flash recovery C:\adb\twrp-3.2.1-3-whyred.img" and hit enter, the device seems to disconnect from pc and there is "press any key to reboot" in fastboot on my phone.
How can I solve this issue?`
Phone gets detected by adb/fastboot tool so its not a driver problem. I tried different cables and usb ports aswell.
Firmware is latest global stable.
Click to expand...
Click to collapse
Well if you already had adb in your pc, rename the twrp file to recovery, you don't have to move the twrp from download folder, open download folder press shift and right click then select open cmd here, on cmd type "adb device" to see if your device connected, then after that type this "fastboot flash recovery recovery.img" press enter than after that type "fastboot boot recovery.img" TEAMWIN logo should appear on your device and then you can unplug your device. Hope this useful
i am trying to flash twrp there is no folder called adb i have installed the 15 second adb and all so i have got this minimal adb flashboot and i tried with that and got this ---- FAILED (remote: Flashing is not allowed in Lock State). i have granted all usb and oem unlocking. please help with this
Phone shows unlocked during the boot?
I had the same Problem,after a Factory Reset works for me.
I am on Miglobe-Rom Miui10 8.6.28.
Minimal ADB is enough.
Or use this from Attachment.
Unpack with Win.zip and copy Twrp in this Folder.
Conect the Phone with your Pc ,boot into Bootloader and click "cmd-here.exe"
Use this Command
fastboot flash recovery twrp-3.2.1-3-whyred.img
@Nazukii - Quick question - any chance you could try running GameBench on your device, and see if our background service dies when the device is disconnected from the PC? I don't have a Note 5 Pro to test, and I've got some user complaints. Any assistance would be awesome!
J
gamebenchjake said:
@Nazukii - Quick question - any chance you could try running GameBench on your device, and see if our background service dies when the device is disconnected from the PC? I don't have a Note 5 Pro to test, and I've got some user complaints. Any assistance would be awesome!
J
Click to expand...
Click to collapse
Have you fixed your app to run on Magisk-SU ?
otonieru said:
Have you fixed your app to run on Magisk-SU ?
Click to expand...
Click to collapse
Hey Otonieru,
Not yet, but I've got one of the engineers working on it - hopefully it'll be up in the next 30 days or so
Same problem here after updating my gcam was not working was enabling hall again but it is not booting into twrp
Redmi Note 5 pro
So my Bootloader is locked,
My phone stuck in MI recovery idk how.
I cant install MIUI via fastboot. Im stuck ..
Can anyone please help me here not sure how to proceed further.
If you have made sure that you have all the drivers installed and still have not solved, you need to use an Intel-based PC / notebook and use a usb 2.0.
”Well if you already had adb in your pc, rename the twrp file to recovery, you don't have to move the twrp from download folder, open download folder press shift and right click then select open cmd here, on cmd type "adb device" to see if your device connected, then after that type this "fastboot flash recovery recovery.img" press enter than after that type "fastboot boot recovery.img" TEAMWIN logo should appear on your device and then you can unplug your device. Hope this useful”
i did that but it is showing failed（too many links）and "press any key to reboot" showing on my phone's fastboot screen
Fastboot boot recovery.img flashing problem on Redmi note 5 pro
My bootloader is unlocked and my oem as well as usb deb is on. After i connect my phone in fastboot mode to my pc. The cmd shows fastboot devices but when it comes to fastboot boot recovery.img flashing device get disconnected. Plzzzzzz let me know a solution for this. A solution for this will be highly appreciateable.
A BIG SORRY for a long post. But I am sure its worth reading step by step. Because many peoples are stucked in same situation, no straight forward solution for this issue is available till now. All solutions are based on 50/50 success ratio.
I think if my issue is resolved then it can become WORLD's FIRST SOLUTION to UNBRICK NOTE 5 PRO with 100/100 success ratio.
About Me: I am an ordinary Android user since years. I know how to root and install TWRP and Custom ROMs on any Android Phone. I am not a Developer, every thing discussed here is purely gained by experiments by playing with my phone.
After playing with my bricked phone I reach at a point where I am hopeless and I think at this stage a Developer can help me only, who have deep knowledge of android OS. That's why I called Devs to help me.
About Phone I have Note 5 Pro Global (whyred)M1803E7SG. Phone is under warranty but unfortunately Front Glass of my phone is broken few months ago but still working, so Mi Service Center refused to accept my phone under warranty due to broken Front Glass. Tried to repair my phone by a local Phone Service Shop, thay have all professional tools like UMT, Avangers, MedusaPro etc. but they were also unable to repair my phone. Now I have no option left other than I should repair it by myself.
Phone was on ARB4, was working fine. Bootloader Unlocked and I have rooted it long time ago and was playing with it since it is rooted by flashing different Custom ROMs on daily basis.
Currently phone was working fine on Masik X 4.1 ROM. Some days ago I flashed Masik X 5.0 ROM via TWRP on my phone and after reboot phone became dead and went to EDL 9008 mode. I noticed that I flashed Masik X 5.0 for Note 6 Pro (tulip) ROM on it mistakenly.
Journey Stats Here:
1 - After bricking my phone I tried to flash fastboot ROM for whyred in EDL mode, phone flashed successfully but still stucked in EDL mode. Tried all fastboot ROMs from ARB2 to ARB4 but still no sign of life, phone was not coming out of EDL mode. Also tried "test anti4.zip" files as well but phone is still in EDL mode after a successful flashing.
2 -After that I tried to flash fastboot ROM of Note 6 Pro (tulip) in EDL mode, after flashing complete when I tried to turn ON my phone, I noticed that phone try to start with vibrate and charging light blinks for a while but nothing on Screen and phone dead again. I checked with USB cable attached to laptop, nothing appear in Device Manager. Here I opened my phone and bring it to EDL mode via Test Point method.
3 - Then after searching on internet I saw on a forum where another person was in same situation. He mentioned his phone display was turning ON on a Mi 6X (wayne) ROM but with "Press any key to shutdown" message on screen. So tried same with Mi 6X (wayne) ROM. Phone is turning ON with "Press any key to shutdown". So I started playing with Mi 6X ROM. I started replacing Mi 6X ROM file with Note 5 Pro files one by one and flashing my phone again and again with every one new file (took so many hours in playing with my phone:crying. Initially had many issues like: missing keymaster64.mbn file as Mi 6X uses keymaster64.mbn but Note 5 Pro is using keymaster.mbn file (so corrected .xml and .bat files according to need), Unable to mount Persist partition in TWRP (corrected it by terminal method in TWRP by using command "make_ext4fs /dev/block/bootdevice/by-name/persist", phone was going to Fastboot for a while, Not going to recovery mode, No USB detection on laptop in Device Manager. Fastboot lasts for a half second and then phone goes off.
In short at the end finally I noticed only three files "abl.elf, pmic.elf, xbl.elf" from Mi 6X ROM are responsible for turning my phone ON.
4 - So I replaced "abl.elf, pmic.elf, xbl.elf" files from Mi 6X ROM with Note 5 Pro ROM files and flashed my phone with this new modified ROM in EDL mode. Phone turned on without any "Press any key to shutdown" message on screen. Now phone can go to fastboot mode and detected on USB on my laptop. But not going to Recovery mode, after pressing Vol UP + Power Button, only a black screen and nothing happening on my laptop Device Manager (no driver at all). In fastboot mode I flashed "PitchBlack-whyred-2.9.0-20190501-1030-OFFICIAL" recovery (initially I tried TWRP Recovery for whyred but in TWRP phone was not detected as MTP device on my laptop, so I used Pitchblack Recovery) and after issuing boot command to recovery.img I can go to Pitchblack recovery mode, phone detected on USB port as "Note 5 Pro", MTP drive appear in My Computer, I can copy/paste files in phone Storage. In Recovery mode I flashed Official "miui_HMNote5Global_V10.3.1.0.PEIMIXM_d4d2c9f2aa_9.0" ROM. Phone flashed successfully but after reboot phone went to EDL mode again. So I revived it again with modified ROM.
5 - After revival I tried to boot phone in normal way, I noticed that MI Splash screen is blinking with behavior: Splash screen appears fine for a while and on second blink Screen is inverted then 3rd blink Screen fine and 4th blink screen inverted and so on till I reach to MIUI10 welcome screen. On welcome screen the behavior is same like once fine then inverted. But here my touch screen is not working, I can't go after this screen. Phone is not allowing to touch Next button. I can charge my phone with charger connected. Phone detected as "Note 5 Pro" on my laptop.
6 - I rebooted phone to fastboot mode, tried to flash "whyred_global_images_V10.3.1.0.PEIMIXM_20190522.0000.00_9.0_global_8201319a7e" with MiFlash but can't flash due to "Product Mismatch" warning by MiFlash. Tried Mi 6X ROM and MiFlash started flashing fine.
7 - Then I flashed "boot.img, recovery.img, cust.img, system.img" files by using fastboot flash xx xxx.img commands for Note 5 Pro. Fastboot flashed all files successfully. But after rebooting phone behavior is same like blinking inverted screen and touch not working.
8 - Now I am helpless at this stage. Tried all ways to revive my phone. Nothing else is remaining as I think. No other file is remaining which I can try.
HELP REQUIRED FROM A Developer
I reached on a stage where my phone is now "Semi Unbricked" but is still useless for me. But I hope some Developer can help me to revive my phone.
My Note 5 Pro is converted to Mi 6X but touch screen is not working. Screen is working fine in Pitchblack Recovery mode, phone is responding in Fastboot mode but as it is the fastboot mode of Mi 6X on a Note 5 Pro so it is useless for my phone.
Kindly assist me further so I can replace Mi 6X fastboot with original Note 5 Pro fastboot so that I can flash Note 5 Pro ROM on it.
Waiting for a very positive and prompt reply.
Regards!
I'm not an expert as well, and my information needs to be verified by someone smarter than me, but if you are getting a mismatch when u are trying to flash miui V10.3.1.0 then edit the flash_all.bat and try to remove those (fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *whyred" || echo Missmatching image and device
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *whyred" || exit /B) (it's in the beginning) and don't leave any space.
When in edl mode, try to flash miui and select flash_all.bat which is now edited and it should flash.
Before doing those things make sure u have whyred device (redmi note 5 pro)
Verity. said:
I'm not an expert as well, and my information needs to be verified by someone smarter than me, but if you are getting a mismatch when u are trying to flash miui V10.3.1.0 then edit the flash_all.bat and try to remove those (fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *whyred" || echo Missmatching image and device
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *whyred" || exit /B) (it's in the beginning) and don't leave any space.
When in edl mode, try to flash miui and select flash_all.bat which is now edited and it should flash.
Before doing those things make sure u have whyred device (redmi note 5 pro)
Click to expand...
Click to collapse
Thank for the hint. But my problem is not solved.
I removed those two lines from "flash_all.bat" and bring my phone to fastboot mode. Selected whyred fastboot files with edited "flash_all.bat", phone started flashing perfectly and there was no warning "Product mismatch" . But after completing flash successfully phone rebooted and went to EDL mode again.
I also tried the flashing flash_all.bat modified files in EDL mode but result is same.
I again revived phone with my modified ROM which is still useless for me.
Any other hint plzzzzzzzzzz
Verity. said:
I'm not an expert as well, and my information needs to be verified by someone smarter than me, but if you are getting a mismatch when u are trying to flash miui V10.3.1.0 then edit the flash_all.bat and try to remove those (fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *whyred" || echo Missmatching image and device
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *whyred" || exit /B) (it's in the beginning) and don't leave any space.
When in edl mode, try to flash miui and select flash_all.bat which is now edited and it should flash.
Before doing those things make sure u have whyred device (redmi note 5 pro)
Click to expand...
Click to collapse
My intention is to get back the fastboot mode of whyred. So I can flash fastboot ROM of whyred in fastboot mode. I think this is the only way to unbrick my phone.
yawarniazi said:
My intention is to get back the fastboot mode of whyred. So I can flash fastboot ROM of whyred in fastboot mode. I think this is the only way to unbrick my phone.
Click to expand...
Click to collapse
I know it's pretty obvious but have you tried to flash with method I provided with a disconnected battery?
It's weird it doesn't want to leave the edl state, I'm intrigued indeed. Let's hope someone has some ideas that'll revive your phone, at that state I'm out of ideas. If I'll happen to know something new I'll let you know.
Is there any way exist that I can extract fastboot.img file from whyred ROM? Possible to make a falshable zip and flash it via TWRP???
Anyone can help me plzzzzzzzzzz???????????
yawarniazi said:
Is there any way exist that I can extract fastboot.img file from whyred ROM? Possible to make a falshable zip and flash it via TWRP???
Anyone can help me plzzzzzzzzzz???????????
Click to expand...
Click to collapse
a quick check says there's no such file in the firmware package. have you tried to flash correct boot.img file? what i know is fastboot is inside boot.img
kekesed97 said:
a quick check says there's no such file in the firmware package. have you tried to flash correct boot.img file? what i know is fastboot is inside boot.img
Click to expand...
Click to collapse
I already have mentioned in OP that I also flashed "boot.img, recovery.img, cust.img, system.img) in fastboot mode. Flashing went successful but nothing change in behavior of phone's display. Screen is blinking. But if I flash fastboot ROM of whyren in fastboot mode of wayne (which is currently installed on my whyred phone) then phone become dead and go to EDL mode again.
In next post I am going to post "abl.elf, pmic.elf, xbl.elf" files of both whyred and wayne.
Some body please compare these files from both phones and let me know the reason why my whyred phone is turning ON on wayne files only but not on its original whyred files.
I am helpless after reaching this stage, kindly assist me further please.
Kindly compare these files from whyred and wayne
Here are "abl.elf, pmic.elf, xbl.elf" files of both whyred and wayne.
Some body please compare these files from both phones and let me know the reason why my whyred phone is turning ON on wayne files only but not on its original whyred files.
I tried to flash Note 6 Pro (tulip) files as well but after successful flashing phone is totally dead, if I try to turn it ON then it vibrates little and then nothing ( nothing on USB of my laptop, no EDL at all). After that testpoint method is the only way to bring my phone to EDL mode again.
I tried to flash Mi A2 (jasmine) Android ONE files, jasmine is the Global variant of Mi 6X wayne (I believe hardware of both phones is same), but after successful flashing phone goes to EDL mode.
I am helpless after reaching this stage, kindly assist me further please.
Any body knows about display/touch driver files inside Android OS???
My touch screen is not working at all on MIUI Welcome screen. I want to embed Display Driver files in ROM so I can go forward ahead of this Welcome Screen.
I have tried so many ROMs from different Xiaomi models, replaced so many files one by one, spent too much time on doing this all. But the only combination of files works mentioned below:
abl.elf (must be from wayne ROM)
pmic.elf (must be from wayne or tulip ROMs, both working)
xbl.elf (must be from wayne ROM)
All other files from whyred ROM are OK to flash to bring my phone alive.
ROMs Used:
whyred_global_images_V10.3.1.0.PEIMIXM_20190522.0000.00_9.0_global_8201319a7e
wayne_images_V10.3.3.0.PDCCNXM_20190514.0000.00_9.0_cn_1d4725ac4d
tulip_global_images_V10.3.2.0.PEKMIXM_20190426.0000.00_9.0_global_2264f9bd86
Now I concluded all this mess as: I can never go back to whyred original ROM. The only way left is to use my phone as a Mi 6X by name if touch screen of my mobile gets start working.
Some body please help me in replacing Display Driver files of whyred with wayne files.
Kindly assist me to pass through this step. I want to see what's working and what's not after MIUI Welcome Screen. e.g. IMEI, BT, WIFI, SOUND, CALL etc......
Please help
Have you tried to flash the vendor partition with fastboot command?
Gerr1 said:
Have you tried to flash the vendor partition with fastboot command?
Click to expand...
Click to collapse
Yes tried "fastboot flash vendor vendor.img" , vendor.img flashed successfully but phone's blinking behavior is same as before.
yawarniazi said:
Yes tried "fastboot flash vendor vendor.img" , vendor.img flashed successfully but phone's blinking behavior is same as before.
Click to expand...
Click to collapse
Whats about your persist partition? Did it exists, it could be broken from your falseflash action, so you have to repair this first before you flash the right firmware for your device.
link for a mi mix3 but its very similar for the redmi note 5 https://xiaomifirmware.com/guides-and-tips/how-to-restore-persist-partition-on-mi-max-3/
Gerr1 said:
Whats about your persist partition? Did it exists, it could be broken from your falseflash action, so you have to repair this first before you flash the right firmware for your device.
link for a mi mix3 but its very similar for the redmi note 5 https://xiaomifirmware.com/guides-and-tips/how-to-restore-persist-partition-on-mi-max-3/
Click to expand...
Click to collapse
Did this as well but problem is still not solved.
How to backup unlocked bootloader files?
At last I managed to repair 50% of my phone.
I flashed "whyred_global_images_V9.2.4.0.NEIMIEK_20180210.0000.00_7.1_global" version along with replacing abl.elf, pmic.elf, xbl.elf files, now touch screen of my phone is working and is in original condition ( no inverse screen at all anymore ). But blinking problem still exists. But this way at least I can use my phone to some extent. Can connect to Wifi, Can Receive/Dial calls, bluetooth working perfect. Means everything working perfect except Camera and Display which is blinking every second and I need to wait after every second to touch an option or type anything on my phone. Camera is not opening.
I can go to fastboot mode, but this time fastboot mode is working in a blank screen mode (no fastboot wallpaper on screen) but fastboot working perfect. This time I can go to Stock recovery mode by pressing Vol UP + Power Button. Can wipe data in Recovery mode. Tried to choose MiAssistant option and phone connected to my Laptop as a "adb sideload" mode. Tried to send rom.zip file via adb sideload command but getting error "adb: failed to read command: No error" and phone reboot imediately.
Tried to update my phone via Updater App, Updater App prompted me about found OTA update "V9.2.13.0.NEIMIEK", downloaded OTA, tapped on "Reboot & Update", phone rebooted, update process started, but after starting update phone reboot on initial stage and update failed and rebooted phone.
Tried to apply update by manually downloaded full rom "miui_WHYREDGlobal_V9.2.13.0.NEIMIEK_2c4578fa45_7.1.zip", process started without any error, but in the middle of progress bar phone become dead and went to EDL Mode again. I think its due to reason: when phone started writing "abl.elf, pmic.elf, xbl.elf" files then its become dead and went to EDL Mode.
Recovered it again by modified (abl.elf, pmic.elf, xbl.elf) rom "whyred_global_images_V9.2.4.0.NEIMIEK_20180210.0000.00_7.1_global" in EDL mode.
After a little research I came to know its due improper unlocked bootloader. So I tried to unlock bootloader again by "MiFlash Unlock" app, MiFlash Unlock prompted me that Bootloader is already unlocked and there is no need to unlock it again.
Just want to know is there any way I can backup my UNLOCKED BOOTLOADER and write it back to my phone???
I decied to relock my bootloader and Unlock it again. But I am afraid in doing it of "locking my bootloader forever". Because till now "Unlocked Bootloader" is the only thing exists on my phone who is allowing me to flash anything on my phone.
Kindly tell me if backing up Unlocked bootloader is possible?
Where the files "abl.elf, pmic.elf, xbl.elf" exists on my phone?
I want to replace them with original "whyred" files after rooting my phone with Root Browser. OR via adb shell commands.
Please help
You can't backup ubl. Also, think twice before relocking bootloader, it's possible you'll wait for like two weeks until you can unlock it again.
Verity. said:
You can't backup ubl. Also, think twice before relocking bootloader, it's possible you'll wait for like two weeks until you can unlock it again.
Click to expand...
Click to collapse
That's why I stopped myself to Relock Bootloader.
Any help on replacing abl.elf, pmic.elf, xbl.elf files?
I don't know where these files are stored on my device.
I tried flashing these files in fastboot mode, flashing done successful but phone goes to EDL Mode again.
fastboot flash abl abl.elf
fastboot flash pmic pmic.elf
fastboot flash xbl xbl.elf
I am near to unbrick my phone. But stucked with these 3 files.
Found everything like abl, pmic, xbl and persist etc etc etc....
inside /dev/block/
By using
adb shell
su
cd /dev/block
Can anybody help me in reconstructing this directory by replacing my original whyred files instead of abl.elf, pmic.elf, xbl.elf wayne files?
Kindly help pleaseeeeeeeeeeeeeeeeee. So many developers on this forum but no one is ready to help me. Very disappointed
I am fed-up now. Tried every thing to repair this phone but no success at all.
Tried Relock/Unlock bootloader. Relocked and then unlocked again successfully but no impact on phone condition.
Phone is accepting "abl.elf, pmic.elf, xbl.elf" files only from Mi 6X China (wayne).
Screen blinking behavior still exists.
Evening guys, let's fix the Bootloop of our RMN8Pro if we have installed a menu Recovery TWRP faulty/unsuitable or we have installed a ROM that does not belong to our smartphone.
This method is valid for China to global or Global to global.
NOT FOR INDIAN (sorry about that)
You'll need:
ADB files
Fastboot ROM V10.4.5.0.PGGEUXM
Download both files and unzip them in C:/ADB (if you don't have that folder... just create it)
You will need to rename the file extension of the file <<begonia_eea_global_images_V10.4.5.0.PGGEUXM_20191007.0000.0000_9.0_eea_f796762f8a.tgz>> from .tgz to .rar
Let's go!!
Turn the phone off, turn it on in fastboot mode (by pressing both POWER and VOL- ) and connect the phone to the PC with its USB cable.
Open a CMD command console (in administrator mode) in C:/ADB and type this (press enter when finished typing):
Code:
fastboot devices
If you have the drivers installed and everything goes well, a series of alphanumeric characters will appear, such as for example:
Code:
a6ghfxfv6 fastboot
Perfect, we can go on.
Next we will flash one by one the files needed to revive the phone.
Write the following lines and press enter at the end of each of them (wait for the files to be installed between line and line):
Code:
fastboot boot boot.img
fastboot flash system.img
fastboot flash vendor.img
fastboot flash cust cust.img
fastboot flash recovery recovery.img
When you're done, restart the phone with:
Code:
fastboot reboot
Congratulations, you have your RMN8Pro fixed.
klurosu said:
Evening, let's fix the Bootloop of our RMN8Pro if we have installed a menu Recovery TWRP faulty/unsuitable or we have installed a ROM that does not belong to our phone.
This method is valid for China to global or Global to global.
NOT FOR INDIAN (sorry about that)
You'll need:
ADB files
Fastboot ROM V10.4.5.0.PGGEUXM
Download both files and unzip them in C:/ADB (if you don't have that folder...create it)
You will need to rename the file extension of the file <<begonia_eea_global_images_V10.4.5.0.PGGEUXM_20191007.0000.0000_9.0_eea_f796762f8a.tgz>> from .tgz to .rar
Let's go!!
Turn the phone off, turn it on in fastboot mode (by pressing both POWER and VOL- ) and connect the phone to the PC with its USB cable.
Open a CMD command console (in administrator mode) in C:/ADB and type this (press enter when finished typing):
If you have the drivers installed and everything goes well, a series of alphanumeric characters will appear, such as for example:
Perfect, we can go on.
Next we will flash one by one the files needed to revive the phone.
Write the following lines and press enter at the end of each of them (wait for the files to be installed between line and line):
When you're done, restart the phone with:
Congratulations, you have your RMN8Pro fixed.
Click to expand...
Click to collapse
So, this is basically a guide of how to flash the images through fastboot, right? Why not just use MiFlash when we are in fastboot mode?
polfrank said:
So, this is basically a guide of how to flash the images through fastboot, right? Why not just use MiFlash when we are in fastboot mode?
Click to expand...
Click to collapse
Because it doesn't work???
Don't believe me?, Just try
send from an RMN8 Pro (xiaomi.eu custom rom)
Miflash will work if in fastboot and have an MI account had requested to unlock BL.
Don't believe me? You try.
idog8818 said:
Miflash will work if in fastboot and have an MI account had requested to unlock BL.
Don't believe me? You try.
Click to expand...
Click to collapse
You still need authorized account Sherlock.
(Omg this guys...)
send from an RMN8 Pro (xiaomi.eu custom rom)
klurosu said:
You still need authorized account Sherlock.
(Omg this guys...)
send from an RMN8 Pro (xiaomi.eu custom rom)
Click to expand...
Click to collapse
if you don't apply for the Mi account to unlock BL, how will you able to flash anything? Only 2 mins for a new account.....What the problem will be?
idog8818 said:
if you don't apply for the Mi account to unlock BL, how will you able to flash anything? Only 2 mins for a new account.....What the problem will be?
Click to expand...
Click to collapse
Read again (this time read well please) 2 posts above
send from an RMN8 Pro (xiaomi.eu custom rom)
klurosu said:
Read again (this time read well please) 2 posts above
send from an RMN8 Pro (xiaomi.eu custom rom)
Click to expand...
Click to collapse
Read again but didn't get it. What do you mean ....
idog8818 said:
Read again but didn't get it. What do you mean ....
Click to expand...
Click to collapse
That you still need an Authorized Xiaomi's Account to do that with the old method dude.
send from an RMN8 Pro (xiaomi.eu custom rom)
klurosu said:
That you still need an Authorized Xiaomi's Account to do that with the old method dude.
send from an RMN8 Pro (xiaomi.eu custom rom)
Click to expand...
Click to collapse
What do you mean by Authorized Xiaomi's Account?? As far as I know, there're 2 types of Mi accounts we commonly talk here.
1. Normal Mi account: used to unlock BL and this can be used in miflash to flash rom, I've tried 100 times in fastboot, and works every time. I registered this account I guess 5 years ago when I need to request unlock BL on note 3 . As I said above, it needs 2 mins to register.
2. Authorised service account: This is not we can easy to register, It's for Mi service center or developers for repair/develop purposes. If no rec, no recovery, blank screen, it can be recovered by SP flash tool, which will need this type of account. This is also why users in following post looking for unbricking.
[GUIDE] [begonia] UNBRICK - stuck on DA mode / Authorised Service Account required
https://forum.xda-developers.com/re...a-mode-authorised-t4000433/page7#post81175069
---------- Post added at 01:20 AM ---------- Previous post was at 01:17 AM ----------
I can prove this by my bricked redmi note 8 pro.
I used my mi account to unlock BL, flashed global rom, but I cannot use it in SP FLASH TOOL to restore because my MI account is not an Authorised Service Account
Hello,
I have a nex Redmi Note 8 pro, I unlocked it after I use Ifixit.. to install twrp, the phone was in bootloap, after I tried to flash with fastboot commands. Now the phone is off and I have a black screeen. I can't power it on (vol + or -) does not work. power on no more. It is not recognized with miunlock. No fastboot nor recovery. Please help me how I can do?
nutellamarco said:
Hello,
I have a nex Redmi Note 8 pro, I unlocked it after I use Ifixit.. to install twrp, the phone was in bootloap, after I tried to flash with fastboot commands. Now the phone is off and I have a black screeen. I can't power it on (vol + or -) does not work. power on no more. It is not recognized with miunlock. No fastboot nor recovery. Please help me how I can do?
Click to expand...
Click to collapse
At the moment you only can do a deep flashing in EDL mode, and need an authorized account... You need to contact someone with this type of account and flash... ( And give some money...)
nutellamarco said:
Hello,
I have a nex Redmi Note 8 pro, I unlocked it after I use Ifixit.. to install twrp, the phone was in bootloap, after I tried to flash with fastboot commands. Now the phone is off and I have a black screeen. I can't power it on (vol + or -) does not work. power on no more. It is not recognized with miunlock. No fastboot nor recovery. Please help me how I can do?
Click to expand...
Click to collapse
Some people are saying they managed to bring to life a phone without rocovery without fastboot mode.search and maybe you find a way. As i remember they said with phone turned off you press volume - and power and you have about 5 seconds to flash. I don't know more details.i wish you success
hello
thanks for your ideas, I can't enter in fastboot mode nor recovery. The screeen is black. When I tried with spflash, when I push together vol+ and vol- i hear a noise, but nothing happens with spflash.
I am trying. I think it is loosed.
nutellamarco said:
hello
thanks for your ideas, I can't enter in fastboot mode nor recovery. The screeen is black. When I tried with spflash, when I push together vol+ and vol- i hear a noise, but nothing happens with spflash.
I am trying. I think it is loosed.
Click to expand...
Click to collapse
as far as I know spflash tool should be ready to flash,. it means with all the files selected, the combination is keeping vol+ and connect the USB cable to PC port, I recommend you search in Google about flashing mediatek devices... Good luck
Literally this guide is really about just how to flash with fastboot instead of Mi Flash(tool which can use anyone with Xiaomi Phone - doesn't require Authorized Service ACC)
nutellamarco said:
hello
thanks for your ideas, I can't enter in fastboot mode nor recovery. The screeen is black. When I tried with spflash, when I push together vol+ and vol- i hear a noise, but nothing happens with spflash.
I am trying. I think it is loosed.
Click to expand...
Click to collapse
I had this problem at the weekend(Stuck at EDL mode - tried to flash with SP tool but without success(needed service acc - brom error)), you can use SP flash tool with authorized service acc - fastest way, maybe there will be some cracked security file in the future as one for redmi 6. Or do battery trick. You are stick at EDL mode and cannot reboot from it. You can wait to discharge your phone(Tooks ~2 day with pushed power button) then connect into computer and when the led turn less bright use vol - + power to get into fastboot or disconnect battery and reconnect with pushed vol - to get into fastboot(I have used this three times because of installing wrong recovery).
Aglik-x said:
Literally this guide is really about just how to flash with fastboot instead of Mi Flash(tool which can use anyone with Xiaomi Phone - doesn't require Authorized Service ACC)
I had this problem at the weekend(Stuck at EDL mode - tried to flash with SP tool but without success(needed service acc - brom error)), you can use SP flash tool with authorized service acc - fastest way, maybe there will be some cracked security file in the future as one for redmi 6. Or do battery trick. You are stick at EDL mode and cannot reboot from it. You can wait to discharge your phone(Tooks ~2 day with pushed power button) then connect into computer and when the led turn less bright use vol - + power to get into fastboot or disconnect battery and reconnect with pushed vol - to get into fastboot(I have used this three times because of installing wrong recovery).
Click to expand...
Click to collapse
Thanks a lot for your reply
I will do that. But How I can know that phone is on to discharge battery? Best regards
nutellamarco said:
hello
thanks for your ideas, I can't enter in fastboot mode nor recovery. The screeen is black. When I tried with spflash, when I push together vol+ and vol- i hear a noise, but nothing happens with spflash.
I am trying. I think it is loosed.[/QUOTE
My oneplus 6 I used to do kind of the same thing... With the phone plugged and everything ready to flash... I used to press - plus power button and it would starting the process..
Click to expand...
Click to collapse
petenoni said:
nutellamarco said:
hello
thanks for your ideas, I can't enter in fastboot mode nor recovery. The screeen is black. When I tried with spflash, when I push together vol+ and vol- i hear a noise, but nothing happens with spflash.
I am trying. I think it is loosed.[/QUOTE
My oneplus 6 I used to do kind of the same thing... With the phone plugged and everything ready to flash... I used to press - plus power button and it would starting the process..
Click to expand...
Click to collapse
I try this method, the spflash does not start
I tried all touche combinaisons.
I will wait until the battery were empty and try again.
Thanks for your reply
Click to expand...
Click to collapse
bootloop fix worked for me
I try to post this yesterday but nothing happened so what i did was...
i installed TWRP and in twrp i wipe all data , system, vendor and reboot phone. that was wrong and i stuck in bootloop. so i go back to fastboot and type commands as u say....
fastboot boot boot.img
fastboot flash system.img
fastboot flash vendor.img
fastboot flash cust cust.img
fastboot flash recovery recovery.img - nothing worked
maybe u forgot some commands.... so i use...
fastboot boot boot.img -dont use, it didnt work
fastboot flash system system.img -ok
fastboot flash vendor vendor.img -ok
fastboot flash cust cust.img -ok
fastboot flash recovery recovery.img - but instead of official recovery i used TWRP.img and after reboot a finally boot into TWRP and i flash xiaomi.eu rom and after reboot magisk and all works fine. im not developer but this method worked for me and excuse my english i have global device
So, a few months ago I rooted my device with twrp and then installed magisk manager... A few days later the manager stopped working and I got tired of not being able do do nothing so I tried to unroot. I used mi flash to flash the daisy rom and it didn't work so I tried to load to the twrp app and flash through there. Didn't work either. From then on every time I boot the device it shows the message "the system has been destroyed" and Bc of that I searched for solutions. I kinda found one. I boot to fastboot mode and with the platform tools I write on the command line ". /fastboot devices" and then it shows my device. After I write ". /fastboot boot continue" and it starts booting the device and it has worked for like 2 months but 2 days ago I had to reboot my device Bc it started to freeze but when I load to fastboot mode and plug it to the pc it show a prompt saying "the device is not recognized" and the device reboots to the message "system has been destroyed". Pls help, I've searched everywhere and didn't find any solution
Are you have your bootloader unlocked? I guess no, the most "easy" solution for your problem is test point , never fail, you need to download Qualcomm drivers (search in Google) open your device connect your device, your phone need to be recognized like 9008 in manager drivers of your PC then flash stock room in mi flash (flash all option) my recommendation is flash 10.0.13.0 or 10.0.18 version of stock rom, good luck.
Os_Herdz said:
Are you have your bootloader unlocked? I guess no, the most "easy" solution for your problem is test point , never fail, you need to download Qualcomm drivers (search in Google) open your device connect your device, your phone need to be recognized like 9008 in manager drivers of your PC then flash stock room in mi flash (flash all option) my recommendation is flash 10.0.13.0 or 10.0.18 version of stock rom, good luck.
Click to expand...
Click to collapse
Yes, my bootloader is unlocked, and is not recognized on the miflash tool.
I cant't even boot the phone to edl mode
0flip3 said:
Yes, my bootloader is unlocked, and is not recognized on the miflash tool.
I cant't even boot the phone to edl mode
Click to expand...
Click to collapse
you are trying to get to edl mode by typing command "fastboot oem edl" when phone is in fastboot?
I flashed a custom rom Long time ago. I want to update now because my phone has some weird glitches and updates are available. When I go into recovery i get into Mi recovery (not twrp which I used to have? don't know for sure)
I use FWUL since windows didn't work (usb debuggin enalbe and phone is unlocked). I want to flash TWRP. My device is recognized (both 'normal' and in fastboot). When I tried to flash new file it stops @ sending file fo or sometimes waiting for device (while fastboot devices 2sec before recognized my phone)
What I tried
- fastboot from phone itself and connect (same result)
-when in fastboot en give reboot command, it says rebooting but the phone doesn't restart
so it seems the fastboot doens't work?
any solutions?
thanks in advance