Lineage 17.1 *UNOFFICIAL* for FIH (SAT/SS2/HH1/HH6/HD1/DRG)

Search This thread

xdaillum

Senior Member
Feb 2, 2012
116
19
Well first off, how can u expect to get a good result by flashing thru a google drive link :confused: and which link by the way

Sorry to clarify, I obtained the files from the Google Drive link. It's surely not possible to flash from a Google Drive link lol

I'm referring to the link in the OP under the red text, "Downloading", "GDrive folder". It links to this.

Is it still necessary to remind flashing is not harmless :

Whatever, u can try this:
Unzip localy the latest firmware.
Try to to enter in the download mode by connecting usb and press power+vol down
Flash boot.img with fastboot.

If u cannot get access to download mode your last chance is emergency mode or 9008 one. Check in the sharp s2 thread how to reach it. That will be painful as opening the phone is required likely :(

ÉDIT: after checking myself, I notice I cannot accès download mode with bouton combo anymore. That’s really scary bécots fastboot is a bit the last backup in case of problems

Yes I know it's not harmless. I'm not a pro by any means (obviously LOL) but not a total noob though so I was somewhat confident lol.

Also I wanted to come back and update that I did actually manage to eventually access what looked like recovery mode. I have attached 2 photos of what I saw on the screen. One shows the top of the screen, and the other shows the bottom. This looks much more promising than what I was seeing previously!

Thanks for your help/advice though, but I think given I can access this mode, the chance of recovery should be higher.

Can someone advise what steps I should take from this screen? I would suspect I would need to "reboot to recovery" and try go from there. I will try it later. Would like to ask though, as per my post above, what files am I supposed to be downloading exactly and how do I flash "boot, system, vendor"? Is what I did correct?

Thanks in advance.
 

Attachments

  • IMG_20200115_010623.jpg
    IMG_20200115_010623.jpg
    133.6 KB · Views: 189
  • IMG_20200115_010629.jpg
    IMG_20200115_010629.jpg
    105.6 KB · Views: 189

Psyl0w

Senior Member
Aug 21, 2018
56
21
Ok fine. Yes you definitely increase your chances of recover proper os with this.
I’m still very surprised by the stuff display on your screenshots. I know there is a certain connection between our sharp and Nokia but the fact you have a recovery with Nokia dragon is surprising. Just for curiosity what is your firmware?
I’m not a super pro but I would select reboot in bootloader to work with fastboot and type the first commande:
Fastboot device to check connection is ok
Then fastboot getvar all to know on which slot is the device.
Then you can flash or just boot a boot image with twrp from fastboot.
Good luck
 
  • Like
Reactions: xdaillum

heineken78

Senior Member
Mar 3, 2009
2,556
1,787
Kiev
www.mediafire.com
Ok fine. Yes you definitely increase your chances of recover proper os with this.
I’m still very surprised by the stuff display on your screenshots. I know there is a certain connection between our sharp and Nokia but the fact you have a recovery with Nokia dragon is surprising. Just for curiosity what is your firmware?
I’m not a super pro but I would select reboot in bootloader to work with fastboot and type the first commande:
Fastboot device to check connection is ok
Then fastboot getvar all to know on which slot is the device.
Then you can flash or just boot a boot image with twrp from fastboot.
Good luck

Nokia 4050 firmware was taken to pass Google certification, also propertary blobs are taken from.
Puur LOS boot looks like that.
He installed old LOS17.0 daily version, that's don't include TWRP boot.
 
  • Like
Reactions: xdaillum and Psyl0w

xdaillum

Senior Member
Feb 2, 2012
116
19
Ok fine. Yes you definitely increase your chances of recover proper os with this.
I’m still very surprised by the stuff display on your screenshots. I know there is a certain connection between our sharp and Nokia but the fact you have a recovery with Nokia dragon is surprising. Just for curiosity what is your firmware?
I’m not a super pro but I would select reboot in bootloader to work with fastboot and type the first commande:
Fastboot device to check connection is ok
Then fastboot getvar all to know on which slot is the device.
Then you can flash or just boot a boot image with twrp from fastboot.
Good luck

I don't know what firmware I'm on...
I have got around to playing with it yet. Will play with it shortly.

Nokia 4050 firmware was taken to pass Google certification, also propertary blobs are taken from.
Puur LOS boot looks like that.
He installed old LOS17.0 daily version, that's don't include TWRP boot.

Hey Heineken. Firstly, thank you for your effort/hard work with this!

What do you mean I installed LOS17.0 daily version? I was going to flash from the file called "LOS17.0-20200105-UNOFFICIAL-S2-S3.zip", but this error I encountered was after trying to flash "boot.img" (the one located in root folder of the linked GDrive folder) as boot, system and vendor. Is this the right thing to do? I did not even manage to get to the stage of flashing "LOS17.0-20200105-UNOFFICIAL-S2-S3.zip" because I already encountered this error prior to that.

In what order do I flash, and from what file exactly?
 

iiandrusii

Member
May 6, 2018
37
9
I thought it will be. Something you have damaged on motherboard, power specific (there is not profit in Performance mode, since its cutted by thermal, right). There is less/more power for 2 cameras on same power slot. It might be one of power controllers, or anything on motherboard or even motherboard.
Leave only 12mp, 8 is useless.


To all:
I have made mistake in thermal hal in 05.01 release just before compiling. If you play games and feel phone too hot I suggest to replace this file in vendor/bin/hw and give permissions 755.
Consider that power modes (in settings)above "balanced" are not covered by CPU thermal protection. Only very few- such charging, battery remain. So if motherboard reaches 60C phone will shut down.

My phone all the time turns off when I charging or watching a movie.
 

Psyl0w

Senior Member
Aug 21, 2018
56
21
... after trying to flash "boot.img" (the one located in root folder of the linked GDrive folder) as boot, system and vendor. Is this the right thing to do?

Well I don’t know if I misunderstand what you write or if it’s confuse in your mind, but it seems you haven’t got the trio of images boot system and vendor are included in the los zip file. So u grab for instance https://drive.google.com/drive/mobi...joHM7icESY?usp=drive_open&sort=13&direction=a
You unzip and you flash each image in the correct partition. You will probably need to perform a factory reset and format data (if encryption hasn’t been removed) but you can try without. If you don’t know how to flash images with fastboot or twrp, google will help u.
 
Last edited:

xdaillum

Senior Member
Feb 2, 2012
116
19
Well I don’t know if I misunderstand what you write or if it’s confuse in your mind, but it seems you haven’t got the trio of images boot system and vendor are included in the los zip file. So u grab for instance https://drive.google.com/drive/mobi...joHM7icESY?usp=drive_open&sort=13&direction=a
You unzip and you flash each image in the correct partition. You will probably need to perform a factory reset and format data (if encryption hasn’t been removed) but you can try without. If you don’t know how to flash images with fastboot or twrp, google will help u.

Oh my god yes I'm the confused one. I have never had to unzip a .zip to "flash" individually. So far, whenever flashing a new ROM (such as this), I've only ever done it by flashing the .zip file itself so I have never even thought to open up the zip file and take the files out individually, or to look inside the zip file individually for boot/system/vendor.

You are correct though - I did not have that trio of images but I can now see it in the .zip file I downloaded.

I'll try that now..!
 

XsceS3

New member
Dec 31, 2019
3
0
Android Service Error

Hi;

I flash last verison 16.11.2020 but system error (says android device error please connect manufacturer ....) and camera app isn't here.Please help.
 

xda-yup

Member
Dec 8, 2019
18
12
Here is what I did:
- from LOS 15 boot to TWRP
- check slot A
- format data
- flash boot
- flash system
- flash vendor
- format data
- check slot a
Only boots to twrp again :(

I had the same problem that almost drives me crazy :mad:
I can’t say exactly how the problem was fixed because I flashed, formatted, rebooted so many time :eek: but I think the issue was the usb cable was kept connected at the first reboot in system. When I did your sequence above but release the usb cable before rebooting from TWRP, I achieved los 17 boot finally.
Good luck

I had the same problem you were having nismohks (LOS bootloops back to TWRP) after following instructions from OP, I was coming from trebled 3.1 . I fixed the issue by flashing 2130 trebled 3.3, then following the OP but this time removing the usb cable during boot to system . Never would have thought to do that so thanks Psyl0w :good: , pretty sure this is the single thing that stopped the bootloop. I am now successfully running 16Jan version LOS17.1 :)
 
  • Like
Reactions: Psyl0w

xda-yup

Member
Dec 8, 2019
18
12
NFC works, people use safetynetfix and pay with gpay app
to do
encrypted, even password will not match in TWRP, cos TWRP uses old keymaster sources.

My SS2 is running on working LOS17.1 16Jan, all great so far.

i've just noticed i can't create backups or restore backups in TWRP though if i have a password set (whereas i could do so back on trebled 3.3). I think because I can't decrypt internal storage due to bug mentioned above / OP where password doesn't match in TWRP. New backups fail and existing backups just show as encrypted strings when you try to restore. So how do i decrypt storage while in TWRP to fix, is there some default password / pattern i can use? Or do i have to remove passord/saved fingerprints to create new backups / and in the event of system crash, will i be unable to restore and only option to reflash fresh 3x LOS .img again, then restore backup from SD card afterwards?

Screenshot of TWRP backup failure: https:// imgur.com/a/auQ8wo1
 

Psyl0w

Senior Member
Aug 21, 2018
56
21
Update TWRP

I’m really interested in an updated TWRP release if somebody makes a new one for los 17.1.
Updated means with Toybox commands updated. The current twrp includes outdated version 0.76 and lots of commands like TAR are buggy or limited regarding Busybox. The last version 0.82 is definitely improved. Android has already included it in its master branch:
https://android.googlesource.com/platform/external/toybox/+/ce2b356a0746e1203be0cf1ab9c90abdb0394e47
But not TeamWin yet :(
And lots of my backup scripts that uses TAR command cannot work properly with the old version. I would probably try to build an updated version but I don’t have Linux machine so far.
Here is the android.mk from twrp, the pathes towards tar and other commands are still pointing the pending folder but they are now in posix one with the new release. :angel:
 
  • Like
Reactions: dmukhin

xda-yup

Member
Dec 8, 2019
18
12
a) You can't do user key encrypted data backups.
b) The bug that twrp can't recognize user key is written on 1st page.

