Develop Bugs

Convert to yakju questions

I have 2 questions now,
I saw this guide: http://forum.xda-developers.com/showthread.php?t=1626895
But I did understand it but isn't a guide with a Galaxy Nexus Root Toolkit? I saw that in this guide: http://webtrickz.com/guide-to-updat...oid-4-0-4-and-get-future-updates-from-google/
It looks like the same, only is this with a gui, so I won't type things wrong, would this be wrong to use?
And...
If I change to yakju and lock the bootloader ( I just want to have everything stock again after that ), can you see then anywhere if you changed to yakju? So if I send it in for warrenty they won't know it?

Marc. said:
I have 2 questions now,
I saw this guide: http://forum.xda-developers.com/showthread.php?t=1626895
But I did understand it but isn't a guide with a Galaxy Nexus Root Toolkit? I saw that in this guide: http://webtrickz.com/guide-to-updat...oid-4-0-4-and-get-future-updates-from-google/
It looks like the same, only is this with a gui, so I won't type things wrong, would this be wrong to use?
And...
If I change to yakju and lock the bootloader ( I just want to have everything stock again after that ), can you see then anywhere if you changed to yakju? So if I send it in for warrenty they won't know it?
Click to expand...
Click to collapse
1) use the first link you posted. dont use the toolkit. http://forum.xda-developers.com/showthread.php?t=1626895
2) no, they wont be able to really tell anything.

Zepius said:
1) use the first link you posted. dont use the toolkit. http://forum.xda-developers.com/showthread.php?t=1626895
2) no, they wont be able to really tell anything.
Click to expand...
Click to collapse
Why not use the toolkit? It looks much easier.
And do I have to do all the optional things also?
Then it would be this?
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept.
4) Reboot by typing: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system system.img
10) Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.
11) Flash the boot partition: fastboot flash boot boot.img
12) Optional (but recommended) -- Flash the recovery partition: fastboot flash recovery recovery.img
13) Erase the cache partition: fastboot erase cache
15) Reboot: fastboot reboot
16) Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the Dalvik cache.

Marc. said:
Why not use the toolkit? It looks much easier.
And do I have to do all the optional things also?
Then it would be this?
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept.
4) Reboot by typing: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system system.img
10) Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.
11) Flash the boot partition: fastboot flash boot boot.img
12) Optional (but recommended) -- Flash the recovery partition: fastboot flash recovery recovery.img
13) Erase the cache partition: fastboot erase cache
15) Reboot: fastboot reboot
16) Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the Dalvik cache.
Click to expand...
Click to collapse
if something happens in the middle of you doing it the way in the link i mentioned, its easier to figure out how to fix items when you're on a certain step.
the toolkit is easier, but if something messes up, its hard to tell where since you have no idea what it is doing
the only other step is once everything is booted back up on yakju and is working properly, go back to fastboot and relock the bootloader with fastboot oem lock

So you say these steps will be right?
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept.
4) Reboot by typing: fastboot reboot-bootloader
5) Flash the system partition: fastboot flash system system.img
6) Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.
7) Flash the boot partition: fastboot flash boot boot.img
8) Optional (but recommended) -- Flash the recovery partition: fastboot flash recovery recovery.img
9) Erase the cache partition: fastboot erase cache
10) Reboot: fastboot reboot
11) Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the Dalvik cache.
12) Lock bootloader again with: fastboot oem lock
And how could I see when its finished flashing for example system.img?
And this would work on doesn't matter what firmware you're on?

Marc. said:
I have 2 questions now,
I saw this guide: http://forum.xda-developers.com/showthread.php?t=1626895
But I did understand it but isn't a guide with a Galaxy Nexus Root Toolkit? I saw that in this guide: http://webtrickz.com/guide-to-updat...oid-4-0-4-and-get-future-updates-from-google/
It looks like the same, only is this with a gui, so I won't type things wrong, would this be wrong to use?
And...
If I change to yakju and lock the bootloader ( I just want to have everything stock again after that ), can you see then anywhere if you changed to yakju? So if I send it in for warrenty they won't know it?
Click to expand...
Click to collapse
Yes, if they check build.prop (unlikely that they will if you relock bootloader), they will be able to see the yakju fingerprint.
Marc. said:
So you say these steps will be right?
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept.
4) Reboot by typing: fastboot reboot-bootloader
5) Flash the system partition: fastboot flash system system.img
6) Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.
7) Flash the boot partition: fastboot flash boot boot.img
8) Optional (but recommended) -- Flash the recovery partition: fastboot flash recovery recovery.img
9) Erase the cache partition: fastboot erase cache
10) Reboot: fastboot reboot
11) Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the Dalvik cache.
12) Lock bootloader again with: fastboot oem lock
And how could I see when its finished flashing for example system.img?
And this would work on doesn't matter what firmware you're on?
Click to expand...
Click to collapse
Why don't you download yakju factory image from Google? It has a bash script that can flash everything for you, in the right order. If you edit flash-all.sh, you'll see the fastboot commands it runs. That's the order you need to run them.
Sent from my i9250

