Develop Bugs

Phone Decryption - Need Help

After installing of Paranoid /AOSPA 6.0.2 ROM I got message saying "To start Android, Enter your password" that mean my phone has been encrypted by itself, I did factory reset and still getting the same, Can you please help me !?

gotta flash a non-encrypting boot.img usually coming in the form of SuperSU systemless or custom kernel or there's some other OP3 specific solutions floating around here somewhere.
After that format /data in twrp. (format, not wipe.)

Boot in fastboot mode and use the command "fastboot format userdata". This will decrypt the device but also erase all data except system partition.

1.Properly Install ADB & Fastboot drivers for One Plus 3
2.Download Minimal ADB & fastboot http://forum.xda-developers.com/showthread.php?t=2317790
3.Boot into FASTBOOT mode [Power + Volume UP]
4.Connect Device via USB
5.Open CMD promt On Minimal ADB & FASTBOOT folder (Installed Folder)
6.Check Connection
Code:
fastboot devices
(If Returning response, Then Device is Connected)
7.Run The Following Command.
Code:
fastboot format userdata
6.Reboot device
Code:
fastboot reboot
NOTE: This will Erase all User data (Installed apps, games etc.)
NOTE: Check Encryption status in Settings > Security > Encrypt Phone [If Showing "Encrypt Phone" button at bottom, Then device is decrypted successfully]

Unable to boot into ROM after flashing

Hey guys! Need some help.
I've been trying to flash a Android Pie ROM on my device and I have no success.
The problem is, after flashing the rom and TWRP Zip the device reboots twice then boots back into TWRP.
Then all the files on the device has random letters and numbers (i.e. ckjrdh574o0hmdu749y7nv)
Why can't I flash a Android Pie rom successfully?
I am on the latest Android Pie update. (Flashed on both slots)
Here is my steps:
Flash stock rom on both slots
Boot up in stock rom. (no set up, no password, no pin, nothing totally skipped setup)
Place files on device (Rom and twrp.zip)
Reboot into Bootloader
Boot into latest TWRP using fastboot
Once in Twrp, slide slider to allow modification to system parition
Factory reset/wipe data (and all that)
Flash rom (I tried Carbon Rom 7 and lineage os 16)
Flashed twrp zip
reboot
After the system reboots twice I am back in twrp and all the files and folder have numbers and letters as files names.
Any idea as to why this keeps happening?
How can I fix this?

MichaelDrakeMS said:
Hey guys! Need some help.
I've been trying to flash a Android Pie ROM on my device and I have no success.
The problem is, after flashing the rom and TWRP Zip the device reboots twice then boots back into TWRP.
Then all the files on the device has random letters and numbers (i.e. ckjrdh574o0hmdu749y7nv)
Why can't I flash a Android Pie rom successfully?
I am on the latest Android Pie update. (Flashed on both slots)
Here is my steps:
Flash stock rom on both slots
Boot up in stock rom. (no set up, no password, no pin, nothing totally skipped setup)
Place files on device (Rom and twrp.zip)
Reboot into Bootloader
Boot into latest TWRP using fastboot
Once in Twrp, slide slider to allow modification to system parition
Factory reset/wipe data (and all that)
Flash rom (I tried Carbon Rom 7 and lineage os 16)
Flashed twrp zip
reboot
After the system reboots twice I am back in twrp and all the files and folder have numbers and letters as files names.
Any idea as to why this keeps happening?
How can I fix this?
Click to expand...
Click to collapse
Flash stock
finish setup
before doing anything else

MichaelDrakeMS said:
Hey guys! Need some help.
I've been trying to flash a Android Pie ROM on my device and I have no success.
The problem is, after flashing the rom and TWRP Zip the device reboots twice then boots back into TWRP.
Then all the files on the device has random letters and numbers (i.e. ckjrdh574o0hmdu749y7nv)
Why can't I flash a Android Pie rom successfully?
I am on the latest Android Pie update. (Flashed on both slots)
Here is my steps:
Flash stock rom on both slots
Boot up in stock rom. (no set up, no password, no pin, nothing totally skipped setup)
Place files on device (Rom and twrp.zip)
Reboot into Bootloader
Boot into latest TWRP using fastboot
Once in Twrp, slide slider to allow modification to system parition
Factory reset/wipe data (and all that)
Flash rom (I tried Carbon Rom 7 and lineage os 16)
Flashed twrp zip
reboot
After the system reboots twice I am back in twrp and all the files and folder have numbers and letters as files names.
Any idea as to why this keeps happening?
How can I fix this?
Click to expand...
Click to collapse
Not sure if Carbon / Lineage has special install instructions or not, but you can follow the initial 9x setup in the link in my sig, then follow cust Rom installation process.

