Database Develop

[Q] Atrix HD wont boot into anything...

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

Boot Loop

I have had my HTC One M7 shortly after it was release. I got it from ATT. I immediately found a guide here and rooted it. I had TWRP and every time ATT tried to push an OTA I would refuse. I haven't bothered with it until a couple weeks ago when I wanted to put in KIT KAT. so I found m7_Stock_Rooted_4.18.502.7_odex.zip. I did a dirty upgrade, as the thread said it was okay. And it was. I am going on a trip so I purchased a sim unlock code in between upgrading to kitkat and today.
I got another OTA. I must not have read the bootloader correctly to refuse the install. I was no longer rooted. I come back to XDA and thought what the heck, I'll try out this ROM, it looks nice: Android_Revolution_HD-One_83.1.zip. I use TWRP to put the ROM in and now I am full of fail. After a little bit of Google I decided to try to do a factory reset. And now I am stuck in a boot loop. I have went back to Google but so far all I have seen is use adb or some other method to put things on the "sd card". But how would I do that when this phone doesn't have a sim card and I can't hook it up to my computer anymore? FWIW at some point in the boot loop my computer will recognize the phone, but it won't stay in that state long before it goes away. What happens is my phone starts too boot. Boot screen comes up. After about 10-15 seconds it restarts. This time saying entering recovery.... at the top. That lasts for about 2 seconds, phone goes black and reboots like normal. Over and over.
Best I can do is get to the android hard reset screen by holding power and reset screen. But that is saying "tampered" and "unlocked" at top. I chose the factory setting option and that doesn't do anything to alter the current state.
Edit:
When I went to flash Android Revolution ROM I chose wipe data. It gave some error that some files were not copied. So I ran it again, straight from TWRP. But that never installed right and I was stuck in a boot loop. I don't have many options with the android hard reset menu. But if choose restore, I will get to see the screen from TWRP flash for just a moment before it goes away and reboots.
Also I do see my phone when I have it plugged in the control panel (windows). Under devices and printers, it is listed as Android 1.0 under unspecified devices.

Budee80 said:
I have had my HTC One M7 shortly after it was release. I got it from ATT. I immediately found a guide here and rooted it. I had TWRP and every time ATT tried to push an OTA I would refuse. I haven't bothered with it until a couple weeks ago when I wanted to put in KIT KAT. so I found m7_Stock_Rooted_4.18.502.7_odex.zip. I did a dirty upgrade, as the thread said it was okay. And it was. I am going on a trip so I purchased a sim unlock code in between upgrading to kitkat and today.
I got another OTA. I must not have read the bootloader correctly to refuse the install. I was no longer rooted. I come back to XDA and thought what the heck, I'll try out this ROM, it looks nice: Android_Revolution_HD-One_83.1.zip. I use TWRP to put the ROM in and now I am full of fail. After a little bit of Google I decided to try to do a factory reset. And now I am stuck in a boot loop. I have went back to Google but so far all I have seen is use adb or some other method to put things on the "sd card". But how would I do that when this phone doesn't have a sim card and I can't hook it up to my computer anymore? FWIW at some point in the boot loop my computer will recognize the phone, but it won't stay in that state long before it goes away. What happens is my phone starts too boot. Boot screen comes up. After about 10-15 seconds it restarts. This time saying entering recovery.... at the top. That lasts for about 2 seconds, phone goes black and reboots like normal. Over and over.
Best I can do is get to the android hard reset screen by holding power and reset screen. But that is saying "tampered" and "unlocked" at top. I chose the factory setting option and that doesn't do anything to alter the current state.
Edit:
When I went to flash Android Revolution ROM I chose wipe data. It gave some error that some files were not copied. So I ran it again, straight from TWRP. But that never installed right and I was stuck in a boot loop. I don't have many options with the android hard reset menu. But if choose restore, I will get to see the screen from TWRP flash for just a moment before it goes away and reboots.
Also I do see my phone when I have it plugged in the control panel (windows). Under devices and printers, it is listed as Android 1.0 under unspecified devices.
Click to expand...
Click to collapse
which twrp version do you have installed?

