Related
Dear XDA Community,
in past 2 months i've been using CM13, constantly having some trouble with apps involving the camera, such as the camera app(surprise) and e.g. snapchat.
So yesterday I decided to update my CM Build, not knowing it would be to CM14 and with this Android 7.
So resulting from this I experienced a lot of issues with different apps, especially the google ones and for example Instagram. I DID NOT Upgrade my twrp, which was pretty stupid as I found out.
So this morning I checked again for CM Updates and Updated to Version Nightly...25 I think... but because I did not update my TWRP it did absolutely nothing except bricking my phone.
I already followed through the Guide for Hard Bricked OP3s (both steps) "http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700"
Though it sadly did not work for me. The Recovery tool and all works but when I want to boot my Phone the md5checksum pops up after the OP3 Logo and it tells me that everythings fine except "boot: failed".
I tried the procedure of the Hard Brick fix over and over again but nothing seems to work. I am fairly new to this whole Custom Rom stuff so I have absolutely no clue what do to.
Does anyone have any idea that could help?
Best Regards
Aliasalex
Try fastboot flashing the whole rom.
how? i dont have a factory img.
i tried flashing CM14 again and OxygenOs OTA. Currently i am getting Cache, Boot and System Failed.
In the meanwhile I managed to get twrp installed, but trying to install OS or CM via twrp didnt work either
//edit: ran the msm download tool again. Now only Boot is failing. tried flashing a boot.img via fastboot but didnt work
//edit2: when flashing the boot.img via fastboot my phone boots and works. When restarting without PC it still has cache and boot failure in md5checksum
try the 1st method you mentioned in the OP but flash https://www.androidfilehost.com/?fid=24591020540821926 . from what I understand, you need to full write all your partitions since they seems corrupted.
aliasalex said:
how? i dont have a factory img.
i tried flashing CM14 again and OxygenOs OTA. Currently i am getting Cache, Boot and System Failed.
In the meanwhile I managed to get twrp installed, but trying to install OS or CM via twrp didnt work either
//edit: ran the msm download tool again. Now only Boot is failing. tried flashing a boot.img via fastboot but didnt work
//edit2: when flashing the boot.img via fastboot my phone boots and works. When restarting without PC it still has cache and boot failure in md5checksum
Click to expand...
Click to collapse
I'll help you when I'm home
Connect your phone to Fastboot. Go to device manager on Windows. Do you see something with OnePlus or kedacomm. I had this issue as well managed to solve it after 2 days.
Demian3112 said:
I'll help you when I'm home
Connect your phone to Fastboot. Go to device manager on Windows. Do you see something with OnePlus or kedacomm. I had this issue as well managed to solve it after 2 days.
Click to expand...
Click to collapse
Yes a Kedacom USB Device "Android ADB Interface" is listed.
aliasalex said:
Yes a Kedacom USB Device "Android ADB Interface" is listed.
Click to expand...
Click to collapse
I'm not home atm. But can you change it by any chance to Oneplus? Your almost there! Maybe the video can explain something, I don't have a pc close.
https://youtu.be/maLWScgXflk
Demian3112 said:
I'm not home atm. But can you change it by any chance to Oneplus? Your almost there! Maybe the video can explain something, I don't have a pc close.
https://youtu.be/maLWScgXflk
Click to expand...
Click to collapse
I installed the adb setup, still shows my OP3 as Kedacom -> android adb device..
my phone has been working for the past few days flawlessly, but it still doesnt boot on its own
aliasalex said:
I installed the adb setup, still shows my OP3 as Kedacom -> android adb device..
my phone has been working for the past few days flawlessly, but it still doesnt boot on its own
Click to expand...
Click to collapse
You can't access Fastboot because of that Kedacom driver, if you right click it you should be able to change the driver.
https://support.hidemyass.com/hc/en...ow-to-disable-Driver-Signing-check-on-Windows try to boot into this. Also try to install Oneplus drivers. It's in the unbrick post.
Demian3112 said:
You can't access Fastboot because of that Kedacom driver, if you right click it you should be able to change the driver.
https://support.hidemyass.com/hc/en...ow-to-disable-Driver-Signing-check-on-Windows try to boot into this. Also try to install Oneplus drivers. It's in the unbrick post.
Click to expand...
Click to collapse
But I can access fastboot!?
Also I disabled Driver Signing Check when first trying to unbrick my phone.
I installed the drivers given in the Unbrick Test, it showed something like Qualcomm [something] 9003. There was something in between.
aliasalex said:
But I can access fastboot!?
Also I disabled Driver Signing Check when first trying to unbrick my phone.
I installed the drivers given in the Unbrick Test, it showed something like Qualcomm [something] 9003. There was something in between.
Click to expand...
Click to collapse
Nice, whdn you boot you still get those errors in red letter something with "failed boot". Then manually flash the boot. Img provided in the folder where you ran the Unbrick tool from. Command for Fastboot "fastboot devices", then "fastboot flash boot boot.img". Make sure that Kedacom is not in device manager when you are accessing Fastboot.
i tried installing the lastest ota update while i had twrp installed, i have tried everything to get out of this loop.
tried flashing the updated rom off the oneplus website and if gave me errors
just looked at my phone and now it wont turn on what so every getting really stressed please help
[SOLVED]
went back to stock recovery and side loaded the full 1.4 gb rom i will leave a link for tutorial that i used, i wanted to get back to complete stock and this was the one use
"https://forums.oneplus.net/threads/guide-how-to-unroot-your-oneplus-3-and-go-back-completely-to-stock.456232/"
When you have TWRP you have to install full zip, not simply the eval OTA zip
bob_cheeseman5 said:
i tried installing the lastest ota update while i had twrp installed, i have tried everything to get out of this loop.
tried flashing the updated rom off the oneplus website and if gave me errors
just looked at my phone and now it wont turn on what so every getting really stressed please help
Click to expand...
Click to collapse
Flash the stock recovery.
Get stock recovery from downloads.oneplus.net
I cant seem to flash the stock recovery. The device is not visible in adb devices or fastboot devices. im facing the same issue.
If you are using TWRP 3.0.4-0 - try a hard boot...hold down the power button for 20s...wait 20s, power it back on.
bob_cheeseman5 said:
i tried installing the lastest ota update while i had twrp installed, i have tried everything to get out of this loop.
tried flashing the updated rom off the oneplus website and if gave me errors
just looked at my phone and now it wont turn on what so every getting really stressed please help
Click to expand...
Click to collapse
easy solution. Boot into fastboot
download this tool.
https://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
if newest version isnt working, download an older version with older twrp
than unzip the tool and run the .bat file and install twrp.
Thats it
There are many posts on Nougat not working with official TWRP (based on 6.0 build). Try booting into stock recovery. performing a system settings reset, then booting into fastboot and run the adb command, <fastboot boot TWRP-3.0.2-1.28.img>. From there you can do virtually anything you need to do. I recommend at least using a modified version of TWRP (such as 1.28). This has been posted many times before, please try and do a search for the answers first, it will help tremendously. Thanks
recovery
i had the same problem on my rooted OP3 when i used TWRP 3.0.2-1 , it worked to flash the full 4.0.1 rom but failed for everything else, flashing latest verion of twrp fixed it for me
Got the same problem (unrooted phone + device state locked, cannot access recover, but can access fastboot) with an added "benefit", USB debugging mode was off before it all went crashing and burning.
How to access my phone via PC? (all the guides I've found assume I had USB debugging mode on before the phone got soft-bricked, but as a normal phone user who never installed anything custom, I've never figured it is A MUST BE ON function).
Or simpler question - what tool to use to turn on the USB debugging mode? (if that is at all possible?)
Aislandas said:
Got the same problem (unrooted phone + device state locked, cannot access recover, but can access fastboot) with an added "benefit", USB debugging mode was off before it all went crashing and burning.
How to access my phone via PC? (all the guides I've found assume I had USB debugging mode on before the phone got soft-bricked, but as a normal phone user who never installed anything custom, I've never figured it is A MUST BE ON function).
Or simpler question - what tool to use to turn on the USB debugging mode? (if that is at all possible?)
Click to expand...
Click to collapse
I have tried doing the installing of the newer twrp but cant find a newer version of it, i am on 3.0.2-1. i have the same problem as you that my USB debugging isnt on i dont think so when trying to use the op3 tool kit i can get it to pick up fast boot but nothing else.
have you found a solution to your problem yet?
bob_cheeseman5 said:
I have tried doing the installing of the newer twrp but cant find a newer version of it, i am on 3.0.2-1. i have the same problem as you that my USB debugging isnt on i dont think so when trying to use the op3 tool kit i can get it to pick up fast boot but nothing else.
have you found a solution to your problem yet?
Click to expand...
Click to collapse
Noted that you solved your issue, but this post is about the new version of TWRP. Version 3.0.3 is available on twrp.me and it works with Nougat.
bob_cheeseman5 said:
I have tried doing the installing of the newer twrp but cant find a newer version of it, i am on 3.0.2-1. i have the same problem as you that my USB debugging isnt on i dont think so when trying to use the op3 tool kit i can get it to pick up fast boot but nothing else.
have you found a solution to your problem yet?
Click to expand...
Click to collapse
Gave up trying and booked a session with OP technicians Will see how it goes in a week.
Hi guys,
i want to flash my MiPad 5 from chinese to global Rom.
I already installed the Bootloader Unlock Tool and waited one week.
Now the bootloader is unlocked and i downloaded "Xiaomi Pad 5 Global MIUI V12.5.4.0.RKXMIXM Update". There are two different Download Versions, one for Recovery and one for fastboot. Which one is correct and usable without root?
Now i'm Stuck in the Process of Downloading TWRP because I can't find a specific version for my MiPad 5. Is there anybody who can give me a step by step Guide what to do now?
Thank you
chrwo said:
Hi guys,
i want to flash my MiPad 5 from chinese to global Rom.
I already installed the Bootloader Unlock Tool and waited one week.
Now the bootloader is unlocked and i downloaded "Xiaomi Pad 5 Global MIUI V12.5.4.0.RKXMIXM Update". There are two different Download Versions, one for Recovery and one for fastboot. Which one is correct and usable without root?
Now i'm Stuck in the Process of Downloading TWRP because I can't find a specific version for my MiPad 5. Is there anybody who can give me a step by step Guide what to do now?
Thank you
Click to expand...
Click to collapse
Try fastboot method without bootloader lock
I bricked it....
Error occurred while flashing the Global ROM.
After that it went directly into fastboot. Can't turn it off right now.
At the moment i am trying to install twrp with help of minimal adb and fastboot. getting errors now...
Tried an Intel and a AMD Computer. Tried CN Rom and Global ROM. Endless flashing, no result. Green loading bar is completed, saying mismatching and flashing... Now its stuck in Fastboot Mode.
can anybody help?
chrwo said:
I bricked it....
Error occurred while flashing the Global ROM.
After that it went directly into fastboot. Can't turn it off right now.
At the moment i am trying to install twrp with help of minimal adb and fastboot. getting errors now...
Tried an Intel and a AMD Computer. Tried CN Rom and Global ROM. Endless flashing, no result. Green loading bar is completed, saying mismatching and flashing... Now its stuck in Fastboot Mode.
can anybody help?
Click to expand...
Click to collapse
Could maybe try this:
https://www.xiaomitool.com/V2/
Don't have any experience with it personally, but worth a try
TWRP is not required to flash the global ROM.
Just specify the unzipped global ROM as the working directory of MiFlash.
try flashing fastboot rom using miflash tool
finally could flash the global rom.
i am pretty sure it was about the ryzen gaming pc i used. now it worked out with my intel laptop....
strange problem
chrwo said:
I bricked it....
Error occurred while flashing the Global ROM.
After that it went directly into fastboot. Can't turn it off right now.
At the moment i am trying to install twrp with help of minimal adb and fastboot. getting errors now...
Tried an Intel and a AMD Computer. Tried CN Rom and Global ROM. Endless flashing, no result. Green loading bar is completed, saying mismatching and flashing... Now its stuck in Fastboot Mode.
can anybody help?
Click to expand...
Click to collapse
Mi Pad 5 didn't have recovery partition, since it use A/B structure. You must execute fastboot boot recovery.img and after that install recovery to RAMdisk.
chrwo said:
I bricked it....
Error occurred while flashing the Global ROM.
After that it went directly into fastboot. Can't turn it off right now.
At the moment i am trying to install twrp with help of minimal adb and fastboot. getting errors now...
Tried an Intel and a AMD Computer. Tried CN Rom and Global ROM. Endless flashing, no result. Green loading bar is completed, saying mismatching and flashing... Now its stuck in Fastboot Mode.
can anybody help?
Click to expand...
Click to collapse
Whered you even get twrp? Had an error while flashing from cn to global as well about sparse super failed. Then tried reflashing but i got the same error as you had and all i did was reboot the tablet in fastboot while it was still in fastboot and after that it flashed successfully even though it threw out am error flash is not done but the tablet rebooted hy itself and then booted up after a minute or two. Almost gave me a heart attack while i was at it
Edit: seems you flashed it successfully already thats good. Fastboot can be clunky on ryzen sometimes, i remeber back on mi a2 had to use a hub instead of directly connecting my phone to my ryzen pc for fastboot to work properly and not get stuck while flashing. But now i can connect directly after switching to a b450motherboard, was using a b350 before
I am trying to use the Mi Flash tool and when I open it, it tells me to install Drivers, but the screen just hangs there when I press Continue.
I also get an error saying a specific log folder is not present.
I also am trying to install global rom on china model. Please help!
chrwo said:
finally could flash the global rom.
i am pretty sure it was about the ryzen gaming pc i used. now it worked out with my intel laptop....
strange problem
Click to expand...
Click to collapse
It would be great if you can make a step-by-step guide on how to do this. Thank you.
puleen said:
I am trying to use the Mi Flash tool and when I open it, it tells me to install Drivers, but the screen just hangs there when I press Continue.
I also get an error saying a specific log folder is not present.
I also am trying to install global rom on china model. Please help!
Click to expand...
Click to collapse
prob just driver problems, i use ryzen and it works fine.
Don't know if I need to create a new thread. After the unlocking, I tried to change the region from RU to CN and got the same problem after a "successful" update as chrwo with "Mismatching image and device" error and fastboot mode. Then I tried to flash global version and the device error is gone but I still have the fastboot mode. Recovery from MiToolv2 doesn't help either, after successful recovery tablet still goes only to fastboot.
Got it working after flashing with miflash on the intel PC. I used a USB port on the motherboard this time.
So maybe there is really a problem with Ryzen.
Choochter said:
Could maybe try this:
https://www.xiaomitool.com/V2/
Don't have any experience with it personally, but worth a try
Click to expand...
Click to collapse
Not work for me.
But when I try with Miflash tool and anoter Rom (newest), it worked
Critical Hit said:
Got it working after flashing with miflash on the intel PC. I used a USB port on the motherboard this time.
So maybe there is really a problem with Ryzen.
Click to expand...
Click to collapse
I meer the same errỏr when I use Intel PC.
So, I dont think this a problem of Ryzen
i also brick the device using mi-flash sucking program. i finally using fastboot command flashing which copying from the stock rom "flash_all.bat" file.
So we can't lock the bootloader after installing the global rom?
good evening
I have been trying to return to stock miui from Pixel Experience since yesterday but get this error every time I try to flash the Firmware and do not know what I can do about it. I would be happy if somebody knew what this error is from and what might fix it.
Same problem. Don't try more things because you will brick your phone like mine.
Thanks for your reply. What did you do that bricked your Phonem? This way I know what to avoid. Thanks you in advance
As you are sure your device is a eea one, try with this last official stable firmware : Version: V13.0.7.0.SKHEUXM
You can find it here https://new.c.mi.com/global/miuidownload/detail/device/1900394
Fastboot version here at bottom : https://xiaomifirmwareupdater.com/miui/alioth/stable/V13.0.7.0.SKHEUXM/
Or https://bigota.d.miui.com/V13.0.7.0...EUXM_20220627.0000.00_12.0_eea_e461331a7d.tgz
Thanks you so much I will try that
and i did not mention this but I started this whole project of returning to miui because my poco was and still is in a bootloop and is only accessible over fastboot, not recovery and even though it sometimes gets to the system it almost instantly crashes and reboots
Still the Same Error unfortunatelly
nockcx said:
and i did not mention this but I started this whole project of returning to miui because my poco was and still is in a bootloop and is only accessible over fastboot, not recovery and even though it sometimes gets to the system it almost instantly crashes and reboots
Click to expand...
Click to collapse
Ok,
Do you have any idea what you did that may have caused this bootloop ?
Have you used any Qualcomm Tools or any soft in EDL mode ?
No, I did not do anything that would mess with the system to my knowledge . which is why i really do not know what to do. Can This Error occur because of a USB 3.0 used to flash? The Phone even tries to reboot when it is detected as a Fastboot device, maybe This has Something to do with it. Maybe it loses the Connection and therefore the flashing process stops. Are there possible ways to fix This?
Try with the latest android platform tools.
Put the content of platform tools archive in the fastboot folder and launch flash_all.bat don't use flash_all_lock
Still the Same Error . Can This be because of a Driver or a hardware issue?
i had similar issues but with the super partition when trying to flash from cmd.
flashing with miflash instead solved it.
It doesnt seem to make any difference to the error whether i flash it via cmd or miflash
nockcx said:
Still the Same Error . Can This be because of a Driver or a hardware issue?
Click to expand...
Click to collapse
Maybe : So as you can try with other PC, USB cable, USB connector, reinstall USB drivers...
I already tried with two Notebooks, I will try again tomorrow with another PC and installing USB drivers again. Thank you
You could try redownloading the MIUI ROM... you got it from xiaomifirmwareupdater.com right?
And yes ^^, try other PCs/laptops and other USB-cables.
Just please make sure
Unfortunately, Fastboot-Flashing is a gamble. It's not a solid protocol. It has zero protection against sudden USB-connection loss.
And manufacturers like Xiaomi go out of their way and block Qualcomm's EDL Mode, which is the only way to recover your phone in case Fastboot Mode stops working, because that Mode itself can also get damaged.
Fixed - first flash a miui recovery rom from twrp make sure the rom version lower than the latest one, now flash and boot miui , now just update from miui updater once you updated to the latest version , now try to flash the fastboot rom that you trying to flash, it should work.
I cant access a bootloader like TWRP because the phone still keeps rebooting after a couple of seconds in the bootloader so i cant really do much. I only have access to fastboot
nockcx said:
just flash a custom vbmeta and then install a custom recovery in to the boot partition like fastboot flash boot ....flash both the slots boot_a and boot_b the run fastboot reboot recovery do all this with latest platform tools
Click to expand...
Click to collapse
okay Im as far as I have never been with a very weird method, maybe somebody can explain. Because my poco always wants to reboot I found out a way to keep in in Fastboot mode. I repeatedly press the power and volume down button, This way it stays on for a lot longer, but it still is not enough to succeed at flashing the rom. It also lets me believe that my problem is not a software but probably a hardware problem, otherwise and cannot explain this suuuper weird behavior. what do you guys think? is there a possible fix you know?
Hi all,
I hope someone will be able to guide me as how to recover from this.
So today I tried flashing my POCO F3 with MIUI 14 (xiaomi.eu_multi_HMK40_POCOF3_V14.0.4.0.TKHCNXM_v14-13) from the stock version MIUI 12.
I first successfuly unlocked the bootloader using MiUnlock. I then unlocked the developer options , usb unbugging etc. again on the fresh phone.
I also had USB / ADB and fastloader drivers installed.
I downloaded xiaomi.eu_multi_HMK40_POCOF3_V14.0.4.0.TKHCNXM_v14-13 , phone was already in fastboot and connected to the computer so run 'windows fastboot first install with data format' as an administrator which opened the cmd , after agreeing it started flashing the first few files successfully but when it gets to " Sending 'cmnlib64_ab' (504 KB) " the process just stopped there and it has been like this for around 30 mins - no error ...simply stuck on this step .....
I am not sure on what to do now to avoid bricking my phone, should I leave it connected ? Disconnect it and try flashing it again ? Download an older version of Xiaomi.Eu ROM (e.g MIUI 13 ) ?
Leave it connected for about 1 hour or so until you get success or error confirmation. If failed just reboot to system. If system failed to show up then go to fastboot again and install xiaomi.eu a12 version.
This is exactly why I hate fastboot method and always install rom from twrp
Flash 14.0.5 via orangefox recovery.
I left it overnight and nothing happened . I disconnected the phone and it rebooted ok. I am kind of worried about trying again. Is the twrp method safer ?
Just discovered that I stupidly set the "USB debugging (Security settings) on but I forgot to turn on "USB debugging" which is a few lines above in settings. Could that be what has stopped the process?
Phone should flash fine even if debugging is off. I would recommend you to make sure that the cable doesnt even move an inch during the whole flashing process as that sometimes interrupts it especially if you have a loose port.
I just switched the usb port from the back of the pc (which I think are USB 3.0) to the front panel of the PC (I suspect USB 2.0 ) and tried flashing the MIUI 14 from yesterday again - It worked !!!!
*Deleted
Hi,
You could check out my post,
Fastboot not working in Windows 11 [Resolved]
Hello! I cant get my Windows 11 virtual machine to detect my Xiaomi 12 when its in Fastboot mode. Does any one happen to have any ideas to solve this? It shows up as 'Android' in device manager. I've also attempted to install a drivers manually...
forum.xda-developers.com
I hope it might help for the future
Hi...
Is it possible to flash a ROM that says "...V12.0.6....V12-10" for example, on a device that shipped with MIUI 11 Android 10, directly, without first updating the device to MIUI 12 normally?
Carl_OX said:
Hi...
Is it possible to flash a ROM that says "...V12.0.6....V12-10" for example, on a device that shipped with MIUI 11 Android 10, directly, without first updating the device to MIUI 12 normally?
Click to expand...
Click to collapse
you can do if you flash the fastboot version by mi flash tool, and your bootloader is unlocked.
mogamycool said:
you can do if you flash the fastboot version by mi flash tool, and your bootloader is unlocked.
Click to expand...
Click to collapse
Thanks... I really appreciate the early reply.
But can't I do this using the recovery method? And also must the android and miui versions of both the global stock rom and custom rom be the same?
Nevermind...thanks for your help
if you want to flash specific version of android, then you need unlocked bootloader and mi flash tool, otherwise make updater app do its job. and no need for the global stock rom and custom rom be the same. just put in your mind to backup your data .
mogamycool said:
if you want to flash specific version of android, then you need unlocked bootloader and mi flash tool, otherwise make updater app do its job. and no need for the global stock rom and custom rom be the same. just put in your mind to backup your data .
Click to expand...
Click to collapse
Thanks boss