Database Users

[ROM][GPe] Android 5.0.1 Update - Lollipop (OTA from Google)

My GPe m7 just got the update notification. I pulled the file from /cache, and here it is.
The SHA1 checksum is in the filename, bad1c593ad07005d8e82754c36caa7e7db9b6cc2. This is not a test release or a beta, so as far as I can tell, I'm the first uploader! My phone is the international m7, running 4.4.4.
NOTE: this is an OTA from 4.4.4 to 5.0.1. It requires the stock recovery from 4.4.4, and so will cannot be installed by people that rooted or manually converted their phone to the Google Play edition. (This means me, in fact. I can't install this! But I'm uploading it in the hopes that a developer can apply the patches manually and make a flashable ROM.) This includes firmware, so installing as a Nandroid backup may or may not work.
EDIT: people in this thread have already uploaded the file and are trying to install it. I suggest browsing there, because here in this thread we haven't figured it out yet!

Can you post a nandroid

Thealshear said:
Can you post a nandroid
Click to expand...
Click to collapse
Plssssssssss system partition

@poon
PLEEAAASSSSEE KERNEL

Link is diwn unfortunately. Dropbox disabled it because it caused to much traffic

I have it. Anyone intrested?
Attached is a picture of the files in the ZIP

WiiiLDFARMER said:
Link is diwn unfortunately. Dropbox disabled it because it caused to much traffic
Click to expand...
Click to collapse
Link has been changed to androidfilehost, so you can try again. And unfortunately, the installer requires the stock GPe recovery, version 4.4.4. Does anyone know where to find that? I found 4.4.2's recovery by searching the internet, but that doesn't help.

wittereuzz said:
@poon
PLEEAAASSSSEE KERNEL
Click to expand...
Click to collapse
Need the Rom first downloading haha

TheRinseM said:
I have it. Anyone intrested?
Attached is a picture of the files in the ZIP
Click to expand...
Click to collapse
If that is a nandroid, yes, yes I am very interested
---------- Post added at 09:40 PM ---------- Previous post was at 09:39 PM ----------
poondog said:
Need the Rom first downloading haha
Click to expand...
Click to collapse
Make sure you grab a nandroid for me, I need this gpe goodness now

I have an initial stock"ish" kernel done already, but still need a nandroid/system dump, I can't flash Gsm as is.
Or I prefer not to anyways...
I'm sure poon won't let you guys down, but he has to have the rom to even test on first, haha.
As do I.
Stock OTA straight from Google is here: LINK

fenstre said:
Link has been changed to androidfilehost, so you can try again. And unfortunately, the installer requires the stock GPe recovery, version 4.4.4. Does anyone know where to find that? I found 4.4.2's recovery by searching the internet, but that doesn't help.
Click to expand...
Click to collapse
Thanks! Downloading now.

Kernel source is up at htcdev also...

how i can convert my htc one m7 sense 4.4.3 to a GPE Lollipop?
here some links to ota download
h**ps://twitter.com/LlabTooFeR/status/540777540907200512
h**ps://twitter.com/LlabTooFeR/status/540743784179724289
i dont know if works

me too but cant wait did try lollipop cm12 but returned to old Carbonrom so i could use your latest cm kernel v32 i think it lasts almost 40 hrs with 3 hours screen on time

Looks like I'm behind the game! The people in this thread are already trying to figure out how to install this: http://forum.xda-developers.com/showthread.php?p=57266830#post57266830

on cm12 i have gotten 3 hours and 2 minutes screen on time before i decided to put it on charge at 3% battery

For which CID is this OTA? GOOGL001?

Bruce666 said:
For which CID is this OTA? GOOGL001?
Click to expand...
Click to collapse
just use supercid which is 111111

