Database Develop

[Q] Unable to restart phone

Hi guys,
Hoping someone here has the knowledge to help with my little problem!
My phone battery died a few days ago. When I got home to recharge I found the charging LED wouldn't show and also the phone wouldn't restart.
After several attempts I resorted to flashing the ROM again. I got it up and running, but then again by restarting manually again the phone went into a bootloop and wouldn't start up.
Has anyone experienced this before? I've had no issues previously but this is really starting to bug me. Means I can't run Xposed modules etc that need a reboot. I've now installed the ROM 3 times and tried clearing the cache after each.
Running ARHD 51.0 with stock kernel.
Many thanks in advance!
Neil

[Q] Help! Post-Root problems

Hey all, I recently tired to root my SGH-i537 att active but ran into problems afterwards. After I rooted I would boot up my phone with a unlock icon, not a big problem, but i was getting security notices an was unable to even slide the wi-fi search to on let alone connect to one. Another problem i ran into was my kernel was destroying my battery! i would charge for 6 hours and only go up to 70% ot have it die in an hour. After all that frustration i unrooted using the SuperSU unroot button. While I am now unrooted(i think) my battery is still dying insanely quickly, I cannot even attempt to connect to wi-fi, and i am still booting up with the unlocked icon. At this point I just want to wipe it and start new but when i did a factory reset all of the problems listed above were still occurring. Should I find a stock ROM and try and have that downloaded on? I have no clue what to do and i need help please D:.

[Q] Bootloops, systemui force closes, and wifi errors after flashing back to stock

I absolutely hate creating yet another thread, but I've tried everything I can and I'm stuck. I was up until 4am (no lie) last night and been at it again for hours tonight. So... here are the symptoms.
Multiple bootloops/reboots at any of the following points:
1) "Preparing device" with the "Please wait" animation.
2) Force close: Unfortunately, Setup has stopped.
3) Force close: process.com.android.systemui has stopped.
4) Force close: Google search has stopped.
5) Bootloop at the bootloader warning message
Usually, the boot animation doesn't even start. Often, I'll see the "Bootloader Unlocked" warning message, then the Moto logo, then it cycles back through any of the above fail points. Sometimes, it'll stay on the bootloader warning message the whole time and then jump directly to the lock screen.
All of this started after unlocking my brand new Moto X Pure Edition and then attempting to use the "Multi-tool" to root. Or...maybe it was after trying to root using one of the Chainfire images. I can't recall. After doing so, wifi stopped working (wouldn't turn on). So, I tried (using the tool again) to flash back to stock. At that point things strange things started happening (force closes). I then tried flashing to stock and immediately flashing the OTA (all via fastboot). When I booted up, Lollipop setup wouldn't load, it'd bootloop, come back and maybe I could get to the next screen, but wifi would be dead. Or I'd get wifi to work, but it'd crash after accepting Google privacy terms.
So, after all of that, I decided I would just revert back to stock. At that point I tried a number of options including what I think is the likely best bet, @SolarTrans guide here. Oh, and somewhere along the line I flashed TWRP 2.8.3 and flashed one of the custom ROMs (LiquidSmooth). It booted, but was very unstable and also threw the same/similar systemui force close messages, occasionally would lose wifi or begin force closing like crazy. Makes me think I have a bigger issue since it happens regardless of ROM/firmware. I also tried graffixnyc's images. So... yeah... just want to get back to stock.
I've been doing this stuff with Android for many years. Not a newbie by any means. Completely comfortable using fastboot or adb command line. I'm just at a loss and feel that it's likely I'll have to send it back to Motorola. I can get into the bootloader no problem. Everything else is a toss up. The last time I flashed files via the SolarTrans guide, it eventually loaded up the home screen (after many bootloops), but wifi wasn't working and I got a strange Moto message about reverting the sensors firmware or update. I rebooted and it never booted again, so I erased cache and userdata via fastboot. That didn't help. I just flashed the original firmware again and it spent a good 20/30 minutes bootlooping before getting to the setup screens. I skipped everything. Then it bootlooped at the home screen.
Open to suggestions!
Edit 1:
Pretty much anything causes the phone to bootloop, but I was able to get a screenshot of the baseband, kernel, build, etc. It bootlooped, but worked the second time around. I think I just made things way worse by trying to turn on bluetooth. It's just bootlooping over and over. Gonna try and get some sleep!

So, before bed, I flashed the OTA from the SolarTrans thread. It booted up, threw some errors and then once I connected to wifi it bootlooped. It did this for at least 10 minutes before I plugged the phone in and went to bed. When I woke up this morning, it was sitting on the setup screen. No errors. I signed in to my Google account and it restored all my apps. I rebooted. Still no problems. Just before leaving for work, I noticed that Dropbox wasn't installed. I installed it, signed in and then it bootlooped. After that...no luck. Kept rebooting. So, I brought the phone to work and left it on my desk for a few hours. It bootlooped or hung on the bootloader unlocked warning screen for at least 3 hours. I wiped cache. Same thing. Just now, I wiped userdata and rebooted. It went through the setup process without errors. Began restoring my apps and then froze. I manually restarted and now... no dice. Bizarre.

