I just bought my wife a new phone (Razr hd ftw) because she was on the original razr and its pretty much no good anymore. I was giving her the luxury phone treatment. I rooted it, unlocked the bootloader, installed CWM, and installed cm11. Everything was going great but now for some reason when I try to get into the recovery...i get the moto logo, and its just shuts off. I flashed a new recovery twice, and it shows success on my cmd window, but its still shutting off when I try to get into recovery menu. Any suggestions?
**Update** I was able to get back into recovery after trying over and over again. I still have the issue where it shuts off, but its random. I wonder whats wrong :-/
Which version of CWM are you using and where did you get it?
This isn't the correct place to asking for help...
Related
My sister said she spilled a little water on the screen of her phone the other day and it started boot looping.
Ive been trying to reflash it, but there are some issues...
If the phone is plugged in, it will cycle the charging battery on and off... unable to get into download or recovery.
If its not, it used to show the galaxy boot screen and turn on and off... now it just stays frozen on that screen. In either instance i was unable to get into recovery or download mode.
I got into recovery a couple of times when it actually booted the ROM, but everytime i would use the power button to try to make a selection the phone would just reboot and go into a cycle again.
I also got it into download mode once through the ROM but it cant get the ROM to boot anymore...
I might be able to get it into recovery but when i do it just reboots when i select anything.
and help would be awesome
thanks.
OH, when i actually got the ROM to boot it would throw an array of system errors and force closes. I also think the water had nothing to do with it and something she did after the water is what started causing the problems
I got recovery and i flashed a new kernal and ROM and erased everything and its still freezing at first Galaxy boot screen.
probably because the phone is water damaged?
See if the guide in the second link of my signature will help.
Thanks ill give it a shot.
But a major problem is that i am unable to get it to boot into download mode.
So i got CWM to boot, and i reflashed the kernal and ROM, with no luck.
CWM read catch error. Unable to mount... format... ect...
From what ive been reading the internal catch is fried....
Anyone have a motherboard they want to ship me? LOL :laugh:
Thanks lumin30, I finally found a way to get the phone into download mode. (take the battery out, Put it back in, hold buttons, plug USB in, press power button) after a few reboots it would finally go.
I followed the link and got it back to stock and it booted. Now letting it sit to settle in and hopefully it will be functional again.
This thread can be deleted! :good:
Hello guys.
I apologize for making yet another "my phone is soft-bricked" thread, but I have been through at least 20-25 of the other threads, seemingly tried everything, and I can't get past my problem. Also, most of the other threads I saw are pretty old and not really active anymore. A few of the tools there can't even be downloaded anymore because the links are dead.
Anyway, here's my story.
I have a 16 GB US retail XT1032 that I bought mostly to give tech support to my parents, whom I also bought a 8GB each. Theirs, I left untouched. Mine, I unlocked bootloader and rooted right away. All went well for a long time.
My parents kept receiving OTA's and it took them all the way to Lollipop. Me being rooted, I got stuck in KitKat somewhere (I'm not 100% sure whether that was in 4.4.2 or 4.4.4), but since it wasn't my daily driver, I let it lie as stock rooted KitKat. Recently I wanted to go to Lollipop in order to keep seeing "the same things" as my parents, and I installed TWRP in preparation to flash a "stock enhanced" version of Lollipop. TWRP flashed fine but there was something funny all along: I could use ADB or a root app to boot into recovery from the ROM, but I could never manage to get the phone to go into recovery by booting into fastboot (vol down+power) and then choosing recovery. Screen would go black and recovery would never load.
So I copied a "stock" Lollipop image and booted into TWRP from the ROM and wiped everything and tried flashing the Lollipop ROM. It got stuck somewhere part way, and a few hours later there was no more progress.
Ever since then, I am stuck in fastboot. Fastboot seemingly works correctly, recently I was able to flash an OG animation to get rid of the nasty "your bootloader is unlocked" warning. I can flash recoveries (TWRP and/or CWM) without error on the phone or the computer, but when I try to then boot into recovery using the bootloader, I get stuck on the black screen and go nowhere.
As others in the various threads have commented, when I try to boot "normally", I get the boot animation and a vibration and then it gets stuck.
I have tried so many things by reading different threads I couldn't tell you anymore what all of them were. I've gotten errors about downgrading, I've gotten stuck in fastboot reason: "failed flash", I've gotten flashing errors about the size of recovery or boot or gpt. What I've never managed to do again is to boot into anything other than bootloader. No recovery and no ROM.
Could someone with a bit of experience please point me to some working links and/or when you have the time, help me look at a couple of logs or something that can help me figure out where my problem lies and how to get out of it? my daily driver phablet died a gruesome death and I wanted to go back to my trusty moto g, to no avail.
Thank you very much to whomever can help.
Ruben.
Try to reflash full stock firmware for your device according to your bootloader version. Hope it helps....
Try typing in fastboot devices
I was having issues with my Motorola Photon Q LTE with the Stock ROM (it has bootloader unlocked and Rooted), but the problem was, when running apps that play video, they wouldn't work (it would just show a white screen with a film icon). Other phones work, just the Motorola Photon Q LTE was having issues with it. So, I figured i'd try another ROM....I had one problem after another with getting ROMs to work. Carbon ROM would install but would force close FaceBook (which is needed), another ROM gave an encryption error. I went between 2 or 3 recoveries and then found someone that said they had a "stock JB" ROM....I was tired and frustrated and wound up just clicking things b/c at this point, I was ready to toss the phone on the ground so hard that it would make it's way to the center of the earth! But, now i'm stuck on the FastBoot screen with it saying "Battery Low" so I can't flash a recovery onto it again. The battery was at 70% when I was in TWRP before that happened....now I can't get even get into Recovery or anything...
Okay, I think I got it fixed now......I managed to get it to take a charge. I had to plug it in, let it get to FastBoot and then push the Power Button....NOT hold it...just push it and it would turn the display off and start charging....its at TWRP now and installing a ROM...HOPEFULLY I can get passed the "Encryption Error" issue...
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?
I've tried Carbon but that one wouldn't actually boot up, just shut my screen off and would shut itself off.
AospExtended ROM, is just sitting at these bouncing dots.
Ressurection Remix, sits at the boot screen of whatever that...logo is supposed to be.
I'm at my witts end here and about to smash this piece of junk. Nothing on this phone has ever worked right since I got it. Figured I'd fix it by getting rid of their trash UI and do custom roms but apparently it can't even do THAT right.
Upgrade your device to EMUI 8. Then flash one of the Treble ROMs.
I can't even get into TWRP anymore. It just keeps going into the EMUI recovery everytime I hold down all 3 buttons.
Spykez0129 said:
I can't even get into TWRP anymore. It just keeps going into the EMUI recovery everytime I hold down all 3 buttons.
Click to expand...
Click to collapse
I've found out myself of why those custom roms wont boot, because you did not clear cache and dalvik before you booted to the custom rom. You wont have to smash ur phone if you do this.
SuperSwordSmasher said:
I've found out myself of why those custom roms wont boot, because you did not clear cache and dalvik before you booted to the custom rom. You wont have to smash ur phone if you do this.
Click to expand...
Click to collapse
That's something I do automatically without thinking. That stuff was finicky back in the OG Droid days so I always do it like 3 times just to make sure.
Anything else that would cause it to get stuck at the booting up screen? I get passed the blue screen and the your device is insecure or whatever. Then it just goes into the fancy booting logo and just sits there. Never on any of the phones I've rooted over the past decade ever got stuck like this.
WOHOOO! I MADE PROGRESS!
My phone is now stuck in a never ending bootloop and can't seem to get into any recovery. Can't even shut the phone off because it just turns itself back on. Backwards progress is where it's AT!
Bump, any ideas?
I went back to Motorola and bought an X4 but I'd like to get this working again so I can sell it.
Spykez0129 said:
Bump, any ideas?
I went back to Motorola and bought an X4 but I'd like to get this working again so I can sell it.
Click to expand...
Click to collapse
What honor 8 model do you use? It should not be Bootlooping then, if there is no solution you can always go to stock.
You could flash twrp again, with fastboot
Boot with power + volume up to boot into twrp
Use dload method