parakleet said:
Flash stock
finish setup
before doing anything else
Click to expand...
Click to collapse
Yup I did. I just didn't sign in my account or do the security pin/pixel imprint. I skipped everything untill I was at the home/launcher.

Az Biker said:
Not sure if Carbon / Lineage has special install instructions or not, but you can follow the initial 9x setup in the link in my sig, then follow cust Rom installation process.
Click to expand...
Click to collapse
Nothing to special from the norm. I didn't everything the forums told me to do.
Okay definitely, I'll check that out and try those steps.
Also do you think I have a phone that twrp can't decrypt? I remember a while back doing one of the twrp updates that some phones won't decrypt because it used the older encryption method or something like that and TWRP was only able to decrypt then phones using the new method or something like that.

Oh and another question, do you guys think I should root the stock image with magisk then boot into twrp using fastboot and install the room then the twrp.zip?

My question would be do you have other details you might have overlooked? For example, at the end of flashing, TWRP would usually ask whether you want to install their app. Did you install it or did you skip it?
Also, what was your exact procedure in flashing stock rom to both slots? I have also messed around with custom roms and reverted back to stock using the following:
Return to Stock:
Source of this knowledge is Method 2 of this video.
#flashing bootloader to slot A and slot B
Code:
fastboot reboot-bootloader
fastboot flash bootloader_a bootloader[...].img
fastboot reboot-bootloader
fastboot flash bootloader_b bootloader[...].img
#flashing radio to slot A and slot B
Code:
fastboot reboot-bootloader
fastboot flash radio_a radio[...].img
fastboot reboot-bootloader
fastboot flash radio_b radio[...].img
#set active slot to B, flash system image
Code:
fastboot --set-active=b
fastboot reboot-bootloader
fastboot --skip-reboot --skip-secondary update image[...].zip
#set active slot to A, flash system image [different command!!!]
Code:
fastboot --set-active=a
fastboot reboot-bootloader
fastboot --skip-reboot update image[...].zip
Now straight from the bootloader, boot into recovery.
Wipe data/factory reset.
Let it reboot back into android.
Then, I followed the install instructions in the twrp thread to get custom recovery back onto my device. (If you want rooted stock android, flash it from twrp and then install the latest magisk manager apk.)
Now just find another custom rom and follow the install directions from that thread.

amartolos said:
My question would be do you have other details you might have overlooked? For example, at the end of flashing, TWRP would usually ask whether you want to install their app. Did you install it or did you skip it?
Also, what was your exact procedure in flashing stock rom to both slots? I have also messed around with custom roms and reverted back to stock using the following:
Return to Stock:
Source of this knowledge is Method 2 of this video.
#flashing bootloader to slot A and slot B
Code:
fastboot reboot-bootloader
fastboot flash bootloader_a bootloader[...].img
fastboot reboot-bootloader
fastboot flash bootloader_b bootloader[...].img
#flashing radio to slot A and slot B
Code:
fastboot reboot-bootloader
fastboot flash radio_a radio[...].img
fastboot reboot-bootloader
fastboot flash radio_b radio[...].img
#set active slot to B, flash system image
Code:
fastboot --set-active=b
fastboot reboot-bootloader
fastboot --skip-reboot --skip-secondary update image[...].zip
#set active slot to A, flash system image [different command!!!]
Code:
fastboot --set-active=a
fastboot reboot-bootloader
fastboot --skip-reboot update image[...].zip
Now straight from the bootloader, boot into recovery.
Wipe data/factory reset.
Let it reboot back into android.
Then, I followed the install instructions in the twrp thread to get custom recovery back onto my device. (If you want rooted stock android, flash it from twrp and then install the latest magisk manager apk.)
Now just find another custom rom and follow the install directions from that thread.
Click to expand...
Click to collapse
Now that's all the steps j took to flash the roms.
I do not install twrp app I skip that.
My first methond to flash stock on both slots is set slot to a then flash stock using the flash all bat file in from the stock images (google directions to flashing images)
Then it would reboot. Then I would set to slot b and flash the stock images the same way using the bat file.
Then I found out that wasn't really the best way to do it so I used deuces (I believe that was the users name) bat file to flash the stock images on both slots the correct way and that's what I've been doing since.
But your steps have a different step then what I do. It seems it does the same as deuces bat file however once it's done I just boot straight into stock rom. I dont boot into stock recovery and factory wipe. But I will definitely try that as well.

