Database Develop

[Q] Bricked Milestone, stuck at Motorola logo

Hi,
I managed to brick my Milestone, terminally I'm afraid, but the symptoms are different than what I see around the forum so they might interest someone else.
So, I first backed up everything with GOT Nandroid and Titanium Backup then modded CyanogenMod 7 RC4 0.08-11.04.05 (Android 2.3.3) successfully, except that the SIM was locked and would not unlock, although it works in another phone. This was a bug supposedly fixed in version 6 of Cyanogen...
Browsing the forums, the only thing that made a bit of sense was that maybe the GSM frequency was set to the wrong value. There is a Nandroid mod (but not GOT) that allows you to change that so I entered GOT Nandroid again. Since it had no such option, I Rebooted. Then, the fun begun.
The phone got stuck on the Motorola logo and no button, not even Power, worked anymore. After waiting for many minutes with no progress, I took out the battery - that made a change , the phone shut down. I then put it back - the phone immediatelly, no, instantly, cause there's no delay as when you were powering it up, lights up with the same Motorola logo. Tried several times, always the same behavior.
I left it booting (but also connected to the charger) for a whole night, no change.
The phone is not seen by the PC when connected to USB. It won't reboot, normally or to recovery. Buttons won't work at all. Yeah, tried with or without the SIM and the sdcard, no change. Tried to start without battery, just the charger, doesn't work.
Useless to say, I am getting bored of that Motorola logo
I suspect that the bootloader in the internal memory got corrupted. Can this be flashed even if the device is not seen by the PC (I mean by the RDSLite installed on it)?
Cheers

When the charger is connected to the phone try at the same timeull out and pull in the battery while holding the buttons who will get you in the OR

Yup, it worked. So first I got the battery with a question mark. Then I put in the battery and I got a battery at 60%. Since I was holding Power+Camera, it continued to the Recovery mode and now I have a working Milestone with Cyanogen mod!!
Thank you a lot, Mikicishte.
I still have to see about the initial locked SIM problem... but that will be mostly fun.

florinadrian said:
I still have to see about the initial locked SIM problem... but that will be mostly fun.
Click to expand...
Click to collapse
Have you tried to factory reset the Milestone, to see if after that the SIM is accessible again ?
http://forum.cyanogenmod.com/topic/14099-sim-card-not-detected-after-factory-reset/
You could try also to install a logger application catlog for example (https://market.android.com/details?id=com.nolanlawson.logcat&feature=search_result ) to see in the logs if you can find out more details to help you with the investigations...

I did the factory reset as part of installing the mod.
Even if the post quoted reports the wipe as the source of the problem and not as a solution, I just wiped again with no good result.
Will try catlog.

florinadrian said:
I did the factory reset as part of installing the mod.
Even if the post quoted reports the wipe as the source of the problem and not as a solution, I just wiped again with no good result.
Will try catlog.
Click to expand...
Click to collapse
or maybe you could try to use an unlock tool to see what error is reporting
https://market.android.com/details?id=com.droidgram.bladeunlock&feature=search_result

Problem! The process com.android.phone has stopped unexpectedly

I already read some other threads with the same name but nothing really like my problem.
I inserted another person's sim card and after i turned on the phone it started giving me "Sorry! The process com.android.phone has stopped unexpectedly... Force Close. "
But its showing up all the time, one after another. I press Force Close and then another pops up. I can';t even navigate in my phone, i can't do anything but turn it off.
Basiclly i am stuck with 400 euro, phone that just gives errors and is totally unusable.
My phone has stock software, not rooted.
When I got the phone I was so happy...and soon the bsod problems started and I was forced to buy a new one (I see what you did there LG) - but i chose Sony Ericsson this time.

Try to root your phone and install a Clockwork Recovery. Then from the Advanced menu in the recovery choose Fix permissions. Restart the phone and see if it is fixed. If it isn't just flash a custom ROM. This will probably do the job.

This might be a hardware problem or a software problem. Since you didn't root the device you can just go back to the store and ask them to repair it or send it to LG or whatever they can do (because you still have your warranty... right?). Why didn't you go back to the store in the first place?
Sent from my LG-P990 using Tapatalk

The problem is after i click on Force Close, it gives me another error too fast and i can't click on anything(I can't really install or use any app). Its like windows errors when you get one error like thousand times and you keep on clicking and clicking and there's no end.
Restarting the phone does nothing.
And yes I already talked with support and Im going to give it back for repair. I don't think its a hardware problem, its the crappy software LG made. I didn't send it back because I could live with 3-4 bsod per week, but now that... Plus im from Bulgaria and the user above knows how long it takes to get your phone back

