Database Develop

[HELP!] Milestone stuck at M logo

Please Help!
Yesterday, my Milestone crashed while using the camera, tried to reboot and got stuck at the M logo.
I CAN NOT access recovery, it sticks at the M logo.
Tried reflashing using RSDLite using both Service and Non-Service ROMS, it appears to work OK, gets to where the phone reboots, the phone stays at the M logo and RSDLite says manually reboot phone. If I reboot to bootloader mode, RSDLite says PASS, but rebooting the phone stays at the M logo.
I was running GOT's SHOLS_U2_02.36.0, Rooted, Overclock (800mhz), Memhack.
I also tried reflashing the bootloader, both 90.73 (my original), also 90.78 (just in case the camera button was broken and was the reason I couldn't access recovery). Same result, stuck at M logo.
Also, if I plug the Milestone into the Wall charger, it sticks at the M logo, I don't get the recharging logo.
I have also tried reflashing the both the SIM card and SDCard removed, still stuck at the M logo and cant get to recovery.
Please help, if anyone has any ideas, this is driving me absolutely crazy.

Hi there,
I got this problem when I flashing the milestone back to offical ROMs using RSD method. Also stuck at the M logo no matter uplung the battery or using the recovery mode.
I solved this by wipe the data and cache in the recovery mode then reboot.......everything works fine. Hope this help!!

sunnylai01 said:
Hi there,
I got this problem when I flashing the milestone back to offical ROMs using RSD method. Also stuck at the M logo no matter uplung the battery or using the recovery mode.
I solved this by wipe the data and cache in the recovery mode then reboot.......everything works fine. Hope this help!!
Click to expand...
Click to collapse
Thanks for the info, but my problem is I can not get into recovery to wipe data and cache. Everytime I try to boot into recovery, it just gets stuck at the M logo.

Did you mean when you plug the battery in,it bootup automatically?
If so, press the carmera button before you plug the battery in,it will boot into recovery mode.
Hope this help.

sunnylai01 said:
Did you mean when you plug the battery in,it bootup automatically?
If so, press the carmera button before you plug the battery in,it will boot into recovery mode.
Hope this help.
Click to expand...
Click to collapse
When I put it the battery, it tries to boot automatically. I had already tried what you suggested, that's the method I can use to access the bootloader menu for flashing. Also, if you pull out the SIM card, the phone doesn't automatically start to boot, I tried that method with power and camera buttons, but didn't work either.
No matter what I try, it won't let me boot into recovery mode. I am sure that if I could access recovery mode, I could wipe data and davlik cache and this would fix my problem.
The only thing I can access is the Bootloader menu (power switch and Up on the keyboard) for flashing with RSDLite.

I am having this problem too. Is there a true fix for this???

Did you tried starting the milestone without battery? When the great battery appears you can put the battery in and let it charge.

I don't have a problem with the battery as i was able to fully charge it. I've tried every thing that i can flash to try to bring it back to life to no avail. Can't get to recovery either. I keep seeing a bunch of people saying that re-flashing it back to stock would un-brick this, but i am starting to think i have a brick.
BTW i have a Telus Milestone.

Maybe the case you have upgraded bootloader?
Have you already tried to flash only the vulnerable recovery and then try to boot in recovery mode?

pippocannelunghe said:
Maybe the case you have upgraded bootloader?
Have you already tried to flash only the vulnerable recovery and then try to boot in recovery mode?
Click to expand...
Click to collapse
I have bootloader 90.78. And yes i have tried the vulnerable recovery. When i try to boot to recovery mode it just sits at a blank screen and reboots back to the moto logo.

I believe it is next to impossible to brick a Milestone as we can't touch anything along the bootline.

DannyDroid said:
I believe it is next to impossible to brick a Milestone as we can't touch anything along the bootline.
Click to expand...
Click to collapse
Everytime i flash the Telus SBF it shows that it finished sucessfully but after it reboots it goes back to the Bootloader 90.78 screen.
I've even tried flashing different sbfs and the same result.

cheerup38 said:
I am having this problem too. Is there a true fix for this???
Click to expand...
Click to collapse
I eventually fixed this by flashing a rom with a diferent baseband. My milestone is a UK model, when I tried flasing the GOT 2.2 for telsus, it actually worked, then I reflashed a UK rom.
I don't know why that worked, maybe I had a corruption is the baseband files, but if that was the case, flashing a uk rom should of worked also.
Hope you get yours going again.

jason600 said:
I eventually fixed this by flashing a rom with a diferent baseband. My milestone is a UK model, when I tried flasing the GOT 2.2 for telsus, it actually worked, then I reflashed a UK rom.
I don't know why that worked, maybe I had a corruption is the baseband files, but if that was the case, flashing a uk rom should of worked also.
Hope you get yours going again.
Click to expand...
Click to collapse
Yeah, i saw your solution on another forum, i tried that and no go. its getting frustrating.

Hy,
This seems a little odd,but at least it's an idea:
Unplug the battery and leave it unplugged for at least one hour. In the meantime(battery still unplugged) press the power button for 5-10 secs or so...this guarantees that there will be no current left on the phone...after the hour,try to reboot and keep the fingers crossed..i know this sounds stupid,but at least give it a try
Good luck!
Sent from my Milestone

cheerup38 said:
Everytime i flash the Telus SBF it shows that it finished sucessfully but after it reboots it goes back to the Bootloader 90.78 screen.
I've even tried flashing different sbfs and the same result.
Click to expand...
Click to collapse
Just to clarify, after you've flashed it boots straight into the bootloader? Does you get any type of error message such as code corrupt or a string of hex codes?
Are you trying to flash 2.1 or 2.2 or have you tried both?
When my was bricked, flashing 2.1 would boot to the m logo and sit there forever. Flashing 2.2 would boot to the m logo, stay there for maybe 30 seconds, then reboot and repeat. It was the diferent effects of flashing the two versions that lead me to try diferent basebands. Also, I'm pretty sure that I tried flashing diferent basebands for 2.1 without it working.
Also, what happens when you plug into the wall charger? Do you get the battery graphic or does it stick at the m logo?

jason600 said:
Just to clarify, after you've flashed it boots straight into the bootloader? Does you get any type of error message such as code corrupt or a string of hex codes?
Are you trying to flash 2.1 or 2.2 or have you tried both?
When my was bricked, flashing 2.1 would boot to the m logo and sit there forever. Flashing 2.2 would boot to the m logo, stay there for maybe 30 seconds, then reboot and repeat. It was the diferent effects of flashing the two versions that lead me to try diferent basebands. Also, I'm pretty sure that I tried flashing diferent basebands for 2.1 without it working.
Also, what happens when you plug into the wall charger? Do you get the battery graphic or does it stick at the m logo?
Click to expand...
Click to collapse
After the flash it goes straight back to the bootloader screen and with a string of hex codes: a5,69,35,00,27
I've flashed both 2.1 & 2.2 sbfs. Same thing happens after each flash, nothing different like you mentioned. So i can't really narrow it down.
I do not get a battery graphic when i plug in the wall charger, it goes from the moto logo to the bootloader 90.78 screen and then reboots. it probably does this about 5 times and then turns off.

cheerup38 said:
After the flash it goes straight back to the bootloader screen and with a string of hex codes: a5,69,35,00,27
I've flashed both 2.1 & 2.2 sbfs. Same thing happens after each flash, nothing different like you mentioned. So i can't really narrow it down.
I do not get a battery graphic when i plug in the wall charger, it goes from the moto logo to the bootloader 90.78 screen and then reboots. it probably does this about 5 times and then turns off.
Click to expand...
Click to collapse
That code is for a bad flash. See this link on android-hilfe.de (its german, link is with google translate), scroll down to lesson 9:
http://translate.googleusercontent....&twu=1&usg=ALkJrhhoVzir_DtnGt57By9kO93AsPmS8g
Try flashing with diferent versions of RSDLite. Re-install usb drivers, try flashing from a different PC, make sure your flashing NON-SERVICE sbf's.
Hope this helps

jason600 said:
That code is for a bad flash. See this link on android-hilfe.de (its german, link is with google translate), scroll down to lesson 9:
http://translate.googleusercontent....&twu=1&usg=ALkJrhhoVzir_DtnGt57By9kO93AsPmS8g
Try flashing with diferent versions of RSDLite. Re-install usb drivers, try flashing from a different PC, make sure your flashing NON-SERVICE sbf's.
Hope this helps
Click to expand...
Click to collapse
Oh ok, i will try this, Thanks.

cheerup38 said:
Oh ok, i will try this, Thanks.
Click to expand...
Click to collapse
Also, redownload your your sbf files, the one your flashing might be corrput.

[Q] Repair Galaxy Note N7000 SystemUI / TouchWiz home stopped working errors?

Hello everyone,
I've been literally 12 hours searching for possible answers on how to repair my Galaxy Note N7000 which from what I've concluded, has a problem that can be easily repaired but I've found nothing but limitations when I have a go at it. It doesn't seem to be bricked as I can still access recovery mode, download mode and it effectively boots, it's only giving me errors.
Here's what happened:
1) I tried rooting it using UnlockRoot PRO. Paid the PRO version, detected the device. Later I find it says the N7000 with 4.1.2 is not compatible so the rooting process was never completed, so I rooted it using Root_SuperSU.0.95.Only-signed and it worked just fine.
2) Everything worked fine, downloaded Andromizer to customize the phone.
3) Changed the DPI size to test it, then went to Developer Options and changed the Animation scales to 0.5 to make it all run faster.
4) Rebooted the device. Once I did, I got nothing but "SystemUI has stopped working" together with "TouchWiz home has stopped working errors".
I checked around the web and so far, what I've found (and tried) is this:
1) There seems to be a bug related to TouchWiz and the Animation Scale option (or perhaps the DPI size option in Andromizer). So I tried to do a wipe data / factory reset through recovery mode.
2) When trying the wipe data / factory reset through recovery mode, I rebooted the phone, only to find the SAME errors after I registered everything.
3) First option that came to mind was to wipe everything and immediatly reinstall the Official JellyBean 4.1.2 firmware (at this point I want to pretty much unroot the device as I didn't know it was going to give me so much trouble). When I tried that, I realized that SUDDENLY, Odin (nor Heimdall) are NOT detecting the phone in download mode. I'm guessing it's because USB Debugging is turned off but, I can't access the phone settings. It's my only logical conclusion, although it should be turned on given I could install PhilZ Custom Recovery later.
4) I search around the web and it says it's a driver problem. So I uninstall everything, run CCleaner, USBDeview to uninstall everything related to the Samsung Galaxy. Reboot. Install drivers again. Reboot. Plug booted phone and let Windows detect the device, installed successfully. Reboot in download mode. Let windows detect the device, installed successfully. Run Odin: DEVICE NOT DETECTED. (It does detect it while it's booted though, only it doesn't work for **** obviously).
I've literally tried everything. I've tried checking for a way to install the firmware via Recovery Mode instead of Download Mode. I've tried checking for a way to remotely access the device and mod the settings from there using ADB, and I get the same problem in ADB, doesn't detect the device.
Also tried to reset settings to normal via PhilZ Custom Recovery which I managed to install later.
Isn't there just a way to reset all settings to normal? Shouldn't a factory reset do this? How can I get SOMETHING to work and try to recover the phone? Any Aroma Recovery Script? Any way to mess with the system folder and modify settings manually via notepad or something since due to the SystemUI / TouchWiz home errors I can't access the phone settings?
I'm barely awake at this point. Can't believe I've stressed myself this much. Please help. This is beyond retarded.
Thank you,
Z