Flashing from MM to N system images via fastboot stuck at google logo

All,
I am not a noob by any means, but when I attempted to manually flash the img files via fastboot for the latest N build from the factory images coming from the last 6.0.1 build I get stuck on the Google logo. I checked the commands and re-flashed again and the same result happened ( i did flash radios and BL ) .
I even tried to format data ( i had backed everything up ) , still no go and stuck at google logo still. I could access BL and able to access TWRP.
I got frustrated and flashed the 6.0.1 images including BL and radio via fastboot and booted up just fine. I then rooted, installed flashfire and used the OTA and Android N installed just fine.
Does anyone have any idea what could be causing this. I am currently on N, but wanted to do a clean install .
Thanks in Advance

Did you flash vendor.img?
Why don't you list the exact commands you used to flash, then people can comment.

fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot flash recovery twrp-3.0.2-2-bullhead.img
fastboot reboot-bootloader
fastboot flash recovery twrp-3.0.2-2-bullhead.img
Flashing mtc20k works successfully
Using the same commands to flashing npf10c results in stuck the google logo
In order for me to even get on N I have to me on 6.0.1 then either use the bullhead-ota-npf10c-d1785fea.zip on the root of the SD card and use flashfire OR use the following command from stock recovery
adb sideload bullhead-ota-npf10c-d1785fea.zip
The later is what I did recently, but both will work to get to N.
So why can I not simply flash the factory images like for 6.0.1?

carm01 said:
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot flash recovery twrp-3.0.2-2-bullhead.img
fastboot reboot-bootloader
fastboot flash recovery twrp-3.0.2-2-bullhead.img
Flashing mtc20k works successfully
Using the same commands to flashing npf10c results in stuck the google logo
In order for me to even get on N I have to me on 6.0.1 then either use the bullhead-ota-npf10c-d1785fea.zip on the root of the SD card and use flashfire OR use the following command from stock recovery
adb sideload bullhead-ota-npf10c-d1785fea.zip
The later is what I did recently, but both will work to get to N.
So why can I not simply flash the factory images like for 6.0.1?
Click to expand...
Click to collapse
What happens when you flash a Nougat factory image that is NOT a developer preview? Try flashing NRD91N from here:
https://developers.google.com/android/images?hl=en
Sent from my Nexus 5X using Tapatalk

carm01 said:
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot flash recovery twrp-3.0.2-2-bullhead.img
fastboot reboot-bootloader
fastboot flash recovery twrp-3.0.2-2-bullhead.img
Flashing mtc20k works successfully
Using the same commands to flashing npf10c results in stuck the google logo
In order for me to even get on N I have to me on 6.0.1 then either use the bullhead-ota-npf10c-d1785fea.zip on the root of the SD card and use flashfire OR use the following command from stock recovery
adb sideload bullhead-ota-npf10c-d1785fea.zip
The later is what I did recently, but both will work to get to N.
So why can I not simply flash the factory images like for 6.0.1?
Click to expand...
Click to collapse
I don't usually flash cache or user.
Try this instead and see if it works.
Instead of flashing cache.img
fastboot erase cache
fastboot format cache
(if you want to reset user)
fastboot erase userdata
fastboot format userdata

