I currently have an unlocked MB860 running 4.5.91. I tried taking the OTA update to 4.5.141 and it did not complete. I removed the battery and rebooted, it got into a boot loop. I was able to clear the bootloop by wiping the cache partition. All this is well documented here in the forum and was a great help.
The problem afterward that I have lingering is that any first menu item on the touchscreen in portrait only mode is not select-able. If i orient to landscape mode, it is.
I have searched without much luck to resolve this and before I try to reset to factory defaults I wanted to reach out and see if anyone here is aware of a resolution.
Thanks in advance...
901racer said:
I currently have an unlocked MB860 running 4.5.91. I tried taking the OTA update to 4.5.141 and it did not complete. I removed the battery and rebooted, it got into a boot loop. I was able to clear the bootloop by wiping the cache partition. All this is well documented here in the forum and was a great help.
The problem afterward that I have lingering is that any first menu item on the touchscreen in portrait only mode is not select-able. If i orient to landscape mode, it is.
I have searched without much luck to resolve this and before I try to reset to factory defaults I wanted to reach out and see if anyone here is aware of a resolution.
Thanks in advance...
Click to expand...
Click to collapse
I have to ask have you tried rebooting the phone again with a battery pull. That fixed my problem when I had something like that with mine
So recently (like 2 hours ago), my phone started acting like it wasn't on the cricket network anymore. I've rebooted. Taken things out and reinserted them. Nothing works. So I figured I would just hard reset my phone. So I get through the process of getting it to the recovery booting screen only to find out that something WON'T LET ME FACTORY RESET MY PHONE!!! I am frustrated beyond belief and I just want to be able to use my phone. Can anyone please please help me? I am afraid I have a virus or someone is trying to hack my device/already has
littllejimmy said:
So recently (like 2 hours ago), my phone started acting like it wasn't on the cricket network anymore. I've rebooted. Taken things out and reinserted them. Nothing works. So I figured I would just hard reset my phone. So I get through the process of getting it to the recovery booting screen only to find out that something WON'T LET ME FACTORY RESET MY PHONE!!! I am frustrated beyond belief and I just want to be able to use my phone. Can anyone please please help me? I am afraid I have a virus or someone is trying to hack my device/already has
Click to expand...
Click to collapse
What do you mean it wont let you factory reset, what happens when you try it?
Sent from my Galaxy S5 using XDA Labs
Sounds like recovery might be corrupted if it doesn't let you into recovery
Or does it enter recovery? Need a bit more detail about what's actually happening, instead of "Something won't let it reset"
Flash a stock ROM back over the top to repair recovery/system etc and try resetting again
My XT1575 just decided to go into a bootloop a week ago on its own, literally. I was just checking traffic on Google maps when I noticed it started to lock up. Finally, I see the Motorola splash screen, and that was the beginning of it. Went into recovery mode and tried a factory reset, clear cache partition, etc. but no luck. I've tried everything under Android 6.0 here but it continues to bootloop no matter what I do.
It's not rooted and the bootloader is locked, so I don't think I can even install TWRP or any custom recovery. I have never even though of enabling USB debugging so that's out of the question. What's odd is after trying all sorts of things, sometimes, after the phone has been off for a while I would power it on and it would actually boot into the Welcome screen. Shortly after that though, it locks up and starts bootlooping again. I don't know what else I can do about this or if it's recoverable. I hope someone can help. If it's of any significance, when in recovery mode, at the top I see what I think is the firmware it's currently on -- motorola/clark_retus/clark 6.0/MPHS24.49-18-4/5. Please help!
Update - After having my XT1575 powered off overnight, I powered it on this morning and it was able boot all the way into the Welcome screen, setup, etc. Right away I went and turned on USB Debugging and Allow OEM unlock. Tried rebooting and again it fails to boot. What's weird is it randomly seems to boot when it wants, and something must be corrupt but I just don't know what it could be. Does anyone have any ideas?
Don't unlock the bootloader.
If it is locked and behaving that way you should be able to get a warranty fix out of Lenovorola. If you unlock the bootloader you void your warranty, and they might choose to not honor it even if you say the problem started before.
Painful and slow as it might be, I'd recommend working with the manufacturer on this one.
jason2678 said:
Don't unlock the bootloader.
If it is locked and behaving that way you should be able to get a warranty fix out of Lenovorola. If you unlock the bootloader you void your warranty, and they might choose to not honor it even if you say the problem started before.
Painful and slow as it might be, I'd recommend working with the manufacturer on this one.
Click to expand...
Click to collapse
Yes undo what you just did an follow this guy
jason2678 said:
Don't unlock the bootloader.
If it is locked and behaving that way you should be able to get a warranty fix out of Lenovorola. If you unlock the bootloader you void your warranty, and they might choose to not honor it even if you say the problem started before.
Painful and slow as it might be, I'd recommend working with the manufacturer on this one.
Click to expand...
Click to collapse
I'm afraid it's too late for the bootloader, since it was one of the things I was trying out of desperation. After trying fastboot flashing the stock firmwares, I still get bootloops and strangely enough I was able to use the phone the other day for several hours before it started bootlooping again Thing is, it seems to behave differently at random times. Sometimes it makes it all the way up to the "Android is upgrading" screen but then freezes and reboots.. Other times it locks up at the Motorola splash screen and reboots.. And sometimes it even boots all the way up, is usable for a little bit, then begins bootlooping on its own.
I'm just wondering if something is corrupt software-wise (boot? system? etc?) or if it's a hardware issue. How do I even tell at this point?
iflyimpilot said:
I'm afraid it's too late for the bootloader, since it was one of the things I was trying out of desperation. After trying fastboot flashing the stock firmwares, I still get bootloops and strangely enough I was able to use the phone the other day for several hours before it started bootlooping again Thing is, it seems to behave differently at random times. Sometimes it makes it all the way up to the "Android is upgrading" screen but then freezes and reboots.. Other times it locks up at the Motorola splash screen and reboots.. And sometimes it even boots all the way up, is usable for a little bit, then begins bootlooping on its own.
I'm just wondering if something is corrupt software-wise (boot? system? etc?) or if it's a hardware issue. How do I even tell at this point?
Click to expand...
Click to collapse
The random nature of what you're describing does sound like hardware. Consider a full restore where you fastboot flash everything back to stock of you haven't already.
Check logs. See if you're getting anything in last_kmsg. Use an app like syslog if you aren't used to pulling them, though you might have to use adb if you aren't getting through boot all the time.
jason2678 said:
The random nature of what you're describing does sound like hardware. Consider a full restore where you fastboot flash everything back to stock of you haven't already.
Check logs. See if you're getting anything in last_kmsg. Use an app like syslog if you aren't used to pulling them, though you might have to use adb if you aren't getting through boot all the time.
Click to expand...
Click to collapse
Thanks for replying. I've tried fastboot flashing everything and even going into recovery and clearing cache partition as well as doing a factory data reset. I'm afraid it may very well be hardware. I'll try your suggestion about the logs.
Is 'last_kmsg' a line I should be looking for in the log? If so, what would I need to see in order to determine whether or not it's a hardware problem?
iflyimpilot said:
Thanks for replying. I've tried fastboot flashing everything and even going into recovery and clearing cache partition as well as doing a factory data reset. I'm afraid it may very well be hardware. I'll try your suggestion about the logs.
Is 'last_kmsg' a line I should be looking for in the log? If so, what would I need to see in order to determine whether or not it's a hardware problem?
Click to expand...
Click to collapse
/proc/last_kmsg is a log file that should get written to if a kernel panic causes a reboot in theory. In practice I find it is often blank even after a random reboot.
iflyimpilot said:
I'm afraid it's too late for the bootloader, since it was one of the things I was trying out of desperation. After trying fastboot flashing the stock firmwares, I still get bootloops and strangely enough I was able to use the phone the other day for several hours before it started bootlooping again Thing is, it seems to behave differently at random times. Sometimes it makes it all the way up to the "Android is upgrading" screen but then freezes and reboots.. Other times it locks up at the Motorola splash screen and reboots.. And sometimes it even boots all the way up, is usable for a little bit, then begins bootlooping on its own.
I'm just wondering if something is corrupt software-wise (boot? system? etc?) or if it's a hardware issue. How do I even tell at this point?
Click to expand...
Click to collapse
going by that logic the thing that you should have done was get a factory image from moto and flash to stock using moto tools if that failed at fixing it then send into moto it might not be lost yet but the more you progress the more less likely to replace the phone moto is...
it sounds like something is going bad could be ram emmc or the soc
What i would do is get into discussions with lenovo to see if they can get you fixed up. if you unlocked the bl they know be straight with them. if you get nowhere and no rom you load can fix it sell as parts replace at your expense...
My nexus 6p was working perfectly fine in the morning then all of a sudden into a bootloop. I went into recovery mmode and factory reset the device and still didnt fix the problem. Now everytime i try to enter recovery mode it just puts itself back into a bootloop. Please help
dragonphx said:
My nexus 6p was working perfectly fine in the morning then all of a sudden into a bootloop. I went into recovery mmode and factory reset the device and still didnt fix the problem. Now everytime i try to enter recovery mode it just puts itself back into a bootloop. Please help
Click to expand...
Click to collapse
I sincerely hope there's something else going on but it is most likely the well documented problem with no fix. Heres just one thread of several. This one's right from this very section of the forum
https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528
Hope this isn't your issue but if it is I hope you're under warranty....
Side note--this really sucks. I've got like 2 months left under warranty but think Google should extend that if they can't find a fix. Ive had no issues-best phone ever for me personally but of course that doesn't count for much if its dead after a year.
Basically as the title says whenever I want to restart my phone I get stuck in this inexplicable boot loop that doesn't stop and I can only actually get into the phone in some weird magical way that I haven't figured out how is done yet.
I've tried flashing stock(I was on btu 7.0), wiping cache partition/factory resetting but the issue still remains. Anyone encountered anything similar?
If flashing rom and factory reset doesn't fix it then it might be hardware issue and need mainboard replacement.
Sent from my SM-G935F using Tapatalk
This is where most of the people make problem even worst, please don't mess with the software anymore and take it to service,it must be hardware related.