I guess you mean the download mode? This doesn't have anything to do with LineageOS.
It could be the same problem in your case.I'm having a similar issue. I can boot into download mode only. When I try to boot into recovery, it shows the TWRP logo for a few seconds and the device reboots. Lineage gets stuck on the loading screen forever. I tried to go back to stock through Odin and repartition with an appropriate PIT file but I had no success, it tries to boot into Lineage. I also tried the NAND erase option on Odin, but it always fails and doesn't continue.
Yes, you can find everything in the first post,
I would retry it.can't download it from androidfilehostany advance download links avaliable maybe ? :.(
You have to reboot into download mode, I guess you try to flash TWRP?when i try to use odin when android running i see ID:COm is com4. But when i am in adb mode ID:com is empty.
And when i try to load the md5 file odin gets not responding. What am i missing ?
isnt the download mode called adb when you boot with power and volume down ?You have to reboot into download mode, I guess you try to flash TWRP?
I guess you mean thea odin mode / download mode.isnt the download mode called adb when you boot with power and volume down ?
<ID:0/004> Odin engine v(ID:3.1203)..I guess you mean thea odin mode / download mode.
ADB is the android debuggin bridge, this is enabled when you allow USB-Debugging.
Download the TWRP "img.tar" and load it under AP.
Problem solved?
Yes , all problems was because i wasn't experienced enough.
I did the exact same thing when i realized there were several other sizes. And got it to work and it is working very nice. Turn off and on faster than before. Thank you very much.I recently installed this version of Lineage on my GT-N8010 (was running stock 4.4.1). Although I'd looked at doing this for some time (years - started looking with a much earlier version of Lineage), I hadn't actually needed to upgrade. I was forced into trying by not being able to use a couple of apps I wanted. It was very straightforward except I wasn't quite sure where to save the image files on internal storage, but it turned out it didn't matter much.
When loading GApps, I tried several versions - micro, nano and then pico - but only pico would fit. I didn't find any info about expanding available space.
Yes , all problems was because i wasn't experienced enough.
But when i try to install gapps, i am getting Insufficient strage space in system partition. Is there a way to make some space on the system partition ?
Yes, there is only space for pico gapps on our system partition (1.3GB).When loading GApps, I tried several versions - micro, nano and then pico - but only pico would fit. I didn't find any info about expanding available space.
Pico seems to offer all I need, thanks. I guess a tutorial about expanding the system partition might be useful for someone but I don't think I'll be needing it anytime soon.Yes, there is only space for pico gapps on our system partition (1.3GB).
It is possible to expand the system partition if you resize data and move all partitions between.
I did this on all my devices to be able to install GSI's. (Most of them need up to 2 GB).
I you really need this, I could write a tutorial, but I still recommend pico gapps because bigger packages will slow the system down.
yeah u gotta install this kernel that @html6405 madeHi all
Having problems trying to flash Magisk 26.1. No matter if I flash from TWRP or if I patch the boot.img, and then flash boot.img, no success.
Is there any problem with Magisk and this ROM?
Thank you
oh, i think there was an older version in the thread for gt-n8020 but the headphone jack wasnt workingThe kernel suggested seems not compatible with my device (GT.N8020)
Any suggestion?
Thanks!
oh, i think there was an older version in the thread for gt-n8020 but the headphone jack wasnt working
if you dont want a new kernel you could install magisk 24.1
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/