I've tried different rom till now and had no problems. I decided to go for the flashable Oreo stock rom. The phone rebooted but IMEI and Baseband were unknown so i went back to Lineage 14.1.
Everything was working fine till the screen went off after the normal 1 minute. I went to wake up the device but the screen remained black with vertical red lines. I managed to boot into recovery:
i wiped dalvik/ cache and restarted but go no result. I tried lineage 16, lineage 15, resurrection remix but have always the same problem. I reinstalled custom firmware with Odin (only AP file) but i have the same
problem, this time the lines are white.
How can i solve it, any ideas?
Solved.
Flashed again all the files in original zip firmware BL. AP. CSC etc.
Related
I'm trying to flash my Galaxy Tab 4 10.1 3G (SM-T531) to the ROM Lineage 14.1 (lineage-14.1-20170309-0134-UNOFFICIAL-matisse3g).
But after flashing and rebooting my tablet get stuck on a screen with Samsung Logo and two messages on the top:
KERNEL IS NOT SEANDROID ENFORCING
Set Warranty Bit: Kernel
I've researched a lot and tried a lot of different things, but same result. If I go back to the stock firmware it works just fine.
The procedure a adopted was:
1- Reset to factory defaults on the stock firmware
2- Install TWRP (twrp-3.1.0-0-matisse) through Odin
3- Wipe Dalvik Cache, Cache, System and Data
4- Flash Lineage (lineage-14.1-20170309-0134-UNOFFICIAL-matisse3g)
5- Flash Stock GApps 7.1 (open_gapps-arm-7.1-stock-20170825)
6- Wipe Dalvik Cache
7- Reboot
My main intention on installing this new firmware is because the latest available firmware for my tablet on Brazil is 4.4.2 and I can install a lot of apps (including WhatsApp).
Does anyone can suggest or help me?
Thanks!
that message is normal...
I know... But my tablet is on this screen for almost 45 minutes... I believe that is not normal...
How could I solve it?
Anyone?
I had a similar issue trying to flash crdroid which is LOS 14 based. I wound up skipping step 6 and it worked. Could try redownloading the ROM though
Problem stills, any more tips?
After flashing the tablet stills on Samsung logo, but emits sounds when clicking on Volume Up, Volume Down, Home Button, Power Button... As it is responding normally but the screen keep stuck on Samsung logo.
Hi... any more tips?
Old but, anyone solved this? I tried Android 9 and 11, TWRP 3.6
I have one XT1570(china version with dual sim), falsh lineage 14.1( the latest nightly one) , gapps with twrp, after flash both of them, I click "reboot", then "system". it can't go inside the system, still show with twrp ui.
Now I tried few times, still the same.
But if click "reboot", then "bootloader", after screen goes up, press power button"start", it looks the initiation of android system, but it last for hours, still loading screen.
Any suggestion for this problem?
Thanks.
Los 14.1 is for Marschmallow, one(?) build is for Nougat.
Xt1570 - Lolipop, if you didn't flashed any upper stock rom. @tigerszheng
the original one is Android 7.0 Nougat™ NPH25.200-15, I think this is the previous rom, but when I do factory reset, it boots into twrp directly.
Since I originally want to flash the lineageos 14.1 for clark, so I download the lineage-14.1-20171106-nightly-clark-signed.zip, and the gapps*.zip,
that's the content I used to flash with twrp, but the problem seems that the rom doesn't work properly. or maybe because the xt1570 default to boot into the recovery(twrp)?
not sure about what's the problem of this?
Thanks.
Try AOSP ext. for 7 modem:
https://forum.xda-developers.com/moto-x-style/development/collection-random-projects-t3662970
@tigerszheng
I've had my note 4 for a little while now and I've been trying a lot of roms. Yesterday I tried flashing the flyme os 6 beta which I couldn't get to boot up. After that I flashed back the rom I was coming from and I noticed that twrp was unable to boot to recovery or system and went straight to stock recovery mode. When I manually started the rom up and tried to boot to twrp the screen went black for about a minute before booting into recovery. I've tried flashing back the factory images, reflashing twrp, different kernels, different BL and CP versions but nothing seems to work, I keep having this weird issue.
PS: I also can't turn it on when it's powered off. I have to remove the battery first before I can.
Has anyone else had this / knows how to get rid of this issue?
I was using RR N since its beginnings and wanted to go back to stock, so I flashed NPJS25.93 through fastboot and everything was just fine. However, an update notification kept popping up but I wasn't able to update the device (when trying to update, after download finished it restarted, but process would fail). Given the annoyance of the notification and pop up screen, I decided to go back to RR N... I flashed TWRP3.2.1 64 bits (because I was waiting for a more stable 64 bits Oreo RR) and tried to flash RR N for the meantime... For my surprise, after clearing system, dalvik, data and cache partitions, flashing process wouldn't finish... the progress bar would keep the animation, but the actual progress would stop at about 6mm of the end of the bar (I estimate 90-95 %). I left the device for lie an hour but nothing... So I reflashed stock N through fastboot and tried all over again... The same thing happened three times...
After failing to flash RR N I just decided to stay on stock N, but wanted root, so I reflashed TWRP and flashed ElementalX kernel to later flash super su... However, to my surprise, ever since flashing TWRP, whenever I reboot my device, it boots into recovery, and in order to reboot into the rom, I must reboot into bootloader first and then select either QCOM or BP TOOLS (I know bp tools is for fixing baseband, but don't know what qcom does). I have now flashed latest 64 bits RR O (15/09/18) cause I still can't flash RR N, but the rebooting into recovery persists...
Any ideas on how I could fix this?
I had flashed first 32 bits RR O but I tried to flashed magisk after the first boot and due to the rebooting into recovery issue, magisk never became functional in the rom (I would open the app and it would remain in the mask screen until a message of "Magisk stopped working" showed up). Something similar happened with SuperSu, but this time, I would never get it installed.
Heyy. Could you help me with this.
So I installed LineageOS 17.1 some weeks ago on my G928F Samsung Galaxy s6 edge+. And have a little problem. My phone is stuck in a bootloop. My phone shutdown because it didn't have battery left. I put the phone to charge and when I tried to power on the phone it just went in a bootloop. I tried several things to make my phone come back. The closest I get was that my boot animation started. But it just went off and again in the bootloop. I tried to wipe cache and dalvik cache. I tried to install boot.img file from the custom Rom zip file. Also I tried to change the boot animation but I can't see the /system/media folder. And I don't want to lose my data. Other detail, I don't want to dirty flash LineageOS 17.1 every time my phone shutdown because there's no battery left. Could you help me?(Sorry my bad English, I'm from Spain)
Nevermind
No problem. I already installed the stock Rom. Because some of important things that the stock Rom has the LineageOs 17.1 don't and that way I make sure that I won't have problems again.