sfhub said:
I don't usually flash cache or user.
Try this instead and see if it works.
Instead of flashing cache.img
fastboot erase cache
fastboot format cache
(if you want to reset user)
fastboot erase userdata
fastboot format userdata
Click to expand...
Click to collapse
SlimSnoopOS said:
What happens when you flash a Nougat factory image that is NOT a developer preview? Try flashing NRD91N from here:
https://developers.google.com/android/images?hl=en
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I have tried fastboot erase userdata and fastboot format userdata and fastboot erase cache
fastboot format cache and that never worked.
I tried that factory image before and resulted in the same, however, I will at sometime attempt to do the final of 7.1.1 once it is available sometime in December 2016 and hopefully will resolve the issue.
I will stay on DP1 right now as i find the battery extremely excellent, the Visual VM is back now, and i notice some notifications are coming through better than in 7.0. (I read an article earlier today about notifications and the pixel not coming through)
Thanks in Advance for the people that did come through so far and wanted to thank you for your input on the matter and if i don't have a pixel by December I will try this out.

Pixel XL Bootloop

Hello Everyone,
My Pixel XL is going in bootloop after working for sometime. I have to factory reset it via recovery to get it working again. I am attching log which i got via ADB when it boot up. Can somebody help me with that?
No root no unlocked bootloader.

rkravi85 said:
Hello Everyone,
My Pixel XL is going in bootloop after working for sometime. I have to factory reset it via recovery to get it working again. I am attching log which i got via ADB when it boot up. Can somebody help me with that?
No root no unlocked bootloader.
Click to expand...
Click to collapse
No log

Sorry My Bad @Homeboy76

Have you tried these steps below?
If you have modified a little the stock android (hosts file, root, kernel, etc.), you may experience a fail in OTA update;
If you have a bootloop/soft brick/not sure of the state of your android system;
This WILL NOT delete your data and apps. This will remove your custom kernel/root/hosts/recovery through (which is a good thing because it will be clean then).
1) Download your system image for Marlin (Pixel XL) on google website.
download the latest version
2) Unzip the file marlin-nde63v-factory-______.zip
3) Unzip inside the new directory (marlin-nde63v) the image-marlin-_____.zip
Execute fastboot commands (assuming the bin is on your PATH)
Code:
fastboot reboot-bootloader
fastboot flash radio radio-marlin-*.img
fastboot reboot-bootloader
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system system.img
fastboot flash system_b system_other.img
fastboot flash vendor vendor.img
fastboot flash modem modem.img
fastboot reboot
to add TWRP;
fastboot boot /path/to/twrp.img
then In TWRP, install twrp.zip for permanent twrp. Goodluck!

Phone now boot into fastboot but not system

Hi
I was trying to install Lineage OS on my device, but I failed, now the phone does not have TWRP anymore, and when I power up, it goes into fast boot only.
I have done quite a lot of work to save my phone, and the last thing that I did was download the stock fastboot rom and run flash_all.bat from it.
(I can not get the Miflash tool working on my PC because when I startup the program, it asks me to download 5 drivers, but it failed to download and throw me an error)

luckyvictor said:
Hi
I was trying to install Lineage OS on my device, but I failed, now the phone does not have TWRP anymore, and when I power up, it goes into fast boot only.
I have done quite a lot of work to save my phone, and the last thing that I did was download the stock fastboot rom and run flash_all.bat from it.
(I can not get the Miflash tool working on my PC because when I startup the program, it asks me to download 5 drivers, but it failed to download and throw me an error)
Click to expand...
Click to collapse
First of all - if your phone boots to fastboot, there seems to be a problem with your bootloader or kernel.
To fix that, you need to reflash aboot.img and boot.img via fastboot.
Boot.img depends on the version, you want to install. Copy both files into your fastboot folder and
Code:
fastboot flash boot_a boot.img
Code:
fastboot flash boot_b boot.img
Code:
fastboot flash aboot_a aboot.img
Code:
fastboot flash aboot_b aboot.img
Now your phone shouldn´t stuck @ fastboot anymore.
Ok, to save your data, you could try to boot twrp:
Code:
fastboot boot twrp.img
If you´re lucky, it can decrypt your data - then you can backup data and internal storage...
If it´s not able to decrypt, you need to install twrp.
To install a fastboot rom without miflash look here
I suggest you to install caf-kernel via twrp. Sometimes your phone boots up with it - magic

