SM-A105FN/DS Lineage OS 17.1 stucks on booting - Samsung Galaxy A10 Questions & Answers

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

Related

[ROM][6.0.1][M1D64S] ext4 marshmallow for dory

This is an ext4-formatted system image of the stock rom for the original LG G watch along with my custom ramdisk/kernel (invisiblek_v8.img). Currently based off M1D64S.
If you like to tinker around with files on your /system partition, you may have noticed that starting with MEC23G, this device now uses squashfs as its /system partition filesystem. The problem here is that squashfs cannot be simply written to like ext4 (or really any other filesystem you're probably familiar with). Which makes it a lot more difficult to mod.
The current system partition isn't big enough for us to use ext4 with everything that's included in the stock rom. So I've had to trim it down a bit. Currently it ends up with about 12mb free.
Here's a list of what I've removed: https://gist.github.com/invisiblek/69927e9727dbc2478fc83f72cc6a8f6e
tl;dr: I remove a bunch of localized fonts, the google fit app, a few watch faces, and a script that replaces your recovery with the stock recovery on boot. You can add these back either by sideloading the apk(s) or pushing the files back to their respective location on /system.
Here's a zip of everything that was removed, in case you want to add something back (which is now super easy since /system is ext4!): http://download.invisiblek.org/dory/rom/M1D64S_ext4/removed.zip
Download: http://download.invisiblek.org/dory/rom/M1D64S_ext4/M1D64S_ext4.zip (this is unrooted, you can flash android wear supersu yourself from twrp)
md5sum: 520781014c3191e8fd73e824556597ff
How to flash:
- You must be OEM unlocked in order to use this as well as being familiar with how to fastboot images.
- Grab the zip from above and extract it
- Reboot your device into fastboot mode (either via adb reboot bootloader from android, or by holding the small button on the back of the device while its powered off)
- Issue the following commands:
Code:
fastboot flash system system.img.ext4
fastboot flash boot boot.img
fastboot reboot
Feel free to use, modify and share this all you want, but please link back here so others wishing to tinker can get a (mostly) fully stock base to start with!
It gets stuck at boot logo, after some time it reboots in twrp
After installing supersu it is in bootloop
After flashing Invisiblek kernel v8 it works!
flash this rom and Invisiblek kernel v8 and twrp, it works good!
eio.adea said:
It gets stuck at boot logo, after some time it reboots in twrp
After installing supersu it is in bootloop
After flashing Invisiblek kernel v8 it works!
Click to expand...
Click to collapse
Ah...lame...well, I just swapped out the boot.img that was in there with a copy of my v8 image.
Seems to work fine for me.
Any chance of us getting a full ROM on this device? i.e. Ghoma for 6.0.1
I did try to move fit to the watch and succeeded, but there is no fit workout app...
A question, is not it better F2FS that ext4? I am sorry, if it is a silly question.
@invisiblek M1D65B released
When I try to flash supersu I keep getting error: 2, no description. I pushed it to /sdcard/ and tried to install it with TWRP.

It was all going so well too... Help with a boot loop brick atm :)

