Database Develop

Phone suddenly acting up need some help

I rooted my droid 4 a few months ago when I first got it so I could tether. I removed a couple of programs using titanium backup (blockbuster app and some other bloat). Phone worked fine until monday when the touchscreen stopped working. I did a reboot (power + volume down) whereupon it just sat at the M "Dual Core" logo. I tried booting into the recovery menu but selecting "recovery" didn't do anything - it would just hang.
Last night I was able to get it working again by going into the recovery menu and selecting asp fastboot, then using RSDLite to push a stock Droid 4 ROM onto the phone. However, it didn't wipe my old system, and didnt install over it either because all my files were there, and the programs I removed were still gone. So the phone worked for a few hours then the touchscreen stopped working again.
I repeated the process with RSDLite and after a few failed attempts where the phone would hang while booting, I finally got it to boot into the OS again. And this is where I am at now.
I am pretty sure that the problem is related to the OS that is on the phone now and that I need to wipe the phone and start fresh with either a custom ROM or the stock D4 ROM. The problem is that I can't get recovery to do a factory reset. As I mentioned above, recovery just hangs and doesn't do anything. I am reasonably literate when it comes to this stuff but I get really confused because there are so many different ways that people seem to do this stuff (safestrap, bootstrap, CM( etc). I would love to try CM9 but my priority right now is just to have a phone that works. Any help would be greatly appreciated.
Thanks.

whoisthisis said:
I rooted my droid 4 a few months ago when I first got it so I could tether. I removed a couple of programs using titanium backup (blockbuster app and some other bloat). Phone worked fine until monday when the touchscreen stopped working. I did a reboot (power + volume down) whereupon it just sat at the M "Dual Core" logo. I tried booting into the recovery menu but selecting "recovery" didn't do anything - it would just hang.
Last night I was able to get it working again by going into the recovery menu and selecting asp fastboot, then using RSDLite to push a stock Droid 4 ROM onto the phone. However, it didn't wipe my old system, and didnt install over it either because all my files were there, and the programs I removed were still gone. So the phone worked for a few hours then the touchscreen stopped working again.
I repeated the process with RSDLite and after a few failed attempts where the phone would hang while booting, I finally got it to boot into the OS again. And this is where I am at now.
I am pretty sure that the problem is related to the OS that is on the phone now and that I need to wipe the phone and start fresh with either a custom ROM or the stock D4 ROM. The problem is that I can't get recovery to do a factory reset. As I mentioned above, recovery just hangs and doesn't do anything. I am reasonably literate when it comes to this stuff but I get really confused because there are so many different ways that people seem to do this stuff (safestrap, bootstrap, CM( etc). I would love to try CM9 but my priority right now is just to have a phone that works. Any help would be greatly appreciated.
Thanks.
Click to expand...
Click to collapse
select recovery by holding the vol buttons and power on boot just like fastboot. press vol - for recovery. when u see dead droid hit both vol up and vol down and theres the recovery

Thanks, I was finally able to get into recovery. Wiped data and did a factory reset which again got stuck at the logo screen. Went back into fastboot and ran RSDlite again to flash the stock ROM which gets me to the "Welcome to Droid4" screen where it says "touch the android to start" but the touchscreen is unresponsive. Starting to think there is something physically wrong with the phone....

send it to motorola, I've heard their customer support is pretty good. but if you voided your warranty by rooting/flashing other roms, I've heard bricking the phone and sending it in works to get a new one too

The only way I can send it back is through an insurance claim so I am trying to save myself $75j if this thing will just work. I just did a reboot and now the touchscreen seems to be working so I am going through the setup process....so weird.
Update: I was able to get the phone to load up and configured my google account etc. It appears that the phone is now running on completely stock installation of OS.....

whoisthisis said:
The only way I can send it back is through an insurance claim so I am trying to save myself $75j if this thing will just work. I just did a reboot and now the touchscreen seems to be working so I am going through the setup process....so weird.
Update: I was able to get the phone to load up and configured my google account etc. It appears that the phone is now running on completely stock installation of OS.....
Click to expand...
Click to collapse
So it has been a couple days now and the phone works totally fine. It looks like the problem was that by removing whatever bloatware that I did, the phone's OS got borked when VZW pushed an update of some kind. Flashing the stock ROM without doing a factory wipe would temporarily solve the problem but eventually the update would get pushed again and the whole thing would lock up again. The factory wipe + reinstall seems to have been the solution to the problem.

Bricked my Amazon fire 5th gen

Hey guys, after successfully changing my OS to cyanogenmod I wanted to do the same on a second amazon fire 5th gen I had laying around. So I rooted it, installed the google apps, downloaded Flashfire from the google play store, but when I used flashfire to flash the most recent CM12.1 from the XDA thread it kept saying that the data was incompatible or something. So I tried doing a factory reset and tried again, but the same thing kept occurring. After that I thought I would try installing the SlimLP mod instead, and it worked. Once I got SlimLP up and running I downloaded Flashfire again, and went to go install CM12.1 once again, but this time it got stuck at the very beginning. It didn't even look like it was writing any data or anything. The whole process only took about a minute on my other amazon fire, so I knew something was wrong. I waited 15-30 mins and no change. Eventually I turned it off, and rebooted, hoping for the best. Unfortunately, it loads the CM boot logo, and just gets stuck their permanently. I tried going into boot recovery by holding down volume down, and the power button, but when I do that it gets stuck at the amazon boot logo. I can still get it to boot into fastboot by holding down the volume up and power button, but when I try to flash a recovery image using fastboot it says that Flashing images is locked, or something.
Can someone tell me if there is still anyway to save it?

This will work
Hi
So i have the same tablet as you do and i faced the same problem as well and i found a way to fix it and this is what i did-
1) I went to recovery mode ( Power button and volume up button at same time) and factory reset and cleared data.
2) Wipe cache patition
3) Then I used this tutorial so i can go back to original state
4) Once there, I rooted my tablet again and download google play store and blahh balhh
5) Then I downloaded flashfire apk
6) This time i didn't download latest CM 12.1 for the tablet but this one ( cm-12.1-20151230-R01-UNOFFICIAL-ford.zip )
7) And gapps
8) I flashed and it worked beautifully.
9) Once done then I flashed the latest version CM 12.1 for the tablet and it worked amazingly . Sorry for not providing the links because i am new and i still have to wait a bit longer Thanks for reading this and i can guarantee 99.9% this work. Don't forget to tell me what happened.