Voodoojonny said:
First of all - if your phone boots to fastboot, there seems to be a problem with your bootloader or kernel.
To fix that, you need to reflash aboot.img and boot.img via fastboot.
Boot.img depends on the version, you want to install. Copy both files into your fastboot folder and
Code:
fastboot flash boot_a boot.img
Code:
fastboot flash boot_b boot.img
Code:
fastboot flash aboot_a aboot.img
Code:
fastboot flash aboot_b aboot.img
Now your phone shouldn´t stuck @ fastboot anymore.
Ok, to save your data, you could try to boot twrp:
Code:
fastboot boot twrp.img
If you´re lucky, it can decrypt your data - then you can backup data and internal storage...
If it´s not able to decrypt, you need to install twrp.
To install a fastboot rom without miflash look here
I suggest you to install caf-kernel via twrp. Sometimes your phone boots up with it - magic
Click to expand...
Click to collapse
Thanks, will give it a try.
Just for my knowledge, what are these boot_a and boot_b please? they relate to the two sim slot in this device?

luckyvictor said:
Thanks, will give it a try.
Just for my knowledge, what are these boot_a and boot_b please? they relate to the two sim slot in this device?
Click to expand...
Click to collapse
Boot.img from fastboot rom... To be flashed in partition boot_a and boot_b. Our device is a AB-device. That means all partitions are doubled (except of data). If your system breaks, you can switch to the other slot by "fastboot set_active a" or b if you are on a.... Btw perhaps that fixes your phone too! Boot twrp and you can see which slot is active (under reboot)

Flash GSI in Realme 3/3i Android 10 (Updated 13-Jan-2021)

Follow bellow steps (carefully) for flashing GSI in realme 3/3i on Android 10, we have only tested few GSIs Like CherishOS, LineageOS, HavocOS etc.
All GSIs have different methods to flash kn Realme 3/3i.
Provided method have tested on CherishOS (GSI Snaps are below)
What you need to flash GSI:
Platform tool (Bootloader should be unlock)
LineageOS 17.1.zip
https://bit.ly/oOo17o1rm1821Orangefox recovery.img
28.81 MB file on MEGA
bit.ly
Boot.img (do not try any other boot.img)
File on MEGA
bit.ly
Dmverity zip file
3.25 MB file on MEGA
bit.ly
GSI image (system.img)
We are flashing CherishOS this time.
https://bit.ly/CherishGSIrmx1821
Steps to Flash:
Copy LineageOS 17.1 and Dmverifyzip file into SD Card.
Flash orangefox
Commands:
fastboot flash recovery xxx.img (xxx is recovery name)
fastboot -w
fastboot reboot recovery
In OrangeFox Recovery
Goto format data and type yes
Now goto wipe, Wipe everything except SD Card and swipe
Now goto files>SD Card and flash LineageOS 17.1 zip file
After flashing done simply reboot to system (no need to wipe cache)
Your phone will boot in lineageos, in lineage OS 17.1 Goto Developer options and enable "Advance Restart" now press power button and click on reboot> recovery, your phone will reboot into recovery. Now goto files and flash Dmverityzip file and after flashing done goto reboot > bootloader (no need to wipe cache).
Once you rebooted into bootloader (fastboot mode) type below commands.
"fastboot --disable-verity --disable-verification flash boot boot.img"
(note this should be the same boot file which i have share in this thread)
"fastboot erase system"
"fastboot flash system xxx.img"
(xxx is cherishOS.img, wait for flashing completion)
"fastboot -w"
"fastboot erase para"
"fastboot reboot"
(Wait atleast 5-10 minites your phone will be in realme logo state, do not panic)
The End.
Special Thanks To Ujjwal for Flashing.
Feel Free to Join https://t.me/joinchat/WM3heLvnFTYXzeOb