mercado79 said:
So, before bed, I flashed the OTA from the SolarTrans thread. It booted up, threw some errors and then once I connected to wifi it bootlooped. It did this for at least 10 minutes before I plugged the phone in and went to bed. When I woke up this morning, it was sitting on the setup screen. No errors. I signed in to my Google account and it restored all my apps. I rebooted. Still no problems. Just before leaving for work, I noticed that Dropbox wasn't installed. I installed it, signed in and then it bootlooped. After that...no luck. Kept rebooting. So, I brought the phone to work and left it on my desk for a few hours. It bootlooped or hung on the bootloader unlocked warning screen for at least 3 hours. I wiped cache. Same thing. Just now, I wiped userdata and rebooted. It went through the setup process without errors. Began restoring my apps and then froze. I manually restarted and now... no dice. Bizarre.
Click to expand...
Click to collapse
So, what was the problem then? The Dropbox app? Why is that?

No. Don't think so. It was just the trigger. I'm convinced any app would have eventually caused the bootloop.
I tried one more clean install of the official image straight from Motorola last night. Same results. So, I've initiated a return/repair.
Sent from my Moto X

Have they accepted repairing your device even with unlocked bootloader and root?
Sent from my XT1097 using XDA Free mobile app

They acknowledged that I'd unlocked the phone (it was logged in the record when they looked up my phone by IMEI), though I said I did so while trying to fix it (in order to wipe partitions and flash images which I also requested via their developer resources page).
They're sending a replacement phone without any push back at all. Honestly, I expected to send it in for repair. The rep said the standard protocol was to issue me a pin to order a new phone (mine is a customized Moto Maker model with a bamboo back).
Just so you're aware, unlocking the bootloader on Pure Edition phones does not void the warranty.
So, a replacement should be in my hands in about a week, I'm told. The phone was still within the initial month and so they're sending a brand new phone.
Sent from my Moto X

[Q] HTC One M7 - Noscreen lock/off after Android Lollipop update

Hello everyone,
I received an OTA update last night for my phone for Android Lollipop. If I had known better, I wouldn't have updated it.
Since the update, my screen doesn't timeout or lock, it just restarts. If I press the power button to turn the screen off, it restarts. I can either shut the phone off completely or keep the screen on, which obviously kills the battery pretty quick.
I tried doing factory reset already, issue is still there. I tried wiping cache partition, same issue.
At this point, I would really like to downgrade to KitKat. Is that possible? And if so, how? I'm on a Vodafone UK contract. My phone is not unlocked.
Any other solution that might help. I don't know what else to do. Please help.

rosesor said:
Hello everyone,
I received an OTA update last night for my phone for Android Lollipop. If I had known better, I wouldn't have updated it.
Since the update, my screen doesn't timeout or lock, it just restarts. If I press the power button to turn the screen off, it restarts. I can either shut the phone off completely or keep the screen on, which obviously kills the battery pretty quick.
I tried doing factory reset already, issue is still there. I tried wiping cache partition, same issue.
At this point, I would really like to downgrade to KitKat. Is that possible? And if so, how? I'm on a Vodafone UK contract. My phone is not unlocked.
Any other solution that might help. I don't know what else to do. Please help.
Click to expand...
Click to collapse
sounds like your phone is broken ..return it if it's Locked and never rooted

Finally fixed
In the end, I had to unlock the bootloader, root the phone and flash a customer ROM (Android Revolution). It worked! Now, I can finally switch my screen off without the phone restarting!
Thanks,
Rose

rosesor said:
In the end, I had to unlock the bootloader, root the phone and flash a customer ROM (Android Revolution). It worked! Now, I can finally switch my screen off without the phone restarting!
Thanks,
Rose
Click to expand...
Click to collapse
you also lost your warranty in the process. If it had not worked you would have been stuck paying for a repair
I'm happy it worked out for you

Help! Razr i stuck on boot (again)

So here's my story: my phone was JellyBean. I didn't tinker with it, didn't root, just used some launchers. It upgraded to KitKat. I kept using it, even though I liked JellyBean better. Then one month ago it froze and stopped responding even to physical buttons. I managed to restart it, but it wouldn't go past the intel logo. Somehow I got it to go past it and give me like two seconds on before it would freeze and become unresponsive again, so I got to enter safe mode (all following instructions on the internet, which buttons to hold to manage to get into safe mode). Once in safe mode, I deleted every app that had been recently updated or installed, one at a time, trying to turn my phone on each time, until I finally deleted facebook (that enourmous blue monstrosity taking all that internal space), and the phone seemed normal. I re-installed the other apps I had uninstalled, then one day later, it froze again. Now it wouldn't go past the intel logo. Only then I gave up and used RSDLite to re-install the firmware - BUT! The firmware I managed to find was JB, but I had been wanting to downgrade for some time, anyway, so I unlocked the bootloader and flashed JellyBean. And it worked. I was proud. Then one month later, today, it froze again. I can do the same procedure, and lose all my data again, but I fear the problem will remain unsolved and it will freeze/crash/explode one month from now. Can someone help me figure out what my problem is, or give an alternate solution to try?
TL;DR:
my razr i was stuck on the intel logo screen, I unlocked the bootloader and flashed JB, it worked, one month later it is now stuck on the WARNING BOOTLOADER UNLOCKED screen. Please help thank you.