Database Users

[TUTORIAL] Remounting/restoring/backup the /EFS partition

/EFS partition contains a lot of information about your phone, f.e: wifi/bt mac address and your IMEI (nv_data.bin).
It's highly recommended to backup the whole partition, or at least copy the files from the efs directory.
CORRUPTED OR NOT?
You can check if the efs is mounted or completly damaged with this command:
adb shell
mount
You will see something like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Red part means /efs is mounted.
IF YOUR PHONE HAVE CORRECT EFS PARTITION:
1, Root your phone - there are several methods to do this.
2, Install root explorer or Estrongs file explorer and copy /efs dir to your sdcard - this will copy the files.
or
2, Make a backup from the whole partition -this is better if you flash a phone with wrong ops, the only way to restore using this backup.
Backup:
adb shell
su
dd if=/dev/block/stl4 of=/sdcard/efs.rfs
Restore:
Add efs.rfs to an unix compatible tar and flash with odin as efs file:
IF YOUR PHONE /EFS IS CORRUPTED:
Flash the included /efs tar with odin:
This will remount your efs partition and (if you have a backup or fixed nv_data.bin) you just need to overwrite files with a file explorer.

confirm WORKING 100% ... all you just need later is the nv_data.bin fixed
Thanks so much for your efforts

I am using I5801 JPB (with restored bootscreen and Rooted via SuperoneClick)
while using "adb shell" command at Better terminal its showing "adb: not found"
I flashed my I5801 from JP9, JPA and JPB till date..
is it possible to restore the backup now..??

Because you need adb.
If you do on phone (Terminal emualtor) adb shell not needed, just su and the other commands.

Szaby59 said:
Because you need adb.
If you do on phone (Terminal emualtor) adb shell not needed, just su and the other commands.
Click to expand...
Click to collapse
many thnx..
BTW i am not able to get the snaps u attached..

sirtbhopal said:
many thnx..
BTW i am not able to get the snaps u attached..
Click to expand...
Click to collapse
google about install ADB for android phone, so you can follow TUT here... good for you now and future..., long journey to go, m8!

how to make .tar file because backup file is .rfs format help me i want my imei back

ok, using the dd method i made the backup of my /efs to a efs.rfs file that have ~4 MB
But when i go to the efs folder (on / ) or see the copy i've made to my SD card, there is no files at all on this folder. How can we "see" those files (nv_data.bin) ?

Hi
For backup I simply copied my /efs folder to SD card using root explorer.
Then I modified nv_data files to get unlocked.
there was no SSNV in the files.
I have a working unlocked phone now but the problem is that IMEI is all zeros like 000000000!
Can I use that folder to restore my files?

dhruvasoni said:
how to make .tar file because backup file is .rfs format help me i want my imei back
Click to expand...
Click to collapse
Download the Tar Utility from GnuWin32's SourceForge Page.
Code:
hxxp://sourceforge.net/projects/gnuwin32/files/tar/1.13-1/tar-1.13-1-bin.exe/download
(change it to http)
It'll install the tar.exe executable and required dlls in C:\Program Files\GnuWin32\bin
Copy those to where you have your rfs (or you can add the bin folder to your PATH Environment Var, google for help on how to do that)
Now type:
Code:
tar -cf efs.tar efs.rfs

Yes, you can, just copy nv_data to /efs.
Windows users can use IZARC to create tar files.

hey guys
i havn´t backuped my file but i have now imei 0000000000000
i need help help me please!!!

burak721 said:
hey guys
i havn´t backuped my file but i have now imei 0000000000000
i need help help me please!!!
Click to expand...
Click to collapse
If you use a I5801 flash a stock firmware of 2.1...the same applies even if you use I5800...
Sent from my GT-I5800 using XDA App

i have done it but my imei is allways 00000000
pleas help

Burak, what kernel do u use? There was a bug in older fugumod version where eds was not propperly mounted or read, thus the phone displayed bad imei, if u use older fugumod please update to latest version