Finally fixed it!
I flash both slots and followed everyone's directions.
The problem was I wasn't wiping all the things I needed too.
I read in another roms steps to not only do the factory reset thin in TWRP, but to also manually wipe system, data, dalvik/art cache. Then flashed the room and TWRP.zip.
I did this and BOOM, I booted up into the room! Thanks again for everyone's help!

amartolos said:
My question would be do you have other details you might have overlooked? For example, at the end of flashing, TWRP would usually ask whether you want to install their app. Did you install it or did you skip it?
Also, what was your exact procedure in flashing stock rom to both slots? I have also messed around with custom roms and reverted back to stock using the following:
Return to Stock:
Source of this knowledge is Method 2 of this video.
#flashing bootloader to slot A and slot B
Code:
fastboot reboot-bootloader
fastboot flash bootloader_a bootloader[...].img
fastboot reboot-bootloader
fastboot flash bootloader_b bootloader[...].img
#flashing radio to slot A and slot B
Code:
fastboot reboot-bootloader
fastboot flash radio_a radio[...].img
fastboot reboot-bootloader
fastboot flash radio_b radio[...].img
#set active slot to B, flash system image
Code:
fastboot --set-active=b
fastboot reboot-bootloader
fastboot --skip-reboot --skip-secondary update image[...].zip
#set active slot to A, flash system image [different command!!!]
Code:
fastboot --set-active=a
fastboot reboot-bootloader
fastboot --skip-reboot update image[...].zip
Now straight from the bootloader, boot into recovery.
Wipe data/factory reset.
Let it reboot back into android.
Then, I followed the install instructions in the twrp thread to get custom recovery back onto my device. (If you want rooted stock android, flash it from twrp and then install the latest magisk manager apk.)
Now just find another custom rom and follow the install directions from that thread.
Click to expand...
Click to collapse
I stumbled across this post after having several issues trying to get my Pixel 2 XL flashed with a custom ROM (constantly resulting in boot-loops), and the steps worked perfectly.
I've ended up running these steps several times today, but I like keeping all of my stock images in sub-folders by release date. I'm not the greatest Powershell guru, but I've written a script that will search sub-directories in a folder for dates, and select the latest date and automatically flash the radio, bootloader, and image from that directory using your steps.
Code:
clear;
# Execution Policy must be adjusted in order to obtain the current executing directory of the script. This is a one-time command that must be run separately.
# Set-ExecutionPolicy RemoteSigned
# To reverse the command set the execution policy to restricted:
# Set-ExecutionPolicy Restricted
# The root directory which contains date sub-folders in the format yyyy-MM-dd representing an extracted OTA zip.
$startingDirectory = split-path -parent $MyInvocation.MyCommand.Definition;
# Alternatively, hard code a starting directory.
# [System.String]$startingDirectory = 'D:\Flashing\Roms\Taimen\Stock\';
[System.String]$targetFolder = (Get-ChildItem $startingDirectory | Select-Object -Property @{Name='Date';Expression = { Get-Date $_.Name -Format 'yyyy-MM-dd' }}, @{Name='FullName';Expression= {$_.FullName}} | Sort Date -Descending | Select -First 1).FullName;
if (-not $targetFolder) {
throw 'No folders are located in directory ''' + $startingDirectory + ''' with the date format yyyy-MM-dd.';
}
[System.String]$bootloader = Get-ChildItem $targetFolder -Name 'bootloader-*.img';
[System.String]$radio = Get-ChildItem $targetFolder -Name 'radio-*.img';
[System.String]$image = Get-ChildItem $targetFolder -Name 'image-*.zip';
# Validate all files have been successfully located.
[System.Collections.Generic.List[System.String]]$messages = [System.Collections.Generic.List[System.String]]::new();
if (-not $bootloader) {
$messages.Add('The bootloader file was not located.');
}
if (-not $radio) {
$messages.Add('The radio file was not located.');
}
if (-not $image) {
$messages.Add('The image file was not located.');
}
if ($messages.Length -gt 0) {
throw 'Unable to locate files in path ''' + $targetFolder + ''':' + [Environment]::NewLine + [System.String]::Join([Environment]::NewLine, $messages);
}
$bootloader = [System.IO.Path]::Combine($targetFolder, $bootloader);
$bootloader;
$radio = [System.IO.Path]::Combine($targetFolder, $radio);
$radio;
$image = [System.IO.Path]::Combine($targetFolder, $image);
$image;
#adb reboot bootloader;
function Reboot-Bootloader {
fastboot reboot-bootloader;
sleep 5;
}
#flashing bootloader to slot A and slot B
'Flashing bootloader to slot A.'
Reboot-Bootloader;
fastboot flash bootloader_a $bootloader;
'Flashing bootloader to slot B.'
Reboot-Bootloader;
fastboot flash bootloader_b $bootloader;
#flashing radio to slot A and slot B
'Flashing radio to slot A.'
Reboot-Bootloader;
fastboot flash radio_a $radio;
'Flashing radio to slot B.'
Reboot-Bootloader;
fastboot flash radio_b $radio;
#set active slot to B, flash system image
'Flashing system image to slot B.'
fastboot --set-active=b;
Reboot-Bootloader;
fastboot --skip-reboot --skip-secondary update $image;
#set active slot to A, flash system image [different command!!!]
'Flashing system image to slot A.'
fastboot --set-active=a;
Reboot-Bootloader;
fastboot --skip-reboot update $image;

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.

Trying to install latest TWRP on Moto G5 gives error (bootloader) Image size exeeded partition limits

Hi
I decided to try installing Lineage OS on a moto G5. I used this guide on the lineage OS website: https://wiki.lineageos.org/devices/cedric/install
That guide pointed me to the TWRP downloads page where I downloaded the latest version, which is currently:
twrp-3.5.2_9-0-cedric.img17.1M 2021-04-05 15:20:14 EDT
I downloaded this, renamed it to "twrp.img", put it in the same folder as my adb tools, then ran the command: "fastboot flash recovery twrp.img"
It gave me the following output in the command prompt:
"(bootloader) has-slot:recovery: not found
(bootloader) is-logical:recovery: not found
Sending 'recovery' (17536 KB) OKAY [ 0.562s]
Writing 'recovery' (bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed"
I googled this and found a few people mentioning this problem on other devices, but couldn't find a solution. Out of curiosity, I downloaded an older version of TWRP which has a smaller file size. I managed to flash that recovery so I thought I had cracked the problem!.. but since I was using an older version of TWRP it meant that actually flashing the Lineage ROM didn't work. As I understand it, the latest Lineage Rom will only work with latest TWRP.
Does anyone know what the problem is?
I managed to do everything else fine, aka I unlocked the bootloader using code from Motorola website.
I will need to sort something out because in trying to fix this I followed a guide which had me wipe everything and now the phone has no OS at all!
Is this a problem with TWRP's file size being too big now for this old phone's recovery partition? Or am I just being stupid?

trickyDicky314 said:
Hi
I decided to try installing Lineage OS on a moto G5. I used this guide on the lineage OS website: https://wiki.lineageos.org/devices/cedric/install
That guide pointed me to the TWRP downloads page where I downloaded the latest version, which is currently:
twrp-3.5.2_9-0-cedric.img17.1M 2021-04-05 15:20:14 EDT
I downloaded this, renamed it to "twrp.img", put it in the same folder as my adb tools, then ran the command: "fastboot flash recovery twrp.img"
It gave me the following output in the command prompt:
"(bootloader) has-slot:recovery: not found
(bootloader) is-logical:recovery: not found
Sending 'recovery' (17536 KB) OKAY [ 0.562s]
Writing 'recovery' (bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed"
I googled this and found a few people mentioning this problem on other devices, but couldn't find a solution. Out of curiosity, I downloaded an older version of TWRP which has a smaller file size. I managed to flash that recovery so I thought I had cracked the problem!.. but since I was using an older version of TWRP it meant that actually flashing the Lineage ROM didn't work. As I understand it, the latest Lineage Rom will only work with latest TWRP.
Does anyone know what the problem is?
I managed to do everything else fine, aka I unlocked the bootloader using code from Motorola website.
I will need to sort something out because in trying to fix this I followed a guide which had me wipe everything and now the phone has no OS at all!
Is this a problem with TWRP's file size being too big now for this old phone's recovery partition? Or am I just being stupid?
Click to expand...
Click to collapse
Note later 64bit twrp version for some reason exceed partition size. If you require a permanently installed TWRP use an old version.
To use the later versions of TWRP you need to boot to TWRP instead each time you want to use it.
Click to expand...
Click to collapse
see
[Official] [5th April 2021] TWRP 3.5.2_9-0 Moto G5 [Cedric] [32/64bit Roms]
Official TWRP For Moto G5 Cedric Post 1 - Instructions Post 2 - FAQs For full details and notes see Official TWRP for Cedric Site For TWRP news change logs etc see TWRP Official Site Instructions For non rooted and rooted phones...
forum.xda-developers.com

As clearly stated on my twrp thread. To use newer versions you have to temp boot to twrp
Or use an older version if you want a permanently installed twrp
twrp-3.5.0_9-0 I think is the latest version you can flash rather than only being able to boot.

sd_shadow said:
see
[Official] [5th April 2021] TWRP 3.5.2_9-0 Moto G5 [Cedric] [32/64bit Roms]
Official TWRP For Moto G5 Cedric Post 1 - Instructions Post 2 - FAQs For full details and notes see Official TWRP for Cedric Site For TWRP news change logs etc see TWRP Official Site Instructions For non rooted and rooted phones...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you for fast reply! I will try just booting new version and installing. I didn't realize that would work, I thought u needed TWRP permanently installed for it to work, (am not experienced with this stuff).
Thanks again!

TheFixItMan said:
As clearly stated on my twrp thread. To use newer versions you have to temp boot to twrp
Or use an older version if you want a permanently installed twrp
twrp-3.5.0_9-0 I think is the latest version you can flash rather than only being able to boot.
Click to expand...
Click to collapse
Thanks for the reply! I hadn't seen that thread. I will try flashing lineage with temp booted TWRP. I don't need it permanently installed, I just thought it was a requirement.

trickyDicky314 said:
Thanks for the reply! I hadn't seen that thread. I will try flashing lineage with temp booted TWRP. I don't need it permanently installed, I just thought it was a requirement.
Click to expand...
Click to collapse
Most builds of Lineage Rom include the lineage recovery anyways.
So when you install the rom it will also install their recovery.

sd_shadow said:
Most builds of Lineage Rom include the lineage recovery anyways.
So when you install the rom it will also install their recovery.
Click to expand...
Click to collapse
I booted into TWRP and tried to install lineage 17.1 via adb sideload. It seemed to get stuck at 38%. I had a look through the instructions again on lineage website and noticed a warning " Before following these instructions please ensure that the device is on the latest Android 8.1 firmware."
Don't know how I missed that first time, but I wonder if that could be the problem as am sure the device was still on android v7. I did try to get OTA update before starting this, but it said everything was up to date, so I just assumed that official support in UK stopped at v7.
Should I try installing Lineage version 15.1, to get the right firmware? Then try installing lineage v17?
Sorry for my complete ignorance about how to do this

trickyDicky314 said:
I booted into TWRP and tried to install lineage 17.1 via adb sideload. It seemed to get stuck at 38%. I had a look through the instructions again on lineage website and noticed a warning " Before following these instructions please ensure that the device is on the latest Android 8.1 firmware."
Don't know how I missed that first time, but I wonder if that could be the problem as am sure the device was still on android v7. I did try to get OTA update before starting this, but it said everything was up to date, so I just assumed that official support in UK stopped at v7.
Should I try installing Lineage version 15.1, to get the right firmware? Then try installing lineage v17?
Sorry for my complete ignorance about how to do this
Click to expand...
Click to collapse
You want stock firmware, custom roms don't overwrite everything.
Depends on your software channel. if it's a UK model it should be on RETGB
There are at least 2 different UK models XT1676, and XT1675.
https://mirrors.lolinet.com/firmware/moto/cedric/official/RETGB/
To be sure you should check getvar all
Code:
fastboot getvar all
Easiest way to install stock is LMSA's Rescue
Just verify it's choosing the correct Model # and Software Channel
Spoiler: This is an example of what LMSA will look like, just a different device
{
"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"
}
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com

trickyDicky314 said:
I booted into TWRP and tried to install lineage 17.1 via adb sideload. It seemed to get stuck at 38%. I had a look through the instructions again on lineage website and noticed a warning " Before following these instructions please ensure that the device is on the latest Android 8.1 firmware."
Don't know how I missed that first time, but I wonder if that could be the problem as am sure the device was still on android v7. I did try to get OTA update before starting this, but it said everything was up to date, so I just assumed that official support in UK stopped at v7.
Should I try installing Lineage version 15.1, to get the right firmware? Then try installing lineage v17?
Sorry for my complete ignorance about how to do this
Click to expand...
Click to collapse
Download stock firmware from below link
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
You want the latest retail version
Put phone into fastboot mode
These are the terminal commands
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Download rom zip
Download gapps (open gapps arm64 nano)
Download magisk (for root)
Flash/boot twrp
Go to wipe
Format data (option on the right)
Restart to recovery
Swipe to allow system modifications in twrp
Go to wipe - advanced wipe
Wipe system data cache
Install rom zip
Install gapps
Install magisk
Wipe delvik cache
Restart
Once booted you can encrypt phone via settings if you want to

sd_shadow said:
You want stock firmware, custom roms don't overwrite everything.
Depends on your software channel. if it's a UK model it should be on RETGB
There are at least 2 different UK models XT1676, and XT1675.
https://mirrors.lolinet.com/firmware/moto/cedric/official/RETGB/
To be sure you should check getvar all
Code:
fastboot getvar all
Easiest way to install stock is LMSA's Rescue
Just verify it's choosing the correct Model # and Software Channel
Spoiler: This is an example of what LMSA will look like, just a different device
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you so much for the help. I installed this programme but it didn't work when I selected the model etc
I tried the longer method provided by the fixitman and it worked! I got lineage installed!
Thanks again

TheFixItMan said:
Download stock firmware from below link
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
You want the latest retail version
Put phone into fastboot mode
These are the terminal commands
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Download rom zip
Download gapps (open gapps arm64 nano)
Download magisk (for root)
Flash/boot twrp
Go to wipe
Format data (option on the right)
Restart to recovery
Swipe to allow system modifications in twrp
Go to wipe - advanced wipe
Wipe system data cache
Install rom zip
Install gapps
Install magisk
Wipe delvik cache
Restart
Once booted you can encrypt phone via settings if you want to
Click to expand...
Click to collapse
Thanks so much! This worked, I am now in Lineage OS! Thanks for taking the time to help out a newb like me by writing out every step

trickyDicky314 said:
Thank you so much for the help. I installed this programme but it didn't work when I selected the model etc
I tried the longer method provided by the fixitman and it worked! I got lineage installed!
Thanks again
Click to expand...
Click to collapse
Yeah, just skip that, and go straight to the rescue option

Development Unofficial Lineageos 20 for capri moto g10 and moto g10 power

!!!!!!!!!!!!!!!!!!!!!!!!!WE ARE NOT RESPONSIBLE FOR ANYTHING THAT MIGHT HAPPEN TO YOUR DEVICE TRYING TO INSTALL THIS ROM!!!!!!!!!!!!!!!!!!!!!!
This ROM has been tested for about a week on two capri devices one from India and other from South America
Loads of thanks to @Electimon for his trees and all his help fixing issues we faced in bringing this ROM
Kernel Source: https://github.com/moto-common/android_kernel_motorola_msm-4.19
Manifest: https://github.com/moto-common/local_manifests
Not working:
FM Radio
Dual Sim (Will look into this soon) - Looked into it. This is being flaky once enabled. Will need more time to fix this.
5Ghz Wifi - not stable, keeps disconnecting, use 2.4Ghz
Telegram group: https://t.me/motobengalchat
Flashing instructions:
Code:
Make sure you are on latest of your stock Android 11, Booted and the rom is working.
Download zip and extract it and run the following commands
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vendor_boot vendor_boot.img
fastboot -w
fastboot reboot fastboot
fastboot flash system system.img
# In case the above command fails saying parititon size is not enough then try to resize it with below command
fastboot resize-logical-partition system_a 1073741824 #(run this only if the above command fails and if you are on slot_a else change it to system_b)
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
To flash gapps, follow instructions below
Flashing gapps:
On the phone screen you should be seeing a menu, press volume down to goto Enter recovery and press power button to choose it
Here you will see a different menu, press power down to navigate to apply update and press power button to choose it and press power button again to choose Apply from ADB
Now on the command line enter below command
Code:
adb sideload MindTheGapps-13.0.0-arm64-20230408_162909.zip
In case you have missed flashing gapps and booted into ROM, make sure you reset device in recovery before flashing gapps

...