Yeah, but like I said, the device freezes before it can get into recovery mode. I can only get into fastboot, but I don't think there is anything I can do with that.

speaker1264 said:
Yeah, but like I said, the device freezes before it can get into recovery mode. I can only get into fastboot, but I don't think there is anything I can do with that.
Click to expand...
Click to collapse
Return it to Amazon. I rang them and basically claimed ignorance that the device had stopped working, they sent me another one (and I returned the 'bricked' one). Luckily the replacement one came with 5.0.1 so I carefully made sure I did not upgrade before replacing the ROM instance with CM12.1.

jeromeof said:
Return it to Amazon. I rang them and basically claimed ignorance that the device had stopped working, they sent me another one (and I returned the 'bricked' one). Luckily the replacement one came with 5.0.1 so I carefully made sure I did not upgrade before replacing the ROM instance with CM12.1.
Click to expand...
Click to collapse
exactly the same thing happened to me as in the op. there is absolutely no way to fix it with the bootloader being locked down. i filed a replacement, telling them that after i installed a program it no longer goes past the boot screen. (i call that a grey area as far as lies go). go through their little trouble shooting performance where they ask if the device is charged.... then they will replace the device as long as it is in the warranty period. drop the old one off at ups, and 2 days later you will get the new one in the mail.

Note 5 stuck in loop while updating firmware at %24

Hi All,
Sorry if this is asked before. I have a new Note 5 unlocked. I turned it on yesterday and started using it. Late at night, its screen froze. I tried pressing Power+Volume_Down buttons to restart the phone. The phone restarted but the the screen was black. Only the notification light was on (blue).
In the morning, the light was still on and the phone was froze. I tried restarting it and I succeeded it. Then I realized the phone was very, I mean veeeery slow. By the time, a firmware update notification popped up. I believe it was Marsmallow update. I hit the yes button. The phone started the update and was stuck at %24. Then it restarted itself. The update process starts over and when it reaches %24, it starts over.
This happened before with my note 4 when I tried to root it. This phone is brand new and is not rooted. However, I transferred my Google profile but I did not select to download my previous apps. So, I don't think it is rooting issue but stucking at the same percentage makes me nervous.
I tried to get into recovery mode but the button combination does not work at all. So I can neither factory reset nor clear the cahe partition. When I press Volume_Down+Home+Power buttons, a custom rom download screen appears but Volume_Up+Home+Power buttons do not work at all. I cannot shut off the phone. It constantly restarts itself, starts the update, fails at %24 and starts the process over again.
What might be the problem? How can I fix this?
Regards

