My sisters Razr I has been acting a bit funny today, when opening apps they would randomly close (no FC dialogue) a reboot did temporarily fix that issue, however it did take over 5 minutes to get past the "M" boot screen.
Later in the evening the apps began exiting again, so I tried another reboot and it is still getting stuck at the "M" logo, only this time it seems to be doing it indefinitely.
I have tried using key combos to get in to the stock recovery and have successfully completed a factory reset, but there is still no progress. It has been stuck on the red M for about two hours since the factory reset.
This phone is completely stock, unrooted and there have been no OTA updates recently so I am not sure what has caused this issue.
I have looked around this sub forum and when ever people had similar issues it was relating to having a altered boot loader during OTA updates, as this is not the case with this phone I'm not sure what the best course of action would be to get this phone back running again?
Thanks for reading,
Mark.
The easiest solution would be to reinstall stock ROM by using RSDlite. I think.
Odesláno z mého XT890 pomocí Tapatalk
Lucki_X said:
The easiest solution would be to reinstall stock ROM by using RSDlite. I think.
Odesláno z mého XT890 pomocí Tapatalk
Click to expand...
Click to collapse
Hey, thanks for the reply, flashed the stock rom using RSD Lite as suggested and it seems to be alive! currently entering all the Google account information.
Why the phone decided to brick itself is a mystery to me, this phone has always had the stock rom with no rooting or modifications done.
THANKS!
Related
Hi.I got problem with my z.1st there came out an error said that there no SIM card and network.but only for few second and it came back.but after few days,my z start shutdown itself after that error comes.the only way to boot back is I need to plug in charger or my z will stuck on boot animation. What I did is I flash back the ROM via recovery, but no luck.same issue.then I flash stock firmware with flashtool,also same.andalso,after a successfully boot,my battery will drained around 45 to 50%. But it takes 10minutes to fully charge back.
Currently running monxdefied ROM with DOOMLORD kernel.here are some snapshots
Sent from my C6603 using xda app-developers app
Here are some video sample for my problem.itsgetting worse
http://www.youtube.com/watch?v=Y07WOJWrLj4&feature=youtube_gdata_player
Sent from my R800i using xda app-developers app
Same fate...
kayrowl91 said:
Here are some video sample for my problem.itsgetting worse
Sent from my R800i using xda app-developers app
Click to expand...
Click to collapse
Looks like we are having the same problem. I'm on 4.3 Commercial and Journalists released by @Androxyde , later in order to use TB, I reflash XZDualRecovery to gain root, then I first encounter serious battery drain, 70% to 8 % when I was on a trip, I don't took notice, later it promptly shut down when no SIM ERROR, shut down when launching camera. In order to fix the problem, I fully wipe the phone, use DISASTER RECOVERY to gain back stock recovery[DoomKernel v19] by @DooMLoRD. I flashed back stock recovery and relock bootloader using Flashtool, I successfully did everything back to 4.2.2 build 2.67, boot back into system though without root, later I notice there is no network signal, i try to launch camera but failed, I tried to charge it to 100% [complete], but instantly it shut off. Later stuck like yours. BootLoop problem. Now I am figuring it wasnt hardware problem. I tried to investigate anything. Inspect battery but Android tell me Battery health is good. So , I figure there is something wrong with kernel, especially chargemon.stock .:silly:
nerodevilangel said:
Looks like we are having the same problem. I'm on 4.3 Commercial and Journalists released by @Androxyde , later in order to use TB, I reflash XZDualRecovery to gain root, then I first encounter serious battery drain, 70% to 8 % when I was on a trip, I don't took notice, later it promptly shut down when no SIM ERROR, shut down when launching camera. In order to fix the problem, I fully wipe the phone, use DISASTER RECOVERY to gain back stock recovery[DoomKernel v19] by @DooMLoRD. I flashed back stock recovery and relock bootloader using Flashtool, I successfully did everything back to 4.2.2 build 2.67, boot back into system though without root, later I notice there is no network signal, i try to launch camera but failed, I tried to charge it to 100% [complete], but instantly it shut off. Later stuck like yours. BootLoop problem. Now I am figuring it wasnt hardware problem. I tried to investigate anything. Inspect battery but Android tell me Battery health is good. So , I figure there is something wrong with kernel, especially chargemon.stock .:silly:
Click to expand...
Click to collapse
i also hope its software issue.but now i cant even entering recovery to flash kernel or ROM. its shutdown itselft to fast.
so,is there any solutions i can do right now? please. my world is dark without Z.
kayrowl91 said:
i also hope its software issue.but now i cant even entering recovery to flash kernel or ROM. its shutdown itselft to fast.
so,is there any solutions i can do right now? please. my world is dark without Z.
Click to expand...
Click to collapse
My Z also down now. But it's possible to get into fastboot mode and recovery mode. I drained my battery to 0 and then plug it into PC and it's possible to get into it. Try it out. But result is the same. It's like the kernel fighting back on its own to prevent cross platform launching.
Try flashing stock again.same result.shutdown itself again and again. I dont think its related to chargemon because i already flash stock firmware,as im aware if we flash stock ftf,chargemon will revert back to original right?
Sent from my R800i using xda app-developers app
i looked. i swear. however, can't find anything that addresses my issue or at least i don't recognize it at my issue.
I have a DE Moto X on VZN.
unlocked bootloader
reverted from 4.4 to 4.2.2
flashed TWRP-2.6.3.1-ghost-4.4
Everything was working just fine and i couldn't leave well enough alone. I was screwing around and tried to flash/install/whatever an apk that would invert gmail colors....basically white to black. i'm not sure if it was before or after i did that but i created a backup in case it screwed something up and i wanted to revert. well, i loaded it and nothing happened so i went to restore my device from the backup i had just created and TWRP told me it was complete/successful or something and gave me the option to reboot. i did and now my phone is stuck in a boot loop. i've tried to restore several times to no avail.
i can get into bootloader menu but normal start up starts the boot loop process again. TWRP loads if i go into recovery. phone isn't recognized by RSD Lite. not sure what to do.
Can anyone help or tell me what additional info you need to be able to help?
texaslegend said:
i looked. i swear. however, can't find anything that addresses my issue or at least i don't recognize it at my issue.
I have a DE Moto X on VZN.
unlocked bootloader
reverted from 4.4 to 4.2.2
flashed TWRP-2.6.3.1-ghost-4.4
Everything was working just fine and i couldn't leave well enough alone. I was screwing around and tried to flash/install/whatever an apk that would invert gmail colors....basically white to black. i'm not sure if it was before or after i did that but i created a backup in case it screwed something up and i wanted to revert. well, i loaded it and nothing happened so i went to restore my device from the backup i had just created and TWRP told me it was complete/successful or something and gave me the option to reboot. i did and now my phone is stuck in a boot loop. i've tried to restore several times to no avail.
i can get into bootloader menu but normal start up starts the boot loop process again. TWRP loads if i go into recovery. phone isn't recognized by RSD Lite. not sure what to do.
Can anyone help or tell me what additional info you need to be able to help?
Click to expand...
Click to collapse
So you've tried restoring your nandroid prior to the flash, and still get bootloops, right? Have you tried wiping the caches? You can also try a full wipe and see if that gets you out of the boot loop, and then you can go back and try to restore your nandroid.
If all else fails and you can get into fastboot, there are instructions here on getting back to stock: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images. I would pull my backup from the device first from within TWRP (although if you don't erase userdata it should still be on the phone). You'll have to re-flash TWRP, but that process should get you back to having a working phone.
there might also be a problem with the fact that oyu were running 4.2.2 and using twrp that was built for 4.4. there is a twrp that was built for 4.2.2 so i don't know why you used the one built for 4.4. don't know what the differences are if any that would affect running twrp 4.4 on a 4.2.2 firmware but there may be some major issues.
You could try manually deleting everything with fastboot, then boot into recovery to restore your backup before flashing the 4.2.2 TWRP.
Thanks for the help. I thought I edited my post to say I fixed the problem. Did that with a wipe from the twrp bootloader our whatever that screen is called when you not into recovery.
Thanks
Sent from my XT1060 using xda app-developers app
I am curious as to why you downgraded back to 4.2.2?
Mainly for FoxFi WiFi. I use it on road trips for my kid's iPad and Nabi.
Sent from my XT1060 using xda app-developers app
If you have an unlocked bootloader, why not use one of the available mods with 4.4?
First I guess would be because I didn't know about it. I wasn't really planning on unlocking and rooting to begin with.
I got the DE because at the time I needed a phone it was the only x I could get with 32GB.
Which mood are you talking about I might have to check it out
Sent from my XT1060 using xda app-developers app
texaslegend said:
First I guess would be because I didn't know about it. I wasn't really planning on unlocking and rooting to begin with.
I got the DE because at the time I needed a phone it was the only x I could get with 32GB.
Which mood are you talking about I might have to check it out
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
There's a flashable zip in this thread.
http://forum.xda-developers.com/showthread.php?t=2561560
It's for 4.4 not 4.2 though, don't flash it unless you update.
Make it easy on yourself and use the Xposed module http://forum.xda-developers.com/showthread.php?t=2601859
Kind of stuck here.
I have VZW developer edition. Rooted, 4.4 with TWRP
Foolishly I accepted the OTA update to 4.4.2, this failed of course but now my phone is constantly rebooting. It stays up for a few minutes then powers back to recovery.
Help !!!
Thanks.
Its a Dev phone just fxz and re-root
Sent from my XT1080 using xda app-developers app
bigv5150 said:
Its a Dev phone just fxz and re-root
Sent from my XT1080 using xda app-developers app
Click to expand...
Click to collapse
If only I had a clue what that meant
homemadehitshow said:
Kind of stuck here.
I have VZW developer edition. Rooted, 4.4 with TWRP
Foolishly I accepted the OTA update to 4.4.2, this failed of course but now my phone is constantly rebooting. It stays up for a few minutes then powers back to recovery.
Help !!!
Thanks.
Click to expand...
Click to collapse
Can you get into the bootloader (hold power + volume down)? If so, you'll probably need to reflash the stock recovery before the update will install.
Thanks, after I stopped panicking and calmed down I was able to flash Stock Recovery and then the next reboot caused the standard update to work. Kind of surprised really, still rooted etc.
Right now phone is working but Wi-Fi indicator is not lit, even though it is using the wi-fi.
Clear cache and dalvik cache?
Sent from my XT1060 using Tapatalk
homemadehitshow said:
Thanks, after I stopped panicking and calmed down I was able to flash Stock Recovery and then the next reboot caused the standard update to work. Kind of surprised really, still rooted etc.
Right now phone is working but Wi-Fi indicator is not lit, even though it is using the wi-fi.
Click to expand...
Click to collapse
Well you have the dev edition, they aren't going to take root from you. Don't know what's up with your wifi, though. When I updated I ended up having to restore a backup and updating again because of several extremely strange problems.
homemadehitshow said:
Thanks, after I stopped panicking and calmed down I was able to flash Stock Recovery and then the next reboot caused the standard update to work. Kind of surprised really, still rooted etc.
Right now phone is working but Wi-Fi indicator is not lit, even though it is using the wi-fi.
Click to expand...
Click to collapse
Disable WiFi and turn it back on right after.
Sent from my Moto X DE
Yep, everything seems to be working again now.
I have blindly followed instructions for flashing etc. using Fasboot but I think I'm finally getting a better feel for what is going on with it.
homemadehitshow said:
Yep, everything seems to be working again now.
I have blindly followed instructions for flashing etc. using Fasboot but I think I'm finally getting a better feel for what is going on with it.
Click to expand...
Click to collapse
Good job taking some initiative. Not as difficult as you thought it'd be right?
the verizon 4.4.2 SBF file is out so any issues anyone is having they can just flash the whole SBF file and be complety stock 4.4.2
enjoy
http://sbf.droid-developers.org/download.php?device=0&file=841
Running a completely stock VZW Moto X on the latest update (4.4.2). Woke up this morning to a half dozen or so app updates, including Active Display and Moto Help. I updated these two, and then an update for Beautiful Widgets started after. My phone then locked up and restarted. Now, it loads through the boot screen and then loads the Verizon screen, then the device goes black. I've tried wiping cache, to no avail. Any suggestions? I've installed the Moto X drivers via the Moto site, but the device isn't being recognized via ADB. I would really really really like to retrieve my files from the phone before doing a full factory reset...
Haven't seen anyone else report this....
Sent from my XT1060 using Tapatalk
Same symptoms on unlocked dev edition
I can't for sure tie it to an update, but the only thing that I did on my Moto X today was enable Motorola Connect. In the ensuing ~3 hours my phone bit it and would get to the Motorola Unlocked Bootloader screen and stop. Tried to boot to custom recovery, but it wouldn't work. Tried reloading TWRP, but gave access error on write but it seems to have fixed it enough to let TWRP open. TWRP showed list of access errors, like the memory had been corrupted. Need to find 4.4.2 image and load it back on via FB, as recovery has no data now.
stastnysnipes26 said:
Haven't seen anyone else report this....
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
omaharper said:
I can't for sure tie it to an update, but the only thing that I did on my Moto X today was enable Motorola Connect. In the ensuing ~3 hours my phone bit it and would get to the Motorola Unlocked Bootloader screen and stop. Tried to boot to custom recovery, but it wouldn't work. Tried reloading TWRP, but gave access error on write but it seems to have fixed it enough to let TWRP open. TWRP showed list of access errors, like the memory had been corrupted. Need to find 4.4.2 image and load it back on via FB, as recovery has no data now.
Click to expand...
Click to collapse
You have a totally separate problem from the OP. I don't have an unlocked boot loader and haven't done a ton of research on the risks of unlocking the consumer edition. 4.4.2 images are posted all around the forums. I would start there.
Sent from my XT1060 using Tapatalk
Thanks. You are right, not the same problem, when my phone soft bricks when I haven't been doing anything to it I get twitchy. I have the DE and have tried (a bunch of times) using RSD Lite and fastboot to push files back to phone, but after reboot everything looks to be reverted back like if WP was enabled, which it isn't. I will take a cruise thru the forums looking for similar issues, but any suggestions would be appreciated
stastnysnipes26 said:
You have a totally separate problem from the OP. I don't have an unlocked boot loader and haven't done a ton of research on the risks of unlocking the consumer edition. 4.4.2 images are posted all around the forums. I would start there.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
omaharper said:
Thanks. You are right, not the same problem, when my phone soft bricks when I haven't been doing anything to it I get twitchy. I have the DE and have tried (a bunch of times) using RSD Lite and fastboot to push files back to phone, but after reboot everything looks to be reverted back like if WP was enabled, which it isn't. I will take a cruise thru the forums looking for similar issues, but any suggestions would be appreciated
Click to expand...
Click to collapse
If you have a Dev edition fast boot stock vzw files, fast boot OEM unlock and reflash SU. simple as that.
Sent from my XT1060 using Tapatalk
Yup. Have gone thru that procedure several times, but phone won't get past the bootloader unlocked screen, and even after flashing stock (with stock recovery partition) TWRP still shows up, so some write to memory isn't sticking. It's very strange, used same procedure on this phone when upgrading to 4.4.2 from 4.2.2 and on other phones with no problem. Since TWRP can't access the flash, I am wondering if I actually have a corrupted memory module. If I can't get things working, I will start a thread. Don't want to hijack this one. Thanks.
stastnysnipes26 said:
If you have a Dev edition fast boot stock vzw files, fast boot OEM unlock and reflash SU. simple as that.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
As an update to the original post...
My phone "magically" booted at some point while it was sitting on my table. It's been working since then, but I tried to restart today and the thing won't boot up again. No idea what causes this and adb still isn't working with the phone in recovery mode.
Well I'm from the old school of if a car won't start you check 3 things spark fuel air. So in the case of our phones I always say fxz if an fxz fails to fix the problem than I lean towards a hardware failure. I have never had an fxz not fix a software issue. And I have bricked more than my fair share of devices several times.
I just did my custom order of the Moto X today. I hope I won't run into any issues. I'm switching from the iPhone 5S.
Sent from my XT1058 using Tapatalk
..
Y
thesandman00 said:
As an update to the original post...
My phone "magically" booted at some point while it was sitting on my table. It's been working since then, but I tried to restart today and the thing won't boot up again. No idea what causes this and adb still isn't working with the phone in recovery mode.
Click to expand...
Click to collapse
Have you tried fastboot?
Also getting the drivers to work can be tricky. You have to install them and then use device manager while you're phone is plugged in to get it working.
Sent from my XT1060 using Tapatalk
Hey guys, I was running Maximum overdrive v1.0 and beastmode 56.8 kernel (no tweaks) when my phone starts freezing and rebooting. It would happen often and even at times It wouldn't boot completely I would have to remove the battery for It to boot. Then It started to get "kernel panic ulpoad mode" I odin flashed back to stock MM but same issues going on. Any ideas? Or its time for a new phone? Thank you
Sent from my SM-N910T using Tapatalk
carmona_sc said:
Hey guys, I was running Maximum overdrive v1.0 and beastmode 56.8 kernel (no tweaks) when my phone starts freezing and rebooting. It would happen often and even at times It wouldn't boot completely I would have to remove the battery for It to boot. Then It started to get "kernel panic ulpoad mode" I odin flashed back to stock MM but same issues going on. Any ideas? Or its time for a new phone? Thank you
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
I was curious cause I never heard of that , and some people said a factory reset solved the problem . However a fresh Odin install is good. Did you wipe system as well as the normal wipes?
Bubba Fett said:
I was curious cause I never heard of that , and some people said a factory reset solved the problem . However a fresh Odin install is good. Did you wipe system as well as the normal wipes?
Click to expand...
Click to collapse
Yes I did, and nothing seemed to work, even went back to stock 5.1 and same issues consist.
Sent from my SM-N910T using Tapatalk
carmona_sc said:
Yes I did, and nothing seemed to work, even went back to stock 5.1 and same issues consist.
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
Yikes. I didn't even see a ton of info on the subject. I can't imagine there is anything left on the device to cause any issues. Hopefully someone with more knowledge about this sees this post. Note 7 release party Aug 2nd if it comes to that!
same issue i see alot of people with it, its the emmc i confirmed it beause yesterday while i was alseep my emmc decided to give up on life no recovery no download failed to read emmc, the problem is repairing it im not gonna take it to samsung as they will charge almost the price of a new phone i have found a chip for it but it says it has sm n910p/f firmware on it not sure if it would be an issue as i could reflash the tmobile firmware on it.
http://www.aliexpress.com/item/Bran...2630152207.html?spm=2114.40010708.4.13.nPWCQ2
any advice on the chip?
So, what was the final solution?