Okay. Then, try these steps. You don't need to install anything on your phone. You will install a new stock firmware using smartflash. I think this is the only way to fix your phone in a situation like this. Follow the steps:
1. Download Smartflash and its drivers from here and after that install the drivers.
2. Now choose a firmware from here and download it.
3. Run the SmartFlashTool_P990.exe executable.
4. Turn off the phone, remove battery, plug USB in and hold the Power + Volume down keys until you see the software update message - the COM ports field in the SmartFlash program will be filled in automatically
5. Now follow this image:
There is a video lesson too.
Source - (bulgarian, вж. точка 5.2)
Всичко това се надявам да оправи проблема ти. След като инсталираш стоковия ROM и всичко е успешно, ако ти се занимава си сложи някой от последните GR Leak Custom-и. Успех

Same Problem
Hi, I have the same problem on my Samsung SGT5830(Galaxy ACE), but it pups up ones or twice, and stop puping up... My phone after that, working whitout problems... I can receive calls, sms, mms. Also I can call, send sms, mms... I can connect on WiFi, GPS is working too... What is a problem? What can I do? How to do it?

Yes do what gkostadinov said and that will fix your phone back to stock, then root and flash clockworkmod recovery you can use the clockworkmod app from android market to do this once you have rooted.
The pick a nice fast custom rom and profit.

extremecupavac said:
Hi, I have the same problem on my Samsung SGT5830(Galaxy ACE), but it pups up ones or twice, and stop puping up... My phone after that, working whitout problems... I can receive calls, sms, mms. Also I can call, send sms, mms... I can connect on WiFi, GPS is working too... What is a problem? What can I do? How to do it?
Click to expand...
Click to collapse
Id suggest using the samsung pc studio(I dont know if it does but there should be some support on updating the phone software) to flash stock rom. Or flash a custom rom if you prefer. If you are able to use the phone and click on the screen then its not a problem to do so.
This is your forum - http://forum.xda-developers.com/forumdisplay.php?f=1167
I think you will find all the information on rooting, flashing and so on.
My problem was different as my phone was basically unable to do anything.
I had it returned to service as I didnt saw gkostadinov reply on time.

Same happened for me some time back. It was caused by google+. try uninstalling and re-installing the google+ app from the market.

I once used hp kernel rc11 and got the same issues. I just reflashed it with the stable version (sr2). Problem solved.

I get this issue when ever I try to toggle between 2G/3g OR toggle data. I am on the latest Cm7 nightly and recently flashed vadonka's 32M_S kernel . This problem occurred some times randomly while on the Cm7 kernel but now it happens almost all the time when I toggle 2G/3G . @vadonka: I can help you with the logs if you wish to look into this

same prroblem in lg optimus l3 e400
i rooted my phone and installed annobox11 then it was working very good from 3-4months from yesterday my battey got low and turned off when i tuurned itt on after charging it is continuesly saying ''unfortunately process com.android.phone has stopped'' pls help me i again reinstalled rom but now also same problem

reinstal rom

[Q] Random soft-reboots (Stock 1.205, root)

Hi guys,
My phone is experiencing random soft reboots (reboots without a need to type in simcard PIN) during the day. It happens totally randomly, sometimes 3 times a day, sometimes not once in a couple of days. Sometimes when I use it, sometimes when it's idle on the table.
I'm running stock JB 4.3 A.1.205, LB, Towel-rooted, no custom recovery (I tried some previously and they were givig me all sorts of trouble, so I downloaded fresh official ROM and Towel).
I've been trying to track down the process that causes reboots, I temporarily uninstalled Xposed framework but it still ocurred.
Is this a known issue? Is there a better way to check what is causing that (perhaps in some log file)?
Thanks in advance,
Regards,
Michal