azharmansoori said:
Follow bellow steps (carefully) for flashing GSI in realme 3/3i on Android 10, we have only tested few GSIs Like CherishOS, LineageOS, HavocOS etc.
All GSIs have different methods to flash kn Realme 3/3i.
Provided method have tested on CherishOS (GSI Snaps are below)
What you need to flash GSI:
Platform tool (Bootloader should be unlock)
LineageOS 17.1.zip
https://bit.ly/oOo17o1rm1821Orangefox recovery.img
28.81 MB file on MEGA
bit.ly
Boot.img (do not try any other boot.img)
File on MEGA
bit.ly
Dmverity zip file
3.25 MB file on MEGA
bit.ly
GSI image (system.img)
We are flashing CherishOS this time.
https://bit.ly/CherishGSIrmx1821
Steps to Flash:
Copy LineageOS 17.1 and Dmverifyzip file into SD Card.
Flash orangefox
Commands:
fastboot flash recovery xxx.img (xxx is recovery name)
fastboot -w
fastboot reboot recovery
In OrangeFox Recovery
Goto format data and type yes
Now goto wipe, Wipe everything except SD Card and swipe
Now goto files>SD Card and flash LineageOS 17.1 zip file
After flashing done simply reboot to system (no need to wipe cache)
Your phone will boot in lineageos, in lineage OS 17.1 Goto Developer options and enable "Advance Restart" now press power button and click on reboot> recovery, your phone will reboot into recovery. Now goto files and flash Dmverityzip file and after flashing done goto reboot > bootloader (no need to wipe cache).
Once you rebooted into bootloader (fastboot mode) type below commands.
"fastboot --disable-verity --disable-verification flash boot boot.img"
(note this should be the same boot file which i have share in this thread)
"fastboot erase system"
"fastboot flash system xxx.img"
(xxx is cherishOS.img, wait for flashing completion)
"fastboot -w"
"fastboot erase para"
"fastboot reboot"
(Wait atleast 5-10 minites your phone will be in realme logo state, do not panic)
The End.
Special Thanks To Ujjwal for Flashing.
Feel Free to Join https://t.me/joinchat/WM3heLvnFTYXzeOb
Click to expand...
Click to collapse
After booting to LineageOS 17.1, and flashing the DM verity disabler, Can i flash the unmodified Android 11 GSI system.img instead of CherishOS.img? Is it going to work?

ATDteam said:
After booting to LineageOS 17.1, and flashing the DM verity disabler, Can i flash the unmodified Android 11 GSI system.img instead of CherishOS.img? Is it going to work?
Click to expand...
Click to collapse
Yes, unmodified GSI will work. Just follow our process from "fastboot --disable-verity --disable-verification etc etc"

azharmansoori said:
Yes, unmodified GSI will work. Just follow our process from "fastboot --disable-verity --disable-verification etc etc"
Click to expand...
Click to collapse
Thank you i will do it when i recover my Realme 3 from being dead. i hard bricked my phone, No Fastboot, No Charge, No Recovery no sign of life in screen, can you suggest how can i fix this? or do you ever encounter this?

ATDteam said:
Thank you i will do it when i recover my Realme 3 from being dead. i hard bricked my phone, No Fastboot, No Charge, No Recovery no sign of life in screen, can you suggest how can i fix this? or do you ever encounter this?
Click to expand...
Click to collapse
There is only option to go to Service Center.

azharmansoori said:
There is only option to go to Service Center.
Click to expand...
Click to collapse
oh i see. however i manage to Extract the OFP firmware of realme 3 with auth_file, scatter file and all the img(s), the only problem is the Download-Agent File, there is a DA file thing error when flashing using SP Flash Tool. By the way thanks a lot.

ATDteam said:
oh i see. however i manage to Extract the OFP firmware of realme 3 with auth_file, scatter file and all the img(s), the only problem is the Download-Agent File, there is a DA file thing error when flashing using SP Flash Tool. By the way thanks a lot.
Click to expand...
Click to collapse
Please see other thread, which is in Guides of Realme 3 for (how to unbrick realme 3, do follow his process and like his post if you successfully unubrick).

azharmansoori said:
Please see other thread, which is in Guides of Realme 3 for (how to unbrick realme 3, do follow his process and like his post if you successfully unubrick).
Click to expand...
Click to collapse
yah i figure it out, im the one who posted the Unbrick Tutorial. Thanks.

ATDteam said:
yah i figure it out, im the one who posted the Unbrick Tutorial. Thanks.
Click to expand...
Click to collapse
Pleasure, would you please contact me at t.me/azharmansoori22 as i am facing issue in your bat file.