i had the same exact problem just few hours ago.....first of all you should boot into recovery mood by pressing vol up+ home button+lock button until samsung logo shows and then wipe all data/factory reset and wipe all cache partitions..........if that didnt fix it you should try rerooting it againg after re wiping

I read the post but it seems you have done a lot of things and nothing worked. So what is the situation right now? You can boot as normal but cannot get any icons or settings as sysUI and TW crashes?

Try installing GB ROM then wipe/cache first. If good, root GB ROM then do full wipe. Then test ROM for crashing.
If good then install JB rom and test. Let us know.

unable to enter phone setting ？ then just simply look for a secsetting.apk for ur version then replace it n set the permission rw-r--r--

You could use adb to modify your build.prop
Sent from my SGNote

Makrilli said:
You could use adb to modify your build.prop
Sent from my SGNote
Click to expand...
Click to collapse
Bwahahah, now I see why you guys enjoy calling newcomers "noobs".
It was a computer problem. I just reinstalled JB 4.1.2 from my netbook and it worked.
Weird as hell though, given that I updated my GT-N7000 to JB 4.1.2 through Odin in this computer and it never gave me any problems.
I AM going to learn some ADB / Android SDK though. I'd rather learn everything before something like this happens to me again.
I appreciate everyone's concern, and thank you all for it.

