I'm just curious as to whether anyone knows how 'thorough' an EDL flash with original Xiaomi fastboot firmware is. As in, is it bit-for-bit identical to a factory fresh unboxed phone? Or are there unique partitions which can become damaged - ones that EDL can't reflash?
I'm asking this since I had one of those 'softbrick' adventures in the wee hours.
Longer version; CM13 to AOSP caused the phone to go barmy but restoring an Official TWRP backup of CM13 didn't fix this, so I reset the device using the CN DEV MIUI8 fastboot files via EDL, pushed alka TWRP and tried again with my original CM13 alka backup from yonks ago after coming from MIUI7. Only to get something like 'E:extractTarFork() process ended with ERROR=255' with the firmware partition. I'm guessing this is essentially since it's attempting a MM to LP downgrade. Anyway, I reflashed via EDL, went straight to a Nougat ROM but left wondering if there's any damage done from those bootloops, CM firmware zips and failed restore pushes even after an EDL reflash. No symptoms anyhow.
Related
well i updated my nexus 9 through OTA update to android 6.0 couple days ago, then i had some battery issue.
So then i tried to flash cm12.1
what i did was, i unlock my device flash TWRP 2.8.7.0, then i got this corrupted message upon rebooting my device.
i did some research(i should've done it before doing anything:silly, it seems like it's something about the force encryption?
i tried almost every guide on xda here, flash de-crypted boot, flash stock recover, flash stock rom, adb sideload function is not working, nothing seems to work?
it seems like nothing can write onto my device as long as it's encrypted?
it works fine now, just wondering if there's a way i can properly de-crypt my device in this state and go back to 5.1.1 or CM12.1
Thanks
TWRP has just been update to 2871 and can now read encrypted partitions. Install this new TWRP.
Sent from my Nexus 9
Hello and first of all thank you for reading. I've a strange problem with my redmi note 3 pro.
i was chatting with it but suddenly it starts to have bootloops (mi logo flashes). I tried to restore it with recovery (it was still not unlocked) but nothing to do. So i flashed rom with the miflash and in edl mode (i tried latest stable, latest developer and first developer fastboot roms) but the bootloop was still here. So i tried to unlock bootloader with unoficial method (official says that my phone is linked to another account, absolutely false but i will come to this point later). Tried to flash zip with TWRP but still bootloops. I was tired and i tried cm13. It worked, phone boots and i was absolutely happy but dialer crashes when i receive calls. So i understand that my phone wants the boot.img of android 6.0 to not go into bootloop. I flashed (via TWRP) latest 6.0 based miui rom and it worked but still with dialer problem. I tried to unlock it but still no go. So i decided to try to sign out of my miaccount (yeah it was still there after flash with miflash in EDL mode, don't know why!) becasue it asked me to enter my password to use the phone when i boot miui 6.0 for the first time.
SO i Have absolutely no idea on what i should do. Phone bootloops when i use a 5.1 based rom, and with 6.0 dialer crashes. That's the strangest thing ever.
I tried many fastboot roms in edl and in fastboot, i tried custom recoveries and stock one, tried to unlock and relock bootloader. I tried basically everything (wipes, system-data-cache-internal) EVERYTHING!
please if you hava any idea i will be glad to try!
I've tried to restore a backup from another RN3P but still bootloop. Maybe is somethig related to the boot.img? changing it makes the phone boot.
Go to a Mi service center. They might be able to help you.
Which gapps you installed after you flashed cm13...
When i used stock package, my dialer was also crashing but when i used micro package, the problem was solved....
claudios91 said:
Hello and first of all thank you for reading. I've a strange problem with my redmi note 3 pro.
i was chatting with it but suddenly it starts to have bootloops (mi logo flashes). I tried to restore it with recovery (it was still not unlocked) but nothing to do. So i flashed rom with the miflash and in edl mode (i tried latest stable, latest developer and first developer fastboot roms) but the bootloop was still here. So i tried to unlock bootloader with unoficial method (official says that my phone is linked to another account, absolutely false but i will come to this point later). Tried to flash zip with TWRP but still bootloops. I was tired and i tried cm13. It worked, phone boots and i was absolutely happy but dialer crashes when i receive calls. So i understand that my phone wants the boot.img of android 6.0 to not go into bootloop. I flashed (via TWRP) latest 6.0 based miui rom and it worked but still with dialer problem. I tried to unlock it but still no go. So i decided to try to sign out of my miaccount (yeah it was still there after flash with miflash in EDL mode, don't know why!) becasue it asked me to enter my password to use the phone when i boot miui 6.0 for the first time.
SO i Have absolutely no idea on what i should do. Phone bootloops when i use a 5.1 based rom, and with 6.0 dialer crashes. That's the strangest thing ever.
I tried many fastboot roms in edl and in fastboot, i tried custom recoveries and stock one, tried to unlock and relock bootloader. I tried basically everything (wipes, system-data-cache-internal) EVERYTHING!
please if you hava any idea i will be glad to try!
Click to expand...
Click to collapse
I had a similar issue a while ago with a friend's Samsung. The service center people said that it was a RAM issue..
. If you can return the phone to wherever you bought it from, Do it ASAP and get another model...
Otherwise you might have to go to a service center and tell them exactly what you are facing. Before that i must suggest
Try installing a custom Kernel perhaps and see if it still bootloops
For every worst case software/firmware failure, full rom flash would be the one to solve it. Based on your story, it must be the hardware problem. So if possible, bring it to your nearest service center..
i really thank you for the reply but this phone comes from china and i'm in Italy so I have no warranty at all (including the fact i changed the screen) I think i will use it as an ipod. I've posted a log of the kernel bootloop so maybe someone with skills could help me!
that's the log! http://pastebin.com/b3CVcBAT
Hey all!
I just got my Note 3 (Snapdragon/Kenzo) from DX and it came with global US rom. I checked and its bootloader is already unlocked. I want to update to Miui 8 global dev but I'm worried with this unlock, is there a way to know if it was officialy or unnoficialy unlocked? I want to flash the oficial recovery rom but heard that it can brick the phone if it was unnoficialy unlocked.
link: http://www.dx.com/p/432294
It came with Miui 7.3 Stable (7.3.2.0.0 LHOCNDD)
Please, help. =)
Hazihell said:
It came with Miui 7.3 Stable (7.3.2.0.0 LHOCNDD)
Click to expand...
Click to collapse
That is a vendor rom.
More than likely it is unofficially unlocked, because your only allow to unlock 1 device per month for each account.
Since your bootloader is unlocked, flash an official rom (which might lock the bootloader again).
Don't flash the latest 6.0.1 rom yet as you might not be able unlock with that.
Then unlock officially.
Check the reddit xiaomi wiki for guides.
Got it! Thanks, for your answer. I realy dont mind unlocking, I just want a miui 8 dev(it has a built in root, right?). I just was afraid of what method of flashing I should use with this unnoficialy unlocked bootloader. I'm going to search this wiki for it.
And better do a Alka TWRP backup now, before anything! Then, if you get your bootloader locked, you can always restore the backup to your current status - ROM and unlocked bootloader. I have two Kenzos in the same situation, and that's the way I do it.
Nice! Will do. Can't I just use that recovery to install an updated rom? There is an annoying bug on this version, I can't open my contact or dialer app, they close befero they appear on screen, tried erasing data but no help.
Boot from TWRP without installing it, make the backup (all partitions), then make sure you get the backup on your PC. After that you can install TWRP and make whatever you wish.
And don't forget, if you need to restore, do it without restoring the firmware partition, or else you'll get an error.
Thansk! But I think I will stick with the global dev. Can I flash it via Fastboot (MiFlash)? This unnoficial unlock wont cause any trouble, right ?
This is not an unofficial unlock. Is isn't either official
My phones came with some vendor MIUI's - 7.4.9.0(LHOCNDD), respectively 7.4.18.0(LHOMIDD), but I never flashed another MIUI, just custom ROMs. For what I know, if you flash via fastboot it will wipe the entire partition structure, including boot and recovery, and the bootloader will get locked. In that case you can not restore the backup you make now. You'll have to apply for official unlocking, or go unofficial.
Hazihell said:
Hey all!
I just got my Note 3 (Snapdragon/Kenzo) from DX and it came with global US rom. I checked and its bootloader is already unlocked. I want to update to Miui 8 global dev but I'm worried with this unlock, is there a way to know if it was officialy or unnoficialy unlocked? I want to flash the oficial recovery rom but heard that it can brick the phone if it was unnoficialy unlocked.
link: http://www.dx.com/p/432294
It came with Miui 7.3 Stable (7.3.2.0.0 LHOCNDD)
Please, help. =)
Click to expand...
Click to collapse
that means.. you recieved an unboxed device, may be refurbished, repacked and resealed and sold $25 costlier than the original. :silly:
Not necessarily. I have two, buyed from a local big online store, both came with unlocked bootloader. Both boxes were sealed, with no sign of foreign hands
I have 7.3.2.0.0 LHOCNDD rom and unlocked bootloader. Can I just type on fastboot:
fastboot flash recovery recoveryAlkaUpdate.img
to get twrp(alka)?
Thats work!
paul_damian said:
This is not an unofficial unlock. Is isn't either official
My phones came with some vendor MIUI's - 7.4.9.0(LHOCNDD), respectively 7.4.18.0(LHOMIDD), but I never flashed another MIUI, just custom ROMs. For what I know, if you flash via fastboot it will wipe the entire partition structure, including boot and recovery, and the bootloader will get locked. In that case you can not restore the backup you make now. You'll have to apply for official unlocking, or go unofficial.
Click to expand...
Click to collapse
I have the same MIUI vendor as you, 7.4.9.0(LHOCNDD), what method did you use to install TWRP? I only want to install AOSP/CM based ROM on this device. I want to flash it ASAP cause this MIUI ROM have a Trojan downloader, which luckily can be disabled.
I used Cofface on first phone, Alka on the second. Before flashing, first boot from TWRP image, make backup of all partitions to the SD card, copy the backup on computer, and only after that flash the TWRP image. After that... flash ROMs
paul_damian said:
I used Cofface on first phone, Alka on the second. Before flashing, first boot from TWRP image, make backup of all partitions to the SD card, copy the backup on computer, and only after that flash the TWRP image. After that... flash ROMs
Click to expand...
Click to collapse
I followed a tutorial that uses ZXC TWRP while on MIUI. Then I flashed ALKA, I'm on Nexus Experience now.
Hi
First a little history...
I recently got an OPX with the intention of installing Sailfish OS on it. So first I need to get CM 12.1 installed. Following the instructions here I flashed TWRP using fastboot, but the version of TWRP provided at the link would not find any system partitions on my device and therefore could not be used to flash any images. Newer versions of TWRP would simply not load.
Eventually, using the stock OPX recovery, I managed to upgrade Oxygen OS to the latest version. I then flashed the latest version of TWRP (3.1.1-1) again and it worked! It found my devices partitions and I could flash ROMs with it. But, it wouldn't flash CM 12.1. Something about a trustzone incompatibility...
So I got the idea to try and downgrade Oxygen OS, which I did via TWRP. But then TWRP stopped working... and here is my problem.
I'm now stuck in a situation where:
- I can access fastboot
- The only versions of TWRP which work (e.g. 3.0.2-0) fail to find my system partitions, and therefore can't be used to flash ROMs
- The stock recovery also seems to fail to find the system partitions (clicking on "install locally" does nothing), so I can't use that to flash ROMs either
So I really need to get a working image on my phone somehow... but how?? Is it possible to do this via fastboot only?
Cheers!
Is your bootloader unlocked? TWRP cannot see system partitions if so.
I unlocked it originally... but since then I have installed a new ROM (Oxygen OS 2.x). Would this overwrite the bootloader? Do I need to unlock again? I think I must be using the old OOS bootloader now...
I think you can see if it's unlocked if you boot into bootloader, connect to pc and write on cmd "fastboot devices".
Whenever you switch between android 5.0 roms and 6.0 and further you have to first use the correct recovery from oneplus, only then you can flash the correct twrp and the adequate roms
My bootloader is unlocked. I cannot flash a new ROM via recovery, because none of the recovery images (stock, TWRP) can see my system partitions (I don't know why). At this stage I would just like to know if there is a way to flash a stock ROM/recovery/bootloader via some other method (fastboot, or a special tool), so I can restore my phone back to factory state. I don't care about losing data. Thanks.
EDIT: Just to clarify, I believe this is my current situation (please correct me if something doesn't make sense):
- OOS has two different bootloaders, 2.x and 3.x.
- The phone originally had OOS 2.x on it. None of the TWRP images I installed recognized my system partitions, so I couldn't flash with TWRP.
- After re-installing the stock recovery (which happened automatically when I booted to the stock ROM), I was able to upgrade to OOS 3.x via stock recovery. Now recent TWRP versions were working (I assume because upgrading to OOS 3.x updated the bootloader too), and were recognizing my system partitions.
- Using a new version of TWRP (3.1.1-1), I re-flashed an older version of OOS 2.x again. I think this was my mistake, because I think this downgraded the bootloader to 2.x again. Now none of the TWRP versions recognize my system partitions, so I cannot flash ROMs.
- I have re-flashed the stock recovery from the OnePlus website, but not even this allows me to flash ROMs. The symptoms look like in TWRP, i.e. that it fails to recognize my system partitions. So I am stuck with no way to flash ROMs, or upgrade the bootloader.
Well great. Device soft bricked. Bootloops endlessly. Can get into fastboot but the moto recovery tool thinks it’s fine and will not do a recovery. I was trying to downgrade from stock a11 to 10 but obviously failed Thinking the recovery tool would bring back to stock. I even put the imie number in and the software still thinks I have the latest firmware but I can’t force it to recover anyway. Help please
Got it back by downloading the latest stock a11 firmware and manually flashing in fastboot so I’m back to stock. Question is can I install any custom rom at all?