My phone works normally but the screen is completely black while it is initializing, it is also completely black in the bootloader, to enter recovery I press down twice without any visual information and confirm. Within Recovery and the system the screen works normally
I have had this problem for many months and the device continues to function normally, without crashes or restarts
Does reflashing ROM not fix it?
5 star!
HOW TO ROOT?
msryzelb said:
HOW TO ROOT?
Click to expand...
Click to collapse
You flash twrp https://twrp.me/motorola/motorolamotog6.html use fastboot boot twrp.img
and then install magisk manager app https://magiskmanager.com/
Then on magisk manager app you download magisk zip and install it with twrp
Related
After downloading CM11 and GApps, I put it in my SD card and went into my recovery cwm9 by using an app. I got in and tried to flash my zips but I couldn't find them. Before I actually tried to flash them I did this first:
Wipe cache ( only required on first installation )
Wipe Dalcik cache ( only required on first installation )
Format /system and optionally /data ( Only necessary if coming from stock or a different ROM )
So when I rebooted I was greeted by getting stuck at the T-mobile boot splash.
I don't know how to get into recovery manually. I can't try to use download mode because I used fastboot. When I get into fastboot I tried using ADB to boot into recovery but device is not found when I'm in fastboot.
Please help me, I literally just got this phone and wanted to flash a custom rom because the LG stock is disgusting.
nemesis101x said:
After downloading CM11 and GApps, I put it in my SD card and went into my recovery cwm9 by using an app. I got in and tried to flash my zips but I couldn't find them. Before I actually tried to flash them I did this first:
Wipe cache ( only required on first installation )
Wipe Dalcik cache ( only required on first installation )
Format /system and optionally /data ( Only necessary if coming from stock or a different ROM )
So when I rebooted I was greeted by getting stuck at the T-mobile boot splash.
I don't know how to get into recovery manually. I can't try to use download mode because I used fastboot. When I get into fastboot I tried using ADB to boot into recovery but device is not found when I'm in fastboot.
Please help me, I literally just got this phone and wanted to flash a custom rom because the LG stock is disgusting.
Click to expand...
Click to collapse
See FAQ thread for getting into recovery.
[SIZE=+1]Q14: I've flashed a custom recovery but what are the key combos to get there?[/SIZE]
Power off the device
Press and hold Power + Volume down
When the LG logo appears on the screen, quickly release the Power button, still holding the Volume down button, and press and hold Power again until the "Factory Reset" screen appears. Don't worry, this won't reset the device.
Use the volume keys to navigate up and down and Power to select. Scroll down and select "Yes" and repeat once more. It may take up to 10 seconds for the device to boot to recovery.
I've now gotten into the recovery and installed both cyanogenmod and GApps. I've actually had to change the rom found here:
http://forum.xda-developers.com/lg-l90/development/rom-cyanogenmod-11-lg-l90-lg-d415-t2871371
I've had to change the updater script that contained "w7" to "w7ds" because it said my device wasn't w7 and that it was w7ds.
I've rebooted and now it's just stuck on the cyanogenmod boot screen.
What do?
nemesis101x said:
I've now gotten into the recovery and installed both cyanogenmod and GApps. I've actually had to change the rom found here:
http://forum.xda-developers.com/lg-l90/development/rom-cyanogenmod-11-lg-l90-lg-d415-t2871371
I've had to change the updater script that contained "w7" to "w7ds" because it said my device wasn't w7 and that it was w7ds.
I've rebooted and now it's just stuck on the cyanogenmod boot screen.
What do?
Click to expand...
Click to collapse
You've got an older recovery it seems. Download Philz-Touch from my thread, the link you posted, or get TWRP from this thread
Since you're having booting issues, use fastboot to flash the recovery.
Thing is when I'm in fastboot, ADB won't detect my device. I've only gotten it to detect my device once and that's when I was unlocking my bootloader. I don't know how to do it again.
So what do I do? BTW, thanks for helping me.
Edit: I formatted everything again and tried to reinstall the cyanogenmod and GApps. Seems like I just had to wait for the boot screen.
nemesis101x said:
Thing is when I'm in fastboot, ADB won't detect my device. I've only gotten it to detect my device once and that's when I was unlocking my bootloader. I don't know how to do it again.
So what do I do? BTW, thanks for helping me.
Click to expand...
Click to collapse
Put device in fastboot mode. ADB can't detect the device when it's in fastboot mode.
Type:
Code:
fastboot devices
You should see a listing similar to "adb devices" output.
Copy recovery image to the same folder fastboot is in. Then type:
Code:
fastboot flash recovery recovery.img
or
Code:
fastboot boot recovery.img
First one will only write the recovery image to the device. The second on will write the image to the device and should then boot the device to the recovery.
EDIT:
Yes, the first boot takes a couple minutes.
Seems I just had to wait for bootscreen.
How do I turn data on and off?
nemesis101x said:
Seems I just had to wait for bootscreen.
How do I turn data on and off?
Click to expand...
Click to collapse
easiest way to explain. Go to Settings and toggle Mobile Networks off/on.
There are several ways. I'm guessing you're new to CyanogenMod ROMs?
shinobisoft said:
easiest way to explain. Go to Settings and toggle Mobile Networks off/on.
Click to expand...
Click to collapse
Well, yeah, but a faster way. Like in LG in the notification bar there was a button that would turn data on and off. Does cyanogenmod have anything like that similarly?
nemesis101x said:
Well, yeah, but a faster way. Like in LG in the notification bar there was a button that would turn data on and off. Does cyanogenmod have anything like that similarly?
Click to expand...
Click to collapse
Quick Tiles. Pull down statusbar and press upper right corner image. There should be a tile already there for data
Sent from my LG-D415 using Tapatalk
shinobisoft said:
Quick Tiles. Pull down statusbar and press upper right corner image. There should be a tile already there for data
Sent from my LG-D415 using Tapatalk
Click to expand...
Click to collapse
Yeah, I got it.
Thank you for all your help!
About a month ago I noticed that I can't boot into recovery. However, flashing it (CWM or TWRP) with Flashify and rebooting helped although I couldn't boot into it manually (key combination or reboot menu).
Now, there's no way to enter recovery, even when I flash it with Flashify. Reboot to recovery reboots directly into the ROM, volume and power key does nothing, phone gets stuck on bootscreen. Otherwise, when booting normally, everything works fine. I just can't get into recovery. I'm currently using CM12.1 on D405n. Any ideas how to fix it? Thanks.
I installed CM 13 on my Droid Turbo after unlocking the bootloader with Sunshine. Everything was going fine until I tried to flash the Open Google Apps zip and I got into a loop with some of the Gapps crashing and I couldn't do anything. I researched this online and they (can't find where now) said to use TWRP to reset the device. So I went into "wipe" on TWRP and under "advanced wipe" I chose "System", "dalvik / art" and "cache" and rebooted the system. Now I've been stuck on the "WARNING BOOTLOADER UNLOCKED" screen for over an hour.
The other thing I have going against me is the power button does not work in anyway whatsoever (before and after I unlocked the bootloader).
Does anyone have any ideas?
You wiped the system partition, which means you erased your phone's operating system. This is why your phone is having trouble booting said operating system. Re-flash CM13 followed by your gapps (flash them sequentially. Don't boot the phone until both are flashed) and you should be fine.
I just went through this. Here's what worked for me, I'm on mobile and your milage may vary, you'll probably want to double check my work.
Get
Minimal adb and fast boot
Motorola turbo USB drivers
Twrp, cm13 20160517 if using nightly, gapps Pico, and in my case SuperSU
Hold power till off
Power up while holding power down
Google for the proper commands to accomplish the following
Fast boot twrp in place for recovery
Edit, boot into twrp.
Adb push cm13 zip
Adb push gapps Pico zip
Adb push SuperSU zip if needed
Edit,reboot back into recovery
Flash cm13, gapps Pico, SuperSU in that order
Reboot, wait for cm13 to load as long as it takes.
Edit, boot into twrp before adb push.
orangestrontium said:
I installed CM 13 on my Droid Turbo after unlocking the bootloader with Sunshine. Everything was going fine until I tried to flash the Open Google Apps zip and I got into a loop with some of the Gapps crashing and I couldn't do anything. I researched this online and they (can't find where now) said to use TWRP to reset the device. So I went into "wipe" on TWRP and under "advanced wipe" I chose "System", "dalvik / art" and "cache" and rebooted the system. Now I've been stuck on the "WARNING BOOTLOADER UNLOCKED" screen for over an hour.
The other thing I have going against me is the power button does not work in anyway whatsoever (before and after I unlocked the bootloader).
Does anyone have any ideas?
Click to expand...
Click to collapse
Since you have no power button this becomes tricky. You can try using adb but don't know if it will work as your phone sits. The only thing I can think of is let your phone die completely once it is off totally plug it in to charge while holding the down vol. Button this will bring you to bootloader where you can use adb commands to start recovery and go into twrp where you can reflash the system and gapps
Grynch13 said:
Since you have no power button this becomes tricky. You can try using adb but don't know if it will work as your phone sits. The only thing I can think of is let your phone die completely once it is off totally plug it in to charge while holding the down vol. Button this will bring you to bootloader where you can use adb commands to start recovery and go into twrp where you can reflash the system and gapps
Click to expand...
Click to collapse
This worked seamlessly, thanks!
I was in the same situation, and your advice got me to drain the battery and get back into recovery mode, so thanks for that! But, when I connected the USB cable, and tried ADB commands, it doesn't recognize my device (it has always recognized it in the past). Any advice? Thanks so much!
Hi, as the title says, i can't boot to twrp when the phone is powered off. It will ignore what i push and just boot into cyanogenmod.
It used to work at some point, also i can get to twrp if i restart via the twrp app.
I should probably just reflash it?
If I'd somehow lock me from the os while experimenting, i could still run twrp via fastboot in ?
kind regards!
nyanxo said:
Hi, as the title says, i can't boot to twrp when the phone is powered off. It will ignore what i push and just boot into cyanogenmod.
It used to work at some point, also i can get to twrp if i restart via the twrp app.
I should probably just reflash it?
If I'd somehow lock me from the os while experimenting, i could still run twrp via fastboot in ?
kind regards!
Click to expand...
Click to collapse
Please note power+ vol+ its to restart phone.
power+vol- to enter recovery.
so if already power down just press power+vol-
if in os press power+vol+ to reboot. when screen off power+ vol- to enter recovery
Hi, I have a Samsung Galaxy S10 SM-G973F. I unlocked the bootloader from the Download mode, then turned on the OEM unlock from the developer settings. I installed Magisk from github, created the patched firmware, then flashed all the files via Odin.
Now the S10 displays a warning that the bootloader has been unlocked, followed by the warning it's not running original samsung firmware, and an option to click the power button to continue.
The problem is, it does not boot into the OS. No matter which buttons I press, it does not boot. It stays on this screen for a while and reboots. I cannot initiate download or recovery mode. I cannot turn off the device. It's in a boot loop.
I used this firmware (I checked it's the correct one): https://samfw.com/firmware/SM-G973F/BGL/G973FXXSBFUF3
And followed this tutorial: https://yewtu.be/watch?v=V_IeG06skk4
I am not using TWRP. Thank you for all help!
oldsamsungdevice said:
The problem is, it does not boot into the OS. No matter which buttons I press, it does not boot. It stays on this screen for a while and reboots. I cannot initiate download or recovery mode. I cannot turn off the device. It's in a boot loop.
Click to expand...
Click to collapse
I install Magisk 23 on a Galaxy TAB S2 and had a boot loop. I reinstalled the boot.img and twrp then reinstalled LinageOS and uninstalled Magisk - Then it was fully recovered. I don't know if the boot.img was necessary.
oldsamsungdevice said:
Hi, I have a Samsung Galaxy S10 SM-G973F. I unlocked the bootloader from the Download mode, then turned on the OEM unlock from the developer settings. I installed Magisk from github, created the patched firmware, then flashed all the files via Odin.
Now the S10 displays a warning that the bootloader has been unlocked, followed by the warning it's not running original samsung firmware, and an option to click the power button to continue.
The problem is, it does not boot into the OS. No matter which buttons I press, it does not boot. It stays on this screen for a while and reboots. I cannot initiate download or recovery mode. I cannot turn off the device. It's in a boot loop.
I used this firmware (I checked it's the correct one): https://samfw.com/firmware/SM-G973F/BGL/G973FXXSBFUF3
And followed this tutorial: https://yewtu.be/watch?v=V_IeG06skk4
I am not using TWRP. Thank you for all help!
Click to expand...
Click to collapse
Hi. I remember on stock A10 when I 1st rooted ,, I had to 'boot to magisk' by doing the button combo for recovery
Code:
bixby, power, volume up then let go of power after the splash screen
But with oneui 3x I think you'd have to use a reboot app. Or ask in this thread
Cheers.