azharmansoori said:
Follow bellow steps (carefully) for flashing GSI in realme 3/3i on Android 10, we have only tested few GSIs Like CherishOS, LineageOS, HavocOS etc.
All GSIs have different methods to flash kn Realme 3/3i.
Provided method have tested on CherishOS (GSI Snaps are below)
What you need to flash GSI:
Platform tool (Bootloader should be unlock)
LineageOS 17.1.zip
https://bit.ly/oOo17o1rm1821Orangefox recovery.img
28.81 MB file on MEGA
bit.ly
Boot.img (do not try any other boot.img)
File on MEGA
bit.ly
Dmverity zip file
3.25 MB file on MEGA
bit.ly
GSI image (system.img)
We are flashing CherishOS this time.
https://bit.ly/CherishGSIrmx1821
Steps to Flash:
Copy LineageOS 17.1 and Dmverifyzip file into SD Card.
Flash orangefox
Commands:
fastboot flash recovery xxx.img (xxx is recovery name)
fastboot -w
fastboot reboot recovery
In OrangeFox Recovery
Goto format data and type yes
Now goto wipe, Wipe everything except SD Card and swipe
Now goto files>SD Card and flash LineageOS 17.1 zip file
After flashing done simply reboot to system (no need to wipe cache)
Your phone will boot in lineageos, in lineage OS 17.1 Goto Developer options and enable "Advance Restart" now press power button and click on reboot> recovery, your phone will reboot into recovery. Now goto files and flash Dmverityzip file and after flashing done goto reboot > bootloader (no need to wipe cache).
Once you rebooted into bootloader (fastboot mode) type below commands.
"fastboot --disable-verity --disable-verification flash boot boot.img"
(note this should be the same boot file which i have share in this thread)
"fastboot erase system"
"fastboot flash system xxx.img"
(xxx is cherishOS.img, wait for flashing completion)
"fastboot -w"
"fastboot erase para"
"fastboot reboot"
(Wait atleast 5-10 minites your phone will be in realme logo state, do not panic)
The End.
Special Thanks To Ujjwal for Flashing.
Feel Free to Join https://t.me/joinchat/WM3heLvnFTYXzeOb
Click to expand...
Click to collapse
azharmansoori said:
Follow bellow steps (carefully) for flashing GSI in realme 3/3i on Android 10, we have only tested few GSIs Like CherishOS, LineageOS, HavocOS etc.
All GSIs have different methods to flash kn Realme 3/3i.
Provided method have tested on CherishOS (GSI Snaps are below)
What you need to flash GSI:
Platform tool (Bootloader should be unlock)
LineageOS 17.1.zip
https://bit.ly/oOo17o1rm1821Orangefox recovery.img
28.81 MB file on MEGA
bit.ly
Boot.img (do not try any other boot.img)
File on MEGA
bit.ly
Dmverity zip file
3.25 MB file on MEGA
bit.ly
GSI image (system.img)
We are flashing CherishOS this time.
https://bit.ly/CherishGSIrmx1821
Steps to Flash:
Copy LineageOS 17.1 and Dmverifyzip file into SD Card.
Flash orangefox
Commands:
fastboot flash recovery xxx.img (xxx is recovery name)
fastboot -w
fastboot reboot recovery
In OrangeFox Recovery
Goto format data and type yes
Now goto wipe, Wipe everything except SD Card and swipe
Now goto files>SD Card and flash LineageOS 17.1 zip file
After flashing done simply reboot to system (no need to wipe cache)
Your phone will boot in lineageos, in lineage OS 17.1 Goto Developer options and enable "Advance Restart" now press power button and click on reboot> recovery, your phone will reboot into recovery. Now goto files and flash Dmverityzip file and after flashing done goto reboot > bootloader (no need to wipe cache).
Once you rebooted into bootloader (fastboot mode) type below commands.
"fastboot --disable-verity --disable-verification flash boot boot.img"
(note this should be the same boot file which i have share in this thread)
"fastboot erase system"
"fastboot flash system xxx.img"
(xxx is cherishOS.img, wait for flashing completion)
"fastboot -w"
"fastboot erase para"
"fastboot reboot"
(Wait atleast 5-10 minites your phone will be in realme logo state, do not panic)
The End.
Special Thanks To Ujjwal for Flashing.
Feel Free to Join https://t.me/joinchat/WM3heLvnFTYXzeOb
Click to expand...
Click to collapse
Can I do this on Lineage os 18.1 using its boot.img for fastboot -disable...., can flash any A11 gsi, and what about gapps, you, you haven't flashed any gapps.

ritukanta said:
Can I do this on Lineage os 18.1 using its boot.img for fastboot -disable...., can flash any A11 gsi, and what about gapps, you, you haven't flashed any gapps.
Click to expand...
Click to collapse
Yes you can flash LineageOS boot.img on Android 11 GSIs.

Amd what for custom rom users, I'm using a11 ppui, what changes will be added, and can I do it with only orfox??

RIVEEKS said:
Amd what for custom rom users, I'm using a11 ppui, what changes will be added, and can I do it with only orfox??
Click to expand...
Click to collapse
No you can do with other suppoted recoveries like SHRP, PBRP (Official) etc.