Related
First of all my Moto X is a stock nothing has been modified. My provider is Verizon running the latest version of android as far as I know.
The problem I'm facing is that my phone is stuck on the Motorola M and powered by android screen when you first start the phone. I first thought it was in an infinite boot loop because no matter what I did from the phone it would not get off that screen. I tried going into the boot options by holding the power button and the volume down screen this was successful, but selecting any of the options form the list would result in the phone returning to the screen with the Motorola symbol on it and powered by android. The battery is now all the way drained and will not charge it seems. The battery is at 0% screen appears sometimes plugged into the charger then the Motorola symbol screen with the powered by android screen will come on until the phone runs out of power. Mind you this is while the phone is connected to the charger via the wall outlet. Also sometimes the phone boots up normally but after 10-60 seconds the phone turns off and returns to the Motorola symbol screen with the powered by android at the bottom.
I have been trying all day to get it to do some things. I have successfully gotten in to boot in safe mode and it still powers off and returns to the Motorola screen with the powered by android. I have got it to boot in recovery mode and I wiped the cache. I have not done a hard reset yet because I cant get it to go past the Motorola screen with the powered by android at the bottom.
I said what the heck and tried to flash a new ROM onto the phone but the phone isn't detected on the computer by gda so I never did anything with flashing.
Any solutions would be much appreciated.
sirlancealot77 said:
First of all my Moto X is a stock nothing has been modified. My provider is Verizon running the latest version of android as far as I know.
The problem I'm facing is that my phone is stuck on the Motorola M and powered by android screen when you first start the phone. I first thought it was in an infinite boot loop because no matter what I did from the phone it would not get off that screen. I tried going into the boot options by holding the power button and the volume down screen this was successful, but selecting any of the options form the list would result in the phone returning to the screen with the Motorola symbol on it and powered by android. The battery is now all the way drained and will not charge it seems. The battery is at 0% screen appears sometimes plugged into the charger then the Motorola symbol screen with the powered by android screen will come on until the phone runs out of power. Mind you this is while the phone is connected to the charger via the wall outlet. Also sometimes the phone boots up normally but after 10-60 seconds the phone turns off and returns to the Motorola symbol screen with the powered by android at the bottom.
I have been trying all day to get it to do some things. I have successfully gotten in to boot in safe mode and it still powers off and returns to the Motorola screen with the powered by android. I have got it to boot in recovery mode and I wiped the cache. I have not done a hard reset yet because I cant get it to go past the Motorola screen with the powered by android at the bottom.
I said what the heck and tried to flash a new ROM onto the phone but the phone isn't detected on the computer by gda so I never did anything with flashing.
Any solutions would be much appreciated.
Click to expand...
Click to collapse
the stock logo/bootanimation does not say "powered by android", so if yours does, it is modified.
if it doesn't get past the boot logo, you will likely need to flash at least the system partition with fastboot or rsd lite. although, if your battery is very low, flashing will probably not work. here is a solution to allow flashing with a low battery:
http://shop.teamblackhat.info/Factory-Adapters-motadapt.htm
if it does get past the boot logo, but boot loops on the animation, you probably just need to wipe data and cache in recovery (same as hard reset from the settings menu).
Not modified.
Q9Nap said:
the stock logo/bootanimation does not say "powered by android", so if yours does, it is modified.
if it doesn't get past the boot logo, you will likely need to flash at least the system partition with fastboot or rsd lite. although, if your battery is very low, flashing will probably not work. here is a solution to allow flashing with a low battery:
if it does get past the boot logo, but boot loops on the animation, you probably just need to wipe data and cache in recovery (same as hard reset from the settings menu).
Click to expand...
Click to collapse
I haven't done any modifications to the phone or had anyone do anything to it. Maybe this is the animation screen it is getting stuck on the big M and the powered by android at the bottom? Would you still suggest flashing the system partition?
Q9Nap said:
the stock logo/bootanimation does not say "powered by android", so if yours does, it is modified.
if it doesn't get past the boot logo, you will likely need to flash at least the system partition with fastboot or rsd lite. although, if your battery is very low, flashing will probably not work. here is a solution to allow flashing with a low battery:
http://shop.teamblackhat.info/Factory-Adapters-motadapt.htm
if it does get past the boot logo, but boot loops on the animation, you probably just need to wipe data and cache in recovery (same as hard reset from the settings menu).
Click to expand...
Click to collapse
This in incorrect. Motorola recently updated their apps and in turn changed the boot logo and animation. it is all over the forums.
Cyphir said:
This in incorrect. Motorola recently updated their apps and in turn changed the boot logo and animation. it is all over the forums.
Click to expand...
Click to collapse
So any solutions?
Cyphir said:
This in incorrect. Motorola recently updated their apps and in turn changed the boot logo and animation. it is all over the forums.
Click to expand...
Click to collapse
ok, thanks for the correction.
i'm running heavily debloated stock with custom logo and animation, and don't spend a lot of time on the forums.
the information on how to recover from a brick is correct.
If you didn't modify anything at all....then its probably an app you loaded recently. Perhaps one NOT from the play store???
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
kj2112 said:
If you didn't modify anything at all....then its probably an app you loaded recently. Perhaps one NOT from the play store???
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
Click to expand...
Click to collapse
I booted in safe mode that doesn't run any applications except the necessary applications and it restarts about 10-60 seconds in. The time varies.
Can I buy that piece to act like a factory cable locally?
sirlancealot77 said:
I booted in safe mode that doesn't run any applications except the necessary applications and it restarts about 10-60 seconds in. The time varies.
Can I buy that piece to act like a factory cable locally?
Click to expand...
Click to collapse
I am facing the same problem you are facing? Did you find a solution? How did you boot into safe mode?
sirlancealot77 said:
I tried going into the boot options by holding the power button and the volume down screen this was successful, but selecting any of the options form the list would result in the phone returning to the screen with the Motorola symbol on it and powered by android.
Click to expand...
Click to collapse
Are you using volume up to select an option? This sounds like you are using power to select - power does not select it instead reboots your phone.
---------- Post added at 02:54 AM ---------- Previous post was at 02:52 AM ----------
sirlancealot77 said:
The problem I'm facing is that my phone is stuck on the Motorola M and powered by android screen when you first start the phone.
Click to expand...
Click to collapse
Download and install Motorola Device Manager on your computer. Then put your phone in bootloader mode, then plug it into your computer and start MDM. It should attempt to repair your phone.
JulesJam said:
Are you using volume up to select an option? This sounds like you are using power to select - power does not select it instead reboots your phone.
---------- Post added at 02:54 AM ---------- Previous post was at 02:52 AM ----------
Download and install Motorola Device Manager on your computer. Then put your phone in bootloader mode, then plug it into your computer and start MDM. It should attempt to repair your phone.
Click to expand...
Click to collapse
Question, since you have experience with MDM. Do you need to be fully stock to use MDM. For example if I have TWRP will it just write over my previous images or will it fail like a OTA would?
I agree getting the stock images right away would be nice. I have always received them from Moto within a day when requested but I do see the advantages of getting it right away for safe keepings. I always make sure to have a copy of my most recent images to return to stock. I have always used fastboot or Mfastboot since the gnex, I stay away from toolkits, but it sounds like MDM is Moto's version of their toolkit?
Travisdroidx2 said:
Question, since you have experience with MDM. Do you need to be fully stock to use MDM. For example if I have TWRP will it just write over my previous images or will it fail like a OTA would?
Click to expand...
Click to collapse
I believe it will fail.
---------- Post added at 06:26 PM ---------- Previous post was at 06:24 PM ----------
Travisdroidx2 said:
I agree getting the stock images right away would be nice. I have always received them from Moto within a day when requested
Click to expand...
Click to collapse
From what I am reading on the Motorola forums, Motorola has still not produced the 5.0 stock images, just kit kat.
---------- Post added at 06:31 PM ---------- Previous post was at 06:26 PM ----------
Travisdroidx2 said:
I stay away from toolkits, but it sounds like MDM is Moto's version of their toolkit?
Click to expand...
Click to collapse
I don't know what your definition of a tool kit is but MDM is a piece of software produced by Motorola that can run some sort of diagnostic on your phone and either update it to the latest version of the software or repair it if your system is damaged.
My brother just got an atrix hd from a guy at work. The phone will not boot into normal, recovery, or anything else besides the AP Fastboot mode. in the AP fastboot screen the text says:
AP Fastboot Flash Mode (S)
10.9B(*) (sha-2e68372, 2012-11-17 23:3308)
eMMC info: size 8GB
Device is LOCKED, Status Code:0
Battery OK
Transfer Mode:
USB Connected
Fastboot Reason: Boot menu selected
From what my brother knows the guy had the phone in his lunchbox and when he got home from work and tried to turn it on this is what the phone was doing.
Is there something i can try or a way to flash a system image? I've rooted, unlocked the bootloader and installed custom roms on a variety of phones and im sure i can get this phone straightened out if i was just pointed in the right direction. Thanks for any and all the help! its greatly appreciated!!!
Mythtools is your friend. Here's a link to the thread.
http://forum.xda-developers.com/showthread.php?t=2262726
[Tools][TheMythTeam] Myth Tools for Atrix HD - Update v1.3 (24/03) - Big Update
Sent from my MB886 using XDA Free mobile app
jrodbrown58 said:
My brother just got an atrix hd from a guy at work. The phone will not boot into normal, recovery, or anything else besides the AP Fastboot mode. in the AP fastboot screen the text says:
AP Fastboot Flash Mode (S)
10.9B(*) (sha-2e68372, 2012-11-17 23:3308)
eMMC info: size 8GB
Device is LOCKED, Status Code:0
Battery OK
Transfer Mode:
USB Connected
Fastboot Reason: Boot menu selected
From what my brother knows the guy had the phone in his lunchbox and when he got home from work and tried to turn it on this is what the phone was doing.
Is there something i can try or a way to flash a system image? I've rooted, unlocked the bootloader and installed custom roms on a variety of phones and im sure i can get this phone straightened out if i was just pointed in the right direction. Thanks for any and all the help! its greatly appreciated!!!
Click to expand...
Click to collapse
Well, firstly, you need to unlock its bootloader IMMEDIATELY then you can try other action (reflash stock roms, etc..). Using Myth Tools is recommended in the post above.
After unlocking bootloader, you can try to download stock firmware from here:
Then flash it with Myth Tools (recommend) or RSDLite
If you satisfy with stock one, just keep it and do further mods or you can flash custom recovery before flashing custom roms.
That's my recommendation but you need to do the FIRST step is Unlocking Bootloader right now
Hope it helps.
DK
I can't even root it, the phone shuts off if disconnected from a charger. And even when on the charger it keeps boot looping.
Sent from my GT-N7105 using Tapatalk
jrodbrown58 said:
I can't even root it, the phone shuts off if disconnected from a charger. And even when on the charger it keeps boot looping.
Sent from my GT-N7105 using Tapatalk
Click to expand...
Click to collapse
The boot looping which you mean is going to the fastboot mode, right?
Did you try to enter bootmenu (turn off phone, hold both vol + and vol - then press press powermenu to turn on) and select "normal powerup"?
Can you tell me whether your phone has ATT logo on its screen's bottom?
Maybe flashing back to its correct original firmware by RSDLite can help to bring it back then we can root and unlock bootloader.
But we need to know exactly which is its original firmware before it stucks there.
I've got it fixed...turns out the battery was bad. So luckily I switched it out with an atrix HD with a broken screen we had and it booted right up so I rooted, unlocked the bootloader and flashed the stock logo and a custom ROM. All smiles now! Thanks for everyone's help!
Sent from my GT-N7105 using Tapatalk
Congrats!
devilsking said:
The boot looping which you mean is going to the fastboot mode, right?
Did you try to enter bootmenu (turn off phone, hold both vol + and vol - then press press powermenu to turn on) and select "normal powerup"?
Can you tell me whether your phone has ATT logo on its screen's bottom?
Maybe flashing back to its correct original firmware by RSDLite can help to bring it back then we can root and unlock bootloader.
But we need to know exactly which is its original firmware before it stucks there.
Click to expand...
Click to collapse
Having a issue with bootlooping, I unlocked the bootloader. I tried to install stock firmware but the phone doesnt even get past the motorola symbol it justs goes blank that tries to boot again. I can get it in to fastboot though. Its ATT version, is there anyway I can fix it?
Did Myth complete the flashing process? Have you tried using RSD lite to flash stock?
PCiE said:
Having a issue with bootlooping, I unlocked the bootloader. I tried to install stock firmware but the phone doesnt even get past the motorola symbol it justs goes blank that tries to boot again. I can get it in to fastboot though. Its ATT version, is there anyway I can fix it?
Click to expand...
Click to collapse
do you install custom roms before flashing stock firmware?
devilsking said:
do you install custom roms before flashing stock firmware?
Click to expand...
Click to collapse
you thinking it's the internal sd crap too...
devilsking said:
do you install custom roms before flashing stock firmware?
Click to expand...
Click to collapse
No
think im bootlooped after changing a digitizer
Someone in a club that i am in ask if anyone fixed phones, I'm a hobbyist, but very good with hardware and worked on countless ipods, tablets, Iphones, you name it. Some of you guys are like GOD MODE ON but i get buy, and really was just trying to help someone. (i haven't even cashed her check) so i tell her hey 15 bucks a phone i'll change the glass if you buy the parts.. grrr my mistake. i got this atrix hd. all i did was change the digitizer and now it hangs at the at&T screen... i tried RSD and flashed successfully, i tried myth and flashed successfully. i have no idea whats wrong with this POS.. i can get in fast boot and recovery ok. Does this phone need a sim in for first boot? i'm loosing my mind, i can't help but wonder if it's the new chinese digitizer, I wish i could get a system log outta this thing to see how it's hanging up.... any help would be greatly appreciated.
fudpucker said:
Someone in a club that i am in ask if anyone fixed phones, I'm a hobbyist, but very good with hardware and worked on countless ipods, tablets, Iphones, you name it. Some of you guys are like GOD MODE ON but i get buy, and really was just trying to help someone. (i haven't even cashed her check) so i tell her hey 15 bucks a phone i'll change the glass if you buy the parts.. grrr my mistake. i got this atrix hd. all i did was change the digitizer and now it hangs at the at&T screen... i tried RSD and flashed successfully, i tried myth and flashed successfully. i have no idea whats wrong with this POS.. i can get in fast boot and recovery ok. Does this phone need a sim in for first boot? i'm loosing my mind, i can't help but wonder if it's the new chinese digitizer, I wish i could get a system log outta this thing to see how it's hanging up.... any help would be greatly appreciated.
Click to expand...
Click to collapse
What ROM was on there before you changed the digitizer? Have you tried flashing a custom recovery and a custom ROM?
fudpucker said:
Someone in a club that i am in ask if anyone fixed phones, I'm a hobbyist, but very good with hardware and worked on countless ipods, tablets, Iphones, you name it. Some of you guys are like GOD MODE ON but i get buy, and really was just trying to help someone. (i haven't even cashed her check) so i tell her hey 15 bucks a phone i'll change the glass if you buy the parts.. grrr my mistake. i got this atrix hd. all i did was change the digitizer and now it hangs at the at&T screen... i tried RSD and flashed successfully, i tried myth and flashed successfully. i have no idea whats wrong with this POS.. i can get in fast boot and recovery ok. Does this phone need a sim in for first boot? i'm loosing my mind, i can't help but wonder if it's the new chinese digitizer, I wish i could get a system log outta this thing to see how it's hanging up.... any help would be greatly appreciated.
Click to expand...
Click to collapse
There's a chance that it could be the digitizer. About a week ago I replaced my Dad's digitizer and I read a crap ton of reviews before purchasing the one I did. Of the bad ones, a few had people complaining about it not working, most were the top 10% of the screen wouldn't respond to touches (like swiping down the nonfiction drawer), and I saw a couple describing your situation.
If you never had a custom rom installed, were rooted, or had the bootloader unlocked before doing this, I doubt that there's anything you can flash that'll fix this. If the bootloader was unlocked before doing this and there was a custom rom installed on the phone, you might have to flash Philz CWM, format the internal sd, and change its mount point to /data/media then format it again. Not changing the internal sd mount point after flashing a fastboot when coming from custom 4.2+ roms causes bootloops.
This is the digitizer I used to fix my Dad's Atrix HD last week. He hasn't had a problem with it whatsoever. My Dad is an ass of the highest degree so I'd know with a loud angry voice if there was ANY minor issue with it.
AT&T splash screen stuck after chinese digitizer install
skeevydude said:
There's a chance that it could be the digitizer. About a week ago I replaced my Dad's digitizer and I read a crap ton of reviews before purchasing the one I did. Of the bad ones, a few had people complaining about it not working, most were the top 10% of the screen wouldn't respond to touches (like swiping down the nonfiction drawer), and I saw a couple describing your situation.
If you never had a custom rom installed, were rooted, or had the bootloader unlocked before doing this, I doubt that there's anything you can flash that'll fix this. If the bootloader was unlocked before doing this and there was a custom rom installed on the phone, you might have to flash Philz CWM, format the internal sd, and change its mount point to /data/media then format it again. Not changing the internal sd mount point after flashing a fastboot when coming from custom 4.2+ roms causes bootloops.
Click to expand...
Click to collapse
Ok so there are multiple questions to answer here.
#1 i do not recall which rom was on the phone.. although it appears it was the lastest AT&T as RSD re-Flashed it with a pass. I suppose i should have checked but i've never ran in to this situation. I was just changing the glass out.... you remove about 16 screws, pop the glass out and put a new one it...
#2 the customer does not want the phone rooted or moded, just stock
#3 the bootloader is locked and mythtool instructions are saying you have to be in debugging mode to unlock.... thats not gonna happen cause it don't boot..
So does anyone know if this thing needs a sim for a first boot after an actuall battery pull?
Also..
I unplugged the digitizer and tried to boot thinking hey other phones will boot without the digitizer, but same thing... AT&T Screen and it's hung. everything on this board is shielded.. so i doubt it got ESD zapped, and i did take static potective precautions.
I bet this thing would look good with a .45cal hole in it.
fudpucker said:
Ok so there are multiple questions to answer here.
#1 i do not recall which rom was on the phone.. although it appears it was the lastest AT&T as RSD re-Flashed it with a pass. I suppose i should have checked but i've never ran in to this situation. I was just changing the glass out.... you remove about 16 screws, pop the glass out and put a new one it...
#2 the customer does not want the phone rooted or moded, just stock
#3 the bootloader is locked and mythtool instructions are saying you have to be in debugging mode to unlock.... thats not gonna happen cause it don't boot..
So does anyone know if this thing needs a sim for a first boot after an actuall battery pull?
Also..
I unplugged the digitizer and tried to boot thinking hey other phones will boot without the digitizer, but same thing... AT&T Screen and it's hung. everything on this board is shielded.. so i doubt it got ESD zapped, and i did take static potective precautions.
I bet this thing would look good with a .45cal hole in it.
Click to expand...
Click to collapse
#1 That's what I'd assume...and it's 22 screws with fine threading... And if you're getting the AT&T boot logo after a fastboot flash, the bootloader is locked.
#2 Customer's loss
#3 Never actually tested that, but I've never once needed a sim for it to boot up....actually, my first boot ever might have been sim free...been a year now so I'm not really sure.
And I didn't take static precautions.
You didn't accidentally warp or mess up the motherboard on the blow dryer part of the digitizer swap? Or any unnecessary bending on the board with you were prying the screen from it? Those two are the only "dangerous" parts in any Atrix HD repair...unless someone isn't steady with a screwdriver, then there are 46 "dangerous" parts to the repair.
Next time you power up the phone, hold down both volumes and power to access the boot menu. Use volume down to scroll to recovery and volume up to select it. Once in recovery, do a factory reset as well as any cache or dalvik wipes available. If a fastboot flash and all the wipes in stock recovery don't fix it, I'm not really sure what will aside from a new motherboard -- in which case you're better off spending an extra 20-30 and just getting a used Atrix HD like I did....I mean, 50 for just a motherboard or 80 for the all the hardware plus accessories...not really a hard choice seeing as the customer will at least have some backup repair parts in case something bad happens in the future.
Stock recovery is worthless
skeevydude said:
#1 That's what I'd assume...and it's 22 screws with fine threading... And if you're getting the AT&T boot logo after a fastboot flash, the bootloader is locked.
did the factory reset and delete cache.. stock recovery doesn't give an option for dalvik cache... can you flash phills with a locked bootloader?
Click to expand...
Click to collapse
fudpucker said:
skeevydude said:
#1 That's what I'd assume...and it's 22 screws with fine threading... And if you're getting the AT&T boot logo after a fastboot flash, the bootloader is locked.
did the factory reset and delete cache.. stock recovery doesn't give an option for dalvik cache... can you flash phills with a locked bootloader?
Click to expand...
Click to collapse
I wouldn't use Philz until you unlock the bootloader.
Click to expand...
Click to collapse
fudpucker said:
skeevydude said:
#1 That's what I'd assume...and it's 22 screws with fine threading... And if you're getting the AT&T boot logo after a fastboot flash, the bootloader is locked.
did the factory reset and delete cache.. stock recovery doesn't give an option for dalvik cache... can you flash phills with a locked bootloader?
Click to expand...
Click to collapse
The only thing you can flash with a locked bootloader is your stock rom with fastboot. That's it. When locked, if manually flashing all the partitions, flashing with RSD, wiping everything that can be wiped, and you're still not booting, then the phone is either truly bricked or you're not doing something correctly.
The only exception to the above is if something went bad during the OTA and you have some sort of partition mix up, in which case the official fastboot for the OTA might fix it for you -- there isn't a stock fastboot for the OTA yet.
Click to expand...
Click to collapse
Hey guys!
So I've got an issue I'm struggling with on the Moto G (2014). First I'll tell you as much as I can about the phone: I bought it from the Motorola website, so I think it's running whatever the stock firmware is. Also, it's the 8 GB US model and isn't tied to any carrier. (I have it on T-Mobile, but got it directly from Motorola. I was trying to figure out what the firmware is but the closest I've been able to get is by running the Motorola Device Manager app while the phone is in fastboot mode. It says there are no available updates for: 21.11.17.titan_retuaws.retuaws.en.us The bootloader is locked and the phone is not rooted. It's pure stock, though it might have automatically gotten an OTA update to the latest official release, I can't be sure because I bought it for someone else.
Okay, so the problem. I'd bought the phone for my dad and set it up and it worked fine for about two months. Yesterday, he came by my place and asked if I could take a look at it because it was stuck on one screen and since there was no removable battery, he didn't know how to reset it. The screen it was stuck on is the boot screen where the Motorola logo is supposed to come up. It was up, but the bottom half of the logo was stretched to the side and pixelated so my first reaction was "crap, he hit it against something and there's damage to the screen." But there was no visible damage to the screen anywhere (neither from a hard hit or from pressure) and he's got the flip case for it and he said it hadn't been hit or anything.
I tried to power it down by holding down the power button, but as soon as it went off, it tried to start up again. A bootloop that always froze on that messed up Motorola boot screen. I set it on the charger for a bit and let it run through the loop a few times and at one point it got as far as the "world" screen where it shows a cartoon planet. This extended down past where the weird stretch happened on the motorola graphic and it was perfectly clear so I realized there was no damage to the screen, just some sort of boot error.
So then I tried booting into fastboot (hold both volume buttons down along with the power button for a few seconds, release) and I was able to get into fastboot. I tried scrolling down to recovery and then hitting the volume up key to select it but the second I hit the volume up key (the selection key in this mode) it reboots the phone. It doesn't go into the recovery screen, just turns off the phone. I tried this for the "Factory" (reset) option, for the "Normal Powerup" option, and the others. Instead of getting anything different, selecting any of them turns the phone off and nothing happens. The computer is recognizing that there's a device connected to it when I have the phone plugged in via usb in fastboot to my Windows 8 laptop. It also appears that I can enter commands in fastboot. (Though I'm not sure what to put in to fix this so I'm turning to you guys.)
So I can't figure out what's wrong. I've got some experience in flashing roms, both manually and with some of the tools, but haven't had to deal with what I'm assuming is a soft brick before.
Can anyone offer any help?
Thanks very much.
Watch this video and try again
https://www.youtube.com/watch?v=vf2sOPoE2b4
Roldorf said:
Watch this video and try again
https://www.youtube.com/watch?v=vf2sOPoE2b4
Click to expand...
Click to collapse
Unfortunately that didn't work. I was able to click the "restore to factory" part and it seemed to do that but I tried it again with the "wipe cache partition" and it just reset. I tried to restart normally and nothing happened. I will start boot and go to the Motorola logo but will always fail there, no matter what I try.
I'm still stuck with the soft-bricked phone. Any help going from Fastboot to somehow getting it to work?
(As I stated in the OP, the recovery options don't work. It seems only the Fastboot area is working.)
try to reflash the rom via fastboot, using the commands on 4.2 on this thread
if you have fastboot working they must work and re-flash the stock rom and everything back to stock...
to have the XML zip of yours rom search in here and download the file regards yours model and OS version that you wanna...
download, very slow download, unzip, to the some folder of mfastboot and give the commands a try... :good:
This is how to solve *ANY* softbrick on the Moto G 2014 (2nd Gen Moto G)
Try unlocking your bootloader with the given instructions on Motorola's website. You can flash a recovery like TWRP or CWM using mfastboot-v2. After flashing the recovery you can reinstall a custom ROM or stock ROM to fix the soft brick. ADB is only available if you enabled USB debugging although it will allow few commands. Using mfastboot-v2 after unlocking the bootloader will play the main factor in resolving the soft brick.:laugh::good:
eyhajee said:
Try unlocking your bootloader with the given instructions on Motorola's website. You can flash a recovery like TWRP or CWM using mfastboot-v2. After flashing the recovery you can reinstall a custom ROM or stock ROM to fix the soft brick. ADB is only available if you enabled USB debugging although it will allow few commands. Using mfastboot-v2 after unlocking the bootloader will play the main factor in resolving the soft brick.:laugh::good:
Click to expand...
Click to collapse
hello eyhajee.
My Moto G 2014 xt1068, running on Android 5.0.2 has some softbrick issue.
I have unlocked its bootloader, rooted it, unrooted it and while I was trying to lock its bootoader, I forgot to enable USB debugging and now it's stuck on fastboot mode.
So I wanna ask that can flashing a custom ROM turn my phone on??
I think so. If you are able to run some basic commands you should be able to flash it to emergency mode.
Hi all, recently I flashed a custom rom on my nexus 6 and it started bootlooping.
Also as mentioned in the title, my volume buttons are faulty which prevents me from booting into recovery.
I have tried using adb but it kept saying my device was offline.
Is there any way I can somehow boot in bootloader?
Are there any suggestions?
Any and all assistance are appreciated. Thank you!
Arthurleeclueless said:
Hi all, recently I flashed a custom rom on my nexus 6 and it started bootlooping.
Also as mentioned in the title, my volume buttons are faulty which prevents me from booting into recovery.
I have tried using adb but it kept saying my device was offline.
Is there any way I can somehow boot in bootloader?
Are there any suggestions?
Any and all assistance are appreciated. Thank you!
Click to expand...
Click to collapse
How are the buttons faulty? Can you remove the volume down key and press the contact inside? That would be the only option if you can't ADB as far as I know.
---------- Post added at 04:57 PM ---------- Previous post was at 04:53 PM ----------
Otherwise, I would suggest returning it. Is it on a custom ROM? Where is it bootlooping? Splash screen or boot animation?
Have you tried "fastboot reboot-bootloader"?
JimSmith94 said:
Have you tried "fastboot reboot-bootloader"?
Click to expand...
Click to collapse
you have to run that in fastboot, in the bootloader. why would he run that in fastboot if he could get into bootloader already? the point is that he cant get into the bootloader.
simms22 said:
you have to run that in fastboot, in the bootloader. why would he run that in fastboot if he could get into bootloader already? the point is that he cant get into the bootloader.
Click to expand...
Click to collapse
Sorry, I hadn't tried it and thought it might work from any phone state. What would be the purpose of rebooting into the bootloader if you're already in the bootloader?
JimSmith94 said:
Sorry, I hadn't tried it and thought it might work from any phone state. What would be the purpose of rebooting into the bootloader if you're already in the bootloader?
Click to expand...
Click to collapse
after flashing something, and something else needs to be flashed or done while I'm the bootloader
Evolution_Tech said:
How are the buttons faulty? Can you remove the volume down key and press the contact inside? That would be the only option if you can't ADB as far as I know.
---------- Post added at 04:57 PM ---------- Previous post was at 04:53 PM ----------
Otherwise, I would suggest returning it. Is it on a custom ROM? Where is it bootlooping? Splash screen or boot animation?
Click to expand...
Click to collapse
Hi thanks for your suggestion,
I'm running, a custom rom chroma and it only started bootlooping after I flashed the latest version 17/6 on my nexus 6. The volume down button does not respond at all
It bootloops from the custom boot animation all the way to android is starting before restarting the whole process again, skipping the Google logo. It does not at any point actually boot into the home screen.
I might try tearing down my phone to make the contacts work otherwise I'm pretty much acrewed I guess
Arthurleeclueless said:
Hi thanks for your suggestion,
I'm running, a custom rom chroma and it only started bootlooping after I flashed the latest version 17/6 on my nexus 6. The volume down button does not respond at all
It bootloops from the custom boot animation all the way to android is starting before restarting the whole process again, skipping the Google logo. It does not at any point actually boot into the home screen.
I might try tearing down my phone to make the contacts work otherwise I'm pretty much acrewed I guess
Click to expand...
Click to collapse
I recommend this guide:
https://www.ifixit.com/Teardown/Nexus+6+Teardown/32877
JimSmith94 said:
Sorry, I hadn't tried it and thought it might work from any phone state. What would be the purpose of rebooting into the bootloader if you're already in the bootloader?
Click to expand...
Click to collapse
After you unlock your bootloader you have to reboot for it to be effective. Also, if you flash a new bootloader it is not active until it is rebooted. And you do both of those from fastboot, so there needs to be a way to reboot the bootloader from fastboot.
(In general, bootloaders, recoveries and kernels are all run from memory, not their storage. That's why you can flash them while using them. In fact, you don't even have to flash a recovery, you can fastboot into one right from an image file.)
brizey said:
After you unlock your bootloader you have to reboot for it to be effective. Also, if you flash a new bootloader it is not active until it is rebooted. And you do both of those from fastboot, so there needs to be a way to reboot the bootloader from fastboot.
(In general, bootloaders, recoveries and kernels are all run from memory, not their storage. That's why you can flash them while using them. In fact, you don't even have to flash a recovery, you can fastboot into one right from an image file.)
Click to expand...
Click to collapse
I'll be honest with you, well, just because I'm that kind of person. some even say that I'm too honest. but I have never in my life reboot the bootloader after unlocking the bootloader or flashing a new bootloader. to say that it is needed is untrue. I've owned every nexus but the n7(2013), and the process is exactly alike on every nexus, and it never includes rebooting the bootloader.
simms22 said:
I'll be honest with you, well, just because I'm that kind of person. some even say that I'm too honest. but I have never in my life reboot the bootloader after unlocking the bootloader or flashing a new bootloader. to say that it is needed is untrue. I've owned every nexus but the n7(2013), and the process is exactly alike on every nexus, and it never includes rebooting the bootloader.
Click to expand...
Click to collapse
I'm just cautious, lol. Most instructions say to do it. Plus I want to know RIGHT THEN if there was an issue flashing the bootloader. Not that I would be any less ****-ed, lol.
On the 2012 N7, pretty sure you had to reboot into the system before the version would change on the bootloader screen (been a while, though...may be mis-remembering). Tegra 3 was a quirky MFer.
So I have this phone (SM-N920P) that a few days ago just went black in the midst of operation... the power button alone would not turn it back on... eventually the power and volume down did power it back up (if it was ever really even off) but at that point it stuck at the boot screen.
So I have went though what I think is every possible option... but I willing to see if there is anything else..
I have used Odin to load various flavors of stock ROMS (it was stock when it went into this condition so it was locked down before it "died:
no developer tools and FRP lock is on.... I tried some Roms that said they could bypass the FRP lock and allow some custom Rom.. thinking that would help but at this point I am not sure that would even matter considering where I am with this unit, regardless they would not load.. or get past the FRP lock..
there are tons of files out there and some seem to come from questionable repositories.. this is my first foray into android issues.. but no one makes it really easy or "safe" feeling..
Anyway the last thing I tried was loading one of the frp unlock roms which fail and cause the phone to boot to a bad load blue screen... then I unpacked an md5 file and took just the recovery.img out... renamed as tar and loaded that...
At that point the phone does boot past the bad load, but I am right back to just that splash screen.. and no matter what I cannot get it to go to an Android screen to use the recovery.img I believe I just loaded.
I loaded fastboot and adb but at this point they do not see a device.. so something beyond Odin.. or some "special" file may be the only hope? Or it is just shot? seems like it should be able to be fixed though... I have spent like 12 hours trying different things so far.
I did get one ROM to load that showed some android output at the top of the boot screen.. and when I did the normal vol up, power, home.. it did go into another screen.. which looked like Recovery... but it just said turn off auto reboot and the Hard Reset the device...
but I could not do anything but reset the device using vol down and power...
The power alone still never does anything... those are the 2 keys.. power alone does nothing... and I cannot get into the android recovery screen.. any help would be great.. thanks.:good:
Hold the power + home + vol down buttons for 7-10 seconds until screen goes off. Then boot into download mode and flash TWRP which you'll then use to flash a working ROM.
Blocked by FRP Lock
duckynawal said:
Hold the power + home + vol down buttons for 7-10 seconds until screen goes off. Then boot into download mode and flash TWRP which you'll then use to flash a working ROM.
Click to expand...
Click to collapse
I can get to that point... but load fails with the Custom Binary(Recovery) Blocked by FRP Lock.. I tried every version of twrp available..
and since the phone cannot get to anything except the download and boot screen I cannot alter any normal usb debug or OEM setting...
MagicNote said:
I can get to that point... but load fails with the Custom Binary(Recovery) Blocked by FRP Lock.. I tried every version of twrp available..
and since the phone cannot get to anything except the download and boot screen I cannot alter any normal usb debug or OEM setting...
Click to expand...
Click to collapse
Since you can boot into download mode, flash TWRP using Odin, then boot into recovery.
Hope this brings some clarity to your current predicament. Wish I had good news.
I've ran into this problem twice now either using .img to .tar tool that isn't set up properly with an incompatable version of stock rom or a corrupt dump of a stock rom or even using a proper stock rom. Or if you just so happen to accidently turn off O..E.M unlock... and your phone died or you restarted it.... Download mode spits out some red code usually or fails or even can complete but not in any case I've ever seen and boot sucessfully.... usually if you try to many times with odin you'll end up with a blue screen that comes up stating something went wrong during update process and to use Samsung's smart switch program on a pc. Only problem is at this point you've already tripped Knox and your warranty is now void so downloading smart switch and typing in your serial and one I will only give you another error stating that your phone is not comparable with smart switch due to Knox being tripped at 0x1......
At that point there are a couple options claim insurance if you have it, $200 or if you don't have insurance. Samsung will give you a spill about how your 1yr warranty is over and even if it isn't when they get your phone they will see your Knox status of 0x1 and tell you sorry your warranty is void due to end user tampering. So they offer a reflash for a cool $80 without warranty and that will reset your phone back to O.E.M specs with a Knox of 0x0 fix it for a mere $80. Smartswitch won't reflash firmware do to Knox being tripped. Sorry. You are more than welcome to try....
COLOR="red"]NEVER, I REPEAT, NEVER TURN OFF O.E.M. UNLOCK UNDER ANY CIRCUMSTANCES IF YOU HAVE ROOTED YOUR PHONE, OR PUT A CUSTOM KERNEL OR FLASH A CUSTOM RECOVERY OR YOUR FAIL TO BOOT.[/COLOR]If you turned off O.E.M unlocking. Basically O.E.M unlocking is telling your phone it's okay that Knox is tripped. O.E.M unlock allows the skipping verified samsung signature checks on the first rom based bootloade rduring the boot sequence alowing it to bypass into the secondary bootloader and kernel.
O.E.M. stands for "Original Equipment Manafacturer" i.e. being Samsung in this case so when you have not done anything to your phone when it comes brand new out of the package. Developer mode is hidden and unacessable for a reason.... O.E.M unlock means that in download mode you can flash unofficial code, i.e. C.W.M., TWRP, Other unsigned code from various developers. With no hassle due to Samsung being so kind to us developers and allowing us the option to manually unlock our bootloaders.
Usually what happens specifically is Samsung has a secure bootloader which uses digital certificates to ensure that the software loaded before the operating system is trusted to boot the linux kernel shell we all know and love as android OS when you load a custom bootloader such as anything not signed by Samsung it fails to pass the signature checks and that's exactly what turning off O.E.M unlock did.
But with us all being blessed with the option to manually unlock our Bootloaders through O.E.M unlock now so many options are open to us so as but not limited to.: Roms, MODS, Hacks, Busybox, Root, Xposed, Various Root Applications, Magisk, Kingoroot, GeoHots stuff, HashCodes stuff, even have the oppourtunity to create and test various of our own creations.
Once upon a time Bootloaders were locked, meaning, No Roms, No kernels, etc, etc... Very, Very difficult to even root phone's. The reason I go into all of that is Because with great power comes great responsibility. Always back up your eds partition, and always always if you root and like to run custom rom Roms and all the development for this scene that only continues to grow and evolve Make sure you do one thing if nothing else and that is to read, read, read and know your phone inside and out. I am a developer and I work with software as much as I do hardware. I can afford to make mistakes as these aren't my daily drivers. I suggest if you like to unlock the full potential of your devices then please heed my warning about reading and knowing all the dos and dont's for what your devices is capable of and what will turn it into a very expensive paper weight. I'm not being a **** I'm trying to help. Because you have now tripped your Knox counter meaning it is permanently stuck in the state of your phone now having a void warranty and there is no going back.
Once you turn O.E.M mode off you lock your bootloader and if you've already tripped Knox you can't flash a stock bootloader or Rom because your phone's hardware is preventing anything unauthorized from making it past the kernel checks..... clear some things up for You? I don't care the people say they have work around forCOLOR="red"]"custom binary frp lock"[/COLOR]because I have yet to see a phone recover. P.S. word to the wise that is one error you never, and I mean never want to see on your boot screen...
I came back from it once with a zeroed out serial number and a null one I. Once and that's a whole nother ball of wax. Claim warranty, play stupid if still covered if not Sammy will know so just shell out the $80 send it to them. They will reflash it and that's the end of that.
P.S. MODS, Why can't I just indent the first letter or word of my paragraphs? It's really bothering me. I tried for like 20 minutes. Everything from highlighting my whole paragraph, to highlighting the first word or letter. Even went as far as editing the hypertext php to no avail...COLOR="red"]What Am I Doing Wrong?[/COLOR]
---------- Post added at 03:11 AM ---------- Previous post was at 02:29 AM ----------
[/COLOR]
MagicNote said:
So I have this phone (SM-N920P) that a few days ago just went black in the midst of operation... the power button alone would not turn it back on... eventually the power and volume down did power it back up (if it was ever really even off) but at that point it stuck at the boot screen.
So I have went though what I think is every possible option... but I willing to see if there is anything else..
I have used Odin to load various flavors of stock ROMS (it was stock when it went into this condition so it was locked down before it "died:
no developer tools and FRP lock is on.... I tried some Roms that said they could bypass the FRP lock and allow some custom Rom.. thinking that would help but at this point I am not sure that would even matter considering where I am with this unit, regardless they would not load.. or get past the FRP lock..
there are tons of files out there and some seem to come from questionable repositories.. this is my first foray into android issues.. but no one makes it really easy or "safe" feeling..
Anyway the last thing I tried was loading one of the frp unlock roms which fail and cause the phone to boot to a bad load blue screen... then I unpacked an md5 file and took just the recovery.img out... renamed as tar and loaded that...
At that point the phone does boot past the bad load, but I am right back to just that splash screen.. and no matter what I cannot get it to go to an Android screen to use the recovery.img I believe I just loaded.
I loaded fastboot and adb but at this point they do not see a device.. so something beyond Odin.. or some "special" file may be the only hope? Or it is just shot? seems like it should be able to be fixed though... I have spent like 12 hours trying different things so far.
I did get one ROM to load that showed some android output at the top of the boot screen.. and when I did the normal vol up, power, home.. it did go into another screen.. which looked like Recovery... but it just said turn off auto reboot and the Hard Reset the device...
but I could not do anything but reset the device using vol down and power...
The power alone still never does anything... those are the 2 keys.. power alone does nothing... and I cannot get into the android recovery screen.. any help would be great.. thanks.:good:
Click to expand...
Click to collapse