niedzwiedz102 said:
Hi guys,
My phone is experiencing random soft reboots (reboots without a need to type in simcard PIN) during the day. It happens totally randomly, sometimes 3 times a day, sometimes not once in a couple of days. Sometimes when I use it, sometimes when it's idle on the table.
I'm running stock JB 4.3 A.1.205, LB, Towel-rooted, no custom recovery (I tried some previously and they were givig me all sorts of trouble, so I downloaded fresh official ROM and Towel).
I've been trying to track down the process that causes reboots, I temporarily uninstalled Xposed framework but it still ocurred.
Is this a known issue? Is there a better way to check what is causing that (perhaps in some log file)?
Thanks in advance,
Regards,
Michal
Click to expand...
Click to collapse
Try with hard reset or try to flash another stock ftf

Thanks, but the reset doens't seem to change much, it occurs anyway.
I'd rather avoid changing rom again, as I said I just recently installed clear stock offcial rom via PCC and only towel-rooted it.
Any ideas how I could try to track the fault process?

niedzwiedz102 said:
Thanks, but the reset doens't seem to change much, it occurs anyway.
I'd rather avoid changing rom again, as I said I just recently installed clear stock offcial rom via PCC and only towel-rooted it.
Any ideas how I could try to track the fault process?
Click to expand...
Click to collapse
I would have said it´s because of the xposed framework if you haven´t said you uninstalled it once. I had the same problem once, and I was kind of sure that it´s because of some gravitybox settings which gave trouble.
I recommend you to uninstall the xposed framwork once again, reboot and give it a try

Crash...X said:
I would have said it´s because of the xposed framework if you haven´t said you uninstalled it once. I had the same problem once, and I was kind of sure that it´s because of some gravitybox settings which gave trouble.
I recommend you to uninstall the xposed framwork once again, reboot and give it a try
Click to expand...
Click to collapse
Well, I'll give it a go, however I did it before and the reboots occurred anyway... I'm now slowly uninstalling all the apps one by one to see when this craziness stops
I'm starting to suspect that it's a fault of Google Play Services, they're always on high positions in my Wakelock and Battery Usage lists, I heard people are also having some other problem with this app.
Edit:
Another thing is that I try to modify something in AppOps (I'm accessing it via some shortcut apps from the Store), but I cannot change permanently any settings (I click back, then enter again some app and it's all 'allowed' again), is this normal?

I'm digging up an old thread, but I narrowed down my problem to Stamina Mode, I think.
I wiped all data via factory reset, reinstalled clean system via PCCompanion and only townel-rooted. The soft-resets began to appear again shortly after first boot. I tried to eliminate differet things and it seems that the reboots occur only when Stamina Mode is on. I've switched it off like a week ago and the phone has been running smooth ever since.
Now I'm just asking out of pure curiosity, has anyone ever stumbled upon similar problem? Is Stamina Mode known for causing any issues of this kind?

[Q]Suddenly shutdowns on MI3 Need help

I'm using mi3 with Euphoria-OS 0509 version. My phone will suddenly shutdown itself even the battery is full.
I tried re-flash this ROM, but no help.
It happens every time when I use the phone in no time. But It won't happen when charging.

Maybe there's a problem on your phone's battery. Try to bring it on a service center.

error01671 said:
I'm using mi3 with Euphoria-OS 0509 version. My phone will suddenly shutdown itself even the battery is full.
I tried re-flash this ROM, but no help.
It happens every time when I use the phone in no time. But It won't happen when charging.
Click to expand...
Click to collapse
What do you mean by "suddenly shutdown itself"?
Do you see 1) the closing down routine? Or 2) does the phone simply not respond to pressing the power button?
If it's 2), plenty of ROMs exhibit the "screen OFF death", where the phone is actually still active but you can't get the screen to light up. try flashing another ROM. Paranoid Android is the most stable ROM for me.
If it's 1), still try flashing another ROM, and it it is still closing down, it's a hardware issue (hopefully battery), so service centre time.