little123 said:
which twrp version do you have installed?
Click to expand...
Click to collapse
Thanks dude. I had an older version, since I originally rooted this phone around 18 months ago and used a version from back then. I watched a youtube video how to push TWRP onto a soft bricked device using ADB. After that, I was able to install the ROM.

Budee80 said:
Thanks dude. I had an older version, since I originally rooted this phone around 18 months ago and used a version from back then. I watched a youtube video how to push TWRP onto a soft bricked device using ADB. After that, I was able to install the ROM.
Click to expand...
Click to collapse
glad i could help with just a question

Soft-Bricked Moto G (2014) won't move beyond Fastboot

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.

Bootloop, can get to "firmware update screen", fastboot commands not working

Bootloop, can get to "firmware update screen", fastboot commands not working
Out of nowhere my phone rebooted and started bootlooping. Eventually it came on but within minutes it did it again. After about an hour of pulling the battery abd trying to boot it, it finally came on. I went to use some app (I cant remember the title) to boot into twrp but it froze and started to bootloop again. I had never granted SU permissions to the app and it hadnt come up. Now that i have my computer I was able to boot into download mode (Firmware update screen) but my fastboot boot twrp.img command is stuck on waiting for device. Im guessing a malicious app caused the bootloop as i granted some app SU permissions only to later realize that it never needed it. All it did was download apk files for pentesting and diagnosis apps. It may be one of those apps however. I was on a custom ROM with an unlocked bootloader and twrp (although i cant seem to boot to it). LG Bridge couldnt find the device. Any help would be appreciated as this is my only device and I'm waiting for a call back for a speeding ticket and don't want to be screwed over :crying:

Since you have twrp and unlocked bootloader you should be able to access twrp still. This happened to me but from wiping internal storage by accident. Make sure you have your custom rom of choice on your sd card or the one you were running. Power off your G4 completely and while its off enter recovery mode manually. You may need to do this a few times for your G4 to enter recovery but it will boot to twrp. I believe its hold power button and volume down button then release for a sec both buttons when you see the lg logo then continue to hold them again. Do the factory reset option and after that it will boot to twrp and flash your rom again. Hope this works.
Sent from my LG-H811 using Tapatalk

srod562 said:
Since you have twrp and unlocked bootloader you should be able to access twrp still. This happened to me but from wiping internal storage by accident. Make sure you have your custom rom of choice on your sd card or the one you were running. Power off your G4 completely and while its off enter recovery mode manually. You may need to do this a few times for your G4 to enter recovery but it will boot to twrp. I believe its hold power button and volume down button then release for a sec both buttons when you see the lg logo then continue to hold them again. Do the factory reset option and after that it will boot to twrp and flash your rom again. Hope this works.
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
I tried that and it doesnt take me to twrp or the factory reset screen

Did you try it a few times? I had to do it like 5 times before I got the factory reset option. Maybe you have the dreaded hardware failure bootloop.
Sent from my LG-H811 using Tapatalk

Happened to me. Every time I would use the hardware keys to get into TWRP it would go back to the bootloop. Most likely is hardware issue like he said ^^ I contacted LG and they told me to send it. It's on its way back to me
Sent from my LG-H830 using XDA-Developers mobile app

My phone started bootlooping on Saturday so i called T-mobile and i just received my replacement phone today. Now im afraid that they're going to find out that my phone was rooted because when u turn the phone on it says bootloader unlocked and if they even get into recovery mode it will have twrp installed
Sent from my LG-H811 using XDA-Developers mobile app

Please help me to unbrick my G5S Plus

