Keep stock recovery and extract the boot image.
You'll need.
Unlocked bootloader as guided here
adb/fastboot and proper drivers on PC.
TWRP from here. Any recent build will do, just grab the latest one.
Steps:
Reboot to fastboot
Code:
adb reboot bootloader
In fastboot, verify it's working properly and get the current slot. The result is either a or b
Code:
fastboot devices
Code:
fastboot getvar current-slot
Now boot into TWRP temporarily. The touchscreen will NOT work(a known issue). Just leave the phone connected
Code:
fastboot boot Twrp_3.5.2-10_EduardoA3677-billie_OxygenOs11_Android11.img
adb should work now. Extract boot image(s).
Code:
adb devices
Code:
adb pull /dev/block/bootdevice/by-name/boot_a boot_a.img
Code:
adb pull /dev/block/bootdevice/by-name/boot_b boot_b.img
Now we have boot_a.img and boot_b.img in current folder. Both should be 96MB or 100,663,296 bytes.
Depends on the result from step 2,
if it's "current-slot: a" then use boot_a.img. if it's "b" use "boot_b.img".
Once done, reboot the phone.
Code:
adb reboot
Now with this boot image, follow the guide to root.
Related
Hi
I was trying to install Lineage OS on my device, but I failed, now the phone does not have TWRP anymore, and when I power up, it goes into fast boot only.
I have done quite a lot of work to save my phone, and the last thing that I did was download the stock fastboot rom and run flash_all.bat from it.
(I can not get the Miflash tool working on my PC because when I startup the program, it asks me to download 5 drivers, but it failed to download and throw me an error)
luckyvictor said:
Hi
I was trying to install Lineage OS on my device, but I failed, now the phone does not have TWRP anymore, and when I power up, it goes into fast boot only.
I have done quite a lot of work to save my phone, and the last thing that I did was download the stock fastboot rom and run flash_all.bat from it.
(I can not get the Miflash tool working on my PC because when I startup the program, it asks me to download 5 drivers, but it failed to download and throw me an error)
Click to expand...
Click to collapse
First of all - if your phone boots to fastboot, there seems to be a problem with your bootloader or kernel.
To fix that, you need to reflash aboot.img and boot.img via fastboot.
Boot.img depends on the version, you want to install. Copy both files into your fastboot folder and
Code:
fastboot flash boot_a boot.img
Code:
fastboot flash boot_b boot.img
Code:
fastboot flash aboot_a aboot.img
Code:
fastboot flash aboot_b aboot.img
Now your phone shouldn´t stuck @ fastboot anymore.
Ok, to save your data, you could try to boot twrp:
Code:
fastboot boot twrp.img
If you´re lucky, it can decrypt your data - then you can backup data and internal storage...
If it´s not able to decrypt, you need to install twrp.
To install a fastboot rom without miflash look here
I suggest you to install caf-kernel via twrp. Sometimes your phone boots up with it - magic
Voodoojonny said:
First of all - if your phone boots to fastboot, there seems to be a problem with your bootloader or kernel.
To fix that, you need to reflash aboot.img and boot.img via fastboot.
Boot.img depends on the version, you want to install. Copy both files into your fastboot folder and
Code:
fastboot flash boot_a boot.img
Code:
fastboot flash boot_b boot.img
Code:
fastboot flash aboot_a aboot.img
Code:
fastboot flash aboot_b aboot.img
Now your phone shouldn´t stuck @ fastboot anymore.
Ok, to save your data, you could try to boot twrp:
Code:
fastboot boot twrp.img
If you´re lucky, it can decrypt your data - then you can backup data and internal storage...
If it´s not able to decrypt, you need to install twrp.
To install a fastboot rom without miflash look here
I suggest you to install caf-kernel via twrp. Sometimes your phone boots up with it - magic
Click to expand...
Click to collapse
Thanks, will give it a try.
Just for my knowledge, what are these boot_a and boot_b please? they relate to the two sim slot in this device?
luckyvictor said:
Thanks, will give it a try.
Just for my knowledge, what are these boot_a and boot_b please? they relate to the two sim slot in this device?
Click to expand...
Click to collapse
Boot.img from fastboot rom... To be flashed in partition boot_a and boot_b. Our device is a AB-device. That means all partitions are doubled (except of data). If your system breaks, you can switch to the other slot by "fastboot set_active a" or b if you are on a.... Btw perhaps that fixes your phone too! Boot twrp and you can see which slot is active (under reboot)
I did everything on https://wiki.lineageos.org/devices/ginkgo/install , I flashed the recovery, on the Prompt I get "okay" to both Sending and Writing, and on "Now reboot into recovery to verify the installation" my phone is still on fastboot, so I press for a long time the power button to (force?) shut down it, use volume_up+power and what I see is the "Redmi-Recovery 3.0" (stock recovery).
Is it possible to have 2 recovery and I simply don't know how to access the LOS one? Maybe I could have more luck installing TWRP and overwriting it with LOS recovery (how to?)?
From fastboot if I write "fastboot reboot recovery" right after "fastboot flash recovery ..." prompt says "Rebooting into recovery...okay" but then the normal OS is loaded.
If I use
Code:
adb reboot bootloader
I access to the stock fastboot, and from there
Code:
fastboot boot recoveryimagename.img
says
Code:
fastboot: error: cannot load 'lineage-17.1-20201228-recovery-ginkgo.img': No such file or directory
. If I use it from MIUI-OS:
Code:
< waiting for any device >
and Prompt is waiting there.
I have fastboot and recovery image in the same folder but with
Code:
fastboot flash recovery *recovery*
I get
Code:
fastboot: error: cannot load 'lineage-17.1-20201228-recovery-ginkgo.img': No such file or directory
, infact I used full path (full of the img file, not the adb/fastboot which I properly installed) instead of relative, giving the "okay", and after that with
Code:
fastboot boot lineage-17.1-20201228-recovery-ginkgo.img
I get
Code:
fastboot: error: cannot load 'lineage-17.1-20201228-recovery-ginkgo.img': No such file or directory
!
Only now I've seen I was writing from root Prompt and therefore from "C:\WINDOWS\system32>", I used "cd platform-tools_path" and (after
Code:
fastboot flash recovery lineage-17.1-20201228-recovery-ginkgo.img
)
Code:
fastboot boot lineage-17.1-20201228-recovery-ginkgo.img
worked, but now the phone is stuck here!! From prompt everything seems ok. The phone is stuck on the normal loading boot after that "fastboot boot..."! Before I even tried installing TWRP...maybe that was too much? Now?
I used again "fastboot boot lineage-17.1-20201228-recovery-ginkgo.img" and it seems to working...maybe in a couple of minutes(hours probably) I'll mark this as solved!
Ok, I think everything is good now, but I have a question: is it possible to have more than one recovery installed?
BEDBOI2 said:
is it possible to have more than one recovery installed?
Click to expand...
Click to collapse
it is possible on other devices, but until now not possible on ginkgo
I haven't touched my LG G7 in a while, so I decided to flash original boot_a/b to be able to OTA update. But when I boot into bootloader, fastboot can't do anything, command simply hangs until I interrupt it.
It is not just that the:
Code:
fastboot flash boot_a boot_v10p.img
fails, but not even:
Code:
fastboot flashing get_unlock_ability
works.
Fastboot recognize the device properly:
Code:
# fastboot devices
LMG710EMabd8a3d8 fastboot
Any thoughts?
1. Copy the boot.img and Magisk apk into the internal storage of my phone.
2. Install Magisk and patch boot.img then I get the file such as magisk_patched.img.(The file name is different, I changed it to magisk_patched.img.)
3. Copy the magisk_patched.img and past in the ADB folder.
4. In ADB floder open command prompt and phone connect to PC.
Type to enter fastboot mode.
5. Check current slot of the device ：fastboot getvar current-slot
It's will show a or b here but it's show
6. Type fastboot flash boot magisk_patched.img into terminal window.（type fastboot flash boot_a(b) magisk_patched.img but my phone can't.）
7. Reboot and phone will be root successful.
All done then my phone is repeated starts and now I only boot to fastboot mode, can't boot to recovery mode. ROOT FAILED
What are problems? How to do? Ty All
Rom is V12.5.8.0 RJEMIXM and Android 11
Is there any way we can root MT2111_11_F.11 because for me fastboot appears to be missing as when i try volume down and power it just keeps on restarting after a see the fastboot screen for 0.01secs.
I tried using adb reboot bootloader as well but didn't work.
You should use adb reboot fastboot instead. Note that this mode doesn't allow to unlock bootloader if it is locked. But if bootloader was unlocked earlier, you may use flash command to flash patched boot.img
Code:
fastboot flash boot boot.img
go to github magisk, get apk install it on your phone, download your Full OTA, extract it via payload.bin extractor and take out boot.img then patch boot.img using magisk and do fastboot flash boot magiskpatchedboot.img
Original boot.img for oos f11 to patch
penguinus said:
You should use adb reboot fastboot instead. Note that this mode doesn't allow to unlock bootloader if it is locked. But if bootloader was unlocked earlier, you may use flash command to flash patched boot.img
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
Button combination = Fastboot Logo flashes for a split second, Phone instantly restarts to system, no access to bootloader therefore impossible to use flash commands
adb from system > reboot to bootloader = exact same as above.
Not bootloader, but userspace fastboot (fastbootd) mode. The command is
Code:
adb reboot fastboot