Related
Present you with a 7.1 .1 Nougat AOSP!
Tested on E6853, released a build for Dual E6883 "NOT TESTED" try at your own risk
Install trough ADB as usual by flashing boot.img system img and userdata.img
(detailed how to in post no.2)
Note:
If you are updating from previous release, flash only system.img if you wanna keep your userdata (you will only loose gapps)
This is pure AOSP.
have tried most of it and everything has been working fine.
Improvments from 7.0:
Camera is working (Not inverted anymore)
Fingerprint is working
Auto brightness works as intended
Known bugs:
AC 5GHz wifi might not work for all.
Fingerprint might bug out for some people.
Download Here
GApps
(Use arm64 7.1)
Updated 2017-04-14
AOSP 7.1.1 rev 38
Cheers
XDA:DevDB Information
AOSP 7.1.*, ROM for the Sony Xperia Z5 Premium
Contributors
Elfmirth
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: _r7
Stable Release Date: 2016-12-18
Created 2016-12-14
Last Updated 2017-04-17
Reserved
How to:
In the ADB folder press shift key and right klick with your mouse, choose "Open Command prompt here"
Power off your phone, once it's off, press and hold volume key up, and plugg it in to your PC, now the indicator on the phone sould turn blue, that shows that the phone is in Fastboot mode.
(Check in your device manager that the sony fastboot drivers are installed)
when all that is done, in the command promt type:
Code:
fastboot flash boot "drag and drop the boot.img file"
when that is done type:
Code:
fastboot flash system "drag and drop the system.img file"
after that:
Code:
fastboot flash recovery "drag and drop the recovery.img file"
when all is done type:
Code:
fastboot reboot
and your phone will reboot, it might take longer than usual.
If you wanna install gapps and root READ!! and follow this to boot up TWRP.
When phone is booted up, turn it off again enter fastboot mode then:
1.
Code:
fastboot [U]boot[/U] TWRP.img
2. On your phone press volume up until you see that you're booting in to TWRP
Thanks a lot! I've been meaning to try building this myself. Thanks for giving me hope again for the Z5P!
e6833
thank you.
is it working for z5p Dual?
faraheed said:
thank you.
is it working for z5p Dual?
Click to expand...
Click to collapse
No so far I have only done a build for E6853, since I have One of those, but ill see if I can give Dual a try this weekend ?
e6833
Elfmirth said:
No so far I have only done a build for E6853, since I have One of those, but ill see if I can give Dual a try this weekend
Click to expand...
Click to collapse
thank you my friend, can i try it on my e6833?
faraheed said:
thank you my friend, can i try it on my e6833?
Click to expand...
Click to collapse
Ofc you can try, but to be safe wait until I have made a proper build for it ?
e6683能用吗，或者说e6653
I've noticed a bug, Wifi AC (5GHz band) doesn’t work with this ROM. i flashed the 3 imgs (Boot, system, userdata) with fastboot, then used the boot.to.TWRP to boot into TWRP and flashed GApps and SuperSU through that.
Tested and played with it for a couple hours. (E6853)
Everything seemed to work flawlessly minus performance being a little on the slow side in comparison to stock Sony Roms.
I didn't notice any issues with the 5ghz as it connected just fine and gave me 351mbps down and 26mbps up.
Im not sure if its 7.1 or an issue with the ROM but i couldn't get SU/Busybox to properly open. It kept FC even after clearing my caches.
(also, i couldnt find the asop.zip you referenced in the OP so i directly flashed all the .imgs directly)
Once we get the performance close to stock, and Camera up to par (its A LOT better, but still lacking features) this will definitely become a daily driver for me!
Lets hope Sony keeps pushing quality uploads to their aosp program!
WannaB101 said:
Tested and played with it for a couple hours. (E6853)
Everything seemed to work flawlessly minus performance being a little on the slow side in comparison to stock Sony Roms.
I didn't notice any issues with the 5ghz as it connected just fine and gave me 351mbps down and 26mbps up.
Im not sure if its 7.1 or an issue with the ROM but i couldn't get SU/Busybox to properly open. It kept FC even after clearing my caches.
(also, i couldnt find the asop.zip you referenced in the OP so i directly flashed all the .imgs directly)
Once we get the performance close to stock, and Camera up to par (its A LOT better, but still lacking features) this will definitely become a daily driver for me!
Lets hope Sony keeps pushing quality uploads to their aosp program!
Click to expand...
Click to collapse
The speed will improve over time, the first 2-3 hours and 2-3 reboots mine was a bit laggy to, but after installing pixel launcher and playing around for a few hours there is no lag at all and it's just as fast as my HTC 10 (if not faster)
FC on SU I havent had, but then again only used it for 3-4 apps but worked fine with those.
The asop.zip was a typo on my end, have removed it now (was a little to tired)
exvargos said:
I've noticed a bug, Wifi AC (5GHz band) doesn’t work with this ROM. i flashed the 3 imgs (Boot, system, userdata) with fastboot, then used the boot.to.TWRP to boot into TWRP and flashed GApps and SuperSU through that.
Click to expand...
Click to collapse
"Edit" I tried a couple of times now and the only issue I had was cus of bad reception. But then again I dont have AC router only N 5GHz
WannaB101 said:
I didn't notice any issues with the 5ghz as it connected just fine and gave me 351mbps down and 26mbps up.
Im not sure if its 7.1 or an issue with the ROM but i couldn't get SU/Busybox to properly open. It kept FC even after clearing my caches.
Click to expand...
Click to collapse
How did you flash? I tried again, fastboot flashing all 3 images then flashing gapps through the provided twrp, but still no 5G wifi.
It's a lot better than the current 6.0.1 ROM I was previously using. RAM usage was cut down by half, battery life is pretty phenomenal and everything is butter smooth. I had some camera issues in the past where the z5p could never focus on anything.
All fixed with AOSP 7.1, making it my daily driver
Great ROM, but I have some issues with fingerprint. I added them during the initial setup and now they don't work after I rebooted once, so I tried to remove and add new fingerprints but the system freezes when I try to delete them. anybody else with same issues?
KbaB.BroS said:
Great ROM, but I have some issues with fingerprint. I added them during the initial setup and now they don't work after I rebooted once, so I tried to remove and add new fingerprints but the system freezes when I try to delete them. anybody else with same issues?
Click to expand...
Click to collapse
Hmm, haven't had that issue, but I never added fingerprint during setup, only added it after setup.
exvargos said:
How did you flash? I tried again, fastboot flashing all 3 images then flashing gapps through the provided twrp, but still no 5G wifi.
Click to expand...
Click to collapse
Hmm that is wierd.
Im building a new rom atm, updated to 7.1_rev7 (from rev6) so hopefully it will fix some issues. Will be uploaded tonight if all goes well, and will upload for e6883 as well.
How is battery life for everyone? I had some massive drain on 7.0 but have had almost 3 days on one charge here (mostly standby)
Elfmirth said:
Hmm, haven't had that issue, but I never added fingerprint during setup, only added it after setup.
Hmm that is wierd.
Im building a new rom atm, updated to 7.1_rev7 (from rev6) so hopefully it will fix some issues. Will be uploaded tonight if all goes well, and will upload for e6883 as well.
How is battery life for everyone? I had some massive drain on 7.0 but have had almost 3 days on one charge here (mostly standby)
Click to expand...
Click to collapse
Battery life is much better than Sony stock ROM and everything based on it, easily lasts me one day which is what I need. Light usage keeps the phone alive for more than two days.
@Elfmirth from which stock FW version did you come from? from my experience fingerprint and other issues happens when I try flashing ROMX over a different FW than it was based of so the 5G WiFi and fingerprint might be a cause of this.
KbaB.BroS said:
@Elfmirth from which stock FW version did you come from? from my experience fingerprint and other issues happens when I try flashing ROMX over a different FW than it was based of so the 5G WiFi and fingerprint might be a cause of this.
Click to expand...
Click to collapse
The first FW I started out flashing from was 32.1.A.1.163. Then I flashed AOSP 7.0 and after that AOSP 7.1
OP Updated with rev7 for both e6853 & e6883
enjoy
Hi Elfmirth,
Thanks for your work.
Hope you keep support for the dual sim devices too. Thanks
Best Regards,
Ashray
Elfmirth said:
OP Updated with rev7 for both e6853 & e6883
enjoy
Click to expand...
Click to collapse
Haven't managed to test if it fixes the bug because I had to sleep lol.
https://github.com/Demon000/libra/commit/b5067833797cd1eb207cd976bf2419c58ca8c7ed
If anyone can test if it works, I would be very thankful.
How I did it?
Get a hex file editor.
Compile kernel with old touchscreen firmware.
Open the synaptics_biel_sharp_update.fw or synaptic_biel_auo_update.fw that have been generated in firmware/ folder in the hex editor.
Get the MIUI kernel, split it, uncompress it.
In the .fw files, the first four hex groups are magic numbers(a hex group looks like "3F"), and after that there are some common hex groups in sharp and auo firmware.
Use the hex editor to search for the common groups in the MIUI kernel, and also find the magic number before the common groups.
Use the "csplitb" program to split the the kernel binary at the newly found magic number + common groups, and strip the result to 12661 lines.
Repeat this for every common group found.
Then use the objcopy program inside the toolchain to convert the binary files to .ihex, and replace the ihex files in the firmware folder.
Done.
It is complicated, but once you get the first steps it will be easy to understand.
Although I don't know if I did a good job at explaining.
Cozmy, you are magic. Lot of thanx, Man.
Many thanks. :good:
How does one flash this?
danbrown162 said:
How does one flash this?
Click to expand...
Click to collapse
You cannot, devs that make custom roms can use it to build rom with fixed display firmware.
danbrown162 said:
How does one flash this?
Click to expand...
Click to collapse
I can post a kernel build with it later, not tested as currently I'm working on lineage os using all the vendor binaries and blobs from the nougat release.
Harrynowl said:
I can post a kernel build with it later, not tested as currently I'm working on lineage os using all the vendor binaries and blobs from the nougat release.
Click to expand...
Click to collapse
I couldn't get it to update the firmware because I was not using Xiaomi touchscreen drivers in my kernel, but the firmware itself should be working fine.
I don't want to bloat my CAF touchscreen driver so it will take me longer until I find where it fails.
Please keep us updated.
https://drive.google.com/open?id=0B9WMSJf5LSatdG5WM24zNnJPaEk
Kernel image which fixes the touchscreen problem.
PS. This kernel may use more battery, just because I didn't spend time optimizing the kernel, but rather optimizing the source-code quality, lol.
You can try flashing your original kernel to see if the fix remains.
Tested on Resurrection Remix Nougat.
EDIT: I haven't tested it on any AUO panels, as my phone has a Sharp one.
EDIT2: Flashed back the Resurrection Remix kernel and touchscreen is still fixed. Success!
Guide: backup your kernel, flash the kernel I provided, restore your old kernel.
Proof as attachment.
Cozzmy13 said:
https://drive.google.com/open?id=0B9WMSJf5LSatdG5WM24zNnJPaEk
Kernel image which fixes the touchscreen problem.
PS. This kernel may use more battery, just because I didn't spend time optimizing the kernel, but rather optimizing the source-code quality, lol.
You can try flashing your original kernel to see if the fix remains.
Tested on Resurrection Remix Nougat.
EDIT: I haven't tested it on any AUO panels, as my phone has a Sharp one.
EDIT2: Flashed back the Resurrection Remix kernel and touchscreen is still fixed. Success!
Guide: backup your kernel, flash the kernel I provided, restore your old kernel.
Proof as attachment.
Click to expand...
Click to collapse
I hope this gets implemented on next releases of our roms
solis_f said:
I hope this gets implemented on next releases of our roms
Click to expand...
Click to collapse
Just give the ROM maintainers a link to this, they will surely add it to the ROM.
Holy **** You're a hero Cozzmy13, thank you!
I just tried the image on my AUO Mi4c, and I couldn't boot TS CM13 with the kernel. The fix didn't stick after restoring the original boot partition, but I have a feeling we're very close here
I'll try flashing RR later and see what I get, I have a Nandroid backup somewhere.
Phlogistol said:
Holy **** You're a hero Cozzmy13, thank you!
I just tried the image on my AUO Mi4c, and I couldn't boot TS CM13 with the kernel. The fix didn't stick after restoring the original boot partition, but I have a feeling we're very close here
I'll try flashing RR later and see what I get, I have a Nandroid backup somewhere.
Click to expand...
Click to collapse
It's my fault, I compiled the image with RR ramdisk. It definitely works on RR Nougat, that's for sure. I have since switched to Lineage OS and the fix sticked.
I have problem . Ive installed the fix on AICP 12.1 the phone doesent boot. Returned the old kernel from backup. My phone boots but now i have problem with my hardware buttons, sometimes take 3-4 to respond to the touch. I also deleted and flashed system partititon but problem stil presist.
bankov said:
I have problem . Ive installed the fix on AICP 12.1 the phone doesent boot. Returned the old kernel from backup. My phone boots but now i have problem with my hardware buttons, sometimes take 3-4 to respond to the touch. I also deleted and flashed system partititon but problem stil presist.
Click to expand...
Click to collapse
Is the touchscreen problem fixed? If it's not then this is not my fault. If it is fixed then it's XIAOMI's fault. I will test on my device and report back. Use on-screen buttons until I do some research.
The problem was not in your update. It was from the last AICP update 23.01.2017 i installed 19.01.2017 and buttons are fine now. The touchscreen seems to be fixed iven with full wipe, going back to miui and restoring 19.01.2017 AICP.
Well, I just installed RR on my AUO mi4c, and it doesn't work. The touchscreen is broken and registers touches consistently but strangely. It even does it in recovery. I'm trying to restore my backup now.
EDIT: backup restored. Still don't know why the firmware didn't work
bankov, which flavor of mi4c do you have? Sharp or AUO?
Phlogistol said:
Well, I just installed RR on my AUO mi4c, and it doesn't work. The touchscreen is broken and registers touches consistently but strangely. It even does it in recovery. I'm trying to restore my backup now.
EDIT: backup restored. Still don't know why the firmware didn't work
bankov, which flavor of mi4c do you have? Sharp or AUO?
Click to expand...
Click to collapse
Can you explain the problem a bit more?
Did it get fixed after restoring?
Phlogistol said:
Well, I just installed RR on my AUO mi4c, and it doesn't work. The touchscreen is broken and registers touches consistently but strangely. It even does it in recovery. I'm trying to restore my backup now.
EDIT: backup restored. Still don't know why the firmware didn't work
bankov, which flavor of mi4c do you have? Sharp or AUO?
Click to expand...
Click to collapse
Mine is AUO. My touchscreen was like yours but it was from AICP update.
Basicly im not 100% shure it is fixed but i remember it couldnt register touch on the left bezel if somhere else is toched on the screen. And now is fine.
For anyone applying this from now on, the process is not reversible, because of the way the driver checks if firmware can be updated, it only wants to do upgrades, not downgrades.
Also, for anyone having problems that go away after a clean flash, they are probably not because of my fix.
If they don't go away, there is probably an updated firmware version somewhere that fixes it. I'll extract them again from the newest Nougat version.
Cozzmy13 said:
Can you explain the problem a bit more?
Did it get fixed after restoring?
Click to expand...
Click to collapse
Sure, I was a bit pressed for time yesterday
The touchscreen was inconsistent, for lack of a better word. Touches on a specific point on the screen didn't register on that location, but on some other one. It wasn't random because I could reliably reproduce this. There were also some points on the screen I couldn't reach at all. The capacitive buttons also didn't work. I'd have taken logs, but I couldn't get into developer options
I don't know exactly how this works, but the touchscreen got reversed to its original state when I managed to restore a backup of my earlier TS CM13.1 system from TWRP (I restored all available partitions). It took a few tries because of the weirdness though When I say original state, I mean it still suffers from the multitouch bug, so nothing got fixed.
Hope this is useful, but I'm stumped. Could we have different digitizers?
So I am running full stock on my Pixel that is updated to Oreo. I've read through the latest thread (HERE) on the new beta for Magisk that supports Pixel devices and wanted to know what steps folks may have followed to get this installed and working. The regular thread details some steps but it appears that those are driven towards other devices and doesn't account for the difference of Pixel devices.
Thx!
loaded up fine on my pixel!
eqbirvin said:
loaded up fine on my pixel!
Click to expand...
Click to collapse
Are you able to share the steps you took to get it loaded? It would seem that it isn't the same as other or previous version since those didn't apply to pixel devices.
Thx
Do modules work?
There's an offical Magisk Pixel (XL) Thread
I'm running it on Pure Nexus July build now. I ended up having to re-flash (dirty) the ROM to clear up the old goodwin_c Magisk install.
Seems okay for now. I have a couple of modules loaded but haven't had the opportunity to test whether they actually work. AirAudio at least doesn't fire a warning that the module isn't found.
There is a new update today. Mods were broken. Supposedly fixed now.
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589/post73966889
Steps on 8.0 were as follows
make sure youre on stock boot
boot into system once with stock boot
then boot into android 0 twrp
flash magisk
reboot to system
finished
Stock Rom ZIPs for Verizon Orbic Wonder
Here's stock ROM zips for the Verizon variant Orbic Wonder. I wouldn't flash this on a vanilla Wonder if I were you, it might screw stuff up. One's a completely stock ROM and the other's pretty much just a normal stock ROM with some debloating here and there. Made using /system and /boot images pulled from a Verizon Orbic, and repacked into a flashable ZIP with SuperR Kitchen. By having this we can flash back to, now we hopefully feel a lot safer trying out and experimenting with other ROMs/mods for this phone. Also you'll need an unlocked bootloader and custom recovery to flash this too.
Since our only TWRP image for this phone is a dirty port from the E4 Plus as of writing this post, I had to remove the "ro.getprop" safety checks from the updater-script to get it to work and flash on the phone. This means that this can theoretically be flashed on any device, which would obviously break your phone if you flashed it on a non-Wonder. Be careful!
WHAT WORKS:
For the non-debloated ROM, everything
For the debloated ROM, everything except what's listed below
WHAT DOESN'T WORK/BUGS:
Some people that tested it reported Google Play crashings and Package Installer not being able to work. If this happens just flash pico OpenGApps in custom recovery and it should clear it right up no problemo
DOWNLOAD:
Link to my Orbic Wonder repo as a whole, where these ZIPs are stored
THANKS TO:
Team Orbic that I'm working with on Telegram to turn this phone into something special, specifically @noidodroid for getting those image pulls for us when we didn't have root at first
XDA user @SuperR. for that bangin' kitchen he made, this let us turn system and boot images into a TWRP flashable zip
Jason has did an awesome job with these builds!! We're working hard towards that (LOS) LineageOS build or AOSP. Until then when i get free time I will be working on a Totally unique cooked, debloated, deodexed, Rom with xposed, kernel mods, custom Launcher, Themes and more! Mine is a bit different than Jasons. I have debloated it and done all the mods i just mentioned just havent broke it down in the kitchen and cooked it up yet. All in due time.
noidodroid said:
Jason has did an awesome job with these builds!! We're working hard towards that (LOS) LineageOS build or AOSP. Until then when i get free time I will be working on a Totally unique cooked, debloated, deodexed, Rom with xposed, kernel mods, custom Launcher, Themes and more! Mine is a bit different than Jasons. I have debloated it and done all the mods i just mentioned just havent broke it down in the kitchen and cooked it up yet. All in due time.
Click to expand...
Click to collapse
Hey Noidodroid i was curious if you ever got free time to finish the ROM for the orbit wonder phone? I've been playing around with one I had in my shelf.
Thank you
DillanPease
jasonmerc said:
Stock Rom ZIPs for Verizon Orbic Wonder
Here's stock ROM zips for the Verizon variant Orbic Wonder. I wouldn't flash this on a vanilla Wonder if I were you, it might screw stuff up. One's a completely stock ROM and the other's pretty much just a normal stock ROM with some debloating here and there. Made using /system and /boot images pulled from a Verizon Orbic, and repacked into a flashable ZIP with SuperR Kitchen. By having this we can flash back to, now we hopefully feel a lot safer trying out and experimenting with other ROMs/mods for this phone. Also you'll need an unlocked bootloader and custom recovery to flash this too.
Since our only TWRP image for this phone is a dirty port from the E4 Plus as of writing this post, I had to remove the "ro.getprop" safety checks from the updater-script to get it to work and flash on the phone. This means that this can theoretically be flashed on any device, which would obviously break your phone if you flashed it on a non-Wonder. Be careful!
WHAT WORKS:
For the non-debloated ROM, everything
For the debloated ROM, everything except what's listed below
WHAT DOESN'T WORK/BUGS:
Some people that tested it reported Google Play crashings and Package Installer not being able to work. If this happens just flash pico OpenGApps in custom recovery and it should clear it right up no problemo
DOWNLOAD:
Link to my Orbic Wonder repo as a whole, where these ZIPs are stored
THANKS TO:
Team Orbic that I'm working with on Telegram to turn this phone into something special, specifically @noidodroid for getting those image pulls for us when we didn't have root at first
XDA user @SuperR. for that bangin' kitchen he made, this let us turn system and boot images into a TWRP flashable zip
Click to expand...
Click to collapse
I installed orange fox recovery on my RC555L and after that the screen is getting messed up. I am attaching a video of exactly what happens.
After boot it looks normal, when I turn the screen off and back on it looks messed up. Any ideas?
I reinstalled the stock recovery from your downloads and it did not fix the problem.
Installing stock rom did not fix the problem. I used the one you provided. It boots fine just when I turn the screen off and on it looks like the picture below.
tnitunes said:
I installed orange fox recovery on my RC555L and after that the screen is getting messed up. I am attaching a video of exactly what happens.
After boot it looks normal, when I turn the screen off and back on it looks messed up. Any ideas?
I reinstalled the stock recovery from your downloads and it did not fix the problem.
Installing stock rom did not fix the problem. I used the one you provided. It boots fine just when I turn the screen off and on it looks like the picture below.
Click to expand...
Click to collapse
OF was a decent recovery but we never completely finished up porting it so that it ran without any hitches. My copy AFAIR ran great and with the Fox addons. I however ditched Fox for 2-3 or so of our other 12? recoveries we have for this devices. Try downloading Batak Recovery. We did this. See if it runs better for you. Depending on what you are wanting to do... boot image, install zip afterwards and go from there.
[POLL] [Recovery] Which Android Recovery Project Do You Use ?
Your Favorite Recovery Project - What do you rely on the most for play or in your work? Hello All I'm curious to what all Recovery Projects are out there other than the 5 i know of and what you rely on when it comes to your work. Please take...
forum.xda-developers.com
^ List of Known Recovery Projects. We have ported the majority. Thanks Jason!
DillanPease said:
Hey Noidodroid i was curious if you ever got free time to finish the ROM for the orbit wonder phone? I've been playing around with one I had in my shelf.
Thank you
DillanPease
Click to expand...
Click to collapse
Sadly not yet but I hope to get some done this summer. I literally have 50 phones and half are all dedicated as "project" phones .. I really have to tone it down a bit I think.
tnitunes said:
I installed orange fox recovery on my RC555L and after that the screen is getting messed up. I am attaching a video of exactly what happens.
After boot it looks normal, when I turn the screen off and back on it looks messed up. Any ideas?
I reinstalled the stock recovery from your downloads and it did not fix the problem.
Installing stock rom did not fix the problem. I used the one you provided. It boots fine just when I turn the screen off and on it looks like the picture below.
Click to expand...
Click to collapse
I had the exact same screen issue. I'm looking into it more
jasonmerc said:
Stock Rom ZIPs for Verizon Orbic Wonder
Here's stock ROM zips for the Verizon variant Orbic Wonder. I wouldn't flash this on a vanilla Wonder if I were you, it might screw stuff up. One's a completely stock ROM and the other's pretty much just a normal stock ROM with some debloating here and there. Made using /system and /boot images pulled from a Verizon Orbic, and repacked into a flashable ZIP with SuperR Kitchen. By having this we can flash back to, now we hopefully feel a lot safer trying out and experimenting with other ROMs/mods for this phone. Also you'll need an unlocked bootloader and custom recovery to flash this too.
Since our only TWRP image for this phone is a dirty port from the E4 Plus as of writing this post, I had to remove the "ro.getprop" safety checks from the updater-script to get it to work and flash on the phone. This means that this can theoretically be flashed on any device, which would obviously break your phone if you flashed it on a non-Wonder. Be careful!
WHAT WORKS:
For the non-debloated ROM, everything
For the debloated ROM, everything except what's listed below
WHAT DOESN'T WORK/BUGS:
Some people that tested it reported Google Play crashings and Package Installer not being able to work. If this happens just flash pico OpenGApps in custom recovery and it should clear it right up no problemo
DOWNLOAD:
Link to my Orbic Wonder repo as a whole, where these ZIPs are stored
THANKS TO:
Team Orbic that I'm working with on Telegram to turn this phone into something special, specifically @noidodroid for getting those image pulls for us when we didn't have root at first
XDA user @SuperR. for that bangin' kitchen he made, this let us turn system and boot images into a TWRP flashable zip
Click to expand...
Click to collapse
The links are dead, can u please post new ones?
TheReal PerHapZ said:
The links are dead, can u please post new ones?
Click to expand...
Click to collapse
I forget where but somewhere on here I posted a full dump of everything Orbic related that I had. Its in one of the Orbic threads.
Orbic Wonder Dev Thread
EDIT: A rooted boot image and dirty port of TWRP recovery are now available. Dev work shall commence
forum.xda-developers.com
Full repo dump located here, to replace my dead links scattered about
The Orbic Wonder is still getting around! Good to see. I almost had the kernel source from Orbic. If someone wants to try them i can share contact info I received speaking to a worker there. I also still have 4 or 5 of the Wonder handsets here waiting for if I ever get spare time. Enjoyed the phone when it first came out. Fun phone.. Still not a bad phone in today's world running stock or with Jason's working cooked Rom.
Im tring to root my orbic and i followed this video but when it got to the end and restarted its saying encryption unsuccessful and wont do anything else only thing i can do is get into red fox recovery can any one assist me? maybe reflash?
Originally, this was thread was centered on the LineageOS 17 GSI by AndyYan, however, CodeF86 has so very generously made a working GSI for the Moto G6 which you can try out now!
Unlike AndyYan's generic GSI, for this you do NOT need to flash johnaltg1's LineageOS 16 image (if you do, this GSI will NOT boot). It is recommended you use stock Pie firmware. Oreo firmware has not been tested and may result in bugs.
Download here—Compiled Feb 22nd, w/ working LTE!
See CodyF86's thread post
Some notes:
Unlike the generic GSI, calling works.
Also unlike the GSI, the colors don't invert randomly.
Magisk DOES NOT work at the moment, neither phhuson's nor regular Magisk. Flashing it will cause a bootloop.
Bluetooth audio has been reported to not work
As with many Android 10 GSIs/ROMs, Chrome freezes or crashes because GApps packages currently are missing the new Trichrome WebView implementation which replaces Chrome as the default WebView. This being worked on (see OpenGApps wiki and issue #773 on their GitHub.) For now, use another browser (like LineageOS's default browser) if you install GApps. —As soon as Trichrome is added onto the ARM package just as it has for ARM64, Chrome should be stable.
For now, that's all I can think of. However, if you notice any other bugs or caveats, let me know so I can add it to the list.
This is a GSI based on phhuson's prereleased GSI work and also based on the prereleased LineageOS 17. This is a pre-release so please be careful and don't use this as a daily driver. Things may break randomly, whoops, so please be patient! If you see any bugs, report them here.
Extremely huge shoutout to CodyF86 for this GSI!
The developer of this ROM has moved on to another phone and the community now has a full fledged 64-bit ROM which has much better support for things.
AgentICS said:
The LineageOS 17 GSI works great on the Moto G6. There are some caveats however for anyone willing to try it:
You MUST first flash the LineageOS 16.0 ROM first or else you will bootloop.
Use this Magisk from phhuson's official GitHub
Your screen may change colors and look weird, when this happens, go to Settings > Display > LiveDisplay> Color mode and change it to the value under the value selected on the menu and then back to the original one and that should fix it
If you flash GApps before first boot, follow AndyYan's suggestions as the Setup Wizard is broken for some reason on most GApps packages.
Calling while not on WiFi is broken for now.
For now, that's all I can think of. However, if you notice any other bugs or caveats, let me know so I can add it to the list.
This is a GSI based on phhuson's prereleased GSI work and also based on the prereleased LineageOS 17. Things may break randomly, whoops, so please be patient!
Click to expand...
Click to collapse
Just to reiterate, you are stipulating that this pre-release build doesn't permit me to make an outgoing phone call (nor possibly receive any) unless connected to a WiFi network? Please pardon my not-so-subtle-sarcasm ... but, why would anyone release this with a bug (or limitation) which inhibits the core functionality of the device? I could see a million other issues being permissible but not being able to make normal phone calls (or possibly even receive them) doesn't warrant any kind of release for testing. That being said, I'd be happy to help if possible and eagerly await a usable version of Android 10 to put on my Moto G6 which I only got a month ago (happily unlocked at a great price on Amazon). However, it is (currently) my main phone for making calls.
xda4joe said:
Just to reiterate, you are stipulating that this pre-release build doesn't permit me to make an outgoing phone call (nor possibly receive any) unless connected to a WiFi network? Please pardon my not-so-subtle-sarcasm ... but, why would anyone release this with a bug (or limitation) which inhibits the core functionality of the device? I could see a million other issues being permissible but not being able to make normal phone calls (or possibly even receive them) doesn't warrant any kind of release for testing. That being said, I'd be happy to help if possible and eagerly await a usable version of Android 10 to put on my Moto G6 which I only got a month ago (happily unlocked at a great price on Amazon). However, it is (currently) my main phone for making calls.
Click to expand...
Click to collapse
everything works for me
taiyofurukawa said:
everything works for me
Click to expand...
Click to collapse
so you can make phone calls without WIFI conection?
xavcasgar said:
so you can make phone calls without WIFI conection?
Click to expand...
Click to collapse
yesssss
xda4joe said:
Just to reiterate, you are stipulating that this pre-release build doesn't permit me to make an outgoing phone call (nor possibly receive any) unless connected to a WiFi network? Please pardon my not-so-subtle-sarcasm ... but, why would anyone release this with a bug (or limitation) which inhibits the core functionality of the device? I could see a million other issues being permissible but not being able to make normal phone calls (or possibly even receive them) doesn't warrant any kind of release for testing. That being said, I'd be happy to help if possible and eagerly await a usable version of Android 10 to put on my Moto G6 which I only got a month ago (happily unlocked at a great price on Amazon). However, it is (currently) my main phone for making calls.
Click to expand...
Click to collapse
It is pre-release so not all the bugs are ironed out, I should have added that this should not be used on your daily driver. But yes, it's dumb to use a phone that can't make calls without WiFi. Just as a note, you can make and receive calls however if you're not using WiFi, the caller can't hear you. I have filed a bug upstream with phhusson as this affects every GSI built using his work (Pixel Experience, Lineage and AOSP which I've tested). I hope this gets fixed soon so stay tuned to that GitHub issue
taiyofurukawa said:
everything works for me
Click to expand...
Click to collapse
xavcasgar said:
so you can make phone calls without WIFI conection?
Click to expand...
Click to collapse
taiyofurukawa said:
yesssss
Click to expand...
Click to collapse
How? What is your modem version/phone model?
Can't Boot
AgentICS said:
The LineageOS 17 GSI works great on the Moto G6. There are some caveats however for anyone willing to try it:
You MUST first flash the LineageOS 16.0 ROM first or else you will bootloop.
Use this Magisk from phhuson's official GitHub
Your screen may change colors and look weird, when this happens, go to Settings > Display > LiveDisplay> Color mode and change it to the value under the value selected on the menu and then back to the original one and that should fix it
If you flash GApps before first boot, follow AndyYan's suggestions as the Setup Wizard is broken for some reason on most GApps packages.
Calling while not on WiFi is broken for now.
Bluetooth is horribly broken for now, it causes the app playing audio to lag and crash so please stay away from it.
Chrome is wonky at the moment. It'll work and then all of a sudden cause the whole OS to lag and crash or become unresponsive. This is possibly an upstream GApps issue.
For now, that's all I can think of. However, if you notice any other bugs or caveats, let me know so I can add it to the list.
This is a GSI based on phhuson's prereleased GSI work and also based on the prereleased LineageOS 17. This is a pre-release so please be careful and don't use this as a daily driver. Things may break randomly, whoops, so please be patient!
I am documenting everything on here. Stay tuned to that page for more info and further updates. Addiotionally, I have filed a bug report regarding calling, please add on to that GitHub issue and bump it so it can get resolved.
Click to expand...
Click to collapse
Ok, so I installed and flashed Lineage 16 first. Then I flashed Lineage 17 GSI in system img, but then when I did that I go into twrp and it said an os was not installed and wouldn't boot. But if I just flash Lineage 16 it would boot. Am I doing something wrong?
SomeAndrodGuyWithInternet said:
Ok, so I installed and flashed Lineage 16 first. Then I flashed Lineage 17 GSI in system img, but then when I did that I go into twrp and it said an os was not installed and wouldn't boot. But if I just flash Lineage 16 it would boot. Am I doing something wrong?
Click to expand...
Click to collapse
First off, are you unzipping the file? The standalone uncompressed file is unflashable. It needs to be decompressed from it's .gz (or whatever it was compressed to) form. If you have, have you tried using fastboot flash system <lineage file name> from a PC?
AgentICS said:
It is pre-release so not all the bugs are ironed out, I should have added that this should not be used on your daily driver. But yes, it's dumb to use a phone that can't make calls without WiFi. Just as a note, you can make and receive calls however if you're not using WiFi, the caller can't hear you. I have filed a bug upstream with phhusson as this affects every GSI built using his work (Pixel Experience, Lineage and AOSP which I've tested). I hope this gets fixed soon so stay tuned to that GitHub issue
Click to expand...
Click to collapse
Just wanted to jump in here and say I'm seeing same bug on xt1925-6 with callers not able to hear me on any 10 gsi's and speakerphone does not work at all. Phh aosp 10 build 209 with stock pie 55-37-7-2 boot vendor boots fine, other gsi's will only boot using the Ali lineage full ROM boot- vendor but call audio is broken as well. Thanks for submitting the bug report, hopefully it will get fixed in future builds.
Hello friends,
It's been a while since i've posted on XDA. I was the person who originally rooted the g6 play. I managed to build a GSI image of 17.1 with the latest code as of today if anyone is interested I can upload it to gdrive or something, didn't feel like making a new thread.
It boots, mobile calls work, dark mode works (which is amazing), it all seems to work.
Getting it to compile was just short of a miracle...lol.
Only bad thing is I cannot get it to boot with any version of magisk even the version specifically for phh / Android 10, but with just the stock kernel with the ,verify removed it boots fine.
CodyF86 said:
Hello friends,
It's been a while since i've posted on XDA. I was the person who originally rooted the g6 play. I managed to build a GSI image of 17.1 with the latest code as of today if anyone is interested I can upload it to gdrive or something, didn't feel like making a new thread.
It boots, mobile calls work, dark mode works (which is amazing), it all seems to work.
Getting it to compile was just short of a miracle...lol.
Only bad thing is I cannot get it to boot with any version of magisk even the version specifically for phh / Android 10, but with just the stock kernel with the ,verify removed it boots fine.
Click to expand...
Click to collapse
That's amazing! Could you upload it please so I can test it?
Thank you!
AgentICS said:
That's amazing! Could you upload it please so I can test it?
Thank you!
Click to expand...
Click to collapse
GSI-Lineage-17.1-2-16-2020-system.img
It seems it only connects at 3g although it lists a different apn server on lineage, I may be able to fix that, and I couldnt get the sd card to format as anything but adaptive storage, but everything works more or less. going to recompile in a week its still pretty early in development stage of lineage.
CodyF86 said:
GSI-Lineage-17.1-2-16-2020-system.img
It seems it only connects at 3g although it lists a different apn server on lineage, I may be able to fix that, and I couldnt get the sd card to format as anything but adaptive storage, but everything works more or less. going to recompile in a week its still pretty early in development stage of lineage.
Click to expand...
Click to collapse
Huge thanks for this GSI!!! I've been using it and it works flawlessly, I have also observed that only 3G works for now but regardless of that, everything works fine.
Again, I can't reiterate enough how thankful I am with you for this GSI!
AgentICS said:
Huge thanks for this GSI!!! I've been using it and it works flawlessly, I have also observed that only 3G works for now but regardless of that, everything works fine.
Again, I can't reiterate enough how thankful I am with you for this GSI!
Click to expand...
Click to collapse
May have a fix for LTE compiling it now, using the stock apn file with the adjusted mcc mnc numbers.
If I could get root I could get it for sure, but I can't get it to boot with a magisk flashed kernel, even the android 10 special version of magisk.
I got LTE but now mobile network stays disconnected although there is an LTE connection. It's an apn issue will work on it. if I get it working will make a thread...not sure why magisk won't work with my builds / kernel though yet.
https://github.com/codyf86
I've noticed that restarting always restarts to the bootloader. I don't know if it's just me but that's weird
Could you provide a link to the kernel source used in the rom?
Uclydde said:
Could you provide a link to the kernel source used in the rom?
Click to expand...
Click to collapse
It's on his GitHub
The kernel is actually just the stock kernel from the latest firmware with the ',verity' flag hexedited out to disable encryption. (You also need to change the fstab that is in all the guides ever made including my original one), but I'm working on building the kernel and making it work...but I got LTE to woooooork with some changes to the stock apn file lineage provides ! lol.
Only thing now is that it thinks my external sd card is corrupted and wont format right unless i set it to adaptive storage, so make a backup of your external sd card for now. Going to try using TWRP to format it with a couple different file systems.
Here she is boys.
Lineage-17.1-02.22.20-treble-arm-system
Still working on getting it to boost with magisk not sure why it won't when it was fine in Pie.
Still playing with the apn file the apn its using says sprint ehrpd but not sure what makes it pick which apns to show on the screen, but the apn is set to x.boost.ispsn which makes LTE work. I'll clean it up soon.
(All of this is assuming you're on Boost / Sprint)