Please help! My phone shows a black screen after I try to boot into the system! - General Questions and Answers

Hello all,
After I wiped my system, I tried to install the latest Magisk (From the official MagiskManager website) and then, after I wiped again, and tried to reboot, my phone just showed a black screen it wouldn't even show the unlocked bootloader warning or the boot logo and when I charge it, the LED flashes constantly (I'm not sure what that means) therefore I have to boot back into the recovery or the bootloader as there is no system. I looked at the system files and there was nothing there although the Lineage OS flashed successfully.
Can anyone help me?
I'm not sure whether my phone is bricked or something as every other time I did it (2 times) there were no problems.
Version of Lineage OS I tried to install (lineage-14.1-20180108-nightly-athene-signed.zip)
Device: Motorola Moto G4 2016 (Athene)
Custom Recovery: TWRP 3.0.2.0
Magsik Version: Magisk-v15.3.zip
Thanks in advance!

You never wipe system unless you are flashing a rom. You pretty much removed the OS and then tried. To boot it.

zelendel said:
You never wipe system unless you are flashing a rom. You pretty much removed the OS and then tried. To boot it.
Click to expand...
Click to collapse
Yeah after I flashed Resurrection Remix, everything went back to normal, but thanks anyways.

Related

Bricked M4 when trying to install CM13... just booting into Fastboot (or Recovery)

Hi,
This is a new Mi4w Global and I got tired of waiting to Marshmallow to come OTA so decided to try CM13 and seem to have bricked it. Please help!
I flashed latest TWRP (also tried CyanogenMod recovery), then I did the factory reset, wipe cache, flashed the CM13 ROM but it won't boot. Always flashes the Mi logo and then straight into Fastboot. I can still access recovery by holding volume up and power, but no amount of flashing the ROM seems to work. I've tried latest Stable and Nightly CyanogenMod ROMs.
Did I miss a step? One thing I remember doing which might have been the problem is while I still had the original Xiaomi recovery I opted to boot onto System 2 or whatever. I think I flashed recovery straight afterwards. I wonder if that is the cause?
Anyway, please help me! Many thanks if you can help me get my phone working again.
Update: In case this helps anyone else, I did manage to find an original Mi4 recovery so I flashed it and the I also flashed the official MIUI developer build of Marshmallow. Now my phone is unbricked. I would still like to figure out how to root it and install CM13 sometime, but at least I have a working phone for now.
It's simple, you selected system 2 before installing cm13, and two installed rom in system 1. Be on system 1 and try again.
Prashanth Meesara: said:
It's simple, you selected system 2 before installing cm13, and two installed rom in system 1. Be on system 1 and try again.
Click to expand...
Click to collapse
OK thanks. What is system 2 then, is that the "sdcard" partition? I had looked in both TWRP and Cyan recovery for an option to change the boot partition but couldn't find it.

CM13 flashing problems. Phone keeps rebooting at CM splash screen after flash