paul c said:
What do you mean by "suddenly shutdown itself"?
Do you see 1) the closing down routine? Or 2) does the phone simply not respond to pressing the power button?
If it's 2), plenty of ROMs exhibit the "screen OFF death", where the phone is actually still active but you can't get the screen to light up. try flashing another ROM. Paranoid Android is the most stable ROM for me.
If it's 1), still try flashing another ROM, and it it is still closing down, it's a hardware issue (hopefully battery), so service centre time.
Click to expand...
Click to collapse
In my case, my phone's screen will suddenly frozen while I'm using, and turn off itself. I need to hard reboot the phone. I used flashed this rom few months ago and change to PAC rom, no such problem until I flash this rom again, all roms were clean flash and the battery was calibrated. So I think it might be the hardware problem.

error01671 said:
In my case, my phone's screen will suddenly frozen while I'm using, and turn off itself. I need to hard reboot the phone. I used flashed this rom few months ago and change to PAC rom, no such problem until I flash this rom again, all roms were clean flash and the battery was calibrated. So I think it might be the hardware problem.
Click to expand...
Click to collapse
Well, if the phone was OK with a different ROM, that implies your current ROM is the problem - try another one.
I recall having had the same behaviour in the past, when I was trying a lot of ROMs in quick succession - so I don't know which one(s) it was.
All the same, it doesn't sound like hardware/battery. Make a Nandroid backup in recovery, then flash eg PAC ROM or Paranoid Android - wait a day before adding all your apps etc - and see if you get that issue again.

paul c said:
Well, if the phone was OK with a different ROM, that implies your current ROM is the problem - try another one.
I recall having had the same behaviour in the past, when I was trying a lot of ROMs in quick succession - so I don't know which one(s) it was.
All the same, it doesn't sound like hardware/battery. Make a Nandroid backup in recovery, then flash eg PAC ROM or Paranoid Android - wait a day before adding all your apps etc - and see if you get that issue again.
Click to expand...
Click to collapse
OK, I got some conclusions, and it might be a hardware problem.
First, I replaced the battery with same ROM, it still got SOD.
Then I flash Omni, PAC, Euphoria-OS, all got SOD like before.
So I return to MIUI, no SOD, but I got random reboots and sometimes Wi-Fi will disconnect itself even in its range.
Now I'm using Ivan's AOSP, still got random reboots and Wi-Fi problem.
And now I need this phone to work because I don't have a backup, waiting for new Nexus!!

T mobile note 4 restart, and power issues

I have had my Sm-N910T for about a year now. When I first got it I rooted it without thinking it through. I used Odin and flashed cf autoroot. I unrooted it when it started giving me issues. Then it would restart, freeze, etc. I now have an app called wakelock and it prevents my phone from turning off. It works great it has the original firmware that installed through Samsung kies but when I try to restart it just shuts down. When I power off I can't always power back on right away. I have to pull the battery and hold the power button for 1 minutes release, then put the battery back in and it works again. I have put the original firmware and it is not rooted anymore. Is there any way I can fix this issue? So basically it works fine but if I turn it off I have to pull the battery to be able to turn it back on. Every once and awhile it'll go into download mode on its own too.

Enalay527 said:
I have had my Sm-N910T for about a year now. When I first got it I rooted it without thinking it through. I used Odin and flashed cf autoroot. I unrooted it when it started giving me issues. Then it would restart, freeze, etc. I now have an app called wakelock and it prevents my phone from turning off. It works great it has the original firmware that installed through Samsung kies but when I try to restart it just shuts down. When I power off I can't always power back on right away. I have to pull the battery and hold the power button for 1 minutes release, then put the battery back in and it works again. I have put the original firmware and it is not rooted anymore. Is there any way I can fix this issue? So basically it works fine but if I turn it off I have to pull the battery to be able to turn it back on. Every once and awhile it'll go into download mode on its own too.
Click to expand...
Click to collapse
Hi,
I have reported this thread to be moved to the right Q & A section where you might be able to get help quickly.
-Vatsal

