Related
I tried to flash the team spain 5.8 recovery but it does not work , flash seem to go well but still only boots into stock recovery.
Rom is 15s
zsajak said:
I tried to flash the team spain 5.8 recovery but it does not work , flash seem to go well but still only boots into stock recovery.
Rom is 15s
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=68462069&postcount=2
sanke1 said:
http://forum.xda-developers.com/showpost.php?p=68462069&postcount=2
Click to expand...
Click to collapse
How can I follow your guide If I cannot flash the recovery?
zsajak said:
How can I follow your guide If I cannot flash the recovery?
Click to expand...
Click to collapse
Are you having correct adb drivers installed? On my PC Windows 10 X64, they get installed from Windows Update and show up as "London Marshal adb interface."
It wouldn't hurt to try a different USB port.
Also try fully resetting your phone to factory default from the settings.
I am using X821 and only the TWRP recovery posted in my guide works. Other recoveries do not work for our device.
BTW I have updated my guide. Check it out again.
sanke1 said:
Are you having correct adb drivers installed? On my PC Windows 10 X64, they get installed from Windows Update and show up as "London Marshal adb interface."
It wouldn't hurt to try a different USB port.
Also try fully resetting your phone to factory default from the settings.
I am using X821 and only the TWRP recovery posted in my guide works. Other recoveries do not work for our device.
BTW I have updated my guide. Check it out again.
Click to expand...
Click to collapse
For some reason it was not working, it is now.
I still get a bootloop when I try to flash the resurrection remix rom.
cm13 by teamspain worked fine though
sanke1 said:
Are you having correct adb drivers installed? On my PC Windows 10 X64, they get installed from Windows Update and show up as "London Marshal adb interface."
It wouldn't hurt to try a different USB port.
Also try fully resetting your phone to factory default from the settings.
I am using X821 and only the TWRP recovery posted in my guide works. Other recoveries do not work for our device.
BTW I have updated my guide. Check it out again.
Click to expand...
Click to collapse
I followed your guide and installed twrp correctly and it worked.
I cannot install any rom besides cm13 unofficial though, i always get a bootloop if I install resurrection remix for example.
Its really very annoying, I wiped everything including data and system, only the official 16s roms works and cm13 unofficial, all other roms result in a bootloop.
something is not right here.
twrp not mounting storage data
sanke1 said:
Are you having correct adb drivers installed? On my PC Windows 10 X64, they get installed from Windows Update and show up as "London Marshal adb interface."
It wouldn't hurt to try a different USB port.
Also try fully resetting your phone to factory default from the settings.
I am using X821 and only the TWRP recovery posted in my guide works. Other recoveries do not work for our device.
BTW I have updated my guide. Check it out again.
Click to expand...
Click to collapse
twrp flased but its not mounting storage data, also sideload command to install supersu.zip didnt worked tried several times
its just stopping exactly at 73% everytime
Hello everyone. I started this thread because I don't think I've seen anything with this issue on my specific phone on this forum. Apologies if this has been discussed before.
Anyway, I'm having issues installing a ROM with adb sideload on TWRP recovery.
I got the ROM and the recovery image from blox2.com (I would post the links but apparently the forum doesn't allow me to...)
Everything works fine, I'm able to boot into TWRP recovery and inititiate the adb sideload, but the process gets stuck when it reaches 28% and throws the error message:
serving: 'BLOX2core-v1.1.1-31217.zip' (~28%) * failed to read command: Success
Click to expand...
Click to collapse
In case this has anything to do with ADB version, I'm using Debian and my adb version is 1:7.0.0+r1-4
If you need any more info, please ask.
Thanks in advance.
Ok, an update.
I now tried installing the ROM through TWRP's own installing option, but TWRP crashes and reboots a couple of seconds after the install is initiated.
max_157 said:
Ok, an update.
I now tried installing the ROM through TWRP's own installing option, but TWRP crashes and reboots a couple of seconds after the install is initiated.
Click to expand...
Click to collapse
Make sure you have MTP turned off. Also DM verity and force encryption needs to be disabled
ieatgravity said:
Make sure you have MTP turned off. Also DM verity and force encryption needs to be disabled
Click to expand...
Click to collapse
How do I disable MTP? I can't get android to boot. Can you disable it from TWRP or is it done from a fastboot/adb command?
I figured it out. I disabled MTP from the mount menu and disabled DM-Verify and encryption from the Advanced menu... same results
max_157 said:
How do I disable MTP? I can't get android to boot. Can you disable it from TWRP or is it done from a fastboot/adb command?
Click to expand...
Click to collapse
Flash supersu then flash the ROM
ieatgravity said:
Flash supersu then flash the ROM
Click to expand...
Click to collapse
OK. I tried
1. Booting into TWRP
2. Selected Install
3. Selected UPDATE-SuperSU-v2.65-20151226141550.zip
It crashed after a couple of seconds.
Tried with MTP disabled and DM-verity and encryption disabled.
max_157 said:
OK. I tried
1. Booting into TWRP
2. Selected Install
3. Selected UPDATE-SuperSU-v2.65-20151226141550.zip
It crashed after a couple of seconds.
Tried with MTP disabled and DM-verity and encryption disabled.
Click to expand...
Click to collapse
I'm would assume the bootloader was unlocked? Are you able to make a nandroid backup? And have you tried flashing twrp to the phone ?
Where do you have the files located at? Is it on the SDcard or on the flash drive?
does this work?
fastboot oem unlock
or
fastboot flashing unlock
Should also erase/wipe everything except system/recovery/boot...
Also hope you made a nandroid backup first with the fastboot boot recovery.img, then booting into TWRP and backup. to flash drive. Need MTP disabled for some to not reboot.
Also try with the new TWRP where the reboot has been fixed.. and which version 16/2 or 64/4 BLU X2 or mini?
ieatgravity said:
I'm would assume the bootloader was unlocked? Are you able to make a nandroid backup? And have you tried flashing twrp to the phone ?
Click to expand...
Click to collapse
The bootloader was indeed unlocked.
I haven't tried flashing TWRP to the phone. Would this make it work? I'm kind of scared of having a recovery image that crashes whenever I try stuff. Can I restore the stock recovery in case anything happens?
AlienTeck said:
Where do you have the files located at? Is it on the SDcard or on the flash
drive?
Click to expand...
Click to collapse
Internal flash drive.
AlienTeck said:
does this work?
fastboot oem unlock
or
fastboot flashing unlock
Click to expand...
Click to collapse
Yup! It works. It says it's already unlocked.
AlienTeck said:
Should also erase/wipe everything except system/recovery/boot...
Also hope you made a nandroid backup first with the fastboot boot recovery.img, then booting into TWRP and backup. to flash drive. Need MTP disabled for some to not reboot.
Click to expand...
Click to collapse
I did wipe cache and everything else, and had MTP disabled.
AlienTeck said:
Also try with the new TWRP where the reboot has been fixed.. and which version 16/2 or 64/4 BLU X2 or mini?
Click to expand...
Click to collapse
64/4 BLU X2 version.
I can't find BLU Life One X2 on the official TWRP website, the only version I tried was on blox2.com, which I think is a modified version of 3.0.2-0.
Problem fixed!
I flashed the stock firmware using QFIL 1.0.2. Thanks so much to everyone who helped!
QFIL
I got the QFIL rom from blox2.com
When you say fixed, do you mean TWRP is now working? Or that you were able to flash the stock back? Did you already take the BLOX2 OTA update?
Trying to figure out if the update had anything to do with this default rebooting on /system being made writable.. Also did you make a nandroid backup?
QFIL is now on 1.0.0.3
AlienTeck said:
When you say fixed, do you mean TWRP is now working? Or that you were able to flash the stock back? Did you already take the BLOX2 OTA update?
Trying to figure out if the update had anything to do with this default rebooting on /system being made writable.. Also did you make a nandroid backup?
QFIL is now on 1.0.0.3
Click to expand...
Click to collapse
I was able to flash the stock back, but via QFIL, not TWRP. The rebooting issue still persists.
I didn't make a nandroip backup, will get to it now.
Oh, I'm actually now trying to fix the rebooting issue. I think it might be a write protection, like the one HTC has. Example: https://www.youtube.com/watch?v=KV3YaMBnEYI
I really really need to be able to modify the system partition because the phone comes with a lot of crawpare and even some malware (https://www.cyberscoop.com/android-malware-china-huawei-zte-kryptowire-blu-products/)
FotaProvider installs some apps without your consent like Uber and some games and supposedly sends some info, too.
When I try to remove it with root uninstallers, the phone reboots. I though I had gotten rid of this issue by reflashing the ROM but apparently not...
I only flashed TWRP to cache and booted to it and flashed super SU, then used root essentials to remove some of the bloatware. But noticed supersu was gone now. It was able to remove or disable some of the stuff without rebooting and then later manually rebooting it. I disabled the apps and then removed it, so I think even the update now has the stuff but still disabled. The update also supposedly removes one of the apps that sent data back.
It rebooted at first until I saw that I had to disable MTP in TWRP options. I have not tried the recent TWRP, I was still using the one under development in the beginning.
AlienTeck said:
I only flashed TWRP to cache and booted to it and flashed super SU, then used root essentials to remove some of the bloatware. But noticed supersu was gone now. It was able to remove or disable some of the stuff without rebooting and then later manually rebooting it. I disabled the apps and then removed it, so I think even the update now has the stuff but still disabled. The update also supposedly removes one of the apps that sent data back.
It rebooted at first until I saw that I had to disable MTP in TWRP options. I have not tried the recent TWRP, I was still using the one under development in the beginning.
Click to expand...
Click to collapse
How do I install this update?
Also, I tried removing some system apps with Root Essentials but it still rebooted.
max_157 said:
How do I install this update?
Also, I tried removing some system apps with Root Essentials but it still rebooted.
Click to expand...
Click to collapse
For the time being you need to boot into TWRP and manually remove apps using ADB. We are currently working on patching the kernel to allow /system to be mounted RW sAo that you can use apps to remove system apps. In the mean time use Blox2core as it has been fully debloated.
ieatgravity said:
For the time being you need to boot into TWRP and manually remove apps using ADB. We are currently working on patching the kernel to allow /system to be mounted RW sAo that you can use apps to remove system apps. In the mean time use Blox2core as it has been fully debloated.
Click to expand...
Click to collapse
Sounds great! Looking forward to it.
I can't install Blox2core since TWRP reboots when I try to install it or even wipe the /system partition though. Some people mentioned TWRP 3.0.3 fixed this issue.
max_157 said:
Sounds great! Looking forward to it.
I can't install Blox2core since TWRP reboots when I try to install it or even wipe the /system partition though. Some people mentioned TWRP 3.0.3 fixed this issue.
Click to expand...
Click to collapse
We have a new tool that you can use to flash TWRP and root. All auto matic. Give it a try and let me know if it works for you.
[TOOL]Draco’s Blox2Autoroot - http://wp.me/p8gYUZ-5x
Afterwards you'll be able to flash Blox2core
Also I was unaware of this TWRP 3.0.3 for the blox2. The only one that has been ported has been 3.0.2 last I checked.
I would say disable MTP in TWRP options and developer options as well. dirst disabled it in developer options before I found out that did not stop the kernel rebooting the phone when /system became writable. I had not installed the oct update BLU sent out and maybe that makes a difference? Although the QFIL should also have the original boot/kernal image? so not sure what is going on..
If that dont stop it we need a new kernal.. I think I have the original kernal/boot saved. If anyone wants to see if that fixed the reboot.
twrp gave a MD5 of it..
152479bd51790d374885cc1a847e4c31 boot.emmc.win
Seems I need a faster course in android.. A few months ago I thought an android was some guy in dr who.
---------- Post added at 12:08 PM ---------- Previous post was at 11:46 AM ----------
The OTA update showed up one day and it installed it.. For the longest time I ignored it but I suppose someone hit ok on it.. But SuperSU seemed to have vanished before that I think. Spending time on 2 other problem phones so this one is not a priority since it works very well comparatively. I love it though it is heavy as a brick. Even my N5x case fits with a little coaxing. Although the DPI setting is set much higher like for a HD screen and not FHD. Maybe we can change it in build.prop to fix it. The N5x has much smaller icons and letters and actually fit 5 icons to a row although they both have the same density screen.. BLU has much better touch though and is far brighter and richer.
---------- Post added at 12:30 PM ---------- Previous post was at 12:08 PM ----------
The 2 boot images ARE different.. But you should first try to write a backup back to itself and see if there are problems and guess I dont have the previlage of attaching files just yet on here.
max_157 said:
Problem fixed!
I flashed the stock firmware using QFIL 1.0.2. Thanks so much to everyone who helped!
I got the QFIL rom from blox2.com
Click to expand...
Click to collapse
Could you share the link to the stock ROM you used with QFIL?
Thanks!
Hi. Maybe some of you have these files but i'll share mod i use on custom roms and LOS 15.1.
I can add to OP more if you share on this topic
Original LOS 15.1 Thread by @OrdenKrieger https://forum.xda-developers.com/axon-7/development/unofficial-lineageos-15-1-zte-axon-7-t3800214
Google Camera for HDR+ and Portrait Mode on Front Camera
https://drive.google.com/open?id=1CZAoa_9HQDnrM-F1qIYDpczuHmZXrfZw
Use pico gapps to use GCam.
Change buttons back and recent. Thanks @kevte89
https://drive.google.com/open?id=1SjY1-uIZ0kTayJ0vouHP2LyaKWPHN_SV
Magisk 16.4 to Root.
https://github.com/topjohnwu/Magisk/releases/download/v16.4/Magisk-v16.4.zip
To Fix Daydream. Thanks to @LuccoJ
https://forum.xda-developers.com/showpost.php?p=76806563&postcount=303
Add the addonsu to root with Magisk (and remove addonsu) https://download.lineageos.org/extras
or
Just root within twrp 3.2.17 (@NFound) - tested by @DarkQuark
@WesTD why the need to use pico gapps? Can't you choose aroma and not install Google Camera or use gapps config to disable it being installed.
@raystef66 you need to install the addonsu, remove it and then install magisk? Why can't you just install magisk?
Dodgexander said:
@WesTD why the need to use pico gapps? Can't you choose aroma and not install Google Camera or use gapps config to disable it being installed.
@raystef66 you need to install the addonsu, remove it and then install magisk? Why can't you just install magisk?
Click to expand...
Click to collapse
You can install magisk when on 3217 as i heard without addonsu but this one runs 3216.
Just use the addonsu and then flash 16.4 and you'll be good to go.
EDIT : maybe 3.2.1.6 can root too without the addonsu but i never tested that. But like said no harm done to use the addonsu
Dodgexander said:
@WesTD why the need to use pico gapps? Can't you choose aroma and not install Google Camera or use gapps config to disable it being installed.
@raystef66 you need to install the addonsu, remove it and then install magisk? Why can't you just install magisk?
Click to expand...
Click to collapse
IDK why but camera has stopped if I install mini or higher
raystef66 said:
You can install magisk when on 3217 as i heard without addonsu but this one runs 3216.
Just use the addonsu and then flash 16.4 and you'll be good to go.
EDIT : maybe 3.2.1.6 can root too without the addonsu but i never tested that. But like said no harm done to use the addonsu
Click to expand...
Click to collapse
I'll have to try when I install it and report back here.
WesTD said:
IDK why but camera has stopped if I install mini or higher
Click to expand...
Click to collapse
Very strange when mini doesn't include camera. The only apps in mini that have anything to do with the camera are face detect and photos.
WesTD said:
Google Camera for HDR+ and Portrait Mode on Front Camera
https://drive.google.com/open?id=1CZAoa_9HQDnrM-F1qIYDpczuHmZXrfZw
Click to expand...
Click to collapse
Is HDR+ and Portrait Mode only working on the front camera?
Any news about the stock camera?
There have been flashable zips in the path if I'm not mistaken, none for oreo after all I know, right?
joaocandeias said:
Is HDR+ and Portrait Mode only working on the front camera?
Click to expand...
Click to collapse
Both rear and front
Just to update here with my findings.
1. Magisk 16.4 works fine installing straight, no reason to install addonsu.
2. Installed aroma gapps from open gapps and it works fine apart from bizarre occasional "Google has stopped " messages.
3. I can't comment on the Google camera shared here but the latest recommend pixel mod camera from here: https://www.celsoazevedo.com/files/android/google-camera/dev-arnova8G2/#apk285 works relatively well, crashed on me once trying slow motion but everything else seems to work. I did not come across the problem mentioned here where certain gapps break gcam.
This is all fresh install, unencrypted, A2017U using universal bootstack and U modem and Nfound TWRP .6.
Is there any reason you chose that exact version of Gcam @WesTD ?
I have been using the latest version arnovas mod and today it crashed quite often taking photos. It also didn't work well recording UHD video and lagged during one of my recordings.
WesTD said:
Hi. Maybe some of you have these files but i'll share mod i use on custom roms and LOS 15.1.
I can add to OP more if you share on this topic
Click to expand...
Click to collapse
You should add this magisk mod to fix issues with DayDream:
https://forum.xda-developers.com/showpost.php?p=76806563&postcount=303
Liquid5n0w said:
You should add this magisk mod to fix issues with DayDream:
https://forum.xda-developers.com/showpost.php?p=76806563&postcount=303
Click to expand...
Click to collapse
Thanks, added OP
Just a general, unimportant question. What's the deal with LOS-based ROMs and cLock? cLock displays weather with the aid of weather providers since Marshmallow I think.
On Oreo none of them seem to work. They install normally but the systems don't see them as providers. Not even Chronus which also acts as a provider.
Just wondering (out loud) why cLock is still included if it's not fully functional anymore.
ZTE Axon 7 A2017U, AospExtended v5.4 ROM, HellsGate Kernel, Multiboot, Tapatalk 4.9.3
Whenever I install magisk the device can't boot in the OS. It just boots in fastboot mode every time and the only way to get it back is re-install the OS from recovery mode (TWRP). So far I have tested with version 16.0 and 16.4, and got the same results on both.
Any idea why this is happening?
laglink said:
Whenever I install magisk the device can't boot in the OS. It just boots in fastboot mode every time and the only way to get it back is re-install the OS from recovery mode (TWRP). So far I have tested with version 16.0 and 16.4, and got the same results on both.
Any idea why this is happening?
Click to expand...
Click to collapse
Yes, it's normal. It was mentionened in other threasds already, that this happens. 16.7 should work though, only hide does not work properly.
WesTD said:
Change buttons back and recent. Thanks @kevte89
https://drive.google.com/open?id=1SjY1-uIZ0kTayJ0vouHP2LyaKWPHN_SV
Click to expand...
Click to collapse
The "swap back and recent" doesn't seem to be working. I'm running the 09/25 build of Lineage 15.1. After a flash and reboot, the buttons work exactly as before.
I tried finding the source of that file, but the user you linked doesn't seem to have any posts here. Could you link the source thread?
orangeisnon said:
The "swap back and recent" doesn't seem to be working. I'm running the 09/25 build of Lineage 15.1. After a flash and reboot, the buttons work exactly as before.
I tried finding the source of that file, but the user you linked doesn't seem to have any posts here. Could you link the source thread?
Click to expand...
Click to collapse
Or try this, mount Vendor : https://androidfilehost.com/?fid=1322778262903999789
raystef66 said:
Or try this, mount Vendor : https://androidfilehost.com/?fid=1322778262903999789
Click to expand...
Click to collapse
I've been pulling my hair out for the last few days trying to get the back button on the right side. Unfortunately, this one didn't work for me either. Am I doing something wrong? I reboot into TWRP 3.2.1-8, go to mount, select vendor, go to install, select file, voila. Everything says it installs, no errors, etc, and then there's no change when I boot into system again.
orangeisnon said:
The "swap back and recent" doesn't seem to be working. I'm running the 09/25 build of Lineage 15.1. After a flash and reboot, the buttons work exactly as before.
I tried finding the source of that file, but the user you linked doesn't seem to have any posts here. Could you link the source thread?
Click to expand...
Click to collapse
bradyarz said:
I've been pulling my hair out for the last few days trying to get the back button on the right side. Unfortunately, this one didn't work for me either. Am I doing something wrong? I reboot into TWRP 3.2.1-8, go to mount, select vendor, go to install, select file, voila. Everything says it installs, no errors, etc, and then there's no change when I boot into system again.
Click to expand...
Click to collapse
It should work under /verdor
Or do it manualy in /vendor/usr/keylayout/synaptics_dsx.kl or search that file
Code:
key 158 APP_SWITCH
key 102 HOME
key 187 BACK
key 143 WAKEUP
I used it in LOS16 and all other Pie roms and working ok. Never tried it on LOS15
After a few failed attempts (using Audio Modification module etc.) I found a way to get Viper working on the Mi 9. installed on the rooted Xiaomi.eu rom via TWRP and Magisk.
1. Download the Viper4Android_FX-v3.4.2.zip via Magisk but don't install it via Magisk
2. Boot to TWRP and flash the Viper zip and then adhere to the following:
- Press a volume button when prompted to do so
- Volume down (to choose vol key installation method)
- Vol up (for new 2.5.0.5)
- Vol up (for material, if preferred)
- Vol up (for system app)
- Vol up (for lib workaround to be installed)
3. Reboot
4. Via Magisk find and install "Init.d injector" and then reboot
Viper4Android should now be processing your audio!
Rommco05 said:
Installation from Magisk doesn't work? Just curious
Click to expand...
Click to collapse
Not the usual way. On my Pixel 2 XL, either the magisk module would work out of the box or using the Audio Modification Library module would make it work. I tried both of these ways, with no success the driver just wouldn't install. Tried the XDA labs apk, along with the Audio Modification Library, didn't work. Was even waiting a few minutes after boot as I know sometimes/some roms it takes a few minutes to initialise.
After lots of playing around of different versions, I tried that additional installation step of the lib workaround, which states that init.d support is needed too. With the use of that extra init.d module, it works!
I spent some time doing this and figured I'd help out others when they come to do it too!
I managed to install via Magisk?? Maybe due to a Magisk update?
*justintime* said:
I managed to install via Magisk?? Maybe due to a Magisk update?
Click to expand...
Click to collapse
Ahh yeah that's fair enough! Probably flashing via TWRP isn't necessary, so long as the additional init module is there too
Rommco05 said:
Installed init and after Viper4 from Magsik and didn't work, need flash ot trough twrp, today...
Click to expand...
Click to collapse
Ah tgats handy to know! My initial istructions remain valid then
Rommco05 said:
Installed init and after Viper4 from Magsik and didn't work, need flash ot trough twrp, today...
Click to expand...
Click to collapse
Funny with twrp it wasn't working for me...... Magisk had an update. "Check updates canary build' in manager.
And it was a straight away. Flash.... Only no equalizer in usb/dock out though for Android auto
Rommco05 said:
btw after last Magisk update I was able install Viper4 over manager. I also installed that last option (fix)
Click to expand...
Click to collapse
Thanks, that's handy to know!
I simply couldn't get viper4android to work and didn't have much luck with the init.d injector... I ended up following your steps and installed a custom kernel and emulated init.d via the kernel auditor app.... Now its working perfectly!
Have any of you tried the ainur sauron mod on the mi 9?
hi is it possible to get viper4android work with magisk flash? because i don't want twrp and loosing encryption.
when i flash trough magisk viper4android app doesn't appear?
thank you
(sorry for bad english)
dffhgg said:
hi is it possible to get viper4android work with magisk flash? because i don't want twrp and loosing encryption.
when i flash trough magisk viper4android app doesn't appear?
thank you
(sorry for bad english)
Click to expand...
Click to collapse
Possibly...
Have you tried rebooting? Otherwise I'm unsure I'm afraid....
cd993 said:
Possibly...
Have you tried rebooting? Otherwise I'm unsure I'm afraid....
Click to expand...
Click to collapse
yes for sure i rebooted many times but no success..
always viper4android doesn't appear
i also tried install via apk download viper4android then install there also not work, after reboot it reask to install driver.
dffhgg said:
yes for sure i rebooted many times but no success..
always viper4android doesn't appear
i also tried install via apk download viper4android then install there also not work, after reboot it reask to install driver.
Click to expand...
Click to collapse
And this is with the init d module as well?
with init.d injector module from magisk? yes i installed it alredy
dffhgg said:
with init.d injector module from magisk? yes i installed it alredy
Click to expand...
Click to collapse
And you're on the latest eu rom?
Hmm all I can suggest is to remove fully uninstall viper, the init d module and make sure no other audio mods are installed, reboot, then install viper again (ensuring to choose yes to the lib workaround) and the init d module.
If that doesn't work, then unfortunately I'm out of ideas as I tried lots 9f things and this was the only method that worked for me.
Good luck
yes i'm on 10.2.17
i will give it a try and let you know.
hope will work thank you
dffhgg said:
yes i'm on 10.2.17
i will give it a try and let you know.
hope will work thank you
Click to expand...
Click to collapse
I'm on the latest weekly 9.4.11, if that makes any difference
can i flash this version whithout data loss?
i tried reinstall everything but no succes
hi guys my problem is solved!
what i did:
change selinux to permissive with this tool: Kernel SEPolicy patcher https://zackptg5.com/android.php
now viper4android is detect driver its full work!
dffhgg said:
hi guys my problem is solved!
what i did:
change selinux to permissive with this tool: Kernel SEPolicy patcher https://zackptg5.com/android.php
now viper4android is detect driver its full work!
Click to expand...
Click to collapse
Great! I'll save that just in case I ever need it
keep getting the following error
Checking for Digest files
Skipping Digest check: no digest file found
on twrp 3.3.0 b8 and latest EU rom
Has anyone been able to successfully install a treble enabled GSI e.g AOSP onto the A80? Also if so, what current issues are there with this device running a treble GSI and is there anyone maintaining it? Thanks.
yes havoc 2.9 workod for me
blackbuga said:
yes havoc 2.9 workod for me
Click to expand...
Click to collapse
how did you install?
Yes would be great to know how you flashed it? I noticed they now have twrp working for our device but I wonder how easy it is to flash a gsi and to what extent things work e.g fingerprint and camera mainly?
any feedback since we now have a functional twrp?
I would say the TWRP made is not that functional, you can’t transfer files through TWRP once you wipe data for some reason. I tried wiping data before flashing a GSI and my computer would then literally not read the phone storage, nothing would come up. Also other ways I tried to do it without transferring over TWRP did not work. Once I got passed it and flashed a gsi, I would just get a bootloop...
So I’m not entirely sure where to go from there to be honest. I re flashed stock and am staying in stock till TWRP is more functional and a GSI is able to be booted.
danielfrancisarthurs said:
I would say the TWRP made is not that functional, you can’t transfer files through TWRP once you wipe data for some reason. I tried wiping data before flashing a GSI and my computer would then literally not read the phone storage, nothing would come up. Also other ways I tried to do it without transferring over TWRP did not work. Once I got passed it and flashed a gsi, I would just get a bootloop...
So I’m not entirely sure where to go from there to be honest. I re flashed stock and am staying in stock till TWRP is more functional and a GSI is able to be booted.
Click to expand...
Click to collapse
did u tried transfer files through adb sideload?
I could not get adb sideload to work, my computer would not recognise the device at all through adb
Hey guys, was wondering if anyone has been able to successfully flash a GSI on the A80? If so, how and which one/s?
LDP12 said:
Hey guys, was wondering if anyone has been able to successfully flash a GSI on the A80? If so, how and which one/s?
Click to expand...
Click to collapse
From A80XDA Telegram Group:
1) Make sure Magisk is properly installed (patch AP) and running on your device first, likely because we need it to disable dm-verity
2) Download any ARM64 AB GSI and rename the image (*.img) to system.img.ext4
3) Pack it into tar format (e.g. 7-zip)
4) Flash via Odin
5) Enter stock recovery and wipe data
Havoc OS
EJYM said:
likely because we need it to disable dm-verity
Click to expand...
Click to collapse
How did you do this?
Captain Beretta said:
How did you do this?
Click to expand...
Click to collapse
I just properly installed Magisk. I did not do anything else.
EJYM said:
I just properly installed Magisk. I did not do anything else.
Click to expand...
Click to collapse
So you have Havoc GSI running on your Samsung Galaxy A80?
Is that Android 9 or 10 version?
Captain Beretta said:
So you have Havoc GSI running on your Samsung Galaxy A80?
Is that Android 9 or 10 version?
Click to expand...
Click to collapse
Yes, Havoc-OS v3.6.
Android 10
EJYM said:
Yes, Havoc-OS v3.6.
Android 10
Click to expand...
Click to collapse
Thanks, it worked!
Takes some time to setup up and configure things... like corner roundness and some bluetooth disconnect bugs, but all running fine now: even TWRP and root!
Too bad fingerprint scanner does not work, but cool that now face unlock does work!
After some time playing around with Havoc:
I really miss fingerprint unlock and the Always On Display. Did you manage to enable Pixel's built in Ambient Display (always on) and use fingerprint unlock? Some 3rd party always on apps are no option for me, I tested them all and they are no good.
Captain Beretta said:
Thanks, it worked!
Takes some time to setup up and configure things... like corner roundness and some bluetooth disconnect bugs, but all running fine now: even TWRP and root!
Too bad fingerprint scanner does not work, but cool that now face unlock does work!
After some time playing around with Havoc:
I really miss fingerprint unlock and the Always On Display. Did you manage to enable Pixel's built in Ambient Display (always on) and use fingerprint unlock? Some 3rd party always on apps are no option for me, I tested them all and they are no good.
Click to expand...
Click to collapse
You're welcome. I did not try, I don't use Ambient Display. Haven't been able to get fingerprint unlock working yet.
Are you able to transfer files using USB and use USB headphones?
EJYM said:
Are you able to transfer files using USB and use USB headphones?
Click to expand...
Click to collapse
Nope, now that you mention it, USB file transfer does not work. USB-headset also does not work, audio just keeps playing over phone speakers.
Bluetooth audio (bluetooth speaker and bluetooth headset) did not work (kept disconnecting/connecting), but after fiddling with some settings it works now.
So all USB things fail, bluetooth is ok now.
its doesnt work
EJYM said:
From A80XDA Telegram Group:
1) Make sure Magisk is properly installed (patch AP) and running on your device first, likely because we need it to disable dm-verity
2) Download any ARM64 AB GSI and rename the image (*.img) to system.img.ext4
3) Pack it into tar format (e.g. 7-zip)
4) Flash via Odin
5) Enter stock recovery and wipe data
Havoc OS
Click to expand...
Click to collapse
I tried to do your method, but it didn't work, and I tried the same method, but using TWRP, but it didn't work.
I made a complete formatting and it didn't work, and I deleted the system and it didn't work too. Please give me a solution
kkmmee94 said:
I tried to do your method, but it didn't work, and I tried the same method, but using TWRP, but it didn't work.
I made a complete formatting and it didn't work, and I deleted the system and it didn't work too. Please give me a solution
Click to expand...
Click to collapse
Did you extract the .img file from the .xz file before you packed it into .tar file?
The fact that usb doesn't work means that the adapter from type-c to 3.5 also doesn't work?