She told me today that the phone wouldn't boot after most of her apps stopped working. Normally, I would factory reset since her phone isn't rooted, but it didn't work. I then tried to flash the latest firmware with RSDlite. After flashing, the phone stays on the motorola logo. Its suprising that my phone works just fine after one flash. I've tried flashing her phone to stock for three time already and no success. Is her phone offically dead or am I doing something wrong?
ozeyguy said:
She told me today that the phone wouldn't boot after most of her apps stopped working. Normally, I would factory reset since her phone isn't rooted, but it didn't work. I then tried to flash the latest firmware with RSDlite. After flashing, the phone stays on the motorola logo. Its suprising that my phone works just fine after one flash. I've tried flashing her phone to stock for three time already and no success. Is her phone offically dead or am I doing something wrong?
Click to expand...
Click to collapse
no errors RSD Lite nor on phone?
Sent from my KFFOWI using XDA Labs
sd_shadow said:
no errors RSD Lite nor on phone?
Sent from my KFFOWI using XDA Labs
Click to expand...
Click to collapse
Everything was a go. I flashed the "VZW_XT907_4.4.2-KDA20.62-15.1_CFC_1FF.xml" firmware, and it still gets stuck on the splash screen.
ozeyguy said:
Everything was a go. I flashed the "VZW_XT907_4.4.2-KDA20.62-15.1_CFC_1FF.xml" firmware, and it still gets stuck on the splash screen.
Click to expand...
Click to collapse
Could try house of moto, but it could be hardware failure
Sent from my KFFOWI using XDA Labs
sd_shadow said:
Could try house of moto, but it could be hardware failure
Sent from my KFFOWI using XDA Labs
Click to expand...
Click to collapse
Tried the House of Moto. Can still go to recovery but won't go past the splash screen.
Related
So here's the story. Bought a used Droid X from a guy at work. Phone was fine. Never rooted or anything related to root. So I decided to root it. Used ZergRush method I believe. Installed Bootstrap Recovery. Wife used Rom Toolbox to change several notification icons, boot animation and boot logo. Everything was great for awhile, but she got tired of it always booting into recovery. So I was going to un-root and return to stock. Ran the same ZergRush Un-root app. Then removed Bootstrap and all other root apps. Then found out wife accepted an OTA before I un-rooted. Well, at this point the phone still worked, and was un-rooted, but still rebooted into recovery, still had custom boot animation and logo as well. So she then reset phone to factory defaults. After that is when we had problems. Basically it wouldn't load past the boot logo. I just pulled the phone out from its hiding spot after a month or so to try and tackle it again. But now I think the battery is shot because it won't turn on period, whether plugged in or not, and the battery looks like its swollen. Has a huge bulge in the middle.
My question is, do you think the phone is able to work again? Cuz if not, I'm not buying a new battery.
Yeah it sounds like a bad battery now but before would it would just boot to the red m? If so an sbf would probably do the trick
Sent from my ADR6425LVW using Tapatalk 2
Ya before it would boot to the M and stay there, until I pulled the battery. So hopefully new battery and sbf and it will work?
Well yeah an sbf should do you just fine
Just be sure once you do the sbf you boot into stock recovery (vol down+home+power then vol up+down together when you see the !) And do a factory reset or you'll just have another headache
Sent from my ADR6425LVW using Tapatalk 2
Alright cool. Looks like I'll be finding a battery and having a whirl at this. Thanks for the replies
So i sbf'd the shadow 2.3.4 using rsd and it said it was completed and to manually boot the phone. So i did and it still stays at red m logo. Only difference is its now the red m where as before the sbf it was the pink Android my wife installed. So some progress I guess.
Any ideas? Try a different sbf file maybe?
Sent from my R800x using XDA
EDIT: Nvm, tried a different sbf and it works fine now.
I know you say it would boot into the M but could you get it to boot into recovery?
Don't remember if i tried actually lol. Its plain now, no root or bootstrap, but it works
Sent from my R800x using XDA
Kasper DG said:
Its plain now, no root or bootstrap, but it works
Click to expand...
Click to collapse
Strange how DroidX phones eventually become stock and unrooted :^)
Sent from my unrooted DroidX using Tapatalk
Nate2 said:
Strange how DroidX phones eventually become stock and unrooted :^)
Sent from my unrooted DroidX using Tapatalk
Click to expand...
Click to collapse
Very strange indeed. Almost like I got the sbf to work or something
Sent from my R800x using XDA
I was trying to root my phone through oden and oden crashed half way through and now my phone is bricked. I can still boot into download mode, but recovery mode just hangs at the booting screen. What can I do to get my phone back to normal?
I have a U.S. Cellular phone.
Thanks.
Which phone is it?
And what firmware were you trying to install?
Accidently sent from my GT-S5570 using xda premium
saleh.adnan said:
Which phone is it?
And what firmware were you trying to install?
Accidently sent from my GT-S5570 using xda premium
Click to expand...
Click to collapse
The phone was the Galaxy S4 from US Cellular and I was just trying to root it without any firmware.
I just got so lucky... I decided to restart my phone to get out of the boot screen for recovery mode and my phone just booted up normally! I guess I do not need help anymore. Thanks anyway.
I was using odin to get my phone back to stock and everything seemed to go ok, it said pass then rebooted but it gets to the yellow sprint screen and just stays there. The blue light is on but cannot get past this screen. I flashed the Tar from Sammobile. Anything I can do to get past this or is the phone bricked? Oh and I have tried the MF9 firmware and the MDL firmware and it gets stuck every time.
redram38 said:
I was using odin to get my phone back to stock and everything seemed to go ok, it said pass then rebooted but it gets to the yellow sprint screen and just stays there. The blue light is on but cannot get past this screen. I flashed the Tar from Sammobile. Anything I can do to get past this or is the phone bricked? Oh and I have tried the MF9 firmware and the MDL firmware and it gets stuck every time.
Click to expand...
Click to collapse
If you booted up you have to do a factory reset.
Sent from my SPH-L720 using xda app-developers app
ROMANTiC KiD said:
If you booted up you have to do a factory reset.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
That was the issue. I had to go to stock recovery and do the factory reset and not all is ok. Thanks
Let me start off by saying I apologize if this is posted somewhere already.
Here's my situation. A couple days ago I lgflashed back to stock. All went well. I then rooted and installed TWRP. No issues at all. I didn't take an update, modify the stock ROM or even flash another ROM. Just ran stock rooted. Today, I pick my phone up, go to turn it on and I'm in recovery. No big deal, right? Well I can't get out of TWRP. My backups are still showing, but when I restore it and reboot the phone I'm right back in recovery.
I can't get into download mode either. Not sure what happened and everything was fine earlier in the day. Any thoughts?
Sent from my Nexus 5 using Tapatalk
I should also say that adb doesn't recognize my phone.
Sent from my Nexus 5 using Tapatalk
droidiac13 said:
I should also say that adb doesn't recognize my phone.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I'm in your same boat right now, working on a buddy's phone cept when i formatted phone to stick a rom on it the nandroid i made got file 13'd
dcillusions77 said:
I'm in your same boat right now, working on a buddy's phone cept when i formatted phone to stick a rom on it the nandroid i made got file 13'd
Click to expand...
Click to collapse
I'm back up and running. I used this thread HERE and did the command through TWRP.
As long as you have a ROM on the phone, you should be good to go.
droidiac13 said:
I'm back up and running. I used this thread HERE and did the command through TWRP.
As long as you have a ROM on the phone, you should be good to go.
Click to expand...
Click to collapse
Tried it but it didn't work :\.....
Mine is stuck in fastboot mode whenever I try to reboot it into recovery what files are missing? Anyone know why whenever I reboot it into recovery it boots fastboot instead? Any help would be much appreciated
If you stuck in fastboot mode. Just push
laf file through fastboot to your phone.
Sent from my LG-F320L using xda app-developers app
droidiac13 said:
I'm back up and running. I used this thread HERE and did the command through TWRP.
As long as you have a ROM on the phone, you should be good to go.
Click to expand...
Click to collapse
I'm so glad your back up and running again. I've been following your thread. And thanks for sharing the fix.
Does that mean that without your knowledge, your phone may have probably automatically updated itself (OTA) when you left your phone overnight? That's why you were stucked in recovery? Because it seems so odd that you didn't do anything wrong and it suddenly behaved that way. And I have read somewhere here that OTA just installed itself automatically without user intervention. So confusing if that did happen. How is that even possible?
Sent from my LG-D802 using Tapatalk
cccho said:
If you stuck in fastboot mode. Just push
laf file through fastboot to your phone.
Sent from my LG-F320L using xda app-developers app
Click to expand...
Click to collapse
Got it up and running by downloading the FreeGee app from play store and installing TWRp that way. I had tried it before just didnt stick the first time
mrm43 said:
I'm so glad your back up and running again. I've been following your thread. And thanks for sharing the fix.
Does that mean that without your knowledge, your phone may have probably automatically updated itself (OTA) when you left your phone overnight? That's why you were stucked in recovery? Because it seems so odd that you didn't do anything wrong and it suddenly behaved that way. And I have read somewhere here that OTA just installed itself automatically without user intervention. So confusing if that did happen. How is that even possible?
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
I can only guess that it updated by itself. I really don't know what else it could be.
Sent from my LG-D800 using Tapatalk
droidiac13 said:
I can only guess that it updated by itself. I really don't know what else it could be.
Sent from my LG-D800 using Tapatalk
Click to expand...
Click to collapse
Yes it might seem that way. Thanks
Sent from my LG-D802 using Tapatalk
Good morning all,
I am throwing this out here hoping someone can please help.
Woke up yesterday to the Essential phone logo screen powered by Android... Unresponsive. Restarted with no luck. Went into recovery mode and factory reset. Went to start up animation for an hour but nothing. Device is locked (bootloader locked) and running on the latest build from Essential (7.1.1/NMJ88C/464). I have never unlocked nor flashed anything on the phone, only OTA updates directly from Essential. Just started it up again today and says your device is corrupt. Factory reset again and now cycling between logo screen and erasing circle.
Any ideas to fix the phone? Reached out to Essential but haven't heard back yet.
Thanks all!
Sent from my A0001 using Tapatalk
trsargent said:
Good morning all,
I am throwing this out here hoping someone can please help.
Woke up yesterday to the Essential phone logo screen powered by Android... Unresponsive. Restarted with no luck. Went into recovery mode and factory reset. Went to start up animation for an hour but nothing. Device is locked (bootloader locked) and running on the latest build from Essential (7.1.1/NMJ88C/464). I have never unlocked nor flashed anything on the phone, only OTA updates directly from Essential. Just started it up again today and says your device is corrupt. Factory reset again and now cycling between logo screen and erasing circle.
Any ideas to fix the phone? Reached out to Essential but haven't heard back yet.
Thanks all!
Click to expand...
Click to collapse
do you have an adb option in your recovery ?
nicoconepala said:
do you have an adb option in your recovery ?
Click to expand...
Click to collapse
Yes, I can get to an adb option in recovery
Sent from my A0001 using Tapatalk
trsargent said:
Yes, I can get to an adb option in recovery
Click to expand...
Click to collapse
ok then you should try to flash stock rom from essential
nicoconepala said:
ok then you should try to flash stock rom from essential
Click to expand...
Click to collapse
Am I able to do that with the device locked? Oem unlocking is not turned on I believe. I have never flashed anything on a phone before
Sent from my A0001 using Tapatalk
trsargent said:
Am I able to do that with the device locked? Oem unlocking is not turned on I believe. I have never flashed anything on a phone before
Click to expand...
Click to collapse
You don't need to be unlocked to adb sideload the Oreo beta builds from essentials website.
Just follow their instructions
Wrong section.
NaterTots said:
You don't need to be unlocked to adb sideload the Oreo beta builds from essentials website.
Just follow their instructions
Click to expand...
Click to collapse
Gave it a try, but it didn't resolve the issue. Got the your device is corrupt message. Any other ideas? Thanks!
Sent from my A0001 using Tapatalk
I'm searching for answers too! My essential is doing the dotted box to the dotted circle spin back & forth over & over ! I saw the dead robot with exclamation mark . The only thing on the essential website is to wipe phone ! Help. If the person that made this phone do this to people dies please let me know, so I can smile during this stressful time . If they r still alive I hope they are in agony over something thx!