I need help installing Lineage Recovery and LOS on my Redmi Note 9 Pro Global version
I managed to unlock the bootloader but Lineage Recovery is messing with me. Once I flash it, I enter it, but can't seem to install LOS because it shows an error when I try to flash it.
Something in the lines of "adb: failed to read command: No status", or something like that. Also bricked the phone but managed to unbrick it.
On the official website it says in the instructions for the device:
Warning: Before following these instructions please ensure that the device is on the latest Android 11 firmware.
This is not necessarily the newest available version! Please up- or downgrade to the required version before proceeding (guides can be found on the internet!).
I thought I just needed to update my device with it's miui updater, but it seems I need to find this specific firmware version and flash it myself.
So if I got this right I first need to flash the firmware, then the recovery and then it should be able to install LOS?
Any idea where I can find this firmware cause there are a lot of files on the xiaomi official pages, not sure which to pick. Also, any good guides on how to flash firmware via adb?
UPDATE: Solved issue - Ignored the "error" and just rebooted to system after installation of LOS, no need for firmware. Just updated MIUI beforehand to newest version. Cheers!
Related
Dear fellas,
I have a problem updating to the new Global ROM Version: V8.0.1.0.MBGMIDG (MIUI8) [Global]
I currently have on my device Version: V8.0.10.0.MBGCNDI (MIUI8) [Chinese - Stable]
When I try to use the updater app, it gives a message: "Can't verify update - Couldn't verify update package"
I looked around in Mi forums, there were tutorials to flash my device using fastboot and adb, I tried following instructions but things didn't work out as they explained. (those tutorials are for other devices).
I also tried using the Mi PC Suite app, but my device isn't recognized by this software. I tried uninstalling drivers through device manager (it was under portable devices), and then connecting to the Mi PC Suite after resetting my device, it stopped at 10% and gave a message that I should update my device for the app to detect it!
Can anybody help me updating my device? I am a noob, and I am afraid to brick my device.
Have you unlocked your bootloader?
Is it a must?
It is !
I think you should go back to MIUI forum then go to the post where you can find the Global rom and follow the post #91.
Sorry I can't post link.
need special cable
To flash rom via xiaomimiflash.
I've just done that, it worked flawlessly(mi5s plus)
Or, if u'r already on custom rom, just unlock bootloader before flashing new rom.
Tell me if u need more info.
My phone is Chinese variant running miui 11 Android 9 and i installed the anti brick from the mega thread. Now i have an Android 10 update and i downloaded the update for 3 times but Everytime it says update.zip is corrupted during update process. I also tried with choose update package to update manually but same results. How can i overcome this problem?
This thread?
Not sure, since it's pretty long ago that i used to flash custom recovery's and roms, but if you have TWRP as your recovery i don think you're able to flash official firmware. Also read something in that thread about Android 10 and Anti Brick not going along very well. My best guess is; get rid of TWRP and Anti Brick by flashing the correct official firmware for your device via Fastboot.
Try and find a very very VERY clear howto. Lots of reading and caution = not bricking your device.
Hi there fellow Moto G5 users. I've been fiddling some time now with the 14.1 version and I want to try out the new 17 version with nightly's. Normally I've have no problems with upgrading or downgrading rom's for my devices, but since newer versions are now 64-bit it's throwing me off.
Since there are so many topics around with tips and procedures I'm a bit confused how to get started to migrate/change to LineageOS 17.
So could anybody help me on how to upgrade to LineageOS 17? As far as I know my phone has: a unlocked bootloader, TWRP with 64-bit support and LineageOS 14.1. What would the first step for me do?
As far as I understand it would be something like this:
(0. Backup up everything + written down both imei's) - done this in advance
1. Lock the bootloader again (whilst LineageOS 14.1 is still installed?)
2. Erase everything (with commands)
3. Flash an official Moto G EU rom (with commands)
4. Update it using OTA to the latest supported version to get a 64-bit rom/kernel/bootloader installed
5. Unlock bootloader again
6. Flash custom recovery again
7. Flash LineageOS 17?
That is what I'm thinking for me to do, is it correct? Or do I miss some stuff?
Any help will be appreciated.
Never lock the bootloader once you have unlocked it - if anything goes wrong in the future you will never be able to fix it without specialist hardware or a motherboard replacement
There is no need to lock the bootloader to change roms
See my post below that is basically answering the same question for full instructions on how to upgrade
Basically update stock firmware to latest retail then format data with latest offical twrp, wipe system data cache & flash rom
[SOLVED] LineageOS stuck at first boot (moto G5 xt1676)
Hello everyone, I just got a Moto G5 (on a refurbishment store) that works perfectly fine with stock OS. My goal is to install lineageOS on it. I managed easily to : - unlock bootloader - install TWRP (3.5.2_9.0) or the lineageOS recovery -...
forum.xda-developers.com
Thanks for the warning, I will try your instructions and see what I can manage. Will post any updates.
I've just updated the rom to 8.1 official. Thanks for the help. @TheFixItMan
And now i'm on Lineage 18.1/Android 11 working great so far.
I am trying to flash firmware on to Huawei MediaPad M2-801L.
I have a number of issues:
Can't get into device to enable Developer Options, there is a firmware problem not allowing me to do this.
I don't have an unlocked bootloader
Using fastboot commands to flash device keeps giving me this error: FAILED (remote: 'Command not allowed'). (I have installed Android Studio, and I am doing the commands within the "platform_tools" folder, with the relevant files to flash the device with).
I have even tried to install twrp with no avail
I have researched the internet for hours yesterday, trying different methods to try and get my tablet back up and running again. Every method I tried, I seemed to bump into many errors along the way.
I can get into fastboot mode and download mode. I have tried using QFIL, however I don't have a RawProgram and Patch file.
Is there something I'm missing? Can anyone guide me in the right direction if possible?
Thanks in advance!
See my post:
m2-a01w, installed Chinese Firmware and can’t revert to global or European.
Hi, I, by mistake, installed a Chinese Firmware into my m2-a01w and now I can’t revert to a global or European version anymore. All Google services are now unavailable. EMUI update fails with a version mismatch error. EMUI Version is 3.1...
forum.xda-developers.com
This could help.
Hi everyone,
for a customer project we have created a custom build of LineageOS 18.1 for SM-P610 and I have an image that is complete with our signage software.
I used to be able to flash these devices following the official installation instructions from the LineageOS page https://web.archive.org/web/20211002124915/https://wiki.lineageos.org/devices/gta4xlwifi/install
Now this doesn't work anymore. On some devices, I can't even unlock the bootloader. This has been discussed elsewhere and I have tried all the tricks from manipulating the datetime to logging on with a google or even a samsung account.
But even on the devices where I could onlock OEM, I can't seem to install the LineageOS recovery. I always get the error message "Only official released binaries are allowed to be flashed (RECOVERY)". FAP LOCK is OFF and OEM LOCK is OFF(U).
It says in the LineageOS install instructions that I must have the latest official Android 11 firmware installed. Previously, I would simply OTA update to this firmware, but nowadays, OTA goes directly to Android 12. So I tried downloading the only available Android 11 firmware from sammobile and flashing it in Heimdall. But unfortunately, I still get the same error message.
Can anybody please tell me which version of the Samsung bootloader I need exactly to install this version of the LineageOS recovery: lineage-18.1-20220112-recovery-gta4xlwifi.img?
Bonus question: Does anybody still have this firmware version mirrored somewhere?
edit: I have downloaded a newer recovery from the internet archives: lineage-18.1-20220504-recovery-gta4xlwifi.img
Now a get a different error message: "Custom binary(RECOVERY) blocked due to remaining installment balance".
Can somebody tell me what this means?
Do you really need LineageOS recovery specifically? Perhaps you may have better luck with the TWRP Recovery and then flash the OS through that instead. It was successful on my Galaxy S4 Mini.
Pelii said:
Do you really need LineageOS recovery specifically? Perhaps you may have better luck with the TWRP Recovery and then flash the OS through that instead. It was successful on my Galaxy S4 Mini.
Click to expand...
Click to collapse
Tbh I don't know. So how would that work? I Install the TWRP recovery (how?) and then I proceed to install the LineageOS image?
Well, looking at TWRP's website and the forums here, there's actually no build for your model specifically, so it seems you're out of luck on that one.
I suppose what's left is to just keep trying different sources of LineageOS recovery, because neither of the errors you described so far look like anything you can fix from your end.
Update: I have found what seems to be the exact Samsung firmware that was the latest one at the time:
https://samfrew.com/de/download/Galaxy__Tab__S6__Lite__-Wi-Fi-__/0kd5/DBT/P610XXU2DUL9/P610OXM2DUL9/
I'm currently downloading.
Also, I have been able to bring one of the really old devices to exactly this firmware state by OTA by cycling through 3 consecutive incremental updates. I was pretty excited to bring it into download mode, only to see this strange error "Custom binary(RECOVERY) blocked due to remaining installment balance" yet again.