Related
Code:
#include "std_disclaimer.h"
/*
* Your warranty is now void... Well, probably not.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
* A lot.
*
* Tl;dr: if your device crashes and burns, I'm sorry, but I'm not to be blamed.
*/
Hey guys.
This is a guide on how to install official Android 8.1.0 "Oreo" on our beloved, forgotten, poor Moto G5s (montana). As you all may know, Lenovorola still hasn't released Oreo for everyone worldwide. Only a few Latin American countries are receiving the update, with Brazil due to receive it Soon™, since we've already received the August security patch (still Nougat though :/).
Update 2018.09.29: Brazil and India have also started receiving Oreo, but with a different build (OPP28.65-37-2).
However, this is Lenovorola we're dealing with, so I went ahead, captured the OTA and created a TWRP flashable zip, by patching the June firmware (NPPS26.102-49-11) with said OTA. And also, there's the standard .xml.zip to be used with fastboot, directly from Moto.
For those of you who want to keep everything stock, locked bootloader and all, I recommend going with the fastboot zip. For those who already have unlocked their phone's bootloaders and have TWRP installed, or are coming from a custom ROM but don't want to fiddle around with fastboot, you should use the TWRP flashable zip.
I can't stress this enough. ALWAYS BACK UP YOUR STUFF!!!! Do a TWRP backup (data, system, boot). I recommend backing up the contents of your internal storage as well. And for those willing to downgrade at some point, back up your persist and efs partitions, otherwise you'll lose IMEI!
Oh, and I assume you already have adb, fastboot and the Motorola USB drivers installed. In case you don't...
Motorola USB Drivers
Android SDK Platform Tools (includes adb & fastboot)
If you use Linux, you don't need to install any drivers, but you may have to configure udev to allow fastboot to detect your device. But that, along with telling how to configure adb and fastboot, is beyond the scope of this thread.
I don't know how things work in the Apple side, so kindly don't ask me how to do that on macOS.
This firmware should work on all Moto G5s models (XT1791/2/3/4/5/7). I can't tell if it works on model XT1799-2 (aka Green Pomelo / Qingyou).
A few warnings:
1. Forced encryption has not been disabled. So, if your phone is not encrypted, it will be encrypted again upon the very first boot. Don't interrupt the process, otherwise you'll lose ALL of your data! (You can flash @Zackptg5's dm-verity / forced encryption disabler if you want to)
2. Xposed doesn't work, whether it's installed to /system or via Magisk (systemless). I've already opened an issue on GitHub and am awaiting a reply.
3. (Fastboot only) Updating to this firmware will also update your bootloader and partition table. If you're unsure about that and/or afraid of a possible hard brick, skip the gpt and bootloader lines.
4. Please install the proper build for your software channel. For retbr and retin, use OPP28.65-37-2. For the other channels, go with OPP28.65-37.
5. If your phone's software channel is retbr or retin and you have already flashed the -37 build, you can simply dirty flash the -37-2 build over it. No need to factory reset / fastboot erase userdata.
With that out of the way, let's get to what matters most.
Downloads:
Build OPP28.65-37 (retla):
Fastboot ZIP (Android File Host | MEGA)
TWRP Flashable ZIP (Google Drive)
Click to expand...
Click to collapse
Build OPP28.65-37-2 (retbr & retin):
Fastboot ZIP (Android File Host)
TWRP Flashable ZIP (Google Drive)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Installation Guide:
Fastboot ZIP:
1. Download (obviously)
2. Extract the contents to a folder of your choice
3. Go to the folder which you extracted the files to
3. Inside the folder, open a command prompt, PowerShell, terminal or whatever you use as a command line interface
4. Put your device into fastboot mode if you haven't already done that (just hold Vol Down + Power for a while) and connect it to your PC
5. Execute the following commands:
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash logo logo.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 system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
reboot
6. Have fun
Click to expand...
Click to collapse
TWRP Flashable ZIP:
1. Download (duh)
2. Put the file at the root of your internal storage (/sdcard)
3. Reboot to TWRP
4. Do a factory reset (optional if coming from stock Nougat) and then format /system
(If your device is encrypted and you want to remove encryption, you will have to format /data and then flash the forceencrypt disabler I mentioned above after flashing the ROM)
5. Flash the zip
6. Reboot
7. Have fun
Click to expand...
Click to collapse
Thanks to:
@NZedPred for the excellent tutorial on how to build flashable zips based on stock firmware and/or OTAs
@Cesarcami53 for telling us that the update was out for retla
@erfanoabdi for his Motorola OTA Link Generator and IMG Patch Tools
@lohanbarth for mirroring the fastboot zips to AFH / Mega
In case I forgot someone, please do let me know.
F.A.Q. (Read this before crying!!!!)
Q: Why did you come up with this?
A: Because Lenovorola is pulling a Samsung, taking forever to officially deliver the Oreo update to everyone.
Q: ERMAHGERD DIS ROM SUCKZ, MAH BATTERY IS DEAD IN 30 MINS, PLZ HALP!
A: Please do blame Motorola, or yourself, or your apps' developers, but not me. I haven't got anything to do with that. I haven't changed anything.
Q: What works and what doesn't?
In theory, everything should work, and nothing should be broken, since this is a stock ROM.
Q: Will you add feature xyz?
A: No.
Q: Why no inbuilt root/Magisk/xyz/abc?
A: Because not. 1. There's something called freedom of choice, and that must be respected. / 2. I want to keep everything as bit-perfect as possible, and as close as possible to what you would get by flashing a real OTA.
Q: How do I report bugs?
A: If you wanna report a bug, send me a logcat. In case of a kernel panic, /proc/last_kmsg will help.
Q: How do I flash this?
A: I suggest you scroll up and read the OP. The instructions are there.
Q: How do I tweak this ROM?
A: For theming, there's full OMS/Substratum support. Xposed doesn't work, so no extra tweaks for now.
Q: This kid is such a n00b!
A: Oh well then, why don't you go do something like this yourself, instead of criticizing my work and wasting your time?
Reserved again
Oh look! Another reserved post!
And as a bonus, have this nice little dark boot logo from me, which hides that dreaded "N/A" and also "bad key" things. Extract the zip file and flash the logo3.bin file inside using fastboot:
Code:
fastboot flash logo logo3.bin
Good Night Guys, if I install it for twrp will the installation fiddle with the bootloader?
Which security pet
Official or Soak test?
Kamin4ri said:
Thanks to:
@NZedPred for the excellent tutorial on how to build flashable zips based on stock firmware and/or OTAs
[/SIZE]
Click to expand...
Click to collapse
Hey man, I am so thankful that someone has found my guide and made something for another device.
Well done, and best of luck with this thread. :good:
I can tell you that this build work very well in european distribution (reteu).
Basicly everything work including sim and nfc(paying not tested yet)
The link with the Fastboot ZIP doesn't work for me, I guess I'm the unlucky one. Is there any chance that you can upload it elsewhere? Thanks.
Also not able to download, please offer another download Location!
Do I need to unlock my bootloader on Russian type of XT1794 to flash this firmware via PC?
ilovepanda said:
Good Night Guys, if I install it for twrp will the installation fiddle with the bootloader?
Click to expand...
Click to collapse
No. Your bootloader will be updated if, and only if, you install via fastboot and actually execute the respective command.
[email protected] said:
Official or Soak test?
Click to expand...
Click to collapse
This is the official firmware released for retla (Latin America). However, the soak tests in Brazil haven't finished yet. I'll update the OP with the link for the Brazilian firmware as soon as it's available.
NZedPred said:
Hey man, I am so thankful that someone has found my guide and made something for another device.
Well done, and best of luck with this thread. :good:
Click to expand...
Click to collapse
Thank you, friend! I'll be definitely using that guide again.
7opex0 said:
Do I need to unlock my bootloader on Russian type of XT1794 to flash this firmware via PC?
Click to expand...
Click to collapse
Only if you're flashing via TWRP. If you're using fastboot, there's no need to unlock your bootloader, since this is an official firmware signed by Motorola.
giugiura said:
The link with the Fastboot ZIP doesn't work for me, I guess I'm the unlucky one. Is there any chance that you can upload it elsewhere? Thanks.
Click to expand...
Click to collapse
dau999 said:
Also not able to download, please offer another download Location!
Click to expand...
Click to collapse
I have the zip here, but uploading it using my home Internet connection would take ages. I'll do it next Monday, I'll use my university's connection. I can get 100+ Mbps transfer rates, so it should be really quick for a file this size (1.5 GB).
Kamin4ri said:
If you're using fastboot, there's no need to unlock your bootloader, since this is an official firmware signed by Motorola.
Click to expand...
Click to collapse
Okay then! Thanks for information.
7opex0 said:
Okay then! Thanks for information.
Click to expand...
Click to collapse
Not at all!
Kamin4ri said:
I have the zip here, but uploading it using my home Internet connection would take ages. I'll do it next Monday, I'll use my university's connection. I can get 100+ Mbps transfer rates, so it should be really quick for a file this size (1.5 GB).
Click to expand...
Click to collapse
Please upload it on some other cloud so that we can download it thanks for help sir
In advance
Hello,
I've been looking through this forum for quite a while, but I have yet to stumble upon a guide that can fix me up for taking the next step after the bootloader unlocking process. Yet, there's been lots of custom roms made for rmx2001. So here I'm with my unlocked rmx2001 or realme 6, wondering if I am missing out on something crucial for the next step because this is my first time doing something like this on a mediatek based phone. Kindly help me out pweese.. thank you;
Update:
I've dwelled deep into the forest, fought clones of sundar pichai, then finally.. successfully flashed my phone with custom recovery.
From what I've had read around this forum and other places, before flashing any custom recovery, the vbmeta.img must be flashed with a patched one, which as usual, there are rules one must follow to modify this certain android component.
This is the first for me, as per Android 8 (or Android 7 with its super confusing arb system took in place), any changes inside the recovery, system, etc are being handled by this vbmeta module.
It seems that vbmeta.img changes for every android or system update and to patch this vbmeta.img, the android version must be the same as what the patch corresponds to... (correct me if I'm wrong; this is my understanding based solely from what I have read, please take this with a big chunk of salt).
I currently have the b.57 update installed on my device, and I only found b.55 here on the next forum's page... the point is I have to wait for the latest patch of vbmeta b.57. Am I understanding this correctly, or am I just talking in elven language to myself? Anyway thank you for reading.
zero help, good for nothing advices. Search on other forums ,you Will get at least real help
cristianwcw said:
zero help, good for nothing advices. Search on other forums ,you Will get at least real help
Click to expand...
Click to collapse
lmao
ignoll said:
From what I've had read around this forum and other places, before flashing any custom recovery, the vbmeta.img must be flashed with a patched one, which as usual, there are rules one must follow to modify this certain android component.
This is the first for me, as per Android 8 (or Android 7 with its super confusing arb system took in place), any changes inside the recovery, system, etc are being handled by this vbmeta module.
It seems that vbmeta.img changes for every android or system update and to patch this vbmeta.img, the android version must be the same as what the patch corresponds to... (correct me if I'm wrong; this is my understanding based solely from what I have read, please take this with a big chunk of salt).
I currently have the b.57 update installed on my device, and I only found b.55 here on the next forum's page... the point is I have to wait for the latest patch of vbmeta b.57. Am I understanding this correctly, or am I just talking in elven language to myself? Anyway thank you for reading.
Click to expand...
Click to collapse
Hi fellow weeb I'm curious of how did you manage to flash custom recovery?
Lyco. said:
Hi fellow weeb I'm curious of how did you manage to flash custom recovery?
Click to expand...
Click to collapse
g'day to you sire *tip*, sorry for the late response. Before flashing any custom recovery;
make sure your phone is unlocked,
- boot to bootloader,
- flash vbmeta.img (this assuming you will not be using realme UI or stock ROM in that case, because chances are you can't go back once you've flashed this image [although not entirely sure])
code here:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
- finally, flash your custom recovery
code here:
Code:
fastboot flash recovery <name of the file>.img
Now, I tried flashing twrp, but for some reason, it didn't work. I personally got recommended to use Pitch Black Recovery Project, basically a fork from twrp. It couldn't read my sdcard, but it has better ui compared to twrp. That said, you still can flash custom rom by adb shell through pbrp.
ignoll said:
g'day to you sire *tip*, sorry for the late response. Before flashing any custom recovery;
make sure your phone is unlocked,
- boot to bootloader,
- flash vbmeta.img (this assuming you will not be using realme UI or stock ROM in that case, because chances are you can't go back once you've flashed this image [although not entirely sure])
code here:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
- finally, flash your custom recovery
code here:
Code:
fastboot flash recovery <name of the file>.img
Now, I tried flashing twrp, but for some reason, it didn't work. I personally got recommended to use Pitch Black Recovery Project, basically a fork from twrp. It couldn't read my sdcard, but it has better ui compared to twrp. That said, you still can flash custom rom by adb shell through pbrp.
Click to expand...
Click to collapse
Do you a vbmeta.img for the latest patches b.59 or any guide to extract vbmeta, Just like you said the vbmeta corresponds with the patch.
Lyco. said:
Do you a vbmeta.img for the latest patches b.59 or any guide to extract vbmeta, Just like you said the vbmeta corresponds with the patch.
Click to expand...
Click to collapse
We can just use the vbmeta.img from stock ROM .ozip
Thanks
HemanthJabalpuri said:
We can just use the vbmeta.img from stock ROM .ozip
Thanks
Click to expand...
Click to collapse
I thought it depends on the patch. i just want to be careful i don't want to brick my device again btw the stock ozip is b.23 am i right? Or do you have a stock vbmeta?
Lyco. said:
I thought it depends on the patch. i just want to be careful i don't want to brick my device again btw the stock ozip is b.23 am i right?
ignoll said:
g'day to you sire *tip*, sorry for the late response. Before flashing any custom recovery;
make sure your phone is unlocked,
- boot to bootloader,
- flash vbmeta.img (this assuming you will not be using realme UI or stock ROM in that case, because chances are you can't go back once you've flashed this image [although not entirely sure])
code here:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
- finally, flash your custom recovery
code here:
Code:
fastboot flash recovery <name of the file>.img
Now, I tried flashing twrp, but for some reason, it didn't work. I personally got recommended to use Pitch Black Recovery Project, basically a fork from twrp. It couldn't read my sdcard, but it has better ui compared to twrp. That said, you still can flash custom rom by adb shell through pbrp.
Click to expand...
Click to collapse
ignoll said:
g'day to you sire *tip*, sorry for the late response. Before flashing any custom recovery;
make sure your phone is unlocked,
- boot to bootloader,
- flash vbmeta.img (this assuming you will not be using realme UI or stock ROM in that case, because chances are you can't go back once you've flashed this image [although not entirely sure])
code here:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
- finally, flash your custom recovery
code here:
Code:
fastboot flash recovery <name of the file>.img
Now, I tried flashing twrp, but for some reason, it didn't work. I personally got recommended to use Pitch Black Recovery Project, basically a fork from twrp. It couldn't read my sdcard, but it has better ui compared to twrp. That said, you still can flash custom rom by adb shell through pbrp.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Is this the stock vbmeta? Or do anyone have any?
Lyco. said:
I thought it depends on the patch. i just want to be careful i don't want to brick my device again btw the stock ozip is b.23 am i right? Or do you have a stock vbmeta?
Click to expand...
Click to collapse
No, we don't need to modify anything to it.
--disable-verity and --disable-verification options to fastboot will patch it and flash automatically for you.
Also you can use vbmeta.img from any version of stock .ozip.
I am a Realme C12 user.
Thanks
HemanthJabalpuri said:
No, we don't need to modify anything to it.
--disable-verity and --disable-verification options to fastboot will patch it and flash automatically for you.
Also you can use vbmeta.img from any version of stock .ozip.
I am a Realme C12 user.
Thanks
Click to expand...
Click to collapse
Ok so what would I do if pbrp didn't showed up? And goes to bootloop, Do i just need to flash ofp and use realme flash tool?
I'm a new at flashing firmware so sorry about that
Lyco. said:
Ok so what would I do if pbrp didn't showed up? And goes to bootloop, Do i just need to flash ofp and use realme flash tool?
I'm a new at flashing firmware so sorry about that
Click to expand...
Click to collapse
Then flash stock recovery.
HemanthJabalpuri said:
Then flash stock recovery.
Click to expand...
Click to collapse
So after i flash the stock recovery should I flash the ozip there? And thanks for all the information.
Hello, is there any possible way to install android 12 beta GSI on Galaxy A10? The only method I come across is fastboot which is just bringing me to download mode which will not work for installing.
alansojan2020 said:
Hello, is there any possible way to install android 12 beta GSI on Galaxy A10? The only method I come across is fastboot which is just bringing me to download mode which will not work for installing.
Click to expand...
Click to collapse
... Galaxy A10 is crying on Android 11... Also wait for devs to make the ROM or make your own ROM. I don't bellive in gsi installing. If you have Android 12 gsi can I have link pls lol
Abd El-Rahman El-Batal said:
... Galaxy A10 is crying on Android 11... Also wait for devs to make the ROM or make your own ROM. I don't bellive in gsi instal
Click to expand...
Click to collapse
Abd El-Rahman El-Batal said:
... Galaxy A10 is crying on Android 11... Also wait for devs to make the ROM or make your own ROM. I don't bellive in gsi installing. If you have Android 12 gsi can I have link pls lol
Click to expand...
Click to collapse
I have it here https://www.getdroidtips.com/download-android-12-gsi/
alansojan2020 said:
Hello, is there any possible way to install android 12 beta GSI on Galaxy A10? The only method I come across is fastboot which is just bringing me to download mode which will not work for installing.
Click to expand...
Click to collapse
Also gimme gsi link lol
alansojan2020 said:
Hello, is there any possible way to install android 12 beta GSI on Galaxy A10? The only method I come across is fastboot which is just bringing me to download mode which will not work for installing.
Click to expand...
Click to collapse
I tried gsi before. I tried android 11 gsi which didn't worked. Anyways can I install vendor with it maybe it works?
Abd El-Rahman El-Batal said:
Also gimme gsi link lol
I tried gsi before. I tried android 11 gsi which didn't worked. Anyways can I install vendor with it maybe it works?
Click to expand...
Click to collapse
I tried it with 64 bit A10 vendor but it doesn't work
alansojan2020 said:
I tried it with 64 bit A10 vendor but it doesn't work
Click to expand...
Click to collapse
Then try 32 bit one lol
alansojan2020 said:
Hello, is there any possible way to install android 12 beta GSI on Galaxy A10? The only method I come across is fastboot which is just bringing me to download mode which will not work for installing.
Click to expand...
Click to collapse
BRO I found the solution.
Ok first clean to install a new ROM in twrp.
I mean wipe system and data and cache. Now switch twrp to install image mode and choose "system.img" flash it as system.
And flash this after it. The dm verification disabler. BUT make sure you have some empty space in internal storage. [About 5GB or smth] clean up space. Tell me your results after doing this. Here is file [check attachments] I'm 50% sure it gonna work. Plz tell me results.
Edit: NVM I tested it people was saying it works it doesn't. So read next post.
alansojan2020 said:
Hello, is there any possible way to install android 12 beta GSI on Galaxy A10? The only method I come across is fastboot which is just bringing me to download mode which will not work for installing.
Click to expand...
Click to collapse
Ok bro the dm verify not gonna work.
You must do the following commands people tried before and it worked.
First put your device in recovery.
Make sure to enable USB debugging.
Then if you can't boot to recovery simply when device is on type command:
and reboot recovery
And it will reboot you to recovery.
Clean the system and other stuff such as data.
TWRP supports adv commands btw
Simply type and reboot bootloader or just reboot to download mode ._ .
Now you gotta type command:
fastboot devices
If you see your device listed type comman
fastboot flash system SYSTEM://IMAGE/LOCATION.IMG
Then when done.. [gsi comes with vbmeta file]
Do this command:
fastboot flash vbmeta VBMETA://IMAGE/LOCATION.IMG
then just do this command:
fastboot reboot
Tell me results.
Abd El-Rahman El-Batal said:
Ok bro the dm verify not gonna work.
You must do the following commands people tried before and it worked.
First put your device in recovery.
Make sure to enable USB debugging.
Then if you can't boot to recovery simply when device is on type command:
and reboot recovery
And it will reboot you to recovery.
Clean the system and other stuff such as data.
TWRP supports adv commands btw
Simply type and reboot bootloader or just reboot to download mode ._ .
Now you gotta type command:
fastboot devices
If you see your device listed type comman
fastboot flash system SYSTEM://IMAGE/LOCATION.IMG
Then when done.. [gsi comes with vbmeta file]
Do this command:
fastboot flash vbmeta VBMETA://IMAGE/LOCATION.IMG
then just do this command:
fastboot reboot
Tell me results.
Click to expand...
Click to collapse
Okay I will do it tomorrow, thank you.
Abd El-Rahman El-Batal said:
Ok bro the dm verify not gonna work.
You must do the following commands people tried before and it worked.
First put your device in recovery.
Make sure to enable USB debugging.
Then if you can't boot to recovery simply when device is on type command:
and reboot recovery
And it will reboot you to recovery.
Clean the system and other stuff such as data.
TWRP supports adv commands btw
Simply type and reboot bootloader or just reboot to download mode ._ .
Now you gotta type command:
fastboot devices
If you see your device listed type comman
fastboot flash system SYSTEM://IMAGE/LOCATION.IMG
Then when done.. [gsi comes with vbmeta file]
Do this command:
fastboot flash vbmeta VBMETA://IMAGE/LOCATION.IMG
then just do this command:
fastboot reboot
Tell me results.
Click to expand...
Click to collapse
When I type in fastboot devices it just comes up
"C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
C:\Program Files (x86)\Minimal ADB and Fastboot>"
alansojan2020 said:
When I type in fastboot devices it just comes up
"C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
C:\Program Files (x86)\Minimal ADB and Fastboot>"
Click to expand...
Click to collapse
Yes me too. I thought my device was broken but smasungs does not support fastboot. It is impossible to install gsi using fastboot in a smasung device. Instead you can wait for a developer to release android 12 ROM.
Abd El-Rahman El-Batal said:
Yes me too. I thought my device was broken but smasungs does not support fastboot. It is impossible to install gsi using fastboot in a smasung device. Instead you can wait for a developer to release android 12 ROM.
Click to expand...
Click to collapse
I found this.
alansojan2020 said:
I found this.
Click to expand...
Click to collapse
Samsungs does not support fastboot. We have to wait until a developer releases android 12 ROM for galaxy a10
Abd El-Rahman El-Batal said:
Samsungs does not support fastboot. We have to wait until a developer releases android 12 ROM for galaxy a10
Click to expand...
Click to collapse
The video isnt using fastboot though
alansojan2020 said:
The video isnt using fastboot though
Click to expand...
Click to collapse
I tried the way and it ended up in a bootloop. I have to install my Rom again and set it up again
Abd El-Rahman El-Batal said:
I tried the way and it ended up in a bootloop. I have to install my Rom again and set it up again
Click to expand...
Click to collapse
Oh okay sorry about that.
alansojan2020 said:
Oh okay sorry about that.
Click to expand...
Click to collapse
So, I'm on cherish is right now. By the way. When I installed the Android 12 gsi and the system partition used all storage. And there was 64mb free only in system partion. Is that the problem?
Also I don't mind it's okay :3
Abd El-Rahman El-Batal said:
So, I'm on cherish is right now. By the way. When I installed the Android 12 gsi and the system partition used all storage. And there was 64mb free only in system partion. Is that the problem?
Also I don't mind it's okay :3
Click to expand...
Click to collapse
Is cherish really fast?
alansojan2020 said:
Is cherish really fast?
Click to expand...
Click to collapse
Want a gaming rom? Fast? Use the stock android 9 rom. Want android 11 gaming rom? Use corvus. Want android 11 gaming rom and with bunch of features? Use LINEAGE OS FE [FAN EDITION] it's the best rom I had for now.
Abd El-Rahman El-Batal said:
Want a gaming rom? Fast? Use the stock android 9 rom. Want android 11 gaming rom? Use corvus. Want android 11 gaming rom and with bunch of features? Use LINEAGE OS FE [FAN EDITION] it's the best rom I had for now.
Click to expand...
Click to collapse
Hi how do I install stock samsung android 10 rom with twrp?
Hey XDA!
On Xiaomi 11 Lite 5G (renoir) after flashing stock firmware, re-unlocking bootloader, etc
Following these steps,
1: Boot into fastboot
2: Doing fastboot flash vbmeta vbmeta.img
3: Doing fastboot reboot fastboot to enter fastbootd
4: Doing fastboot flash system dotOS-R-v5.2-arm64-ab-GAPPS-OFFICIAL.img
5: Doing fastboot -w
6: Doing fastboot reboot
Booting into system, I see Mi Logo for a second, then I'm kicked back into bootloader (fastboot), no GSI has worked except for the one here.
I'd love some help, and I apologize for not being very verbose, I would love to get GSIs working on this phone so I'm going to respond as soon as I can with any information regarding.
I don't install TWRP because Nebrassy's TWRP, while functional. Is completely useless for fastbootd, which ruins any troubleshooting opportunities.
Skylius said:
Hey XDA!
5: Doing fastboot -w
Click to expand...
Click to collapse
don't do that but go to stock recovery and format data from here...
rayman95 said:
don't do that but go to stock recovery and format data from here...
Click to expand...
Click to collapse
Doing that doesn't work either, I resorted to doing fastboot -w if the latter doesn't work because it's the only thing that's given me any success.
Skylius said:
Doing that doesn't work either, I resorted to doing fastboot -w if the latter doesn't work because it's the only thing that's given me any success.
Click to expand...
Click to collapse
follow my tuto...
rayman95 said:
follow my tuto...
Click to expand...
Click to collapse
That's pretty much what I've been following, I've tried different firmware, different methods, your method a thousand times, countless roms, different versions of miui as a base, honestly all just do nothing for me
Skylius said:
That's pretty much what I've been following, I've tried different firmware, different methods, your method a thousand times, countless roms, different versions of miui as a base, honestly all just do nothing for me
Click to expand...
Click to collapse
have you take the files I upload specially adb folder...send screenshot of the error on cmd..
rayman95 said:
have you take the files I upload specially adb folder...send screenshot of the error on cmd..
Click to expand...
Click to collapse
Honestly, I've switched my focus at this point to making an unofficial DotOS build. Will upload when ready
Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Changelog:
• Updated sources to latest
• Almost Everything working fine.
Only for MIUI 13 Android 11
Creator: @Aghora7
Download
Installation instructions
whats is with data encrypten? is it working or problems with: "cant decrypt fbev2 partition"?
lurchiii said:
whats is with data encrypten? is it working or problems with: "cant decrypt fbev2 partition"?
Click to expand...
Click to collapse
I can't answer to this question, because it depends on you made any mistakes during the installation or not
Its support for A12 miui 13.0.4
Does it support A12 eea europe rom ?
xristos1925 said:
Does it support A12 eea europe rom ?
Click to expand...
Click to collapse
it supports a11
It seems Poco M4 Pro is not supported by TWRP and OrangeFox and that this unofficial TWRP is only for Android 11..
In my case I rooted (with magisk) from the latest ROM with Android 12..
And then installed LineageOS (Android 13). Everything works fine..
But I want to have a custom recovery for installing e.g. Gapps...
How can I do that?
Or do I need to rollback to previous ROM, install this TWRP then root with magisk and then go and install Lineage OS (and in that case I will still have TWRP and rooted)?
Thanks for any details..
sanjibukai said:
It seems Poco M4 Pro is not supported by TWRP and OrangeFox and that this unofficial TWRP is only for Android 11..
In my case I rooted (with magisk) from the latest ROM with Android 12..
And then installed LineageOS (Android 13). Everything works fine..
But I want to have a custom recovery for installing e.g. Gapps...
How can I do that?
Or do I need to rollback to previous ROM, install this TWRP then root with magisk and then go and install Lineage OS (and in that case I will still have TWRP and rooted)?
Thanks for any details..
Click to expand...
Click to collapse
Once you have lineageos installed, you must to flash twrp via fastboot and then flash Gapps
1. Flash system ( when it's done, don't reboot phone, just flash twrp
2. If you already are on twrp flash your Google apps
3. When you're done with flashing gapps, restart phone to system (twrp will be gone after reboot)
4. You have installed Gapps
i don't know how to flash twrp permanently, if you want further informations about this recovery, then join fleur telegram development channel
BloxetPL said:
1. Flash system ( when it's done, don't reboot phone, just flash twrp
Click to expand...
Click to collapse
Hello and thanks for the reply..
Currently when I'm installing LineageOS I do the following:
Code:
# SMINORI SCRIPT
fastboot flash system system.img
fastboot reboot fastboot
fastboot getvar is-userspace
fastboot erase system
fastboot delete-logical-partition product_a
fastboot flash system system.img
# <- here?
fastboot reboot recovery
Do you mean that after installing LineageOS above, I need to run:
Code:
fastboot flash boot twrp.img
fastboot boot twrp.img
# Booting in TWRP despite the error
adb sideload gapps_file.zip
And then just install Gapps using the TWRP GUI?
sanjibukai said:
Hello and thanks for the reply..
Currently when I'm installing LineageOS I do the following:
Code:
# SMINORI SCRIPT
fastboot flash system system.img
fastboot reboot fastboot
fastboot getvar is-userspace
fastboot erase system
fastboot delete-logical-partition product_a
fastboot flash system system.img
# <- here?
fastboot reboot recovery
Do you mean that after installing LineageOS above, I need to run:
Code:
fastboot flash boot twrp.img
fastboot boot twrp.img
# Booting in TWRP despite the error
adb sideload gapps_file.zip
And then just install Gapps using the TWRP GUI?
Click to expand...
Click to collapse
Remove "fastboot reboot recovery" from SMINORI tool and instead of this type "fastboot flash boot twrp.img
fastboot boot twrp.img"
I currently have MIUI13 and Android 11.
Tried to install TWRP with the instructions given but my phone will keep on bootloop.
TWRP interface shows for a few seconds but it shuts down after.
Im looking everywhere for answers but couldnt find any
globalfandemic said:
I currently have MIUI13 and Android 11.
Tried to install TWRP with the instructions given but my phone will keep on bootloop.
TWRP interface shows for a few seconds but it shuts down after.
Im looking everywhere for answers but couldnt find any
Click to expand...
Click to collapse
I saw that your question on telegram, as they said do "fastboot reboot recovery" no "fastboot boot twrp.img"
BloxetPL said:
I saw that your question on telegram, as they said do "fastboot reboot recovery" no "fastboot boot twrp.img"
Click to expand...
Click to collapse
Already tried, still same issue.
Tried using a couple new commands too with no result:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot_a twrp.img
fastboot flash boot_b twrp.img
fastboot reboot recovery
Also tried using only the commands you gave:
fastboot flash boot twrp.img
fastboot reboot recovery