Related
FOR LG-H815, bought in Germany.
a) Went through the effort and unlocked the bootloader through LG's official method.
b) Confirmed, several times, that the bootloader is indeed unlocked.(via 'fastboot getvar unlocked' and verifying that the response is "unlocked: yes")
c) Tried to swap the Stock Recovery Mode with TWRP, using 'fastboot flash recovery twrp-2.8.6.0-h815.img'. The process ends in 1 sec. After booting in recovery mode, I find out it doesn't actually flash it.
d) Inside cmd: adb reboot bootloader
fastboot boot twrp-2.8.6.0-h815.img
At this point I am trying to boot TWRP for a one-time job of rooting the device.
-Install>>Select UPDATE-SuperSU-v2.46.zip>>Swipe to Install>> Reboot System
e) After reboot: PERMANENTLY STUCK, will not boot past LG's Logo. It is still possible to enter the Stock Recovery Mode, and Stock Download Mode.
I have repeated the process twice, reflashing the stock ROM, to the same effect. Any help is greatly appreciated.
You're flashing outdated versions of TWRP and SU...
I helped with this problem about 100 times now but I will do it one more time...
Firstly, reflash the stock MM ROM again.. Then download the better looking TWRP 3.0.2-0 from official twrp site -> https://dl.twrp.me/h815/twrp-3.0.2-0-h815.img.html
Now a little explanation. As far as I know in 6.0.X Google changed their policy a bit and the option to root the phone/ flash recovery is locked even though you have unlocked bootloader, and as well system root doesn't work, so instead of old SuperSU 2.46 you want to download newest systemless root zip -> http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 . Now, since there is no stock modified boot.img for G4, you have to download and unpack the custom kernel like SimpleGX and take it's boot img that you want to flash via fastboot, or you can try flashing boot.img from the Autoprime's V20D flashable zips, I didn't try that one and I will not be able to because my G4 got a bootloop issue that I recovered it of by my self but I cannot boot it up on Marshmallow stock firmware. Anyway once you flashed the modified boot img you should be able to flash recovery and boot it up normally, then flash systemless root and if you used boot.img from custom kernel, flash the full package because you did not flash all the stuff from the package what may cause software problems in the long term I suppose. I think that's all you need to do to root it on MM.
Adam Myczkowski said:
I think that's all you need to do to root it on MM.
Click to expand...
Click to collapse
And you would be correct. Although I have to wonder why guides on XDA don't even mention flashing a custom kernel like SimpleGX_KERNEL_H81520X_v1.3.2.zip
Additional steps for installing ROOT/TWRP on LG G4:
Inside CMD:
C:\adb>adb reboot bootloader
error: device '(null)' not found
C:\adb>adb devices
List of devices attached
LGH81539bf5a8e device
C:\adb>adb reboot bootloader
C:\adb>fastboot boot twrp-3.0.2-0-h815.img
downloading 'boot.img'...
OKAY [ 0.956s]
booting...
OKAY [ 0.028s]
finished. total time: 1.000s
Inside TWRP: Install>>Select SimpleGX_KERNEL_H81520X_v1.3.2.zip>>Swipe to the right>>Reboot // .zip file is ~19MB
Inside CMD:
C:\adb>adb reboot bootloader
C:\adb>fastboot flash recovery twrp-3.0.2-0-h815.img //now attempting to overwrite the stock recovery
target reported max download size of 536870912 bytes
sending 'recovery' (31652 KB)...
OKAY [ 0.969s]
writing 'recovery'...
OKAY [ 0.378s]
finished. total time: 1.365s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.002s
C:\adb>adb devices
List of devices attached
LGH81539bf5a8e device
C:\adb>adb reboot recovery //to verify that TWRP has been installed.
Inside TWRP:
Install>>Select BETA-SuperSU-v2.71-20160331103524.zip>>Swipe to the right>> Reboot
DONE.
I'm not sure if it's right place to start this thread but the problem is that after clean install of lineageOS nightly build from 25th of January I have no recovery that's what ROM manager app says, phone doesn't show "SONY" logo while booting which means that I can't boot into recovery mode (and that's obvious because I think I don't have recovery) also phone is not rooted and works without gapps. Is there any option to fix it?
Lineage OS recovery
I installed Lineage OS for my Xperia M which was running on Cyanogenmod 14.1.
After installing the OS I pressed the recovery option after pressing power option, but the set do not boot to recovery by to Lineage OS only. I used TWRP recovery.
I tried to flash TWRP recovery via ADB, but the message is
C:\adb>fastboot flash recovery twrp.img
sending 'recovery' (11208 KB)...
OKAY [ 0.705s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.721s
Can some one help me.
I am new to this forum and a non - techie.
I have moto G2, Sony XperiaM and Nexus 6 all phones rooted. MotoG2 and Nexus 6 are running with resurrection remix.
Xperia M does not have a recovery partition like some other devices. See the "some info" section on this post
I don't know of a fix at the moment, but as a work around in the meantime you could:
flash an image containing a recovery to the boot partition
Code:
fastboot flash boot recovery.img
Then when booting the phone you'd have the recovery options
If you wanted to boot to android, you would need to reflash the boot partition with the boot.img file in the lineageOS zip
Thanks for the reply. Will post after trying this solution.
Sriwelcomesu said:
I installed Lineage OS for my Xperia M which was running on Cyanogenmod 14.1.
After installing the OS I pressed the recovery option after pressing power option, but the set do not boot to recovery by to Lineage OS only. I used TWRP recovery.
I tried to flash TWRP recovery via ADB, but the message is
C:\adb>fastboot flash recovery twrp.img
sending 'recovery' (11208 KB)...
OKAY [ 0.705s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.721s
Can some one help me.
I am new to this forum and a non - techie.
I have moto G2, Sony XperiaM and Nexus 6 all phones rooted. MotoG2 and Nexus 6 are running with resurrection remix.
Click to expand...
Click to collapse
I haven't tried to flash recovery via adb yet but thanks for information that it won't work
Edit:
You flashed twrp.img as far as I remember you should change file name to boot.img and then flash. I'll try it later hopefully phone will boot in recovery mode
I had the same problem on my girlfriend's Sony Xperia M.
Just download the latest Lineage OS nightly (I used 20170131) and extract boot.img from the zip. Then go into bootloader mode (settings -> developer options -> advanced reboot, long press of lock button -> reboot -> bootloader, you should now have the blue light on and the screen turned off), connect it to the PC and run
Code:
fastboot flash boot boot.img
TWRP should now work again
Motherjoker said:
I had the same problem on my girlfriend's Sony Xperia M.
Just download the latest Lineage OS nightly (I used 20170131) and extract boot.img from the zip. Then go into bootloader mode (settings -> developer options -> advanced reboot, long press of lock button -> reboot -> bootloader, you should now have the blue light on and the screen turned off), connect it to the PC and run
Code:
fastboot flash boot boot.img
TWRP should now work again
Click to expand...
Click to collapse
Thanks, you saved me a lot of time.
For anyone else who are in the same shoes:
Note that it is crucial to only connect the USB when it is already in fastboot mode, since if you have to unplug and replug it for driver detection/reinstall purposes, when you unplug it the device simply turns off or reboots to system.
If it is stuck <waiting for device> you might have to visit the device manager and update the fastboot device's driver.
Thanks everybody for your replies. This is how i solved the issue.
Got the phone to fastboot mode using key combination
connected to pc
Confirm device status by typing fastboot devices
Then flashed recovery by typing
Fastboot flash boot boot.img
Twrp was renamed as boot before flashing.
After completion used key combination to go to recovery and i was in twrp.this booting to twrp will take around 10 mins. Be patient.
The os will not be there. We need to flash os and gapps
Hi,
i want to install twrp-3.2.3-0-whyred.img recovery on my Xiaomi and later xiaomi.eu_multi_HMNote5Pro_V10.0.1.0.OEICNFH_v10-8.1.
But I always get some errors. I never had this with my mi max 2.
I am afraid to brick this Redmi Note 5. Please help me
Redmi Note 5 Global Version RED (dual camera)
Miui version: miui global 9.6 stable 9.6.4.0 (OEIMIFD)
model name: M1803E7SG
Bootloader Unlocked by http://en.miui.com/unlock/
USB Debugging Enabled
Using latest platform-tools
PS C:\Users\Marija\Desktop\platform-tools> fastboot devices
PS C:\Users\Marija\Desktop\platform-tools> adb reboot bootloader
* daemon not running; starting now at tcp:****
* daemon started successfully
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
PS C:\Users\Marija\Desktop\platform-tools> adb kill-server
PS C:\Users\Marija\Desktop\platform-tools> adb reboot bootloader
* daemon not running; starting now at tcp:****
* daemon started successfully
PS C:\Users\Marija\Desktop\platform-tools> fastboot devices
*Numbers* fastboot
PS C:\Users\Marija\Desktop\platform-tools> fastboot flash recovery C:\Users\Marija\Desktop\platform-tools\twrp.img
Sending 'recovery' (36324 KB) OKAY [ 0.859s]
Writing 'recovery' FAILED (remote: Anti-rollback check failed)
Finished. Total time: 0.906s
cassinni said:
Hi,
i want to install twrp-3.2.3-0-whyred.img recovery on my Xiaomi and later xiaomi.eu_multi_HMNote5Pro_V10.0.1.0.OEICNFH_v10-8.1.
But I always get some errors. I never had this with my mi max 2.
I am afraid to brick this Redmi Note 5. Please help me
Redmi Note 5 Global Version RED (dual camera)
Miui version: miui global 9.6 stable 9.6.4.0 (OEIMIFD)
model name: M1803E7SG
Bootloader Unlocked by http://en.miui.com/unlock/
USB Debugging Enabled
Using latest platform-tools
PS C:\Users\Marija\Desktop\platform-tools> fastboot devices
PS C:\Users\Marija\Desktop\platform-tools> adb reboot bootloader
* daemon not running; starting now at tcp:****
* daemon started successfully
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
PS C:\Users\Marija\Desktop\platform-tools> adb kill-server
PS C:\Users\Marija\Desktop\platform-tools> adb reboot bootloader
* daemon not running; starting now at tcp:****
* daemon started successfully
PS C:\Users\Marija\Desktop\platform-tools> fastboot devices
*Numbers* fastboot
PS C:\Users\Marija\Desktop\platform-tools> fastboot flash recovery C:\Users\Marija\Desktop\platform-tools\twrp.img
Sending 'recovery' (36324 KB) OKAY [ 0.859s]
Writing 'recovery' FAILED (remote: Anti-rollback check failed)
Finished. Total time: 0.906s
Click to expand...
Click to collapse
First, copy the twrp image onto internal storage. After you connect it in the fastboot mode, boot into twrp (fastboot boot twrp-3.2.3-0-whyred.img), then after you booted into twrp, flash the twrp image within twrp.
attitude12 said:
First, copy the twrp image onto internal storage. After you connect it in the fastboot mode, boot into twrp (fastboot boot twrp-3.2.3-0-whyred.img), then after you booted into twrp, flash the twrp image within twrp.
Click to expand...
Click to collapse
I copied the same twrp.img into internal storage that is in platforms-tools folder and fastboot devices is showing the phone number and i get this:
...\platform-tools> fastboot flash recovery C:\Users\Marija\Desktop\platform-tools\twrp.img
< waiting for any device >
Different attept: platform-tools> fastboot boot twrp.img
Downloading 'boot.img' FAILED (Write to device failed (Invalid argument))
Finished. Total time: 0.024s
cassinni said:
I copied the same twrp.img into internal storage that is in platforms-tools folder and fastboot devices is showing the phone number and i get this:
...\platform-tools> fastboot flash recovery C:\Users\Marija\Desktop\platform-tools\twrp.img
< waiting for any device >
Different attept: platform-tools> fastboot boot twrp.img
Downloading 'boot.img' FAILED (Write to device failed (Invalid argument))
Finished. Total time: 0.024s
Click to expand...
Click to collapse
Are you sure ur doing everything right?
Is usb debugging on?
Stock twrp is a hustle to install you need to unlock the fastboot using dummy.img and use lazy flasher...
Just use redwolf recovery find it and
Fastboot boot redwolf.img
Install redwolf.img as recovery
Reboot to recovery
Enable USB Debugging (security settings) and then try
fastboot boot twrp.img
Then once again flash twrp.img within twrp recovery
t0per666 said:
Stock twrp is a hustle to install you need to unlock the fastboot using dummy.img and use lazy flasher...
Just use redwolf recovery find it and
Fastboot boot redwolf.img
Install redwolf.img as recovery
Reboot to recovery
Click to expand...
Click to collapse
There is no redwolf for this modell
SunilSuni said:
Enable USB Debugging (security settings) and then try
fastboot boot twrp.img
Then once again flash twrp.img within twrp recovery
Click to expand...
Click to collapse
USB Debugging is enabled under developer mode
\platform-tools> fastboot flash recovery twrp.img
< waiting for any device >
cassinni said:
There is no redwolf for this modell
Click to expand...
Click to collapse
https://forum.xda-developers.com/re...t/recovery-red-wolf-recovery-project-t3766997
Next time use search function sir
Doesn't work even with redwolf. Adb is installed, twrp.img is in root storage of phone and in adb folder. usb debugging enabled, phone unlocked by xiaomi (during booting and in settings it says unlocked). tried usb 2 and 3.0 ports on pc. windows 10 x64.
PS C:\Users\marija\Desktop\platform-tools> adb reboot bootloader
PS C:\Users\marija\Desktop\platform-tools> fastboot flash recovery twrp.img
sending 'recovery' (37592 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: -0.000s
cassinni said:
Doesn't work even with redwolf. Adb is installed, twrp.img is in root storage of phone and in adb folder. usb debugging enabled, phone unlocked by xiaomi (during booting and in settings it says unlocked). tried usb 2 and 3.0 ports on pc. windows 10 x64.
PS C:\Users\marija\Desktop\platform-tools> adb reboot bootloader
PS C:\Users\marija\Desktop\platform-tools> fastboot flash recovery twrp.img
sending 'recovery' (37592 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: -0.000s
Click to expand...
Click to collapse
fastboot flash recovery commands will not work in antirollback enabled ROM
All you have to do is fastboot boot twrp.img
From twrp once again you have to flash twrp.img
Waiting for device means you haven't installed required Xiaomi drivers in your PC, install drivers and then try
There are two types of USB DEBUGGING in Xiaomi phones
USB DEBUGGING
USB DEBUGGING (Security settings)
You have to enable these two options
If you still face problem maybe you can try different PC/Laptop
SunilSuni said:
fastboot flash recovery commands will not work in antirollback enabled ROM
All you have to do is fastboot boot twrp.img
From twrp once again you have to flash twrp.img
Waiting for device means you haven't installed required Xiaomi drivers in your PC, install drivers and then try
There are two types of USB DEBUGGING in Xiaomi phones
USB DEBUGGING
USB DEBUGGING (Security settings)
You have to enable these two options
If you still face problem maybe you can try different PC/Laptop
Click to expand...
Click to collapse
Both USB Debugging are enabled. Also the right drivers are installed. I have done this several times for other Xiaomi
devices, but this Redmi Note 5 Global Version (Dual Cameras) Red is crazy.
Maybe this cannot work because this is not Global Rom. It is Global Version and there is no twrp that supports Version.
I want to install twrp so i can flash xiaomi.eu 10 on it. Everything is stock on the phone and it does not work.
Sometimes it finds the phone and says file size too large and wont flash, or it gets stuck while flashing for 30mins and nothing happens or i get this error i just posted. I dont want to downgrade firmware, i want to update from 9 to 10.
I tried now on the laptop and it shows the device but it will not work.
PS C:\adb> adb kill-server
PS C:\adb> adb start-server
* daemon not running; starting now at tcp:5027
* daemon started successfully
PS C:\adb> adb devices
List of devices attached
60dbr4g2 device
PS C:\adb> fastboot boot twrp.img
< waiting for any device >
SunilSuni said:
fastboot flash recovery commands will not work in antirollback enabled ROM
All you have to do is fastboot boot twrp.img
From twrp once again you have to flash twrp.img
Click to expand...
Click to collapse
The antirollback was the issue. Now I am in TWRP. Do i have to wipe something? Please give exact command lines and where I enter them.
I flash twrp successfully. Then i went to wipe Dalvik, Cache, Data, System, Vendor.
Then Installed xiaomi.eu_multi_HMNote5Pro_8.8.30_v10-8.1.zip. At the end of install it had an error
for Vendor. E2001 Failed to update vendor image. Updater process ended with error 7.
I rebooted and now everytime i reboot it takes me to Fastboot screen?
Please help
cassinni said:
I flash twrp successfully. Then i went to wipe Dalvik, Cache, Data, System, Vendor.
Then Installed xiaomi.eu_multi_HMNote5Pro_8.8.30_v10-8.1.zip. At the end of install it had an error
for Vendor. E2001 Failed to update vendor image. Updater process ended with error 7.
I rebooted and now everytime i reboot it takes me to Fastboot screen?
Please help
Click to expand...
Click to collapse
Once again fastboot boot twrp.img and flash twrp
You have to avoid erasing vendor partition just system data cache dalvik cache is enough
I was in fastboot and used in adb fastboot boot twrp.img, then i got to twrp.
Now I should reflash twrp-3.2.3-0-whyred.img as recovery or vendor image?
I did already as recovery and then wiped data, cache, delvik and system as you said
then installed xiaomi.eu rom but i got the same vendor error.
Hello.
The problem is arb4 in this version of miui
follow the order of operations marked here:
https://androidfilebox.com/tips/root-redmi-note-5/
just add between step 10 and step 11 the unlocking of the arb4 ; this is possible with "toolkit flasher" that you find there:
http://en.miui.com/forum.php?mod=viewthread&tid=3282063&extra=page=3&mobile=2 (4 flash unlock anti roll back)
everyone tells me something different
the phone is not on miui 10. it was on stock stable miui 9. the flashing of 10 failed. The bootloader is already unlocked by xiaomi.
I believe my problems come from wiping vendor before i tried to flash miui 10 in twrp. I wasnt trying to downgrade (roll back), so arb4 should be irrelevant.
cassinni said:
everyone tells me something different
Click to expand...
Click to collapse
do as you like.
I rooted yesterday my note 5 (same model) which also turns on 9.6.4.0.
Hi, I was on 11.0.11 and after flashing 11.0.12 from TWRP
miui_GINKGOGlobal_V11.0.12.0.PCOMIXM_912960e1fc_9.0.zip
I can't flash TWRP
twrp-3.4.0-1-ginkgo.img
in fastboot mode even though there isn't an error
Code:
fastboot flash recovery twrp-3.4.0-1-ginkgo.img
Sending 'recovery' (65536 KB) OKAY [ 1.564s]
Writing 'recovery' OKAY [ 0.277s]
Finished. Total time: 1.868s
if I try to boot into recovery TWRP isn't there, it's on stock recovery. My bootloader is unlocked if it isn't obvious.
If I do
fastboot reboot recovery
after flashing TWRP, it doesn't boot into TWRP but instead into normal phone mode, not recovery.
If I do
fastboot reboot recovery
after flashing TWRP and then keep pressing the recovery key combo (PWR+VOLUP) it doesn't boot any recovery, it just keeps rebooting
-
Hacker?pcs said:
Hi, I was on 11.0.11 and after flashing 11.0.12 from TWRP
miui_GINKGOGlobal_V11.0.12.0.PCOMIXM_912960e1fc_9.0.zip
I can't flash TWRP
twrp-3.4.0-1-ginkgo.img
in fastboot mode even though there isn't an error
Code:
fastboot flash recovery twrp-3.4.0-1-ginkgo.img
Sending 'recovery' (65536 KB) OKAY [ 1.564s]
Writing 'recovery' OKAY [ 0.277s]
Finished. Total time: 1.868s
if I try to boot into recovery TWRP isn't there, it's on stock recovery. My bootloader is unlocked if it isn't obvious.
If I do
fastboot reboot recovery
after flashing TWRP, it doesn't boot into TWRP but instead into normal phone mode, not recovery.
If I do
fastboot reboot recovery
after flashing TWRP and then keep pressing the recovery key combo (PWR+VOLUP) it doesn't boot any recovery, it just keeps rebooting
Click to expand...
Click to collapse
Download twrp fastboot mode.
Download TWRP-3.3.2B-0627-REDMI_NOTE8-10.0-CN-wzsx150-fastboot.zip - Redmi Note 8
Download TWRP TWRP-3.3.2B-0627-REDMI_NOTE8-10.0-CN-wzsx150-fastboot.zip - Redmi Note 8 - in MiFirm ✅ - Xiaomi MIUI Firmware - ROM - TWRP download free and max speed - The biggest Xiaomi Mi download
mifirm.net
J. Harry Potter said:
Download twrp fastboot mode.
Download TWRP-3.3.2B-0627-REDMI_NOTE8-10.0-CN-wzsx150-fastboot.zip - Redmi Note 8
Download TWRP TWRP-3.3.2B-0627-REDMI_NOTE8-10.0-CN-wzsx150-fastboot.zip - Redmi Note 8 - in MiFirm ✅ - Xiaomi MIUI Firmware - ROM - TWRP download free and max speed - The biggest Xiaomi Mi download
mifirm.net
Click to expand...
Click to collapse
Doesn't work,
fastboot boot recovery-TWRP-3.3.2B-0627-REDMI_NOTE8-10.0-CN-wzsx150.img
bring me to a different screen, the one that says "Redmi by Xiaomi" instead of the one with the little thing with the communist hat tinkering with Android but it's fastboot again, no TWRP.
Flashing it to recovery is the same as the official, rebooting to normal phone mode and if I do adb reboot recovery it gets me to stock recovery, not TWRP
Hacker?pcs said:
Doesn't work,
fastboot boot recovery-TWRP-3.3.2B-0627-REDMI_NOTE8-10.0-CN-wzsx150.img
bring me to a different screen, the one that says "Redmi by Xiaomi" instead of the one with the little thing with the communist hat tinkering with Android but it's fastboot again, no TWRP.
Flashing it to recovery is the same as the official, rebooting to normal phone mode and if I do adb reboot recovery it gets me to stock recovery, not TWRP
Click to expand...
Click to collapse
Then ig.......try after reseting your device or clean flash latest miui with mi flash tool.(your bootloader needs to be unlocked)
Hacker?pcs said:
Doesn't work,
fastboot boot recovery-TWRP-3.3.2B-0627-REDMI_NOTE8-10.0-CN-wzsx150.img
bring me to a different screen, the one that says "Redmi by Xiaomi" instead of the one with the little thing with the communist hat tinkering with Android but it's fastboot again, no TWRP.
Flashing it to recovery is the same as the official, rebooting to normal phone mode and if I do adb reboot recovery it gets me to stock recovery, not TWRP
Click to expand...
Click to collapse
By the way this is a different method. this should have worked. what did you do ?
J. Harry Potter said:
Then ig.......try after reseting your device or clean flash latest miui with mi flash tool.(your bootloader needs to be unlocked)
Click to expand...
Click to collapse
My bootloader is unlocked, I'm with Magisk since I bought the device, I usually to update download the recovery rom
Miui Updates
Redmi Note 8 Global Stable V11.0.12.0 OTA Apply for V11.0.11.0 https://bigota.d.miui.com/V11.0.12.0.PCOMIXM/miui-blockota-ginkgo_global-V11.0.11.0.PCOMIXM-V11.0.12.0.PCOMIXM-a0ac2f3c57-9.0.zip Recovery ROM...
t.me
and flash it then flash Magisk then TWRP to recovery, sometimes I forget though TWRP and then flash it from fastboot. I forgot it now but now it doesn't flash via fastboot for some reason
J. Harry Potter said:
By the way this is a different method. this should have worked. what did you do ?
Click to expand...
Click to collapse
As I've said, it acts like the official TWRP, it either reboots to fastboot or to normal phone mode.
Hacker?pcs said:
My bootloader is unlocked, I'm with Magisk since I bough the device, I usually to update download the recovery rom
Miui Updates
Redmi Note 8 Global Stable V11.0.12.0 OTA Apply for V11.0.11.0 https://bigota.d.miui.com/V11.0.12.0.PCOMIXM/miui-blockota-ginkgo_global-V11.0.11.0.PCOMIXM-V11.0.12.0.PCOMIXM-a0ac2f3c57-9.0.zip Recovery ROM...
t.me
and flash it then flash Magisk then TWRP to recovery, sometimes I forget though TWRP and then flash it from fastboot. I forgot it now but now it doesn't flash via fastboot for some reason
As I've said, it acts like the official TWRP, it either reboots to fastboot or to normal phone mode.
Click to expand...
Click to collapse
i don't know how you flashed that twrp. Just open EN_Recovery-twrp-oneclick-EN then press enter. and then boot your phone to fastboot mode and connect to pc. then in pc type 2 and then i hope it will work
J. Harry Potter said:
i don't know how you flashed that twrp. Just open EN_Recovery-twrp-oneclick-EN then press enter. and then boot your phone to fastboot mode and connect to pc. then in pc type 2 and then i hope it will work
Click to expand...
Click to collapse
I've flashed it with the fastboot I have from Android SDK, didn't run the script. I've checked it out and saw that it flashes the misc.bin file too, I've tried flashing it but now I'm stuck on fastboot... ffs
I've downloaded the official Fastboot rom
ginkgo_global_images_V11.0.12.0.PCOMIXM_20201119.0000.00_9.0_global_37804edbcb.tgz
but I can't flash its misc.bin, it says Volume full...
fastboot continue
says "system has been destroyed"
I really don't want to wipe data and start fresh with Mi Flash tool ffs
Hacker?pcs said:
I've flashed it with the fastboot I have from Android SDK, didn't run the script. I've checked it out and saw that it flashes the misc.bin file too, I've tried flashing it but now I'm stuck on fastboot... ffs
I've downloaded the official Fastboot rom
ginkgo_global_images_V11.0.12.0.PCOMIXM_20201119.0000.00_9.0_global_37804edbcb.tgz
but I can't flash its misc.bin, it says Volume full...
never heard of volume full problem. place the fastboot rom in desktop menu. and install necessary drivers that need to flash via mi flash tool
Click to expand...
Click to collapse
J. Harry Potter said:
never heard of volume full problem. place the fastboot rom in desktop menu. and install necessary drivers that need to flash via mi flash tool
Click to expand...
Click to collapse
Well the misc.bin from your link is 8KB, the misc.img from fastboot rom tgz is 8MB
It sucks because mi flash tool erases data...
EDIT
THANK GOD,
fastboot erase misc
fixes the destroyed problem and lets me boot.
I figured it out from the bat script in the tgz fastboot rom, it doesn't flash the contained 4MB misc.img, it just has "fastboot %* erase misc" near the end
Problem that I can't flash TWRP again so I can't root :/
Hacker?pcs said:
Well the misc.bin from your link is 8KB, the misc.img from fastboot rom tgz is 8MB
It sucks because mi flash tool erases data...
EDIT
THANK GOD,
fastboot erase misc
fixes the destroyed problem and lets me boot.
I figured it out from the bat script in the tgz fastboot rom, it doesn't flash it, it just has "fastboot %* erase misc" near the end
Problem that I can't flash TWRP again so I can't root :/
Click to expand...
Click to collapse
so now you can boot.
if you have a pc just store your data in pc and then flash miui. then ig it will clear all the bugs u r facing and then you can try to flash twrp
J. Harry Potter said:
so now you can boot.
if you have a pc just store your data in pc and then flash miui. then ig it will clear all the bugs u r facing and then you can try to flash twrp
Click to expand...
Click to collapse
Yeah seems to the only way, something blocks the custom TWRP recovery and a clean slate may be the only way
Hacker?pcs said:
Yeah seems to the only way, something blocks the custom TWRP recovery and a clean slate may be the only way
Click to expand...
Click to collapse
don't forget to flash VBMETA after so the custom recovery (twrp or orangefox) persist
I can't boot to recovery from fastboot:
fastboot flash recovery twrp-3.6.0_9-0-kuntao.img
fastboot boot twrp-3.6.0_9-0-kuntao.img
Booting with volume up and down and power doesn't work too.
Can someone help me with this ?
edit: booting from boot.img isn't working either. I'm stuck here.
fastboot flash boot boot.img
downloading 'boot.img'...
OKAY [ 0.351s]
booting...
OKAY [ 0.571s]
finished. total time: 0.934s
But it stays in fastboot and crashes.
I reflashed to stock with those commands:
Flash the boot image: fastboot flash boot boot.img
Flash the recovery image: fastboot flash recovery recovery.img
Flash the system chunks one after the other, starting with the first one until the last one. For example, to flash the first system chunk: fastboot flash system systemchunk1.img
fastboot reboot, no changes only lenovo Logo screen