I posted this on reddit...but didn't get much help...i hope the geniuses at xda can help me
As the title says, the camera app (any camera app) won't work because as you start any of them, it asks to insert the sd card, but this is a 2013 Nexus 5...so it doesn't have an sd card.
I've done a fair amount of research and the only thing that seems to be mentioned is factory reset. I've done that...both through the settings and twrp. The phone has a stock marshmallow rom.
I tried to download any other file and it won't let me download anything becauase the "sd card" is not available. So it's as if the internal sd card isn't mounted? how do I fix this? I don't have a computer nearby to do anything with adb...any help would be GREATLY appreciated...
The amount of storage according to the settings is correct (3gb used of 12 gb..16gb nexus 5)...all app permissions are correct. I've reflashed two different stock firmwares with the exact same result.
Try this:
boot into fastboot;
run this fastboot command: fastboot erase recovery (to erase existing recovery);
run this fastboot command: fastboot flash recovery recovery.img (to flash stock recovery from stock ROM)
run this fastboot command: fastboot erase userdata;
run this fastboot command to flash the usedata img from the stock ROM: fastboot flash userdata userdata.img;
boot into stock recovery and perform a factory wipe/reset and wipe cache;
reboot.
audit13 said:
Try this:
boot into fastboot;
run this fastboot command: fastboot erase recovery (to erase existing recovery);
run this fastboot command: fastboot flash recovery recovery.img (to flash stock recovery from stock ROM)
run this fastboot command: fastboot erase userdata;
run this fastboot command to flash the usedata img from the stock ROM: fastboot flash userdata userdata.img;
boot into stock recovery and perform a factory wipe/reset and wipe cache;
reboot.
Click to expand...
Click to collapse
I'll try that tonight or tomorrow morning. Where do you suggest I download recovery.img (the stock recovery)?
Thanks for the help one way or another.. Hehe
The stock Google images are here: https://developers.google.com/android/nexus/images?hl=en
I assume the phone has an unlocked bootloader since you were able to flash stock ROMs.
What did you do between all being fine and now this problem?
Sent from my Xperia z5 using Tapatalk
Ben36 said:
What did you do between all being fine and now this problem?
Sent from my Xperia z5 using Tapatalk
Click to expand...
Click to collapse
I sold the phone to someone I know. I had a rom (i can't remember which)...so before i sold the phone, i encrypted it, wiped it clean, flashed the stock rom (and radio)....and did a factory reset.
audit13 said:
Try this:
boot into fastboot;
run this fastboot command: fastboot erase recovery (to erase existing recovery);
run this fastboot command: fastboot flash recovery recovery.img (to flash stock recovery from stock ROM)
run this fastboot command: fastboot erase userdata;
run this fastboot command to flash the usedata img from the stock ROM: fastboot flash userdata userdata.img;
boot into stock recovery and perform a factory wipe/reset and wipe cache;
reboot.
Click to expand...
Click to collapse
Thanks! I used the factory images and flashed everything from the compressed archive and it worked..you're a lifesaver. I guess I had to go further and reset everything..but thanks again!
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via recovery (either stock or twrp) because is no more needed. The updates will be done on the slot not used for example if you are using slot a the update will be installed on slot b and the slot b will be set as default. If you brick and you are in bootloop how you can restore the rom? You can't with Stock ROM you have, because the zip can be only installed via Update Engine, so what can you do? Flash a stock rom via fastboot. I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlocked. This will erase all your data and will wipe your internal storage.
HOW TO FLASH
This version is only for not branded devices
Download the zip;
Unpack the zip in a folder;
Reboot the OnePlus 7 in fastboot mode (Power and volume + and volume-);
Connect the OnePlus 7 to PC;
Run flash-all.bat flasher you need;
Wait until the process end;
The phone will automatically reboot.
FLASHER ADVANCED GUIDE
flash-all-partitions-fastboot.bat : this .bat will flash all possible partitions through fastboot (Except persist) , there are some criticals partitions that can't be flashed through fastboot;
flash-only-persist.bat : this .bat will flash only persist partition in fastboot mode (This is good for people that have problems with sensor);
flash-all-partitions-recovery-criticals.bat : this .bat will boot the twrp and will flash criticals partitions, use this carefully;
flash-system-boot-vendor.bat : this .bat is the same of older flash-all.bat and so it will flash only vendor, system and boot;
flash-all-partitions.bat : this .bat will run flash-all-partitions-fastboot.bat , then flash-only-persist.bat and then flash-all-partitions-recovery-criticals.bat .
Now usually the one needed is only the first "flash-all-partitions-fastboot.bat" but if you are badly bricked i recommend to use flash-all-partitions.bat .
DOWNLOAD
All roms on AFH: https://www.androidfilehost.com/?w=files&flid=295200
All roms on Sourceforge: https://sourceforge.net/projects/fastbootroms/files/OnePlus 7
BRANDED PHONE
For now branded device are not supported
MANUAL FLASH: Windows - OSX - Linux
If you want to manual flash these roms these are the commands (you need to extract images.zip before proceed)
Fastboot Partitions:
Code:
fastboot flash aop_a aop.img
fastboot flash aop_b aop.img
fastboot flash bluetooth_a bluetooth.img
fastboot flash bluetooth_b bluetooth.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash qupfw_a qupfw.img
fastboot flash qupfw_b qupfw.img
fastboot flash storsec_a storsec.img
fastboot flash storsec_b storsec.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash LOGO_a LOGO.img
fastboot flash LOGO_b LOGO.img
If you need also persist partition, this is the command:
Code:
fastboot flash persist persist.img
Criticals Partitions, for these you need to boot the TWRP:
Code:
fastboot boot TWRP.img
When you are in TWRP you need to run these commands to push and flash all criticals partitions:
Code:
adb push abl.img /sdcard/abl.img
adb shell dd if=/sdcard/abl.img of=/dev/block/bootdevice/by-name/abl_a
adb shell dd if=/sdcard/abl.img of=/dev/block/bootdevice/by-name/abl_b
adb push cmnlib.img /sdcard/cmnlib.img
adb shell dd if=/sdcard/cmnlib.img of=/dev/block/bootdevice/by-name/cmnlib_a
adb shell dd if=/sdcard/cmnlib.img of=/dev/block/bootdevice/by-name/cmnlib_b
adb push cmnlib64.img /sdcard/cmnlib64.img
adb shell dd if=/sdcard/cmnlib64.img of=/dev/block/bootdevice/by-name/cmnlib64_a
adb shell dd if=/sdcard/cmnlib64.img of=/dev/block/bootdevice/by-name/cmnlib64_b
adb push devcfg.img /sdcard/devcfg.img
adb shell dd if=/sdcard/devcfg.img of=/dev/block/bootdevice/by-name/devcfg_a
adb shell dd if=/sdcard/devcfg.img of=/dev/block/bootdevice/by-name/devcfg_b
adb push hyp.img /sdcard/hyp.img
adb shell dd if=/sdcard/hyp.img of=/dev/block/bootdevice/by-name/hyp_a
adb shell dd if=/sdcard/hyp.img of=/dev/block/bootdevice/by-name/hyp_b
adb push keymaster.img /sdcard/keymaster.img
adb shell dd if=/sdcard/keymaster.img of=/dev/block/bootdevice/by-name/keymaster_a
adb shell dd if=/sdcard/keymaster.img of=/dev/block/bootdevice/by-name/keymaster_b
adb push xbl.img /sdcard/xbl.img
adb shell dd if=/sdcard/xbl.img of=/dev/block/bootdevice/by-name/xbl_a
adb shell dd if=/sdcard/xbl.img of=/dev/block/bootdevice/by-name/xbl_b
adb push xbl_config.img /sdcard/xbl_config.img
adb shell dd if=/sdcard/xbl_config.img of=/dev/block/bootdevice/by-name/xbl_config_a
adb shell dd if=/sdcard/xbl_config.img of=/dev/block/bootdevice/by-name/xbl_config_b
adb push odm.img /sdcard/odm.img
adb shell dd if=/sdcard/odm.img of=/dev/block/bootdevice/by-name/odm_a
adb shell dd if=/sdcard/odm_config.img of=/dev/block/bootdevice/by-name/odm_b
adb push tz.img /sdcard/tz.img
adb shell dd if=/sdcard/tz.img of=/dev/block/bootdevice/by-name/tz_a
adb shell dd if=/sdcard/tz.img of=/dev/block/bootdevice/by-name/tz_b
REMEMBER
"Invalid sparce file format at header magic" is not an error, you need to wait a bit when you see that string, just wait.
These ROMs can't be used to update or downgrade your phone but just to restore your phone, so don't use them to come back to oreo or to update from oreo to pie.
If the rom seems doesn't start go in recovery stock and follow this guideline: English -> Wipe data and cache -> Erase everything.
If you want to rebrand your phone from HydrogenOS to OxygenOS you can follow this guide: Rebrand Guide
If you want you can use also my tool to flash Factory Images, unlock bootloader, flash twrp or to understand if the device is recognized: https://toolaio.tk/
Thanks to @SaiBork for first time tested
If you got some problems like write error or no partition, check this: https://forum.xda-developers.com/showpost.php?p=76658555&postcount=34
DONATE LINK
If you want to support this and others my projects please consider making a donation, thanks.
What does branded devices mean?
What about locking the bootloader. I noticed recovery image is not included
Recovery is a part of the boot image for A/B devices such as Oneplus 7.
---------- Post added at 02:47 PM ---------- Previous post was at 02:46 PM ----------
arvindgr said:
What does branded devices mean?
Click to expand...
Click to collapse
Branded device means it is customized by mobile service provider, such as T Mobile.
any way to flash this without erasing data
Dragonlord07 said:
any way to flash this without erasing data
Click to expand...
Click to collapse
There were multiple scripts included in the zip
Just Be sure to flash the script that does not include -w fastboot parameter
Also, @mauronofrio My phone was originally GM57AA, but since stock image is of GM57BA my phone become GM57BA. Any ideas on how to go back to GM57AA...?
Dragonlord07 said:
any way to flash this without erasing data
Click to expand...
Click to collapse
Just remove -w from the script
arvindgr said:
There were multiple scripts included in the zip
Just Be sure to flash the script that does not include -w fastboot parameter
Also, @mauronofrio My phone was originally GM57AA, but since stock image is of GM57BA my phone become GM57BA. Any ideas on how to go back to GM57AA...?
Click to expand...
Click to collapse
Just flash the GM57AA rom, there are boths in the link you can find in the first post
Ismael034 said:
What about locking the bootloader. I noticed recovery image is not included
Click to expand...
Click to collapse
Hello, I have sent you a message regarding this message. a greeting.
Stuck at boot animation. Is there a way to make it do it's thing on both slots?
fusk said:
Stuck at boot animation. Is there a way to make it do it's thing on both slots?
Click to expand...
Click to collapse
Go in stock recovery, go to wipe data, check also internal storage and wipe it, then it should work.
mauronofrio said:
Go in stock recovery, go to wipe data, check also internal storage and wipe it, then it should work.
Click to expand...
Click to collapse
There is 3 options. Reset system settings, wipe cache & erase everything. There does not appear to be an option to "wipe data" like it would say in twrp or check internal storage. I erased everything and restarted the process, hope that was what you meant.
---------- Post added at 19:23 ---------- Previous post was at 19:15 ----------
That worked, now my question is. The reason i was doing this was because slot B was unable to mount storage, slot A worked fine and phone worked fine. Would this process fix the issue i had with slot B?
fusk said:
There is 3 options. Reset system settings, wipe cache & erase everything. There does not appear to be an option to "wipe data" like it would say in twrp or check internal storage. I erased everything and restarted the process, hope that was what you meant.
---------- Post added at 19:23 ---------- Previous post was at 19:15 ----------
That worked, now my question is. The reason i was doing this was because slot B was unable to mount storage, slot A worked fine and phone worked fine. Would this process fix the issue i had with slot B?
Click to expand...
Click to collapse
if in the slots you have different roms with different security patches only the recent slot will be able to boot. In the .bat there is a command to wipe data, but i don't know why it doesn't work on the oneplus 7 pro
mauronofrio said:
if in the slots you have different roms with different security patches only the recent slot will be able to boot. In the .bat there is a command to wipe data, but i don't know why it doesn't work on the oneplus 7 pro
Click to expand...
Click to collapse
I don't have a 1+7p, so i wouldn't know anything about that. Phone was 9.5.5 when i got it, updated to 9.5.6 with some problems. Wanted to update to 9.5.7 which was unsuccessful. When loading slot B in twrp it could not mount storage or sdcard. Looking at cmd while running your tool, it looks like it's only working with slot A and not touching slot B at any point.
---------- Post added at 19:48 ---------- Previous post was at 19:28 ----------
Appears it worked, can now boot both slots and mount storage and sdcard on both. Thanks for the assist.
fusk said:
I don't have a 1+7p, so i wouldn't know anything about that. Phone was 9.5.5 when i got it, updated to 9.5.6 with some problems. Wanted to update to 9.5.7 which was unsuccessful. When loading slot B in twrp it could not mount storage or sdcard. Looking at cmd while running your tool, it looks like it's only working with slot A and not touching slot B at any point.
---------- Post added at 19:48 ---------- Previous post was at 19:28 ----------
Appears it worked, can now boot both slots and mount storage and sdcard on both. Thanks for the assist.
Click to expand...
Click to collapse
Hello friend, can you say how you did it in the end so that the two slots (A and B) will work? Thank you. Was it because you had encrypted memory and did not let mount slot B? What did you do? Thanks greetings.
mauronofrio said:
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via recovery (either stock or twrp) because is no more needed. The updates will be done on the slot not used for example if you are using slot a the update will be installed on slot b and the slot b will be set as default. If you brick and you are in bootloop how you can restore the rom? You can't with Stock ROM you have, because the zip can be only installed via Update Engine, so what can you do? Flash a stock rom via fastboot. I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlocked. This will erase all your data and will wipe your internal storage.
Click to expand...
Click to collapse
@mauronofrio Hello friend, thanks for your work, I want to ask you if these files to put a rom by fastboot are valid for my version of OnePlus 7 (not pro) Chinese version Gm1900?
Another question I have is, my oneplus 7 gm1900 came with the AA version and I manually added the BA version locally for local improvement. If this fastboot method works, could I put the BA or do I have to put the AA files first?
Thank you.
tURkOsANsE said:
Hello friend, can you say how you did it in the end so that the two slots (A and B) will work? Thank you. Was it because you had encrypted memory and did not let mount slot B? What did you do? Thanks greetings.
Click to expand...
Click to collapse
I did as mentioned. When the .bat failed, i entered "Go in stock recovery" and choose "erase everything" and then ran the .bat again and it worked. I had encryption on both, so that was not the issue. It's fixed now.
fusk said:
I did as mentioned. When the .bat failed, i entered "Go in stock recovery" and choose "erase everything" and then ran the .bat again and it worked. I had encryption on both, so that was not the issue. It's fixed now.
Click to expand...
Click to collapse
Thank you for answering friend, what version do you have of OnePlus 7? Do you have the Chinese version Gm1900 ?.
Before putting the rom by fastboot did you have Twrp installed?
mauronofrio said:
if in the slots you have different roms with different security patches only the recent slot will be able to boot. In the .bat there is a command to wipe data, but i don't know why it doesn't work on the oneplus 7 pro
Click to expand...
Click to collapse
Hello friend, thanks for your work, I want to ask you if these files to put a rom by fastboot are valid for my version of OnePlus 7 (not pro) Chinese version Gm1900?
Another question I have is, my oneplus 7 gm1900 came with the AA version and I manually added the BA version locally for local improvement. If this fastboot method works, could I put the BA or do I have to put the AA files first?
Thank you.
tURkOsANsE said:
Hello friend, thanks for your work, I want to ask you if these files to put a rom by fastboot are valid for my version of OnePlus 7 (not pro) Chinese version Gm1900?
Another question I have is, my oneplus 7 gm1900 came with the AA version and I manually added the BA version locally for local improvement. If this fastboot method works, could I put the BA or do I have to put the AA files first?
Thank you.
Click to expand...
Click to collapse
Yes it will work on the oneplus 7, there are 2 different thread for the fastboot roms this one is for oneplus 7 only. AA or BA there are not a lot of.differences, just use the one you prefer.
I accidentally made a mistake, flash custom kernel when my phone has custom kernel installed. Now every time i'm trying to boot up, my phone is only able to boot on fastboot mode, no recovery and i unable to install recovery too (stock/custom).
I wonder, is this method can save my phone?
Thank you.
cakriez92 said:
I accidentally made a mistake, flash custom kernel when my phone has custom kernel installed. Now every time i'm trying to boot up, my phone is only able to boot on fastboot mode, no recovery and i unable to install recovery too (stock/custom).
I wonder, is this method can save my phone?
Thank you.
Click to expand...
Click to collapse
Yes
Hi All.
I have stuck in weird issue in my pixel 3. Can't able to install any custom rom
Process I hav gone through..
Flash the stock rom Android 10/11 using flash all.bat (downloaded from Google website)
Then install the custom ROM'S boot image and install rom using adb sideload.
There is no error after adb sideload. Showing success.
After reboot, it normally boot into stock os.
Please help me to fix the same. Thanks in advance.
logeshwywan said:
Hi All.
I have stuck in weird issue in my pixel 3. Can't able to install any custom rom
Process I hav gone through..
Flash the stock rom Android 10/11 using flash all.bat (downloaded from Google website)
Then install the custom ROM'S boot image and install rom using adb sideload.
There is no error after adb sideload. Showing success.
After reboot, it normally boot into stock os.
Please help me to fix the same. Thanks in advance.
Click to expand...
Click to collapse
I recently had similar issues (maybe same) doing Lineage. For me the key was to switch to using a usb 2.0 port. Lineage mentions doing this in their directions. I'm familiar with apps like qfil needing it also. Sure enough, all worked as expected with a 2.0 usb port.
cheers
Did you flash stock to both slots? Here's how I flash a custom ROM, starting with a clean flash of stock image:
Once in fastboot:
fastboot --slot=all flash bootloader stock-bootloader.img(or drag and drop to cmd window)
fastboot reboot bootloader
fastboot --slot=all flash radio stock-radio.img(or drag and drop to cmd window)
fastboot reboot bootloader
fastboot --slot=(current slot) --skip-reboot update stock-image.zip(or drag and drop to cmd window)
fastboot reboot bootloader
fastboot --slot=(other slot) --skip-reboot update stock-image.zip(or drag and drop to cmd window)
Then you enter recovery and wipe/format data and reboot to system after.
From here, you enable USB debugging and reboot back into fastboot and follow the flashing instructions for your preferred ROM.
AlexKarimov said:
Did you flash stock to both slots? Here's how I flash a custom ROM, starting with a clean flash of stock image:
Once in fastboot:
fastboot --slot=all flash bootloader stock-bootloader.img(or drag and drop to cmd window)
fastboot reboot bootloader
fastboot --slot=all flash radio stock-radio.img(or drag and drop to cmd window)
fastboot reboot bootloader
fastboot --slot=(current slot) --skip-reboot update stock-image.zip(or drag and drop to cmd window)
fastboot reboot bootloader
fastboot --slot=(other slot) --skip-reboot update stock-image.zip(or drag and drop to cmd window)
Then you enter recovery and wipe/format data and reboot to system after.
From here, you enable USB debugging and reboot back into fastboot and follow the flashing instructions for your preferred ROM.
Click to expand...
Click to collapse
Thanks for your inputs, will try with your steps.. I have one doubt on this..As per Google's statement "Execute the flash-all script. This script installs the necessary bootloader, baseband firmware(s), and operating system." - Flash-all script won't flash on both slots? please clarify! Because I did stock rom flash in that way only..
AsItLies said:
I recently had similar issues (maybe same) doing Lineage. For me the key was to switch to using a usb 2.0 port. Lineage mentions doing this in their directions. I'm familiar with apps like qfil needing it also. Sure enough, all worked as expected with a 2.0 usb port.
cheers
Click to expand...
Click to collapse
Wholla! It's working fine with 2.0 USB Ports. Many thanks for your suggestions.
Tried with 2 custom roms, perfectly great with first attempts..!
logeshwywan said:
Thanks for your inputs, will try with your steps.. I have one doubt on this..As per Google's statement "Execute the flash-all script. This script installs the necessary bootloader, baseband firmware(s), and operating system." - Flash-all script won't flash on both slots? please clarify! Because I did stock rom flash in that way only..
Click to expand...
Click to collapse
I don't use the flash-all script, I use ADB and fastboot. Someone in the Dirty Unicorns thread had the same issue and edited the flash-all.bat and left instructions but he still had to use ADB and fastboot in the end to set the active slot and run flash-all again.
From the DU thread:
And could you please explain how we flash it to both slots?
Edit; got it working now
- Removed the -w in flash-all (not sure if it was necesarry)
- Runned flash-all while on b
- Then fastboot --set-active a
- Runned flash-all while on a
Then followed the instructions, and it worked.
So, for those that may not realize, we should clarify why we may want to flash to both slots;
A custom rom isn't 'complete' by itself. It uses the 'blobs' that are a part of the original firmware. By flashing 'both' slots with the same firmware, that means when the custom rom does an 'update', both slots will have the same version of the 'blobs', and the update will work as expected.
So, if you never plan to update the custom rom, and only want to 'test' it, there's no reason to flash both slots. But, this does necessitate you know which slot you're on, and which slot things are being flashed to, of course.
Yeah, the A/B slot thing, it's confusing.
cheers
Suppose we want to flash the boot.img file to the A and B Slot of the boot partition. So the general command that I use is:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Click to expand...
Click to collapse
However, nowadays, I am coming across this command:
fastboot flash boot_ab boot.img
Click to expand...
Click to collapse
So do both the commands perform the same functionality? In other words, would the 'fastboot flash boot_ab boot.img' command flash the boot.img file to both the A and B partition?
As far as I know, yes. The official documentation doesn't tell me anything about it ("fastboot -h"/"fastboot flash -h")
My steps
1. oem unlock and unlock bootloader with the command
2. get the files from lmsa
3. Patch boot.img using magisk
4. Flash boot.img and vbmeta.img
5. Reboot using fastboot reboot
It should boot me normaly but it boots in to the boot loader
What device are you talking about ?
f1tm0t said:
What device are you talking about ?
Click to expand...
Click to collapse
Tab p11 4gig
Return the stock boot.
I can't tell you anything specific about this device. I own other.
If there is TWRP for your version of Android, flash Magisk.zip from TWRP.
f1tm0t said:
Return the stock boot.
I can't tell you anything specific about this device. I own other.
If there is TWRP for your version of Android, flash Magisk.zip from TWRP.
Click to expand...
Click to collapse
Threr is no twrp sadly
blocky3321 said:
My steps
1. oem unlock and unlock bootloader with the command
2. get the files from lmsa
3. Patch boot.img using magisk
4. Flash boot.img and vbmeta.img
5. Reboot using fastboot reboot
It should boot me normaly but it boots in to the boot loader
Click to expand...
Click to collapse
who told you to flash vbmeta.img?
You should flash patched_boot.img in fastbootd
You need to edit out vbmeta.img / vbmeta_system.img to actually disable verification. Change the byte at offset 123 from 0x00 to 0x03.
Another way is to use the following command when flashing vbmeta. You may need to use a relatively newer version of fastboot binary to get it work.
Code:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
mingkee said:
who told you to flash vbmeta.img?
You should flash patched_boot.img in fastbootd
Click to expand...
Click to collapse
I tried it i flashed patched boot.img only in fastbootd still boots me in to the bootloader
LSS4181 said:
You need to edit out vbmeta.img / vbmeta_system.img to actually disable verification. Change the byte at offset 123 from 0x00 to 0x03.
Another way is to use the following command when flashing vbmeta. You may need to use a relatively newer version of fastboot binary to get it work.
Code:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
Click to expand...
Click to collapse
now it only boot in to the bootloader earlier it would boot normaly if i did factory treset in recovery mode
blocky3321 said:
now it only boot in to the bootloader earlier it would boot normaly if i did factory treset in recovery mode
Click to expand...
Click to collapse
Which Magisk version did you use? From what I can tell any official Magisk version should work.
I haven't really tested the recent builds of vvb2060's Alpha or huskydg's Delta... so if you're using these versions I can't really help you much...
Additionally, you need to check which slot you are now, and through fastbootd check which slot actually has system, vendor and such. Normally the super partition only has enough size for one slot. You may have entered a wrong slot that doesn't have usable system.
blocky3321 said:
My steps
1. oem unlock and unlock bootloader with the command
2. get the files from lmsa
3. Patch boot.img using magisk
4. Flash boot.img and vbmeta.img
5. Reboot using fastboot reboot
It should boot me normaly but it boots in to the boot loader
Click to expand...
Click to collapse
Getting Started: What's Your Device ?
Tab p11 4gig
Device->settings->About : Model & Hardware -> Lenovo ??? (Tb-j606f,TB-J616F...) In your case stiker on box or on back.
mingkee said:
who told you to flash vbmeta.img?
Click to expand...
Click to collapse
???