Related
Hello guys, ive been generally lucky in the sense that i have had no issues...until now.
I have tried installing the most recent updates (7.0, and now 7.1.1) and i continue to get this error through cmd. It does not seem to want to flash anything, and i have gotten it to flash, root, and twrp, but it still acted funky. Today, trying to remedy the situation, i attempted to flash the new 7.1.1 update, and return to stock (to later return to power user) but it is still doing it.
It says Bootloader: has-slot (not found), and a couple other things. When i try to flash individual pieces, it does not retain it. when i try to flash the flashall.bat, it flashes but does not flash everything, it will say the stuff has transferred 0 and skips it as it looks like. I cannot get my bootloader off the october one, and i have looked everywhere i can to try to fix this.. please help, its driving me mad. I will be happy to provide any information needed.
Thanks Community! You rock!
Have you tried a different USB cable? A different computer? How about a different USB AND a different computer? I think this would be a good place to start.
Can i ask you why this would matter? My usb seems to work fine, and my computer had no issues before this... i can still perform different actions, and my phone is showing up as ADB and Fastboot.
If it's not pc or usb cable related you can try to flash latest factory image step by step via fastboot without your simcard
Well, you might want to post the complete output of your flashing attempt, but if the bootloader slot isn't found, that's usually a sign of a hardware problem. Hopefully I'm wrong, but until we see more from you, I simply don't have an answer for you.
Ive tried to fastboot everything individually, and it refuses to take. I tried the flashall, same thing. I used NRT and it partially worked, but has sorta the same error. I will be flashing again and providing screenshots right now. I was able to get into a rom, root, twrp but i still cannot update all of those core things (bootloader, radio, and such) Thank you guys for the help. Much needed.
Here is the attempt to just flash the bootloader, i have tried from a different location but this is directly in Platform-Tools of the SDK. As you can also see, it does register under fastboot...
Try to flash radio and bootloader via twrp
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
Did you try without simcard?
coremania said:
Try to flash radio and bootloader via twrp
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
Did you try without simcard?
Click to expand...
Click to collapse
yes i have, i only do it with the simcard removed. Now whats weird is it says my bootloader is on 72.01, but my cmd clearly tells me its not working correctly...
coremania said:
Try to flash radio and bootloader via twrp
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
Did you try without simcard?
Click to expand...
Click to collapse
I just tried what you suggest, and im not sure if it worked. It said everything wrote (on twrp) but it was very quickly done. I feel it did the same thing as CMD did.
You could try using the correct Fastboot command...
fastboot flash bootloader bootloader.img
The command is fastboot flash <partition> <image>
Your screenshot says only "fastboot flash image" but doesn't state the partition you're trying to load, hence "unknown partition".
And since we're on the subject, perhaps a repetition of the procedure I used to use before the full OTA days might be useful to you and other people.
Preparation.
- Take a TWRP backup and save it on your PC.
- Download factory image (https://developers.google.com/android/nexus/images#shamu) and unzip all files, including the zip within the zip. Rename the *.img files to the names below. Copy all of them to the same folder as your ADB/fastboot executables.
- Download the relevant TWRP and rename to twrp.img - also put in ADB/fastboot folder.
- Copy SuperSU to device (if root wanted).
- Set USB debugging in Developer options & attach to your PC.
- Open a CMD window, navigate to your ADB folder, and check connectivity with "adb devices". If it's ok, copy & paste each command below into the CMD window and run them - the only lengthy one is the system.img.
1. adb reboot bootloader
2. fastboot flash bootloader bootloader.img
3. fastboot reboot-bootloader
4. fastboot flash radio radio.img
5. fastboot reboot-bootloader
6. fastboot erase system
7. fastboot flash system system.img
8. fastboot erase boot
9. fastboot flash boot boot.img
10. fastboot erase cache
11. fastboot flash cache cache.img
12. fastboot reboot-bootloader
13. fastboot flash recovery twrp.img
14. From bootloader boot to TWRP and reflash superSu
dahawthorne said:
You could try using the correct Fastboot command...
fastboot flash bootloader bootloader.img
The command is fastboot flash <partition> <image>
Your screenshot says only "fastboot flash image" but doesn't state the partition you're trying to load, hence "unknown partition".
And since we're on the subject, perhaps a repetition of the procedure I used to use before the full OTA days might be useful to you and other people.
Preparation.
- Take a TWRP backup and save it on your PC.
- Download factory image (https://developers.google.com/android/nexus/images#shamu) and unzip all files, including the zip within the zip. Rename the *.img files to the names below. Copy all of them to the same folder as your ADB/fastboot executables.
- Download the relevant TWRP and rename to twrp.img - also put in ADB/fastboot folder.
- Copy SuperSU to device (if root wanted).
- Set USB debugging in Developer options & attach to your PC.
- Open a CMD window, navigate to your ADB folder, and check connectivity with "adb devices". If it's ok, copy & paste each command below into the CMD window and run them - the only lengthy one is the system.img.
1. adb reboot bootloader
2. fastboot flash bootloader bootloader.img
3. fastboot reboot-bootloader
4. fastboot flash radio radio.img
5. fastboot reboot-bootloader
6. fastboot erase system
7. fastboot flash system system.img
8. fastboot erase boot
9. fastboot flash boot boot.img
10. fastboot erase cache
11. fastboot flash cache cache.img
12. fastboot reboot-bootloader
13. fastboot flash recovery twrp.img
14. From bootloader boot to TWRP and reflash superSu
Click to expand...
Click to collapse
hahahaha well that could surely be the issue :silly:, but the one thing im wondering is why it wouldnt work through NRT, and i also "successfully" sideloaded the ota... Gonna try this now and hopefully it works! I shall report back when finished
dahawthorne said:
You could try using the correct Fastboot command...
fastboot flash bootloader bootloader.img
The command is fastboot flash <partition> <image>
Your screenshot says only "fastboot flash image" but doesn't state the partition you're trying to load, hence "unknown partition".
And since we're on the subject, perhaps a repetition of the procedure I used to use before the full OTA days might be useful to you and other people.
Preparation.
- Take a TWRP backup and save it on your PC.
- Download factory image (https://developers.google.com/android/nexus/images#shamu) and unzip all files, including the zip within the zip. Rename the *.img files to the names below. Copy all of them to the same folder as your ADB/fastboot executables.
- Download the relevant TWRP and rename to twrp.img - also put in ADB/fastboot folder.
- Copy SuperSU to device (if root wanted).
- Set USB debugging in Developer options & attach to your PC.
- Open a CMD window, navigate to your ADB folder, and check connectivity with "adb devices". If it's ok, copy & paste each command below into the CMD window and run them - the only lengthy one is the system.img.
1. adb reboot bootloader
2. fastboot flash bootloader bootloader.img
3. fastboot reboot-bootloader
4. fastboot flash radio radio.img
5. fastboot reboot-bootloader
6. fastboot erase system
7. fastboot flash system system.img
8. fastboot erase boot
9. fastboot flash boot boot.img
10. fastboot erase cache
11. fastboot flash cache cache.img
12. fastboot reboot-bootloader
13. fastboot flash recovery twrp.img
14. From bootloader boot to TWRP and reflash superSu
Click to expand...
Click to collapse
Unfortunately, it did not work. Now google app keeps crashing. Phone is extremely buggy.
Calko2882 said:
Unfortunately, it did not work. Now google app keeps crashing. Phone is extremely buggy.
Click to expand...
Click to collapse
Can you give a bit more detail? So the phone is crashing, but is it now on the version that you wanted to have (7.0, 7.1.1)? There is rarely such a thing as "too much information".
dahawthorne said:
Can you give a bit more detail? So the phone is crashing, but is it now on the version that you wanted to have (7.0, 7.1.1)? There is rarely such a thing as "too much information".
Click to expand...
Click to collapse
Ok, so what happens is that it says i am on 7.1.1 with i guess the related info, but it does not load in properly as you can see with the screenshots. I start up the initial setup, and i can get through most of it fine, but some areas *permissions* are all blotchy. like i can toggle them on to submit data but i cant see what it is exactly im agreeing to. Then i start the phone, Google App automatically crashes, along side system ui. When i updated them, it seemed to fix the problem. But the issue is, i am not receiving phone calls and texts until possibly days later, and when i send texts it says "sending" and proceeds to spam the hell outta whoever its going to (sends literally 30+ texts). When i call someone, my phones Do Not Disturb mode gets enabled, and then nicely cuts out my audio. I can turn this feature off when im in the call, but sometimes it will then glitch the phone app, and i cannot essentially "hangup". My phone also now dies at 9%, where it had not previously (when i was on other rom / older stock) This all started after i updated to the october patch, and i noticed in december that i didnt have the december patch / update. I went to install it, and the same exact thing occurred. Ive attempted a rescue ota, and a sideload ota, and now this stuff as well, but i fear the worst for my phone. Let me know if i need to add anything else
Strephon may be right in suggesting a hardware fault, but equally it may just be that your phone is now somehow corrupted. My only suggestion is that you nuke it - factory reset, TWRP, wipe everything again in TWRP, and then try installing from fresh using the 7.1.1 full (not OTA) image and the instructions I posted earlier. If it still doesn't work I'm out of ideas, but there are people with far greater experience here than I have, so don't give up. It's too nice a device to just write off.
Calko2882 said:
When i call someone, my phones Do Not Disturb mode gets enabled
Click to expand...
Click to collapse
That's a new feature of 7.1.1. So you won't have to listen to notifications while on the phone. It's disabled as soon as the phone call is over.
dahawthorne said:
Strephon may be right in suggesting a hardware fault...
Click to expand...
Click to collapse
I hope I'm wrong.
WARNING:
You need to backup your data before installing. I am not responsible for any damage or loss that might occur. Proceed at your own risk.
Tested with MIUI version 10.2.5.0 Global.
Bootloader must be unlocked (https://en.miui.com/unlock/)
1. Unpack Minimal ADB and Fastboot to C:\ drive of your PC
2. Rename patched boot to boot.img. Rename recovery file to recovery.img. Place boot.img, recovery.img, vbmeta.img in ADB folder.
3. Enable USB-debugging in developer options on your phone.
4. Connect phone with PC via USB. Reboot phone to fastboot mode (Volume-down + Power).
5. On your PC open command prompt and nagivate to ADB folder.
6. Enter the following commands:
Code:
fastboot flash boot boot.img
Code:
fastboot flash vbmeta vbmeta.img
Code:
fastboot flash recovery recovery.img
7. Reboot to recovery (Volume-Up + Power; release Power when phone turns on, keep holding Volume-Up until you see screen of TWRP). If TWRP asks for PIN, enter the PIN of your unlock screen.
8. Wipe Dalvik / ART cache, System, Data, Cache. Format Data > Yes
Do not wipe Internal Storage!
9. Unpack the downloaded GSI Rom and move it to your phone.
10. Flash the Rom (Install image).
11. Reboot to Recovery.
12. Move files Magisk, Permissiver, FM-Radio fix, GApps to your phone.
13. Flash Magisk (optional)
14. Flash Permissiver
15. Flash GApps (optional).
If you get 'insufficient space' error, first resize System partition.
16. Flash FM-Radio fix:
In TWRP, Mount System. Then flash fix.
17. Reboot system and enjoy.
-----------------------
Downloads:
Minimal ADB and Fastboot
https://forum.xda-developers.com/showthread.php?t=2317790
GSI Rom:
https://forum.xda-developers.com/pr...lopment/gsi-lineageos-17-0-gsi-archs-t4004673
You need to get a64_bvN version from folder lineage-17.x.
Patched boot img file:
http://www.mediafire.com/folder/zx0167qqaknc3/Redmi_7a_patched_boot
Check your MIUI version in System, so that you download the correct boot img file.
TWRP recovery
https://www.mediafire.com/file/irntn5ccdiguuuu/TWRP-20191023-3.3.1.0-pine.img/file
vbmeta file
http://www.mediafire.com/file/bgpn9b87b4t8yye/vbmeta.img/file
Magisk
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Permissiver
https://androidfilehost.com/?fid=6006931924117940902
GApps (choose 'ARM' & '10.0')
https://opengapps.org/
FM Radio fix:
https://androidfilehost.com/?fid=8889791610682885147
After installing Gsi
After installing Gsi, can I get the fast boot mode later
Ts40 said:
After installing Gsi, can I get the fast boot mode later
Click to expand...
Click to collapse
Yes, you can still get into fastboot mode.
TWRP recovery
https://www.mediafire.com/file/irntn5ccdiguuuu/TWRP-20191023-3.3.1.0-pine.img/file
- is this the recovery.img?
Hi! I'm on Lineage 17.1 March 2020.
If I want to try out Lineage 18 - do I have do go back to MIUI global first before flashing Lineage with fastboot?
Other question:
Actually the internal storage seems to be encrypted. It is shown if I attached it to my PC but only some cryptical filenames are there - no chance to load anything to the internal storage for flashing it with TWRP. Any chances to "decrypt" it or make it "visible"?
kra_ppo said:
Hi! I'm on Lineage 17.1 March 2020.
If I want to try out Lineage 18 - do I have do go back to MIUI global first before flashing Lineage with fastboot?
Other question:
Actually the internal storage seems to be encrypted. It is shown if I attached it to my PC but only some cryptical filenames are there - no chance to load anything to the internal storage for flashing it with TWRP. Any chances to "decrypt" it or make it "visible"?
Click to expand...
Click to collapse
i would recommend you to flash MIUI global first, because if somethings goes wrong you can't say whats the reason for the error.
and the encrypted folders can be deleted in twrp by format data -->yes
raijinlee said:
TWRP recovery
https://www.mediafire.com/file/irntn5ccdiguuuu/TWRP-20191023-3.3.1.0-pine.img/file
- is this the recovery.img?
Click to expand...
Click to collapse
thats the one i'm using and never had problems with this, so yes
after testing several Treble GSis, I finally found CherishOS. Most of them are not booting, or other issues (no mobile data, only calling, settings are crashing,....). Save your time and choose CherishOS.
How I flashed it:
1. clean flash zeus_eea_global_images_V13.0.10.0.SLBEUXM_20220129.0000.00_12.0_eea (that's the full fastboot rom)
2. extract boot.img, vendor.img, vbmeta.img from miui_ZEUSEEAGlobal_V13.0.10.0.SLBEUXM_8af10526e8_12.0 (that's the update zip)
3. after clean install: let it boot up and shut down
4. fastboot reboot fastboot (Everything in fastbootd !!!)
5. fastboot getvar current-slot (see which slot u are using. Ex: a , b)
6. fastboot --set-active=a (if u are using slot b, change a to b) to make sure u're flashing gsi on 1 slot
7. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
8. fastboot flash vendor vendor.img
8. fastboot erase system
9. fastboot flash system YOURsystem.img
10. fastboot -w (shows an error)
11.fastboot flash boot boot.img
12. fastboot reboot
I've skipped wiping data through Mi Recovery
After that, you can flash Magisk.
It passes safteynet.
Whats NOT working:
- auto brightness (I use Velis Autobrightness)
- vibration
- fingerprint and face recognition
- bluetooth call issues
But after all, it's a very good start for new device, if you don't want to stick with MIUI
a bit too many steps for me lol
More details pls
And the camera?
bhammler said:
after testing several Treble GSis, I finally found CherishOS. Most of them are not booting, or other issues (no mobile data, only calling, settings are crashing,....). Save your time and choose CherishOS.
How I flashed it:
1. clean flash zeus_eea_global_images_V13.0.10.0.SLBEUXM_20220129.0000.00_12.0_eea (that's the full fastboot rom)
2. extract boot.img, vendor.img, vbmeta.img from miui_ZEUSEEAGlobal_V13.0.10.0.SLBEUXM_8af10526e8_12.0 (that's the update zip)
3. after clean install: let it boot up and shut down
4. fastboot reboot fastboot (Everything in fastbootd !!!)
5. fastboot getvar current-slot (see which slot u are using. Ex: a , b)
6. fastboot --set-active=a (if u are using slot b, change a to b) to make sure u're flashing gsi on 1 slot
7. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
8. fastboot flash vendor vendor.img
8. fastboot erase system
9. fastboot flash system YOURsystem.img
10. fastboot -w (shows an error)
11.fastboot flash boot boot.img
12. fastboot reboot
I've skipped wiping data through Mi Recovery
After that, you can flash Magisk.
It passes safteynet.
Whats NOT working:
- auto brightness (I use Velis Autobrightness)
- vibration
- fingerprint and face recognition
- bluetooth call issues
But after all, it's a very good start for new device, if you don't want to stick with MIUI
Click to expand...
Click to collapse
My question - when custom recovery available and when custom rom available
Can you share some pictures of cherris os
What about battery drain,120fps work or not,video tutorials step by step need
bhammler said:
after testing several Treble GSis, I finally found CherishOS. Most of them are not booting, or other issues (no mobile data, only calling, settings are crashing,....). Save your time and choose CherishOS.
How I flashed it:
1. clean flash zeus_eea_global_images_V13.0.10.0.SLBEUXM_20220129.0000.00_12.0_eea (that's the full fastboot rom)
2. extract boot.img, vendor.img, vbmeta.img from miui_ZEUSEEAGlobal_V13.0.10.0.SLBEUXM_8af10526e8_12.0 (that's the update zip)
3. after clean install: let it boot up and shut down
4. fastboot reboot fastboot (Everything in fastbootd !!!)
5. fastboot getvar current-slot (see which slot u are using. Ex: a , b)
6. fastboot --set-active=a (if u are using slot b, change a to b) to make sure u're flashing gsi on 1 slot
7. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
8. fastboot flash vendor vendor.img
8. fastboot erase system
9. fastboot flash system YOURsystem.img
10. fastboot -w (shows an error)
11.fastboot flash boot boot.img
12. fastboot reboot
I've skipped wiping data through Mi Recovery
After that, you can flash Magisk.
It passes safteynet.
Whats NOT working:
- auto brightness (I use Velis Autobrightness)
- vibration
- fingerprint and face recognition
- bluetooth call issues
But after all, it's a very good start for new device, if you don't want to stick with MIUI
Click to expand...
Click to collapse
From where you get cherish os rom file
could you receive SMS on GSIs?
if yes, did you do any modifications?
we can't receive any SMS in any GSI on SD 8gen1 models here in China
sometimes it works when you put your SIM Card in Slot 2. But it's not only the SMS issue, sometimes it's impossible to make a call, because the other one can't here you.
It's not a daily driver
bhammler said:
sometimes it works when you put your SIM Card in Slot 2. But it's not only the SMS issue, sometimes it's impossible to make a call, because the other one can't here you.
It's not a daily driver
Click to expand...
Click to collapse
thank you for sharing.
it seems to be an ims problem, but it's weirld that we can't receive sms in 2g/3g network too.
I've tried everything but failed. now only to do is to wait until phh fix it
esta guia para instalar la gsi rom, tambien sirve para el xiaomi 12x?
Mod Edit: English Translation Below
This guide to install the gsi rom, also works for the xiaomi 12x?
Why suddenly thread died in half way ?
Hi all, did anyone manage to install a GSI? If yes, how and which GSI image used? Thanks.
Seem to be for CUPID not ZEUS.
NOSS8 said:
Seem to be for CUPID not ZEUS.
Click to expand...
Click to collapse
感觉可以刷
Mod translation via GT: Feels like it can be brushed
bhammler said:
after testing several Treble GSis, I finally found CherishOS. Most of them are not booting, or other issues (no mobile data, only calling, settings are crashing,....). Save your time and choose CherishOS.
How I flashed it:
1. clean flash zeus_eea_global_images_V13.0.10.0.SLBEUXM_20220129.0000.00_12.0_eea (that's the full fastboot rom)
2. extract boot.img, vendor.img, vbmeta.img from miui_ZEUSEEAGlobal_V13.0.10.0.SLBEUXM_8af10526e8_12.0 (that's the update zip)
3. after clean install: let it boot up and shut down
4. fastboot reboot fastboot (Everything in fastbootd !!!)
5. fastboot getvar current-slot (see which slot u are using. Ex: a , b)
6. fastboot --set-active=a (if u are using slot b, change a to b) to make sure u're flashing gsi on 1 slot
7. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
8. fastboot flash vendor vendor.img
8. fastboot erase system
9. fastboot flash system YOURsystem.img
10. fastboot -w (shows an error)
11.fastboot flash boot boot.img
12. fastboot reboot
I've skipped wiping data through Mi Recovery
After that, you can flash Magisk.
It passes safteynet.
Whats NOT working:
- auto brightness (I use Velis Autobrightness)
- vibration
- fingerprint and face recognition
- bluetooth call issues
But after all, it's a very good start for new device, if you don't want to stick with MIUI
Click to expand...
Click to collapse
I think this is long procedure and you shouldn't fastboot -w
The proper steps are:
1. starting from stock ROM, reboot to bootloader
2. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
where vbmeta.img is stock one that you can get it from stock ROM images folder
3. fastboot reboot fastboot
4. fastboot erase system
5. fastboot flash system gsi_image_file
6. fastboot reboot recovery
From the recovery choose wipe data , then restart to the system and you are fine.
Hi, I tried many GSI ROMs. But none of them works for me. They can't detect the SIM card and wifi doesn't work either. Can you help me?
Hi All,
The following has been done.
enable usb debugging > adb devices (shows my device)
disable driver signature verification in Windows 11 > install the driver to be able to unlock my bootloader and use the fastboot devices command.
adb shell > getprop ro.build.ab_update > false
adb reboot bootloader
fastboot devices (shows my device)
fastboot flash recovery filename (SHRP/TWRP/PBRP).img
fastboot reboot recovery
But still unable to boot into the customer recover img, it only boots into the stock rom after sometime.
or
fastboot boot (SHRP/TWRP/PBRP).zip > (FAILED (remote: image is not a boot image')
Any pointer as to why?
i had the same problem... but after a lot of search... the answers were here ---> https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4225163/
in particular where it tells that before flashing a recovery you need to flash the correct vbmeta
vbmeta for 13.0.2 is in the list if you follow the suggested link in the post i mentioned
then you can flash a recovery for the 13.0.2 ( i used the project arrow one )
Thanks for your reply tigrato.
I have followed the link below.
"You need to disable verification for vbmeta too. Here, you can find patched vbmeta with disabled verification: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218909/"
fastboot --disable-verity --disable-verification flash vbmeta vbmeta_vd171--V13.0.2.0.SJOMIXM.img
&
fastboot flash vbmeta vbmeta_vd171--V13.0.2.0.SJOMIXM.img
Ran with success, but when I run,
fastboot flash recovery filename (SHRP/TWRP/PBRP).img
But still unable to boot into the customer recover img, it only boots into the stock rom after sometime. If I power off + volume +, or adb reboot recovery I am in the MIUI recovery 5.0 main menu.
Thanks
Finally..able to install magisk with the below command.
fastboot flash boot magisk_patched-25200_ganYk.img
make sure you enable su in the app.
adb shell > su
But...
fastboot flash recovery filename (SHRP/TWRP/PBRP).img
Unable to boot into the customer recover img, it only boots into the stock rom after sometime. If I power off + volume +, or adb reboot recovery I am in the MIUI recovery 5.0 main menu.
Just don't use TWRP, there's custom os recoveries that work pretty well on miui 13 a12, you can try lineage or crdroid recovery, or just downgrade to miui 12 a11 and I can send you a working TWRP.
Hi, first of all, I'm not a dev or else just user who had difficulties to flash GSI on my phone... Was 7 years with a samsung galaxy Note 3, with twrp....So easy to flash....
with the help of @gr0ndpa, thanks to him.....
FLASH GSI
Now I will explain how to flash easily with files attached
1/ first of all you need a phone and drivers installed, use xiaomi pc suite, unzip and install it
2/ you need to activate USB debug in dev options.
3/ dl platform tools folder unzip it and put in C
4/ run command and type
Code:
cd /adb
5/ then
Code:
adb devices
to check if phone recognised
6/
Code:
adb reboot bootloader
once in fast boot
7/
Code:
fastboot flash vbmeta vbmeta.img
wait finished type to enter in fastbootD
8/
Code:
fastboot reboot fastboot
9/
Code:
fastboot flash system
LiR 313.XXX.img
you will have a system error, but wait the flash begin in few seconds
at the end wait ok then
10/
Code:
fastboot reboot recovery
on stock recover
11/ wipe data and reboot with +/- and PWR
and you're done...
In case you want to flash custom kernel or patched boot image to root with magisk, you have to
12/
Code:
adb reboot bootloader
Copy kernel boot image to C drive and rename kernel boot image to boot.img.
13/
Code:
fastboot flash boot c:\boot.img
14/
Code:
fastboot reboot
In case you want to flash twrp put the file to adb folder and type in fastboot
15/
Code:
fastboot boot twrp.img
You can check what I ve done on tuto ss...
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++==================================================================================================================================================================================================================++
Flash ROM
This now how to flash ROM on your device, it's convenient for all roms like LOS, corvus, awaken...
First you need all the proper drivers installed and unlocked bootloader, USB debugging all of that stuff.
Now open up a cmd/terminal , and put the files i sent and the ROM file in the folder from where you're opening the cmd/terminal and connect the phone (you may need to put ./ as an suffix for all the commands if you're on linux)
Type
Code:
adb reboot bootloader
Then type
Code:
fastboot devices
to see if everything is ok
Then type
Code:
fastboot flash boot_ab boot.img
(you can drag and drop the file instead of typing it)
After that's done type
Code:
fastboot flash vendor_boot_ab vendor_boot.img
(you can drag and drop this too if you want)
Code:
fastboot flash dtbo dtbo.img
(you can drag and drop this too if you want)
After that's done type
Code:
fastboot reboot recovery
This will boot you into a recovery and now you need to go to wipe and format data
After that go to apply update then adb sideload then
In the cmd type
Code:
adb sideload rom.zip
for example (you put the ROM zip here you can drag and drop it)
Wait for that to finish it will go to 47% and on the phone it will show step 1/2 then step 2/2
and when it's done it's gonna show an error
adb: failed to read command: No error
Then you can reboot to system
One more
Two more
This the tuto I follow to flash renoir, who have same characteristic than all Note 12 series... Tuesday I can confirm it works
I'm having a problem that my phone can't go to fastboot via CMD after I flash vbmeta.
Is is me doing wrong or also happen to you?