thanks, i read about user key bug i just don't think i understood the implications of it - ah so that bug means that to make a twrp backup we have to remove password before rebooting to twrp (that's what i've been doing so far). when i remove password, fingerprints removed, Gpay cards removed, so wanted to make sure i wasn't doing this each time without need :) tiny issue though in light of how awesome this rom is to use. i'm really enjoying LOS17.1 16Jan version , all working very smoothly, Gpay and Gcam confirmed working etc . Thanks so much for your work on it!
 

Top Liked Posts

  • There are no posts matching your filters.
  • 29
    LEGAL
    https://lineageos.org/legal/
    You flash this ROM on own risk!


    XDA:DevDB Information
    Lineage 17 *UNOFFICIAL* for Sharp Aquos S2, S3 (SAT/SS2/HH1/HH6)
    Multi ROM from sources supporting devices:
    Sharp Aquos S2 4/64 -SS2/C10,
    Sharp Aquos S2 6/128 -SAT,
    Sharp Aquos S3 -sdm630 (HH1/HH6).
    Sharp Aquos P6
    Nokia x6 (DRG)


    Contributors/Maintainers
    heineken78


    ROM OS Version: Android 10
    ROM Kernel: CAF 4.4.205
    ROM Firmware Required: Minimum update installed 2130WW/CN -for S2. For S3 - D350KR, Nokia DRG - Android 9-10.
    Based On: Android 10- Lineage 17.1
    Recovery: TWRP included.
    Device sources: here

    Gapps: Not included. Recommend to use only NANO version, because it includes necessary apps like Welbeing
    Data Encryption: encrypted;
    Do not: use boot(twrp) or vendor with other older/stock roms.

    Version Information
    Status: Beta
    Created 2019-11-03
    Last Updated LOS 17.1 2020-09-02

    Sources: https://github.com/Eddie07

    DOWNLOAD:
    Gdrive folder



    Changelog 02.09.2020:
    Lineage OS 17.1 02/09/20 for SAT/SS2/HH6/HD1
    -kernel: optimize power driver;
    -kernel: fix mdsi panel on from suspend crushes;
    -vendor/system:implement from sources Bluetooth QTI;
    -vendor/System:implement from sources perf QTI;
    -vendor/system:implement com.qualcomm.gps and drivers from sources;
    -kernel/system/vendor: new touchscreen gestures;
    -system: more options for Android 10 gestures;
    -system: disable magnet sensor;
    -system: implement new telecom framework from sources;
    -system: sim toogle swithes;
    -vendor/system: audio enhancements.
    -selinux fixes;
    -GSI:flash and go.
    -other.

    Changelog 07.08.2020:
    -remove restrictions for audio records
    -fixed auto recording option in Dialer
    -icon packs support option for LA Trebuchet: nova, etc.
    -long screenshot (Q from ASUS);
    -enabled show mv of QC in lockscreen.
    -fixes screen on bug after suspend

    Changelog 02.08.2020:
    Kernel:
    -Livedisplay for S2 & S3 & NOkia DRG; -Fast charging S2;
    System:
    -ARcore support without Magisk;
    -Dialer: autorecording;
    -Quick internet change via QCTiles (multisim); -Imitation of wifi for android when using a mobile network: persist.force.unmetered = true: -Display Profiles (4) for S2 & S3
    Vendor:
    - updating halls; - selinux fixes; - fix for gsi boot; - other garbage to make everything work.

    Changelog 13.05.2020:
    -updated recovery 3.4.0: supports OTA updates, key decryption works;
    -added custom face unlock: may need to assign camera perms manually;
    -fixed sensors init issue;

    -updated vendor.

    Note: due to fixes in encryption this version needs fresh boot after format! Backup your data.
    Use old backup, and apply gapps zip only after the first boot of system, dont boot to recovery after formatting.


    LOS 17.1 beta 13b-04-2020
    -fixed selinux denials: sensors issue, ril;

    LOS 17.1 beta 13-04-2020
    -LOS Android update android-10.0.0_r33 (05.04)
    -added Nokia DRG (x6) support
    -fixed configs media -front camera video fail fix in gcam.
    -updated audio configs to Q.
    -selinux still in testing.

    LOS 17.1 beta 23-02-2020
    -Able to disable sim card (if 2)- experimental;
    -Lineage vendor implementations: Off screen gestures; Adjustable vibrations ( 3 levels);- More overlays.
    - yuv support;


    Also:

    Kernel:
    Power, sound, display changes, updated latest wifi driver. Also defined min brightness and tfa chip switching via nodes.
    System:
    Extra Minimum brightness option, reorganized, added settings, implementation of google personalisation (work but Screen Attention fails) no need gapps. 6x5 grid for launcher, option to add quick tile rows.
    Vendor:
    Made real blue accent color pickable, sound chip tweaking.
    Still to do:virtual displays and wfd. (I think problem is hwc sources, need fix later)

    LOS 17.1 daily 04-02-2020
    -VENDOR: fixes wifi sharing (want working in last two builds), fixed diag_lsm error,
    added support of external usb cameras.


    LOS 17.1 daily 02-02-2020
    -KERNEL: power drain fix to all previous kernels from 28.12 due hotplug conflict with PERF2.0 hal;
    merged with LA.UM.8.2.r2-00700-sdm660.0;
    updated qcacld (wifi);

    not tested with s3.

    -SYSTEM: Latest LOS updates, more telephony implementations from nokia stock Q;
    -VENDOR: LOS updates, qcom caf updates, more display implementations.


    LOS 17.1 test 08-01-2020
    -New LOS Android;
    -Kernel battery control changes (s2)
    -gps enchantment, phone enchantments.


    05-01-2020
    -kernel: thermal related fixes.
    -system: Snap camera replace by stock FIH cam, qcom ril framework blobs remade.
    -vendor: manual network selection fix, new thermal impl.Fixed compatibility with GSI roms: camera and softkey navigation bar enabled.


    25-12-2019
    Kernel:
    -merged 4.4.205;
    -camera fix for gcam, dualcam; use this cam with dualcam enabled.
    If gcam keeps crashing disable dualcam: persist.vendor.camera.expose.aux=0
    -showing battery type (C10/S2);
    System and Vendor:
    -LOS up-to-date;
    -implementation on new qcom encryption, booting faster;
    -LOS beta circle battery icon ;
    Note if you find that media folder is not getting encrypted with key/password - make full format from twrp and boot with current version.

    14-12-2019
    service pak N141219

    28-11-2019
    kernel: changes in kernel config
    system: LOS 17.1 upd up 27.11
    vendor: upd ril, qti, camera blobs, fixed PERF drain, fix bt lags, add APTX Bt codec.
    -Rounded corners can be now disabled via vendor/build.prop.
    -GUI of S3 of S2 can be chosen from developers settings (remain for GSI too)

    17-11-2019
    Update Android 10.0.0_r11

    15-11-2019
    -supports Sharp Aquos S3 models -HH1 and HH6!
    -Los up-to-date

    05-11-2019
    -kernel updated to 4.4.194 (caf LA.UM.8.2.r1-04800-sdm660.0)
    -CAMERA: latest camera vendor blobs Q from 2060 Nokia PL2 (test option prop persist.cam.dv=(PL2/B2N/C1N) for camera hal)
    -PERFORMANCE: PERF 2.0 fixed
    -LINEAGE: current Lineage updates from mainstream(not much)
    -SOUND: revert to stock soundtrigger
    -VNDK rebuild with Q rules
    -added many enhancements in build.props

    03-11-2019
    First release

    Installation
    1. First time
    Enter twrp or from fastboot and flash images: boot, system, vendor. Reboot back recovery and format data. Install Gapps same time (as option).Reboot to new system.

    2. Next updates/upgrades
    Enter twrp and flash new images. If you had installed Gapps, flash same zip file o gapps. Reboot to system.
    Pls note: Due to changes in encryption, if your data is before July 2020, you will have to format data to be able to use newer roms.


    Bugs:
    -Minor LOS bugs.
    -You will find may be
    5
    second rear lens work? how? its only for "depth" effect...

    Sent from my Sharp Aquos S2 4/64 using Tapatalk


    13.04. update on your risk as usual
    -LOS Android update android-10.0.0_r33 (05.04)
    -added Nokia DRG (x6) support :)
    -fixed configs media -front camera video fail fix in gcam.
    -updated audio configs to Q.
    -selinux still in testing.
    5
    Version from 08.04 is available:
    -added HD1 dt2wake support;
    -fixed more selinux denials ( hight power consumption fix);
    -fixed old root detection in some applications;
    note: for ss2 c10 use boot.img from previous version
    5
    There is new build 16.02 available for test:
    Kernel:
    Power, sound, display changes, updated latest wifi driver. Also defined min brightness and tfa chip switching via nodes.
    System:
    Extra Minimum brightness option, reorganized, added settings, implementation of google personalisation (work but Screen Attention fails) no need gapps. 6x5 grid for launcher, option to add quick tile rows.
    Vendor:
    Made real blue accent color pickable, sound chip tweaking.
    Still to do:virtual displays and wfd. (I think problem is hwc sources, need fix later)
    4
    link doesnt work for me, can you upload it on your google drive?

    This weekend next Los release, with fixed virtual displays and many things I hope also.
    And supporting of this never exist device https://www.youtube.com/watch?v=JuLLZMTyDkk
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone