So recently, i updated from CM12 (some nightly build) to CM13 following this guide titled: Update LG G2 with Android Marshmallow via CyanogenMod CM13 custom ROM [How to instal] ( I Can't link it because I'm a newbie apparently).
Now, if I try to boot my phone, the LG logo appears on the screen for about a half second then disappears, then the screen is very dully illuminated with absolutely nothing on the screen. As of right now, I can access TWRP (2.8.6.0) and do anything that TWRP allows me too.
In fact, when I installed the CM13.zip it said it installed successfully in the TWRP log window. I can also connect to my PC via MTP and add files to the phone (maybe add .img files that could solve this?). Is there anyway to fix this problem using the capabilities listed above?
EDIT: I also do not know which boot-loader I had. I was coming from android lollipop CM12, so I assumed it was bump.
Pritster5 said:
So recently, i updated from CM12 (some nightly build) to CM13 following this guide titled: Update LG G2 with Android Marshmallow via CyanogenMod CM13 custom ROM [How to instal] ( I Can't link it because I'm a newbie apparently).
Now, if I try to boot my phone, the LG logo appears on the screen for about a half second then disappears, then the screen is very dully illuminated with absolutely nothing on the screen. As of right now, I can access TWRP (2.8.6.0) and do anything that TWRP allows me too.
In fact, when I installed the CM13.zip it said it installed successfully in the TWRP log window. I can also connect to my PC via MTP and add files to the phone (maybe add .img files that could solve this?). Is there anyway to fix this problem using the capabilities listed above?
EDIT: I also do not know which boot-loader I had. I was coming from android lollipop CM12, so I assumed it was bump.
Click to expand...
Click to collapse
You might try reflashing CM12, but if all else fails you can go back to stock from Download mode and start fresh.
http://forum.xda-developers.com/showthread.php?t=2663369
Related
Hi!
So the situation is that I have Motorola Moto G (xt1039) with no OS and no custom recovery installed cause I fumbled couple of times trying to install CM on my phone. I had Android 5.1 installed before this mess. I can only get to the bootloader menu and to the phones stock recovery mode (the dead android screen). In bootloader menu it says that USB is connected so I think there are changes to save my phone(?)
So I tried to follow this guide: http://forum.xda-developers.com/showthread.php?t=2542219 but when I try to run mfastboot.exe, it says that I'm missing AdbWinApi.dll file. If I'm not completely wrong, the stock firmware restoring would be the right thing to do in this situation?
I would respect simple step-by-step guide because I'm pretty uncertain with these things. I trust to you guys, I would be so cheerful if I get my phone back to work.
Edit: Got it to work! Only had to move two .dll files to the firmware folder.
Hello everyone, I have a Oneplus One device with 5.0.2 lollipop. The phone is rooted with TWRP as custom recovery. I have used it to boot up Linux Mint and it worked perfectly, yet recently when I choose my image and choose readable usb or writable usb my phone simply reboots. I have tried to google a solution or find a thread yet noting seems to work. Please help, all I want is to be able to use drivedroid to boot images without the phone rebooting all the time. Thanks in advance.
Hello. My tablet ( V400 LG G Pad 7.0) is a little bit slower on original ROM (Android 5) so I tried to install a custom rom (CM). I rooted the tablet, and when I tried to install another .img file using a software, the tablet is remain in secure boot problem or something like that and the only way that bring the tablet back is restore using LG Software. Ok, so I tried to downgrade to Android Kit Kat (4.4 original ROM). I did everything using LGFlashTool2014 but the tablet is looping in LG logo, restarting over and over again and I have to go back at 5.0 original ROM. Can someone help me to install CM ? Any ideeas?
Even worse
AndreyStyle007 said:
Hello. My tablet ( V400 LG G Pad 7.0) is a little bit slower on original ROM (Android 5) so I tried to install a custom rom (CM). I rooted the tablet, and when I tried to install another .img file using a software, the tablet is remain in secure boot problem or something like that and the only way that bring the tablet back is restore using LG Software. Ok, so I tried to downgrade to Android Kit Kat (4.4 original ROM). I did everything using LGFlashTool2014 but the tablet is looping in LG logo, restarting over and over again and I have to go back at 5.0 original ROM. Can someone help me to install CM ? Any ideeas?
Click to expand...
Click to collapse
Same here expect that my LGFlashTool went unresponsive at 80%, stopped time counter, so I had to restart my v400 with power+volulme down. Since then v400 is unresponsive to any button combination or usb plug in, it only vibrates sometime. Device manager shows it a COM port. Do you have any idea what to do?
trewallier said:
Same here expect that my LGFlashTool went unresponsive at 80%, stopped time counter, so I had to restart my v400 with power+volulme down. Since then v400 is unresponsive to any button combination or usb plug in, it only vibrates sometime. Device manager shows it a COM port. Do you have any idea what to do?
Click to expand...
Click to collapse
Yep. I know how to fix this problem (I already had this before). If you still interest just leave me a pm so we can talk in private. Regards, Andrey
AndreyStyle007 said:
Yep. I know how to fix this problem (I already had this before). If you still interest just leave me a pm so we can talk in private. Regards, Andrey
Click to expand...
Click to collapse
Hello Andrey,
I have this problem now and don't know how to fix. Do you still remember the procedure.
Thanks in advance
Hello everyone!
I have a huge problem with smartphone mentioned in the thread title.
Once i wanted to install Cyanogen mod on it (yes, i rooted my device before flashing new room) and everything was well until the final reboot of the device.
Well, it is in bootloop. It only shows animated Cyanogen mod icon and nothing else.
I still have access to Droidboot that has an active "SD Download" option.
Is there any possible way to repair this device? Even with clean android?
I would apreciate any help whit this thread.
Well, noone seems to know solution to my problem, so i figured it out myself.
I am posting solution to this problem so if anyone in the future will have this issue, then he will have solution right here.
1. I downloaded stock android from asus website (Version 4.1.0 if i recall).
2. I copied the .RAW file to SD card and put it in smartphone
3. I booted up Droidboot and choose "SD Download"
4. I waited a while and after the instalation is complete, i booted up the system
There still was a bootloop but now with the asus logo. But then, i made another step:
5. I booted up Droidboot again and choose "Wipe/reset device"
After that, it worked like a charm
The stock android didn't have drivers for the Back, Home and menu touchbar so i made i think four system updates from android update software and it worked.
I hope i will help somone wit this thread.
Take care everyone
xGacutx said:
Hello everyone!
I have a huge problem with smartphone mentioned in the thread title.
Once i wanted to install Cyanogen mod on it (yes, i rooted my device before flashing new room) and everything was well until the final reboot of the device.
Well, it is in bootloop. It only shows animated Cyanogen mod icon and nothing else.
I still have access to Droidboot that has an active "SD Download" option.
Is there any possible way to repair this device? Even with clean android?
I would apreciate any help whit this thread.
Click to expand...
Click to collapse
I'm glad you sorted your problem, I'll move this to android general while its a guide
Regards
Sawdoctor
Hi guys,
from last one week I was experimenting new roms for my oneplus one. In order to install oreo rom, someone suggested to update twrp recovery to 3.2 wherein I was using 3.0.1. So I did!!
First i tried with official twrp app it showed successful but I was not able to boot into recovery mode. It got stuck in oneplus logo. But it was booting fine to os (oxygen os).
To fix this issue I found one post on XDA to run FIRSTAID.BAT file and I did.. Now, my phone is not booting at all. It was worst decision of my life to follow that monkey.
I feel my phone is soft bricked and not even getting detected in pc.
CAN SOMEONE PLEASE HELP!!!!!:crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:
rohitgothwal said:
Hi guys,
from last one week I was experimenting new roms for my oneplus one. In order to install oreo rom, someone suggested to update twrp recovery to 3.2 wherein I was using 3.0.1. So I did!!
First i tried with official twrp app it showed successful but I was not able to boot into recovery mode. It got stuck in oneplus logo. But it was booting fine to os (oxygen os).
To fix this issue I found one post on XDA to run FIRSTAID.BAT file and I did.. Now, my phone is not booting at all. It was worst decision of my life to follow that monkey.
I feel my phone is soft bricked and not even getting detected in pc.
CAN SOMEONE PLEASE HELP!!!!!:crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
Can you boot into fastboot or twrp?