Related
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
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...
Please excuse my incompetence. I'm just very overwhelmed how how different things are from Nexus devices
For Nexus devices, there is a page that has stock images for every update. I can't seem to find such a page for the G5 Plus. At least not an official one. Too many outdated threads that link to outdated pages with dead download links, I can't actually find what the latest update is.
Even still, I tried to install this update https://www.getdroidtips.com/npns25-137-33-11-august-moto-g5-plus/ and I get an error in recovery saying:
E3002: Package expects build thumbprint of 7.0/NPNS25.137-33-11/11:user/release-keys or 7.0/NPNS25.137-33-5/5:user/release-keys; this device has 7.0/NPN25.137-33/35:user/release-keys.
E:Error in /sideload/package.zip
(Status 7)
Click to expand...
Click to collapse
I then tried to download this update https://www.getdroidtips.com/npns25-137-35-5-may-moto-g5-plus/ butthe download link was dead
Further, on Nexus devices, if I had a custom ROM, and there was an update to the ROM that required some updates from the official stock image, I would just flash the vendor, radio, and bootloader images extracted from the stock zip file. These update files seem to only be flashable in stock recovery. How would I be able to get these updates with a custom ROM an TWRP?
Sorry if all of this is obvious. Like I said, I'm just overwhelmed.
Yousie642 said:
Please excuse my incompetence. I'm just very overwhelmed how how different things are from Nexus devices
For Nexus devices, there is a page that has stock images for every update. I can't seem to find such a page for the G5 Plus. At least not an official one. Too many outdated threads that link to outdated pages with dead download links, I can't actually find what the latest update is.
Even still, I tried to install this update https://www.getdroidtips.com/npns25-137-33-11-august-moto-g5-plus/ and I get an error in recovery saying:
I then tried to download this update https://www.getdroidtips.com/npns25-137-35-5-may-moto-g5-plus/ butthe download link was dead
Further, on Nexus devices, if I had a custom ROM, and there was an update to the ROM that required some updates from the official stock image, I would just flash the vendor, radio, and bootloader images extracted from the stock zip file. These update files seem to only be flashable in stock recovery. How would I be able to get these updates with a custom ROM an TWRP?
Sorry if all of this is obvious. Like I said, I'm just overwhelmed.
Click to expand...
Click to collapse
Can you try the TWRP flashable builds from here?
https://forum.xda-developers.com/g5-plus/development/rom-twrp-flashable-stock-builds-t3675616
Or the fastboot ROM from here...
https://forum.xda-developers.com/g5-plus/how-to/stock-firmware-npn25-137-67-5-fastboot-t3694738
psychopac said:
Can you try the TWRP flashable builds from here?
https://forum.xda-developers.com/g5-plus/development/rom-twrp-flashable-stock-builds-t3675616
Or the fastboot ROM from here...
https://forum.xda-developers.com/g5-plus/how-to/stock-firmware-npn25-137-67-5-fastboot-t3694738
Click to expand...
Click to collapse
I'd actually seen the Fastboot thread already, but I guess in my frustration I misread the firmware version of the download in the OP as the one I was currently on, so I dismissed it as being outdated info. Silly me lol. Thanks!
Yousie642 said:
I'd actually seen the Fastboot thread already, but I guess in my frustration I misread the firmware version of the download in the OP as the one I was currently on, so I dismissed it as being outdated info. Silly me lol. Thanks!
Click to expand...
Click to collapse
From which nexus do you come?
GopalKaul said:
From which nexus do you come?
Click to expand...
Click to collapse
5x, as well as the 5 before that
Moto G5 is a pretty "plain jane" Android device, so is a Nexus device...
That is where the similarity ends, Moto/Lenovo does not provide ANY factory images and all the ones we have are leaked files, and they do not support anything after an unlock code has been issues (doesn't matter if you actually unlock it or not), and "relocking" does not return it to a true locked status like a Nexus device. Downgrading is very difficult and often requires some trickery to get accomplished, if at all.
No device is really like a Nexus as far as enthusiast support, except maybe a OnePlus.
How does this help? It doesn't... it's just some info.
Yousie642 said:
5x, as well as the 5 before that
Click to expand...
Click to collapse
On the 5..
acejavelin said:
Moto G5 is a pretty "plain jane" Android device, so is a Nexus device...
That is where the similarity ends, Moto/Lenovo does not provide ANY factory images and all the ones we have are leaked files, and they do not support anything after an unlock code has been issues (doesn't matter if you actually unlock it or not), and "relocking" does not return it to a true locked status like a Nexus device. Downgrading is very difficult and often requires some trickery to get accomplished, if at all.
No device is really like a Nexus as far as enthusiast support, except maybe a OnePlus.
How does this help? It doesn't... it's just some info.
Click to expand...
Click to collapse
I appreciate it nonetheless. Thanks! I'm actually a bit scared about the warranty now that I've unlocked it. I saw the message that popped up and mentioned it as I was getting my unlock code, but I was kinda mindlessly clicking "OK" through things and didn't realize what it actually said until it was too late :S
Yousie642 said:
I appreciate it nonetheless. Thanks! I'm actually a bit scared about the warranty now that I've unlocked it. I saw the message that popped up and mentioned it as I was getting my unlock code, but I was kinda mindlessly clicking "OK" through things and didn't realize what it actually said until it was too late :S
Click to expand...
Click to collapse
A G4 Play I have that's unlocked still gets updates. Haven't done anything with the G5+ yet.
[official] TWRP for onyx has been updated to 3.2.0-0 date: 17/11/30
please share any experiences of flashing/backup/restore and if anyone has tried successfully on oreo roms or if you encounter any kind of issue, feel free to share and comments below
official TWRP link:
https://dl.twrp.me/onyx/twrp-3.2.0-0-onyx.img.html
huge thanks to @Nachiket.Namjoshi (still as onyx's maintainer?) @Dees_Troy and all TeamWin-RecoveryProject peeps.
Seems OK for me. It installs OK.
Back up is OK.
Will see in a few days for flashing other Oreo's Roms.
Works fine for me. Flashed AOSP 8.0 and other items fine.
I'm curious what makes this an Oreo update when flashing Oreo roms on the last version of TWRP worked fine.
Tanner1294 said:
I'm curious what makes this an Oreo update when flashing Oreo roms on the last version of TWRP worked fine.
Click to expand...
Click to collapse
change logs are here
https://plus.google.com/+DeesTroy/posts/PhAUQHMXnJK
is restoring from a backup okay in this version?
there were user reports on restoration failures on other models, such as in oneplus one thread as well as twrp g+ page..
iamelton said:
is restoring from a backup okay in this version?
there were user reports on restoration failures on other models, such as in oneplus one thread as well as twrp g+ page..
Click to expand...
Click to collapse
would be much useful if you can provide links to those issues
*i cant find reported issue regarding restoration failure in official G+ and either on opo thread,
it might be device specific issue (as OP announcement: might affected some devices) but i cant guarantee, have not tried restore but other than that i can confirmed all function working ok on onyx,
maybe it should be a problem when you tried to restore backup from previous twrp version using the latest, so for kind of this crucial thing i always prepare and have 2 backed ups of my current rom from previous twrp and the other one from latest twrp,
also its unnecessary to update twrp if they've decided to stick on nougat, the update is meant/optimized for oreo
Part.0 said:
would be much useful if you can provide links to those issues
*i cant find reported issue regarding restoration failure in official G+ and either on opo thread,
it might be device specific issue (as OP announcement: might affected some devices) but i cant guarantee, have not tried restore but other than that i can confirmed all function working ok on onyx,
maybe it should be a problem when you tried to restore backup from previous twrp version using the latest, so for kind of this crucial thing i always prepare and have 2 backed ups of my current rom from previous twrp and the other one from latest twrp,
also its unnecessary to update twrp if they've decided to stick on nougat, the update is meant/optimized for oreo
Click to expand...
Click to collapse
OPO (the last 2 posts atm): https://forum.xda-developers.com/showthread.php?t=2766186&page=162
strangely i couldnt find the post in official g+ page now.. maybe its removed.. not sure..
iamelton said:
OPO (the last 2 posts atm): https://forum.xda-developers.com/showthread.php?t=2766186&page=162
strangely i couldnt find the post in official g+ page now.. maybe its removed.. not sure..
Click to expand...
Click to collapse
may be a random issue and no logs attached so what can we say? *not much details from the reports
as soon as i flashed new rom ill try to perform restore from previous backed up and ill share here how it goes
Part.0 said:
may be a random issue and no logs attached so what can we say? *not much details from the reports
as soon as i flashed new rom ill try to perform restore from previous backed up and ill share here how it goes
Click to expand...
Click to collapse
exactly cant generalise with such few reports.. could also be possibly user errors..
anyway thx a lot for your response and look forward to your success story..
installed without issue. working fine.
https://dl.twrp.me/onyx/
UPDATE: official twrp 3.2.1-0 is been available for onyx
https://dl.twrp.me/onyx/
Part.0 said:
UPDATE: official twrp 3.2.1-0 is been available for onyx
https://dl.twrp.me/onyx/
Click to expand...
Click to collapse
i tried the latest version.. backup was generated without problem, though i found a minor issue which i posted in the official thread a couple of days ago:
https://forum.xda-developers.com/showpost.php?p=74830196&postcount=190
iamelton said:
i tried the latest version.. backup was generated without problem, though i found a minor issue which i posted in the official thread a couple of days ago:
https://forum.xda-developers.com/showpost.php?p=74830196&postcount=190
Click to expand...
Click to collapse
I dont know if that should be an issue, since flashing, backup, restore are just working fine and I noticed no .md5 too for efs2 using previous 3.2.0, SHA2 check box is enabled by default in twrp but the output still .md5 in backup files, maybe @Nachiket.Namjoshi has the answers
Part.0 said:
I dont know if that should be an issue, since flashing, backup, restore are just working fine and I noticed no .md5 too for efs2 using previous 3.2.0, SHA2 check box is enabled by default in twrp but the output still .md5 in backup files, maybe @Nachiket.Namjoshi has the answers
Click to expand...
Click to collapse
yes exactly.. there was md5 file generated for efs2 with previous twrp 3.1 though.. thats why i got the question..
No issues, working fine with my onyx
No Luck for me.
Version 3.2.1-0 not work here.
BUILD E1003_15, i have to use this Version to get a ROM work.
https://forum.xda-developers.com/on...official-twrp-arsenic-kernel-oneplus-t3573644
Is there be a fix for my Version of the OPX ?
Regards
Working great
Why I'm not even able to download it ?
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.