dc959 said:
just use supercid which is 111111
Click to expand...
Click to collapse
Actually, supercid is 11111111 (8 1's)

i manually converted to GPe and flashed this OTA

Solution for Redmi Note 3 Volte issue

http://en.miui.com/forum.php?mod=viewthread&tid=402767&mobile=2
A little backgroud:Like most of the users of Redmi Note 3,I have been at wits end to get volte working on the recent versions of global developer rom.Post 6.9.22 I wasn't able to use volte and since the feature was essential to me,I would revert back to 6.9.22 global developer rom.
Soultion:Here is an easy way that would help you guys to get volte up and running on the recent versions of MIUI.I backed up my 6.9.22 rom using TWRP ZCX,since I had volte working on it.I installed the version 6.10.27(since it was on my laptop,tested on 6.11.3 as well..screenshot enclosed)using TWRP ZCX,then restored the modem and efs from 6.9.22 that I had backed up.Volte is up and running.No issues so far.Will update this if I face any issues.
Result so far:Volte is working flawlessly on 6.11.3.In fact it is better than in 6.9.22,where you had to delete the APN to get volte.Also no issue of data being on at the time of volte,like it was in some earlier builds.Posting a screenshot as well.

Anyway to install 6.11.3 using twrp ??

i havnt faced any volte issue, m always on latest beta.

tharmor said:
Anyway to install 6.11.3 using twrp ??
Click to expand...
Click to collapse
I will recommend TWRP ZCX as I have tried it multiple times.Most recently I flashed 6.11.3 yesterday.On TWRP alka I got a soft brick.So I can't say if TWRP will work properly.

c_/\/\_k said:
i havnt faced any volte issue, m always on latest beta.
Click to expand...
Click to collapse
Well then you must be a luck guy.Do you clean flash always?

mmnspeed said:
Well then you must be a luck guy.Do you clean flash always?
Click to expand...
Click to collapse
never, i love my userdata, so i always prefer dirty flash, and all the system mods again n again.
---------- Post added at 10:32 AM ---------- Previous post was at 10:30 AM ----------
tharmor said:
Anyway to install 6.11.3 using twrp ??
Click to expand...
Click to collapse
either you flash boot image patcher or use modified recovery.

c_/\/\_k said:
never, i love my userdata, so i always prefer dirty flash, and all the system mods again n again.
Click to expand...
Click to collapse
There is a minority of people on MIUI forums also who say what you are saying.I have even tried clean flashing on my device,but it doesn't work.As I said you are the lucky few.For the rest of us it has been 6.9.22 all the way.At least till yesterday.Hopefully the developers will find a permanent fix.I am not complaining as the fix I posted yesterday is working flawlessly.

mmnspeed said:
There is a minority of people on MIUI forums also who say what you are saying.I have even tried clean flashing on my device,but it doesn't work.As I said you are the lucky few.For the rest of us it has been 6.9.22 all the way.At least till yesterday.Hopefully the developers will find a permanent fix.I am not complaining as the fix I posted yesterday is working flawlessly.
Click to expand...
Click to collapse
anyways i barely use miui forum so no idea about it, and builds are perfectly fine because we all downlods frm same servers, issue may be device specific or may b large batch of devices are affected frm it, btw global beta releases for RN3 qualcom were suspended after 6.10.13 bcoz few major bugs have been reported on few of the devices, may be you r one of them.

c_/\/\_k said:
never, i love my userdata, so i always prefer dirty flash, and all the system mods again n again.
---------- Post added at 10:32 AM ---------- Previous post was at 10:30 AM ----------
either you flash boot image patcher or use modified recovery.
Click to expand...
Click to collapse
c_/\/\_k said:
anyways i barely use miui forum so no idea about it, and builds are perfectly fine because we all downlods frm same servers, issue may be device specific or may b large batch of devices are affected frm it, btw global beta releases for RN3 qualcom is suspended after 6.10.13 bcoz few major bugs have been reported on few of the devices, may be you r one of them.
Click to expand...
Click to collapse
I myself suspect the same.Maybe some differences in device hardware.Global dev 6.11.3 has been released yesterday for Redmi Note 3 after being suspended for a few weeks.I was on 6.9.22 and initially downloaded the ota zip and dirty flashed it.Lost volte.Then reverted to 6.9.22 and decided to do something.lol.Can you tell me which version you last used fast boot ROM of?Just curious.I just yesterday saw a mod telling a poster that volte is working fine on beta 6.9.22 and global stable 8.0.6(haven't tried that..tried 8.0.5 but volte wasn't working).They are well aware of the issue.That confirms that there is one.
PS:Also if you dirty flash to 6.11.3,please do post your experience here.Whether volte works normally.

mmnspeed said:
I myself suspect the same.Maybe some differences in device hardware.Global dev 6.11.3 has been released yesterday for Redmi Note 3 as well after being suspended for a few weeks.I was on 6.9.22 and initially downloaded the ota zip and dirty flashed it.Lost volte.Then reverted to 6.9.22 and decided to do something.lol.Can you tell me which version you last used fast boot ROM of?Just curious.I just yesterday saw a mod telling a poster that volte is working fine on beta 6.9.22 and global stable 8.0.6(haven't tried that..tried 8.0.5 but volte wasn't working).They are well aware of the issue.That confirms that there is one.
PS:Also if you dirty flash to 6.11.3,please do post your experience here.Whether volte works normally.Since you are on 6.10.13,it will be a full update,around 1.3Gb.
Click to expand...
Click to collapse
as i can see in screenshot above, you are using 2 gb variant, and i use 3gb variant, we are on different soc so it quite obivous that we will have different experiences. i still wonder wat kind of problem you are talking about because i never suspected anything like that.. i flashed 6.8.x as a last fastboot rom, afterwards i do dirty flashes, i used boot image patcher previously but nw i do it with zcx twrp. and 6.9.22 was quite stable build for me.. i didnt noticed any bug in anything. i hv jst flashed 6.11.3, its booted up, and seems fine to me as well.
Edit: Everytime i flash beta builds, i need to flash super su, xposed, few mod zips as well... and i have toremove bloatwares and few xiaomi core apps too everytime.. after all these efforts the rom becomes so smooth and fast to play with.

c_/\/\_k said:
as i can see in screenshot above, you are using 2 gb variant, and i use 3gb variant, we are on different soc so it quite obivous that we will have different experiences. i still wonder wat kind of problem you are talking about because i never suspected anything like that.. i flashed 6.8.x as a last fastboot rom, afterwards i do dirty flashes, i used boot image patcher previously but nw i do it with zcx twrp. and 6.9.22 was quite stable build for me.. i didnt noticed any bug in anything. i hv jst flashed 6.11.3, its booted up, and seems fine to me as well.
Click to expand...
Click to collapse
I didn't know you have a 3Gb variant.One thing is clear to me now that there is a definite issue with certain devices and I own one of them.As is evident we have a slightly different hardware configuration.But thankfully not a big deal now as I have it working flawlessly and xiaomi can take its own sweet time.Enjoy the new update.

RETUS Nougat OTA (discussion, root, setups, etc.)

Hey guys,
Not much of a poster but it seems the retus guys are left out in discussions involving flashing our firmware...
I present the official nougat OTA I received for RETUS only. This has the January security patch (vanilla android yet we are still behind security patches...nice Lenovo...).
For those sideloading this and are still on MM, you'll just need to adb sideload the file. Keep in mind that I received my OTA update on a November security patch, so it may not mater at all which patch you have.
RETUS NOUGAT OTA (Mega link)​
Preparation:
For those who rooted and caused a bunch of hell on your system partition, you can grab some stock unsigned firmware here and revert what you did. Fastboot flash the boot, sparsechunks (in order), recovery, and oem images (then reboot back to bootloader to choose recovery mode). You can now finally sideload it flawlessly without losing any data. If you need more information you can check out one the revert to stock firmware guides, I'm not going to post something repetitive.
Root options:
You want root? You have two options...first you obviously need TWRP.
flash a custom ROM
flash this gentleman's (tomparr) custom kernel over on his thread and then flash superSU or Magisk. You can flash both SuperSU and Magisk but you could also just flash Magisk which comes with it's own systemless root.
Revert?
You can reflash MM images but I suggest using something more autonomous like this flashing tool by core720 since there's a lot more commands involved to officially downgrade. There's also an edit of the downgrade bat script in the comments of the thread which I suggest to use instead.
Viper4Android!? Atmos!?
There are currently magisk modules that work (both arise and independent ones).

I am also on the Nov. security and got the notice today of the update being available and twice after what I believe it to be successful it boots back up and tells me there was an error and nothing was updated. So thanks I guess I have no choice but to try to side-load this. Would love to know why it failed to update after being downloaded though.

I am on July security patch and just got the prompt so don't think patch level matters

xantanion said:
I am on July security patch and just got the prompt so don't think patch level matters
Click to expand...
Click to collapse
Please let me know if yours updates, mine has failed four times today already.

Jimi Mack said:
Please let me know if yours updates, mine has failed four times today already.
Click to expand...
Click to collapse
Mine went flawlessly

Jimi Mack said:
I am also on the Nov. security and got the notice today of the update being available and twice after what I believe it to be successful it boots back up and tells me there was an error and nothing was updated. So thanks I guess I have no choice but to try to side-load this. Would love to know why it failed to update after being downloaded though.
Click to expand...
Click to collapse
Jimi Mack said:
Please let me know if yours updates, mine has failed four times today already.
Click to expand...
Click to collapse
I'm not sure where you're coming from, have you ever altered your system partition? If you sideload through recovery, you would be able to see the recovery log and see the error it shows each time rather than having the OTA handled through the OTA client.

DroneDoom said:
I'm not sure where you're coming from, have you ever altered your system partition? If you sideload through recovery, you would be able to see the recovery log and see the error it shows each time rather than having the OTA handled through the OTA client.
Click to expand...
Click to collapse
Tried booting into Recovery to see such logs, all I get is "No Command." I picked this phone up 2nd hand, I am going to assume system partition was altered as the unit was already unlocked but showing to be stock. I am best at this point maybe just installing TWRP and working with what roms are available.
---------- Post added at 07:12 PM ---------- Previous post was at 07:10 PM ----------
xantanion said:
Mine went flawlessly
Click to expand...
Click to collapse
You installed this downloaded OTA or did you get yours OTA? Thanks.

Jimi Mack said:
Tried booting into Recovery to see such logs, all I get is "No Command." I picked this phone up 2nd hand, I am going to assume system partition was altered as the unit was already unlocked but showing to be stock. I am best at this point maybe just installing TWRP and working with what roms are available.
---------- Post added at 07:12 PM ---------- Previous post was at 07:10 PM ----------
You installed this downloaded OTA or did you get yours OTA? Thanks.
Click to expand...
Click to collapse
Got my OTA today and had no issues. Just got the phone brand new yesterday as well

Jimi Mack said:
Tried booting into Recovery to see such logs, all I get is "No Command." I picked this phone up 2nd hand, I am going to assume system partition was altered as the unit was already unlocked but showing to be stock. I am best at this point maybe just installing TWRP and working with what roms are available.
---------- Post added at 07:12 PM ---------- Previous post was at 07:10 PM ----------
You installed this downloaded OTA or did you get yours OTA? Thanks.
Click to expand...
Click to collapse
To unlock the stock recovery menu, bring up that 'no command' instance again and hold the power button and double tap the vol+ while still holding the power button. It's tricky, you may need to press them both at once or just play around with it until you see the menu.

DroneDoom said:
To unlock the stock recovery menu, bring up that 'no command' instance again and hold the power button and double tap the vol+ while still holding the power button. It's tricky, you may need to press them both at once or just play around with it until you see the menu.
Click to expand...
Click to collapse
Thanks, I was able to get into it, but the sad part is I have no idea on what I am looking at, that might as well been a foreign language...lol. I saw several error logs, but as I said, no idea on what I was looking at. I did not know what to expect but was kind of hoping for a red lag or something that said "hey schmuck loot at this. "

Jimi Mack said:
Thanks, I was able to get into it, but the sad part is I have no idea on what I am looking at, that might as well been a foreign language...lol. I saw several error logs, but as I said, no idea on what I was looking at. I did not know what to expect but was kind of hoping for a red lag or something that said "hey schmuck loot at this. "
Click to expand...
Click to collapse
If you invested in some Z mods and want them working (battery packs work but there's no software indication of charge or anything) you may have to flash some stock images to get everything sorted out. If you don't care then by all means you can use a custom nougat rom, the MM modem and radios still work even on a nougat rom.

DroneDoom said:
If you invested in some Z mods and want them working (battery packs work but there's no software indication of charge or anything) you may have to flash some stock images to get everything sorted out. If you don't care then by all means you can use a custom nougat rom, the MM modem and radios still work even on a nougat rom.
Click to expand...
Click to collapse
Hopefully at sometime there is a stock N rom I can flash from TWRP on a MM base.
Or I can try side loading yours and hope that works.
Question: What is the differences in the two "unsigned firmware" in the 1st post?

Just got the update when I checked manually (Consumer Cellular RETUS Unlocked)
First impression: What an... interesting boot animation.

Jimi Mack said:
Hopefully at sometime there is a stock N rom I can flash from TWRP on a MM base.
Or I can try side loading yours and hope that works.
Question: What is the differences in the two "unsigned firmware" in the 1st post?
Click to expand...
Click to collapse
I think there may be a difference in security patches but they have the same build number so I'm not too sure.
holabola said:
Just got the update when I checked manually (Consumer Cellular RETUS Unlocked)
First impression: What an... interesting boot animation.
Click to expand...
Click to collapse
Yeah it is, it reminds me of the days when I had a Motorola razr lol.

For anyone that was wondering, the display size scaling works PERFECTLY.
I originally changed the DPI to make everything smaller, but it led to a lot of random issues with other apps (mainly involving the camera). The display size scaling mimics the effects of a DPI change right out of the box without all the issues and need for a computer (I wasn't rooted so)
Also, when I got the update, I was on the December 1st security patch.

DroneDoom said:
This has the January security patch (vanilla android yet we are still behind security patches...nice Lenovo...).
Click to expand...
Click to collapse
Yeah motoblur might look like stock android, but it is very different under the hood. This is also the first 32-bit nougat phone in existence, and certainly the first nougat phone on the snapdragon 625. This phone is also unique in that it has to work with all of the Moto mods (none of the aosp Roms in the "ROMs" section work with Moto mods, so this probably wasn't trivial to add). For such a unique phone, we got updated pretty quickly. We got nougat before the Axon 7 (advertised as "daydream compatible" for +6 months before updated to 7.0) and plenty of other phones. It's not a nexus or a Oneplus, but Moto did good considering this isn't a flagship (although to most of us, it is).
DroneDoom said:
Magisk
Click to expand...
Click to collapse
Just want to be clear, Magisk v11 will brick on nougat. V12 works perfectly. I've got a whole thread dedicated to Magisk on nougat and was finally able to pass safetynet using s3v3n's 3.0.1 build and the latest v12 Magisk. Did not flash supersu or ARISE.

xxBrun0xx said:
Yeah motoblur might look like stock android, but it is very different under the hood. This is also the first 32-bit nougat phone in existence, and certainly the first nougat phone on the snapdragon 625. This phone is also unique in that it has to work with all of the Moto mods (none of the aosp Roms in the "ROMs" section work with Moto mods, so this probably wasn't trivial to add). For such a unique phone, we got updated pretty quickly. We got nougat before the Axon 7 (advertised as "daydream compatible" for +6 months before updated to 7.0) and plenty of other phones. It's not a nexus or a Oneplus, but Moto did good considering this isn't a flagship (although to most of us, it is).
Just want to be clear, Magisk v11 will brick on nougat. V12 works perfectly. I've got a whole thread dedicated to Magisk on nougat and was finally able to pass safetynet using s3v3n's 3.0.1 build and the latest v12 Magisk. Did not flash supersu or ARISE.
Click to expand...
Click to collapse
Thanks for the feedback (fixed op), I noticed v11 doesn't patch the kernel correctly and the ROM tries to boot without it. I thought it was just me since I was playing around trying to change my cache partition to f2fs but I guess the kernel doesn't support that filesystem for cache (ROM boots but doesn't initialize).
S3v3n's ROM is based on firmware stock right? I tried magisk with V4A module but it doesn't work and Atmos somehow bricks stock but it doesn't brick on a ROM built from different source (works on xperience). I noticed today that the ARISE project has a magisk module for it's latest project so maybe there's a possibility for stock to have systemless V4A.

Question, when I am in Stock Recovery to side load the update, I ma getting this.. anyone know what Status 225 is?
Now send package you want to apply
to the device with "adb sideload ,filename>...
status 255
Installation aborted.
---------- Post added at 01:05 PM ---------- Previous post was at 01:01 PM ----------
I think I may have found the issue, in Stock Recovery, is says :motorola/addison-retail/addison
but under ABOUT PHONE on the phone it states this is on a retus channel. Conflict of information, any suggestions?

Jimi Mack said:
Question, when I am in Stock Recovery to side load the update, I ma getting this.. anyone know what Status 225 is?
Now send package you want to apply
to the device with "adb sideload ,filename>...
status 255
Installation aborted.
---------- Post added at 01:05 PM ---------- Previous post was at 01:01 PM ----------
I think I may have found the issue, in Stock Recovery, is says :motorola/addison-retail/addison
but under ABOUT PHONE on the phone it states this is on a retus channel. Conflict of information, any suggestions?
Click to expand...
Click to collapse
Addison is our phone model's codename. For instance the Moto z variants are codenamed "griffin." They each have individual builds based on a region's network range and so they are codename as well...We are RETUS (retail US) which is the channel that we get our updates from so that each device will get specifically tuned update based on the region it represents. Reteu (Europe), retbr (Brazil) etc.
As for your 255 error, there is no specific documentation about this. It may be some incompatibility error or a failed sideload based on the same error # given in TWRP and CM recoveries.

DroneDoom said:
Addison is our phone model's codename. For instance the Moto z variants are codenamed "griffin." They each have individual builds based on a region's network range and so they are codename as well...We are RETUS (retail US) which is the channel that we get our updates from so that each device will get specifically tuned update based on the region it represents. Reteu (Europe), retbr (Brazil) etc.
As for your 255 error, there is no specific documentation about this. It may be some incompatibility error or a failed sideload based on the same error # given in TWRP and CM recoveries.
Click to expand...
Click to collapse
I thank you. I got the update to begin to load, it fails and aborts at 45% . It states something about content, lists my build number and give a code 755. I can not find out anything about this one either. I guess something is screwy with what is installed on my phone and what should be...

New treble roms for Honor 8 and P9

I have seen that nobody shared this informations: openkirin is working on lineageos, resurrection remix, carbonrom and omnirom. These are treble ROMs and openkirin has published beta previews that support our device, we have fully working cameras with stock emui camera app on every rom( with all functions), every rom works perfecly, no bugs, no issues, everything works, I only faced with overheating caused by fast charger that I fixed using a normal charger. You find links on openkirin telegram group, keep in mind that these are only previews so things could be even better. (Thanks openkirin)

Fully supported Openkirin LOS b5 for honor 8 is out... Download at openkirin.net

Volte working?

annujangra said:
Volte working?
Click to expand...
Click to collapse
Not yet

Any chance of volte working??

annujangra said:
Any chance of volte working??
Click to expand...
Click to collapse
https://openkirin.net/support/

Can we enable it by a magisk module called volteenabler??

No. No volte. The openkirin team will tell you the exact same thing. And sorry but those who pay attention to xda about Oreo know these images already exist. They've been discussed here for well over a month.

I don't think the Treble ROMs are working very well. I've Tried LOS Beta 5 from openkirin's website. Factory reset using custom recovery after Flashing the LOS system image didn't work. However the ROM booted and there was some issues like, random google error message pop-ups and both the camera apps aren't working. I've tried this thoroughly by following the installation guide on their website but still had these issues. Any suggestions or help is welcomed.

You should NOT use custom recovery at all.

Alok Bajaj said:
I don't think the Treble ROMs are working very well. I've Tried LOS Beta 5 from openkirin's website. Factory reset using custom recovery after Flashing the LOS system image didn't work. However the ROM booted and there was some issues like, random google error message pop-ups and both the camera apps aren't working. I've tried this thoroughly by following the installation guide on their website but still had these issues. Any suggestions or help is welcomed.
Click to expand...
Click to collapse
Just use commands ( fastboot erase system and the Fastboot flash system ) for installing.
Graphical issues had fixed and reuploaded .Download it again :highfive:

i have Android 8, emui 4.2 and i want to flash one of these roms. Root and open bootloader is there.
Somebody has an idea what the perfect procedure to flash one of this roms is? First Oreo than the rom? Thanks

Palindrom87 said:
i have Android 8, emui 4.2 and i want to flash one of these roms. Root and open bootloader is there.
Somebody has an idea what the perfect procedure to flash one of this roms is? First Oreo than the rom? Thanks
Click to expand...
Click to collapse
You first need to update to Oreo, yes. Neither Marshmallow nor Nougat support Treble ROMs.
Depending on where you live and what model you own you probably need to rebrand though. Or you wait until Honor/Huawei rolls out the update for your region, which shouldn't take TOO long anymore.

Moh3n.B said:
Just use commands ( fastboot erase system and the Fastboot flash system ) for installing.
Graphical issues had fixed and reuploaded .Download it again :highfive:
Click to expand...
Click to collapse
I'll try. Now I'm on AOSPA 7.1

Alok Bajaj said:
I'll try. Now I'm on AOSPA 7.1
Click to expand...
Click to collapse
Just bear in mind... installation needs to be done through fastboot and not through twrp.. Also its also recommended that you extract the stock files like ramdisk etc. so that incase something goes wrong you would be able to go back to it
All the best mate.. I m running LoS B5 with Magisk and it works like a charm..

kishorev said:
Just bear in mind... installation needs to be done through fastboot and not through twrp.. Also its also recommended that you extract the stock files like ramdisk etc. so that incase something goes wrong you would be able to go back to it
All the best mate.. I m running LoS B5 with Magisk and it works like a charm..
Click to expand...
Click to collapse
Thanks for the tips. And yes I flashed via fastboot not twrp. But if you please, could you write down exact steps to flash this ROM considering I'm on EMUI 8 with stock Recovery... And what would be the exact steps that I need to do next.
Are you using Magisk 16.x? And it works with fingerprint and PIN set on the device?

Alok Bajaj said:
Thanks for the tips. And yes I flashed via fastboot not twrp. But if you please, could you write down exact steps to flash this ROM considering I'm on EMUI 8 with stock Recovery... And what would be the exact steps that I need to do next.
Are you using Magisk 16.x? And it works with fingerprint and PIN set on the device?
Click to expand...
Click to collapse
I m using the custom version of magisk.. i shall share you to the links later today when I get back from work..infact all these details are available on openkirin.net

kishorev said:
I m using the custom version of magisk.. i shall share you to the links later today when I get back from work..infact all these details are available on openkirin.net
Click to expand...
Click to collapse
Okay. I had followed the instructions on openkirin.net. However I ran into some issues that I posted recently. I'll wait for the link. Now I'm going to try RROS B2.

Alok Bajaj said:
Okay. I had followed the instructions on openkirin.net. However I ran into some issues that I posted recently. I'll wait for the link. Now I'm going to try RROS B2.
Click to expand...
Click to collapse
I'm experiencing similar things.
SD card doesn't get recognized/system says it's corrupted which is obviously isn't, root via ramdisk method works but Magisk is buggy and modules just won't install, WiFi randomly turns off or disconnects with no pattern behind it... I've tried both LOS (twice) and ROS (once) and they both have similar problems. Guess I'll have to stay on EMUI then... *sigh*

Frau Son said:
I'm experiencing similar things.
SD card doesn't get recognized/system says it's corrupted which is obviously isn't, root via ramdisk method works but Magisk is buggy and modules just won't install, WiFi randomly turns off or disconnects with no pattern behind it... I've tried both LOS (twice) and ROS (once) and they both have similar problems. Guess I'll have to stay on EMUI then... *sigh*
Click to expand...
Click to collapse
Have you tried the RROS B2? It was posted recently. It's working well for me now.

Where are the Alpha Omega ROM threads? I wanted to search them for GPS help.

Does anyone know where the Alpha Omega ROM threads are?
I'm on AO Oreo on both the US996 and VS995.
I was going to search in them for GPS issues (on the VS995), but I can't find the threads.
Anyone know where I can find some GPS help and/or AO Rom thread?

Unfortunately, it seems that the dev requested the threads to be removed, probably after being bothered too much by users, even though it was clearly stated that the work was discontinued long ago. I've only been able to find archived versions of the first pages for AO Nougat and AO Oreo. And you can still find the ROM files on AndroidFileHost here.
And FWIW, although it's not my main V20, I never had GPS issues on my US996 on AO Oreo.

C D said:
Unfortunately, it seems that the dev requested the threads to be removed, probably after being bothered too much by users, even though it was clearly stated that the work was discontinued long ago. I've only been able to find archived versions of the first pages for AO Nougat and AO Oreo. And you can still find the ROM files on AndroidFileHost here.
And FWIW, although it's not my main V20, I never had GPS issues on my US996 on AO Oreo.
Click to expand...
Click to collapse
Thanks on both acounts.

It is unfortunate the dev choose to drop his rom and no longer provide support. I still run it as my daily.

Yeah, the only problem I have with it is since Verizon rolled out a new update I lost WiFi calling on a clean install. Does anyone know a trick to make it work? Mis also considering performing the update. But I don't know what the consequences could be. I want to at least get my second v20 up and running.

Whosondephone said:
Yeah, the only problem I have with it is since Verizon rolled out a new update I lost WiFi calling on a clean install. Does anyone know a trick to make it work? Mis also considering performing the update. But I don't know what the consequences could be. I want to at least get my second v20 up and running.
Click to expand...
Click to collapse
I would advise against taking it i disable updates.

Hi somebody tried to flash this rom on f800?
Link:https://androidfilehost.com/?w=files&flid=284267

TarAntonio said:
Hi somebody tried to flash this rom on f800?
Link:https://androidfilehost.com/?w=files&flid=284267
Click to expand...
Click to collapse
I think the hybrid Oreo variant is based on the VS995 and was released before official Oreo existed for the US996. I don't own an F800, but you could probably just try the more updated VS995 version.

C D said:
I think the hybrid Oreo variant is based on the VS995 and was released before official Oreo existed for the US996. I don't own an F800, but you could probably just try the more updated VS995 version.
Click to expand...
Click to collapse
Do you mean flash directly the last of vs995 folder in link?
Downloads for : LG V20 | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com

TarAntonio said:
Do you mean flash directly the last of vs995 folder in link?
Click to expand...
Click to collapse
Yes, the latest 1.3.1 version. As always, make a backup of your current setup before trying this. And you may need to be a on a VS995 TWRP version to get the installer to work. I also heard that some users of other V20 models had problems installing Alpha Omega on TWRP versions higher than 3.2.3-4, so keep that in mind.

C D said:
Yes, the latest 1.3.1 version. As always, make a backup of your current setup before trying this. And you may need to be a on a VS995 TWRP version to get the installer to work. I also heard that some users of other V20 models had problems installing Alpha Omega on TWRP versions higher than 3.2.3-4, so keep that in mind.
Click to expand...
Click to collapse
Phoenix twrp for try?

TarAntonio said:
Phoenix twrp for try?
Click to expand...
Click to collapse
Yeah, look for the 3.2.3-4 for the VS995 under the old versions in that TWRP thread.

C D said:
Yeah, look for the 3.2.3-4 for the VS995 under the old versions in that TWRP thread.
Click to expand...
Click to collapse
Old versions for vs995 there aren't

TarAntonio said:
Old versions for vs995 there aren't
Click to expand...
Click to collapse
You can find it under the "Old versions" section and "3.2.3-4: 2018-10-18" in the first post of this thread:
https://forum.xda-developers.com/t/recovery-unofficial-twrp-3-3-1-1-2019-10-25.3720239/
Sometimes, AndroidFileHost can't find a mirror for some old files, but if you keep refreshing and trying again, a mirror should eventually show up.

C D said:
You can find it under the "Old versions" section and "3.2.3-4: 2018-10-18" in the first post of this thread:
https://forum.xda-developers.com/t/recovery-unofficial-twrp-3-3-1-1-2019-10-25.3720239/
Sometimes, AndroidFileHost can't find a mirror for some old files, but if you keep refreshing and trying again, a mirror should eventually show up.
Click to expand...
Click to collapse
Ok thanks i will try. Until now flashed without error but permanent vibration Until verizon logo but not goes on

TarAntonio said:
Ok thanks i will try. Until now flashed without error but permanent vibration Until verizon logo but not goes on
Click to expand...
Click to collapse
I think the constant vibration during boot-up is a side-effect for all VS995 ROMs, and there may not be any workaround for that. US996 ROMs don't have that problem, but I don't know how compatible they would be for the Korean models.

C D said:
I think the constant vibration during boot-up is a side-effect for all VS995 ROMs, and there may not be any workaround for that. US996 ROMs don't have that problem, but I don't know how compatible they would be for the Korean models.
Click to expand...
Click to collapse
Tried with 3 4 recovery but not goes on remains at verizon logo. Restore with one of my backup worked but vibration remains.