Hello,
I have a RAZR HD XT925 on 4.1.2 GSM.
I was able to unlock the bootloader through the Motorola website, and Root the device using motochopper.
I have tried 3 different custom recoveries:
recovery-clockwork-6.0.4.4-xt925
recovery-clockwork-touch-6.0.4.4-xt925
philz_touch_6.43.8-moto_msm8960
TWRP-2.7.0.0-moto_msm8960-xhdpi
The flashing results always report successful. But when I attempt to boot up the phone in recovery mode, it always goes to the screen with the android character laying on his back with his stomach compartment open and a red triangle with an exclamation point hovering over.
I have to wait about 30 seconds until the phone reboots itself to normal mode and everything works fine.
Any help is greatly appreciated.
Thanks!
you can use twrp 2.6.0.0
Related
Using Wug Fresh Nexus Toolkit v1.8.2
This is (was) a new Nexus 7 WiFi Tablet running Kitkat 4.4.2 KOT49H. Trouble started when having Unlocked the device I used Root option next. But just hung... 3hrs Boot img message, restarted the whole process couple of times each time hung on same message. On one of these at the point of using Root rung as usual unplugged device re plugged went into TWRP and hung, unplugged message said Rooted. Though had really failed.
Thought use Flash Stock + Unroot Device is on /Normal... followed instructions. Device now stuck in Bootloader Mode, Fastboot, bla,bla Unlocked.
(*)Stuck all I could do was Power Off, Recovery (did nothing but start bootloader), Restart bootloader and START which gave me black screen with Google across it and Unlocked padlock at bottom.
All other Toolkit options returned ADB not found
So after a number of other tries using Flash Stock + Unroot that gave me the same result as above (*) concluded the only option was to use the Forced Flash Stock + Unroot.
All looked good but now Only have the black screen with Google across it and Unlocked padlock at bottom. Can switch OFF and ON but can go no where else.... any helpful suggestions please?
Attached two screen grabs of what appeared to be successful Forced Flash Stock + Unroot.View attachment 2708842
View attachment 2708843
I have looked at multiple guides on this and other sites, googled and tried stuff and I cannot resolve this problem. Hopefully I am posting in the right place.
I took the jump and unlocked the bootloader on my Moto G first generation, XT1034 successfully. I flashed TWRP 2.8.60.xt1034.zip with adb and this was successful. Then I flashed Super SU 4.6 Update and that was successful. I got into trouble I guess when I tried to flash Cyanogenmod 12.1 nightly. I used TWRP to flash via install. The flash had an error, which unfortunately I didn't write down. I believe it was something to do with a partition. However, it looked like the flash failed. At this point and for hours I have been trying to fix the "Warning Bootloader Unlocked Loop I am stuck in.
I have been able to get into the phone and flash via adb commands. I've tried several commands suggest to fix this that I have found in forums. I have tried flashing several recoveries including an older TWRP per the method in this thread, a clockworkmod - and the original 2.8.6.0.xt1034. When I get into the phone bootloader which is available, I have not been able to access any options in recovery. Pushing the power button on recovery leads to a blank screen sometimes followed by a recovery starting or a Motorola Logo starting up and a couple times a recovery. TWRP has started a couple times, but never gets past the intro screen, where it locks up. clockworkmod (clockworkmod-6.0.4.7-falcon.img started once after flashing through adb and gave me flash options. I tried to sideload, didn't understand, went back and the recovery locked up. These recoveries no longer load at all.
Through all of this the "Warning Bootloader Unlocked" logo screen comes up after plugging into the computer (Windows 8.1).
Example, I open the phone bootloader by waiting for the phone screen to go from the "Warning Bootloader Unlocked" screen to blank - it cycles from logo to blank. If I'm quick the phone and hard boot the phone will boot into bootloader. I connect to the laptop through USB. When I toggle to recovery and hit the power button the screen goes blank, the Motorola Logo pops up, goes blank and then the "Warning Bootloader Unlocked" appears. The Laptop then seems to connect and disconnect as the Warning screen comes on and turns off.
The factory selection just goes to a blank screen.
I would really appreciate some advice on how to get the phone back to a state in which I can work with it and try again. It is very difficult wading through all of the information out there. I've learned a lot through this issue, but can't take it any further.
Thanks, Jeff
Solved - Stuck in "Warning Bootloader Is Unlocked" Loop
This resolution took many hours to figure out, but I finally got there with this guide - http://forum.xda-developers.com/showthread.php?t=2542219, this thread - http://forum.xda-developers.com/showthread.php?p=54855457#post54855457 and this thread - http://forum.xda-developers.com/gen...e-firmware-t3042687/post59139823#post59139823.
I tried RSD Lite on different computers and USB cables I could not get the device recognized. So I ended up with the MfastbootV2 method to reload stock firmware, which I found on the firmware thread above - this was big, as my phone is with Wind Mobile in Canada and the link is the right one. The only thing I picked up from a different website was to use a computer with USB 2 ports. This is what I did, but I don't know one way or the other if USB 2 was needed. .
Can't thank you hard working guys enough for the time you take to put these threads together. I'm back up and running. As a bonus, after a big clean up in the process, my phone is running fast again.
Thanks everyone.
Hi, people. I hope you can help me.
My problem is that my rooted Nexus 7 (2012) with 3G and kitkat Stock Android suddenly turned into so called brick state. Only Google logo was appearing during the boot, and that will last forever. Then, just for interest, I tried to enter into the recovery mode (Clockwork Recovery v6.0.4.3 for tilapia), but the device did not go into it. The logo of CWM appeared in the middle of the screen and then the device reboots automatically showing the Google logo screen for several seconds and then going into recovery mode with the CWM logo appearing on the centre of the screen, and then reboot again. This recovery bootloop lasts forever or till the battery runs out. I tried to use
Code:
adb devices
and
Code:
fastboot devices
on my nexus 4, everythings works fine (meaning drivers are installed correclty). But
Code:
fastboot devices
for the nexus 7 outputs into
Code:
- waiting for device -
I tried to force the battery to run out and then tried to go into fastboot, but that did not help, the recovery bootloop appeared on its own again. Please, help me, I don't know what to do.
EDIT. I tried to pull out the battery for a half day (disconnect battery connectors) in hope that this will somehow reset the boot options, but this did not help.
Any thoughts?
Also, if the thread is not in the appropriate branch of the forum, please, let me know, probably at correct location I will find more help. Thanks.
EDIT2. I solved the problem by trying to enter the bootloader mode via adb. But to enter bootloader required a liitle bit of humoristic approach. I was pressing UP then ENTER to enter fastboot mode via termianl (#adb reboot-bootloader) for 5 to 10 minutes. When I managed to enter the fastboot, I flashed TWRP recovery for tilapia and the latest 5.1 Lopllipop But it seems there is a bug in the stock recovery because it does not work with NEXUS 7, the last two updates of Kitkat and Lollipop required to flash custom recovery, because the stock one did the bootloop on either Google logo or the animation of "beautiful" circles.
Thanks for reading, hope this might help someone.
from danik
Hi,
Glad to hear it solved
Good Luck!
Thread Closed.
Just wanting some advice (if any) to a white line issue I'm having with this tablet. I bought this tablet with Lollipop 5.0.1 already installed. I managed to get it downgraded, rooted, and currently have TWRP installed as well as CM12.1 nightly. The problem I have is that as soon as I install ANY custom recovery (TWRP or CWM recovery) it boots normally at first giving me the LG logo. Then, instead of getting the AT&T logo (or the CM custom boot animation), it gives me a series of white lines spamming from top to bottom of the screen. I know for a fact it has to be software related as when I return to stock KK everything boots fine, giving me the LG logo followed by the AT&T logo. I did NOT use the ADB method. Instead I downgraded using the LG Flash Tool, and a test KDZ file, which allowed me to install Flashify, then TWRP. My problem ONLY begins once I install ANY custom recovery. This process did not unlock my bootloader, however. Could this be my culprit, or would it be something else? Any help is greatly appreciated, and thanks in advance for any help/tips. More information is completely available upon request.
P.S. The white lines eventually disappear when the screen goes to sleep on it's own. I can then press the power button to wake the device which gives me the lock screen as normal. I just want to know if I can get the boot animation working. Everything else works fine.
You found cwm?
Hey guys, I've got a Kyocera Brigadier and I decided to change the runtime from Dalvik to ART. Now the phone is stuck on loadscreen and I don't know how to fix it. The phone is rooted using the KingRoot app, but I don't know if that would help in any way.
Please help me guys!
Similar Issue
I am have a very similar issue, I also rooted my Brigadier with Kingroot and all went well. However, I attempted to flash the Xposed Framework onto it using Flashify. After doing such it got stuck in a bootloop, I was able to fix that problem by booting into fastboot mode and using fastboot to push stock firmware back onto my device. However now I have an even bigger problem where my phone boots up to the Powered by Android screen and then to the Kyocera screen, however instead of continuing to boot to the Verizon Wireless screen and then into the phone, it gets stuck at a black screen. I have tried waiting for hours and nothing at all happens, also I can no longer seem to boot into fastboot mode or in other words the Powered by Android screen with the little 1 in the top left corner of the screen. Fastboot nor ADB recognizes the device when plugged into my computer, as neither list anything when ran. Please help, I don't want to have to pay and end up sending my phone into Verizon to be unbricked.
Ornias Abezethibou said:
I am have a very similar issue, I also rooted my Brigadier with Kingroot and all went well. However, I attempted to flash the Xposed Framework onto it using Flashify. After doing such it got stuck in a bootloop, I was able to fix that problem by booting into fastboot mode and using fastboot to push stock firmware back onto my device. However now I have an even bigger problem where my phone boots up to the Powered by Android screen and then to the Kyocera screen, however instead of continuing to boot to the Verizon Wireless screen and then into the phone, it gets stuck at a black screen. I have tried waiting for hours and nothing at all happens, also I can no longer seem to boot into fastboot mode or in other words the Powered by Android screen with the little 1 in the top left corner of the screen. Fastboot nor ADB recognizes the device when plugged into my computer, as neither list anything when ran. Please help, I don't want to have to pay and end up sending my phone into Verizon to be unbricked.
Click to expand...
Click to collapse
I have the same problem. I bought a new a Brigadier that was on 4.4.2. I rooted with Kingroot ran update and now my phone will not boot past Kyocera screen. It goes black with the back light on. Did factory wipe and still nothing. I am shocked that KK has killed yet another phone of mine. I very much dislike KK ROM. What did you find out?