Hi
I have installed TWRP, and through that recovery, i have flashed the device with cyanogenmod CM11 (cm-11-20140504-SNAPSHOT-M6-falcon.zip)
After installing it, when the telephone starts, the screen shows a white line on top of the screen and sudenly the screen starts to flash, and loops again
To make it worst, if i restart and enter in the bootloader (power and vol down) it doesnt go into the bootloader and tries to start again
Any suggestion?
Thanks
Issue solved. I managed to get into the bootloader and flashed with another version
Looks like graphics didnt work. The phone was starting and working but nothing was displayed in the screen
javixeneize said:
Issue solved. I managed to get into the bootloader and flashed with another version
Looks like graphics didnt work. The phone was starting and working but nothing was displayed in the screen
Click to expand...
Click to collapse
Questions about the XT1032 Moto G should be ask here.
http://forum.xda-developers.com/moto-g/help
not General
Related
Hi,
I recently rooted my htc vivid and i tried to flash a rom. However, the rom didnt work and my phone isnt working. The phone's bottom touch-buttons vibrate when touched, but the screen remains off no matter what i do. What's wrong with it?
EDIT: I got it to boot, however, its stuck on booting, the boot logo just keeps on popping up. What should I do?
any luck?
sounds like you need to try and flash the rom again. this may or may not be a know issue with the rom. check the thread where you got the rom. I had to flash twice with the same rom the last time i did it (unrelated device)
May have to hold the buttons in a specific sequence to get back to the debug mode.
also have a look through this thread:
http://forum.xda-developers.com/showthread.php?t=1433149&page=2
I tried unlocking the bootloader and it said unlocked, but when it booted back up it did the whole system update thing, and then it kept force closing the phone app. Well, I held down the power button for ~15 seconds, and now when it boots back up, it gets to the brown part of the boot animation, (farm type motorola) and goes to a black screen.
Going into the bootloader and selecting factory does the same thing.
Please help?
(US GSM 16GB version XT1034)
Flashed CWM, wiped data/cache and it got past the screen with the brown, but now it just boots to the black screen after the water drop part.
Try to restore stock firmware...look here: http://forum.xda-developers.com/showthread.php?t=2542219&highlight=failed
Pablitooos said:
Try to restore stock firmware...look here: http://forum.xda-developers.com/showthread.php?t=2542219&highlight=failed
Click to expand...
Click to collapse
Thank you so much. It's working. At first I flashed the XT1032 because I thought AWS was the Global version, but I flashed the correct firmware just now. Again, thanks.
landonh12 said:
I tried unlocking the bootloader and it said unlocked, but when it booted back up it did the whole system update thing, and then it kept force closing the phone app. Well, I held down the power button for ~15 seconds, and now when it boots back up, it gets to the brown part of the boot animation, (farm type motorola) and goes to a black screen.
Going into the bootloader and selecting factory does the same thing.
Please help?
(US GSM 16GB version XT1034)
Flashed CWM, wiped data/cache and it got past the screen with the brown, but now it just boots to the black screen after the water drop part.
Click to expand...
Click to collapse
If you don't find a solution, you could try doing the same to about 2,000 more moto G's and build a small house..
So, my phone was stuck in No Command bootloop. I’ve done the power+volume up and had cleared cache and even done a factory reset. Those did nothing and my phone is still in stuck No Command loop. I think I’ve made it even worse by trying to Flash Recovery and Reboot options in the Nexus Tool Kit because my phone won’t even get to the No Command screen. It just turns on and turns off after Google comes on. Currently it stuck in that loop and only stops once the battery is completely drained. Also i have tried using power + volume up and it doesn't help . Please help
vigneshkumargv said:
So, my phone was stuck in No Command bootloop. I’ve done the power+volume up and had cleared cache and even done a factory reset. Those did nothing and my phone is still in stuck No Command loop. I think I’ve made it even worse by trying to Flash Recovery and Reboot options in the Nexus Tool Kit because my phone won’t even get to the No Command screen. It just turns on and turns off after Google comes on. Currently it stuck in that loop and only stops once the battery is completely drained. Also i have tried using power + volume up and it doesn't help . Please help
Click to expand...
Click to collapse
As you've upgraded to lollipop ?? You came from a custom rom ?? Enters the bootloader?
vigneshkumargv said:
So, my phone was stuck in No Command bootloop. I’ve done the power+volume up and had cleared cache and even done a factory reset. Those did nothing and my phone is still in stuck No Command loop. I think I’ve made it even worse by trying to Flash Recovery and Reboot options in the Nexus Tool Kit because my phone won’t even get to the No Command screen. It just turns on and turns off after Google comes on. Currently it stuck in that loop and only stops once the battery is completely drained. Also i have tried using power + volume up and it doesn't help . Please help
Click to expand...
Click to collapse
with wugfresh nexus root toolkit click on the button "soft-bricked"(flash stock + unroot) or something like that to restore the phone. After that try another time to unlock and root with a custom recovery (for example twrp).
When nexus root toolkit installing the original lollipop rom, look the "dos window" to see if the software shows errors, because sometimes the process ends without a real restore.
If you have other problems, please post a screenshot.
Fenix46 said:
As you've upgraded to lollipop ?? You came from a custom rom ?? Enters the bootloader?
Click to expand...
Click to collapse
Yes I was using a custom rom, but I not even reached the step where a was supposed to use the rom, I was steel still cleaning the divece.
Here is a photo from the screen I'm stuck in:
eeee.... I'll find a wint to send the photo to this forum ^^" wait
After installing blisspop (or I don't really remember), I realized that WiFi wasn't working and neither was bluetooth so I decided to flash Extended Stock Kernel kernel, first with flashing the boot, then flashing the zip from recovery mode and even after that, the result was the same. It didn't work. Later on I went to the Phantom kernel's page and flashed that without checking that the kernel was meant for 4.4 and it bricked my device. Now, whenever the phone starts, it shows the Phantom kernel boot at start with its logo without any led light appearing below and due to that I'm unable to go into either flashmode or fastboot. It keeps restarting the Phantom boot at start and doesn't go any further. Please help!
EDIT: A more detailed version that I wrote a few months ago to the kernel's developer.
-
Previously I had my Xperia L reset on stock ftp then flashed the Extended Stock Kernel on it. Since the wifi wasn't working, I tried to download R17 and flashed it through CWM and now the phone keeps restarting on the Phantom Logo. It shows the logo, waits for about 10 seconds then restarts and the same keeps repeating. I saw it was for Kitkat but then too I insisted on installing. I can't access neither bootloader nor recovery mode. The light which comes when the Phantom Logo pops doesn't appear either. Can you help me please? Anything would be greatly appreciated. I know I did a stupid thing but I really don't want to give up on this device.
-
Xephor_EX said:
After installing blisspop (or I don't really remember), I realized that WiFi wasn't working and neither was bluetooth so I decided to flash Extended Stock Kernel kernel, first with flashing the boot, then flashing the zip from recovery mode and even after that, the result was the same. It didn't work. Later on I went to the Phantom kernel's page and flashed that without checking that the kernel was meant for 4.4 and it bricked my device. Now, whenever the phone starts, it shows the Phantom kernel boot at start with its logo without any led light appearing below and due to that I'm unable to go into either flashmode or fastboot. It keeps restarting the Phantom boot at start and doesn't go any further. Please help!
EDIT: A more detailed version that I wrote a few months ago to the kernel's developer.
-
Previously I had my Xperia L reset on stock ftp then flashed the Extended Stock Kernel on it. Since the wifi wasn't working, I tried to download R17 and flashed it through CWM and now the phone keeps restarting on the Phantom Logo. It shows the logo, waits for about 10 seconds then restarts and the same keeps repeating. I saw it was for Kitkat but then too I insisted on installing. I can't access neither bootloader nor recovery mode. The light which comes when the Phantom Logo pops doesn't appear either. Can you help me please? Anything would be greatly appreciated. I know I did a stupid thing but I really don't want to give up on this device.
-
Click to expand...
Click to collapse
yea.... output battery... reinput it.... DONT TOUCH POWERBUTTON.... holf vol - and connevt to pc
Sent from my Xperia T using XDA Free mobile app
SdtBarbarossa said:
yea.... output battery... reinput it.... DONT TOUCH POWERBUTTON.... holf vol - and connevt to pc
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
-
It worked, I flashed the generic ftf and everything's okay. Thank you so much!
-
help needed !!
I have a KFHD7(tate) and had been running CM12.1 for a while with only an occasional update using the nightly builds, I only updated occasionally as the unit would not always turn on at the first attempt and would stick at the CM boot logo, after switching it off and back on the unit would run quite smoothly, however none of the updates seemed to cure the problem.
I noticed that there was a new release 'cm-13.0-20160218-UNOFFICIAL-tate' which I flashed via TWRP along with 'open_gapps-arm-6.0-stock-20160301', these were flashed at the same time.
after a reboot the KFHD7 worked fine with no apparent problems, I then downloaded one of the dark themes,(not sure exact one) and this seemed ok at first, I entered the settings screen and only a few words and graphics were visible!
I rebooted back into TWRP recovery and performed a factory reset from within TWRP ... big mistake, now the unit only boots to the blue TWRP boot screen and blinks off after a few seconds it is stuck in a loop and I dont know how to recover it, I have tried the usual combinations of holding the power and vol buttons but still comes on the same .. any suggestions would be appreciated (dumbed down solutions please as not that techy, but can muddle through if step by step instructions)
Hello,
Welcome to XDA.
Try posting your issue in the thread linked below that you got your ROM from.
http://forum.xda-developers.com/kindle-fire-hd/7-development/rom-marshmallow-t3315075
The experts there may be able to help. Good luck.