Related
Dear Owners,
Discontinued
In this post you can find a multilingual (mainly European) modified rom for the smartphone Lenovo A820.
IMPORTANT NOTE!
The newer phones do not work well with S138 or older kernel (no info about S147).
The sympthom is that the touch screen works on inappropriate way: after the first screenlock it does not work again.
For this reason it is highly recommended that update your kernel if you have got this issue.
The kernel changer to S150 zip can be run from modified recovery (CWM, TWRP, COT, Carliv, etc...).
Note that all the things in this thread you do with your phone can be dangerous. I cannot take responsibility for your phone damage.
So, do it at your own risk.
Before you do anything, I recommend you to save your current ROM (I would say it is mandatory!)
There are many ways to save and I highlight some (links will be added later):
1, for non-rooted phones:
- SP_Flashtool, readback option.
- CWM (or TWRP) backup, if it is available on your phone
2, for rooted phones:
- MTKDroidTools backup
- command line dd-backup
In order to install this ROM, you need to have CWM recovery on your phone.
If you have not got this recovery or you do not know which recovery you have got, you have to read post#3 before you do anything.
If you get error during the installation of the ROM, see post#4.
The restore option of the CWM rcovery is not as good as it could have been expected, so please read post#4 carefuly for CWM restoration issues, tricks.
Update: CWM 6.0.4.0 with S150 stock kernel.
Just to clarify the power-on modes:
Normal phone mode: press the power button
Meta mode: VOLUME DOWN + POWER
Factory mode: VOLUME UP + POWER
Recovery mode: VOLUME DOWN + VOLUME UP + POWER
Consider the warranty issues, you need to backup you rom.
In addition, I always suggest to do a backup before install any new ROM to your phone.
You can do it with CWM recovery in backup menu.
About installation in general.
Pre-requisites: CWM recovery menu installed on your phone. (This ROM can be installed from CWM recovery.)
The ROM file must be saved on your physical SD card.
Enter into CWM recovery.
In CWM recovery you can go up/down with the volume up/down keys. The “enter” is the power button.
Choose the “install zip from SD card” menu item.
Choose the “choose zip from SD card” menu item.
Select the rom you want to install.
Choose “OK” in the menu item.
If you need a detailed explanation of its use, see the tutorial : http://bm-smartphone-reviews.blogspot.com/2012/02/complete-guide-to-clockworkmod-recovery.html
Right after the ROM installation has been finished, you can install gapps as well, before restart.
Windorws driver installation:
Please do not ask me about it. I use mainly Linux, which is more friendly.
What I did in XP under Virtualbox was:
Downloaded the Lenovo drivers from here: <link>
Manually added the com ports in control panel.
MOD CP4.0
V1
The modified rom has got the stock kernel - Lenovo A820_ydss_S135_130403
This completely changes your phone appearance, your Lenovo UI will be disappeared.
Also Lenovo applications are not integrated to this rom.
It will look like the stock Jelly Bean.
Main features:
-The firmware is rooted.
-Boot logo, boot/shutdown animations and sounds are changed to Lenovo.
-Minimalist appearance and content, for this reason you have to install google applications manually, from CWM recovery <link>. After gapps installation everything works well (many people wants to have mainly Google Play. It do work.)
-Slide unlock.
-Multilingual. For supported languages, see the screenshots.
-The default language/region is Hungarian, but you can easily choose your one.
Known bugs:
- I found was that the charging logo with turned off phone is not proper.
-the camera does not work adequately in video-camera mode.
-the default setting in some of the application is V987.
V2
The modified rom has got the stock kernel - Lenovo A820_S135_130403
The camera was changed to a non-multilingual one. It looked that the black screen in camcorder mode solved.
But after googleapps something went wrong... black screen again.
V3
The modified rom has got the stock kernel - Lenovo A820_S135_130403
In V3 there is not any significant changes (camera app was changed back to the multilingual one), but I modified the gapps, which caused the camcorder issue.
So, for this modified rom you need to use this gapps.
V3 download link: CP4.0-by-cappa72-v3 - dropbox
or
CP4.0-by-cappa72-v3 - 4shared
Bug: Still, the camera has got green lines in the case of playback.
CP4.1
V1
The kernel has changed to A820_YDSS_S130_130324.
The camera application does not generate green bands in playback.
The default language was set to English, default time zone was set to London.
CP4.1-by-cappa72-v1
You can use the googleapps mentioned for CP4.0-v3
CP4.2
V1
The kernel has changed to A820_S138_130419
CP4.2-by-cappa72-v1
Bug list
#3 - CP4.2-v1 - Wen try to choose themes, the laucher is Force Closed (FC) - Settings was modified to resolve this issue.
#4 - CP4.2-v1 - Serial number is 0123456789ABCDEF instead of the original S/N - not a real bug
#5 - CP4.2-v1 - Under the battery level of 15% the SystemUI is Force Closed (FC) - was a user error, when people deleted the necessary ui files.
CP4.3
This release will be the continuation of the 4.2, but with the newest available kernel (S150) and will (plan) contain all the things that are included in the 5.3.
This will not be with Aromainstaller and will contain the gapps.
Hopefully comng within two weeks.
MOD CP5.3
Available now (25.11.2013.)
CP5.3
V1
Change log; what’s new compared to CP4.2
Aromainstaller is used for optional installation possibilities.
- still Jelly Bean 4.1
- kernel is the stock S150
- Modified systemUI by [email protected] (1% battery signal; automatic hide function for non-used sim signal)
- Modified Settings by apeelme (sloving bug #3)
- Baseband is from the stock ROM S150.
- gps.conf is set to EU by default
- apns.xml is modified for Telenor-HU from “net” to “online”
- gps-tracker solver added to build.prop (dalvik.vm.execution-mode=int:fast)
- libvcodecdrv.so replaced to solve green bars in case of video playback.
- updated MobileUncleTools (2.9.5) in case of 3rd party SW.
There is no default ringtone set! Right after the installation you have to set the ringtone, message alert and so on... otherwise your phone will not play sound...
Important feature!
If you have already repartitioned with the script, you can simply install this ROM, it will recognise that the repartition had been done; and you do not have to run "disable internal SD card" script from CWM.
But please note that this function is onyl available with the repartition script; with Meteos rom editor repartitioning this function is not available.
Right after the installatio, there is not any sound set. Nor the ringtone, nor the message an alert. So, you have to set it first.
Available on mediafire : Link
md5sum: 86e241fcac6faf4fa6baf0f9cc4a18a0
Additional possibility:Change of FM radio
The FM radio can be changed back to Lenovo’s one with this script. It was requested by some people due to the fact that Lenovo’s FM radio can work without connecting the earphone.
The link is here. http://data.hu/get/6494163/FM-radio-change.zip
You can install it from CWM recovery, with the same method that you used during the installation of the ROM. This script does not affect any other part of the ROM, but the FM radio.
Repartition
Please DO NOT USE IT for Lenovo-based ROMs. Sometimes it can cause bootloop or other inconvenience.
The repartition of internal memory of the Lenovo A820 phone has been solved already.
With this action youd intednal SD card will be disappeared and will be added to the /data partition.
Before you do anything, make a CWM backup, and save all your data from internal SD card!
The easiest way is to use this CWM script, if you want to have the maximum available size (2,7GB) for the /data partition.
You have to install it from CWM recovery.
After the installation you need to do a factory reset.
After the factory reset, you have to disable your internal SD card, with CWM script.
And then, you can reboot your phone to check if yo have got the new size of /data partition:
settings --> storage
"internal data storage; full capacity 2,7GB"
"internal SD card; full capacity <your physical SD card capacity"
If the above data appear, you have successfully repartitioned you phone's internal memory!
If you want to have your data back, go into CWM recovery, and choose
backup and restore --> advanced restore --> <choose your save> --> Restore data
And then, your data are available again, after the reboot.
Please do not use it, if you do not want to have the 2,7GB of /data partition!
For Lenovo-based ROMs you need to use Meteos-apk for repartition of A820.
Internal/external SD card exchanger
If you want to use your physical SD card as the default one, and still want to use your emmc-SD card (aka internal SD card by default), you can change it by this CWM script.
Important link in summary:
The driver what works is here.
The original stock recovery is here
The autoroot package can be found here.
The preferred CWM is here.
The root script is here, you can install is from CMW, and your phone will be rooted.
The usable Flashtool is here.
The scattel file for Flashtool is here.
Credits:
bgcngm for the base of the ROM (BM1.0 for ZTE V987), and his amazing tutorials
iBotPeaches and brut.all for apktool
dsixda for his ROM kitchen which is really helpfull for easy-deodexing
Koush for his wonderfull CWM recovery
amarullz for his amazing AROMA installer
...and finally to all the devs whose apps, tweaks and scripts I have used on my custom ROMs
Very nice Thanks for your hard work and good luck
CWM recovery
Installing CWM on your phone
You need to install proper drivers to your computer.
Available (ported) CWM recoveries:
With newest kernel:
CWM recovery 6.0.1.2 - S150 - ported from [email protected] ZTE V970 recovery.
CWM recovery 6.0.4.0 - S150 - ported from [email protected] ZTE V967S recovery.
CWM recovery 6.0.1.2 - S138 - ported from [email protected] ZTE V970 recovery.
CWM recovery 6.0.1.2 - S135 - ported from [email protected] ZTE V970 recovery.
Option 1, with SP Flashtool
Download the SP_Flashtool software to your computer. Extract it to a directory, where you want to run it from.
Download the scatter file, which you will need if you want to use SP_Flashtool.
Download the CWM
(5.5.0.4, 6.0.1.2, 6.0.2.8; it is your decision)
Run the SP_Flashtool.
Browse your scatter file.
Choose only the recovery.
Tick the “DA DL all with checksum” (you can find it close to the download button). It is a really important point!
If your phone is connected, let’s disconnect it from the computer.
Turn off your phone. Take the battery out from your phone for 5 sec. Insert the battery to you phone. Keep it still turned off.
In the flashtool press the Download button.
Choose OK to the warning message.
Connect your phone to the computer.
The flashtool will flash the recovery into your phone.
When the green circle appears, wait for 5-10 secs, and the unplug your phone.
If everything went well, you can enter into the recovery menu (see 1st post, power-on modes)
Option 2, on rooted phone, with MobileUncleTools.
Install MobileUncletools 2.8.x or higher from the Play Store.
Save one of the CWM I linked to the root directory of your physical SD card.
- select menuitem Recovery Update. The program will list the available recovery images.
- choose the one, what you want to install
- It asks back: "Are you sure flash recovery!" - Use recovery file: <name of the recovery what you choose previously>. Tap to OK.
- After the flashing process it offers you to reboot into recovery. If you tap OK, it will automatically reboot your phone to recovery. If you tap cancel, you can use your phone as a phone.
- Before you tap to "reboot to recovery", I suggest you to wait approx. 5-10sec.
Use of the CWM.
If you enter into the CWM (6.x.x.x) recovery, the following buttons can be used:
- Power button : “enter”
- Volume down : step down in the menu
- Volume up : step up in the menu
- Soft key “option”: step down in the menu
- Soft key “back” : step back in the menu
In 5.x.x.x you cannot use soft keys, but the physical buttons works on the same way as in the case of 6.x.x.x
CWM restoration
I experienced failures in restoration of the CWM backup.
This was a real surprise for me because I have not faced this issue with other MTK phones.
So, the issue is that the CWM restoration does not work immediately.
In details:
-I saved the stock rom by CWM 6.0.1.2 (CWM was complied by Bruno, and I modified it for A820)
-For checking the restore function, I did a factory reset: the phone stopped working.
-I did the CWM restoration, but still the phone stopped at the boot animation. And stayed it for 15min. I removed the battery then.
In order to solve the issue, the following method was done:
-In the advanced restore I choose the restore /system (only!)
-After restoring the /system I turned off the phone took the battery out, waited 5 secs, inserted the battery back.
-Turning on the phone it worked again with the restored data, BUT the internal SD card was injured! I formatted the internal SD card – with this action I lost all my data that were saved on the internal SD card.
So, please be careful using it! Save your internal SD card data before the CWM restoration!
This was experience in case of all the available CWM (5.5.0.4, 6.0.1.2, 6.0.2.8).
Installation issues
Post#4 troubleshooting
If you cannot install the ROM by an error:
Code:
assert failed: getprop("ro.product.model") == "Lenovo A820"
E:Error in /sdcard/Lenovo-a820-update-CP4.0-v1.zip (status 7)
This is a safety feature, not a bug.
This error message is a warning that you have not got the proper CWM. (Most of the available CWMs are based on ZTE, STAR phones and contain improper model description.
My CWMs contain the proper one, I modified them, so you need to install a CWM I mod for Lenovo A820.
In this case you have to update your CWM to a ported one that I did.
Great!
I would love an multi lingual rom, but for now I just want to root it. (ones it gets delivered that is)
Are there tools specific for this device to root is with out flashing?
Checking out your rom in the meantime. :fingers-crossed:
ebsbow said:
Great!
I would love an multi lingual rom, but for now I just want to root it. (ones it gets delivered that is)
Are there tools specific for this device to root is with out flashing?
Checking out your rom in the meantime. :fingers-crossed:
Click to expand...
Click to collapse
If you have got CWM recovery on your phone (or a chinese one that has got "xx SD yyy ZIP" menuitem), then you can use root-zip, installing it from CWM recovery.
Thanks
Thanks
Where are the screenshots?
please add some screenshots.
deathhand said:
please add some screenshots.
Click to expand...
Click to collapse
I tried to upload some, but the server was down that time.
I will try it again tomorrow.
Thanks for this rom, I flashed it succesfull on the Lenovo A820, it also takes away that terrible skin from Lenovo.
Gapps link
Thnak you for your ROM. I tried it for a couple of hours and there some minor problems that I don´t know if there are rom related.
1. There is no link to the gapps, so I downloaded a random one and I have errors with google search.
2. The videocam record with a green band on one side.
3. The gps is slow, doesn´t pick satellites easily.
4. If you choose automatic time the it always consider that you´re in china. If you choose manually your timezone then it is ok.
Overall it is a very well-done rom and I would keep it for daily use.
Thanks
1. Are you sure you downloaded the Gapps for Android 4.1.x? You should have this gapps version: gapps-jb-20121011-signed, this the right version you should flash. I first flashed the rom and after that the gapps.
I have reproduced your issue and you need to update the Google search app in the playstore, after that the errors are gone.
2. I have reproduced what you reported, I want to try if I can grab the original camera app from Lenovo and see if it still has the issue, but I don't think its a big problem, I bought the phone for someone else, but this issue is not to big, I don't suppose people often record with an smartphone and this rom at least got Dutch in, the original phone firmware was bloated with China Unicom bloatware, Lenovo skin and had no Dutch support.
3. Try GPSfix, ussualy this kinda works, but the MT6577 chip was know for having GPS problems, perhaps its the same with MT6589? But there are many apps out there that can help you fix it.
I think this in a great rom, Lenovo is a big brand in China, so many will choose Lenovo and with this rom you get rid off the terrible lephone skin, I mentioned this rom in my review about this phone
Oh here you got some screenshots.
Feel free to use them in the OP.
Don't know about you but I do use my device a lot for video recording.
I think it is imperative that all basic functions work flawlessly.
The custom rom's with android 4.2 also have an video bug at this time, which is a bit unacceptable.
I'm sure it will be sorted out :victory:
Well yes, but having fully Dutch support is better, you can always flash new update off the custom rom when it get fixed. I only recorded a few time video with my own smartphone.
Lebrija said:
Thnak you for your ROM. I tried it for a couple of hours and there some minor problems that I don´t know if there are rom related.
1. There is no link to the gapps, so I downloaded a random one and I have errors with google search.
2. The videocam record with a green band on one side.
3. The gps is slow, doesn´t pick satellites easily.
4. If you choose automatic time the it always consider that you´re in china. If you choose manually your timezone then it is ok.
Overall it is a very well-done rom and I would keep it for daily use.
Thanks
Click to expand...
Click to collapse
1, I have added the link.
2, Thanks for the feedback, it is really useful to know. The playback contains the green band, the file itself does not.
I changed the kernel to the '130'-one, and now it works with the camera application, and the playback is also correct.
3, You shall try the EPO / A-GPS support for getting it better. Or thy DexterMorganNL's suggestion.
4, I have never faced this issue, but in the new version I set the default time zone to London.
The new one is available, you can see it in the first post.
cappa72 said:
1, I have added the link.
2, Thanks for the feedback, it is really useful to know. The playback contains the green band, the file itself does not.
I changed the kernel to the '130'-one, and now it works with the camera application, and the playback is also correct.
3, You shall try the EPO / A-GPS support for getting it better. Or thy DexterMorganNL's suggestion.
4, I have never faced this issue, but in the new version I set the default time zone to London.
The new one is available, you can see it in the first post.
Click to expand...
Click to collapse
Thank you for your time. I will try the new version. But, why have you used an older kernel?
By the way, with version 3 I also had some problems with the gyroscope when playing Real Racing 3.
Great work
Its great you released the update so fast, you brought us really good work. I think new owner off this phone is going be thankful, they requested me to buy a phone for them while I'm in China, and when I got it it was not fully Dutch supported, had the terrible skin.
So its great have this phone, because this way I can deliver it without the Chinese bloatware and with full Dutch language and ofcourse Google apps.
EDIT
The newest release gives me a black screen after I boot it up after having it flashed, so I have reverted back to your previous release.
OK. I'm ready to weep.
I've previously had a ROM from NeedRom on my A820.
I'd like to give Cappa's ROM a try, but when I try to install from CWM Recovery I hit the Error outlined in Post 4.
I then follow the advice of Post 3... But there are no links to A820-compatible CWM Recovery installations. I found one on a hungarian site linked to Cappa, but all I get is a .img file and no idea how to get that on to my phone.
Can anyone post detailed instructions, or send me to a page (in English) where I can find instructions on how to get the ball rolling so I can use Cappa's ROM?
Thanks.
Google is my friend. Yes. But Google Translate isn't.
TheTen said:
OK. I'm ready to weep.
I've previously had a ROM from NeedRom on my A820.
I'd like to give Cappa's ROM a try, but when I try to install from CWM Recovery I hit the Error outlined in Post 4.
I then follow the advice of Post 3... But there are no links to A820-compatible CWM Recovery installations. I found one on a hungarian site linked to Cappa, but all I get is a .img file and no idea how to get that on to my phone.
Can anyone post detailed instructions, or send me to a page (in English) where I can find instructions on how to get the ball rolling so I can use Cappa's ROM?
Thanks.
Google is my friend. Yes. But Google Translate isn't.
Click to expand...
Click to collapse
Update, I think I sorted it...
Bit of imagination (and could have totally done the wrong thing, but it seems to be making progress...)
I decided to take a known ROM install that I've tested and that works, which has a recovery.img included, and I renamed the recovery.img to recovery_bak. I then renamed my 'new' CWMRecovery image to recovery.img and dumped it in the directory with the ROM data that I got off NeedRom. I loaded up SPFlashTool and loaded the scatter file from that ROM, then deselected every component except 'recovery' and flashed it.
End result is that I have a phone which recovery-boots to the version 6 cappa-modded CWMR which I found on the Hungarian site, and in turn that CWMR has just installed both the required ZIP updates outlined in Post 1, and Cappa's ROM is now sat on my second A820 awaiting setting up...
I hope I did the right thing, and this won't come back to bite me in the ass later... The newer recovery.img was slightly larger than the old one, but I'm assuming that the scatter file isn't about storing specific pieces of the ROM in specific places based on exact size of file, and thus perhaps all things will continue to work swimmingly.
It seems there are some conflicting reports on the issue. Some people say that rooting Oreo can't be done because there is an issue with Magisk/SuperSU preventing it, while others says they've managed to root their Oreo A8.
I would just like to get an idea of anyone who has tried to root Oreo. Please share your experience to date.
Did it fail or was it successful?
Is everything running smoothly?
What method and steps did you use?
I'm sure I'm not the only one who would appreciate the feedback.
it failed
no natter what i did
on modifying the /system through twrl, on reboot, the os locks the sim, uninstalls the Samsung apps like pay/health etc and then re encrypts the phone
shunsai said:
It seems there are some conflicting reports on the issue. Some people say that rooting Oreo can't be done because there is an issue with Magisk/SuperSU preventing it, while others says they've managed to root their Oreo A8.
I would just like to get an idea of anyone who has tried to root Oreo. Please share your experience to date.
Did it fail or was it successful?
Is everything running smoothly?
What method and steps did you use?
I'm sure I'm not the only one who would appreciate the feedback.
Click to expand...
Click to collapse
Yep
https://forum.xda-developers.com/ga...--other-development/root-magisk-oreo-t3825096
Used Ashyx TWRP and no-verity-opt-encrypt_ashyx, from corsicanu's thread. I've used Magisk v16.0 stable as well as beta v16.7.
Root is working for ADB, Termux and Xposed (installed as Magisk module). Root is not working for Titanium (says it can't detect root; used Magisk busybox) and for Stericson's Busybox (says unverified binary and won't install). Another thing I've noticed is that microG's UnifiedNlp "self check" says NO to "UnifiedNlp is registered in system".
Magisk was showing as "not installed" in Magisk Manager for a while, but switched to green (installed) after a few reboots. Not sure what I've done to change it. I suspect it's a certain combination of TWRP and no-verity-opt-encrypt that does the trick, because I've been alternating between Mesa's and Ashyx's versions. Magisk root was working even when Manager was saying "not installed".
I will retry with a clean reinstall of Oreo 8.0.0, Mesa's TWRP and no-verity-opt-encrypt-6.0.zip from his TWRP thread. I'm on official ROM A530FXXU2BRG1.
I haven't tested SuperSU much, I will try it more thoroughly. (Personally I don't care about systemless and hiding from SafetyNet or *Pay stuff, so whatever root method works is fine with me.)
Whatever you do, a piece of advice: follow whatever guide you're using carefully, because not doing all the steps properly can end up in a mess (eg. bootloops, or you get a screen asking for password to decrypt phone that won't go away). Also, it seems that mixing flashable stuff from different sources is a bad idea unless you know what you're doing.
Same as above. Best working combination I've found is Mesa's TWRP and no-verity, with Magisk 16.7 and Manager 5.8.3.
Root works with mostly everything I've thrown at it, with the following notable exceptions:
* Titanium Backup triggers the popup to ask for root, but says "Sorry, I could not acquire root privileges."
* UnifiedNlp's self check says "can't integrate with system".
* As soon as you flash Magisk, MTP and ADB stop working. When you connect to the PC there's no popup for either "allow connection" or ADB fingerprint.
Mesa's kernel fixes the MTP issue, and PC connection "allow" popup starts working again.
On the flip side, attempting to enter developer settings while running Mesa's kernel crashes the settings app. I've used a terminal app (Termux) to enable ADB manually (or you can enable it before you flash the kernel):
Code:
settings put global development_settings_enabled 1
settings put global adb_enabled 1
Here's everything I've gathered about the process (or as I like to call it, "how to get root on A8 2018 in 20 easy steps"):
* Start the phone, enable OEM lock from developer settings. Never disable it again, it prevents the phone from booting if any of the partitions are unofficial.
* Use Odin 3.13 or later, earlier versions can't deal with the new LZ4 compression Samsung applies to the partition images. Heimdall is very old and will not work. If you're on Linux, use a virtual machine to run Odin under Windows. VirtualBox is excellent (remember to connect the phone from VB's USB menu when in download mode).
* Power+VolDn+VolUp from any situation will force reboot. Power+VolDn+VolUp immediately after start enters download mode.
* Flash BL, AP, CP and CSC from an official ROM to bring the device to factory status.
* At this point you phone is functional, if you don't want root and just want to use it, stop here.
* If you intend to continue, I recommend that you don't boot to system.
* Reboot and re-enter download mode, flash Mesa's TWRP.
* Reboot and immediately press Power+VolUp to enter TWRP. Do NOT boot to system just yet, you can trip the anti-theft protection.
* [Always] swipe to allow modifications when entering TWRP.
* You may want to grab a TWRP backup of various partitions at this moment. Recovery is obviously not official anymore, but you can grab boot, system, efs, baseband, modem etc. Very good idea. If your SD card is not large enough for system (has 3.5 GB) at least grab the others.
* From Wipe menu, choose format data. Boot to RECOVERY. Do not install TWRP app.
* From Mount menu, verify that Data is mounted.
* Flash in this order: RMM fix and no-verity.
* Reboot to system, let it work (Samsung logo and blue led flashing). Yes, it may take a lot of time, let it work.
* At this point you have a clean system with custom recovery but no root. Check that stuff is still working fine.
* During phone setup, do NOT check "send diagnostic data".
* Reboot to TWRP, flash Magisk.
* Again, the first boot may take a long time, let it work.
wirespot said:
Same as above. Best working combination I've found is Mesa's TWRP and no-verity, with Magisk 16.7 and Manager 5.8.3.
Root works with mostly everything I've thrown at it, with the following notable exceptions:
* Titanium Backup triggers the popup to ask for root, but says "Sorry, I could not acquire root privileges."
* UnifiedNlp's self check says "can't integrate with system".
* As soon as you flash Magisk, MTP and ADB stop working. When you connect to the PC there's no popup for either "allow connection" or ADB fingerprint.
Mesa's kernel fixes the MTP issue, and PC connection "allow" popup starts working again.
On the flip side, attempting to enter developer settings while running Mesa's kernel crashes the settings app. I've used a terminal app (Termux) to enable ADB manually (or you can enable it before you flash the kernel):
Here's everything I've gathered about the process (or as I like to call it, "how to get root on A8 2018 in 20 easy steps"):
* Start the phone, enable OEM lock from developer settings. Never disable it again, it prevents the phone from booting if any of the partitions are unofficial.
* Use Odin 3.13 or later, earlier versions can't deal with the new LZ4 compression Samsung applies to the partition images. Heimdall is very old and will not work. If you're on Linux, use a virtual machine to run Odin under Windows. VirtualBox is excellent (remember to connect the phone from VB's USB menu when in download mode).
* Power+VolDn+VolUp from any situation will force reboot. Power+VolDn+VolUp immediately after start enters download mode.
* Flash BL, AP, CP and CSC from an official ROM to bring the device to factory status.
* At this point you phone is functional, if you don't want root and just want to use it, stop here.
* If you intend to continue, I recommend that you don't boot to system.
* Reboot and re-enter download mode, flash Mesa's TWRP.
* Reboot and immediately press Power+VolUp to enter TWRP. Do NOT boot to system just yet, you can trip the anti-theft protection.
* [Always] swipe to allow modifications when entering TWRP.
* You may want to grab a TWRP backup of various partitions at this moment. Recovery is obviously not official anymore, but you can grab boot, system, efs, baseband, modem etc. Very good idea. If your SD card is not large enough for system (has 3.5 GB) at least grab the others.
* From Wipe menu, choose format data. Boot to RECOVERY. Do not install TWRP app.
* From Mount menu, verify that Data is mounted.
* Flash in this order: RMM fix and no-verity.
* Reboot to system, let it work (Samsung logo and blue led flashing). Yes, it may take a lot of time, let it work.
* At this point you have a clean system with custom recovery but no root. Check that stuff is still working fine.
* During phone setup, do NOT check "send diagnostic data".
* Reboot to TWRP, flash Magisk.
* Again, the first boot may take a long time, let it work.
Click to expand...
Click to collapse
Were you able to test from a non-tripped Knox and if so was it tripped by your process?
I don't have another phone with the e-fuse not tripped so I can't test, but USB works perfectly fine until you flash root and also after you flash Mesa's kernel.
Pipsname said:
Were you able to test from a non-tripped Knox and if so was it tripped by your process?
Click to expand...
Click to collapse
Un-tripped Warranty Bit and Root are two thing that can't stay together lol
---------- Post added at 06:01 PM ---------- Previous post was at 06:00 PM ----------
wirespot said:
On the flip side, attempting to enter developer settings while running Mesa's kernel crashes the settings app.
Click to expand...
Click to collapse
Never heard about this issue; Could you please share a log of the error to look at it to fix it? A new version of the kernel is under-the-hood so would be nice to fix all the possible issues
BlackMesa123 said:
Un-tripped Warranty Bit and Root are two thing that can't stay together lol
Click to expand...
Click to collapse
I am currently rooted on 7.1.1 with no tripped Knox so I was wondering if it was possible with Oreo.
Pipsname said:
I am currently rooted on 7.1.1 with no tripped Knox so I was wondering if it was possible with Oreo.
Click to expand...
Click to collapse
Rooted without tripping Warranty Bit? And how since bootloader checks binary signatures at each boot lol
BlackMesa123 said:
Never heard about this issue; Could you please share a log of the error to look at it to fix it? A new version of the kernel is under-the-hood so would be nice to fix all the possible issues
Click to expand...
Click to collapse
Kernel log? Would an export from logcat do?
wirespot said:
Kernel log? Would an export from logcat do?
Click to expand...
Click to collapse
Nah a simple logcat is what I need lol. Use Logcat Extreme if you don't wanna use adb
BlackMesa123 said:
Nah a simple logcat is what I need lol. Use Logcat Extreme if you don't wanna use adb
Click to expand...
Click to collapse
Lel I use matlog
In some hour (or maybe less lol) the new version of my custom kernel will be released, with a good present for you all... ?
BlackMesa123 said:
In some hour (or maybe less lol) the new version of my custom kernel will be released, with a good present for you all... ?
Click to expand...
Click to collapse
I can't open the therd image.
BlackMesa123 said:
Rooted without tripping Warranty Bit? And how since bootloader checks binary signatures at each boot lol
Click to expand...
Click to collapse
I used your guide.
https://forum.xda-developers.com/ga...recovery-twrp-3-2-2-0-galaxy-a8-2018-t3818201
Pipsname said:
I used your guide.
https://forum.xda-developers.com/ga...recovery-twrp-3-2-2-0-galaxy-a8-2018-t3818201
Click to expand...
Click to collapse
Lol that's faked userspace warranty bit prop. Go in Download Mode and you see Warranty Bit is actually blown
BlackMesa123 said:
Lol that's faked userspace warranty bit prop. Go in Download Mode and you see Warranty Bit is actually blown
Click to expand...
Click to collapse
Well would you look at that! Thank you.
Is Magisk 16.7 Beta?
Samsung Galaxy (SM-A530F/DS) A8 (2018), Android 8.0.0.
After 129 hours I got OEM Unlock. I installed TWRP 3.2.3-0. In TWRP > Wipe>Format Data and follow the instructions in screen. After I flashed latest no-verity-opt-encrypt zip and RMM Bypass zip. Reboot System.
In TWRP I flashed MCK-Oreo_A8_BRG1_v1-fix.zip. Reboot System.
In TWRP I flashed Magisk 16.7 Beta. Reboot System.
I installed Magisk Manager 5.8.3. and I got this:
Hi everyone!
I present to you the practical and simple guide special for dummies that will allow you to try and use the wonders of google treble project in our beloved Moto Z [Griffin has no official support but...] thanks to the great work of the highly recognized developer @erfanoabdi we can enjoy project treble in an easy way [*could apply user restrictions] in our griffin.
*First of all, this guide is designed for those who are curious and have a high degree of autonomy when they try to solve low level or common problems of the Android system. You dont need to be a developer but you must have experience in using and applying the following words: unlocked bootloader, ADB and Fastboot basic commands, Lineage OS, TWRP, Magisk , Back to Stock, Frustration, No "daily driver user" or maybe according to your needs, contribute to general knowledge, dont demand from me more than here is already here because I'm not a developer, I'm just a curious user who likes to try new things in his griffin and I have already given you more than 168 hours of trial and error with the only goal of making the process easier and more fun to you.
Now let's go to what interests us, do you have your bootloader unlocked?
If the answer is no, go here and do it or you can not continue
First we start with the files that we need to download:
Latest Lineage OS from here:
https://download.lineageos.org/griffin
[Thanks to Erfanoabdi]GSI image of your favorite flavor from here:
https://mirrors.lolinet.com/firmware/gsi/
Only type A not AB just A like ColorOS-Aonly-9-20190605-ErfanGSI.img.7z not ColorOS-AB-9-20190605-ErfanGSI.img.7z and decompress the .7z file to get the IMG file inside.
To decompress the .7z file
https://www.7-zip.org/download.html
If everything goes to hell [100% sure to happen at least once] Stock ROM and adb-fastboot-latest.rar from here:
https://forum.xda-developers.com/moto-z/development/stock-moto-z-8-0-firmware-t3805226
Thanks to @thuybang for the post and @erfanoabdi again for the needed files.
Official TWRP from here:
https://dl.twrp.me/griffin/twrp-3.3.1-0-griffin.img.html
Latest Stable Magisk from here:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Thanks to @topjohnwu
Magisk module "Device Spoofing Tool" from here:
https://forum.xda-developers.com/apps/magisk/qa-want-to-install-modules-magisk-v13-3-t3800435
Thanks to @Dreamer(3MF)
Device ID apk from here:
https://androidfilehost.com/?fid=673956719939830832
Latest Android System WebView APK from here:
https://www.apkmirror.com/apk/googl.../android-system-webview-76-0-3809-36-release/
Finally put this on favorites because you will need it for the final touch:
https://www.google.com/android/uncertified/
Only if you have all those files downloaded and placed in your PC in the folder that you want you can continue.
Now the easy way step by step if you are on Official Stock ROM:
1 - Reboot to Bootloader and flash twrp-oemasvendor-2.img you can use ADB and fastboot of the .rar adb-fastboot-latest.rar that you ¿downloaded? from the back to stock link
Use
Code:
fastboot flash recovery twrp-3.3.1-0-griffin.img.img
Hard-reboot to bootloader again, down two steps and select reboot to recovery.
2 - Already in TWRP do this:
2.1 - Wipe Data - if it gives you error go reboot and select reboot recovery and again wipe data it should have been erased without errors, back and
2.2 - Manually wipe caches, system, vendor, data, internal storage
2.3 - Do "Swipe to Factory Reset" probably not necessary but for me it works.
3 - Now connect your Griffin and copy the Lineage OS ROM downloaded [obviously still inside of TWRP]
3.1 Go to Install and select the copied Lineage ROM and then install
3.2 Finished the installation restart and skip all startup, now in the launcher screen shutdown your griffin
4 - Power on your griffin again in bootloader, two steps down and select reboot recovery again.
4.1 - Now in TWRP copy the GSI type A image that you downloaded [MIUI, ColorOS, OneUI, Pixel, Flyme OS, etc)
4.2 - Allready copied go to Install and select "Install Image"
4.3 - Now you see the .IMG file, select and then flash as "System" and go let finish, clear cache and restart to System.
5 - Be very patient, you will see the warning image for having your bootloader unlocked for 5 to 10 seconds [may vary] then you will see the start animation according to the GSI image that you will select before, again be very patient it can take 3 to 15 minutes to your griffin to start completely (MIUI 3-5 minutes, Pixel 3-5 minutes, OneUI 5-10 minutes, Flyme 15 to 20 minutes in my experience) If you see that the start animation reduces its brightness after a few minutes, it means that we are on the right track wait a little longer.
5.1 - Finally we start system we enter directly without previous configurations (configure wifi, google account, PIN, etc) just start screen now go to step 6, if not then go here:
If everything goes to hell [100% sure to happen at least once] Stock ROM and adb-fastboot-latest.rar from here:
https://forum.xda-developers.com/moto-z/development/stock-moto-z-8-0-firmware-t3805226
Thanks to @thuybang for the post and @erfanoabdi again for the needed files.
And start again
6 - Ok you are one of those who managed to install and start their GSI image and you dont have google services enabled and your griffin is not certified you probably have app errors that crash infinitely [if they are 1 or 3 - example the camera] manage to go to app administration in the ROM and cancel auto-start of that apps, instead if you have so many apps errors that dont let you move anything in the interface you need to go to TWRP and clean davlink cache and cache and reboot.
That's why this step is important
Code:
4.3 - Now you see the .IMG file, select and then flash as "System" and go let finish, [B][COLOR="Red"]clear cache and restart to System
[/COLOR][/B].
7 - Now Root your griffin with Magisk, you know how otherwise I dont know how you got here
8 - Already in system, install the "Device Spoofing Tool" magisk module and reboot to activate the module.
9 - Again already in system, install Device ID APK
9.1 - Open Device ID app and find your device’s GSF (Google Service Framework) Device-ID
9.2 In your PC go HERE and use your GSF to register and certify your griffin
10 - Now install Android System WebView APK
10.1 - Go to TWRP again and clean cache one more time and reboot to system
11 - Configure your google account and be happy
11.1 - Camera its a common fail, use Gcam or Snapdragon Camera instead of GSI stock camera app
12 - Enjoy your griffin :highfive:
Well that's all from me and remember if something goes wrong or it does not work you can always go here:
If everything goes to hell [100% sure to happen at least once] Stock ROM and adb-fastboot-latest.rar from here:
https://forum.xda-developers.com/mot...mware-t3805226
Thanks to @thuybang for the post and @erfanoabdi again for the needed files.
The 99.99999999 percent of all this, maybe more, it's thanks to @erfanoabdi If you want to thank someone, buy a coffee for him.
Screenshots (sorry just from MIUI with my emotion I forgot to save from the other GSI that I proble) I feel comfortable with MIUI and now it is my ROM-GSI of daily use in my griffin (I really love taking screenshot with my three fingers )
https://ibb.co/bmDkRrz
https://ibb.co/HX3mghC
https://ibb.co/10jGLNr
https://ibb.co/jz6njXm
https://ibb.co/vv1Nr2F
https://ibb.co/9Gr29nv
https://ibb.co/qsZ2pFD
https://ibb.co/948H110
https://ibb.co/42nXM72
https://ibb.co/Jd73QwC
https://ibb.co/vVs15Hq
https://ibb.co/MVfptZ5
https://ibb.co/SywLwrW
https://ibb.co/ZXvg0QG
https://ibb.co/z8DF8L1
https://ibb.co/bBv1wxW
https://ibb.co/09nBnHW
Finally dont be mad with my english, itis very bad and I use translator
Thanks for guide, very cool
Official TWRP is updated with treble support BTW
Nice ,thanx to your contributions.
whats the waiting time for the moto image? ive installed the moto image, and still waiting for the device to bootup. its been about 15 mins
---------- Post added at 07:46 PM ---------- Previous post was at 07:25 PM ----------
after installing the image, im stuck on this (device will boot in 5 seconds screen) Can i boot back into recovery, and re install the image? its been more than 30 mins on this screen
Pixel image is the only one I managed to boot, but couldn't get gsf id from it, and it constantly force closed (cache was cleaned) and couldn't make it work at all. Moto image just gives black screen, all other images couldn't even be installed (either error in twrp or something else.) I'll try miui image one of these days, but would really like to try to make pixel image work, but without gsf id it's impossible
EDIT: Changed twrp to twrp-oemasvendor-2.img version, and managed to boot miui (but after magisk it bootlooped) and to start booting moto GSI images (moto bootloops), and just tried to boot pixel images, will see later... but I think that the problem was that twrp uses cache as vendor partition, and deleting cache, well, deletes vendor partition (will need clarification from @erfanoabdi on this)...
Can we flash the GSI over other Custom ROMs like the OMNI instead of Lineage...?
anwesh said:
Can we flash the GSI over other Custom ROMs like the OMNI instead of Lineage...?
Click to expand...
Click to collapse
Nop, Omni does not have the type of partition needed
After following this guide, I am able to boot into system (only with Pixel or MIUI GSI), but SIM is not getting detected. Frequent app crashes are also observed. Cache and dalvik are being cleared before booting...
Do I still need to follow this How to make GSI...?
But LOS 16 seems to flash vendor image, isn't it...?
What am I missing...?
By the way, clearing vendor partition always gives me an error...
anwesh said:
After following this guide, I am able to boot into system (only with Pixel or MIUI GSI), but SIM is not getting detected. Frequent app crashes are also observed. Cache and dalvik are being cleared before booting...
Do I still need to follow this How to make GSI...?
But LOS 16 seems to flash vendor image, isn't it...?
What am I missing...?
By the way, clearing vendor partition always gives me an error...
Click to expand...
Click to collapse
Go to TWRP and make full wipe factory, that fix the problem
I've been hunting down and trying out some different gsi's. With the latest twrp + los16 installed I've had success with some from this list
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
AOSP 10 with gapps included
Msm xtended gapps included
Blissrom + gapps
Aosip + gapps
EvolutionX gapps included
DU13 + gapps (not on list but works)
If installing gsi's without gapps included, let it boot first then reboot TWRP and install gapps + magisk if you want root.
Available kernel ?
I cannot retrieve the GSF id, how can I fix this?
Flashed OneUI GSI but it's stuck on the boot logo
So on my Moto Z running LineageOS 17, I can't launch Netflix on it. Will Treble-ing my Moto Z fix that problem?
This also works on moto z force?
STANDARD DISCLAIMER: I am not responsible for any damages caused to your phone. Use this Guide at your own risk there is no warranty or guarantee.
How to Root the H910 and install the Lemon Drop Rom?
1. Disable real time scanning, on the windows virus scanner. Download all the files, save terminal emulator to your microsd card the other two save on your computer, unzip dirtysanta, install usb drivers if using windows. Root your H910 with this guide.
h910_root_pkg.zip "DirtySanta root package"
usb drivers for windows
Terminal Emulator for Android "f-droid Download APK at bottom of page"
2. [ROOT] HOWTO: AT&T H910 up to v20g (FULLY TESTED) Note: before you flash the KDZ to downgrade your firmware make a DUMP backup with LGUP all files. You don't need to DUMP system or cache. It will have your EFS.
3. On step3.bat wait for phone to reboot from fastboot mode, when you see the LG logo, pull the battery. Do a factory reset and that will load TWRP How to factory reset the Lgv20.
4. Then format data. Very important, you format data with the older version of twrp that is with dirtysanta.
5. Then power off phone.
Note: This next part is for the H910, you need to get your version of twrp for your model of Lgv20. Latest version of twrp link at the bottom of page
6. Download twrp for the H910 twrp-3.7.0_9-0-h910.img
7. With the phone powered off, hold the down volume button and plug in usb to computer and phone.
fastboot flash recovery twrp-3.7.0_9-0-h910.img
fastbboot reboot
take battery out
put back in
go into twrp by doing a factory reset. How to factory reset the Lgv20
8. Then you want to format data once more with the new version of twrp.
9. power off phone
10. Then go to: [Lemon Drop] A [Debloated] & [DeGooged] [Stock] [Oreo] [Rom] for the H910 & Most Lgv20 phones.
(archived)
Install Oreo on the H910 & debloat ALL lgv20 phones.
Any Lgv20 phone can debloat go to step 13. H910 phones start at step one.
If you are having issues downloading the rom you can try this download manager for Firefox.
Turbo Download Manager
1. Download the following files. And put them on the sdcard.
twrp-3.3.1-0-h910.img
H910_20g_Oreo_full_rooted.zip
h910oreomodem.img
H910_1.0-ezV2020.zip new kernel
adreno+5xx+-+v313+rev23+-+non-treble.zip new gpu drivers
Magisk-v19.0.zip (direct link to github)
MagiskManager-v7.1.1.apk (direct link to github)
2. Restart phone into recovery. (aka twrp)
3. Then install twrp-3.3.1-0-h910.img (The img file can be flashed with twrp you just need to select Install Image, select the file and choose recovery).
4. Reboot phone into Recovery
5. Click wipe then Swipe to factory reset
6. Install H910_20g_Oreo_full_rooted.zip
7. Then install h910oreomodem.img (The img file you can flash with twrp you just need to select Install Image, select the file and choose modem)
8. Then install twrp-3.3.1-0-h910.img (The img file can be flashed with twrp you just need to select Install Image, select the file and choose recovery).
9. Then install Magisk-v19.0.zip
10. Then install adreno+5xx+-+v313+rev23+-+non-treble.zip
11. Then install H910_1.0-ezV2020.zip then wipe dalvik cache
12. If you do not want to debloat Stock Oreo, then go to step 16. Otherwise to go step 14.
13. Any Lgv20 Reboot into twrp. Do steps 14, 15, 17, 18. Can debloat numbers 10 - 18
14. Click on Mount, make sure Mount system partition read-only is unchecked. Mount System. Then open up file manager under advanced.
15. If you want to debloat the H910 phone, these 18 lines can be safely deleted with the trwp file manager. Note these 17 lines should be removed before first boot H910.
01. "/system/priv-app/AMBS" bloatware at&t backup and sync messaging
02. "/system/priv-app/ATT_Lookout" bloatware att lookout
03."/system/priv-app/ATT_AppSelect" bloatware installs unwanted apps in background.
04. "/system/priv-app/ATT_DeviceHelp" bloatware
05. "/system/priv-app/ATT_IQI" bloatware
06."/system/priv-app/ATT_RemoteSupport" bloatware
07. "/system/priv-app/ATT_SNT" bloatware
08. "/system/priv-app/MetricService" bloatware
09. "/system/vendor/app/ATT_HotSpots" bloatware
10. "/system/priv-app/EdenService" bloatware
11. "/system/priv-app/LGDMSClient" OTA Updates
12. "/system/priv-app/LIAInformant" bloatware
13. "/system/app/LGATCMDService" OTA Updates
14. "/system/app/LGFOTA" OTA Updates
15. "/system/vendor/app/SecProtect" bloatware
16. "/system/vendor/bin/triton" It's an antivirus program, slows the phone down.
17. "/system/vendor/bin/tftp_server" Prevents phone from downloading any updates
18. "/system/priv-app/GCUV" Blotware some kind of LGE sign in portal, looks like it may cause a battery drain also.
16. Restart and run setup and update Magisk v23.0 confirmed working.
17. Disable MLT/LDB Use a root file manager
required folders:
/system/vendor/overlay/com.lge.mlt
/system/priv-app/LGLDB
open: "/mpt/enable" change "1" to "0"
change file permissions for "/mpt/enable" to 0444
reboot
18. done
Recommended twrp options for backup.
Boot
Recovery
System Image
data (excl. storage)
EFS
Fimrware
LAF/Download Mode
Optional packages to debloat H910 and ALL Lgv20 phones.
LG Messaging is required, to run the setup, first boot. Most other apps that are not on the list, you can just disable them in Oreo.
If for what ever reason you need to reinstall an app all you need to do is unzip the rom H910_20g_Oreo_full_rooted.zip and locate the "system" file and rename to "system.img" mount it on your computer and copy back the folder to the same location on the phone, reboot. Keep in mind this is the "/system" directory on the phone. File permissions 0644 for apk file.
Free root file manager no ads
[APP][2.2+] MiXplorer v6.x Released (fully-featured file manager)
ALL Lgv20 phones can debloat #07 - #32.
H910 phones can debloat #01 - #31.
These folders can safely be removed.
01. "/system/priv-app/ATT_DriveMode" ATT Drive Mode
02. "/system/priv-app/ATT_CallerNameID" ATT Caller Name ID
03. "/system/vendor/app/DirecTV_Remote" DIRECTTV Remote
04. "/system/vendor/app/DirecTV" DIRECTTV
05. "/system/vendor/app/ATT_UBER" Uber
06. "/system/priv-app/MyATT" My At&t app
07. "/system/app/EditorsSlidesStub" Google Slides
08. "/system/app/EditorsSheetsStub" Google Sheets
09. "/system/app/EditorsDocsStub" Google Docs
10. "/system/app/Music2" Google Play Music
11. "/system/app/Videos" Google Play Movies & TV
12. "/system/app/Drive" Google Drive
13. "/system/app/YouTube" YouTube
14. "/system/app/Maps" Google Maps
15. "/system/app/LatinImeGoogle" Google keyboard
16. "/system/app/Photos" Google Photos
17. "/system/vendor/app/facebook" Facebook
18. "/system/priv-app/facebook-installer" Facebook App Installer
19. "/system/vendor/app/facebook-appmanager" Facebook App Manager
20. "/system/app/Hangouts" Google Hangouts
21. "/system/priv-app/LGEmail" LG Email
22. "/system/app/GoogleInApps" Google In Apps
23. "/system/vendor/bin/xtra-daemon" info
........"/system/vendor/etc/xtra_root_cert.pem"
........"/system/vendor/etc/cacert_location.pem"
24. "/system/app/SDEncryptionHelper" SD Encryption Helper, I don't use SD Encryption.
25. "/system/app/WfdService"
......"/system/bin/wfdservice"
......."/system/etc/init/wfdservice.rc"
......."/system/app/atfwd"
......."/system/vendor/bin/ATFWD-daemon"
........"/system/vendor/etc/init/[email protected]"
.........'/system/vendor/bin/wifidisplayhalservice"
Screen Share may not work, if removed. Been reports of people using this app to hack into the phone, and view everything on your screen via wifi or LTE data reddit
26. "/system/vendor/app/SVIService" This app messes with the auto brightness. With it removed, you can change your brightness level with auto brightness enabled. If it's to bright, turn down the brightness and the phone will remember that setting, next time in the same light level.
27. "/system/etc/init/atrace.rc"
This is for debugging the kernel. Kernel trace logs are stored at "/data/anr/" you can delete them if you want. This slows boot time down and takes up memory. The phone makes a log about the size of 700MB each boot.
28. "/system/priv-app/LGBackup" Slows phone down use twrp to backup up
29. "/system/priv-app/BackupRestoreConfirmation" Slows phone down use twrp to backup up
30. "/system/vendor/overlay/com.lge.sizechangable.weather" Uses cpu cycles
31. "/system/priv-app/LGWeather" Uses cpu cycles
32. "/system/priv-app/Lookout T-Mobile Lookout
Credits, A Special Thank You
@ezzony - for the ezV2020 kernel. XDA
@askermk2000 - for the MK2000 kernel. XDA
@me2151 for DirtySanta. XDA
@clsA for the H910 v20g rom. XDA
@runningnak3d for a great H910 root guide. XDA
@darkknight200 for the H910 Oreo modem drivers. Download Link
at hardreset.info on how to factory reset the Lgv20
at TeamWin TWRP, for TWRP.
at the people over at Magisk, for an Opensource Root.
at XDA, for a Great Platform.
And everyone else that I may have missed that helped with the Lgv20.
Thank you all, for helping make the Lgv20 phone one of the best rooted phones of all time.
how fast is the performance like pubg
DesrtSailor said:
how fast is the performance like pubg
Click to expand...
Click to collapse
I have never played pubg so I cant tell you, I can tell you the UI is faster and I do have one game on my phone Reckless Racing 3 and it seems to play a little faster and does not skip frames that I can see. But keep in mind that the Lgv20 is not the fastest phone around it's a 2016 model. But my guide will help you get the fastest experience out of your phone.
did u run geekbench scores or antutu
how is compared to nougat
DesrtSailor said:
did u run geekbench scores or antutu
how is compared to nougat
Click to expand...
Click to collapse
Yeah I got some benchmarks. I should have uploaded them but I was still working on my guide. Sorry don't have Nougat.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My phone has the H91020I update, could I use this method to root? Or I am out of luck.
HAMSATHI said:
My phone has the H91020I update, could I use this method to root? Or I am out of luck.
Click to expand...
Click to collapse
That's a good question, unfortunately I don't have the answer, please ask in this forum.
[ROOT] HOWTO: AT&T H910 up to v20g (FULLY TESTED)
I am so glad I waited, this guide sounds like exactly what I am looking for! I'll be attempting this tonight on my backup AT&T V20 variant. Thank you
Dream Reality Syndrome said:
I am so glad I waited, this guide sounds like exactly what I am looking for! I'll be attempting this tonight on my backup AT&T V20 variant. Thank you
Click to expand...
Click to collapse
Your welcome.
Darnrain1 said:
Your welcome.
Click to expand...
Click to collapse
I attempted to download the Oreo image several times but it seems the mirror on AFH kept dropping out. Is there another host for that particular image? Should I try to find some other Oreo image?
Dream Reality Syndrome said:
I attempted to download the Oreo image several times but it seems the mirror on AFH kept dropping out. Is there another host for that particular image? Should I try to find some other Oreo image?
Click to expand...
Click to collapse
I have had that happen before with AFH. I used firefox and just pressed retry a lot. Let me think about this maybe I can just upload the files to xda.
Darnrain1 said:
I have had that happen before with AFH. I used firefox and just pressed retry a lot. Let me think about this maybe I can just upload the files to xda.
Click to expand...
Click to collapse
okay I am uploading the files to xda but my upload speed is not that fast. I think this will take an one hr or two. As for package manager and Mixplorer you still should download the apps from the developers.
Dream Reality Syndrome said:
I attempted to download the Oreo image several times but it seems the mirror on AFH kept dropping out. Is there another host for that particular image? Should I try to find some other Oreo image?
Click to expand...
Click to collapse
xda does not allow me to upload the 2.5 gb file. I guess it's to large.
Try firefox and if the download stops press retry and it should continue where it left off. As for using another version you can try but I recommend H910 V20g it seems to be stable.
Darnrain1 said:
xda does not allow me to upload the 2.5 gb file. I guess it's to large.
Try firefox and if the download stops press retry and it should continue where it left off. As for using another version you can try but I recommend H910 V20g it seems to be stable.
Click to expand...
Click to collapse
I will try your method tonight. Thank you for trying!
Dream Reality Syndrome said:
I will try your method tonight. Thank you for trying!
Click to expand...
Click to collapse
Try this downloading extension for Firefox. I was having issues also but this worked for me.
Multithreaded Download Manager by jingyu9575
T
Darnrain1 said:
Try this downloading extension for Firefox. I was having issues also but this worked for me.
Multithreaded Download Manager by jingyu9575
Click to expand...
Click to collapse
This worked out perfectly, thank you!!
My H910 V20 has been up for 18 + days can counting. Very stable install of Oreo.
Darnrain1 said:
STANDARD DISCLAIMER: I am not responsible for any damages caused to your phone. Use this guide at your own risk there is no warranty or guarantee.
This guide will walk you through step by step on how to install Oreo on the H910.
I assume that your phone is already rooted. If not, click on this link below.
[ROOT] HOWTO: AT&T H910 up to v20g (FULLY TESTED)
You may be wondering why I used v20g version when there is an v20h version out. The v20g version is very stable. And most of the updates from g to h are most likely just carrier updates not OS updates. I went with version 19.0 of Magisk because it's very stable, newer versions may prevent your phone from booting.
How to install Oreo on the H910 with Root
Make sure you have a backup of all your important files from the internal storage before you start. We will be reinstalling the android operating system.
Note: If you have trouble downloading the files you can try this Firefox downloading extension.
Multithreaded Download Manager by jingyu9575
1. Download the following files. And put them on the sdcard. You can use MIXplorer or another root file manager of your choice you just need to be able to install the file manager from the sdcard (no internet).
recovery-twrp-h910-2018-10-18.img
H910_20g_Oreo_full_rooted.zip
h910oreomodem.img
MK2000 kernel 2.0
Magisk Uninstaller
Magisk 19.0
Magisk Manager 7.1.0
[APP][2.2+] MiXplorer v6.x Released (fully-featured file manager)
Package Manager
2. Restart phone into recovery. (aka twrp)
3. Install recovery-twrp-h910-2018-10-18.img (The img file can be flashed with twrp you just need to select Install Image, select the file and choose recovery).
4. Reboot phone into Recovery.
5. Do a format, then do a standard wipe.
6. Install H910_20g_Oreo_full_rooted.zip
7. Then install h910oreomodem.img (The img file you can flash with twrp you just need to select Install Image, select the file and choose modem) Then select Install Zip.
8. Then install H910_v2.0-mk2000.zip
9. Then wipe dalvik cache
10. Then install Magisk-v19.0.zip
11. Then reinstall recovery-twrp-h910-2018-10-18.img (The img file can be flashed with twrp you just need to select Install Image, select the file and choose recovery).
12.. Reboot phone into System.
13. Then after the phone boots up into the setup screen click next and disable cell and wifi data. Internet need's to be off for this whole process.
14. Click next it will ask you to enable but just skip everything.
15. When you get to home screen, put the phone in airplane mode.
16. Open the LG file manager and install MiXplorer from the sdcard and give it root access. (Or use any root file manager you like, as long as you can install the file manager from the sdcard offline.)
17. Open your root file manager go to (root) /system/priv-app/
18. I deleted some folders, this will make your phone run faster. (Bloatware)
ATT_DeviceHelp
ATT_IQI
ATT_Lookout
ATT_CallerNameID
ATT_AppSelect
ATT_RemoteSupport
ATT_SNT
19. Reboot your phone but stay in airplane mode for now.
20. Install com.smartpack.packagemanager_45.apk (aka package manager) from the sdcard.
21. Open Package Manager give it root access, go to system and do a search for the following updates and Uninstall them. (Updates will break your phone because it's rooted.)
com.lge.android.atservice
com.lge.lgdmsclient
com.lge.lgfota.permission
22. Open Magisk go into settings and disable, Check for Updates. I would recommend just staying with Magisk 19.0 it's stable and works well with Oreo.
23. Congratulations on completing the installation process. You can now enable cell data and wifi.
Note: Don't uninstall the built in weather app, it will cause second screen to crash and make your phone unusable. I would recommend using package manager to disable the apps you don't want, that way you can always re-enable them. Also the Amazon app takes up a lot of battery power. The Amazon app is is not well optimized for android at the time of writing this guide.
There is a bug in the latest version of chrome and web view that makes the screen flicker on some apps. To fix this you need to disable chrome and enable chrome and check do not auto update in the play store, and don't update chrome. I use the Kiwi browser it's based off of chromium and you can install chrome extensions.
I have found a fix for the flickering you have to install the updated graphics driver. This driver is for oreo only lgv20, after you flash in twrp you must wipe dalvik cache.
[10/27][Adreno][OREO][Vulkan]Driver for Snapdragon 820/1[V313 REV23 | V330 REV3]
To fix the image retention install this shell script.
LGv20 fix image retention, aka screen burn in. shell script (root only)
Apps & Tweaks. All apps & tweaks are free to use or open source.
Thermal Throttling Fix LGv20 (Stock root only) (fix thermal throttling for gaming)
[APP][2.2+] MiXplorer v6.x Released (fully-featured file manager) (Root file manager, free to use & no ads, there is a paid version on google play store if you want to support the dev.)
[GUIDE] Best Battery Life Possible (Disable LDB & Logging will increase speed of phone) This guide is for the LG G6 but will work with lgv20 phones, NOTE do not change the screen resolution go to the line that says Disabling LDB.
Package Manager (system app uninstaller)
Clock (Deskclock is a fork of the AOSP clock, so it offers all its functions) Good alarm clock.
LGv20 fix image retention, aka screen burn in. shell script (root only) (shell script to fix the screen burn in aka image retention on lgv20.)
Disable find my device administrator account. (Shell script to disable device administrator account.)
Disable lock screen service administrator account. (Shell script to disable lock screen service administrator account.)
Swap memory disabler (Disable zram on lgv20 Magisk Module.)
Sleep Timer (Sleep Timer helps you fall asleep while listening to music or podcasts. When the timer stops, audio playback is gradually lowered then paused.)
[APP] CpuFloat [March27] Floating cpu, gpu, temperatures, deep sleep, network monitor (Shows cpu info and float's on the screen.)
Simple Gallery Pro (Great gallery app for all your photos.)
Build Prop Tweaks
(just copy and past every thing below in /system/build.prop file at the very bottom save and reboot. With this tweak I recommend you have zram enabled.)
# Tweaks
# better multitasking
ro.vendor.qti.sys.fw.bservice_enable=true
ro.vendor.qti.sys.fw.bservice_age=5000
ro.vendor.qti.sys.fw.bservice_limit=5
# extend battery life
wifi.supplicant_scan_interval=180
Issues I had with my lgv20
I had some issues with a magisk module called zram_manager, The apps I had open were acting funny and I had to close them and open them back up again. I don't recommend that magisk module for the lgv20. I just use the stock zram.
I was having a odd issue with the files on my sd card. My file extensions were getting renamed to .0 such as song.mp3.0 so I could not play my music. It was VLC or vanilla music player. I uninstalled both and so far the issue has not returned. For now I am just using MiXplorer to play my music and watch videos on my phone. Update so far it's been a month and no issues with the renaming of my songs.
Click to expand...
Click to collapse
Works 99%, except no data (T-Mo, AT&T H910) - modem file? Anyone else found a solution to no data? (Calls OK, just no network data)
TomJ2 said:
Works 99%, except no data (T-Mo, AT&T H910) - modem file? Anyone else found a solution to no data? (Calls OK, just no network data)
Click to expand...
Click to collapse
I have AT&T, 4G LTE data works. But if you using an AT&T phone on T-Mobile then that may be why the data is not working.
This is what I found on the internet.
Will an unlocked H910 AT&T model support T-Mobile wi-fi calling?
MORE ATT CRAP TO GET RID OF
In order to completely disable fota. i had to get rid of the following (i deleted anything in the system folder with fota in the file name):
/system/apps/lgfota
/system/etc/fota
/system/etc/terms/fota
/system/lib/libfotajni.so
/system/lib64/libfotajni.so
/system/etc/permissions/com.lge.fota.xml
There's also extra att bloatware to get rid of:
/system/app/vvm_att
/system/vendor/app/facebook-appmanager
/system/vendor/app/facebook
/system/vendor/app/directv_remote
/system/vendor/app/directv
/system/vendor/app/att_uber
The only att app you want to leave on the phone is /system/vendor/app/att_hotspots; wifi calling will not work without it.
Now, get ready for some weird stuff....
GOOGLE CRAP TO KEEP
These folders are split up among /system/app and /system/priv-app
googlepackageinstaller (keep to be able to install apk's)
googleextshared (phone boot loops without this)
googleextservices (phone boot loops without this)
webviewgoogle (aurora store at this moment seems to only work with the webview that came with the stock rom and it's browser and will work with no others)
chrome (aurora store at this moment seems to only work with the webview that came with the stock rom and it's browser and will work with no others)
Here's where it gets weirder, but if i figured it out for everyone, it wasn't easy...
GOOGLE CRAP TO GET RID OF AND KEEP WIFI CALLING FUNCTIONAL
This next part is specifically for degoogling and maintaining wifi calling without having google try to update apps the moment you get connected to wifi. I did this in two stages...
PART 1
Get rid of the following:
These folders are split up among /system/app and /system/priv-app
youtube
editors slides
editors sheets
editors docs
photos
maps
hangouts
phonesky
music
videos
google pay
gmail
latininlmegoogle
drive
calculator
velvet
driveactivator
tag
GoogleBackupTransport
GoogleContactsSyncAdapter
googlecalendarsyncadapter
google tts
hotwordenrollment (all hotword enrollment folders)
google in apps
talkback
GoogleFeedback
GooglePartnerSetup
GoogleOneTimeInitializer
SetupWizard
PART 2
After part 1 is complete
A. Boot into android.
B. Connect to wifi.
C. Activate wifi calling.
D. Verify wifi calling works (call your phone, have another phone call your phone, either or for that test).
E. Go into android settings and disable google play services and google framework, restart phone, then confirm wifi calling still works.
F. Reboot phone into twrp, remove gmscore and googleservicesframework (again, you'll find these folders among system/app and /system/priv-app).
G. Congratulations, you've degoogled as much as possible without clawing at the walls wondering why wifi calling isn't working after you degoogled.
MICROG?
Microg works very well on this phone. Microg is pretty much fake google services so you can still run normal apps from the play store.
1. Reboot into twrp and flash nanodroid patcher patckage. This patches the phone to allow signature spoofing; a requirement of microg.
2. Flash nanodroid microg package.
3. Reboot into android.
4. Open microg settings.
5. Go into "self-check" inside of microg settings, allow everything and check off all the boxes in there.
6. Get out of self-check and go into "google device registration" and turn that on.
7. Update to the latest version of aurora store since the nanodroid package include an old one.
8. Go into aurora store after you updated it, allow all it requires, keep it with the "session installer".
9. Once aurora store initial setup is complete, go into "blacklist manager" and check off all the boxes in there.
A. Aurora store will mistake microg as outdated and want to wipe it out with a google play services installation.
B. You don't want aurora store upgrading any of the android operating system files on your phone.
C. Doing this ensures that any app you install from aurora store afterward won't be blacklisted, and aurora store gets relegated for apps you installed and updates for those apps.
10. Consider installing fdroid so you can keep aurora store regularly updated with the newest version.
11. Congratulations, you've degoogled as much as possible without losing wifi calling and still run apps from the play store.
SHORTER BOOT TIME AND SHUTDOWN TIME
Delete the following to shave seconds off boot and shutdown time (your phone will have no more start up noise, turn on 5 seconds faster, and have no more shutdown animation since att's attempt at visualizing a shutdown was very odd).
/system/media/bootanimation.zip
/system/media/shutdownanimation.zip
You can actually get rid of the media folder, but do that if you don't want user interface sounds, or your typical alarm noises (and that's how you don't wake up to a silent alarm the next day if you delete this folder).
[GUIDE/TUTORIAL/HOWTO] Samsung Galaxy S7 Edge Stock to Android 13
[GUIDE/TUTORIAL/HOWTO] Samsung Galaxy S7 Edge (hero2lte Exynos SOC) Stock to Android 13 / LineageOS 20
Supported models
International & Canada:
- SM-G935F
- SM-G935FD
- SM-G935X
- SM-G935W8
Korea:
- SM-G935S
- SM-G935K
- SM-G935L
This detailed step-by-step guide helps you transform your Samsung Galaxy S7 Edge hero2lte to a powerful one with Android 13.
Make sure your phone is hero2lte/Exynos SOC before going further: in Android, go to Settings > About phone > Check Model number is listed above.
If not, quit this tutorial.
### READ THOSE WARNING COMMENTS
CHANGELOG
v5. Back to TWRP 3.6 (3.7 oversize)
v4. Android 13, TWRP 3.7
v3. BitGApps v1, Magisk 25.2
v2. Update TWRP, add adb to change screen definition, update download link
v1. Initial release for Android 12
1) DOWNLOAD
- djibe Galaxy S7 hero2lte pack: https://bit.ly/djibe-galaxys7edge-pack
(contains Samsung tweaked Odin 3.13.1 + Samsung USB drivers + TWRP 3.6.2_9-0 official recovery + Magisk Root + adb.exe). Unzip files.
+ ROM Unofficial LineageOS 20: https://forum.xda-developers.com/t/...ofing-ota-updates-for-s7-edge-exynos.4484511/
Download latest build: https://ivanmeler.github.io/devices/hero2lte.html
+ BiTGApps Package ARM64 13: https://github.com/BiTGApps/BiTGApps-Release/releases
OR NikGApps T Basic: https://sourceforge.net/projects/nikgapps/files/Canary-Releases/NikGapps-T/
OR MindTheGApps 13 ARM64: http://downloads.codefi.re/jdcteam/javelinanddart/gapps
+ Charge phone to 100%
2) BACKUP DATA
Install Samsung USB drivers (you unzipped earlier).
Then plug phone to PC in File transfer mode.
Collect all .jpg or .mp4
Use Google built-in cloud to backup apps like SMS Backup & Restore to backup texts, contacts, etc.
Backup your WhatsApp messages in Google Drive.
Everything else: podcasts, Authenticators, TODOs etc...
Then copy the backup on your PC.
Make sure you have latest official updates for your phone:
Connect to Wifi and go to Settings > About device > Software update > Update now
### BACKUP NOW, you will lose everything.
3) FLASH TWRP 3.7 RECOVERY
Go to Settings > About phone> Software information.
Tap 7 times on Build number item to unlock Developer options.
Go to Settings > Developer options, switch OEM unlock ON and Confirm.
Shutdown phone.
Boot in Download Mode: hold Home + Power + Volume- until you see blue-green Warning screen and release buttons.
Confirm access to Download mode by pressing Volume+.
Phone now displays "Downloading..., Do not turn off target".
Connect phone in USB, wait for drivers installation.
Then launch Odin.exe (included in my archive) and wait for Odin indicator ID:COM to become blue.
In options: Verify re-partition and Auto Reboot are NOT ticked while F. Reset Time is ticked.
In AP > select twrp-3.6.2_9-0-hero2lte.img.tar
### Same recovery for Korean models (G930S/K/L variants)
### Warranty will be Void after next click ###
Click Start.
Wait until flash Success message appears.
Unplug phone.
Restart phone to recovery :
- hold Power + Home + Volume- until phone screen becomes black...
- and immediatly switch from Volume- to Volume+ (still holding Power + Home) and hold until Samsung's logo is displayed to land in TWRP recovery.
### If Android launches, hold 3 buttons until phone restarts and Samsung logo appears.
4) BACKUP IMEI PARTITION AND SYSTEM (Nandroid backup)
(Boot in Recovery Mode: Hold Home + Power + Volume+ until you see Samsung's logo then release and wait a few seconds for TWRP recovery to boot)
Recovery asks for Keep System Read Only ? > Swipe to Allow Modifications.
Go to Wipe > Format Data.
Type: yes and confirm with bottom right check icon.
Encryption is removed. You can now access partitions.
### If you miss this step you won't have access to any partition.
Back to home menu > Backup.
You can now select the partitions you want to save.
Select at least EFS partition to backup your IMEI. If a flash fails and partition is damaged you will still be able to restore this partition and use the phone.
If IMEI is lost during a flash, phone won't be able to reach cellphone networks.
I prefer to backup Boot, System, Baseband and EFS partitions. In case of problem, you will have your phone in its original state.
Swipe to Backup and wait during process.
Go to Home screen and continue with next chapter.
Save backup: still under TWRP recovery, connect phone to PC.
Go to Mount menu and check Data partition is checked and MTB button is on "Disable MTP" state.
From Windows explorer, access phones memory and copy-paste the TWRP folder (located in root folder, beside DCIM and Music folders) somewhere safe on your computer.
5) FORMAT PARTITIONS
### Make sure you copied TWRP backup from internal memory to somewhere safe.
Go to Wipe > Advanced wipe,
select Dalvik, Cache, System, Data, Internal Storage (if you really made a backup at step 2), then Swipe to Wipe.
Back to TWRP home screen, go to Reboot > Recovery and swipe to reboot.
On next launch, check the checkbox to remember choice and swipe to allow modifications.
6) FLASH ROM, (MAGISK ROOT) AND GAPPS
Back to TWRP main menu, go to Mount menu again to connect phone to PC again.
Connect phone to PC and use Windows explorer to copy files on phone's internal memory.
Copy TWRP folder from your phone to somewhere safe on PC.
This backup can restore your phone to its original Samsung state.
Copy files of ROM + BitGApps + Magisk on phone.
Go back to TWRP Home menu. Then tap on Install > choose lineage*.zip,
Optional for root: Add More zips > Magisk*.zip
then Swipe to confirm Flash.
Wait for operation to end.
Go to Reboot > Recovery and swipe to reboot.
After restart, go to Install, select bitgapps*.zip and swipe to flash.
Then tap Wipe cache/dalvik, swipe to confirm,
then Reboot System and on Install TWRP App? menu, tap on button Do Not Install
Wait for the phone to boot during 5 minutes.
7) ROOT ACCESS
Configure Android as you like.
Don't try to set fingerprints at first setup. It will crash.
No need for extra work to be root.
Magisk launches with Android.
Superuser permissions can be managed from Magisk Manager app.
8) TWEAKS
- Calibrate battery: https://www.ifixit.com/Wiki/Battery_Calibration
- Set dark Mode to improve battery by 30%
Settings > Display > Dark theme.
- For better battery, remove Always on display
Settings > Display > Lock screen > Ambient display
- Activate Developer options
Go to Settings > About.
At bottom, tap 7 times on Build number. You activated Developer options.
Go to Settings > System > Advanced > Developer options.
- Change screen definition for low GPU/CPU usage: from 1440x2560 to 1080x1920
You need developer options to enable USB debugging.
Open a terminal where adb.exe from my pack is located.
Plug phone and Authorize USB debugging.
Then type:
Code:
adb shell wm size 1080x1920 && adb shell wm density 400
// Defaults 1440x2560 and 504
- Screen sensitivity is too low ?
Try to recalibrate screen sensitivity with https://play.google.com/store/apps/details?id=touchcalibration.favoritappindia&hl=en&gl=US
Enjoy,
djibe
Thanks: @Ivan_Meler, LineageOS team, TWRP team, TopJohnWu
---------------------------------------
Coming from another ROM
- Backup
- Recovery: Wipe Cache, Dalvik cache, System and Format Data > yes
- Reboot recovery
- Flash rom
- Reboot recovery
- Flash BitGApps
Enjoy
Force Samsung Galaxy S7 restart
Hold Power + Volume down for 10-20 seconds
Thanks for the detailed instructions.
Please fix two minor typos: In the Odin instructions, the files should be hero2lte* not herolte*.
Re Magisk: 24.0, I suppose, should be used / upgraded to. (I've run into issues with 24.2 on another platform.)
steve8x8 said:
Thanks for the detailed instructions.
Please fix two minor typos: In the Odin instructions, the files should be hero2lte* not herolte*.
Re Magisk: 24.0, I suppose, should be used / upgraded to. (I've run into issues with 24.2 on another platform.)
Click to expand...
Click to collapse
Hi, you are correct and I'll fix glitch.
For Magisk, as you report bugs, I'll wait to move to 24.x. You can create an Issue here: https://github.com/topjohnwu/Magisk/issues
Thanks for sharing
I have a problemi instaled twrp format data and and instal rom after configuration rom when i rebooting to twrp data is encrypted. why ?
zulwik said:
I have a problemi instaled twrp format data and and instal rom after configuration rom when i rebooting to twrp data is encrypted. why ?
Click to expand...
Click to collapse
Hi, did you Format Data then Advanced Wipe > Format Cache, System ?
Then
Reboot to Recovery
Flash ROM
Reboot to recovery
Flash BitGapps
Reboot
I solved problem.
I installed older version TWRP with Odin and new version
hey @djibe89 & other XDA folks, thanks for these steps.
I have a SMG935W8 and currently borked on the BiTGApps step. All proceeded smoothly until there and now I'm seeing an error on TWRP and I'm not really sure how to resolve it.
It's complaining that the install config is not found and that it's an unsupported Android SDK version, which doesn't seem quite right.
Any tips would be highly appreciated
Judging from my deep dive, the current LineageOS 19.1 builds are SDK 32, and the BiTGapps builds only support up to 31... Definitely looking for tips, still.
Going to try this post's GApps
Hi, for now, stick to latest LOS 19 build: https://github.com/ivanmeler/ota_provider/releases/tag/herolte_lineage-19.0_1646935359, not 19.1
Or could you try NikGapps and tell us?
Thanks @djibe89 ! I went with NikGapps and that was a win.
It might be good to edit the top post to say 19.0 or have the NikGapps linked in it, for future readers.
Phone's working great. I appreciate it!
Bujiraso said:
Thanks @djibe89 ! I went with NikGapps and that was a win.
It might be good to edit the top post to say 19.0 or have the NikGapps linked in it, for future readers.
Phone's working great. I appreciate it!
Click to expand...
Click to collapse
Hi, I'll update it.
I hoped a newer BitGapps update would be released by now.
Enjoy, this phone is awesome
Hey again!
Been daily driving this for a bit and here's a laundry list of the issues I see, in no order at all.
I'm not sure if they're Lineage issues or artifacts of being an "unsupported" Lineage build.
1. The screen just stays on despite the power save settings (I've tried 15s, 30s, you name it) if I'm on the home screen. Trebuchet, is it?
It's like it has some keep alive function a la YouTube. It's not 100% but it seems far more than 50% of the time that I have to manually lock the device. Anyone know if I've just configured something wrong or if this is how the launcher is supposed to work?
2. Phone services will not stop demanding my location, no matter what I configure. It's every few minutes and it's creeping me out a ton. Why is it so nosey?
3. The call audio quality is still barely usable. While I *can* have intelligible business conversations when required, they suffer the quality noticeably and are terribly robotic and tinny. For personal calls, I tried to play it off once but immediately was laughed out of the call: they asked before even a "how are you" could pass if we could switch to VoIP since it was so comically bad. After some kind tips from Ivan I tried mucking with the mixer levels to no avail. They did seem a bit "low" compared to the 18.1/19.0 values, so I pumped them in a couple places (NB volume from 22 to 32, call default volume on 917 from 98 to 164 -- I have no clue what any of these mean). It might be louder now? It's not worth an A/B test to confirm what should be the expectation, but my point is that it didn't fix the robotic, tinny quality.
4. Banking app complains of the device being rooted, but it isn't. "Great." I hear the latest Zygisk might fix? I haven't tried yet.
Now, I'm still excited to be on 12L! I'm trying to buff my ability to dev on this ROM and fix up some of these issues, as I really don't think this phone needs to be replaced yet, but being stuck on stock Oreo isn't working either, so I say let's hack this thing till it's stable as stock!
Hi @Bujiraso , thanks for sharing.
Didn't use it on a daily basis
Have you tried another launcher ?
I think bank apps detect custom ROM, nothing can be done. Hope I'm wrong. Some genius of signature spoofing can pass this I believe. But I'm not.
djibe89 said:
- To tweak overclocking and more, use SmartPack-Kernel Manager
SmartPack-Kernel Manager - Apps on Google Play
The ultimate tool to manage your kernel
play.google.com
Enjoy,
djibe
Click to expand...
Click to collapse
We're sorry, the requested URL was not found on this server. New Link please.
SERGE4NT said:
We're sorry, the requested URL was not found on this server. New Link please.
Click to expand...
Click to collapse
Hi, you can try https://play.google.com/store/apps/details?id=com.performancetweaker.app or https://f-droid.org/repo/com.smartpack.kernelmanager_174.apk
hi, is it possible for the model number SM-G9350
Klein44 said:
hi, is it possible for the model number SM-G9350
Click to expand...
Click to collapse
Hi, sadly no.
9350 and 9300 have Snapdragon SOCs, not Exynos.
Only Android 8 ROMs: https://forum.xda-developers.com/f/samsung-galaxy-s7-edge-snapdragon-roms-kernels.5975/
Oh, ok. And is there any good custom rom for the SM-G9350 model?
Klein44 said:
Oh, ok. And is there any good custom rom for the SM-G9350 model?
Click to expand...
Click to collapse
Like you see here: https://forum.xda-developers.com/f/samsung-galaxy-s7-edge-snapdragon-roms-kernels.5975/
No.
This happens with Qualcomm proprietary SOCs