Im trying to get the new Official Tmobile USA rom on my phone. I just flashed my phone over from a China 2.2 rom running one of jboogies recoverys. I wiped, then flashed the leaked tmobile rom. When I try to log into my motoblur account, the phone just locks up, and then shows a black screen. This lockup is once im within android, not during the boot sequence. The sbf was successfully flashed, but just black screens after a while. Also, the keyboard wasnt appearing when I tried typing in my details.
Any help is appreciated.
Ive managed to get passed the login screen by essentially racing to typing in my account and password before it crashed. I eventually got it. I can now the android os but it crashes almost instantly. About 10 or so seconds of actually navigation. I tried to get into the "about the phone" menu in the setting, but it kicks me out of it really fast. I saw something that said 2.1_update1. on my latest boot, ive activated USB debugging, which seems to be working. The phone isnt shutting down anymore. I however have no service (I didnt have any before USB debugging either though).
My phone seems stable being on with usb debugging on, but I still cant get into the "about phone" menu. It just kicks me back out. Still open to suggestions
Heres what i can read from the "about phone"
System Version:
Blur_Version.3.6.360.MB525.T-Mobile.en.us
Model Number
MB525
Firmware Version
2.1_update1
Baseband
EPU93ST2_U_03.04.2
Kernal Version
2.6.29
[email protected] #1
My phone keeps pushing me out of several apps such as the dialer, messagging, mostly anything Motorola related.
Tried flashing the tmobile us 3.4.2. I got my reception back, but home home screen was just black. I did have my bar at the top though. I couldn't access anything. I could receive calls. Flashing back to the u3_6.36.3.0 sbf. what a headache
I think i know my problem. I guess I need to do a full wipe in between flashing. Only problem is is that im not rooted anymore and i cant get any SBF to really work anymore. all im getting are black screens. What sbf can I use that I can root so I can wipe.
As far as wiping is concerned. I did wipe the first time, but then I rebooted the phone. I feel like that was my mistake.
Anyways, how can i get my phone working again?
After an unbelievable amount of frustration, ive managed to get it
Firstly, I went back to the u3_6.36.3.0 sbf. Like all the other roms I tested, I continued to have a black screen with a menu bar. I shut the device down, and booted into the stock recovery (Volume down + Power). I then touched the bottom right corner to get into the menu. I did a full factory reset. After I rebooted, the device was working 100% as intended. I check for the system update, and sure enough, its downloading now.
I really hope this can help someone, but I feel due to my lack of proper notation and poor documentation, it wont. Anyways, My only advice can really be to those trying to get the official tmobile 2.2. If when you flash the u3_6.36.3.0 sbf and you get a ton of errors, just try a factory reset via the stock bootloader.
What do you mean by touching the bottom right corner of the phone? On the screen or button need to be pressed? And surely it will enter into another menu sort of service menu where one can do a list of actions??
Great getaway by the way...
bottom right corner of the screen (lcd). Its the stock recovery. When you boot into the stock recovery, it will have a exclamation point in a triangle as well as an android standing by it. Once you actually enter the menu, it will look alot like the custom recovery. Also, be patient if you do the factory reset. it takes a little bit. It doesnt really show any indication that its working other then some periods occurring two or three times throughout the process.
Related
Stock galaxy nexus, ui force closed. Powered off. Can get into recovery mode to attempt to reinstall stock rom. It shows a droid with an opened chest, with a red triangle above it when I try to go to recovery mode from the odin screen.
Anyone else have this issue? Is there a way to flash using a mac? I have limited access to a pc.
Thanks all.
This is the hspa version.
svntsvn said:
Stock galaxy nexus, ui force closed. Powered off. Can get into recovery mode to attempt to reinstall stock rom. It shows a droid with an opened chest, with a red triangle above it when I try to go to recovery mode from the odin screen.
Anyone else have this issue? Is there a way to flash using a mac? I have limited access to a pc.
Thanks all.
Click to expand...
Click to collapse
The android icon you're referring to sounds like the stock recovery. In order to flash a ROM (even stock) from recovery mode, you'll need to load a custom recovery. This requires the device to be unlocked.
Not very often a stock setup needs to be restored. Generally, with the stock setup, only the /data partition is wiped (revert to factory default) and the issues are cleared. Not sure why a stock setup would need to be restore.
If you're still going to pursue reloading the system, without access to the normal android mode, the best route will be using fastboot. This can be done on a mac and the fastboot commands should be the same.
Hope that helps get a start!
This happened me earlier. I was able to factory reset it, which, unfortunately really annoyed me because I hadn't saved a backup..
Before the "Google" logo shows up, press and hold the power button and the volume up and down buttons.
Then go into recovery mode using the volume buttons.
When it reboots, you get that Droid with the hazard sign (which I know you're at, but just for the sake of others who need help) all you have to do is hold down the power button and WHILE it's held, press the volume up or down button and move to "Factory Reset". When you hold down the power button and press the volume rocker, a little menu will appear. It should only take a few minutes then.
Hope this helps. Apparently this is a WiFi issue. I'll definitely be keeping backups as of now..
I left it off, plugged it back in for a couple of hours and it booted right up. Strange.
I'm wondering if it had anything to do with juice defender and its settings that take effect at a lower battery level? Its the only thing I can come up with. Never had a stock phone's ui force quit and not reboot. The battery was definitely up to 25% given the time it was initially charging, but maybe it was still interfering.
Well, now that she's running, time to get root, recovery, rom and rejoice.
Thanks for the replies, very much appreciated.
svntsvn said:
I left it off, plugged it back in for a couple of hours and it booted right up. Strange.
I'm wondering if it had anything to do with juice defender and its settings that take effect at a lower battery level? Its the only thing I can come up with. Never had a stock phone's ui force quit and not reboot. The battery was definitely up to 25% given the time it was initially charging, but maybe it was still interfering.
Well, now that she's running, time to get root, recovery, rom and rejoice.
Thanks for the replies, very much appreciated.
Click to expand...
Click to collapse
I had the exact same problem happen last night with UI crashing and then the getting stuck at the boot animation. I was desperately searching online, looking to find a solution that didn't involve rebooting to factory setting and came across this post and did exactly what you did and it WORKED, very strange, I really wanna know what caused that!!!!
I've had the same problem with my Galaxy Nexus. I received it on December 21st, with stock 4.0.1 build. No root or unlock attempt at any time. On January 2nd I experienced this problems (UI process crash, screen not responding, reboot and stuck in boot animation).
The only solution was to do a factory reset and start over.
On January 10th same problem, same solution. Second factory reset.
I got the 4.0.2 OTA just two days after that. I thought that would resolve the problem. The phone seemed more stable, with less FC's and no trace of the UI crash. Indeed it lasted long...
Exactly until January 24th when I picked up the phone and seemed in the sleep of dead. Removed the battery, restarted the phone... and stuck in the boot animation.
Do you have any advice? Should I return the phone? Aside from those specific problems I am quite happy with the SGN and Android 4 in general. And I use it quite a lot (I have a very long train commute) without other problems.
Again...
It happened again!!
I don't know what to do anymore, this is not a usable phone when I have to reinstall and reconfigure every 3 weeks.
I may have found the problem
Well, not me exactly, but this bug report seems to fit the problem and the charging workaround. Seems to be a problem the file used to store the battery stats and draw the charge graph.
It also fits my usage (I try not to charge it up until 100%).
I can't post links to the forum, the issue is id number 24518 which you can find in code.google.com/p/android/
So, after being rooted for a bit, i decided to do some things that ultimately messed up my phone a bit. so instead of trying the numerous fixes for the problem, i decided to do a factory restore. it goes off fine, and brings me to the setup. i connect to my wifi and now its searching for updates. i figured it would take a bit so i went off and did some other things while the phone was on my desk. now about an hour and a half later its still checking for updates. my only options is to go back, which yields no other options, or to skip, but the skip is greyed out and i cant press it. so im stuck in the software update screen while it forever checks for updates and i cant get out of it. Ive restarted a few times and also shut it off for a bit, but still its stuck on this screen.
sperks117 said:
So, after being rooted for a bit, i decided to do some things that ultimately messed up my phone a bit. so instead of trying the numerous fixes for the problem, i decided to do a factory restore. it goes off fine, and brings me to the setup. i connect to my wifi and now its searching for updates. i figured it would take a bit so i went off and did some other things while the phone was on my desk. now about an hour and a half later its still checking for updates. my only options is to go back, which yields no other options, or to skip, but the skip is greyed out and i cant press it. so im stuck in the software update screen while it forever checks for updates and i cant get out of it. Ive restarted a few times and also shut it off for a bit, but still its stuck on this screen.
Click to expand...
Click to collapse
*UPDATE* Still cant do anything... ive booted into recovery and factory reset, cleared cache, and all that and still nothing... i cant get to the home screen or any other screen other than the one that says "checking for updates". if i dont turn wifi on and then continue, all it says is "Just a sec..." and stays on that forever. If anyone has any suggestions please leave them here i dont have a backup phone and need this fixed asap thank you.
I reflashed root file but I'm not sure if factory wipe has taken the file off your internal sdcard but yeah, i just reflashed the system file. Best of skills
Sent from my VS986 using Tapatalk
Hi All,
Really hoping someone can suggest a possible solution for this one, only had the phone a few months!
So, Chinese released M9. Unlocked. Stock recovery, not rooted. Gapps installled.
Everything perfect, then today I got the 5.1 update.
Seemed like a slightly iffy install process...looked a little like it failed a couple of times and tried again.
Finally finished, the phone shows the white screen with the one logo, takes a while, opens on the desktop and turns off, back to the white screen with the logo.
I have been able to boot into safe mode, which is stable
I have been able to get to download mode and bootloader. Neither of these offer a cache wipe or a factory reset.
I have not been able to get into recovery mode, it shows a phone with a red triangle and an exclamation point.
So for my (largely uneducated) part I have two theories for the cause:
1) Gapps is somehow proving a problem, either faulting the install or causing a fatal error on startup
2) Since the update was notified and downloaded while on a VPN via Hong Kong, I wonder if I accidentally ended up with the HK version in which case I suspect there may be hardware differences (at least the radio). This seems unlikely, I would hope there were enough checks in place to prevent this happening.
No solid idea where to go from here. I have not yet tried ADB access, but even if I can connect, what will I do? Flash a new ROM? I'd rather not. And surely I'd need to root in order to do that....
At a loss, any potential solutions welcomed whole heartedly!
Thanks...
Booting into safe mode, but not booting otherwise, indicates a problem with some app or rom setting.
You're probably going to need to do a factory reset, but that's odd that it doesn't show up in bootloader or download mode. Have you tried the options in stock recovery (which is that screen with the red triangle)? Use the volume keys to change options.
Hi iElvis - the screen with the red triangle - there's nothing other than the red triangle, no options, no text and nothing happens if I press any of the physical buttons.
Trying a factory reset from safe mode - I'll let you know what happens!
misteral1970 said:
Hi iElvis - the screen with the red triangle - there's nothing other than the red triangle, no options, no text and nothing happens if I press any of the physical buttons.
Click to expand...
Click to collapse
Hmm. It would seem the Chinese models are set up differently, which would not surprise me at all.
I was just using my phone like normal today opening up the transit app at the bus stop and it randomly froze and restarted. After that, it only shows the initial Google screen and just keeps bootlooping, but never even gets to the part where the OS is loading (with the google animation). It was just on stock 6.0.1, MTC20K I think. Was not rooted. Bootloader was/is unlocked. Secure boot was/is enabled. It won't even go into stock recovery (when I select recovery it immediately goes back to the Google screen and continues as if I had never selected recovery). I have tried manually flashing each piece of the latest factory 7.0.0 build (NRD90S), but even though fastboot says everything was successful, nothing seems to have changed. Any ideas on how to fix this?
Same thing just happened to me. I have no root or anything but it will not boot the OS. I hope there is a fix for the problem because I really want to use the phone.
Same thing just happened to me.
Click to expand...
Click to collapse
No recovery for you either?
What was the latest Build you had when it was working fine?
To get into the recovery plug the phone into your computer. Go into fastboot (vol down + power) and select the power off option. When it turns off or goes to the charging screen, hold volume up + power to boot to download mode. Once in download mode, turn the phone off by holding vol down + power, then go back into fastboot and you should be able to now access recovery mode. This is what I did, and then flashed back to 6.0.1 and it runs fine now. No Idea why going into download mode allows you to then access recovery and get one clean boot, but it does
Druas said:
I was just using my phone like normal today opening up the transit app at the bus stop and it randomly froze and restarted. After that, it only shows the initial Google screen and just keeps bootlooping, but never even gets to the part where the OS is loading (with the google animation). It was just on stock 6.0.1, MTC20K I think. Was not rooted. Bootloader was/is unlocked. Secure boot was/is enabled. It won't even go into stock recovery (when I select recovery it immediately goes back to the Google screen and continues as if I had never selected recovery). I have tried manually flashing each piece of the latest factory 7.0.0 build (NRD90S), but even though fastboot says everything was successful, nothing seems to have changed. Any ideas on how to fix this?
Click to expand...
Click to collapse
Had the same thing happen - Now typing to you from my warranty replacement. Only option.
blackpaw78 said:
To get into the recovery plug the phone into your computer. Go into fastboot (vol down + power) and select the power off option. When it turns off or goes to the charging screen, hold volume up + power to boot to download mode. Once in download mode, turn the phone off by holding vol down + power, then go back into fastboot and you should be able to now access recovery mode. This is what I did, and then flashed back to 6.0.1 and it runs fine now. No Idea why going into download mode allows you to then access recovery and get one clean boot, but it does
Click to expand...
Click to collapse
Surprisingly, this worked. I forgot about download mode being an option. I also am not sure why this worked.
Edit: The phone boots, but is still randomly rebooting rather often. Not sure why, as everything was wiped and it should have been a fresh install of everything.
Another Edit: Back to boot looping/not getting to the Android loading screen. I didn't do anything other than let it download my apps. Maybe it is a hardware problem after all because it did successfully boot into Android a couple times.
This seems to be a common problem which I have, too. Looks like a whole series of devices had these issues. Currently LG is unable to repair my device because auf missing spare parts they say. So after effortless 3 weeks they will send my unrepaired device back to me with a letter for my dealer to get back my money.
Nice quality and service, LG - NOT!
Janny82 said:
This seems to be a common problem which I have, too. Looks like a whole series of devices had these issues. Currently LG is unable to repair my device because auf missing spare parts they say. So after effortless 3 weeks they will send my unrepaired device back to me with a letter for my dealer to get back my money.
Nice quality and service, LG - NOT!
Click to expand...
Click to collapse
That is actually pretty good outcome. Pixel phone is coming out soon.
Just had this happen today. Streaming music over Bluetooth and using another app, then tried switching tracks in Google Play Music and the app froze. Phone was unresponsive with app on the screen, then screen went off and wouldn't power on.
I finally got it on by holding down power for 30 seconds, but kept boot-looping to Google boot screen. I was able to get into fastboot mode and wipe everything and install the factory image. Still doing the same thing!
Just got off phone with Google. Told the rep everything I had tried and she is working on a replacement order. Supposed to call me back after chatting with higher level support. I wish they would just send me a new Pixel phone, or the 6P at least!
Ive had the same issue, where I just couldnt get passed the Google screen, the only solution for me to get back on to my phone was to let it happen until the battery died. After i let the battery die i turned it back on normally and connected it to my charger, it hasnt turned off since but im sure it will sooner or later
Edit: Issue is still happening but the only way for me to turn it back on is because the battery dies
This just happened to my and my wifes phones...all within a week of each other. I sent my wife's in about a week and a half ago to LG for warranty service. I am hoping that they are able to fix it...it is still in the 'repair' phase. I am trying to decide whether or not I want to send my phone in (which just died yesterday) before or after LG figures out what is going on with my wifes. In both cases, the phones were running fine and just shut down by themselves. The battery was not dead. Each time, the phone will boot to the Google screen, but then immediate shut down. I can get in to recovery and do actions within there, so I do not believe it to be a battery issue. However, as soon as you attempt to boot the phone, it will die.
Were you guys using stock setups or custom ones?
Sent from my Nexus 5X using Tapatalk
Its a 'known' issue. Google has confirmed there is an issue. Only solution appears to be a warranty replacement.
https://productforums.google.com/forum/#!topic/nexus/r29mtzLFS0g;context-place=topicsearchin/nexus/nexus$205x$20bootloop
---------- Post added at 10:22 AM ---------- Previous post was at 10:21 AM ----------
Psychofrantics said:
Were you guys using stock setups or custom ones?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
on both phones, bone stock. Only difference was I was running the beta before getting the stock OTA and my wife's was full stock and received the stock OTA.
I'm having the exact same problem here. Running Android 6.0.1, rooted. Phone suddenly turned off and won't start past the "Google" screen, except for once when it booted fully then immediately shut down, and three times when it loaded the boot animation and shut down. Bootloader is unlocked and TWRP recovery is installed. I can access fastboot but not recovery. I've tried the suggestion of booting into download mode then recovery again, but that didn't work. I have NOT tried updating to Android 7 yet, so this isn't the same boot loop issue faced by some other users. I don't want to try flashing stock yet and lose my data because I have a ton of Tasker profiles and tasks that I haven't backed up in months and I don't want to risk losing them! Serves me right...
Any suggestions?
Same HERE !!!!
the samed for me, and still now i can't light it up
sagshar said:
I'm having the exact same problem here. Running Android 6.0.1, rooted. Phone suddenly turned off and won't start past the "Google" screen, except for once when it booted fully then immediately shut down, and three times when it loaded the boot animation and shut down. Bootloader is unlocked and TWRP recovery is installed. I can access fastboot but not recovery. I've tried the suggestion of booting into download mode then recovery again, but that didn't work. I have NOT tried updating to Android 7 yet, so this isn't the same boot loop issue faced by some other users. I don't want to try flashing stock yet and lose my data because I have a ton of Tasker profiles and tasks that I haven't backed up in months and I don't want to risk losing them! Serves me right...
Any suggestions?
Click to expand...
Click to collapse
In my opinion your EMMC probably died, but you can try reflashing factory images to see if it is some other problem.
I would only try LGUP as a last resort because it will set Allow OEM unlocking to false and lock your bootloader, making further experimentation difficult.
BTW IMO the Android 7 bootloop probably isn't related to Android 7. I think they are just saying hardware problem (EMMC failure) that happens to show up more frequently when you have large updates of OS.
The way Google worded it, it made it seem like Android 7 is killing some hardware because of some incompatibility with just some isolated hardware builds.
I would suggest you let it keep booting and flash some factory images and sometimes EMMC will come back briefly and boot. If it does, immediately backup as much as you can before doing anything else.
Same deal for me and they are sending a replacement. This is a MAJOR blackeye!
Is your phone under warranty then? I am having the same problem as everyone on here. I've tried everything. I bought the phone just over a year ago though, so am a little concerned Google will turn around and tell me it's not their problem... Even though this is clearly a fault!
My Galaxy Tab S prompted me for an update last night. I was at 5.0.2, so I'm not certain what I was getting upgraded to but it was about a 190MB download. The download went fine and the install seemed to go OK. However, at the end of the update install, the tablet rebooted, and that's when everything screwed up. It went through a normal reboot sequence but, when it started to come up like it was going to take me to the home screen, I got hundreds of error windows popping up one on top of the other. They all said "Unfortunately, this has stopped." or that has stopped, basically running through pretty much every default pre-installed and me-installed app on my tablet. And they kept appearing faster than I could press OK. I have just a black screen with these white error boxes. I'm never able to get to the home screen at all. I've rebooted. I've completely powered down and waited for several minutes before booting. Nothing seems to help. I keep getting a normal boot sequence, right up until the point that it would relinquish control to me, and then these same hundreds of error boxes and no home screen or any sort of control over my tablet. I have no idea what to do.
Has anyone ever heard of any behavior like this or know what I should do?
Thanks.
try to enter the recovery mode by pressing home+vol up+power button. and reset your device
or you can download your full firmware and flash it using odin.
edan1979 said:
try to enter the recovery mode by pressing home+vol up+power button. and reset your device
or you can download your full firmware and flash it using odin.
Click to expand...
Click to collapse
Just got up for the day and saw your response. I'm on nights right now, sorry.
Thank you very much for your reply. I was able to get into recovery mode. Just to clarify, when you say "reset", are you saying a reboot (the first option) or wipe data/factory reset (the fourth option)?
EDIT:
You can disregard. I went ahead and rebooted, and that did what I figured; pretty much nothing. Basically just rebooted, got out of recovery mode, and booted right back into the state that it was in before, which was screwed up. Factory resetting now.
Thanks.
OK, system wiped OK and it's restoring from a Google Backup right now. So, I guess we'll see how it goes the next time I try to update. I have the Wi-Fi version, just standard SM-T800. Isn't Marshmallow available as an update now? I'll see how things go I guess and see what updates are available.
Gotta remember recovery mode, for when all seems darkest!
Thanks again for your help.
OK, so, my tablet is back up and running, but that update won't install. It isn't causing the same problems as before, but it still won't install. I'm at 5.02 and the update is 190MB. It downloads and it starts to install after I accept the EULA. The screen goes black, the little Samsung logo pops up, then the little Android guy comes up and it says installing update 0%, waits for about two seconds, then the little Android guys is on his side with his cover plate up and it says error, then reboots. I can still use my tablet, I just can't install this update, whatever it is. I'm pretty sure it isn't the Marshmallow update, because I'd heard that was up over 1GB. Still, if I can't get this update, whatever it is, I doubt I'll ever be able to get the Marshmallow update.
Now I'm happy I have my tablet back, but frustrated because it won't update.
definitely it already has MM update. you could go to Odin way. Update it manually. can download the firmware here.
http://updato.com/firmware-archive-select-model?q=T800&order=date&dir=desc&exact=1
edan1979 said:
definitely it already has MM update. you could go to Odin way. Update it manually. can download the firmware here.
http://updato.com/firmware-archive-select-model?q=T800&order=date&dir=desc&exact=1
Click to expand...
Click to collapse
Yeah, I was thinking the same thing. It doesn't seem too hard. I'm reading up on it now. I'll download everything I need and possibly try it this weekend. I intentionally haven't reinstalled a lot on my tablet yet, thinking I was going to go that route.
Hopefully, that will take care of my issues.
Thanks again for the advice.
Well, updating with Odin went off without a hitch. After it had updated, I performed a factory reset, just to be safe, and reinstalled everything. It's running great now and I sitting pretty with 6.0.1.
Thanks again for your help.