I recently flashed the new LineageOS 17 based on Android 10 but I did it using a non-SAR TWRP. I realized later. The flash went nice and I can use the phone with LOS17 but without Gapps, cause after I flashed the rom the recovery disapperead and I couldn't flash them. Now I can't do nothing cause for some reason I can't flash any kind of Custom Recovery through fastboot (it doesn't even start the process) and Mi Flash doesn't recognize at all my phone as a Mi Mix 2 so I can't flash Miui.
Does someone know what could I do? Thanks in advance
It could be a problem with the computer, did you try with another computer?
Yeah I tried with two computers with ADB drivers from different sources. Thank you for your reply
Did you try to flash stock rom with mi flash? Maybe you can do this and the go back to another rom
Yes, this is what happens. I waited for hours but nothing happened.
Are you using always the same cable? Did you try another one? Is your usb port clean?
Yep, I tried this kind of things. I switched from an USB 3.0 to 2.0 and viceversa, tried with the official cable i always used and some others I have. I think some partitions are damaged or gone
Well... Do you have enabled usb debugging and oem unlocking in your developer options?
Maybe you can get into EDL mode, search for it on XDA
atembleque said:
Well... Do you have enabled usb debugging and oem unlocking in your developer options?
Maybe you can get into EDL mode, search for it on XDA
Click to expand...
Click to collapse
Yeah I checked again on LineageOS and I have debugging on. I could try with EDL, but isnt it the same as fastboot? From what I know EDL is useful for phones that cant boot into fastboot because theyre bricked or something. I think I will receive the same error i posted early, but i'll try anyway. Thanks again.
Nvm worked with EDL im now on MIUI 11 completely stock as I wanted thank you so much for the help
Please post the link of the guide you followed
Davv said:
Nvm worked with EDL im now on MIUI 11 completely stock as I wanted thank you so much for the help
Click to expand...
Click to collapse
can you please guide me for the same issue? i am not able to flash original recovery or twrp. its lost. i need to flash everything back to stock.
Related
My One Plus 3 managed to delete its own Operating System, USB Debugging wasnt enabled, the Bootloader is not unlocked, its not rooted either and I dont have a custom recovery like TWRP installed. I tried to flash it wtih the adb console commands but it stops at some percentage and the device says that the installation failed (tried this with cm, oxygen and pacman). I tried to install TWRP over fastboot but cant manage it because USB Debugging isnt activated. I dont know what to do and need help
PS: Hope this Post is in the right thread
SolomonOdonkah said:
My One Plus 3 managed to delete its own Operating System, USB Debugging wasnt enabled, the Bootloader is not unlocked, its not rooted either and I dont have a custom recovery like TWRP installed. I tried to flash it wtih the adb console commands but it stops at some percentage and the device says that the installation failed (tried this with cm, oxygen and pacman). I tried to install TWRP over fastboot but cant manage it because USB Debugging isnt activated. I dont know what to do and need help
PS: Hope this Post is in the right thread
Click to expand...
Click to collapse
bro, do you even google?
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
bombaglad said:
bro, do you even google?
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Click to expand...
Click to collapse
I did but didn't found that thread, but thanks mate
SolomonOdonkah said:
I did but didn't found that thread, but thanks mate
Click to expand...
Click to collapse
that is literally the first thing on the list if you google "oneplus 3 unbrick" but i'm glad i helped, that thread saved my ass several times already
Hey guys,
I've got a Oneplus 3 that freezes every time it tries to boot. Fastboot and recovery are still working, factory reset makes no difference. After sideloading the latest OxygenOs the screen just goes blank after the Oneplus splash screen and recovery doesn't work anymore. The MsmDownloadTool only gets me where I started, back at the bootloop. So the old OOS gives me bootloop with recovery and fastboot while the new OOS only gives me fastboot and a blank screen.
New system with old working boot and recovery gives "md5 checksum failed".
The bootloader is locked and as long as I can't get in the settings there is no way to unlock it, so my options are pretty limited here.
I've contacted Oneplus but they aren't really helping either.
Is there any way to get this thing back to life?
Robert1852 said:
Hey guys,
I've got a Oneplus 3 that freezes every time it tries to boot. Fastboot and recovery are still working, factory reset makes no difference. After sideloading the latest OxygenOs the screen just goes blank after the Oneplus splash screen and recovery doesn't work anymore. The MsmDownloadTool only gets me where I started, back at the bootloop. So the old OOS gives me bootloop with recovery and fastboot while the new OOS only gives me fastboot and a blank screen.
New system with old working boot and recovery gives "md5 checksum failed".
The bootloader is locked and as long as I can't get in the settings there is no way to unlock it, so my options are pretty limited here.
I've contacted Oneplus but they aren't really helping either.
Is there any way to get this thing back to life?
Click to expand...
Click to collapse
https://forum.xda-developers.com/on...mega-unbrick-guide-hard-bricked-t3405700/amp/
That always works.. use method 2
dmilz said:
https://forum.xda-developers.com/on...mega-unbrick-guide-hard-bricked-t3405700/amp/
That always works.. use method 2
Click to expand...
Click to collapse
Not this time... That is the tool I mentioned, only gets me back to the bootloop
Robert1852 said:
Not this time... That is the tool I mentioned, only gets me back to the bootloop
Click to expand...
Click to collapse
I know what you talking about.. Went through that too when i used method one.. use method 2..it will flash stock OOS and you will boot successfully
If you already did..try once more..download the tools over again
dmilz said:
I know what you talking about.. Went through that too when i used method one.. use method 2..it will flash stock OOS and you will boot successfully
If you already did..try once more..download the tools over again
Click to expand...
Click to collapse
Yeah already tried method 2 multiple times, downloaded the tools again but it still doesn't work on this phone..
Robert1852 said:
Yeah already tried method 2 multiple times, downloaded the tools again but it still doesn't work on this phone..
Click to expand...
Click to collapse
Ooh ok.. i see.. hope you will find a way out
Robert1852 said:
Yeah already tried method 2 multiple times, downloaded the tools again but it still doesn't work on this phone..
Click to expand...
Click to collapse
Probably a stupid question but have you tried flashing oxygen os recovery and then tried to flash stock ROM?
Xceeder said:
Probably a stupid question but have you tried flashing oxygen os recovery and then tried to flash stock ROM?
Click to expand...
Click to collapse
That unbrick tool also flashes the stock recovery. I cant flash anything using fastboot because the bootloader is locked
Robert1852 said:
That unbrick tool also flashes the stock recovery. I cant flash anything using fastboot because the bootloader is locked
Click to expand...
Click to collapse
And why is it locked then? Why would you ever relock your bootloader? You should be able to unlock it anyway without going in to settings. Are you sure you are using the correct drivers? Windows installs the wrong once by default.
Puddi_Puddin said:
And why is it locked then? Why would you ever relock your bootloader? You should be able to unlock it anyway without going in to settings. Are you sure you are using the correct drivers? Windows installs the wrong once by default.
Click to expand...
Click to collapse
It has never been unlocked. In the settings is the "Allow OEM Unlock" option which you should check before you can unlock the bootloader. As long as I can't boot the phone I can't check this option, or someone must know a workaround. Yes I'm pretty sure I'm using the correct drivers
Robert1852 said:
It has never been unlocked. In the settings is the "Allow OEM Unlock" option which you should check before you can unlock the bootloader. As long as I can't boot the phone I can't check this option, or someone must know a workaround. Yes I'm pretty sure I'm using the correct drivers
Click to expand...
Click to collapse
If you plug your phone in how does it show up under Device Manager? Have you also tried "fastboot OEM Unlock"?
Puddi_Puddin said:
If you plug your phone in how does it show up under Device Manager? Have you also tried "fastboot OEM Unlock"?
Click to expand...
Click to collapse
When it's in the bootloader menu it shows up as "Android Bootloader Interface", when it's in EDL mode it shows up as "Qualcomm HS-USB QDLoader 9008 (COM3)". It connects fine with the pc and flashes everything without problems as far as I can see. Yeah it says "FAILED (remote: oem unlock is not allowed)" probably because the allow oem unlock option in the settings isn't checked.
Most likely won't do anything, but have you tried a different computer? Seems like it would make no difference but tiny things like that have saved me in the past.
ZVNexus said:
Most likely won't do anything, but have you tried a different computer? Seems like it would make no difference but tiny things like that have saved me in the past.
Click to expand...
Click to collapse
Yea I know what you mean I tried it on a few different computers, even with different cables but it doesn't make a difference...
Robert1852 said:
Yea I know what you mean I tried it on a few different computers, even with different cables but it doesn't make a difference...
Click to expand...
Click to collapse
Pretty sure you are using wrong drivers. You should be able to unlock the bootloader even tho it is remote. When I first bricked my phone I forgot about the drivers aswell. My phone booted up and showed. System: Failed, Userdata:Failed. This means it failed to detect those partitions which you can find in unbrick program itself called system.img, userdata.img. You can actually flash these manually with fastboot flash system system.img but I also got the "Remote is not allowed error". After booting into disabled Driver Signature Enforcement mode and changing the drivers from on the guide I could actually flash these partitions. Your phone has to show up as Qualcomm 9008 or something close and not as Android Interfere Device. I have helped multiple people fixing their phone with this guide and they also had a locked bootloader and they also did not have the correct drivers.
Boot into https://www.google.com/amp/s/www.ho...so-that-you-can-install-unsigned-drivers/amp/ then install the driver linked on the Unbrick Guide. Your phone should show up correctly. Then run the unbrick guide as admin and it should go through flawless.
Puddi_Puddin said:
Pretty sure you are using wrong drivers. You should be able to unlock the bootloader even tho it is remote. When I first bricked my phone I forgot about the drivers aswell. My phone booted up and showed. System: Failed, Userdata:Failed. This means it failed to detect those partitions which you can find in unbrick program itself called system.img, userdata.img. You can actually flash these manually with fastboot flash system system.img but I also got the "Remote is not allowed error". After booting into disabled Driver Signature Enforcement mode and changing the drivers from on the guide I could actually flash these partitions. Your phone has to show up as Qualcomm 9008 or something close and not as Android Interfere Device. I have helped multiple people fixing their phone with this guide and they also had a locked bootloader and they also did not have the correct drivers.
Boot into https://www.google.com/amp/s/www.ho...so-that-you-can-install-unsigned-drivers/amp/ then install the driver linked on the Unbrick Guide. Your phone should show up correctly. Then run the unbrick guide as admin and it should go through flawless.
Click to expand...
Click to collapse
Tried everything it says in the guide about the drivers (even the last part about installing the certificates) but it just keeps showing up as qualcomm hs-usb qdloader 9008, even though I'm pretty sure they are installed correctly. It just won't show up as Qualcomm 9008, as it is supposed to, whatever I try. But it looks like these drivers are only for the EDL mode, and as far as I know it is normal for the phone to show up as Android Bootloader Interface when it's in the bootloader menu. And you can't use fastboot from EDL mode... Will try it later again on a different pc though, really hope you are right about the drivers after all
Hi Robert,
I am having same problem with my oneplus3. I also tried both unbrick methods and tried different oxygen ROMs.
Are you able to fix your phone?
Thanks in Advance,
Anil
Have you tried this http://www.androidbrick.com/oneplus-one-two-3-3t-5-mega-unbrick-guide-twrp-flashing/
Robert1852 said:
Hey guys,
I've got a Oneplus 3 that freezes every time it tries to boot. Fastboot and recovery are still working, factory reset makes no difference. After sideloading the latest OxygenOs the screen just goes blank after the Oneplus splash screen and recovery doesn't work anymore. The MsmDownloadTool only gets me where I started, back at the bootloop. So the old OOS gives me bootloop with recovery and fastboot while the new OOS only gives me fastboot and a blank screen.
New system with old working boot and recovery gives "md5 checksum failed".
The bootloader is locked and as long as I can't get in the settings there is no way to unlock it, so my options are pretty limited here.
I've contacted Oneplus but they aren't really helping either.
Is there any way to get this thing back to life?
Click to expand...
Click to collapse
Hi
Go back to an older Version...3.xx
worked for me
be warned ..3.xxx formats internal memory
I also have the same problem, I'll try to restore to old version too.
Do you also have artifacts on the screen?
Hi all,
After reading many posts i got a little confused and i'm not getting any result. Please help.
What i want?: Flash stock rom and later consider rooting, and flashing haden or lineagos. (already found guidance but..)
The issue?: It doesn't get recognized through USB with my PC. (drivers installed, cable connected but...)
My questions? (correct me if wished):
1) In Odin mode (which i enter) is the usb port enabled by default? or it depends on the phone configuration.
2) In recovery mode i still cannot see the phone through the USB so is it open by default on stock recovery?
3) Finally can i flash stock rom i downloaded from sammobile through SD card? i found that to be my last resort but i think odin actual proper way or not?
I first thought it was the cable...since is not the original but it seems not be the case...which leads me to think its the phone's usb port....but with the cable i can charge the phone although i cannot see it through my PC.
So bottom line if the answer to my questions are that is always open (accesible through usb port) then it HAS to be the cable right?
If last quesiton is possible then i will conclude my searchings to be ended for now.
Thanks to all the posts within this tree.
Findings
Is it normal that when boot to bootloader from stock recovery the ADB console keeps <waiting for device> while phone actually boots normaly?
I found that bootloader booting is accesible through fastboot independently from USB debugging option...
I'm considering buying official usb cable but store guy confirmed it works for data/power uses...
There definitely is a way to flash stock via TWRP, i once did that myself. However you need a dedicated tool on the PC to create a flashable zip, because the firmware can't be flashed by itself
Edit: i saw that you have FRP-lock enabled. Search for a guide on how to disable it and try again
verdugon said:
Is it normal that when boot to bootloader from stock recovery the ADB console keeps <waiting for device> while phone actually boots normaly?
I found that bootloader booting is accesible through fastboot independently from USB debugging option...
I'm considering buying official usb cable but store guy confirmed it works for data/power uses...
Click to expand...
Click to collapse
Are you on Samsung? If so, they don't have fastboot. Nor can you boot to bootloader. Do
Do you have the drivers installed? I have yet to see an unofficial cable not work for data transfer. Excepting damaged ones.
Light at the end of the tunnel!!!
PMFRTT said:
There definitely is a way to flash stock via TWRP, i once did that myself. However you need a dedicated tool on the PC to create a flashable zip, because the firmware can't be flashed by itself
Edit: i saw that you have FRP-lock enabled. Search for a guide on how to disable it and try again
Click to expand...
Click to collapse
Thanks PMFRTT!! I finally disabled FRP-lock and phone is usable again. I now will try to unlock OEM bootloader and enable USB debugging to see what happens. Thanks
Light at the end of the tunnel!!!
SnowFuhrer said:
Are you on Samsung? If so, they don't have fastboot. Nor can you boot to bootloader. Do
Do you have the drivers installed? I have yet to see an unofficial cable not work for data transfer. Excepting damaged ones.
Click to expand...
Click to collapse
Thanks @SnowFuhrer for your reply.
To answer your question yes its SMSUNG. I didn't know about that Thx.
The cable is brand knew but i noticed now that the phone is usable that is claims its on slow charge...may be my PC is quite old now....
Like i said i will try to unlock bootloader and make it accesible to odin to later see what to do.
verdugon said:
Thanks @SnowFuhrer for your reply.
To answer your question yes its SMSUNG. I didn't know about that Thx.
The cable is brand knew but i noticed now that the phone is usable that is claims its on slow charge...may be my PC is quite old now....
Like i said i will try to unlock bootloader and make it accesible to odin to later see what to do.
Click to expand...
Click to collapse
And to unlock the bootloader, just enable OEM unlock in the dev settings and it's ready to flash twrp. I remember when I got my Samsung and I was trying to fastboot unlock it lol.
Thanks to both of you! I will keep the thread on just in case...anyway may be it helps someone else.
verdugon said:
Thanks PMFRTT!! I finally disabled FRP-lock and phone is usable again. I now will try to unlock OEM bootloader and enable USB debugging to see what happens. Thanks
Click to expand...
Click to collapse
Good luck! Let me know how it went.
Hello everyone, I have rooted and used my MI 9 SE for at atbout one month normally. Today, phone discharged and since that time after charged, Iam not able to boot everywhere, except "fastboot screen", while trying anything like (power and +; power and - etc..) phone always vibrates and boots into fastboot screen.
unfortunatelly, I so far I havent managed to connect it to PC and reflash anything, it is not visible and does nothing, when try to connect to PC (tried all USB ports etc).
Also MI flash tool doesnt do anything with that, so, any idea or solution?
Thank you, sorry for my english.
MTAVALI said:
Hello everyone, I have rooted and used my MI 9 SE for at atbout one month normally. Today, phone discharged and since that time after charged, Iam not able to boot everywhere, except "fastboot screen", while trying anything like (power and +; power and - etc..) phone always vibrates and boots into fastboot screen.
unfortunatelly, I so far I havent managed to connect it to PC and reflash anything, it is not visible and does nothing, when try to connect to PC (tried all USB ports etc).
Also MI flash tool doesnt do anything with that, so, any idea or solution?
Thank you, sorry for my english.
Click to expand...
Click to collapse
So you can boot into fastboot but somehow your PC still won't see the phone?
xXPhoenixXx said:
So you can boot into fastboot but somehow your PC still won't see the phone?
Click to expand...
Click to collapse
Yeap
MTAVALI said:
Yeap
Click to expand...
Click to collapse
Are you using USB 2.0 or USB 3.0?
Edit: there is this: https://www.xiaomitool.com/V2/
I used this to unlock my bootloader, though I've noticed that it has "unbrick" feature, whatever that may be, haven't tried it before, see if it helps. If you cannot get fastboot working, you're in deep sh*t.
I'm afraid I can't help beyond this, I never bricked a phone badly enough to ruin fastboot, so at this point I'm clueless what you can do other than returning the phone. They unbrick it for you and the warranty wont be void but you'll have to pay.
xXPhoenixXx said:
Are you using USB 2.0 or USB 3.0?
Edit: there is this: https://www.xiaomitool.com/V2/
I used this to unlock my bootloader, though I've noticed that it has "unbrick" feature, whatever that may be, haven't tried it before, see if it helps. If you cannot get fastboot working, you're in deep sh*t.
I'm afraid I can't help beyond this, I never bricked a phone badly enough to ruin fastboot, so at this point I'm clueless what you can do other than returning the phone. They unbrick it for you and the warranty wont be void but you'll have to pay.
Click to expand...
Click to collapse
OK will try.
Thank U
MTAVALI said:
Hello everyone, I have rooted and used my MI 9 SE for at atbout one month normally. Today, phone discharged and since that time after charged, Iam not able to boot everywhere, except "fastboot screen", while trying anything like (power and +; power and - etc..) phone always vibrates and boots into fastboot screen.
unfortunatelly, I so far I havent managed to connect it to PC and reflash anything, it is not visible and does nothing, when try to connect to PC (tried all USB ports etc).
Also MI flash tool doesnt do anything with that, so, any idea or solution?
Thank you, sorry for my english.
Click to expand...
Click to collapse
Have you tried to flash from fastboot with MiFlash?
Download here fastboot image and extract it, than Google for MiFlash ver. 2016.08.30 and just unbirck your phone...
sHAKaJaada said:
Have you tried to flash from fastboot with MiFlash?
Download here fastboot image and extract it, than Google for MiFlash ver. 2016.08.30 and just unbirck your phone...
Click to expand...
Click to collapse
Yes that looks working ..) Very thanks
After booting you have to reboot to bootloader and reflash twrp (if you need them) and if you want to flash some dev rom wipe: DALVIK, CACHE and DATA ONLY from WIPE menu, NOT System, than flash dev rom if you like ...
Sent from my Mi 9 SE using XDA Labs
So I wanted to try out the A12. I really like it, but the ROM makes it unenjoyable. Slow speeds, stutter, lag, delay in actions like: locking the screen, volume control.
I want to ask if I need to do something special to downgrade or I can just simply flash the device? (Wanting to flash Pixel Experience)
DanXdHun said:
So I wanted to try out the A12. I really like it, but the ROM makes it unenjoyable. Slow speeds, stutter, lag, delay in actions like: locking the screen, volume control.
I want to ask if I need to do something special to downgrade or I can just simply flash the device? (Wanting to flash Pixel Experience)
Click to expand...
Click to collapse
Just flash the latest stable release of your MIUI build thru fastboot with miflash and you are set.
Dont attempt to flash anything via TWRP or any other method, or you will brick your phone.
Also, "DO NOT LOCK YOUR BOOTLOADER".
=)
Thank you very much for your help!
I want to also ask why is my MiFlash "flashing" the phone in 0 or 1 second. I know that it does not flash the phone.
Can you help me solve this issue?
DanXdHun said:
Thank you very much for your help!
I want to also ask why is my MiFlash "flashing" the phone in 0 or 1 second. I know that it does not flash the phone.
Can you help me solve this issue?
Click to expand...
Click to collapse
Try the latest version of miflashtool, you can find it here
Xiaomi Flash Tool - Official Mi Flash Tool
Download the latest and Official Xiaomi Flash Tool from the Official Xiaomi Flash Tool Website.
xiaomiflashtool.com
The same issue still occurs.
DanXdHun said:
The same issue still occurs.
Click to expand...
Click to collapse
Some questions to understand the situation...
Is the usb debugging option enabled in the developer settings of the phone?
Are the phone drivers installed correctly on the pc?
Have you tried to restart the pc after installing miflash and drivers?
Have you tried to start miflash as administrator?
Usb Debugging is enabled
I didn't install any drivers, since I didn't see it was required
The PC has been restarted since, Yes.
I didn't try it yet.
DanXdHun said:
Usb Debugging is enabled
I didn't install any drivers, since I didn't see it was required
The PC has been restarted since, Yes.
I didn't try it yet.
Click to expand...
Click to collapse
Also try to change the USB port to which you connect the phone to the PC if 2.0 is better.
then you may have other useful information in this guide
How to flash ROM and TWRP on POCO F3 / k40 / mi11x. And an explanation. A very important guide
Mandatory instructions for beginners (and not only beginners) to install ROM and other on poco f3 Prerequisite, unlocking the bootloader For questions, if something is not clear, please write to "Conversations", I will try to correct it in a post...
forum.xda-developers.com
I am using USB 2.0 for everything.
I'll get back to you with the updates in about 30 minutes
DanXdHun said:
I am using USB 2.0 for everything.
I'll get back to you with the updates in about 30 minutes
Click to expand...
Click to collapse
Ok!
try this too. Thanks to @dreamytom for sharing it
Xiaomi Community
c.mi.com
RollDload said:
Ok!
try this too. Thanks to @dreamytom for sharing it
Xiaomi Community
c.mi.com
Click to expand...
Click to collapse
@RollDload
I have found out, that the same drivers are also included in Mi Flash, and that you just need to boot Windows with Driver Signature Enforcement disabled to be able to install all the drivers.
DanXdHun said:
Thank you very much for your help!
I want to also ask why is my MiFlash "flashing" the phone in 0 or 1 second. I know that it does not flash the phone.
Can you help me solve this issue?
Click to expand...
Click to collapse
Disconnect phone from PC and reboot Fastboot Mode, then re-connect to PC.
This is because, after an initiated Flash, Fastboot Mode may not accept any more input.
Also make sure to not reboot Fastboot Mode while phone is already connected to PC. You need to connect after you rebooted Fastboot.
This sounds weird, but you can also try using a different PC. Mi Flash is stubborn.
You can also try putting the ROM-folder directly to C:/.
Mi Flash doesn't like spaces in folder-names, and although you don't have any spaces I would still do it... Mi Flash's errors are unpredictable.
And yeah, like RollDload said, try using a different USB port
or try this: https://www.droidwin.com/unbrick-poco-f3/
this was te only way to get my F3 back.