FadeFx said:
Burak, what kernel do u use? There was a bug in older fugumod version where eds was not propperly mounted or read, thus the phone displayed bad imei, if u use older fugumod please update to latest version
Click to expand...
Click to collapse
I have used fugomod kernel 2.4
Sent from my GT-I5800 using XDA App

my imei is also showing ooooooo.....plss help mee dudes plss

i dont have imei at all!!! and sim card is not recognized,and no signal,phone unknown ....what am i supposed to do?

huzo said:
i dont have imei at all!!! and sim card is not recognized,and no signal,phone unknown ....what am i supposed to do?
Click to expand...
Click to collapse
Pray ...

LOL good answer

[UTILITY][RUU IMITATE]Easy Installer - Install your rom's like an RUU[HTC only]

Easy Installer​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What is Easy Installer?
Easy installer is a windows RUU imitate that helps you as user to install your Rom's with only 2 clicks. Fully automated!
For devs Easy installer helps to provide Rom's alternate to the recovery zip archive.
Click to expand...
Click to collapse
How does Easy installer work?
Thats easy. The developer create a system img file of his rom and configure Easy installer easily with one config file. The package can provide like a normal rom.
The user run a little exe-file and the RUU installs the rom fully automated! If something runs false, the RUU gives the user an error and a explanation what he can to do now.
Click to expand...
Click to collapse
What i need for Easy installer
For now, Easy Installer works only with image files, so you need your Rom as a image file. You can create a image file of your rom easily with mkyaffs.arm (find in attachements).
The config file is easy to understand. An example here (found in package too):
Code:
;The config file is neccessary for the RUU. Here you define all file namens.
[functions]
;imgfile specify, if you want to flash a image or a zip file (0=zip-file, 1=img-file). For now, only img files working, sry :(
imgfile=1
;waitbl set the time the RUU wait for the bootloader (fastboot). Some devices take a while to reboot to bootloader. Set the time here, in generally the time 10 is enough
waitbl=10
;the img-name specify the name of the image file without the file extension!
img-name=system
;zip-name is for one of the next versions, when it is possible to flash zip files. If you want, you can delete this
zip-name=HC_MIUI3.2
;boot-name specify the name of the boot.img without extension.
boot-name=boot
;set the name of the clockworkmod recovery file for your device here.
cwm-name=cwm
;rec-name is the original recovery of HTC that must be inserted for img-files. Put the name here without extension
rec-name=recovery
[labels]
;specify the shown rom-name in the RUU
rom-name=.sense
;the device name is the full name of the device the rom is for
device-name=Wildfire S
;some devices has more versions (marvel, marvelc, marvelct e.g.). Specify for what device your rom is.
device-code=marvel
The picture in the RUU is namend "PHONE.bmp" in package, you can replace with your own.
Click to expand...
Click to collapse
How to create the system.img?
Well, thats is easy
1. Install your Rom you want to use in Easy Installer at your phone via the Recovery (don't start the Rom!!!)
2. Go to recovery, connect your phone via USB-Cable to computer
3. Download the mkfs.arm.zip (see attachements)
4. Create a new directory in your SD-Card (example: "build")
5. Copy the extracted file "mkfs" of the downloaded archive into the folder "build"
6. Insert the SD-Card into the phone
7. In recovery go to: "mounts&storage->mound /sdcard" or run following adb-command: adb mound /sdcard
8. run the following commands in adb one after one:
adb shell
cd /sdcard/build
./mkfs /system /sdcard/build/system.img
9. Wait for the "Build OK."-message
10. Exit the adb shell via exit command and turn off the phone
11. Take the SD-Card of the phone and insert it into your PC
12. in the SD-Card's folder /build you will find a "system.img". Use this file for the easy installer
Click to expand...
Click to collapse
Changelog
v0.0.1
- first version, basic install function
Click to expand...
Click to collapse
Download
See the attachements (WSWizard.zip)
Click to expand...
Click to collapse

Will this work for all devices?
Any chances of bricking? Because many of users of Micromax A70 bricked their phone by a chinese flashing tool.
Burned from my laser torch using pencil cells

Sorry, i see now, that i posted this in false section. In genarally it works only for HTC devices which are unlocked or S-OFF, not for others!

How can I use the mkfs.arm?

it works only on ARM-based devices, like the HTC phones.
You must copy the file onto your sd-card e.g.:
adb push mkfs.arm /sdcard/build
After this you install your Rom on the device or copy the /system-files to the sd-card. Now you run following command:
adb shell
cd /sdcard/build
./mkfs.arm /system /sdcard/system.img
ODER
./mkfs.arm /sdcard/build/system /sdcard/system.img
Then the file will build a system.img and copy it onto the sdcard for next use

Would like to know if this would work to ONelll123
Wipe everything
Flash Rom
Make Nandroid
Use Nandroid as ROM's Images
It seems much easier to me than having to go to shell and all Not meant to be an insult, just a recommendation/question

Hmm, it ia qn idea, but idk in what filesystem the backups are saved. If it is yaffs2 it can be that this works.
But you must do shell commands too. Its for secruity reasons and that this method used works.
Sent from my HTC Wildfire S A510e using XDA

ONeill123 said:
it works only on ARM-based devices, like the HTC phones.
You must copy the file onto your sd-card e.g.:
adb push mkfs.arm /sdcard/build
After this you install your Rom on the device or copy the /system-files to the sd-card. Now you run following command:
adb shell
cd /sdcard/build
./mkfs.arm /system /sdcard/system.img
ODER
./mkfs.arm /sdcard/build/system /sdcard/system.img
Then the file will build a system.img and copy it onto the sdcard for next use
Click to expand...
Click to collapse
Thanks I will be try this when htc one x gets adb working recovery

Root Nexus 4 on Linux

I just rooted my Nexus 4 using Ubuntu 12.04.
The instructions I found weren't quite what I'd liked them to be, none of them were for Linux and I had to do quite a bit of trial and error.
I know that a few years ago I wouldn't have been able to do it with those instructions.
So I thought I'd write down what I did so others can do it easier and faster than me.
To be able to easily understand this guide you need to know the basics about using a terminal, but other than that I'm trying to not to require the reader to know anything.
If you use another Linux distro everything should work pretty much exactly the same, but for the additional packages I had to install, but their name should be easy to guess because they are usually similar across distributions and how you install them should be explained in the documentation of your distro.
Connect your Nexus 4 to your computer using an USB cable.
First I downloaded the ADT Bundle from there developer.android.com/sdk/index.html and unpacked it into a new folder. Doesn't matter where, I'll use ~/androidSDK in those instructions. The tools which you need to root your phone are ~/androidSDK/adt-bundle-linux-x86-20130514/sdk/platform-tools/adb and ~/androidSDK/adt-bundle-linux-x86-20130514/sdk/platform-tools/fastboot
"x86" means I downloaded the 32bit version and "20130514" is the date of when the version I'm using was published, that will most likely be different for other people.
Now most likely adb and fastboot won't run yet (if you run them it will tell you something like "~/androidSDK/adt-bundle-linux-x86-20130514/sdk/platform-tools/adb: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory"). To fix this you need to install the packages "lib32ncurses5" and "lib32stdc++6". You can run the following command to do that:
Code:
sudo apt-get install lib32ncurses5 lib32stdc++6
(got that from there: stackoverflow.com/questions/10005907/eclipse-android-plugin-libncurses-so-5)
For adb to work you also need to activate USB debugging: Go to Settings->About phone and tap "Build Number" until it says you are developer. Then a new entry will appear in "Settings", called "{ } Developer options". Check the box next to "USB debugging", confirm with ok.
Now you need to backup everything on your Nexus 4 because it will be wiped while rooting. You can do this by running:
Code:
cd ~/androidSDK/adt-bundle-linux-x86-20130514/sdk/platform-tools
(in the future I'll assume you stayed inside that directory)
Code:
./adb backup -apk -shared -all -system
Before this command can finish you need to confirm on your Nexus 4 that it's okay to do that backup (just do what it says on it's screen).
This will put a file named backup.ab in the current directory. You can change the name and location of that file using the -f paramter, if you want.
Run
Code:
./adb reboot bootloader
to boot into the bootloader. After a moment the Nexus 4 should display something like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(image stolen from reviews.cnet.co.uk/mobile-phones/how-to-root-your-google-nexus-4-50010361/)
Now the actual unlocking happens: Enter
Code:
sudo ./fastboot oem unlock
Maybe try without sudo first (just leave it out), but it only worked with sudo for me; without sudo it displayed "waiting for device" forever and I needed to abort with Ctrl+C.
Download SuperSU from there http://download.chainfire.eu/supersu (at the moment "CWM-SuperSU-v0.98.zip").
Put that file on your Nexus 4 any way you want, one possible way is to do:
Code:
./adb push ~/CWM-SuperSU-v0.98.zip /sdcard/
That assumes you downloaded SuperSU to your home directory. For that to work you need to activate USB debugging again (it was deactivated during unlocking).
Download the Nexus 4 "Touch Recovery" from www.clockworkmod.com/rommanager.
I guess you shouldn't need the touch version, but it's more comfortable for sure. When I downloaded it the file was named "recovery-clockwork-touch-6.0.4.7-mako.img" and that's what I'm going to use when I give you commands to run.
This "Touch Recovery" needs to be installed to the Nexus 4. To do this first boot into the bootloader again:
Code:
./adb reboot bootloader
And then flash the file using the fastboot utility:
Code:
sudo ./fastboot flash recovery recovery-clockwork-touch-6.0.3.1-mako.img
(if it needed sudo the last time it will need it again, if not, not)
Now go to the recovery mode (use volume buttons to navigate and power to confirm).
Tap "install zip from sdcard"
Tap "choose zip from sdcard"
Tap "0/"
Find the SuperSU .zip file you put on the phone earlier (tip: scrolling works as usual by swiping or if you want with the volume buttons) and tap on it.
Confirm that you really want to install it.
Boot into Android again and restore the backup you made earlier (if you made one).
Code:
./adb restore backup.ab
You need to confirm that command on the Nexus 4.
As you are now finished you can of course disconnect your Nexus 4 from your computer.
You should be finished now. Unless I remembered something wrongly when writing this because I mostly wrote this from memory, after rooting my Nexus 4. If something doesn't work as I claim then please tell me and I'll fix it (possibly eventually).
I myself followed those instructions http://forum.xda-developers.com/showthread.php?t=2018179 as far as possible and then googled what didn't work or just tried around for a bit.
Edit: As of now (18.8.14), those instructions should still work.

TWRP Serious problem after failed restore: unable to decrypt storage

So today I wanted to try something as I had issues with an app.
I made a full nandroid backup with twrp.
After setting up my phone and try the new app I wanted to restore to the old situation.
When restoring I got the error
createTarFork() process ended with ERROR: 255
After a reboot, no decryption password is asked, all files and folders have strange names.
As a result the phone doesn't boot any more except into recovery.
I'm on oxigen os 9.0.8, latest twrp.
Any clues on how I can fix this.
Phone is a brick now...

yelti said:
So today I wanted to try something as I had issues with an app.
I made a full nandroid backup with twrp.
After setting up my phone and try the new app I wanted to restore to the old situation.
When restoring I got the error
createTarFork() process ended with ERROR: 255
After a reboot, no decryption password is asked, all files and folders have strange names.
As a result the phone doesn't boot any more except into recovery.
I'm on oxigen os 9.0.8, latest twrp.
Any clues on how I can fix this.
Phone is a brick now...
Click to expand...
Click to collapse
Some treads below yours is the possible solution https://forum.xda-developers.com/oneplus-5/help/createtarfork-process-error255-t3727673
And: you should always remove pin/security before restore or before backup

strongst said:
Some treads below yours is the possible solution https://forum.xda-developers.com/oneplus-5/help/createtarfork-process-error255-t3727673
And: you should always remove pin/security before restore or before backup
Click to expand...
Click to collapse
Thx,
I checked but not really my situation.
I don't have the 999 users issue.
I have made a screenshot of my /sdcard folder:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
* it seem that my picture is not comming through, so a link to it imgur
Hopes this sheds some light.
What I got from those threads:
My backup was pretty large, 22GB.
I think I will try to flash the stock rom and see where that gets me.

yelti said:
Thx,
I checked but not really my situation.
I don't have the 999 users issue.
I have made a screenshot of my /sdcard folder:
* it seem that my picture is not comming through, so a link to it imgur
Hopes this sheds some light.
What I got from those threads:
My backup was pretty large, 22GB.
I think I will try to flash the stock rom and see where that gets me.
Click to expand...
Click to collapse
So I tried a sideload of the factory images.
Flashing is successfull, next I reboot the phone.
It shows me the oneplus logo and reboots to recovery.
I tried installing the stock recovery, but then when I try to sideload the firmware, the usb device is not recognized.

I have an idea, but I don't know if is doable.
I would want to backup the data partition, (adb pull /dev/block/sda13 data_encrypted.img).
Next I would wipe the phone completely, setup encryption with the same pincode.
Next I would like to restore the old data, but I don't know how.
I hope this way I will ask to decrypt my data partition again.
Anyone an idea?

So an update:
I dumped the data and recovery partition.
Code:
adb pull /dev/block/sda13 data_encrypted.img
adb pull /dev/block/sde22 recovery.img
5494 KB/s (67108864 bytes in 11.927s)
Next I wiped the data partition, phone started normally.
I encrypted the phone again with the same pin code.
Next I tried a nandroid backup and restore while the phone was encrypted, no issues there.
Next I flashed an older recovery to the phone.
Now the test to restore the recovery from the image.
On the phone with an adb sheel:
Code:
dd of=/dev/block/sde22 | nc -l -p 9999
On the pc:
Code:
adb forward tcp:9999 tcp:9999
nc 127.0.0.1 9999 < recovery.img
On the phone I get a lot of data on the screen and the message
Code:
8+0 records in
8+0 records out
4096 bytes transferred in 64.155 secs (63 bytes/sec)
First thing I noticed: number of bytes transferred where not the same as the original recovery.
Next I dumped the recovery partition again to disk and compared the md5 hashes, not the same.
Rebooted the phone and it did not go into recovery.
So this process did not work.
Any ideas?

So, It didn't work with netcat, so I did the following:
connect an usb-c to usb-a coverter to the phone, and connected the external drive with the "bad" image on it.
Then dd-ed the image to the data partition.
When I rebooted the phone, it didn't ask for a pin code and the file and folders where gibbirish again.
So I was back to the starting position.
I'm affraid my data is lost forever :s.

Hello @yelti , I know it's been a long time but I'm kinda into the same issue. Have you been able to fix yours? Do you remember how? Thanks.

[GUIDE] System partition too small? Installing Android 12, GApps & large GSIs on Pixel 2!

SPECIAL THANKS TO
@Lunarixus on XDA
I wouldn't have figured out how to maneuver the pixel 2 XL partition table without him.​
!!!WARNING PLEASE READ!!!!
This tutorial only applies to Walleye (regular 2). There's another tutorial for Taimen (2 XL). Please join the telegram group if you can! ​Google Pixel Development Group.​​ALSO, this only increases system partition on slot B. If you want to flash GSIs, make sure you are on the correct slot with this command:​​fastboot --set-active=b​​REQUIREMENTS:
Walleye with unlocked bootloader.
Updated adb & fastboot binaries.
GNU parted for ARM64. Get it here: https://guidedflame.dev/parted
Custom recovery for Walleye with adb support.
STEPS:
1. Enable USB Debugging​
2. Reboot into fastboot mode​adb reboot bootloader​
3. Boot into the recovery (format data if it is stuck on splash screen)​fastboot boot path/to/recovery.img ​(optional) you can flash TWRP permanently if you wish. fastboot flash boot_a path/to/recovery.img and fastboot flash boot_b path/to/recovery.img DO NOT FLASH TWRP. JUST BOOT TO IT.​
4. In TWRP...​
If it asks you to decrypt your data, do it.
If it asks you to swipe for RW permissions on system partition, do it.
Unmount all partitions. Click on Mount, then un-tick everything.
5. Back to your PC. Copy parted to /sbin.​adb push path/to/parted /sbin​
6. Enter shell mode.​adb shell​
7. Change permissions of parted.​chmod 777 /sbin/parted​
8. It's time to use parted!​​We mainly use 3 commands. Here's how they work.​
rm x - Removes partition number x. For example: rm 13
Click to expand...
Click to collapse
mkpart name fstype startUNIT finishUNIT - Makes a partition where fstype is the type of filesystem (like ext4), start is the beginning of the partition, and finish is the end of the partition. UNIT is the unit for the start and finish arguments (like KB, MB, B, or s) For example: mkpart system_a ext4 32KB 1000KB
Click to expand...
Click to collapse
name x part_name - Names partition number x and gives it part_name as a label. For example: name 14 userdata
Click to expand...
Click to collapse
In your terminal (still in shell mode), type parted /dev/block/sda
It should greet you with a welcome screen. Type p free, and save what you get in a screenshot or text file (on windows you can copy and paste in notepad, or use Snipping Tool, since it's installed by default). THIS IS VERY IMPORTANT IF YOU GET STUCK!!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​
We have to delete all partitions starting from the bottom until system_b. Make sure to keep the screenshot or text file you saved earlier from p free, because we are gonna need it to recreate the deleted partitions later. YOUR PARTITION SCHEME MIGHT BE DIFFERENT THAN THIS. Make sure to STOP after system_b is removed.
rm 45
rm 44
rm 43
Once you are done, it's time to recreate those partitions. We do it in the proper order now, starting from system_b. Refer to the screenshot or text file you saved earlier. We will increase the partition size to 3GB to be able to boot most GSIs, including Android 12. If it says that the partition isn't aligned, type Ignore.
mkpart system_b ext2 4073MB 7173MB
mkpart padding1 7173MB 7179MB
mkpart userdata ext4 7179MB 62400MB (if you have 128GB Walleye, do mkpart userdata ext4 7179MB 126300MB)
Check your partitioning with p free and compare with your screenshot/text file. It should be similar, with some extra free spaces.
Time to name the partitions.
name 43 system_b
name 44 padding1
name 45 userdata
Check your partitioning again with p free. It should show the named partitions. If everything looks good to you, leave parted.
quit
9. Exit shell mode.
exit​
10. Reboot into fastboot mode
adb reboot bootloader​
11. Format all the partitions we made
fastboot erase system_b​fastboot erase padding1​fastboot erase userdata​fastboot format:ext2 system_b​fastboot format:ext4 userdata​​And that's all!
NOTICE: At this point, the partitions should repopulate themselves on the next boot. If they don't, flash latest Android 11 stock ROM (And flash it using flash-all.bat for windows/flash-all.sh for linux).
Flashing the stock ROM won't undo your partitioning. You will keep your 3GB system partition!
Click to expand...
Click to collapse
You can start immediately flashing GSIs/Android 12. If you're stuck on splash screen, that means the partitions didn't repopulate correctly. Follow the advice above!
If you have any questions, or accidentally brick your device, join the telegram group for direct support, or ask here in the XDA thread.

Thanks for your help on the Telegram group man. I just skipped Step 11 and did fastboot -w so I completed the process without any errors.

always type wrong,so crazy its code,