nice to hear that you had this one fixed

Glad to hear its working now.

n7000 touchwiz home stopped
Zardonic said:
Bwahahah, now I see why you guys enjoy calling newcomers "noobs".
It was a computer problem. I just reinstalled JB 4.1.2 from my netbook and it worked.
Weird as hell though, given that I updated my GT-N7000 to JB 4.1.2 through Odin in this computer and it never gave me any problems.
I AM going to learn some ADB / Android SDK though. I'd rather learn everything before something like this happens to me again.
I appreciate everyone's concern, and thank you all for it.
Click to expand...
Click to collapse
hi.... im having the same problem as yours. i dont know what to do

lulu2050 said:
i had the same exact problem just few hours ago.....first of all you should boot into recovery mood by pressing vol up+ home button+lock button until samsung logo shows and then wipe all data/factory reset and wipe all cache partitions..........if that didnt fix it you should try rerooting it againg after re wiping
Click to expand...
Click to collapse
I have tried to upgrade my touchwiz to the new one, but got the danger message, would clearing the cache help?
Sent from my SM-N910C using Tapatalk

[Q] LG L90 D315 bricked without recovery access etc

So this is my first xda thread. I spent hours searching without finding a solution for my particular case.
I am using a LG L90 D415 (T-Mobile version) and I got bored of it and so I started playing with the system (not the first phone I'm doing that with, so I know a bit about that sutff). So I tried to install the new Android L home launcher from here http://forum.xda-developers.com/showthread.php?t=2796019
I did everything like explained, installed it and changed the build.prop like described. But after I rebooted my phone, expecting a new home launcher, the phone boots, I am at the lockscreen, but after like 4 seconds I receive multiple errors (like gapps stopped working) and than everything freezes and it reboots.
Unfortunaly I didn't install a recovery or unlocked fastboot. So I can access download mode, but that's it. My computer doesn't see my phone (because usb debugging deactivated?) and so I don't know what to do. I think that's a pretty tough case but I hope some smart person can help me
Thank you

mcfiish said:
So this is my first xda thread. I spent hours searching without finding a solution for my particular case.
I am using a LG L90 D415 (T-Mobile version) and I got bored of it and so I started playing with the system (not the first phone I'm doing that with, so I know a bit about that sutff). So I tried to install the new Android L home launcher from here http://forum.xda-developers.com/showthread.php?t=2796019
I did everything like explained, installed it and changed the build.prop like described. But after I rebooted my phone, expecting a new home launcher, the phone boots, I am at the lockscreen, but after like 4 seconds I receive multiple errors (like gapps stopped working) and than everything freezes and it reboots.
Unfortunaly I didn't install a recovery or unlocked fastboot. So I can access download mode, but that's it. My computer doesn't see my phone (because usb debugging deactivated?) and so I don't know what to do. I think that's a pretty tough case but I hope some smart person can help me
Thank you
Click to expand...
Click to collapse
No custom recovery and no fastboot? Factory reset is your only option. See this post. Scroll down to Q14. Even though it's titled something else, the same button presses apply for your device in it's current state, ie; no recovery, no fastboot

shinobisoft said:
No custom recovery and no fastboot? Factory reset is your only option. See this post. Scroll down to Q14. Even though it's titled something else, the same button presses apply for your device in it's current state, ie; no recovery, no fastboot
Click to expand...
Click to collapse
First thanks for the fast answer. So I figuered that I only need to delete the build.prop file and replace it with my backup file. Isn't there any way to rescue my files and/or access the /system folder? I'm an exchange student now and I don't wanna lose my picture memories
And btw I know that I build the perfect worst case scenario right now
Oh and in the L90 faq it says that when you flashed a recovery and you navigate to factory reset it won't reset but boot into recovery. Does something like this work even without recovery, so I could try doing stuff with adb?

mcfiish said:
First thanks for the fast answer. So I figuered that I only need to delete the build.prop file and replace it with my backup file. Isn't there any way to rescue my files and/or access the /system folder? I'm an exchange student now and I don't wanna lose my picture memories
And btw I know that I build the perfect worst case scenario right now
Click to expand...
Click to collapse
If adb isn't detecting the phone, no. There isn't any other way.
mcfiish said:
Oh and in the L90 faq it says that when you flashed a recovery and you navigate to factory reset it won't reset but boot into recovery. Does something like this work even without recovery, so I could try doing stuff with adb?
Click to expand...
Click to collapse
Unfortunately, no.
Factory reset will not erase your sdcard. It will however erase internal data. It will return the phone to the state it was in the first time it was powered on.

[Q] LG Optimus L90[LG DG415] stuck on logo

So I was just screwing around with my fonts folder(under system) and I replaced my custom font file for Roboto-Normal.ttf with the original Roboto font and when I rebooted my phone it got stuck on the LG logo and wouldn't advance after that. I also noticed while it was stuck on the LG logo if I hit any buttons in any combinations the phone would vibrate randomly. My phone is rooted with debugging on.

MrKidQuisine said:
So I was just screwing around with my fonts folder(under system) and I replaced my custom font file for Roboto-Normal.ttf with the original Roboto font and when I rebooted my phone it got stuck on the LG logo and wouldn't advance after that. I also noticed while it was stuck on the LG logo if I hit any buttons in any combinations the phone would vibrate randomly. My phone is rooted with debugging on.
Click to expand...
Click to collapse
Maybe the font was not compatible for your phone,If it was compatible for you it should apply and you should see it immeadiately,Rebooting is not required.
Try to connect the computer and Use the LG R&D Tool to flash the ROM.

androidvillage said:
Maybe the font was not compatible for your phone,If it was compatible for you it should apply and you should see it immeadiately,Rebooting is not required.
Try to connect the computer and Use the LG R&D Tool to flash the ROM.
Click to expand...
Click to collapse
No I wasn't using a custom font installer I was just putting a different font into the system root fonts folder and that ended up slowing down the phone so I restarted it and now its bootlooping.

MrKidQuisine said:
No I wasn't using a custom font installer I was just putting a different font into the system root fonts folder and that ended up slowing down the phone so I restarted it and now its bootlooping.
Click to expand...
Click to collapse
That's Because the font was written bad or the system cant render it because wrong format,that's why ended up slowing.
Turn off your phone,Hold Volume + And Plug it into USB.AndUse the LG Mobile Support Tool,Select CS_Emergency Mode and Flash...
Or if you could get into the phone into safemode,Fix it by replacing other font into the file.
That's only 2 way to fix your phone.

androidvillage said:
That's Because the font was written bad or the system cant render it because wrong format,that's why ended up slowing.
Turn off your phone,Hold Volume + And Plug it into USB.AndUse the LG Mobile Support Tool,Select CS_Emergency Mode and Flash...
Or if you could get into the phone into safemode,Fix it by replacing other font into the file.
That's only 2 way to fix your phone.
Click to expand...
Click to collapse
When I hold down volume up and power it just goes into the logo and if I continue to hold it it vibrates then immediately shuts off. Ive tried before to enter recovery mode on this phone but I think LG blocked it.

MrKidQuisine said:
When I hold down volume up and power it just goes into the logo and if I continue to hold it it vibrates then immediately shuts off. Ive tried before to enter recovery mode on this phone but I think LG blocked it.
Click to expand...
Click to collapse
Perform a factory reset. See this thread Q14.

I had a very similar problem that stemmed from trying to install a new font. When I tried a hard key factory reset, it did nothing to fix the bootloop. Rather, I think it made the phone impossible to reach with ADB by resetting the "debugging mode" setting along with everything else. My advice to you, though I haven't actually tried this because of the above problem, is to try to access your phone through ADB.
If that doesn't work, what I ended up doing was sending my phone to an LG service facility with a note attached detailing the problem and cause. They were able to restore it, despite it being rooted.

Update
Ok so I left my phone out unplugged for about and hour on the logo and it popped on so Im trying the same thing again but with the sim card in and if it works Im going to see if I can make the thing load faster by updating the permissions on the font file or using a font installer all together.

MrKidQuisine said:
Ok so I left my phone out unplugged for about and hour on the logo and it popped on so Im trying the same thing again but with the sim card in and if it works Im going to see if I can make the thing load faster by updating the permissions on the font file or using a font installer all together.
Click to expand...
Click to collapse
Still stuck in bootloop no other activity since restarting and puting in sim, I also about two hours ago took out the sim and restarted

similar problem
i was messing with the app chainfire 3d was prompted to install a graphics driver which and gave me a warning that it might brick my phone if it was not compatible so i said what the hell and proceeded now im stuck at lg logo with no clue on how to get it back to normal i am currently trying lg mobile support tool which seems to only stay at 10% been at it for about 15 min now not sure if just copying files or what im clueless on what to do im running rooted d415 stock rom my phone is on download mode right now

Same problem, different cause
I was installing an update to CM. In the recovery it said something about symlinks failed. I restarted, and now phone will get past the LG logo, but black screen. I can't access recovery either. In adb, I see the device, but it is unauthorized, and I obviously have no way to authorize it. Any way to fix this without sending it back?
Thanks in advance

Fixed it
I found a way to recover, but you must have a custom recovery.
Use the button shortcut for force reset. It will take you to recovery. From there you can restore or reinstall a rom.

[Q] Turbo Stuck on Android Screen

So I flashed but now my phone just boots to Android Screen - I am a Novice in this area - how can I restore my phone to factory or getting back to working condition

bturkel said:
So I flashed but now my phone just boots to Android Screen - I am a Novice in this area - how can I restore my phone to factory or getting back to working condition
Click to expand...
Click to collapse
Likely your flash was interrupted. Try flashing again and make sure the progress gets all the way through. My last time took the attempts to get a clean flash. Had to keep it in the foreground and not do anything else on my computer.

rgerrans said:
Likely your flash was interrupted. Try flashing again and make sure the progress gets all the way through. My last time took the attempts to get a clean flash. Had to keep it in the foreground and not do anything else on my computer.
Click to expand...
Click to collapse
Also, make sure you have the lastest mofo (version 0.0.2).

So I tried to flash the hotspot rooted image also the just plain rooted image. Which image do you suggest I use? Yes my first flash got interrupted. So are you saying that since I get to the white android screen that's a good sign?

bturkel said:
So I tried to flash the hotspot rooted image also the just plain rooted image. Which image do you suggest I use? Yes my first flash got interrupted. So are you saying that since I get to the white android screen that's a good sign?
Click to expand...
Click to collapse
Shouldn't matter but I'd stick with the original root image. Android logo isn't a good sign you are just stuck in a bootloop. If you can't get the regular rooted image flashed then you can go here for rsd plus stock, but I'd only do that as last resort since good chance of loosing all your data - http://forum.xda-developers.com/droid-turbo/development/quark-stock-firmware-moto-maxx-droid-t3063470
If it still won't flash the root image, you might want to hit the Mofo Thread and ask for help since a few others are having similar issues of not being able to get 100% through a flash - http://forum.xda-developers.com/general/paid-software/mofo-root-turbo-t3064404. They seemed to have identified issues if you installed more then one usb driver and/or are using a usb 3.0 port.

All good now - lost data but wiped phone then flashed - it work finally

hi every body, i have the same issue, i decide to udpate my phone to lollipop and everything was working fine except for one error that was doing my phone every time i use settings, and i decide to wipe the cache under recovery, when i tried to do it, the phone get stuck in erasing cache and then after some minutes here i turn off and on again the phone and make the same procedure and this time the wipe was very fast and then i restart my phone and here is the problem now, it get stuck in android screen and is not coming back from here, i tried to make a factory reset and nothing happens it is still on android screen and i dont know what else i can do, my bootloader is locked.
any ideas?

bturkel said:
All good now - lost data but wiped phone then flashed - it work finally
Click to expand...
Click to collapse
Hey how did you fix it? Im stuck on the moto logo and have no idea how to fix it. I have tried everything! Thanks in advance.