Hi all,
I went ahead and rooted my Mate 10 Pro today - I unlocked my bootloader, installed TWRP and got it running pretty sweet. Then, like a tool - tried installing xposed framework and got myself into a boot loop.
I can get to fastboot, I can get into twrp - but for the life of me don't know how to get a system wipe and fresh format! I've tried flashing LineageOS - but that's stuck on a loading screen and then boot loops after about 10minutes.
What happens is I turn my phone on - see the bootloader message - if I do nothing there's a 50/50 changes Huawei's eRecovery window opens (where if i connect it to the wifi, it fails and gives me the option of reboot or shutdown) or LineageOS boot animation loops for about 10minutes before shutting down.
At this stage, I don't mind what rom i get working - i just want something working and I'm really regretting xposed (I should of googled!).
I really don't want to pay $40 usd - and am happy tinkering around, but would appreciate some solid advice on how I can use TWRP to wipe everything and start again!
I'm also a little confused as to why eRecovery is coming up at all - and why it can't download anything!!!!!
Can someone help me get a phone back?
Thanks!
Yeah, I bootlooped going with xposed too, but I have the Mate 10 (regular) and no TWRP. Can you get to TWRP and simply flash a clean ROM? If not, which I presume is the case, can you get to Fastboot? To try, when you get to the eRecovery window, use the option to shut down your phone. Then press the power button and, while holding it, plus in your USB cable (the other end which should already be attached to your computer). Then go to Mankindtw's thread for flashing ROMs (Mate 10 Flash Oreo one). Basically, you download three zip files from a russian language page with all the latest Huawei ROMs, repackage them within his utility, and then flash them from within his utility. Worked for me.
download update.zip (for your firmware) from http://pro-teammt.ru/firmware-database
Extract update.app from update.zip
Download Huawei Update Extractor (open it and go to settings and disable header check)
Open update.app in Huawei Update Extractor
Extract SYSTEM from update.app using Huawei Update Extractor.
(Not sure if Xposed modifies vendor too, so you might have to extract that as well)
Fastboot flash system system.img
See if it boots now. If not you could try extracting recovery_ramdisk and flash recovery_ramdisk.img to the recovery_ramdisk partition then factory reset from stock recovery.
If it does modify vendor you'd have to flash vendor as well.
Or you could try flashing lineage os system, flash recovery_ramdisk and factory reset from stock recovery (factory reset is needed to get aosp roms running)
If it still fails, use mankindtws HWOTA as described by rogerinnyc above. (link: https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814)
Stock rom seems to be installing. TY for your help
Toldorn said:
The problem I'm having now is, on my win7 and win10 pc's - when I enter fastboot, neither PC will accept drivers for it and therefore, I can't fastboot flash anything.
I just get '<waiting for device>' even when plugged in (and windows 'driver no successful' message)
Is there a way to transfer the files via twrp adb sideload?
Click to expand...
Click to collapse
Sadly no, this corresponds to reflashing the whole phone, block by block.
have you tried to find matching drivers ? (it should be pretty easy on windows 10 normally...)
Toldorn said:
The problem I'm having now is, on my win7 and win10 pc's - when I enter fastboot, neither PC will accept drivers for it and therefore, I can't fastboot flash anything.
I just get '<waiting for device>' even when plugged in (and windows 'driver no successful' message)
Is there a way to transfer the files via twrp adb sideload?
Click to expand...
Click to collapse
ChriKn said:
Sadly no, this corresponds to reflashing the whole phone, block by block.
have you tried to find matching drivers ? (it should be pretty easy on windows 10 normally...)
Click to expand...
Click to collapse
Install this regfix https://www.dc-unlocker.com/huawei-mate-10-fastboot-usb-device-not-recognised-fix
However, you would probably have had problems before too when flashing twrp.
But worth a shot I guess.
Didn't see it said you tried on win 7 too.
And if it worked before on Win 10 it should work without it.
I guess you could push system.img to /data/system.img then tap Install and selectInternal storage, tap on (go up one level) in browser, now you'll be at /. Tap on /data and then on system.img. Flash to 'System Image'.
Edit: I've tested with recovery and that flashes fine from /data/.
please see below;
Hi all. My SDCARD was encrypted in TWRP, so I googled and saw I should run this command;
recovery --wipe_data --set_filesystem_encryption=off
Which I did on TWRP terminal - and now im boot looping again. I tried fastboot system.img and it's still bootloading. I see there's supposed to be a 'boot.img' in my update.app, but there isn't.
Any ideas?
Toldorn said:
Hi all. My SDCARD was encrypted in TWRP, so I googled and saw I should run this command;
recovery --wipe_data --set_filesystem_encryption=off
Which I did on TWRP terminal - and now im boot looping again. I tried fastboot system.img and it's still bootloading. I see there's supposed to be a 'boot.img' in my update.app, but there isn't.
Any ideas?
Click to expand...
Click to collapse
Boot.img is for Nougat. Oreo uses ramdisk.
Try wiping data in TWRP (Wipe - Format Data).
You can't turn off encryption in TWRP. It's controlled by /vendor/etc/*.fstab (* = kirin970 in this case). (You can temporarily turn off encryption but it re-encrypts after booting if fstab is untouched)
But removing encryption won't fix you bootlooping, and that command you used is for Full disk encryption, we use file based encryption.
You could also try flashing back stock recovery and do factory reset from there.
Edit: Oh, you're the guy who PM'd me
I've reflashed my 'system.img' as before - but im having trouble getting into factory reset menu.
all it ever does is go into e'Recovery instead, which is useless.
Also, my booting image is still a green page of pixels - rather than a huawei logo.
Hi. I have a bla-a09 and need help. can boot into twrp but will not boot.

Making custom boot.img for MTK 6577 device.

Hello all,
I have a question about flashing Lenovo IdeaTab A1000LF (MTK6577 device). I would like to add busybox into initramfs and slightly change init strategy. boot.img from official ROM A1000LF_A412_01_05_130705_USER_DCC was unpacked with abootimg from Fedora repo. I added busybox for armv7l into initramfs/sbin and packed it again with the same tool. New boot.img was flashed into device with Flash Tools 3 (works on virtual machine with Win7) in Firmware Update mode with DA DL All With check sum option. Download mode did not work (there was errors in scatter file, __NODL_FAT partition exactly). Tablet was starting after flashing fow a few seconds. First boot logo was shown and then reboot again. Everything seems to work fine in case of flashing original boot.img. There might be some problems with Checksums or packing/unpacking initramfs (even if I create new boot.img without changes, tablet will not boot correctly). Do you have any ideas?
P.S. I didn't find suitable general thread for such kind of devices and tasks. Maybe you can suggest something.

Ulefone Armor X6. Tests for modification.

Ulefone Armor X6 - mt6580, 720x1280 5-inch, 2/16 ram/rom Android 9. There is a full rom, ulefone site (Support > Software Download). I use EU version.
Rom is with "-sign.img"s, system/build.prop: "ro.treble.enabled=true", "ro.expect.recovery_id=0xb4248...", boot-sign.img without ramdisk.
Used tools: Linux - IMG-SIGN Extractor (signimg2img), simg2img/img2simg, mount, SP Flash Tool, Carliv Image Kitchen, Windows - Miracle.
Tests for modification:
Fastoboot flashing unlock - ok.
SPFT - before connection - hold volume down - is possible to flash full rom. Single img - error.
Patching recovery-sign.img in magisk, recovery mode. Fastboot flash recovery magisk_patched.img = bootloop.
System-sign.img - unsign, unsparse, mount, remove bootanimation.zip and apps (Duo, YTMusic), edit build.prop: "ro.treble.enabled=false", remove "ro.expect.recovery_id=0xb4248...". Umount, sparse, flash system via fastboot. Fastboot say "ok". After start - stil stock system, without modification.
For the upper rom exist update ~400mb. Update, dump with Miracle - img's are unsigned.
System.img - unsparse, mount, remove bootanimation.zip and apps (Duo, YTMusic), edit build.prop: "ro.treble.enabled=false", remove "ro.expect.recovery_id=0xb4248...". Umount, sparse, flash system via Miracle = bootloop.
Also, I make a few ports of TWRP via Carliv Image Kitchen. Always bootloop (I never had trouble with a previous ports, for other phones, especially for this cpu)
Any other ideas? Or links to the right treads. This is my first rom with treble / "-sign.img"s.
Root
Tested on "GQ3085DH1_KSP2E_Ulefone_EEA_20200312_V01(Eu)" (Baseband version MOLY.WR8.W1449.MD.WG.MP.V237.4,2019/10/28 09:26, Kernel version 4.9.117 #2 Mon Oct 28 09:48:24 CST 2019)
Unlocking bootloader and disable verification (fastboot - min. version 1.8, vbmeta.img from stock rom):
fastboot flashing unlock
(volume up)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot reboot
On Android - Mtk-easy-su-v1.1.3.apk & MagiskManager-v7.5.1.apk.
Mtk-easy-su:
1. Run on boot
2. Magisk.v20.4.zip (assets-r22) - install
3. "Activate bootless root"
Restart phone. After start, wait to see "Success" on screen (bottom). Magisk work.
After root, if adb is needed:
adb shell
su
mount -o rw,remount /
Do you have made any progress?
Im sitting here on my armor x6 and have the same problems.
ahaff said:
Ulefone Armor X6 - mt6580, 720x1280 5-inch, 2/16 ram/rom Android 9. There is a full rom, ulefone site (Support > Software Download). I use EU version.
Rom is with "-sign.img"s, system/build.prop: "ro.treble.enabled=true", "ro.expect.recovery_id=0xb4248...", boot-sign.img without ramdisk.
Used tools: Linux - IMG-SIGN Extractor (signimg2img), simg2img/img2simg, mount, SP Flash Tool, Carliv Image Kitchen, Windows - Miracle.
Tests for modification:
Fastoboot flashing unlock - ok.
SPFT - before connection - hold volume down - is possible to flash full rom. Single img - error.
Patching recovery-sign.img in magisk, recovery mode. Fastboot flash recovery magisk_patched.img = bootloop.
System-sign.img - unsign, unsparse, mount, remove bootanimation.zip and apps (Duo, YTMusic), edit build.prop: "ro.treble.enabled=false", remove "ro.expect.recovery_id=0xb4248...". Umount, sparse, flash system via fastboot. Fastboot say "ok". After start - stil stock system, without modification.
For the upper rom exist update ~400mb. Update, dump with Miracle - img's are unsigned.
System.img - unsparse, mount, remove bootanimation.zip and apps (Duo, YTMusic), edit build.prop: "ro.treble.enabled=false", remove "ro.expect.recovery_id=0xb4248...". Umount, sparse, flash system via Miracle = bootloop.
Also, I make a few ports of TWRP via Carliv Image Kitchen. Always bootloop (I never had trouble with a previous ports, for other phones, especially for this cpu)
Any other ideas? Or links to the right treads. This is my first rom with treble / "-sign.img"s.
Click to expand...
Click to collapse
Yo, can you send me the port of TWRP for this phone please?

T865 Rooting with Android 12 - Bootloop and Error

Hello Everyone,
hopefully this is the right section for my question. If not please let me know.
I got a t865 with android 12 and want to root it. So i use the helping guide from Magisk (https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root).
What i did:
1) Unlocking the Bootloader (The OEM is grayed out) and i get a message every boot their is a open bootloader
2) Download with frijya the last stock image
3) Transfer it to the tablet
4) Download magisk and patching the file with recovery boot (no ramdisk)
5) Adb pull back to the laptop
6) Reboot to download mode and patch the magisk ap and the bl, cp and csc
And after the flashing, i cannot reboot to into the recovery. Everytime i get the info about the open bootloader and than the message: The tablet is not running samsung official software. ... (You can see the error on the image)
I can get back to the download mode and flashing the orignal stock image and be back were i started, but without rooting.
Can someone tell me how i can fix it?
Thx a lot in advanced
smartech0815
hi, don't worry about rebooting into recovery to wipe, if you did a clean install that's not the problem. i think the problem is the file patched with magisk. try to patch a new one leaving the flag on ramdisk and try the flash again
Thank you for your answer. You mean the check of the “Recovery Mode Option“ when I patch the file with magisk?
peppet said:
hi, don't worry about rebooting into recovery to wipe, if you did a clean install that's not the problem. i think the problem is the file patched with magisk. try to patch a new one leaving the flag on ramdisk and try the flash again
Click to expand...
Click to collapse
Thank you very much. It worked perfectly with leaving the flag on ramdisk. Just a little change, but it saved my day. Thanks.

Categories

Resources