Hi, I have been testing this on this device, and finally I was able to make AOSP 10 (GSI) run on our device.
Our device needs overlay to fix this issues. I will try to work into that
How to flash
WARNING: Your device must have unlocked bootloader
1. Download the latest TWRP Recovery: https://forum.xda-developers.com/mi...overy-unofficial-twrp-xiaomi-mi-note-t4015805
2. Download the latest AOSP 10 GSI (ab with gapps): https://github.com/phhusson/treble_experimentations/releases/
3. Download vbmeta.img: https://github.com/TadiT7/xiaomi_ce...9.3.1-release-keys/firmware-update/vbmeta.img
4. Disable vbmeta partition by flashing vbeta.img
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
5. Flash TWRP
Code:
fastboot flash recovery <twrp_file_name.img>
6. Boot TWRP, make wipe (Format Data only!)
7. Flash the AOSP system.img file to System partition
NOTE: Trying to flash system.img using fastboot causes bootloop.
Aditionally here you can flash GAPPS and Magisk
- Flash GAPPS: https://opengapps.org/
- Flash Magisk: https://github.com/topjohnwu/Magisk/releases
10. Reboot system & enjoy!
Bugs
- Fingerprint
- Auto-brightness
- NFC
-Weird notification audio: can be fixed flashing this -> https://github.com/hmuny99/GsiSystemAudioFix/raw/master/fixaudiogsi.zip
-Video recording: can be fixed by flashing this -> https://forum.xda-developers.com/attachment.php?attachmentid=4374464&d=1514638461
-Flashing Magisk causes bootloop
- GCAM Camera starts to lag when the device has been on for a long time
Since we have a complete kernel sources/device tree, we can have this as a daily diver :good:
For now, I'd need the framework-res.apk from Stock rom, if someone could provide it, that would be really helpful
iFlashed said:
For now, I'd need the framework-res.apk from Stock rom, if someone could provide it, that would be really helpful
Click to expand...
Click to collapse
I saw this on another topic.
https://forum.xda-developers.com/showpost.php?p=81824837&postcount=50
Hi, what do you think, this flashing method will work with phhussons GSI too?
https://github.com/phhusson/treble_experimentations/releases
---------- Post added at 08:00 AM ---------- Previous post was at 07:43 AM ----------
If you need it still, I can copy it now, if you tell me the full path of this file.
technoboi1 said:
Hi, what do you think, this flashing method will work with phhussons GSI too?
https://github.com/phhusson/treble_experimentations/releases
---------- Post added at 08:00 AM ---------- Previous post was at 07:43 AM ----------
If you need it still, I can copy it now, if you tell me the full path of this file.
Click to expand...
Click to collapse
Same steps, Boots up, I recommend the system-quack-arm64-ab-gapps from your link, as it includes Gapps.
However, With that both I couldn't flash Magisk or I would get a bootloop. With LoS It would also not install gapps. But would boot just fine without Gapps or Magisk.
Currently Phhussons is working with Gapps. LOS Is not, atleast for me, but neither is working with Magisk 20.4.
thank for your reply, it has same bugs like LOS?
deathhall said:
Same steps, Boots up, I recommend the system-quack-arm64-ab-gapps from your link, as it includes Gapps.
However, With that both I couldn't flash Magisk or I would get a bootloop. With LoS It would also not install gapps. But would boot just fine without Gapps or Magisk.
Currently Phhussons is working with Gapps. LOS Is not, atleast for me, but neither is working with Magisk 20.4.
Click to expand...
Click to collapse
technoboi1 said:
thank for your reply, it has same bugs like LOS?
Click to expand...
Click to collapse
Yup, Same bugs
Sent from my Mi Note 10 using Tapatalk
I remember when Android P GSI comes, we have distorted audio bugs, maybe its same bug again.
Deleting folder vendor/lib64/soundfx fixed bug in Android P.
Bugs
- Fingerprint
- Auto-brightness
- NFC
-Weird notification audio
I have been working on an overlay, but seems like I couldn't fix any bug.
Fingerprint works, but for any reason the Google API/Fingerprint config app is not recognizing it, but I can see in logcat that sensor recognizes when I use the fingerprint with any problem, so maybe problem from the GSI?
For the rest of the bugs, nothing for now
Is there an improvement?
UtkuAblak said:
Is there an improvement?
Click to expand...
Click to collapse
I'm trying to contact with phhusson. Audio can be fixed flashing a .zip
This rom use stock camera or? And what about current photo quality?
Good work and thank you guys!
Hudinited said:
This rom use stock camera or? And what about current photo quality?
Good work and thank you guys!
Click to expand...
Click to collapse
I recommend using a Gcam in order to get better quality, for example: https://www.celsoazevedo.com/files/android/google-camera/dev-urnyx05/ (tell me if you find something better!)
how did you fix the fingerprint?
iSonik said:
how did you fix the fingerprint?
Click to expand...
Click to collapse
It's not fixed yet, What I just said is that 'works' in terms that if you touch the fingerprint it will be recognized in logcat, but nothing will happend on the fingerprint setup app. Currently I'm talking with phhusson about this and thinks that this could be a GSI related issue because he told me he will make a test image
technoboi1 said:
Hi, what do you think, this flashing method will work with phhussons GSI too?
https://github.com/phhusson/treble_experimentations/releases
---------- Post added at 08:00 AM ---------- Previous post was at 07:43 AM ----------
If you need it still, I can copy it now, if you tell me the full path of this file.
Click to expand...
Click to collapse
iFlashed said:
It's not fixed yet, What I just said is that 'works' in terms that if you touch the fingerprint it will be recognized in logcat, but nothing will happend on the fingerprint setup app. Currently I'm talking with phhusson about this and thinks that this could be a GSI related issue because he told me he will make a test image
Click to expand...
Click to collapse
My fingerprint is recognized in logcat as well as the button lighting up, but it doesn't work even in stock rom funny enough.
deathhall said:
My fingerprint is recognized in logcat as well as the button lighting up, but it doesn't work even in stock rom funny enough.
Click to expand...
Click to collapse
What do you mean when you say It doesn't work in stock rom funny enough?
iFlashed said:
What do you mean when you say It doesn't work in stock rom funny enough?
Click to expand...
Click to collapse
When I flashed this GSI for Lineage 17 when the other thread first started, even after Miflashing back to Global Stock my fingerprint doesn't work anymore, If i use the testing options, it'll activate the fingerprint and register me using my finger on it, but wont activate fingerprint settings as a password, it goes to the input screen then kicks back out immediately
deathhall said:
When I flashed this GSI for Lineage 17 when the other thread first started, even after Miflashing back to Global Stock my fingerprint doesn't work anymore, If i use the testing options, it'll activate the fingerprint and register me using my finger on it, but wont activate fingerprint settings as a password, it goes to the input screen then kicks back out immediately
Click to expand...
Click to collapse
This could be something related to unlocked bootloader? u tried to relock the bootloader?
iFlashed said:
This could be something related to unlocked bootloader? u tried to relock the bootloader?
Click to expand...
Click to collapse
Are you asking if i did, or i should? Also, I don't wanna hijack the thread, maybe chat in PM or Discord or whatever you prefer?
Related
After factory resetting/reinstalling [Resurrection_Remix][Android 6.0.1, r_52][Kenzo], the "Unfortunately Setting Has Stopped" has started appearing whenever I try to access the Privacy setting to change the password/pin/pattern option. I also noticed that the Fingerprint scanner is no longer in the Privacy setting.
Under TWRP I have also tried wiping Dalvik / ART Cache, Data, Internal Storage, and Cache when reinstalling any other Custom ROMs and Gaap. The other custom ROMS I've installed are causing the Setting->Privacy option to crash also. All the searches I've made doesn't seem to fix the issue, particularly the searches in the Redmi section. Any suggestion would be helpful, thanks.
phonester said:
After factory resetting/reinstalling [Resurrection_Remix][Android 6.0.1, r_52][Kenzo], the "Unfortunately Setting Has Stopped" has started appearing whenever I try to access the Privacy setting to change the password/pin/pattern option. I also noticed that the Fingerprint scanner is no longer in the Privacy setting.
Under TWRP I have also tried wiping Dalvik / ART Cache, Data, Internal Storage, and Cache when reinstalling any other Custom ROMs and Gaap. The other custom ROMS I've installed are causing the Setting->Privacy option to crash also. All the searches I've made doesn't seem to fix the issue, particularly the searches in the Redmi section. Any suggestion would be helpful, thanks.
Click to expand...
Click to collapse
Flash radio.zip fix.and dont forget to flash gapps after flashing roms.
Sent from my Redmi Note 3 using Tapatalk
khan_pegasus said:
Flash radio.zip fix.and dont forget to flash gapps after flashing roms.
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
It worked, thanks.
link to download radio.zip?
This situation happens when you switch to an OFFICIAL Rom from an UNOFFICIAL one like Mokee or RR from Siddhesh or Santosh. This is because these ROMs lock the bootloader and cause other problems too.
Radio.zip may not always fix the problem. If you are really stuck, there is a lengthy process that is guaranteed to work.
1. Flash one of the MiUI Fastboot ROM (global or chinese stable works fine) for RN3SD with Mi Flash tool. Use Flash All in the options at the bottom.
2. If you had an officially unlocked bootloader, use the Mi Unlocker tool to unlock your bootloader. Otherwise, you need to follow the unofficial unlock guide.
3. Flash official TWRP or a variant if you now what you are doing. Refer to this thread if you are not sure which TWRP will work.
3a. Download and copy this file to internal storage - LazyFlasher. I have verified this file to work with MiUI7 and MiUI8 global.
3b Reboot the phone in fastboot mode. On your PC, copy the TWRP img file to the adb directory and open command window there. Rename it to recovery.img. Use this command
Code:
fastboot flash recovery recovery.img
3c Boot into recovery (using ADB or Vol-pwr button shortcut). DO NOT BOOT into the phone before you do this. Flash the Lazyflasher zip with TWRP. You could probably flash this using fastboot too, I just never tried it.
Dhanajay made a guide video here. The video is a little outdated, and the updated instructions are in the description and comments.
You phone is now rooted and you have TWRP. Happy flashing.
This method will soon be outdated as a graphical UI for ADB is already in progress. Others have done it before, but this one shows real promise. Check here for details.
It has been a few months now since the RN3SD launch and the time has come when unofficial ROMs are no longer the best option around. Most Official ROMs, including the ones from RR and XOSP among others work great now and are incredbilby smooth and efficient. The war for the best kernel is now starting, and custom kernels will be responsible for the next round of reasons for bricked phones. Be VERY careful when you are flashing a ROM with a custom kernel. Be prepared to do some legwork if things go wrong.
Joswin said:
link to download radio.zip?
Click to expand...
Click to collapse
http://builder.balika011.me/official-cm13/cm-13.0-RADIOS.zip
I would also recommend anyone having this issue to read this post.
talkaboom said:
http://builder.balika011.me/official-cm13/cm-13.0-RADIOS.zip
I would also recommend anyone having this issue to read this post.
Click to expand...
Click to collapse
Link isn't working...
Can you mirror it?
Joswin said:
Link isn't working...
Can you mirror it?
Click to expand...
Click to collapse
Seems to be down. Normally works. Give it some time.
But if you are moving from an unofficial ROM, flashing radios alone is unlikely to work. Radio zip fix is for undetected SIM and IMIE errors. Check your IMIE number in About Phone. If you are showing an IMIE number instead of '0', flashing radio may be pointless.
Joswin said:
Link isn't working...
Can you mirror it?
Click to expand...
Click to collapse
New Link available.
https://mega.nz/#!9hlljJKD!QmjwPqMOH...gOqWkEJ0QasGE4
talkaboom said:
New Link available.
This link needs a decryption key not provided. Why even post this?
Click to expand...
Click to collapse
virtualgates said:
This link needs a decryption key not provided. Why even post this?
Click to expand...
Click to collapse
Link is from August 8th. That **** has mirrored a hundred times by now.
Also, the problem is now tackled in a different way. If you're facing a similar issue, ask in the rom thread you are trying to flash.
If you are facing this problem now, just flash the correct CM firmware.
P.S. On XDA, please do not question why someone posted a link or method that did not work for you. Do your research. No one is obligated to solve your problems.
Flashed radio. Zip. Worked for me.
Sent from my Redmi Note 3 using Tapatalk
Hello talkaboom!
the link is not working anymore. Any chance to upload it again please? Thanks a lot!
Dual boot Patcher now works with our v20 I can confirm it works with the h918 but I cannot confirm it works with any of the others but as they are the same Hardware I cannot see why not.
I take no credit for this mod as all I did was send the original developer the necessary files to get it working on our phones, so go give @chenxiaolong a thanks and go here http://forum.xda-developers.com/showthread.php?t=2447534&page=1083
To download the latest snapshot and DualBoot utilities to easily managed between the two or three or however many you get.
This will really come in handy once we get Aosp up and running for our devices! Set alarm just putting this here in case anyone is interested.
jthrasher47 said:
Dual boot Patcher now works with our v20 I can confirm it works with the h918 but I cannot confirm it works with any of the others but as they are the same Hardware I cannot see why not.
I take no credit for this mod as all I did was send the original developer the necessary files to get it working on our phones, so go give @chenxiaolong a thanks and go here http://forum.xda-developers.com/showthread.php?t=2447534&page=1083
To download the latest snapshot and DualBoot utilities to easily managed between the two or three or however many you get.
This will really come in handy once we get Aosp up and running for our devices! Set alarm just putting this here in case anyone is interested.
Click to expand...
Click to collapse
Thank you so much for the heads up on this! I used this on my Note 4 and loved it!
Sent from my LG-H918 using Tapatalk
Thanks for sharing! Works great! Just flashed CM as secondary
Be warned, I used this with NATFs ROM as a primary and CM as secondary and I got locked out of my phone when going back to NATFs ROM. Pattern lock said it was wrong pattern. So be careful and disable lockscreen and fingerprints before doing this. There are still some bugs floating around.
But nice job and great progress for our phones!!!
jthrasher47 said:
Dual boot Patcher now works with our v20 I can confirm it works with the h918 but I cannot confirm it works with any of the others but as they are the same Hardware I cannot see why not.
I take no credit for this mod as all I did was send the original developer the necessary files to get it working on our phones, so go give @chenxiaolong a thanks and go here http://forum.xda-developers.com/showthread.php?t=2447534&page=1083
To download the latest snapshot and DualBoot utilities to easily managed between the two or three or however many you get.
This will really come in handy once we get Aosp up and running for our devices! Set alarm just putting this here in case anyone is interested.
Click to expand...
Click to collapse
For some reason I'm losing root on my secondary rom. I checked the dual boot thread and did not figure it out. Any ideas on what I can try? Thanks
Edit: I figured it out. If I flash it in twrp root sticks.
Sent from my LG-H918 using Tapatalk
For future reference for anyone with root sticking problems.. Just patche the SuperSU. Zip for dual or multi whatever you are going to use then flash it either in app or recovery and when you are booted into your secondary Rom make sure to set kernel accordingly
dfogelstrom said:
Be warned, I used this with NATFs ROM as a primary and CM as secondary and I got locked out of my phone when going back to NATFs ROM. Pattern lock said it was wrong pattern. So be careful and disable lockscreen and fingerprints before doing this. There are still some bugs floating around.
But nice job and great progress for our phones!!!
Click to expand...
Click to collapse
If you do run into this, delete all `lockscreen.db*` files in `/data/system/`.
Yes, it is good etiquette to remove lock screen patterns and fingerprints before installing a new ROM in any of your slots as it will not let you in when you go back to the other
I was having issues with this on my ls997. I was running teamdev ROM with werewolf kernel set as primary. I patched resurrection remix for secondary and tried to flash through app and got an error. So I tried to flash from TWRP and it failed to flash. I saw an error about the us996 at some point. Anyone have this working on ls997? What am I doing wrong?
almony8 said:
I was having issues with this on my ls997. I was running teamdev ROM with werewolf kernel set as primary. I patched resurrection remix for secondary and tried to flash through app and got an error. So I tried to flash from TWRP and it failed to flash. I saw an error about the us996 at some point. Anyone have this working on ls997? What am I doing wrong?
Click to expand...
Click to collapse
Did you patch the Rom and gapps zips before flashing?
Yes I patched them. I even tried downloading the ROM again. Still no luck. Any other thoughts?
almony8 said:
Yes I patched them. I even tried downloading the ROM again. Still no luck. Any other thoughts?
Click to expand...
Click to collapse
What's the error?
Zacharee1 said:
What's the error?
Click to expand...
Click to collapse
I didn't get a screenshot or anything but it said something about it not being a h918. It said like file type unrecognized
almony8 said:
I was having issues with this on my ls997. I was running teamdev ROM with werewolf kernel set as primary. I patched resurrection remix for secondary and tried to flash through app and got an error. So I tried to flash from TWRP and it failed to flash. I saw an error about the us996 at some point. Anyone have this working on ls997? What am I doing wrong?
Click to expand...
Click to collapse
Unfortunately this dual boot Patcher is setup for the h918.
So what you were going to have to do to get it working is extract the entire Resurrection ROM folder and open the updater script and remove the get prop lines and then save the file and rezip then patch and Flash after that all should be well
jthrasher47 said:
Unfortunately this dual boot Patcher is setup for the h918.
So what you were going to have to do to get it working is extract the entire Resurrection ROM folder and open the updater script and remove the get prop lines and then save the file and rezip then patch and Flash after that all should be well
Click to expand...
Click to collapse
I'll hold off I guess until RR gets a little further along instead of messing with it now
almony8 said:
I was having issues with this on my ls997. I was running teamdev ROM with werewolf kernel set as primary. I patched resurrection remix for secondary and tried to flash through app and got an error. So I tried to flash from TWRP and it failed to flash. I saw an error about the us996 at some point. Anyone have this working on ls997? What am I doing wrong?
Click to expand...
Click to collapse
works fine
almony8 said:
I'll hold off I guess until RR gets a little further along instead of messing with it now
Click to expand...
Click to collapse
It works
I admit its a bit confusing but once you figure it out it will be so easy to use
ricohz said:
works fine
Click to expand...
Click to collapse
Did you do what he said to do with removing the prop stuff or just install and use regular?
---------- Post added at 10:56 PM ---------- Previous post was at 10:54 PM ----------
ricohz said:
It works
I admit its a bit confusing but once you figure it out it will be so easy to use
Click to expand...
Click to collapse
I used this dual boot before on old phones without issues, just not working for me on this phone. I'll give it another shot when I have the time
just a regular install
I was having trouble with patching the zip files
so with file explorer I went to file's location and saw that the patch files were way smaller(for example gapps patch zip was like 20mg) so i deleted all the files and started over
jthrasher47 said:
Unfortunately this dual boot Patcher is setup for the h918.
So what you were going to have to do to get it working is extract the entire Resurrection ROM folder and open the updater script and remove the get prop lines and then save the file and rezip then patch and Flash after that all should be well
Click to expand...
Click to collapse
Device.json? Or am I in the wrong file?
known issue:
1> camera occasionally stops working and needs reboot to work again
2> gps not working
3> Mic not working
,,,V3.5 fixed mic,gps, and added open camera as default camera(removed CM snap), include gps test,
4> video camera not recording--V3.7 has fixed back video recording front still not working--also camera has still crashed on V3.7(but less often)
V3.8 synch up to changes made in SLIM6 port. Audio has not dropped out in this RoM like it has been for SLIM.
Files listed here under /system/lib/hw came from slim port. Other files under added and changed come from BLU R1_HD V21
Addional files under /priv-app came from apk mirror . com
V5.2
Removed extra apps previously added for testing.
Changed boot.img init files to change permissions.
Sim card 2 not tested by me I only have one card. Sim one works phone, text, and data.
Rom ported from BLU_Max_Life
need unlocked bootloader
need TWRP => Latest TWRP 3.1.1-0
gapps (google apps) not included. If want/ need playstore add gapps.
As with any and all modifications to your phone, you do at your own risk
.
.
.
XDA:DevDB Information
LineageOS 13 Port, ROM for the BLU R1 HD
Contributors
mrmazak, @vampirefo
ROM OS Version: 6.0.x Marshmallow
Based On: @vampirefo 'sLineageos-13-BLU_Max_Life
Version Information
Status: Beta
Current Beta Version: port-3.8
Beta Release Date: 2017-06-18
Created 2017-06-14
Last Updated 2018-02-27
updated link and photos and thanks :]
When I click the rom link it sends me to aliexpress?
is that the right image to flash >> lineage-13.0-20170527-UNOFFICIAL-Life_Max.zip
from TWRP 3.0.3-0 by Vampirefo or we need a newer TWRP version?
no that is not the right file. that is the rom this was ported from.
the download for this device is in the download tab
That also, the other one points to wrong device...only gapps link works properly
---------- Post added at 09:55 PM ---------- Previous post was at 09:48 PM ----------
mrmazak said:
no that is not the right file. that is the rom this was ported from.
the download for this device is in the download tab
Click to expand...
Click to collapse
My apologies , I always forget about dl tab...and use to the direct links...
I recently flashed this and latest openGapps.
Seems to be working fine, only bug I've found so far is CM setup thought my phone had a fingerprint sensor.
Better than the stock rom.
---------- Post added at 03:06 AM ---------- Previous post was at 02:57 AM ----------
Actually it appears to have trouble accessing the front facing camera... I will try with opencamera instead of the stock CM camera app.
roboman2444 said:
I recently flashed this and latest openGapps.
Seems to be working fine, only bug I've found so far is CM setup thought my phone had a fingerprint sensor.
Better than the stock rom.
---------- Post added at 03:06 AM ---------- Previous post was at 02:57 AM ----------
Actually it appears to have trouble accessing the front facing camera... I will try with opencamera instead of the stock CM camera app.
Click to expand...
Click to collapse
Trouble, as in what.
I just took multiple shots front and back both.
No problem.
edit;:
right after that opened camera from lock screen, now having trouble connecting to camera at all. and some icons have gone(phone in particular). doing reset now
mrmazak said:
Trouble, as in what.
I just took multiple shots front and back both.
No problem.
Click to expand...
Click to collapse
It was complaining about not being able to access it...
Just required a reboot, works fine now.
I just flashed the lineage-13.0-R1-HD-Port-2.zip rom from TWRP, it says a success flash but when rebooting, it always goes to recovery ???
pas7771 said:
I just flashed the lineage-13.0-R1-HD-Port-2.zip rom from TWRP, it says a success flash but when rebooting, it always goes to recovery ???
Click to expand...
Click to collapse
I had similar issue once before, it was due to not mounting system partition then booted correctly...
So cameras working or not, You mentioned it's hanging?
Mae7 said:
So cameras working or not, You mentioned it's hanging?
Click to expand...
Click to collapse
It works when you first boot, but after short time it will no longer connect.
Appears to happen more if the selfie side is on. (i never remember if that is front or back)
kormend said:
I had similar issue once before, it was due to not mounting system partition then booted correctly...
Click to expand...
Click to collapse
do I flash this rom with system mounted in twrp or umounted? then I need to mount the partition before reboot.
I'm so confused...
pas7771 said:
do I flash this rom with system mounted in twrp or umounted? then I need to mount the partition before reboot.
I'm so confused...
Click to expand...
Click to collapse
you shouldnt have to touch the mount
99.9% of the time, unless you are doing stuff in terminal from recovery , the mount screen should look like the photo attached
So I got rom flashed and gapps loaded all seems fine except wifi won't turn on/connect and also I have no network access via sim1/sim2, flashed slimrom 6 got same outcome, now trying to recover my previous stock rom....
Update stock rom recovered and wifi/network access is restore, so not sure why either Slimrom6/Lineage not allowing wifi/network access, under the system settings IP are showing blank on sim 1/2 and wifi.
mrmazak said:
It works when you first boot, but after short time it will no longer connect.
Appears to happen more if the selfie side is on. (i never remember if that is front or back)
Click to expand...
Click to collapse
I disabled stock camera and installed open camera now. It has not "hug-up" again since. So as long as this trend holds up, I will just add a note to disable camera. And I do not have gapps, (gapps replaces camera, I do not know if that newer app is better)
mrmazak said:
you shouldnt have to touch the mount
99.9% of the time, unless you are doing stuff in terminal from recovery , the mount screen should look like the photo attached
Click to expand...
Click to collapse
Ok great I flashed the rom like the picture but still. it always go back to recovery. I tried installing from the internal and from the micro sd card
wipe everything, did all flashing again still it boot in recovery.
my phone is a PRIME BLU R1 HD v 6.6 unlocked successfully with tool V11
what you guys thing I should do now to get at least something going?
pas7771 said:
Ok great I flashed the rom like the picture but still. it always go back to recovery. I tried installing from the internal and from the micro sd card
wipe everything, did all flashing again still it boot in recovery.
my phone is a PRIME BLU R1 HD v 6.6 unlocked successfully with tool V11
what you guys thing I should do now to get at least something going?
Click to expand...
Click to collapse
you also had some problem with flashing wrong recovery. right.
perhaps you should also format /data.
from twrp => wipe menu => lower right corner button "format data" => must type "yes" to confirm.
then will need to install from micro sd card. Just in case remove sdcard before format
mrmazak said:
you also had some problem with flashing wrong recovery. right.
perhaps you should also format /data.
from twrp => wipe menu => lower right corner button "format data" => must type "yes" to confirm.
then will need to install from micro sd card. Just in case remove sdcard before format
Click to expand...
Click to collapse
yes, I re-flashed the recovery image from fastboot..
Could I have a boot img partition corrupt ?
I did all the wipe possible, format the data with "yes" re-flashed the rom and still it goes back to recovery
any other solution I can use?
it build with help of sony 8.1 build guide this is initial release if something is not working forgive me
know issue:
only these gapps are working http://downloadmirror.co/Wnu/open_g...=sNzCRW8kTd7udNDbSyWYjIgAv+YR5AibE7aCrJr8PuY=
and after flashing gapps install play store from here https://uploadfiles.io/q90da
mobile network is slow to start
good news is
google cemra working
120hrz display working
instructions
install adb first here is link https://forum.xda-developers.com/showthread.php?t=2588979
then copy all files their
and open cmd or powershell by shift+ right click
for windows 10 ONLY
IF POWERSHELL OPEN
THEN TYPE cmd
now for all user in cmd type
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash oem SW_binaries_for_Xperia_Android_8.1.6.4_r1_v10_yoshino.img
download link are at 2 post
https://drive.google.com/drive/folders/1W03Yhs6sRFJP4aXWC___LZ6joNCRps6A?usp=sharing
Have you flashed the DRM Patch or not needed?
Gesendet von meinem G8341 mit Tapatalk
sir
i think drm is not needed for aosp based rom its only for sony specific software
correct me if i am wrong.
I can't boot on g8341...
eggimong said:
I can't boot on g8341...
Click to expand...
Click to collapse
sir sorry i forgot to specify it is for g8342 give me 3 hour i will upload for you model
Thanks for your help
Please let us know when a build for the 8431 is available and I'll download it and test
n1ghtr08d said:
please let us know when a build for the 8431 is available and i'll download it and test
Click to expand...
Click to collapse
okay uploading in 2 hours its in process
Cool. Any idea why GAPPS doesn't work?
N1ghtr08d said:
Please let us know when a build for the 8431 is available and I'll download it and test
Click to expand...
Click to collapse
here you go plz test it
https://drive.google.com/drive/folders/1al3wXW7-pwN5fyCqR4jvW6ebHvBDmpZR?usp=sharing
Downloading now. I'll flash and report back with results
eggimong said:
I can't boot on g8341...
Click to expand...
Click to collapse
plz test this one
https://drive.google.com/drive/folders/1al3wXW7-pwN5fyCqR4jvW6ebHvBDmpZR?usp=sharing
I'm also downloading a fresh version of openGAPPS just in case
---------- Post added at 10:52 PM ---------- Previous post was at 10:44 PM ----------
Is it necessary to flash the recovery as I would prefer to keep TWRP?
So i flashed all the files and they flashed successfully and it booted just fine. Here's what i've noticed so far...
Things like Wifi and BT are all working. The Mobile data/Network didn't take any longer than usual to start up than it does on stock. I installed the latest TWRP from @modpunk and i flashed the latest version of GAPPS 8.1 and it flashed perfectly in TWRP........However, when i actually open the Play Store to set up my account it crashes after a minute or so and if i reopen the app then it just stays on the very first "Checking Info" screen and does nothing else.
I need a working phone as an everyday driver but i'm willing to leave it like this until tomorrow in case there's any logcats i can run for you or any other testing, just let me know.
Many many thanks for your work so far and you are so close to making so many users dreams come true by offering us a fully functional AOSP rom with a working camera and the ability to install Magisk for root. Please let's work together to figure this out and get it up and running on 8.1.
N1ghtr08d said:
So i flashed all the files and they flashed successfully and it booted just fine. Here's what i've noticed so far...
Things like Wifi and BT are all working. The Mobile data/Network didn't take any longer than usual to start up than it does on stock. I installed the latest TWRP from @modpunk and i flashed the latest version of GAPPS 8.1 and it flashed perfectly in TWRP........However, when i actually open the Play Store to set up my account it crashes after a minute or so and if i reopen the app then it just stays on the very first "Checking Info" screen and does nothing else.
I need a working phone as an everyday driver but i'm willing to leave it like this until tomorrow in case there's any logcats i can run for you or any other testing, just let me know.
Many many thanks for your work so far and you are so close to making so many users dreams come true by offering us a fully functional AOSP rom with a working camera and the ability to install Magisk for root. Please let's work together to figure this out and get it up and running on 8.1.
Click to expand...
Click to collapse
I told you no gapps are working it is something related to rom itself if you manually select mobile network it will work
If I manually select mobile network... What will work? Gapps will work?
Hello guys.
I have managed to get playstore working.
I have installed first 8.1 gapps, and failed then i have manually installed framework services, play store services, account manager and the play store.
You can find the files in the zip at https://ufile.io/q90da it also contains the Chrome APK. It is not flashable, just install it from the Files app on the phone.
Hope this helps.
I installed these apks and when i try to get my account set up i get a CONSTANT play services framework crashing saying it needs to update but it won't launch the play store to do it.
PLEASE HELP IT'S DRIVING ME INSANE WITH THE INCESSANT NOTIFICATIONS
---------- Post added at 10:56 AM ---------- Previous post was at 10:40 AM ----------
What exactly was your process? Did you flash the stock recovery? Did you flash TWRP then flash the Open GAPPS 8.1 package and THEN install all these files?
I'm trying to figure out how you managed to get this working and i can't.
hello.
I am sorry for your issues.
I will describe the exact steps I took :
-flashed the files for AOSP
-flashed twrp
-flashed magisk
-flashed gapps 8.1 unofficial
-flashed the 4 files
-opened play store
It worked well for me. Sorry if it caused even more trouble for your phone. I am on G8431.
## I TAKE NO RESPONSIBILITY IF YOU BRICK YOUR DEVICE##
THIS IS A MATERIAL TWRP IMG THAT I MADE FOR THE PAYTON
I HAVE TESTED THIS WHIT MY OWN DEVICE
ITS IS FULLY STABLE NOW YOU ALL TO ENJOY!!!
BUT IM STILL TWEAKING THING
INSTALL THE SAME WAS AS EVERY OTHER TWRP IMG
RECOMMEND CLEAN INSTALL DO NOT INSTALL OVER OTHER TWRP
reboot to bootloader
run this command
Fastboot boot TWRP-payton-material.img
wait for it to boot
then flash the installer zip
IF YOU KEEP REBOOTING BACK INTO TWRP REFLASH MAGISK
TO GET THE ADD ON TO BE ABLE TO CHANGE COLOR LAYOUT AND ALL THAT
AFTER FLASH COMPLETELY REBOOT BACK TO OS
THEN REBOOT BACK TO TWRP CLICK THE ICON NEXT TO SETTING IN THE TOP RIGHT
IT WILL ASK YOU FOR UI.ZIP CLICK CHANGE THEME SWIPE TO FLASH AND THERE YOU GO
DOWNLOAD
I HOPE EVERYONE ENJOYS!!!
FEATURES SO FAR
EVERYTHING IS WORKING!!!
MTP(YES)
OTG(YES)
ADB SIDELOAD(YES)
DECRYPTION(YES)
BONUS TWEAKS BUILT IN (YES)
GROUP AND BUG REPORTS
will this stay in place with a rom OTA (like havoc?)
themedicduck said:
will this stay in place with a rom OTA (like havoc?)
Click to expand...
Click to collapse
At this time i cant give a 100% yes
I only have a couple of beta tester as of right now
But they have reported it work like normal
so I do be leave that it will
if you do a OTA and it fails please tell me asap
Im still working on it but is stable enough to be beta tested :good:
FizzyAps said:
At this time i cant give a 100% yes
I only have a couple of beta tester as of right now
But they have reported it work like normal
so I do be leave that it will
if you do a OTA and it fails please tell me asap
Im still working on it but is stable enough to be beta tested :good:
Click to expand...
Click to collapse
Good deal.
I'm guessing dirty flashing this over my current TWRP is a bad idea? Clean install?
Recommend clean install do not install over other twrp
FizzyAps said:
Recommend clean install do not install over other twrp
Click to expand...
Click to collapse
Ok.
Did you do anything special to get this to build?
What sources are you using? Omni trees or los?
gee one said:
Did you do anything special to get this to build?
What sources are you using? Omni trees or los?
Click to expand...
Click to collapse
I de-compiled the official 3.2.3-1 and syberhexen 3.2.3-0
and re-compiled
them together with the themed ui the us see to get stable result
so mix of both
gee one said:
Did you do anything special to get this to build?
What sources are you using? Omni trees or los?
Click to expand...
Click to collapse
you can follow the build and updates on all are twrps here
https://t.me/motox4twrp
themedicduck said:
will this stay in place with a rom OTA (like havoc?)
Click to expand...
Click to collapse
There is no longer a recovery partition, instead recovery is built into the boot.img on X4 (and all other slot A/B devices)
So when you flash a rom, that file gets updated and you loose twrp.
The only way around that would be a custom installer that manually installs twrp during flash.
SchmilK said:
There is no longer a recovery partition, instead recovery is built into the boot.img on X4 (and all other slot A/B devices)
So when you flash a rom, that file gets updated and you loose twrp.
The only way around that would be a custom installer that manually installs twrp during flash.
Click to expand...
Click to collapse
Gotcha ok. I think I get it now. So if I don't want TWRP to be overwritten, I'll just have to manually flash updates every time like I do now.
themedicduck said:
Gotcha ok. I think I get it now. So if I don't want TWRP to be overwritten, I'll just have to manually flash updates every time like I do now.
Click to expand...
Click to collapse
You have to flash TWRP after every rom flash whether its OTA or manual.
Thank you for providing the decrypt function.
But I use a 6x6 pattern, and it is literally impossible to succeed with my pattern since the dots are so close together. Possible to spread them out?
I need to know: What are the bonus tweaks built in? Thanks
flieswithhawks said:
I need to know: What are the bonus tweaks built in? Thanks
Click to expand...
Click to collapse
Everything listed in the post
Which installer, TWRP-payton-Material-stb1 or TWRP-payton-material-installer? What's the difference?
flieswithhawks said:
I need to know: What are the bonus tweaks built in? Thanks
Click to expand...
Click to collapse
BONUS TWEAKS BUILT IN (YES)
It says right there. (YES)
I'd also like a list of what exactly the bonus tweaks are, as they are apparently mixed in with regular non-tweaked content.
So, in the context of recovery images... how exactly is there such a thing as a "dirty" flash? A flash is a flash for the recovery image. It is contained. What am I missing?
Please tell me!
TWRP-payton-Material-stb1.img or TWRP-payton-material.img - what's the difference, which one to use? Will the project be further developed - 3.3.1-0?
Thank you for a good job!
@FizzyAps Nicely done. Although I wish I could get the theme used when booting from the IMG file (TWRP-payton-material.img). -- That was impressive! Unfortunately, I see that the installer (and the ui.zip) do not include that. Still, it is both a visual and tech improvement over the current stock TWRP.