I have moto g4 plus (2016) and want to install custom rom but I have some questions and without knowing about them i can't take the risk.so please answer sir.
1) There is 2 Twrp custom recovery one is 32 bit and second is 64 bit, so which is best ?
2) if I use 32 bit and flash 64 bit rom ,can it possible?
3) if No then if am use 64 bit Twrp and flash 32 bit rom accidentally ,can it will brick my device??
4) i am currently on stock rom android 7.0 , today most custom rom is based on 9.0 ,if I flash pie custom rom and after months i want revert back to stock or Oreo rom ,can i will do it? Because in some custom rom there is note that after flashing this rom you can not revert back lower version of rom.
5) where is rom take space if I flash it, means in ram ,internal storage???
Thanks in advance.i know this question is help for other noob:good:
keval3492 said:
I have moto g4 plus (2016) and want to install custom rom but I have some questions and without knowing about them i can't take the risk.so please answer sir.
1) There is 2 Twrp custom recovery one is 32 bit and second is 64 bit, so which is best ?
2) if I use 32 bit and flash 64 bit rom ,can it possible?
3) if No then if am use 64 bit Twrp and flash 32 bit rom accidentally ,can it will brick my device??
4) i am currently on stock rom android 7.0 , today most custom rom is based on 9.0 ,if I flash pie custom rom and after months i want revert back to stock or Oreo rom ,can i will do it? Because in some custom rom there is note that after flashing this rom you can not revert back lower version of rom.
5) where is rom take space if I flash it, means in ram ,internal storage???
Thanks in advance.i know this question is help for other noob:good:
Click to expand...
Click to collapse
64bit recoveries can handle 32bit roms too. Use a 64bit recovery and everything is fine.
You cannot downgrade your bootloader from stock Oreo to stock nougat(your current Rom). Custom roms won't flash bootloaders,only stock roms.
Your whole flash storage of your device is divided into several partitions like system, data, boot, recovery, internal storage. That's why you have to deal with less memory in your internal storage(10 out of 16 for example).
You cannot(yeah, but don't do it) modify the partition size cause it's used to met some requirements.
The rom will be flashed into system/data partition, not internal storage but also uses ram of course
Thanks man , but can you elaborate my question on if I flash today custom rom on pie base and that is rumor on moto g4 plus that oreo update will launch soon and I also wait for it.so can i get that update if I am on pie custom rom.sorry for your answer ,i not understand that .
keval3492 said:
Thanks man , but can you elaborate my question on if I flash today custom rom on pie base and that is rumor on moto g4 plus that oreo update will launch soon and I also wait for it.so can i get that update if I am on pie custom rom.sorry for your answer ,i not understand that .
Click to expand...
Click to collapse
Yes you can get official Oreo update if you are on Pie custom rom. You just need to go back to stock rom or flash the stock Oreo rom manually like the soak test.
Can you give me Twrp 64 bit link and also which custom rom do you prefer on gaming performance , battery performance and customisable wise? Thanks a lot...
keval3492 said:
Can you give me Twrp 64 bit link and also which custom rom do you prefer on gaming performance , battery performance and customisable wise? Thanks a lot...
Click to expand...
Click to collapse
Here's a link for the 64 bit TWRP https://forum.xda-developers.com/mo...recovery-twrp-3-2-1-unofficial-touch-t3722206 for flashing both 32 bit and 64 bit custom ROMs and TWRP flashables.
Of course, unlocking your bootloader and flashing a custom ROM via TWRP will unavoidably erase your device, so back up as necessary. Be also aware that flashing a custom ROM may necessitate flashing magisk as well, to get your device Google certified again.
As for a particular ROM, your best bet is to have a look at each custom ROM's page and particularly the first page and the last few pages. Both of those should give you information on how suitable the ROM is from other user's reports for your usage and also give you an idea how often the ROM is updated.
It is necessary for flashing magisk? Because magisk root my mobile and I don't want to do it right now.
keval3492 said:
It is necessary for flashing magisk? Because magisk root my mobile and I don't want to do it right now.
Click to expand...
Click to collapse
For some apps, like banking apps for example, these apps may not function properly if they detect an unlocked bootloader, or if your device does not pass Google Play Store certification. If you're wanting to flash a custom ROM or a TWRP flashable, then you may have to consider flashing magisk for magisk hide. Magisk hide helps to hide your unlocked bootloader status and thus may get your device certified to use these apps. Up to you - depends on if you use apps that won't work if they detect your device has an unlocked bootloader.
Thanks sir for get me guide .What is athens when I open xda moto g4 plus and what is kernel and how it is important ??
keval3492 said:
Thanks sir for get me guide .What is athens when I open xda moto g4 plus and what is kernel and how it is important ??
Click to expand...
Click to collapse
I'm guessing by Athens you mean athene? If so, athene is the device codename for the Moto G4/plus (2016). Custom ROMs and software designed for athene should work on our services, though please check the release dates of such software. That also means software built for another device codename may not work.
A kernel is part of the software communicating between the hardware and the software. Custom ROMs will come with one usually. If you choose to flash another kernel, ensure you flash the correct type of kernel - there are kernels for stock 7.0/6.0 (Motorola), 7.1 (custom) and kernels for custom 8.1/9.0 ROMs. These may not be cross compatible and as such if you flash the incorrect kernel to your device your device may fail to boot (buy then that's what TWRP backups are for). Due to the lack of source code for stock 8.1, I've not seen custom kernels built for the stock Motorola 8.1 stock ROM yet.
Thank you sir for guide me about athene and kernel ,so i choose custom rom only made for athene and kernel is also built in with custom rom.
I am on stock oreo on moto g4 plus ,it is same process in oreo for unlock bootloader??
keval3492 said:
I am on stock oreo on moto g4 plus ,it is same process in oreo for unlock bootloader??
Click to expand...
Click to collapse
Please search within the correct rom thread https://forum.xda-developers.com/mo...4-oreo-soak-test-update-t3871136/post78966322
I did not get proper answer from link you send ,please help for this..
keval3492 said:
I did not get proper answer from link you send ,please help for this..
Click to expand...
Click to collapse
Should be the same process to unlock your bootloader, provided your motherboard is the same and you've still got your IMEI and software channel.
Can you elaborate what you said about motherboard and IMEI ,i am getting that method is same as nought but after that line i don't understand.
keval3492 said:
Can you elaborate what you said about motherboard and IMEI ,i am getting that method is same as nought but after that line i don't understand.
Click to expand...
Click to collapse
When you unlock your bootloader, you need the unlock key. The unlock key is likely generated from and linked to your motherboard; if your motherboard had been changed, then you'd have to get a new unlock key.
If your IMEI is still present in your device and working, the unlock key should work. Some users with existing IMEI issues may not be able to unlock their bootloaders.
Basically, if your device is the same when you requested the unlock key, and everything is working okay, then unlocking should be the same as Nougat without any further steps. Back up, boot to fastboot and connect your device to your computer, then enter the unlock key command - with your key - on your computer in the minimal ADB terminal.
I changed my motherboard once and after that I unlock my bootloader also ,but I brick my device by installing 64 bit rom on 32 bit twrp version and after that I lock my bootloader and start as a fresh device till now.
Same key is still working for me as I want unlock my bootloader??
keval3492 said:
I changed my motherboard once and after that I unlock my bootloader also ,but I brick my device by installing 64 bit rom on 32 bit twrp version and after that I lock my bootloader and start as a fresh device till now.
Same key is still working for me as I want unlock my bootloader??
Click to expand...
Click to collapse
Should be - use the same key as you used to unlock your bootloader before (after you had your motherboard changed). Be aware you will not be able to re-lock your bootloader if you unlock your bootloader at the moment. We do not have the Oreo firmware to lock stock Oreo devices or devices previously updated to stock Oreo firmware.
Oreo firmware means coding in CMD ??
Related
Hi there,
I'm using 4.4.2 wanamlite 2.9 rom on a i9505 with twrp 2.8.
Recently I encountered lot of problems like modem not working properly, rebooting, videos playing in slowmo, no sound etc... weird stuff...
I'm convinced to upgrade to (lets say) marshmallow (any custom rom) but I dunno how to do it properly. So here my questions:
- should I flash the stock rom and start again with root / custom rom etc? Or...
- should I upgrade with odin to stock modem and bootloader first, and after that install a custom rom via twrp? Which way is the correct one?
Btw. Should I upgrade to lolli, marsh or 7.x? Dunno whats better. I'm using touchwiz with xposed framework. I dont need tw but i find xposed very helpful. Any advice or link to guides?
Thanx
Upgrade the individual components. In your case, that means recovery, bootloader, and modem via Odin. Your copy of TWRP is ancient and the newer versions of Android need a newer version of TWRP to properly flash them. Once you've upgraded the components, download any Android 6.x ROM for your device - since you want Xposed - and flash it via TWRP. Android 7.x ROMs are available for your device, but Xposed does not work on them, and I don't expect it to work any time soon.
Strephon Alkhalikoi said:
Upgrade the individual components. In your case, that means recovery, bootloader, and modem via Odin. Your copy of TWRP is ancient and the newer versions of Android need a newer version of TWRP to properly flash them. Once you've upgraded the components, download any Android 6.x ROM for your device - since you want Xposed - and flash it via TWRP. Android 7.x ROMs are available for your device, but Xposed does not work on them, and I don't expect it to work any time soon.
Click to expand...
Click to collapse
Thanx Stephron.
Yesterday I updated via .img the recovery (TWRP 3.2).
Now I'll look for bootloader and modem. Should I use the stock ones or are on xda some threads with better modems and bootloaders?
I think I'm going for resurrection remix or for some aosp. Any experience?
Best and happy new year .
foongaz said:
Thanx Stephron.
Yesterday I updated via .img the recovery (TWRP 3.2).
Now I'll look for bootloader and modem. Should I use the stock ones or are on xda some threads with better modems and bootloaders?
I think I'm going for resurrection remix or for some aosp. Any experience?
Best and happy new year .
Click to expand...
Click to collapse
There are no custom modems and bootloaders.
Pwnycorn said:
There are no custom modems and bootloaders.
Click to expand...
Click to collapse
:good:
Really appreciate your help folks. I didnt follow xda for a while and I felt obsolete somehow heheheh
Is it possible or is it with the recovery image im using
Asus Zenfone 2 laser ze550kl z00l is my phone model
I have tried many stockroms to install but only one get installed perfectly namely back2stock-1.17.40.1234.zip. Because of this i can't even install any other custom roms like i tried to install lineage rom but itstuck on bootloop
Any kind of replies and queries about my problem asked will be much help full
moddinandroid said:
Is it possible or is it with the recovery image im using
Asus Zenfone 2 laser ze550kl z00l is my phone model
I have tried many stockroms to install but only one get installed perfectly namely back2stock-1.17.40.1234.zip. Because of this i can't even install any other custom roms like i tried to install lineage rom but itstuck on bootloop
Any kind of replies and queries about my problem asked will be much help full
Click to expand...
Click to collapse
Install mm framware then install custom ROM...it will sure booted up
mg712702 said:
Install mm framware then install custom ROM...it will sure booted up
Click to expand...
Click to collapse
What im trying to tell is that my problem is not only installation in custom roms but i also cant install any other roms eiether from official site or some other site which means i cant install any roms accept the one the stock rom i mentioned above. And also i already tried to install MM firmware but it gives out error code 7 in twrp. I tried as i was said to install the previous version of lollipop before the update of MM came out but still i cant install them.
moddinandroid said:
What im trying to tell is that my problem is not only installation in custom roms but i also cant install any other roms eiether from official site or some other site which means i cant install any roms accept the one the stock rom i mentioned above. And also i already tried to install MM firmware but it gives out error code 7 in twrp. I tried as i was said to install the previous version of lollipop before the update of MM came out but still i cant install them.
Click to expand...
Click to collapse
Which Android u r using now
Lolipop or MM
is your bootloader locked on unlocked?
just go back to stock versions for now
if u r on lollipop, download the 'next version' from asus
if u r on marshmallow, download the next version from asus
use fastboot (bootloader) mode to flash if required
when all is stable and done,
download & flash twrp
flash lineage 13, then lineage 14
yograjfire18 said:
Which Android u r using now
Lolipop or MM
Click to expand...
Click to collapse
Iam using lollipop right now
pokipokipxorn said:
is your bootloader locked on unlocked?
just go back to stock versions for now
if u r on lollipop, download the 'next version' from asus
if u r on marshmallow, download the next version from asus
use fastboot (bootloader) mode to flash if required
when all is stable and done,
download & flash twrp
flash lineage 13, then lineage 14
Click to expand...
Click to collapse
Yes my bootoader is unlocked cuz i tried rooting my phone when MM update came out
I cant roll back to the original/factory rom cuz i can't install any rom including official asus ones
2. Ill be trying to using fastboot will post results soon
moddinandroid said:
Iam using lollipop right now
Click to expand...
Click to collapse
that's the reason u can install any custom rom, bcs they r all MM or N
so U hav to first upgrade to mm using stock rom
then u can flash any rom
moddinandroid said:
Iam using lollipop right now
Click to expand...
Click to collapse
https://basketbuild.com/filedl/devs?dev=LuK1337&dl=LuK1337/ZF2L-FW/Z00L-WW-21.40.1220.1615.zip
Download and flash then u r ready to go
Now u can install any rom, like RR MM, CM 13 many others too
Hit thanks if i helped
Yeah that right..or you can make backtostock.zip by your self,just download stock mm rom and copy the following requirement file to backtostock.zip and flash that on twrp..
Thnsk guys for all your replies
My problem i was not using latest twrp recovery
Again thank you so much for ur help
Hi guys I have rooted my YU yureka cm 11. Its been 2 days I am trying to flash twrp on my device using both twrp official app and twrp manager. I have tried 3.1,3.0,3.02 versions while flashing. After flashing it says successfull but when I tried to reboot into recovery the mobile stucks on YU logo I think gets bricked this is what happening every time
CM11?
Any reason to sticking with CM11?
It is a 32 bit ROM and TWRP you're trying to flash is 64 bit. It won't get flashed ever.
Better install COS12.1 or any other custom ROMs.
There is no any specific reason for sticking with cm11 I thought it is most stable.
So is there any way I can flash twrp?
Or do I have to upgrade to cm 12.1 and then try to flash?
Can you recommend me any rom with better stability for yureka?
First try to upgrade to COS12.1 and than flash TWRP.
There are lots of N custom ROMs available and is stable. You can find more about them here or at YU Forum.
minestrome said:
There is no any specific reason for sticking with cm11 I thought it is most stable.
So is there any way I can flash twrp?
Or do I have to upgrade to cm 12.1 and then try to flash?
Can you recommend me any rom with better stability for yureka?
Click to expand...
Click to collapse
Flash Cos12.1 via fastboot, as it will change ur architecture from 32bit to 64bit...
Then check bootloader status, and if locked, unlock it as well, flash TWRP and enjoy custom ROMs,
Nougat ROMs are much stable now
For any problem, feel free to ask,
Thank YOU
thanks
Thank you very much guys , your help is very very appreciated.
The fingerprint was working fine on stock rom. Unlocked the bootloader and flashed twrp image. Somehow I formatted the internal storage erasing everything. After that, I flashed Pixel Experience custom rom and the fingerprint scanner isn't working. Getting "fingerprint enrollment issue". The enrollment happens only when I try pressing it very hard and I didn't face the issue on stock rom. I tried every custom rom available my bad. Somehow registered the edge of the finger and its working for now. What is the issue, I don't think it is hardware issue Any fixes for the same?
+1
ajeteja said:
The fingerprint was working fine on stock rom. Unlocked the bootloader and flashed twrp image. Somehow I formatted the internal storage erasing everything. After that, I flashed Pixel Experience custom rom and the fingerprint scanner isn't working. Getting "fingerprint enrollment issue". The enrollment happens only when I try pressing it very hard and I didn't face the issue on stock rom. I tried every custom rom available my bad. Somehow registered the edge of the finger and its working for now. What is the issue, I don't think it is hardware issue Any fixes for the same?
Click to expand...
Click to collapse
By any chance were you on the Oreo soak test when last on Stock rom? If so, the blobs wouldn't be compatible. Confirm whether or not that was the case, and if it is, then I'll point you in the right direction.
Yes I was on soak test. Pls help Moto g5s plus
---------- Post added at 10:47 AM ---------- Previous post was at 10:46 AM ----------
NZedPred said:
By any chance were you on the Oreo soak test when last on Stock rom? If so, the blobs wouldn't be compatible. Confirm whether or not that was the case, and if it is, then I'll point you in the right direction.
Click to expand...
Click to collapse
Yes I was on soak test. Pls help Moto g5s plus
@NZedPred Can you pls help? I am also facing the same issue.
#shubham Bane/- said:
Yes I was on soak test. Pls help Moto g5s plus
---------- Post added at 10:47 AM ---------- Previous post was at 10:46 AM ----------
Yes I was on soak test. Pls help Moto g5s plus
Click to expand...
Click to collapse
kiranbala003 said:
@NZedPred Can you pls help? I am also facing the same issue.
Click to expand...
Click to collapse
Taken from the Oreo thread:
Important information if downgrading to Nougat and Custom Oreo roms
The Oreo roms will change the ownership of specific files and folders in the /persist folder. As a result of this, stock Nougat will have issues such as lost IMEI, no Volte, no 4G, etc. In order to overcome these issues, either follow the instructions in the link above, or flash the following zip in TWRP.
potter-stock-persist-fix.zip
Another potential issue is that, as a result of various partitions being updated, the new Oreo blobs may not be compatible with existing Nougat roms (stock or custom), or even current Custom Oreo roms. This may result in issues such as the fingerprint reader not working, etc. To ensure they run correctly, it is MANDATORY to install one of the latest Stock Nougat TWRP flashables. This will ensure that all affected partitions are compatible with Stock Nougat and Custom Oreo roms. You can get these from this thread here:
[Nougat][Stock][Rom] TWRP Flashable Stock Builds
So flash the persist fix from the first link, and flash the latest Nougat stock rom from the second. Reboot and make sure all is working OK in stock. Then flash whichever custom rom you want.
NZedPred said:
Taken from the Oreo thread:
Important information if downgrading to Nougat and Custom Oreo roms
The Oreo roms will change the ownership of specific files and folders in the /persist folder. As a result of this, stock Nougat will have issues such as lost IMEI, no Volte, no 4G, etc. In order to overcome these issues, either follow the instructions in the link above, or flash the following zip in TWRP.
potter-stock-persist-fix.zip
Another potential issue is that, as a result of various partitions being updated, the new Oreo blobs may not be compatible with existing Nougat roms (stock or custom), or even current Custom Oreo roms. This may result in issues such as the fingerprint reader not working, etc. To ensure they run correctly, it is MANDATORY to install one of the latest Stock Nougat TWRP flashables. This will ensure that all affected partitions are compatible with Stock Nougat and Custom Oreo roms. You can get these from this thread here:
[Nougat][Stock][Rom] TWRP Flashable Stock Builds
So flash the persist fix from the first link, and flash the latest Nougat stock rom from the second. Reboot and make sure all is working OK in stock. Then flash whichever custom rom you want.
Click to expand...
Click to collapse
@NZedPred thanks man. It worked
kiranbala003 said:
@NZedPred thanks man. It worked
Click to expand...
Click to collapse
hi, i am also facing the same issue. fingerprint lock disappeared after i flash a AEX custom rom from stock oreo soak test in my moto g5 plus (potter).
could you please provide the setp by step procedure to fix my issue thanks a lot
ugander1989 said:
hi, i am also facing the same issue. fingerprint lock disappeared after i flash a AEX custom rom from stock oreo soak test in my moto g5 plus (potter).
could you please provide the setp by step procedure to fix my issue thanks a lot
Click to expand...
Click to collapse
Step by step instructions are in my post above... Do you have a more specific question?
Does this work with moto G5s plus [sanders]
Will the above method work with moto g5s plus sanders
sarath6622 said:
Will the above method work with moto g5s plus sanders
Click to expand...
Click to collapse
Yes, if you did the same thing, i.e. flashed stock Oreo and then went to an Oreo custom rom, then yes the same approach will work. I have a flashable build and persist fix for sanders here:
https://www.androidfilehost.com/?w=files&flid=280579
Clean flash/Dirty flash?
@NZedPred I am facing the same problem. I own the Indian Moto G5 Plus (retin)
Here's what I did -
1. I unlocked my bootloader
2. I updated to Oreo (soak test) using the OTA capture.
2. I somehow rooted my phone after flashing TWRP.
3. Just after I flashed TWRP i.e. before rooting, I took a complete backup including the persist and EFS partitions.
4. After rooting, I clean installed MSM-Xtended ROM (8.1.0)
5. Everything is fine, but the fingerprint feature doesn't work/appear anywhere. Even the gesture support is gone.
What do I need to do?
If I follow your steps mentioned above i.e. flashing the persist-fix first, flashing the Nougat ROM you provided and then flashing any custom ROM, how should I proceed?
I am really confused whether I should clean flash (Wipe Data, System, Cache) after every step or dirty flash everything.
Please guide me.
Before you go back to custom ROM from stock Oreo ROM you have to flash stock nouget ROM if not fingerprint , NFC will not work.
NZedPred said:
Taken from the Oreo thread:
Important information if downgrading to Nougat and Custom Oreo roms
The Oreo roms will change the ownership of specific files and folders in the /persist folder. As a result of this, stock Nougat will have issues such as lost IMEI, no Volte, no 4G, etc. In order to overcome these issues, either follow the instructions in the link above, or flash the following zip in TWRP.
potter-stock-persist-fix.zip
Another potential issue is that, as a result of various partitions being updated, the new Oreo blobs may not be compatible with existing Nougat roms (stock or custom), or even current Custom Oreo roms. This may result in issues such as the fingerprint reader not working, etc. To ensure they run correctly, it is MANDATORY to install one of the latest Stock Nougat TWRP flashables. This will ensure that all affected partitions are compatible with Stock Nougat and Custom Oreo roms. You can get these from this thread here:
[Nougat][Stock][Rom] TWRP Flashable Stock Builds
So flash the persist fix from the first link, and flash the latest Nougat stock rom from the second. Reboot and make sure all is working OK in stock. Then flash whichever custom rom you want.
Click to expand...
Click to collapse
I was also in the same problem of fingerprint not working. Tried your method i.e. flashed persist zip and nougat rom (after wiping dalvik, system ,data, cache) and now when I try to clean flash custom Oreo rom . Gapps is not getting flashed . Its detecting the rom as 7.1.2. any solution for this
navinsingh said:
I was also in the same problem of fingerprint not working. Tried your method i.e. flashed persist zip and nougat rom (after wiping dalvik, system ,data, cache) and now when I try to clean flash custom Oreo rom . Gapps is not getting flashed . Its detecting the rom as 7.1.2. any solution for this
Click to expand...
Click to collapse
@sinchan_nohara
navinsingh said:
I was also in the same problem of fingerprint not working. Tried your method i.e. flashed persist zip and nougat rom (after wiping dalvik, system ,data, cache) and now when I try to clean flash custom Oreo rom . Gapps is not getting flashed . Its detecting the rom as 7.1.2. any solution for this
Click to expand...
Click to collapse
U wrongly flashed firmware, try Oreo custom rom
NZedPred said:
Taken from the Oreo thread:
Important information if downgrading to Nougat and Custom Oreo roms
The Oreo roms will change the ownership of specific files and folders in the /persist folder. As a result of this, stock Nougat will have issues such as lost IMEI, no Volte, no 4G, etc. In order to overcome these issues, either follow the instructions in the link above, or flash the following zip in TWRP.
potter-stock-persist-fix.zip
Another potential issue is that, as a result of various partitions being updated, the new Oreo blobs may not be compatible with existing Nougat roms (stock or custom), or even current Custom Oreo roms. This may result in issues such as the fingerprint reader not working, etc. To ensure they run correctly, it is MANDATORY to install one of the latest Stock Nougat TWRP flashables. This will ensure that all affected partitions are compatible with Stock Nougat and Custom Oreo roms. You can get these from this thread here:
[Nougat][Stock][Rom] TWRP Flashable Stock Builds
So flash the persist fix from the first link, and flash the latest Nougat stock rom from the second. Reboot and make sure all is working OK in stock. Then flash whichever custom rom you want.
Click to expand...
Click to collapse
dhinesh_cool said:
U wrongly flashed firmware, try Oreo custom rom
Click to expand...
Click to collapse
can you please guide me to install a custom oreo rom. because when i try to flash custom oreo rom (franken rom i used) , the rom gets flashed but the gapps (arm64 mini 8.1.x) fails everytime and shows error code 20 (incompatible rom). but i had flashed both the rom and the gapps successfully before the fingerprint issue bcoz of which i had to flash the stock 7.0 with the persist fix. and one more thing the rom is getting flashed succesfully (as twrp shows me) but when i try to boot into system without the gapps installed( i.e. only with the rom) it gets stuck on the bootloader page so i think the rom itself is not getting flashed. please help......
navinsingh said:
can you please guide me to install a custom oreo rom. because when i try to flash custom oreo rom (franken rom i used) , the rom gets flashed but the gapps (arm64 mini 8.1.x) fails everytime and shows error code 20 (incompatible rom). but i had flashed both the rom and the gapps successfully before the fingerprint issue bcoz of which i had to flash the stock 7.0 with the persist fix. and one more thing the rom is getting flashed succesfully (as twrp shows me) but when i try to boot into system without the gapps installed( i.e. only with the rom) it gets stuck on the bootloader page so i think the rom itself is not getting flashed. please help......
Click to expand...
Click to collapse
ask in telegram grp
hey ! i want to flash fastboot rom , currently im on custom rom. please tell me what is the latest firmware for indian varrient & link also of firmware.
If you're on a custom rom, and that rom is an Oreo rom, you will need to apply the persist fix to make sure you don't have any problems when moving to stock (e.g. lost IMEI, no Volte, no 4G, etc). For the guide here:
https://forum.xda-developers.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147
If you know what you're doing, here's a link to NPNS25.137-92-14, the latest for the retin channel.
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Edit: Also, do you really need the fastboot roms? Unless you're looking to lock your bootloader, maybe you'll be fine with the TWRP flashable stock roms - available for both Nougat and Oreo (soak test, not yet official).
NZedPred said:
If you're on a custom rom, and that rom is an Oreo rom, you will need to apply the persist fix to make sure you don't have any problems when moving to stock (e.g. lost IMEI, no Volte, no 4G, etc). For the guide here:
https://forum.xda-developers.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147
If you know what you're doing, here's a link to NPNS25.137-92-14, the latest for the retin channel.
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Edit: Also, do you really need the fastboot roms? Unless you're looking to lock your bootloader, maybe you'll be fine with the TWRP flashable stock roms - available for both Nougat and Oreo (soak test, not yet official).
Click to expand...
Click to collapse
Thanks for your reply bro , one last ques is it worthy to move to proper stock again?? or flashable builds are better ?
zooreo said:
Thanks for your reply bro , one last ques is it worthy to move to proper stock again?? or flashable builds are better ?
Click to expand...
Click to collapse
Comes down to what you want to do with your phone. If you want to keep root access, then you may as well stick with the TWRP flashables, as the full stock firmware will not install OTAs if you are rooted. Quite often the TWRP flashable builds will be available sooner than a lot of people receive OTAs through official channels. That is, once one person receives the OTA and shares it with me, I build the next flashable zip normally within a couple of days (I'm the maintainer). The modifications are minimal - just disabling dm-verity and forced encryption (the latest Oreo flashables built on the Aroma installer make that optional).
If you want to lock the bootloader for any reason (e.g. in order to sell your phone, or you want to ensure the highest level of security) then you only really have one choice - full fastboot stock.
Anyway, you can have a read in the two threads for Nougat and Oreo:
[Nougat][Stock][Rom] TWRP Flashable Stock Builds
[Oreo][Stock][Rom] TWRP Flashable Stock Builds