Enalay527 said:
I have had my Sm-N910T for about a year now. When I first got it I rooted it without thinking it through. I used Odin and flashed cf autoroot. I unrooted it when it started giving me issues. Then it would restart, freeze, etc. I now have an app called wakelock and it prevents my phone from turning off. It works great it has the original firmware that installed through Samsung kies but when I try to restart it just shuts down. When I power off I can't always power back on right away. I have to pull the battery and hold the power button for 1 minutes release, then put the battery back in and it works again. I have put the original firmware and it is not rooted anymore. Is there any way I can fix this issue? So basically it works fine but if I turn it off I have to pull the battery to be able to turn it back on. Every once and awhile it'll go into download mode on its own too.
Click to expand...
Click to collapse
sounds like the same software issue I had. Idk what happened but the internal memory failed on my note 4. Have you experienced constant freeze ups? also have you gone into download mode with an error that says "mmc_failed can't boot"? It was something along the lines of that.

Re:
alfadog77 said:
sounds like the same software issue I had. Idk what happened but the internal memory failed on my note 4. Have you experienced constant freeze ups? also have you gone into download mode with an error that says "mmc_failed can't boot"? It was something along the lines of that.
Click to expand...
Click to collapse
Yes I have those same issues. I am getting a new phone but I have to give this one to someone else and I need it in good shape to give it to them. Do I need to just buy a replacement or is there any way I can get it fixed?

Enalay527 said:
Yes I have those same issues. I am getting a new phone but I have to give this one to someone else and I need it in good shape to give it to them. Do I need to just buy a replacement or is there any way I can get it fixed?
Click to expand...
Click to collapse
Have you tried to update to the latest firmware? DOK2 fixes a lot of issues including the memory leak.
Sent from my SM-N910T using Tapatalk

aaldiar said:
Have you tried to update to the latest firmware? DOK2 fixes a lot of issues including the memory leak.
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
I updated it ota then on Samsung kies with the latest firmware. Everything works fine except the power off issues.

I think this is a common 5.0.1 issue, same thing started happening to me after update. Gotta wait for update or back to 4.4.4.

Enalay527 said:
I have had my Sm-N910T for about a year now. When I first got it I rooted it without thinking it through. I used Odin and flashed cf autoroot. I unrooted it when it started giving me issues. Then it would restart, freeze, etc. I now have an app called wakelock and it prevents my phone from turning off. It works great it has the original firmware that installed through Samsung kies but when I try to restart it just shuts down. When I power off I can't always power back on right away. I have to pull the battery and hold the power button for 1 minutes release, then put the battery back in and it works again. I have put the original firmware and it is not rooted anymore. Is there any way I can fix this issue? So basically it works fine but if I turn it off I have to pull the battery to be able to turn it back on. Every once and awhile it'll go into download mode on its own too.
Click to expand...
Click to collapse
I would recommend downloading the full DOK2 firmware. You can find it in the below linked thread. Make sure you use the newest version of ODIN to flash it 3.10.7.
It should give the phone aq complete clean install of the firmware. Kies sometimes can be janky. It you are going to get rid of the phone the best is to do a full ODIN flash.
http://forum.xda-developers.com/note-4-tmobile/development/mirror-stock-tw-t3260858

I been having the same issues ...even with full firmware flashed DOK2....I get internal memory failure. Hope someone finds a fix. Have to pull out battery, sim cards, and spen, then press all the buttons, thennnnn....put everything back to boot up. Power button won't work, and reboot won't reboot. It Just turns off. Sucks...I love this phone. Right now it's acting ok...occasionally I get freezes and major lag. Someone please help!

