Hi all,
I try to replace PhilZ Touch 3 by TWRP on my (old) galaxy S2 (GT-I9100) to install LineageOS 16 ( lineage-16.0-20191006-UNOFFICIAL-i9100.zip)
I tried using PhilZ:
1) wipe data/factory reset
2)wipe cache partition
3) install zip from sdcard
but it failed and I read that TWRP should be used to do that.
I have no M$ system, only linux OS, also I get Heimdall 1.4.2 and booting in download mode I did:
Code:
$ sudo heimdall flash --RECOVERY twrp-3.3.1-0-i9100.img
Heimdall v1.4.1
Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
100%
RECOVERY upload successful
Ending session...
Rebooting device...
Releasing device interface...
But after reboot it's Philz is always the recovery system
Any idea of how to success?
Pierre_ said:
Hi all,
I try to replace PhilZ Touch 3 by TWRP on my (old) galaxy S2 (GT-I9100) to install LineageOS 16 ( lineage-16.0-20191006-UNOFFICIAL-i9100.zip)
Click to expand...
Click to collapse
I also followed https://wiki.lineageos.org/devices/i9100/install guide until step 7 where when I reboot the device into recovery mode I have still Philz CWM instead off TWRP.
Perhaps a solution found within the FAQ of PhilZ Touch 6.59.0
5- CMUpdater cannot flash downlaoded files
If you get a /sdcard/0 error, it means you have /sdcard set as /data/media/0 in recovery
The reason is that CM app doesn't support /data/media/0 and is faking recovery with a /sdcard/0 implementation
You still can alter the setting and force it to /data/media in Advanced menu. This will give full compatibility with cwm, CM roms and CM Updater
6- How to flash a boot.img or recovery.img file?
- Put your boot.img or/and recovery.img files under a subfolder in clockworkmod/backup on sdcards
exp: /sdcard/clockworkmod/backup/cm-10.1-nightly_20130713/boot.img
- Navigate to Backup and Restore / Custom Backup and Restore / Custom Restore Job
- Unselect all partitions except boot and/or recovery
- Select >> Start Custom Backup Job <<
- Browse to your backup location until your cm-10.1-nightly_20130713, and select any file inside it
- You are done
Click to expand...
Click to collapse
I'll try it soon
Related
I was trying to update the CM 11 Rom that was on my phone but in the process of doing this it failed and now whenever I reboot it just boots straight into recovery. I've read about flashing a ROM with Odin but my windows 8 laptop isn't recognizing my phone even after getting the micro USB port on my phone replaced. It's charging just not being recognized!
Also when I tried to flash a ROM in recovery it says it fails
This is what comes up when flashing
Code:
Updating partition details
Installing '/external_sd/cm-11-20140407-UNOFFICI
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/extern
Error flashing zip '/external_sd/cm-11-20140407-
Updating partition details
Then when I click reboot system it says (this only happens if I try and flash a rom)
Fix superuser permissions?
Root permissions appear to be lost.
fix root permissions now?
(Fixes permissions on su binary & app)
Can someone help me fix my phone please
1st try flashing stock rom,then comment here
The .zip file of the ROM that you're trying to flash seems corrupted.
Try to get your phone recognized by Odin and flash a stock ROM into the phone.
Hello everyone,
I want to share my experience with rooting (n00b). So for the first time ever, I managed to root my g900t and my p-600 note --needless to say, I was very excited. When everything checked out and Root Checker told me that I was indeed rooted, the first thing I did was going to Youtube to see what I could do first.
The very first thing that came up was to create a Custom Recovery...fair enough. I watched multiple videos that guaranteed to install the CR "easily". Well, I think I'm an idiot because I couldn't get anything to work.
I tried TWRP, CWM, Philz Touch and TWRP and Philz both loaded on my recovery boot but I still kept getting messages on Rom Manager that I didn't have a custom recovery. At times I also got a lot of errors. I not only tried to get information from the forum but their respective sites and matching my device, installing it through flash & Odin--no luck.
Anyways, I soft-bricked both my g900t and my p600 and after reading hundreds of posts here and other forums and spending all day, I managed to get them running again.
Right now, I'm thankful that I have both devices running and rooted but I still don't know if I have a custom recovery and frankly, I'm scared to try it again. How important is it to get a CR?
By the way, is it bad that all those bad CRs that I installed are still there (if they are)?
I read the rules and also a a lot of forum posts with different variations of CRs for my devices with no luck.
For reference:
Galaxy s5 (5.1.1) Rooted SM-G900T
Samsung Note 10.1 (5.1.1) (Wi-fi) Rooted SM-P600
Thanks guys!
Flashing TWRP through ODIN is very simple - lots of guides out there, but here are some steps:
- Install Samsung Mobile Driver
- Download and unzip ODIN 3 (e.g, 3.1.0.7) to a directory
- Download twrp-2.8.7.0-klte.img.tar from twrp.me
- Boot phone into Download Mode (Vol Down - Home - Power), follow instruction to get to the download mode
- Connect phone to PC, wait for the drivers to be ready
- Start Odin, wait for "Added" message to show up
- Click AP and choose the TWRP tar file
- Go
Sometimes a trick is to uncheck "auto reboot", then flash it twice. That is, flash once, when completely done ("success" on Odin), disconnect and remove/replace battery, power up to boot mode again, then flash again. This is rarely needed but I've had to do this for modem flash once or twice in the past.
Alternatively, you can flash it on the phone from a terminal/cmd shell (lots of apps to choose from on Google Play), and if you have twrp.img extracted to /sdcard, you can do this (again, on the phone):
> su
# dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
The dd method is also doable from ADB shell, but that requires ADB to be set up on the PC.
Hope this helps - I wrote the steps the above from memory but others can correct me I stated anything inaccurately.
EDIT: there are also apps that can install custom recovery, such as Flashify, TWRP manager, ROM Toolbox, Nandroid Manager, etc. Of course, root is required.
many thanks
lost_ said:
Flashing TWRP through ODIN is very simple - lots of guides out there, but here are some steps:
- Install Samsung Mobile Driver
- Download and unzip ODIN 3 (e.g, 3.1.0.7) to a directory
- Download twrp-2.8.7.0-klte.img.tar from ]
- Boot phone into Download Mode (Vol Down - Home - Power), follow instruction to get to the download mode
- Connect phone to PC, wait for the drivers to be ready
- Start Odin, wait for "Added" message to show up
- Click AP and choose the TWRP tar file
- Go
Sometimes a trick is to uncheck "auto reboot", then flash it twice. That is, flash once, when completely done ("success" on Odin), disconnect and remove/replace battery, power up to boot mode again, then flash again. This is rarely needed but I've had to do this for modem flash once or twice in the past.
Alternatively, you can flash it on the phone from a terminal/cmd shell (lots of apps to choose from on Google Play), and if you have twrp.img extracted to /sdcard, you can do this (again, on the phone):
> su
# dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
The dd method is also doable from ADB shell, but that requires ADB to be set up on the PC.
Hope this helps - I wrote the steps the above from memory but others can correct me I stated anything inaccurately.
EDIT: there are also apps that can install custom recovery, such as Flashify, TWRP manager, ROM Toolbox, Nandroid Manager, etc. Of course, root is required.
Click to expand...
Click to collapse
Thank you lost_,
my issue wasn't rooting the devices --they both are, it's getting a custom recovery installed. Neither TWRP nor CWM can find a recovery for my device (g900t). I've looked at countless posts with the same luck. At one point at recovery I had TWRP, which from what I was reading, it meant that I had a custom recovery, right? but again, TWRP and CWM say that I don't have one installed and when I tried to reboot out of recovery it would go into a boot loop forcing me to re-root my device. Basically, I'm stuck at this point and all I really want is to backup all my apps so that they run from my SD card, no coding, no custom roms but it gives me issues. Thanks again.
molotovgod said:
Thank you lost_,
my issue wasn't rooting the devices --they both are, it's getting a custom recovery installed. Neither TWRP nor CWM can find a recovery for my device (g900t). I've looked at countless posts with the same luck. At one point at recovery I had TWRP, which from what I was reading, it meant that I had a custom recovery, right? but again, TWRP and CWM say that I don't have one installed and when I tried to reboot out of recovery it would go into a boot loop forcing me to re-root my device. Basically, I'm stuck at this point and all I really want is to backup all my apps so that they run from my SD card, no coding, no custom roms but it gives me issues. Thanks again.
Click to expand...
Click to collapse
No offense intended, I think you're lost and confused. My post was never about rooting. I did understand you were rooted already. I was outlining how to install a custom recovery, which TWRP and CWM are. Yeah, if you're having a hard time sorting things out based on what I outlined, I don't know how else to get you going. Perhaps start over with your research and read up again on some basic Android 101 (not a HOWTO but an explanation on what is what). Good luck!
ps: this thread should be on the Q&A forum, but we're all helpful and friendly here and you should ask specific questions on that forum instead.
if you're using stock samsung recovery & its stock android, they will overwrite what you just flashed when they boot
odin->flash twrp WITHOUT reboot option->remove battery->put battery->turn on phone directly into recovery, you should see TWRP & you'll be able to flash whatever you want from here, i have no idea what happens if you boot to stock after this since i use CM
i came from stock 4.4 november 2014, used odin 3.07 & https://dl.twrp.me/klte/ 2.8.7.0
kn00tcn said:
if you're using stock samsung recovery & its stock android, they will overwrite what you just flashed when they boot
odin->flash twrp WITHOUT reboot option->remove battery->put battery->turn on phone directly into recovery, you should see TWRP & you'll be able to flash whatever you want from here, i have no idea what happens if you boot to stock after this since i use CM
i came from stock 4.4 november 2014, used odin 3.07 &TWRP 2.8.7.0
Click to expand...
Click to collapse
I have the same phone and cannot flash custom recovery either, as I am a linux user I used heimdall and here is my output
Code:
[[email protected] Downloads]# heimdall flash --RECOVERY twrp-2.8.7.0-klte.img --no-reboot
Heimdall v1.4.1
Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
Re-attaching kernel driver...
[[email protected] Downloads]#
I flashed my wife's Samsung Galaxy S3 (GT-i9300) and my Galaxy Tab 2 (GT-P5113) a successfully using the procedure described in each device wiki in cyanogenmod page, but same procedure in my phone fails.
My Samsung Galaxy S5 (GT-G900T) is running Samsung's stock Android 5.1.1 (not rooted btw) and stock recovery.
Can you spot what I am doing wrong? Thank you in advance.
pablomino said:
I am a linux user I used heimdall
Click to expand...
Click to collapse
https://github.com/Benjamin-Dobell/Heimdall/issues/209 i couldnt use heimdall either, but there is a patch in that thread that might work for you, you just have to recompile yourself if they didnt update the linux binary
if that still doesnt work, i think you should just use virtualbox to run windows7 & odin with whatever the option is called to have usb pass-through/direct usb access
kn00tcn said:
if that still doesnt work, i think you should just use virtualbox to run windows7 & odin with whatever the option is called to have usb pass-through/direct usb access
Click to expand...
Click to collapse
I moved to a physical Win7 PC, it didn't work either, same error. Could it be because the device is already on Android 5?
Thank you a lot.
Code:
Microsoft Windows [Versión 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Reservados todos los derechos.
C:\>cd heimdall
C:\heimdall>heimdall version
v1.4.0
C:\heimdall>cd Drivers
C:\heimdall\Drivers>zadig
C:\heimdall\Drivers>zadig
C:\heimdall\Drivers>cd ..
C:\heimdall>heimdall flash --RECOVERY twrp-2.8.7.0-klte.img --no-reboot
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
C:\heimdall>
---------- Post added at 08:42 PM ---------- Previous post was at 08:13 PM ----------
kn00tcn said:
you just have to recompile yourself
Click to expand...
Click to collapse
Anyway I will try compiling the tool from source, I will update with my results. Thank you lot.
pablomino said:
I moved to a physical Win7 PC, it didn't work either, same error.
Click to expand...
Click to collapse
i said to use odin, i have done it several times already, although some people say a newer odin is needed for lollipop based samsung installations... i mentioned 3.07 earlier, today i did 3.10.7 with the latest G900TUVS1FOL1 complete package from sammobile so i can update my baseband & bootloader easily, then once again odin->flash twrp without reboot->remove battery->boot into twrp recovery->flash CM
heimdall does not have the code update that supposedly fixes the PIT error in the official windows binaries, so heimdall will never work on windows unless you compile the fix yourself
(if using odin, always check the exe on virustotal, always get it from someplace reliable like sammobile or an active thread here rather than google)
kn00tcn said:
i said to use odin
Click to expand...
Click to collapse
This solved my problem, thank you a lot.
yeah what stupid thing am i doing please?
twrp2870-20150814-p4.zip
Tab 10.1 p7500 3g stock 4.0.4
Heimdall 1.4.0
Ubuntu 14.04
seems to flash fine (blue progress bar ok)
hangs when selecting recovery (VOL-+POWER, select left side icon, VOL+).
is there some way to get into recovery from Heimdall btw? adb doesn’t work in download mode afaik.
*****.********:~/Downloads/TWRP/recovery$ sudo heimdall flash --SOS recovery.img --no-reboot
[sudo] password for ******:
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading SOS
100%
SOS upload successful
Ending session...
Releasing device interface...
Click to expand...
Click to collapse
CWM 6031 works! hmmmm not sure if that's ok to use or not, will have to investigate..
Smiff2 said:
CWM 6031 works! hmmmm not sure if that's ok to use or not, will have to investigate..
Click to expand...
Click to collapse
turns out CWM works ok for installing 5.1, but not 6.0.. maybe ROM specific issues, maybe not.. anyone have ideas?
error status 7 when trying to install 6.0 with CWM 6031.
i know i can hack the ROM but would prefer to get TWRP working as recommended by ROM author.
ah i may have the answer! some recovery needs 2 partitions.. SOS and HIDDEN
The recovery partition is only 5 megabytes. This is not enough space for the features of newer recovery software. This version of recovery uses the "hidden" partition to extend the recovery storage space. The hidden partition was used by official Samsung ROMs (Ice Cream Sandwich 4.0.4 and Honeycomb 3.2) to preload apps. It is not being used by most custom ROMs.
Warning: You must be careful with the hidden partition while using this recovery. Since it is a normal partition, it is possible that for whatever reason it is mounted and the recovery files deleted/modified. To protect this partition I've modified the kernel so that this partition can only be mounted as read-only. But you must be careful while using other ROMs with kernels that do not have this.
Click to expand...
Click to collapse
I searched up and down, read all the stickies here.
Problem is, in many posts links or images are broken. Other posts assume, the device already has seen custom firmware.
I got a never-touched I9100 and I want to get TWRP running. Once this is achieved, I know the rest. I currently have the stock recovery booting - somewhere this was called 3e. All my attempts to flash TWRP via heimdall resulted in only the old recovery showing up. Somewhere it was mentioned I have to flash another kernel first.
So please, does someone have a tutorial or can leave some notes that WORK?
install Apolo kernel TWRP version
https://app.box.com/s/bp9vm6i0vuq1c0x4d8x3y9253b8i38q6/folder/6395372561
Abels2 said:
install Apolo kernel TWRP version
https://app.box.com/s/bp9vm6i0vuq1c0x4d8x3y9253b8i38q6/folder/6395372561
Click to expand...
Click to collapse
404 - This app.box.com page can’t be found
Exactly my problem - all dead or outdated or for wrong setting.
mad-murdock said:
404 - This app.box.com page can’t be found
Exactly my problem - all dead or outdated or for wrong setting.
Click to expand...
Click to collapse
I just uploaded to my google drive the latest version
https://drive.google.com/open?id=1hXCiQ4TijP3d8nUeC5DsRyo8oBuoANmH
to control BLN, governors and others download the Apolo configurator app from google play
https://play.google.com/store/apps/details?id=com.pedestre.configuratorapolo
Edit: it has preinstalled TWRP 2.6.3
if you want the latest versions TWRP 3.x isorec you should go to MM or N roms
Abels2 said:
I just uploaded to my google drive the latest version
https://drive.google.com/open?id=1hXCiQ4TijP3d8nUeC5DsRyo8oBuoANmH
to control BLN, governors and others download the Apolo configurator app from google play
https://play.google.com/store/apps/details?id=com.pedestre.configuratorapolo
Edit: it has preinstalled TWRP 2.6.3
if you want the latest versions TWRP 3.x isorec you should go to MM or N roms
Click to expand...
Click to collapse
Thanks for helping and taking your time to upload! So I heimdall-flash this kernel and then 3-button-combo brings me into twrp 2.6.3 from where i can flash lineage or something similar?
And the reason for this is - if I understand right - recovery on I9100 is not a standalone partition but part of the kernel partition - so your recovery will always be bound to your kernel. Did I get this right?
Nope, cannot flash this kernel with heimdall:
Code:
heimdall flash --BOOT Apolo-4.15b_ExtrV2-TWRP/zImage --no-reboot
results in an error:
Code:
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading BOOT
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: BOOT upload failed!
Ending session...
Releasing device interface...
mad-murdock said:
Nope, cannot flash this kernel with heimdall:
Code:
heimdall flash --BOOT Apolo-4.15b_ExtrV2-TWRP/zImage --no-reboot
results in an error:
Code:
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading BOOT
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: BOOT upload failed!
Ending session...
Releasing device interface...
Click to expand...
Click to collapse
it is installed by means of recovery
the recovery and kernel that are not compatible for all the versions of android therefore if you install some custom rom that already has some recovery or kernel pre installed you will have to
guide for partitions without computer
https://forum.xda-developers.com/galaxy-s2/help/kernel-to-root-lineage-i9100-device-t3748674/post75556909#post75556909
Abels2 said:
it is installed by means of recovery
the recovery and kernel that are not compatible for all the versions of android therefore if you install some custom rom that already has some recovery or kernel pre installed you will have to
guide for partitions without computer
https://forum.xda-developers.com/galaxy-s2/help/kernel-to-root-lineage-i9100-device-t3748674/post75556909#post75556909
Click to expand...
Click to collapse
Unfortuately this wont help. I tried to install it with the Samung 3e recovery via adb sideload, but the 3e fails to verify the signature. So I cannot use your kernel.zip file. Reading the other linked thread now.
Thanks for helping me, btw. I guess everyone owning a S2 already has a custom rom installed and thats why all the guides I find are oudated. My S2 is just for playing around, so I am in no hurry.
Hi folks,
I had opened the bootloader for this device, the TRWP is starting fine. The partitions: product, boot and vendor is not modified, only the vbmeta has been changed, and also the recovery and the system.
I'm used the system file: lineage-17.1-20200402-UNOFFICIAL-treble_a64_bvN.img
The file I'll has flash with the command: heimdall flash --SYSTEM lineage-17.1-20200402-UNOFFICIAL-treble_a64_bvN.img, the flashing was successfully.
The SMA105 is booting, but after 10 minutes, the phone is stucking in the same boot logo. Nothing is happend, no steps for terminating the system installation. It seams, the SMA105 waiting for an command. But, I can not read an log file for the booting or switching of temporally the bootlogo.
Any solutions for me?
Greetings tiptel170
P.S.
Flashing other roms for example Viper etc ... This is the same effect. Wateing and wateing ...
renaming the file "bootaniamation.zip" in the folder /system/media was not successful. Because, it turns the animation on with the word "ANDROID". And the adb logcat, the same it will not working.
I'll has changed the file default.prop
Code:
ro.adb.secure=0
persist.sys.usb.config=mtp,adb
ro.secure=0
Thanks...
Edit:
On the SM-T813 I'll had the same problem, but I could resolved with the "heimdall print-pit". And the tablett reboot normaly. But I use the same command on the A10, nothing has been changed, the same result with the booting.
I did the same haha. It shows android but it booted
tiptel170 said:
Hi folks,
I had opened the bootloader for this device, the TRWP is starting fine. The partitions: product, boot and vendor is not modified, only the vbmeta has been changed, and also the recovery and the system.
I'm used the system file: lineage-17.1-20200402-UNOFFICIAL-treble_a64_bvN.img
The file I'll has flash with the command: heimdall flash --SYSTEM lineage-17.1-20200402-UNOFFICIAL-treble_a64_bvN.img, the flashing was successfully.
The SMA105 is booting, but after 10 minutes, the phone is stucking in the same boot logo. Nothing is happend, no steps for terminating the system installation. It seams, the SMA105 waiting for an command. But, I can not read an log file for the booting or switching of temporally the bootlogo.
Any solutions for me?
Greetings tiptel170
P.S.
Flashing other roms for example Viper etc ... This is the same effect. Wateing and wateing ...
Click to expand...
Click to collapse
Samsung Galaxy A10 has Lineage 17.1 custom rom (arm and arm64 versions)
You can download them here:
arm version
arm64 version
Note:
-> They will boot only with permissive selinux kernels (here)
-> It's a rom, not a gsi. It has it's own vendor.
-> You just need to flash the rom in recovery (twrp) , and then flash the permissive kernel.
Hello Chatur27,
I 'll had installed the system and the kernel. This is the same effect, stucks on booting. Then I 'll changed form arm to arm64 with the same kernel, it's the same result. And I used the twrp. And waiting more then 10min for the finish up the booting.
tiptel170 said:
Hello Chatur27,
I 'll had installed the system and the kernel. This is the same effect, stucks on booting. Then I 'll changed form arm to arm64 with the same kernel, it's the same result. And I used the twrp. And waiting more then 10min for the finish up the booting.
Click to expand...
Click to collapse
I will suggest you to stick to stock rom if you are not able to install a rom
Cheers!
I'm able to install roms on the Samsung phones / tablets. Something is missing, but it will not continua. And on this phone is not an stock rom installed, it's empty. I think I will be back to the stock rom and then reinstall the LOS 17. May be I' ll erased an part for booting. ;-)
Cheers.
Update:
I 'll had downloaded the firmware for this phone, then I extracted the packages in to the /tmp directory:
Code:
BL_A105FNXXU6BUC3_CL20057335_QB39107009_REV00_user_low_ship.tar
cm.bin.lz4
param.lz4
sboot.bin.lz4
And
Code:
CP_A105FNXXU6BUC3_CP18543320_CL20057335_QB39107009_REV00_user_low_ship.tar
modem.bin.lz4
Decompress the lz4 files:
Code:
cd /tmp
for lz4 in `ls *.lz4`; do unlz4 $lz4; done
Boot in to the download-modus and than I had flashed with heimdall
Code:
heimdall flash --CM cm.bin --PARAM param.bin --SBOOT sboot.bin --RADIO modem.bin
The RADIO partition is very important, if is not installed your SIM-Card wil not be detected and the mobil network will not work!
Reboot to the download-modus
And finally I had installed the twrp-3.5.2_9-0-a10.img.tar and vbmeta_disabled.tar:
Code:
heimdall flash --RECOVERY recovery.img --VBMETA vbmeta.img
Reboot again in this case in to the recovery mode:
Wipe
Code:
data
cache
And install this:
Code:
lineage-17.1-20200921-UNOFFICIAL-a10.zip
open-gapps
magisk-amager 20.4
And the phone will be start up normaly.
This system with this version works well, but:
- The battery runs out very fast - in an day is the battery at 9%
- Open files with WhatsApp, K9-Mail or simelar dose not work: The dialog open with an APP will be open very sohrt and cloed quickly, by WhatsApp crashed the window and restart the Whatsapp.
And this version of the lineage OS lineage-17.1-20210221-UNOFFICIAL-a10.zip
- Crashed the grafics, the screen goes withe, and then I need make an hard reset.
Need help for resolver the problem.
Thanks, tiptel170