Hi guys,
I got a G5S+, which got stuck the other day.
It was booting, showing the blue Motorola screen but ended up with a lying down android with a red questionmark and saying 'no command'.
I read through a couple of threads and finally decided, I need to flash stock again.
I did not have switched on USB debugging and so on, as the phone was quite new to me.
I decided to run with that tutorial here:
https://forum.xda-developers.com/g5-plus/how-to/solution-to-flash-stock-romfactory-t3691396
Which seemed to be the right one.
Said so, booted into bootloader, installed the driver on my Win10 PC and ran through the steps.
I gut stuck on 'fastboot flash system system.img_sparsechunk.3' (15mins waiting..... after the steps before required about 12 Sec each) and needed to disconnect and connect the phone again.
Started with the same command and it worked.
Anyway when I got to the command 'fastboot flash system system.img_sparsechunk.5' I realized in the Potter Retail, there is no such file (neither there is 6 or 7).
I skipped the commands and continued.
When it came to rebooting the phone disconnected and thats it.
Since then I am not able to turn my phone back on.
Sometimes there seems to be a small notofication led showing up when trying to turn on the phone.
And you can hear the USB connect sound when I connect it to my computer.
Did anyone of you guys experience the same issue or has an idea what to do?
I have no idea what I shall so.
Best regards,
Matt

Which stock ROM did you flash? I'm hoping that following that guide, you flashed a stock ROM for sanders (i.e. the codename for Moto G5S Plus) and not for potter (codename for G5 Plus), which appear to be not compatible with each other.
Your original issue appears to be your device is booting into the stock recovery (which the start of is the 'no recovery' screen).
Do you know what model number or retail software channel, or the software build you had on your device before it failed? If so, we may be able to flash the correct sanders stock ROM to your device and get it going again. Another user appears to have gotten their device working when they incorrectly flashed the potter stock ROM and not sanders. https://forum.xda-developers.com/moto-g5s-plus/help/bricked-moto-g5s-plus-t3747064 Ideally you will want to flash the correct stock ROM for your device.

Oha damn you are right.
I am an idiot and tried to flash Potter to a G5S Plus.
Oh boy. I should not flash a cellphone after a long day at work.
I had the latest safety update installed and the latest release.
I am not sure though which software that used to be.
Unbelievable.....
Anyway, so my screen does not show anything anymore.
I guess the display driver dows not work or something like that.
The cellphone is still working I think, as the USB sound still appears.
Does anyone have an idea what to do if the screen stays black.
I still cannot believe it.....
Thanks though for your help!
EDIT: fastboot still reckognizes the phone. I guess this is good.
But the command 'fastboot oem fb_mode_set' runs into an error.
Edit2:
I skipped the first command and everything ran through (with some error messages though).
I hope it works now.
Device is currently rebooting and showing the blue motorola screen.
Lucky me.....

Okay, at least your device is booting now (ish)... I saw your other post and was wondering if you were able to boot from the bootloader.
1)Boot to fastboot (probably easiest by powering off your device, then hold down power and volume down keys until your device boots).
2)Once in the fastboot menu (with details about your device, like bootloader version), check that 'Start' is selected, and press the Power button to select. If 'Start' is not showing, use the volume keys to scroll through the options until 'Start' appears. Sometimes, this booting via fastboot bypasses an auto-boot to recovery mode.
Failing that, if you're on the 'no command' screen, then hold down the power button and tap the volume up key. Release both and it should let you into the recovery menu. Then, you can try to reboot to system.

Hi there,
I ran through all the steps you said.
But I ended up having the same issue. I always get back to the broken droid.
Is there a way to flash a completely new ROM to the device in its current condition?
I don't mind having a customrom, but I want to get it working again.
Thanks!
Matt

I solved my problem:
It was the SD card. I cannot believe it.
I got myself another G5S Plus and swapped everything:
Same issue.
So I removed the memory card and all good again.
I am quite sad though not having figured that out earlier, becoz all my data is lost now....
Thanks for your help though!