notufatjesus said:
I been having the same issues ...even with full firmware flashed DOK2....I get internal memory failure. Hope someone finds a fix. Have to pull out battery, sim cards, and spen, then press all the buttons, thennnnn....put everything back to boot up. Power button won't work, and reboot won't reboot. It Just turns off. Sucks...I love this phone. Right now it's acting ok...occasionally I get freezes and major lag. Someone please help!
Click to expand...
Click to collapse
I had this problem too except it got really really laggy and would constantly reboot anytime I tried to do anything. Best I could figure out was it was a problem with the internal sd. Called TMO tech support, told them I did factory reset, tried it without the sd card, blah blah blah. I said it's a hardware issue that is beyond my control and I don't feel like I should have to pay for it. They said well it sounds like you already did the work for us. I guess it was still under warranty but I got a new phone the next day and no problems since. Hopefully whatever was wrong they have fixed the issue by now but so far so good.
Definitely mention the mmc read fail error or whatever it says. All it cost me was a $5 charge. Give em a call.

I have the same problem, and it only happen when I update the phone to newest firwame, DOK2.
When I use COG1 firwame it very fast and easy use. but when I update DOK2 over Odin, I few very lag and usually restart the phone when I run a big application, then It can't restart after, just turn off.
And after that, can't turn on the phone. I had remove pin in 10s, pull in and it power on normal.
Sometime I turn on the power and the phone go into download mode with notice "mmc_fail can't boot".
Now I just only want to download my phone to old firwame, COG2 and use it normal, but the new firwame with new bootloader don't allow to download old bootloader. So sad
anyone can't show me how to download to COG2 firwame, Please....

tony yayo said:
I had this problem too except it got really really laggy and would constantly reboot anytime I tried to do anything. Best I could figure out was it was a problem with the internal sd. Called TMO tech support, told them I did factory reset, tried it without the sd card, blah blah blah. I said it's a hardware issue that is beyond my control and I don't feel like I should have to pay for it. They said well it sounds like you already did the work for us. I guess it was still under warranty but I got a new phone the next day and no problems since. Hopefully whatever was wrong they have fixed the issue by now but so far so good.
Definitely mention the mmc read fail error or whatever it says. All it cost me was a $5 charge. Give em a call.
Click to expand...
Click to collapse
Hello there, I'm having the same exact issue lately, phone is a Year old, and I think its failing, One question though!
Was your phone ever rooted? mine is, but I flashed the Stock DOK2, so its official with NO root now, but I think the Device status is CUSTOM not official, Also KNOX has tripped while rooting, would T Mobile honor a replacement? At least its on the Official OS with NO Root now.
Please enlighten me

Willy318is said:
Hello there, I'm having the same exact issue lately, phone is a Year old, and I think its failing, One question though!
Was your phone ever rooted? mine is, but I flashed the Stock DOK2, so its official with NO root now, but I think the Device status is CUSTOM not official, Also KNOX has tripped while rooting, would T Mobile honor a replacement? At least its on the Official OS with NO Root now.
Please enlighten me
Click to expand...
Click to collapse
Not really sure. Mine was never rooted. I've heard of plenty of people sending their rooted phones in with no problem.

thiennvbk said:
I have the same problem, and it only happen when I update the phone to newest firwame, DOK2.
When I use COG1 firwame it very fast and easy use. but when I update DOK2 over Odin, I few very lag and usually restart the phone when I run a big application, then It can't restart after, just turn off.
And after that, can't turn on the phone. I had remove pin in 10s, pull in and it power on normal.
Sometime I turn on the power and the phone go into download mode with notice "mmc_fail can't boot".
Now I just only want to download my phone to old firwame, COG2 and use it normal, but the new firwame with new bootloader don't allow to download old bootloader. So sad
anyone can't show me how to download to COG2 firwame, Please....
Click to expand...
Click to collapse
Make sure you are using the ODIN version 3.10.7 if you are using an older version of may be what caused the issue.
If you did use the newest Odin, then I would factory reset your device, but into twrp and wipe everything but external SD Card, boot back into download mode and flash the firmware again. Most likely a few files for messed up during your Odin flash and it messed up the process. Also make sure you are using the USB cord that came with the device.

I found the fix for this mmc_failed. Making a new thread for this.
---------- Post added at 06:11 AM ---------- Previous post was at 05:38 AM ----------
http://forum.xda-developers.com/showthread.php?t=3277144
Here's is the fix. Don't forget to hit Thanks button