Hi,
Try flashing some stockfirmware via Odin (ideally something of the same android version i.e. lollipop/marshmallow). Once it's installed you should be able to access recovery from which I strongly recommend clearing your cache afterwards as you've already suggested. If you are not worried about loosing any data, then flash new firmware that is inclusive of BL/CP/CSC files too (each one has a category for such in Odin). With the latter, by all means flash marshmallow etc. :good:
Regards

Stuck on AT&T logo and cannot enter recovery mode

This is my first post, but I've had my phone rooted for a few months now with no problems until today out of the blue. What I've done to root my phone in the first place was flash to 4.4.2 NE3, root it, then upgrade to 5.0.1 OC 7 DeOdexed while keeping the root according to the link below. And then I put Xposed framework on it.
https://forum.xda-developers.com/galaxy-s4-active/general/how-to-update-to-i537oc6-5-0-1-t3089355
And this has worked well for me for a few months since that was back at the end of December. Flash forward to today when my phone was being rather slow to respond to my actions so I decided to restart it. And upon restarting it, it's been stuck on the AT&T logo screen for a very long time. I can power it down with the power button, but think it actually just restarts it because then it boot ups again on its own. I cannot enter recovery mode with power+home+volume up, but I can get to the custom OS screen with power+volume down. My computer cannot see it as an adb device either. I've also tried removing the SIM card and the SD card and it's still gets stuck at the AT&T logo.
I've done nothing different with the OS or Xposed recently. The only new thing was about 2 hours prior to restarting it, I connected it to my computer to transfer some video files to the sd card. While I had it connecting to the computer and looking at the files on it through the phone's My Apps, it was sluggish to respond to my actions. But after disconnecting it, it was fine. I don't know if this is related, but I haven't done anything else different with it. Is there anyway to get my phone to boot up correctly? Or am I going to have to reflash it all over again? Thank you for any help.
Edit: I can enter recovery mode and I tried wiping the cache. It still gets stuck at the AT&T logo screen. I should also note that it no longer shows the Samsung "custom" boot screen anymore like it used to after rooting, now it just has the default Samsung boot screen, so it would certainly seem like my OS has been corrupted.

Phone do not boot after Oreo update

As i installed update and clicked reboot to apply it, now my system do not boot. Phone always stuck on white NOKIA logo boot screen forever. I tried few times to restart it via VOL-UP + POWER, but it always have same result - never boots. Please give me advice how to deal with it

It happened to me too, in December already. Mobile is in service now.
They flashed original fw, tested and returned it with results no fault. Right after switch on and new Oreo update it starts to freeze and produce various mistakes again, so I have returned phone to service. Will complain with seller about exchange.

ravkhar said:
It happened to me too, in December already. Mobile is in service now.
They flashed original fw, tested and returned it with results no fault. Right after switch on and new Oreo update it starts to freeze and produce various mistakes again, so I have returned phone to service. Will complain with seller about exchange.
Click to expand...
Click to collapse
That really sucks. But what do you mean by various mistakes? Like your system boots, but some functionality is not working? As i said in my case it totally cannot boot and recovery mode i can't enter factory recovery mode by VOLUME UP + POWER on start.

gornex said:
That really sucks. But what do you mean by various mistakes? Like your system boots, but some functionality is not working? As i said in my case it totally cannot boot and recovery mode i can't enter factory recovery mode by VOLUME UP + POWER on start.
Click to expand...
Click to collapse
Ach yes, sorry. First it stucked in logo Nokia and rebooting again... VolumeUp+Power does not work normally on Nokia.
It helped procedure found here:
https://forum.xda-developers.com/showpost.php?p=74406267&postcount=34
Then I was able to make factory reset and mobile booted, but worked with various faults.

Did you unlock your bootloader , flashed TWRP and then changed the slot? Slot A to B or vice versa?
If so, then the solution is
How to solve!
I simply waited until the battery ran out
When battery was completely dead and no Nokia-logo appear any more >>
Then I charged the battery 3% juice without booting
and from there I entered recovery-mode with the help of a USB cable.
Holding the volume+ button while connecting the USB-cable
From TWRP-recovery I changed to the other inactive slot
and whooala, that's it!
Edit: I sucked the juice (mAh electric-capasity) out of the battery quicker with help of OTG-cable and an external USB-powerd fan.
Use almost any external max 5volt USB-powered devices available at home, even charging another phone unless the second phone doesn't reverse-charge, this Nokia can be used as a power-bank.