Hi!
I got this new Pixel 7 2 weeks ago, yesterday the battery went completly discharged and now the phone starts into Fastboot mode, with the Enter Reason being boot failure. Recovery mode and rescue mode both fail to load, and just send me back to the Fastboot Mode. I alredy tried a bunch of stuff to fix it, but the phone its still OEM lock so flashing via the Google flash tool its imposible, does anyone has any idea of what can i do to save it?
Did you try this too?
https://pixelrepair.withgoogle.com/carrier_selection
t-ryder said:
Did you try this too?
https://pixelrepair.withgoogle.com/carrier_selection
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
yes, Rescue Mode fails to load, so it gives me Unable to connect the Phone
There's fastboot mode and fastbootD I guess. You can enter fastbootD from fastboot. Maybe I confuse stuff tho, since lately I got a lot of chaos in my head. DYOR.
Have you tried Pixel Flasher?
https://github.com/badabing2005/PixelFlasher/releases
t-ryder said:
There's fastboot mode and fastbootD I guess. You can enter fastbootD from fastboot. Maybe I confuse stuff tho, since lately I got a lot of chaos in my head. DYOR.
Have you tried Pixel Flasher?
https://github.com/badabing2005/PixelFlasher/releases
Click to expand...
Click to collapse
No, i am going to give it a go and update on results
t-ryder said:
There's fastboot mode and fastbootD I guess. You can enter fastbootD from fastboot. Maybe I confuse stuff tho, since lately I got a lot of chaos in my head. DYOR.
Have you tried Pixel Flasher?
https://github.com/badabing2005/PixelFlasher/releases
Click to expand...
Click to collapse
It failed, it gives me "Bootloader is locked, can't flash." and trying to unluck the bootloader with the fastboot commands gives me FAILED (remote: 'flashing unlock is not allowed')
And get into fastbootd and sideload a full OTA somehow?
https://developers.google.com/android/ota?hl=en
Or is adb disabled?
t-ryder said:
And get into fastbootd and sideload a full OTA somehow?
https://developers.google.com/android/ota?hl=en
Or is adb disabled?
Click to expand...
Click to collapse
adb its disabled and entering recovery mode also fails, the phone its pretty much new, so i didn't have time do much with it.
I've seen this before where people's phones have "died" when letting the battery run out. I haven't seen any successful methods to recover (not to say there isn't).
Since you're bootloader is locked and you don't have OEM Unlocking enabled you won't be able to flash anything via fastboot. If OEM Unlocking were enabled you would be able to use Android Flash Tool as that will unlock your bootloader during the process as long as you have OEM Unlocking enabled.
Maybe try to see if Pixel Flasher can get you into recovery mode to see if you can sideload an OTA, although given the circumstances I'm doubtful it will. By the way, you don't need USB Debugging enabled to sideload an OTA. Being in sideload mode enables a very limited set of ADB commands on Pixels, including adb sideload <imagename>.zip.
Good luck...
Lughnasadh said:
I've seen this before where people's phones have "died" when letting the battery run out. I haven't seen any successful methods to recover (not to say there isn't).
Since you're bootloader is locked and you don't have OEM Unlocking enabled you won't be able to flash anything via fastboot. If OEM Unlocking were enabled you would be able to use Android Flash Tool as that will unlock your bootloader during the process as long as you have OEM Unlocking enabled.
Maybe try to see if Pixel Flasher can get you into recovery mode to see if you can sideload an OTA, although given the circumstances I'm doubtful it will. By the way, you don't need USB Debugging enabled to sideload an OTA. Being in sideload mode enables a very limited set of ADB commands on Pixels, including adb sideload <imagename>.zip.
Good luck...
Click to expand...
Click to collapse
Even trying to get into recovery mode with Pixel Flasher fails.. looks like my only option its asking for warranty and i wanted to avoid that.
Have you tried issuing the command fastboot getvar all to see what slot you're on and what the status of your slots are? Maybe switching slots could get you a boot.
41rw4lk said:
Have you tried issuing the command fastboot getvar all to see what slot you're on and what the status of your slots are? Maybe switching slots could get you a boot.
Click to expand...
Click to collapse
Unfortunately their bootloader is locked so they won't be able to switch slots via fastboot commands. Even if they were able to switch slots they would then have to flash the OS to that slot before being able to boot into that slot since you can only boot into the slot where the OS was last flashed in this circumstance.
I can't get over the fact that you can't just flash an official image on a locked bootloader. I used to be a Moto fan and that was always the good thing about them, as long as it was officially signed, locked or not you could flash the same or updated firmware. Plus if it was qualcomm, when you bricked it would go into edl mode and you could blankflash your way back.
Yet a Google device, who also develops android, you're up a creek unless you unlock your bootloader.
Related
OK here is my problem,
I got a brand new Xiaomi Mi5 64GB and the first thing that I did was to connect it with Mi PC Suite to check for updates.
It found an update and started to update until it failed, after that the device couldn't normal boot or recovery boot (Vol+ and POWER went to a black screen with "mi logo" same as normal boot).
View attachment 3788573
I can only boot on fastboot mode, but can't do anything in the fastboot as BL is locked.
Official BL unlocking method can't work as device isn't linked to any Mi Account and MiFlashUnlock can't verify my device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So my questions is, can I someway repair my phone with QPST or would you suggest another solution?
en.miui.com/thread-291785-1-1.html
wissou050987 said:
en.miui.com/thread-291785-1-1.html
Click to expand...
Click to collapse
in this guide have to boot into recovery, i CANT boot into recovery, got no recovery.
you have to flash with miflash tool booting into fastboot then
wissou050987 said:
you have to flash with miflash tool booting into fastboot then
Click to expand...
Click to collapse
MiFlash cant flash anything as bootloader is locked.
Try: http://en.miui.com/thread-291785-1-1.html
It works fine
tiflao said:
Try: http://en.miui.com/thread-291785-1-1.html
It works fine
Click to expand...
Click to collapse
Read OP again please.
1. I CAN'T boot into recovery.
2. I CAN'T boot EDL.
3. I CAN boot just into Fastboot, but Bootloader is Locked.
4. I CAN'T unlock BL via official methode as there is no linked Mi Account on Device.
I think that i need a hardware way to unlock BL.
Have you tried this method to see if it works?
http://forum.xda-developers.com/redmi-note-3/how-to/guide-reboot-to-edl-mode-fastboot-test-t3398718
http://forum.xda-developers.com/and.../guide-how-to-reboot-to-edl-fastboot-t3394292
VirusPlus said:
Read OP again please.
1. I CAN'T boot into recovery.
2. I CAN'T boot EDL.
3. I CAN boot just into Fastboot, but Bootloader is Locked.
4. I CAN'T unlock BL via official methode as there is no linked Mi Account on Device.
I think that i need a hardware way to unlock BL.
Click to expand...
Click to collapse
You CAN boot into recovery, don't be silly. Have you read the instructions?
Hold volume up and power button and a MI logo should came up, that's the recovery.
abyssq said:
You CAN boot into recovery, don't be silly. Have you read the instructions?
Hold volume up and power button and a MI logo should came up, that's the recovery.
Click to expand...
Click to collapse
Recovery was a black screen with a white phone, not "mi".
Phone is not detectable anyway if i normally or vol+ boot.
Im not a noob i know what recovery is, so i need answers with the facts that i mention before, no recovery, no edl, unlockable bl.
Im gonna send it to repair shop anyway but still my situation is a big problem that xiaomi should look into it. I get bricked via official update tool, and i cant unlock bl cause xiaomi's unlocking tool stupidly requires linked mi account on device to verify.
When you boot into fastboot and update in mipc suite, it doesn't work ?
I don't understand why official tool need unlock bootloader, it's insane from Xiaomi
rcd1030 said:
When you boot into fastboot and update in mipc suite, it doesn't work ?
I don't understand why official tool need unlock bootloader, it's insane from Xiaomi
Click to expand...
Click to collapse
Mi PC Suite doesn't recognize device in fastboot mode, it returns a screen to connect in normal mode first.
Only MiFlash can see the device in fastboot but it needs unlocked BL to flash the Official fastboot ROMs. Madness!
Aarff just, you're right
Just speculation but maybe can you reboot in recovery with adb commands ? (adb reboot recovery)
Or maybe download twrp, run shell from where it is saved and run
Code:
fastboot boot twrp.img[
?
VirusPlus said:
Recovery was a black screen with a white phone, not "mi".
Phone is not detectable anyway if i normally or vol+ boot.
Im not a noob i know what recovery is, so i need answers with the facts that i mention before, no recovery, no edl, unlockable bl.
Im gonna send it to repair shop anyway but still my situation is a big problem that xiaomi should look into it. I get bricked via official update tool, and i cant unlock bl cause xiaomi's unlocking tool stupidly requires linked mi account on device to verify.
Click to expand...
Click to collapse
Oh yes sorry, it's a phone, my bad.
Then the recovery works fine for you, just the PC doesn't recognise it, which is driver or windows problem, not your phone.
SpinoRex: Fastboot doesn't work because of the locked bootloader. Only option is the official recovery with chinese mi pc suite.
check this post : en.miui. com/thread-299790-1-1.html
You need Engineering Flash Cable
They are in the same situation ... solved?
Mi suite in chinese
You may try to use MI SUITE in Chinese. I was in your exact situation trying to remove a fake rom from my MI5, but with this I solved all the issues.
Just one advice: don't use a pre-loaded ROM, let the program to download it from the internet.
you can boot your device into edl mode with a special fastboot
just type "fastboot reboot" to go to the Edl mode and flash rom with miFlash
If i return to Stock with ADB, but not Relock Bootloader, when we received OTA Oreo, can i accept this or brick my phone with bootloader unlocked?
Flash a full stock firmware using fastboot..a matching build as per your software channel
If all partitions are unmodified and stock recovery is installed ( Must for ota installation)..you will be able to install Oreo even if your bootloader is unlocked.. applicable for all type of OTA.
I've successfully received OTA ( Monthly security patch) and installed properly after returning to stock with unlocked bootloader.
Caution : all partitions must be untouched.
No ADB/FASTBOOT on bootloader after OTA update on stock ROM rooted phone
Good evening. I hope you can help me. I'm sorry if I'm posting in the wrong place on the forum. I have already looked everywhere in the www and found nothing to solve my problem.
I have a g5s plus XT1802 rooted. I already tested several roms and was recently at AOSP Extended. Tired of not having dual cam working I decided to reinstall rom stock. I installed and it worked normally until my son decided to do an OTA update. My phone crashed into bootloop straight to recovery. I tried to solve several ways, I got to install other roms via twrp but nothing solved. Finally through the bootloader I decided to use the START function and my device is working again.
After that, every time I reboot the device it goes straight to recovery (TWRP) and I need to enter the bootloader to use the START option.
I tried to reinstall rom stock again using adb / fastboot however after this problem the device is recognized by adb / fastboot devices command only when the cell phone is turned on. When I am in the bootloader it does not recognize. I would like to reinstall the rom stock but without adb it is not possible. Can someone help me?
guguptb said:
Good evening. I hope you can help me. I'm sorry if I'm posting in the wrong place on the forum. I have already looked everywhere in the www and found nothing to solve my problem.
I have a g5s plus XT1802 rooted. I already tested several roms and was recently at AOSP Extended. Tired of not having dual cam working I decided to reinstall rom stock. I installed and it worked normally until my son decided to do an OTA update. My phone crashed into bootloop straight to recovery. I tried to solve several ways, I got to install other roms via twrp but nothing solved. Finally through the bootloader I decided to use the START function and my device is working again.
After that, every time I reboot the device it goes straight to recovery (TWRP) and I need to enter the bootloader to use the START option.
I tried to reinstall rom stock again using adb / fastboot however after this problem the device is recognized by adb / fastboot devices command only when the cell phone is turned on. When I am in the bootloader it does not recognize. I would like to reinstall the rom stock but without adb it is not possible. Can someone help me?
Click to expand...
Click to collapse
pass these commands through fastboot
fastboot oem fb_mode_set
fastboot oem fb_mode_clear
jakson7474 said:
pass these commands through fastboot
fastboot oem fb_mode_set
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
As soon as I get home today, I'll try this, thank you!
---------- Post added at 09:54 AM ---------- Previous post was at 09:45 AM ----------
joaonds said:
If i return to Stock with ADB, but not Relock Bootloader, when we received OTA Oreo, can i accept this or brick my phone with bootloader unlocked?
Click to expand...
Click to collapse
The problem I'm having is exactly because of this, take care...
So long as you have the stock recovery installed OTA's work fine. My bootloader is unlocked and I'm rooted, but I can receive OTA updates
Same problem
jakson7474 said:
pass these commands through fastboot
fastboot oem fb_mode_set
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
Could not do this.
When my phone is turned on adb recongnize the phone, but fastboot dont and in bootloader either adb and fastboot dont recongnize device.
I have already tried it on a mac and 5 diferent windows computer and same things happens...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
William1020000 said:
So long as you have the stock recovery installed OTA's work fine. My bootloader is unlocked and I'm rooted, but I can receive OTA updates
Click to expand...
Click to collapse
the problem that happend to my phone is because this... after installed a custom rom, and get back to stock rom... OTA update got me to a bootloop... and fastboot dont recgonize my device anymore
1) Does not boot to TWRP. FAILED (remote: Failed to load / authenticate boot image: Load Error)
2) The bootloader is unlocked and can not be unlocked. FAILED (remote: Flashing Unlock is not allowed
3) Therefore I can not flash images of any kind, nor use MiFlashTool
4) MiUnlock does not work (current account can not unlock this device)
5) "Corrupted device" appeared, now it only stays locked in the "Android One" logo.
6) This happened to accidentally block the bootloader after trying to install the beta of Pie (which as it says in the post, you can not point them with your finger, but when you try to put the command "flashing critical" it tells you that the device is locked with oem unlocked and everything breaks.)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any suggestions? Is there something to do, or direct to the trash?
I think deep flash with test points is the cure. Check xda and Google you'll find the method, you'll have to disassemble your phone though.
if you can enter fastboot you should be able to enter EDL aswell. Did you try MiFlash in EDL?
windforce3425 said:
if you can enter fastboot you should be able to enter EDL aswell. Did you try MiFlash in EDL?
Click to expand...
Click to collapse
C:\Users\guzma>fastboot oem edl
< waiting for device >
...
FAILED (remote: Device is already locked!)
finished. total time: 0.030s
The only possibility to get into EDL would be with test points but even with that you have no guarantee it will actually work out. Also that would void your warranty. Have you tried contacting Xiaomi and try to explain them your problem?
I have the same issue. Device is stuck on android one logo overnight. No changes were made to the device.
I tried the miflash and i get same error Flashing is not allowed in lock state.
If i try and using Fastboot OEM Unlock i get the following:
C:\Tools\platform-tools>fastboot.exe oem unlock
FAILED (remote: 'Flashing Unlock is not allowed
')
Finished. Total time: 0.008s
If i use the fastboot that came with the mi unlock tool, i get the following error
C:\Users\Downloads\miflash_unlock_en_3.3.827.31>fastboot.exe oem unlock
argc is 2
Anyone have any suggestions?
Flash the rom by fastboot or flash stock image and then only boot tge twrp image.
This might be solve your problem.
And main tip keep your device charge if battery will totally drain then your device will not stand on his speakers.
I have that experience with my past device which has same problem.
The fix for this is flash rom stock with Mi Flash in EDL Mode (touch test points with two clips, battery and screen flex connected, and connect to PC (with qualcomm hs drivers).
In miflash appears "com##" and u can flash the rom.
u need a kit to dissamble it
AlvaroBenitez99 said:
The fix for this is flash rom stock with Mi Flash in EDL Mode (touch test points with two clips, battery and screen flex connected, and connect to PC (with qualcomm hs drivers).
In miflash appears "com##" and u can flash the rom.
u need a kit to dissamble it
Click to expand...
Click to collapse
Did you fix yours?
So if I can't get into Developer Mode to enable OEM unlocking, (Reason being device is stuck on Android One Bootup Logo) is my only option to try and get device into EDL mode in order to flash it?
Or can I use an EDL cable and will that get around me having to open up the device?
After having device sit as a paper weight for a few months, i broke down and ordered a phone repair kit. Opened device up and flashed via test point method. Worked Flawless. Time to enable OEM unlock so i don't have to open it up again. Thanks to community for all the help.
Thanks, it worked for me. My client Mi A2 now live it own life
I install jasmine__V10.0.8.0.PDIMIXM and after I set "fastboot oem lock" but Now my MI A2 Can't enter in OS.
I have this message on screen
"Your device has loaded a different operation system"
and another page says
"Your device software can'tbe checked for corruption. Plese lock the bootlader.
But when I check in fastboot I have bootloader locked.
Any suggestion to unlock ? I can't enter in OS.
Thanks
I had a similar issue and I solved it by entering fastboot mode and using the "fastboot flashing unlock_critical" method. After that I could flash the stock rom with MiFlash Tools.
Hello, I never experienced this before so here I am trying to find some explanation, hopefully it's the right place... I have a Xiaomi Mi 5 Pro, few years old, sometimes slow but otherwise perfect, I changed the battery couple times.
Today I noticed it was at around 20% charge, I plug it to the wall, and leave it on the bed (turned on). After a few hours I go back to check on it and found the 100% indicator, but the phone was turned off.
I obviously try to turn it back on, but it gets stuck at the Mi logo (black screen with "unlocked" text below). I have installed a MIUI.eu rom ver. 11, twrp 3.2.3-0 recovery, and everything has been fine for years. I tried several times, still Mi logo (it's not bootloop, it's just stuck).
Suprised, I try to boot into recovery, and there I noticed that all the partitions are marked empty 0 bytes. I tried several things like backup, switching file format, restoring file system, etc., but it just won't work. It's like it has all been wiped and can't be mounted again.
I connected it to my desktop, MTP enabled from twrp, device recognized, storage completely empty. I remember I could see files there just the other day...
I tried all possible wipes, they won't work, either can't mount the partitions or other errors.
I already asked for suggestions elsewhere, which pointed me to fastboot flash using the adb/fastboot tools on Windows.
Well it says "Looking for devices...", the fastboot screen on the phone stays there for about 30 seconds, then it goes to the black Mi logo and then it shuts down.
Also if I boot in recovery, I can see it detected in the adb/fastboot tools screen, the scary part is that there it says "Bootloader: locked" (but it has been unlocked for years, and it even says unlocked in the black Mi screen!)
I'm lost, I never had anything like this, any suggestions to save the device? I would be really grateful
ZexDC said:
Well it says "Looking for devices...", the fastboot screen on the phone stays there for about 30 seconds, then it goes to the black Mi logo and then it shuts down.
Click to expand...
Click to collapse
You probably don't have proper drivers for Mi 5 installed, download MIFLASH UNLOCK 3.5.1108.44 from here https://xiaomifirmware.com/downloads/download-mi-unlock-3-5-1108-44/
Double click on MiUsbDriver and install fastboot driver. Then phone will stay in fastboot mode when connected to PC, so you can try to install some original fastboot rom. I don't know what is the problem.
Indie Zex said:
You probably don't have proper drivers for Mi 5 installed, download MIFLASH UNLOCK 3.5.1108.44 from here https://xiaomifirmware.com/downloads/download-mi-unlock-3-5-1108-44/
Double click on MiUsbDriver and install fastboot driver. Then phone will stay in fastboot mode when connected to PC, so you can try to install some original fastboot rom. I don't know what is the problem.
Click to expand...
Click to collapse
Thanks it was the driver stopping the fastboot.
Now I still cannot flash anything though, I get the following error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tried different roms, different MiFlash, from terminal, but same error.
From recovery I still see empty not mounted partitions.
Any other suggestions?
Well I don't know. Have you tried to format data in TWRP? Go into Wipe/Format Data/type yes (this will wipe EVERYTHING on phone) then from main menu reboot into recovery again and see if things changed.
Indie Zex said:
Well I don't know. Have you tried to format data in TWRP? Go into Wipe/Format Data/type yes (this will wipe EVERYTHING on phone) then from main menu reboot into recovery again and see if things changed.
Click to expand...
Click to collapse
Yes that was the first thing I tried unfortunately that's where I found out something was off... I can't wipe any partition, I can't mount any partition, I tried to switch filesystem but no luck.
I was reading in the forums here about "sudden death" and it kinda feels that's what happened. Phone fine one day, dead the next with no real explanation...
ZexDC said:
I was reading in the forums here about "sudden death" and it kinda feels that's what happened. Phone fine one day, dead the next with no real explanation...
Click to expand...
Click to collapse
That's a bummer. I don't think that phone is dead, but it looks that it somehow locked itself. According to this guide https://flash-er.com/xiaomi-mi-5-flash-file/ you can flash fastboot roms only on unlocked devices. But you can't unlock it now in this state...
Indie Zex said:
That's a bummer. I don't think that phone is dead, but it looks that it somehow locked itself. According to this guide https://flash-er.com/xiaomi-mi-5-flash-file/ you can flash fastboot roms only on unlocked devices. But you can't unlock it now in this state...
Click to expand...
Click to collapse
It's very weird, I've been flashing lots of stuff in the past but I've never been locked out like this.
And the joke is that the black Mi logo screen still says "unlocked" as it should be... no idea, maybe it is programmed to just give up after some years.
Could be that your TWRP recovery is corrupted. You can install new one from a fastboot mode:
1. Copy latest twrp-3.5.2_9-0-gemini.img to your fastboot tools location on PC
2. Put the phone in fastboot mode (power + volume down) and connect it to the computer
3. Enter these commands in cmd prompt:
fastboot flash recovery twrp-3.5.2_9-0-gemini.img
fastboot boot twrp-3.5.2_9-0-gemini.img
Then the phone will boot into new TWRP so you can check if it's ok.
Indie Zex said:
Could be that your TWRP recovery is corrupted. You can install new one from a fastboot mode:
1. Copy latest twrp-3.5.2_9-0-gemini.img to your fastboot tools location on PC
2. Put the phone in fastboot mode (power + volume down) and connect it to the computer
3. Enter these commands in cmd prompt:
fastboot flash recovery twrp-3.5.2_9-0-gemini.img
fastboot boot twrp-3.5.2_9-0-gemini.img
Then the phone will boot into new TWRP so you can check if it's ok.
Click to expand...
Click to collapse
I tried that, it gives the following error:
I noticed that even from MiFlash the device id sometimes disappears, not sure if that's the no link error
I really don't know what's going on. Maybe you can try this tutorial (it is for Mi 9, but can be applied to all Mi phones)
Indie Zex said:
I really don't know what's going on. Maybe you can try this tutorial (it is for Mi 9, but can be applied to all Mi phones)
Click to expand...
Click to collapse
Thanks for trying I really appreciate. I did follow the tutorial, same error.
It's like the internal storage got fried or something? I have no clue
So I restarted my phone today and it just entered an infinite boot loop. Not sure what happened but that's all it's doing whenever I turn it on. I can enter the bootloader but other than that nothing is working. I noticed the bootloader and baseband are empty as well.
I wish this phone had an unbrick tool like the oneplus 7 devices but I don't know. I guess I may just have a brick until someone shakes.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
biglo said:
So I restarted my phone today and it just entered an infinite boot loop. Not sure what happened but that's all it's doing whenever I turn it on. I can enter the bootloader but other than that nothing is working. I noticed the bootloader and baseband are empty as well.
I wish this phone had an unbrick tool like the oneplus 7 devices but I don't know. I guess I may just have a brick until someone shakes.
View attachment 5694575
Click to expand...
Click to collapse
Are you rooted? Can you get in recovery? What model number?
twinnfamous said:
Are you rooted? Can you get in recovery? What model number?
Click to expand...
Click to collapse
Was rooted, can get to recovery using the enhanced flash tool and model is 2210.
biglo said:
Was rooted, can get to recovery using the enhanced flash tool and model is 2210.
Click to expand...
Click to collapse
Have you tried flashing stock boot.img or factory resetting?
twinnfamous said:
Have you tried flashing stock boot.img or factory resetting?
Click to expand...
Click to collapse
Yes, I tried both options without success.
biglo said:
Yes, I tried both options without success.
Click to expand...
Click to collapse
That's not good usually one or the other fixes it. Only thing I can think of is flashing all images in fastboot. But try vendor_boot first
When this happened to me on my OP6 when I had it and when I couldn't recover it with MSM tools or boot.img, I decided it is motherboard failure.
But I would try fastboot ROM if I were you. If it doesn't help, I will send it to the service center.
You may have booted a patched yet not made it permanent so when you rebooted you lost it.
If that rings a bell then just boot a patched boot image. Not flash.. once you're booted and in the system just open magisk and click direct install..
Reboot and it should be permanent.
Beyond that you can go to recovery or fastboot to get back in business although you'll lose your data
My phone did this once when I accidentally changed A/B partition, try switching partition via fastboot
Do the following
fastboot getvar all
then you'll get somewhere the following
(bootloader) current-slot:A or B
then you should be able to do either
fastboot set_active other
or either
fastboot set_active a
fastboot set_active b
unsafe8989 said:
My phone did this once when I accidentally changed A/B partition, try switching partition via fastboot
Do the following
fastboot getvar all
then you'll get somewhere the following
(bootloader) current-slot:A or B
then you should be able to do either
fastboot set_active other
or either
fastboot set_active a
fastboot set_active b
Click to expand...
Click to collapse
I tried switching slots the other day, it gave me the same results.
hello did you found any solutions?
biglo said:
I tried switching slots the other day, it gave me the same results.
Click to expand...
Click to collapse
That means you have no boot img on it
try to flash a boot img to slot a and slot b
Is this still ongoing?? Lol that's insanity.
The reason you cannot boot is 100% your boot image.
So either boot or flash a boot image (stock or patched)
If you'd like to reflash your whole phone then click on vol up and then recovery.
If you're looking for a tool then grab fastboot enhance, whilst in fastboot use it to remove the cow files, search for them, once that's done, flash a payload.bin and this will reload your whole OS.
There are guides for everything I've mentioned above, just search.
dladz said:
Is this still ongoing?? Lol that's insanity.
The reason you cannot boot is 100% your boot image.
So either boot or flash a boot image (stock or patched)
If you'd like to reflash your whole phone then click on vol up and then recovery.
If you're looking for a tool then grab fastboot enhance, whilst in fastboot use it to remove the cow files, search for them, once that's done, flash a payload.bin and this will reload your whole OS.
There are guides for everything I've mentioned above, just search.
Click to expand...
Click to collapse
Hi,
I have the same problem. Never used the phone. Just to install Magisk and edit the payload.bin file. When I installed the new boot file via Fastboot it went wrong.
Tried everything but can't get the phone out of the loop. I don't have a recovery function!
You indicate that there are manuals for existing solutions everywhere. Do you have the links for me? Not very good at finding this.
*-MaCK-* said:
Hi,
I have the same problem. Never used the phone. Just to install Magisk and edit the payload.bin file. When I installed the new boot file via Fastboot it went wrong.
Tried everything but can't get the phone out of the loop. I don't have a recovery function!
You indicate that there are manuals for existing solutions everywhere. Do you have the links for me? Not very good at finding this.
Click to expand...
Click to collapse
Doesn't help that the forums went through a crap update that broke the sections.
That being said, you're looking for a guide so that's your key word.
(Guide) Rooting, payload dumper, magisk_patched guides NE2213
Hi all, Thought i'd share a guide on how to get these boot images yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it without obtaining one yourself Please read the process before...
forum.xda-developers.com
There's a good few of them, the screen shot is taken from the main OnePlus 10 pro forum section, I can see two. Mine and the 2215 one.
Also when you say 'installed' I hope you meant boot and not flash, booting is risk free.. Read my thread and it'll make sense.
I wish people would read more...cause it all here...just need to take the time and read alot of post...to find what they are looking for...lol