Ok... slightly frustrated here.
Basic issue: Have flashed CM13 (Nightly 5.17.16) along with the latest Gapps. Upon reboot my phone will go to the Cyanagenmod splash screen, appear to load for several seconds, and then restart. It keeps doing this for at least 10 minutes until I turn it off. I have re-flashed a couple times after reloading the backup but no change.
Process I used: First of all my phone already has Android 6.0.1 firmware installed (not sure if that's an issue). I have TWRP setup as recovery and rooted with su 2.52 (and yes I verified the root prior to flashing). To flash I boot into recovery (obviously), factory reset, install cm13, clear dalvik, and repeat process with gapps. I've done this before with older CM's successfully but for some reason I can't get past the CM splash screen.
Any assistance is appreciated. If I have made a completely stupid error in my process or this exact issue is covered in another thread don't hesitate to point that out!!
Thank you in advance.
You need to be on 5.0 Lollipop. Custom recovery. Rooted. Then flash the ROM after you Wipe in Twrp

got stuck in a boot loop

I have been flashing cynogenmod and LineageOS since the Galaxy S2 so I thought I knew what I was doing but on this occasion I may have gotten ahead of myself.
I got the UK version of theMi Mix 3, waited 72 hours, unlocked it, flashed twrp and flashed [9.0][OFFICIAL]RR v7.0 & Pixel ExPie [GSI]
I do right ahead and flash gappsand magisk too and when I rebooted i just leep seeing the Mi logo and the unlock warning on repeat.
So i wiped my cache and system again, tried again without gapps and magisk but the same thing happened.
I then tried [non-GSI] Unofficial ArrowOS 9.x and [non-GSI] Unofficial Pixel Experience P but the same thing happened.
I think I might be missing something important about "China 9.1.10 Vendor"... all the instructions for each rom have something vague like that.
Do i perhaps have to go and get the factory rom for the chinese version and flash that before i flash my custom rom?
If so, can anyone point me to the location?
Also, is it then important not to wipe anything before flashing the custom rom on top?
still stuck
I thought I'd answered my own question and i found the link for the original chinese rom.
I flashed that and I can boot to it perfectly.
So i rebooted to recovery and quickly learnt that running miui restores the original recovery...
So i rebooted to fastboot, reflashed twrp, flashed miui then flashed arrow...
but i'm still stuck in a boot loop!
ChrisI984 said:
I thought I'd answered my own question and i found the link for the original chinese rom.
I flashed that and I can boot to it perfectly.
So i rebooted to recovery and quickly learnt that running miui restores the original recovery...
So i rebooted to fastboot, reflashed twrp, flashed miui then flashed arrow...
but i'm still stuck in a boot loop!
Click to expand...
Click to collapse
Format data by typing yes then flags magisk on custom roms

Stuck on LineageOS boot animation (first boot taking 1h+)

Need some help, I keep getting a infinite boot animation. I tried to install LineageOS (thread) on my G920F three times and let them all boot for about an hour without success.
This is the order of how I flashed it:
1. Wipe Davik, System, Data and Cache
2. Flash the LineageOS zip
3. Flash the Zerofltexx kernel img
4. First try flashed OpenGAPPS, second try flashed MindTheGAPPS and third try didn't flash GAPPS at all
5. Reboot and wait, after an hour still booting
Any idea's of what I'm doing wrong?
Fixed my issue!
Hi!
I had the same issue as you, followed the guides and installed TWRP through ODIN and flashed the OS through TWRP to boot it.
When I booted the device it just got stuck indefinitely on the loading animation (the Lineageos loading logo in my case).
Since you and some others had the same issue as me I assumed it was something to do with a new version of some software.
I resolved the issue by installing an older version of TWRP through ODIN,
I installed the TWRP version 3.2.3.
And then I flashed the same ROM with the GAPPS again.
After the ROM and GAPPS I also flashed MAGISK aswell from the magiskmanager website.
Download the MAGISK Zip.
After I flashed the ROM, GAPPS and MAGISK through the TWRP 3.2.3 it booted as intended.
Hope this works for you aswell!
how long did it take to boot
First Boot needs longer...up to 15 minutes is possible.
solonf
speedson
i have same probleme wtih my samsungs6 g920f i wiil try it ...hope it work ....
Remove the TWRP from the phone via the advance key in TWRP. I had tried several ROMs and Gapps only to get stuck on the boot screen then back to the TWRP screen. Removing the app made my new rom boot in less than 10 seconds.
If you can give us exactly the steps you follow
Lineageos 17 boot animation stuck
krimnian said:
If you can give us exactly the steps you follow
Click to expand...
Click to collapse
Steps (I have followed the instructions to the letter)
Wiped all partitions (advanced wipe)
formatted DATA partition
rebooted back into recovery
installed Lineage 17 and Gapps
Rebooted to system and left it all day, still stuck on boot animation
Tried again without gapps same results
Tried other roms they work, AOSP showing no encryption which works fine
What am I doing wrong? Do I have to flash different kernel? TWRP 3.3.1 installed.
Im using G920L it booting to long then just go to twrp anyhelp?
Helpful
crmcc said:
Remove the TWRP from the phone via the advance key in TWRP. I had tried several ROMs and Gapps only to get stuck on the boot screen then back to the TWRP screen. Removing the app made my new rom boot in less than 10 seconds.
Click to expand...
Click to collapse
this was extremely helpful as soon as i unchecked installing with twrp it worked immediately.
crmcc said:
Remove the TWRP from the phone via the advance key in TWRP. I had tried several ROMs and Gapps only to get stuck on the boot screen then back to the TWRP screen. Removing the app made my new rom boot in less than 10 seconds.
Click to expand...
Click to collapse
Can you explain the process a little?I have flashed lineage os 18.1 in moto g5 plus , but it's stuck on lineage booting animation.
rog__ said:
Can you explain the process a little?I have flashed lineage os 18.1 in moto g5 plus , but it's stuck on lineage booting animation.
Click to expand...
Click to collapse
For reference, formatting data after install seems to often be the solution when flashing a new OS to a Moto G5 Plus.
gamemaster2030 said:
Need some help, I keep getting a infinite boot animation. I tried to install LineageOS (thread) on my G920F three times and let them all boot for about an hour without success.
This is the order of how I flashed it:
1. Wipe Davik, System, Data and Cache
2. Flash the LineageOS zip
3. Flash the Zerofltexx kernel img
4. First try flashed OpenGAPPS, second try flashed MindTheGAPPS and third try didn't flash GAPPS at all
5. Reboot and wait, after an hour still booting
Any idea's of what I'm doing wrong?
Click to expand...
Click to collapse
These steps solved my issue. thanks

Phone stuck in a bootloop! (Lineage os 17.1 installed)

Hi! I have lineage os 17.1 by ivanmeler installed on my S7 flat , I was using opera browser to download a 1GB file, As soon as the download started my phone shut down and got stuck in a bootloop, I booted to the TWRP recovery, And tried to restore a backup that I had done before, but I got an error that says (extractTar error 255), Then I decided to just wipe data and system and flash the rom again, the rom gets flashed, I reboot into system and the phone gets stuck in a bootloop again, what is going on withmy phone, Please someone help!
Thanks in advance.
zariouh said:
Hi! I have lineage os 17.1 by ivanmeler installed on my S7 flat , I was using opera browser to download a 1GB file, As soon as the download started my phone shut down and got stuck in a bootloop, I booted to the TWRP recovery, And tried to restore a backup that I had done before, but I got an error that says (extractTar error 255), Then I decided to just wipe data and system and flash the rom again, the rom gets flashed, I reboot into system and the phone gets stuck in a bootloop again, what is going on withmy phone, Please someone help!
Thanks in advance.
Click to expand...
Click to collapse
Wipe cache before reboot.
cooltt said:
Wipe cache before reboot.
Click to expand...
Click to collapse
I have already tried wipping cache and dalvik cache, I even wiped system and data and installed the ROM again but the phone's still stuck in a bootloop.
Now I'm about to flash through Odin back to stock and see if the phone turns on.
Hm... While I was downloading the stock firmware to flash the phone, I thought of checking the data folder inside the TWRP recovery, And turns out The data is still there, It never got wiped, that's why the phone is stuck in a bootloop, Now what could be preventing the data from getting wipped? I don't get any errors when I wipe the data partition, And this is also strange because usually you get a bootloop when you flash some kind of zip file through the recovery (mods or something like that), but I was just using the browser to download a file , And phone suddenly shutdown and got stuck in a bootloop, Could someone pls help me figure out what's causing the problem
zariouh said:
Hm... While I was downloading the stock firmware to flash the phone, I thought of checking the data folder inside the TWRP recovery, And turns out The data is still there, It never got wipped, that's why the phone is stuck in a bootloop, Now what could be preventing the data from getting wipped? I don't get any errors when I wipe the data partition, And this is also strange because usually you get a bootloop when you flash some kind of zip file through the recovery (mods or something like that), but I was just using the browser to download a file , And phone suddenly shutdown and got stuck in a bootloop, Could someone pls help me figure out what's causing the problem
Click to expand...
Click to collapse
That ROM is in BETA mode, which means it could be lost of things. Your question should be asked on the LOS 17 thread itself but when a ROM is in BETA mode it's very difficult to tell what the problem is. Ask the developer @ivanmeler he might be kind enough to answer you.
Help Me too !!!!
No Lineage based android Q roms booting on my S7 too. I restored stock but then also bootloop.
Pls Help
I'll try to help
Ayushskull said:
No Lineage based android Q roms booting on my S7 too. I restored stock but then also bootloop.
Pls Help
Click to expand...
Click to collapse
Hi! Can you describe the steps that you tried to revert back to stock? Did you use the repair firmware (5 files) or one file firmware?
zariouh said:
Hi! Can you describe the steps that you tried to revert back to stock? Did you use the repair firmware (5 files) or one file firmware?
Click to expand...
Click to collapse
Bro I used these files AP, BL, CP, CSC
Also when I try to boot rom (Aicp) with Cronos Kernel which is for Oneui 2.0 my phone somehow booted but wifi is not working. So can you tell me exact problem as a OneUI based kernel is booting AOSP while when I use morokernel no AOSP based rom boots
Ayushskull said:
No Lineage based android Q roms booting on my S7 too. I restored stock but then also bootloop.
Pls Help
Click to expand...
Click to collapse
Ayushskull said:
Bro I used these files AP, BL, CP, CSC
Also when I try to boot rom (Aicp) with Cronos Kernel which is for Oneui 2.0 my phone somehow booted but wifi is not working. So can you tell me exact problem as a OneUI based kernel is booting AOSP while when I use morokernel no AOSP based rom boots
Click to expand...
Click to collapse
Sorry but I don't have enough knowledge to help with kernels, Now from what I understand is that you tried flashing stock ROM and your phone got stuck in a bootloop, Right? And just to confirm could you mention the model of your s7?
Ayushskull said:
Bro I used these files AP, BL, CP, CSC
Also when I try to boot rom (Aicp) with Cronos Kernel which is for Oneui 2.0 my phone somehow booted but wifi is not working. So can you tell me exact problem as a OneUI based kernel is booting AOSP while when I use morokernel no AOSP based rom boots
Click to expand...
Click to collapse
Flashing stock rom will restore stock kernal. Firmware must be correct for device and region.
Bootloop after Odin Flash.
1. After flash boot into stock recovery
2. How to>>> In this sequence hold volume down+home+power. As soon as phone goes off move finger to volume up while still holding home and power. It may take several attempts as you have to time it just right when the screen goes black.
3. Once in stock recovery choose wipe data/ factory reset. Then choose reboot device
4. Can take 5-10 minutes on first boot. Updating and erasing screens are normal during this process as well as rebooting. Just leave it finish.
If this does not work Reflash stock with Odin but this time uncheck "auto reboot" in Odin options before you start.
Once Flash finish, disconnect from pc and follow 1-4 as above.
Kernel Problem
Pls help as I figured out that all the kernels after v3.18.140.5 are not booting on my phone. Can someone help me with this.
Model No: SM-G930FD
Device: Galaxy S7 Flat
BL: 8 (Latest)
File System: ext4
I have already restored stock many times and formatted my device many times. I used firmware from samfw to go to stock.
That is why no Aosp was booting on my phone
Pls Help

Categories

Resources