Database Users

Failed Root -- Bricked Bootloop SM-G930A

I'm completely at a loss at this point.
I attempted to root my Samsung S7 (AT&T) with Odin, and received an error. This is my first time ever rooting a phone, and I am generally oblivious to this kind of stuff. I disconnected the phone, and it began bootloop. I loaded it into download mode, and attempted to reset to stock. However, I have had endless issues trying to flash the stock firmware to my phone. At one point I unplugged the device once again, and I received the "use Emergency Restore" error screen. I tried to restore with Smart Switch, but I was not able to access my S/N (box is nowhere to be found, managed to find a S/N on Samsung's website since I registered it but Smart Switch wouldn't take it). So, I figured trying to restore with Odin was my last option. I have tried at least 3 different Odin versions, both modified and not, and not a single one of them has worked. I've received Complete(write) errors, Model Dispatch Fail errors, and Re-Partition errors. I've tried about 3 different firmware files as well, and while I think the one I have right now is most recent, none of them seem to be working. I thought maybe an issue I was encountering was that USB debugging or whatever it's called was disabled, but I have no way of telling because I cannot boot my phone.
I was fiddling around with all of this from 11pm to 6am last night, and picked it back up as soon as I woke up. I've been freaking out about this for hours.
I feel like I'm running in circles here. I don't understand what I'm doing wrong. I'm recovery bootlooped as well. The only thing I can boot is download mode.
I wasn't very cautious with this process, and I am completely unfamiliar with most lingo on these forums and the whole process in general. I really regret trying to do this. So -- is there anything else I can try to do to fix it? Or is my phone bricked for good??? I'm endlessly frustrated and have honestly felt like crying a few times over this. I shouldn't have messed with something I know nothing about. :crying:
I thank you for your patience in dealing with me as a beginner + appreciate any help you're able to give.
Cheers.

aerialslam said:
I'm completely at a loss at this point.
I attempted to root my Samsung S7 (AT&T) with Odin, and received an error. This is my first time ever rooting a phone, and I am generally oblivious to this kind of stuff. I disconnected the phone, and it began bootloop. I loaded it into download mode, and attempted to reset to stock. However, I have had endless issues trying to flash the stock firmware to my phone. At one point I unplugged the device once again, and I received the "use Emergency Restore" error screen. I tried to restore with Smart Switch, but I was not able to access my S/N (box is nowhere to be found, managed to find a S/N on Samsung's website since I registered it but Smart Switch wouldn't take it). So, I figured trying to restore with Odin was my last option. I have tried at least 3 different Odin versions, both modified and not, and not a single one of them has worked. I've received Complete(write) errors, Model Dispatch Fail errors, and Re-Partition errors. I've tried about 3 different firmware files as well, and while I think the one I have right now is most recent, none of them seem to be working. I thought maybe an issue I was encountering was that USB debugging or whatever it's called was disabled, but I have no way of telling because I cannot boot my phone.
I was fiddling around with all of this from 11pm to 6am last night, and picked it back up as soon as I woke up. I've been freaking out about this for hours.
I feel like I'm running in circles here. I don't understand what I'm doing wrong. I'm recovery bootlooped as well. The only thing I can boot is download mode.
I wasn't very cautious with this process, and I am completely unfamiliar with most lingo on these forums and the whole process in general. I really regret trying to do this. So -- is there anything else I can try to do to fix it? Or is my phone bricked for good??? I'm endlessly frustrated and have honestly felt like crying a few times over this. I shouldn't have messed with something I know nothing about. :crying:
I thank you for your patience in dealing with me as a beginner + appreciate any help you're able to give.
Cheers.
Click to expand...
Click to collapse
If you can at least get into download mode, then simply flash it with the latest STOCK firmware for your particular model.
That will bring it back to life, and you can attempt rooting it again, if you dare

aerialslam said:
I'm completely at a loss at this point.
I attempted to root my Samsung S7 (AT&T) with Odin, and received an error. This is my first time ever rooting a phone, and I am generally oblivious to this kind of stuff. I disconnected the phone, and it began bootloop. I loaded it into download mode, and attempted to reset to stock. However, I have had endless issues trying to flash the stock firmware to my phone. At one point I unplugged the device once again, and I received the "use Emergency Restore" error screen. I tried to restore with Smart Switch, but I was not able to access my S/N (box is nowhere to be found, managed to find a S/N on Samsung's website since I registered it but Smart Switch wouldn't take it). So, I figured trying to restore with Odin was my last option. I have tried at least 3 different Odin versions, both modified and not, and not a single one of them has worked. I've received Complete(write) errors, Model Dispatch Fail errors, and Re-Partition errors. I've tried about 3 different firmware files as well, and while I think the one I have right now is most recent, none of them seem to be working. I thought maybe an issue I was encountering was that USB debugging or whatever it's called was disabled, but I have no way of telling because I cannot boot my phone.
I was fiddling around with all of this from 11pm to 6am last night, and picked it back up as soon as I woke up. I've been freaking out about this for hours.
I feel like I'm running in circles here. I don't understand what I'm doing wrong. I'm recovery bootlooped as well. The only thing I can boot is download mode.
I wasn't very cautious with this process, and I am completely unfamiliar with most lingo on these forums and the whole process in general. I really regret trying to do this. So -- is there anything else I can try to do to fix it? Or is my phone bricked for good??? I'm endlessly frustrated and have honestly felt like crying a few times over this. I shouldn't have messed with something I know nothing about. :crying:
I thank you for your patience in dealing with me as a beginner + appreciate any help you're able to give.
Cheers.
Click to expand...
Click to collapse
Did you finally recover your phone? I'm in the same problem here since yesterday and feel your frustration right now. My phone is a Samsung S7 model SM-G930A from AT&T.
I found this thread https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039 and I following the "Return to stock part", now downloading the firmware. Hope it helps.
I'm stucked in the blue screen "An error ocurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software". Of course I try the Smart Switch but says that my model is not supported!
How can you recovered the download mode? I press the on/off button for some seconds and the screen turn of, but it turn on again with the freaking blue screen "An error ocurred while updating the device software. ...". I tried all the possible button combinations.
Thanks and good luck.

Stock firmware
Make sure when you go into download mode and flash that plugging the phone in is the LAST thing you do. I.e. plug phone in only after it is in download mode and only after you open Odin. Secondly, make sure you flash the STOCK firmware, as in Android Marshmallow v6.0.1 . Additonally, make sure that the re-partition option is NOT ticked, and also you might want to try turning off auto-reboot, and just hold the power button after unplugging once the status bar is all the way full and Odin says complete. Also, you need to make absolutely sure that you're getting the firmware for your exact device. I.e. SM-G930A stock firmware is NOT compatible with SM-G930F models. You could also try reinstalling the Samsung drivers. I just flashed to stock firmware then updated back to Nougat yesterday, mostly without a hitch by following these guidelines. There is a download page on rootmygalaxy with all the stock firmwares, that's what I used (I'd link but I just registered here). There is a very helpful guide on droidviews about how to update to Nougat 7.0 once you have finished flashing the stock firmware.
If I were you, I would just avoid rooting altogether. Rooting for me caused very bad performance and battery life, and it wasn't really worth the trouble. Sure, getting in-app-purchases for free was nice but I never tried flashing a custom ROM or anything because most of the stories I read involved soft bricks, bootloops, etc.
Hopefully not having USB Debugging and OEM unlock ticked doesn't brick your phone, I'm doubtful that it will. For the poster above me, make sure your phone is all the way off, the download mode button combo is vol. down+power+home all at the same time, and hold them. A screen should pop up saying press vol. up to continue. If you're still having problems, I regret to say that I am also relatively new to this and I am not all that knowledgeable.
I just made a post about my unrooting process, hopefully it helps!

https://www.youtube.com/watch?v=o6ryOQepX2Q Video shows booting into Download Mode. Or take it to a Best Buy that has a Samsung Sales section.

DANGEROUS UPDATE : C432B185; do not apply

Hello,
I just applied the latest update C432B185 on a 8 pro honor; it remains blocked at restart. Another user reports an identical problem on the FRANDROID site.
Do not apply this update because the problem is blocking; you will no longer be able to use your honor 8 pro.
Solution on hold.
Thank you

I have the exact same problem. I started the update, and put it back in my pocket. I grabbed my phone after a few minutes and blindly touched the fingerprint sensor and pressed where normally the home button is. Instead, I catched a glimpse of a black screen, a triangle and a button. The button was at almost the same spot as where the home button normally is, so I clicked it and my phone restarted. After that, the only thing my phone does right now is show the white Honor logo with a lightblue blackground.
I already tried everything that can be done, I think.
Restarted the phone 20 times, did a 'user reset', cleared the cache 20 times and did a lot of factory resets (sometimes stuck at 99%).
Nothing made my phone work again. I also tried to use eRecovery to 'Download latest version and recovery' but that only resulted in 'Getting package info failed'.
If someone has any clue to what can be done to revive the Honor 8 Pro again (or to see some kind of logs to view what's going on), please... help! :crying:
The topic on Frandroid that Pascal was talking about: forum.frandroid.com/topic/261525-mise-%C3%A0-jour-qui-plante-le-smartphone

Hello,
I have exactly the same problem with my honor 8 pro.
I can't use it anymore, the user reset is staying 99%
If someone has a solution...

Also had the update, tried everything, wanted to flash other rom but i haven't got my product ID to unlock the bootloader.
Worst part of all, there is no care centre in The Netherlands...
so what im suppose to do? not sure at all, eRecovery fails,
using the dload method fails.
nothing seem to work atm...

Thank you for sharing this. It's not released in India yet seems but disabled the auto download update over wifi feature just in case.

Also, I can't connect to the phone with ADB or fastboot. /adb reboot recovery returns error: device unauthorized. This adb server's $ADB_VENDOR_KEYS is not set and ./fastboot getvar all returns FAILED (remote: Command not allowed). HiSuite (never tried before) can't find my phone on OSX and crashes after 5 minutes.
No root, no unlocked bootloader. Also shows FRP is locked.

Same here (france) Factory reset doesn't work, dload method doesn't either and the WIFI update doesn't find anything so I'm stuck with no phone for the moment :'(

Same here (Poland). Phone is bricked, second visit in service within 2 months :/

Oh ,god, i was about to let people know that a new update b185 had just come up until i see this post...I immediatly stopped the downloading process of this Update, so bad news for the ones who already applied the update and who got stuck now...
There might be an ultimate solution for bricked phone by using the DC Phoenix unlock software method...

Same Problem with the Honor 8Pro update
Hi,
Same problem in the Netherlands, Brabant.
Just downloaded the update for the Honor 8Pro.
Tried everything, also the eRecovery, Same problem with the package Failure.
Also E-mailed to HiHonor for an sollution, nothing so far.
Somebody got any tip? Can miss my phone for work..
Greeting from Oss, The Netherlands.

Same problem
Same problem here in The Netherlands. Literally nothing works. Never even rooted this device or anything like that. Also, what is this "download and recovery" in eRecovery even for if nothing downloads? I am very disappointed in this. Have no idea what I should be doing while normally I find a way to work around such problems.

TheVeeeMan said:
Same problem here in The Netherlands. Literally nothing works. Never even rooted this device or anything like that. Also, what is this "download and recovery" in eRecovery even for if nothing downloads? I am very disappointed in this. Have no idea what I should be doing while normally I find a way to work around such problems.
Click to expand...
Click to collapse
Zelfde probleem hier en nu een onbruikbare telefoon...
Nog geen half jaar oud!
Ik heb net Honor gemaild .. even afwachten tot morgen..
Sterkte alvast!

Thank you for the warning!

flash a stock rom by -=MoRpH=-.
these are factory firmwares and reset your device back to full stock, yes, even with locked bootloader!
Regards

OldDroid said:
flash a stock rom by -=MoRpH=-.
these are factory firmwares and reset your device back to full stock, yes, even with locked bootloader!
Regards
Click to expand...
Click to collapse
I have explicitly chosen to not root or otherwise mod my phone just yet. Does this void your warranty? Right now, I can send it back to the supplier and they will fix it. Of course if something else is faster (supplier says max. 3 weeks) then I am happy to try, if it does not void my warranty.
EDIT: and also, how can I see which version I need? I don't know how for sure which version I have, and of course I can't get into the UI anymore. As I posted before, ADB and Fastboot don't give me any info.

OldDroid said:
flash a stock rom by -=MoRpH=-.
these are factory firmwares and reset your device back to full stock, yes, even with locked bootloader!
Regards
Click to expand...
Click to collapse
Hello,
that didn't work.
:crying:

Krystal666 said:
Oh ,god, i was about to let people know that a new update b185 had just come up until i see this post...I immediatly stopped the downloading process of this Update, so bad news for the ones who already applied the update and who got stuck now...
There might be an ultimate solution for bricked phone by using the DC Phoenix unlock software method...
Click to expand...
Click to collapse
Thank you.
I have made use of many Huawei phones in recent years (Mate 7, Mate 9, P8 Lite, P9 Lite) and Honor 8 Pro. I quickly realized that this update was blocking; it was common sense to inform users of the Honor 8 Pro in order to limit the number of service returns, unnecessary time wastage, etc.
This is our precious ...
Welcome

Here in Holland this morning the same problem.

Thanks for the Info. No update notice for my phone (in Germany). Hopefully Huawei/Honor will have stopped the update rolling out. Jeez, don't these updates get tested before they're released?

You can use Firmware Finder for PC to send an update for installation via erecovery with changing your routers DNS.
Erecovery is used in customer services to install manually sent updates only. That's why it can't find anything without sending an update to your device.

Axon 7: No connectivity after upgrade to 7.1.1

Hi
I have Axon 7 A2017G. Bought from AliExpess in Feb of this year. It has been a very good phone so far with no issues. Well, at least until yesterday.
I was on Android 6 until yesterday when I found out that I can upgrade to Android 7.1.1. So, I stupidly upgraded to 7.1.1 (getting the upgrade from from ZTE) and now I have *lost my connectivity* (I am using three.co.uk sim). It doesn't recognise my sim card at all.
I have tried deleting and wiping the cache - no joy. Not sure what else to do.
I tried to use other upgrade from ZTE (Nougat to Marshmallow) and Marshmallow. Both fail with 'e footer is wrong e signature verification failed installation aborted'.
Everything else seems to be fine and I have had no issues with Axon 7 (had it since Feb) before the upgrade.
Hope someone can either help to get the connectivity back or somehow degrade my Android back to 6 (when it was all working fine).
Thanks Robie

SlickRobie said:
Hi
I have Axon 7 A2017G. Bought from AliExpess in Feb of this year. It has been a very good phone so far with no issues. Well, at least until yesterday.
I was on Android 6 until yesterday when I found out that I can upgrade to Android 7.1.1. So, I stupidly upgraded to 7.1.1 (getting the upgrade from from ZTE) and now I have *lost my connectivity* (I am using three.co.uk sim). It doesn't recognise my sim card at all.
I have tried deleting and wiping the cache - no joy. Not sure what else to do.
I tried to use other upgrade from ZTE (Nougat to Marshmallow) and Marshmallow. Both fail with 'e footer is wrong e signature verification failed installation aborted'.
Everything else seems to be fine and I have had no issues with Axon 7 (had it since Feb) before the upgrade.
Hope someone can either help to get the connectivity back or somehow degrade my Android back to 6 (when it was all working fine).
Thanks Robie
Click to expand...
Click to collapse
The problem is probably that you do not have an A2017G. Turn your phone around and tell me what the model erched into the back of the phone is. I suspect that you have an A2017, you didn't read the little paper that came with the phone that explained what they (the aliexpress seller) did with it, and you flashed an A2017G ROM on your A2017, effectively messing up the modem file.
I don't know if flashing through EDL fixes the issue, but it might be worth trying. It involves downloading a FULL_EDL package (the full system for your device model), then flashing it entirely through EDL.
The failproof method is to unlock the bootloader, flash TWRP, then flash the modem file corresponding to your device.

Choose an username... said:
The problem is probably that you do not have an A2017G. Turn your phone around and tell me what the model erched into the back of the phone is. I suspect that you have an A2017, you didn't read the little paper that came with the phone that explained what they (the aliexpress seller) did with it, and you flashed an A2017G ROM on your A2017, effectively messing up the modem file.
I don't know if flashing through EDL fixes the issue, but it might be worth trying. It involves downloading a FULL_EDL package (the full system for your device model), then flashing it entirely through EDL.
The failproof method is to unlock the bootloader, flash TWRP, then flash the modem file corresponding to your device.
Click to expand...
Click to collapse
Doh! Doh! Doh! :crying:
You are ABSOLUTELY correct. I didn't read that little paper that came with it because it was all Chinese - not English. Damn - why didn't I check. :crying:
When I bought it, the website said it was a 2017G model and therefore I assumed it was 2017G model.
Anyway, I don't understand some of the things you wrote (I am okay with upgrade and such like but not so much programming lark). What is this FULL_EDL package and how straight forward would it be for me to use it? Where do I get hold of it?
Everything is fine except phone call, sms and data of course. Internet connection is fine and all the apps works too.
Another question, would it help if I did a full factory reset and then applied the correct upgrade? I have backup of all my apps, contacts, pictures, music, etc.
Thanks
Robie

SlickRobie said:
Doh! Doh! Doh! :crying:
You are ABSOLUTELY correct. I didn't read that little paper that came with it because it was all Chinese - not English. Damn - why didn't I check. :crying:
When I bought it, the website said it was a 2017G model and therefore I assumed it was 2017G model.
Anyway, I don't understand some of the things you wrote (I am okay with upgrade and such like but not so much programming lark). What is this FULL_EDL package and how straight forward would it be for me to use it? Where do I get hold of it?
Everything is fine except phone call, sms and data of course. Internet connection is fine and all the apps works too.
Another question, would it help if I did a full factory reset and then applied the correct upgrade? I have backup of all my apps, contacts, pictures, music, etc.
Thanks
Robie
Click to expand...
Click to collapse
Not at all, this is much more messed up. A factory reset only wipes data, you need to fix a part of the system. If you are okay with unlocking your phone (i think you don't have warranty anyways) then you should do that, there are guides but be sure that they are FOR THE A2017!
After unlocking you need to install TWRP, those guides usually also explain you how to do this. Then you download this file and flash it through TWRP (put it in the phone, go to TWRP, Install - select the zip - swipe to start)

It may help understanding to know that there are 3 models.
A2017 is the Chinese one, A2017U is the American one and A2017G is multinational/European. There are different telephony frequency bands in use around the world and the Chinese one also has different storage and memory. A bit bummed they held that back from the rest of the world.....

Choose an username... said:
Not at all, this is much more messed up. A factory reset only wipes data, you need to fix a part of the system. If you are okay with unlocking your phone (i think you don't have warranty anyways) then you should do that, there are guides but be sure that they are FOR THE A2017!
After unlocking you need to install TWRP, those guides usually also explain you how to do this. Then you download [https:// androidfilehost.com/?fid=457095661767137840]this file and flash it through TWRP (put it in the phone, go to TWRP, Install - select the zip - swipe to start)
Click to expand...
Click to collapse
Thank you for quick response.
Yes, you are correct, warranty is non-issue anyway and I will make sure it is for A2017 (not A2017G/U). Wish I had just checked the back of the phone then I would not have ended up here but it is nice to learn new things, however painful..
Thanks for the heads up on the process as well. There goes my weekend but the boss (wife) is away so it is okay.
I will report if I manage to get it working next week. Wish me luck.
Robie

Update.
I spent the weekend on this and sadly didn't get anywhere. I followed the instructions and download from here:
http://https://forum.xda-developers.com/axon-7/how-to/guide-b13-chinese-a2017-root-unlock-t3549873.
Unfortunately, no joy. I can get my phone in EDL mode (drivers downloaded & suetup successfully, COM port is correct, etc) but the following commands just sit forever. They don't respond at all.
axon7backup.exe -p COM# -d
axon7root.exe -p COM# -r
Not sure where to go from here. If anyone has any ideas then please let me know.
Thanks.
Robie

Newbie Help with an Unrooted, Unmodified Phone Stuck in Fastboot Mode After Update

I'm not really looking to do anything unofficial or invalidating or ultra-complicated to my phone. I've been looking everywhere for help, and I'm having a lot of difficulty, so I'm really hoping there might be someone here who can help me. My phone is a Moto X Style, and last night I tried to update it (I can't remember what the update was called, but I had been trying to avoid it like the plague because anytime I update ANY KIND OF THING WHATSOEVER something ends up going wrong. I got tired of getting the little pop-up reminding me to update my phone, so I finally decided to install it). I had connected it to the charger to make sure it would stay charged during the update since updates can take a while. But when I checked my phone next, it had gone into fast-boot mode with this message:
Start Up Failed:
Your device didn't start up successfully. Use the Software Repair Assistant on computer to repair your device.
Connect your device to your computer to get the Software Repair Assistant.
Turning it off and on again just results in the same thing. I thought maybe if I tried to do a reset to factory settings maybe it would work again. But unfortunately, I can't seem to access recovery mode, either. When I try to access recovery mode, the phone restarts and still gives me the start-up failed message in bootloader logs as well as a couple of messages in a purplish-pink that's all:
Version downgraded for recovery
Failed to validate recovery image
ERROR: Failed to pass validation, backup to fastboot
Fastboot Reason: Fall-through from recovery boot mode
I tried talking to Motorola Technical Support on their website via Online Chat. They were effectively useless, and at one point recommended I take the phone to a Service Repair Center...
In India. (I live in the United States, and I work as a cashier in retail. I can't afford a trip to India - might as well buy a new phone at that point. Of course, I can't really afford to buy a new phone right now, either).
I've tried doing some research on my own. The only Software Repair Assistant that seems to be available is the one from Verizon Wireless. I tried to get that to work but no dice. No surprise there, I guess, since I'm not actually with Verizon Wireless (I'm on a Republic Wireless phone plan cause cheap). I read that sometimes Republic Wireless can interfere with things update-wise and cause something like this to happen? But I couldn't find anything about how to fix it.
I have no idea how much it would cost if I tried to take it to some kinda other non-official repair service somewhere, and I want to try and avoid that option if I can. Please if you have any suggestions that won't result in my phone ending up in worse condition, I could really use the help. I'm so upset and frustrated by this issue. I knew updating my phone would suck, but I didn't think this would happen!

Gigglypuff said:
I'm not really looking to do anything unofficial or invalidating or ultra-complicated to my phone. I've been looking everywhere for help, and I'm having a lot of difficulty, so I'm really hoping there might be someone here who can help me. My phone is a Moto X Style, and last night I tried to update it (I can't remember what the update was called, but I had been trying to avoid it like the plague because anytime I update ANY KIND OF THING WHATSOEVER something ends up going wrong. I got tired of getting the little pop-up reminding me to update my phone, so I finally decided to install it). I had connected it to the charger to make sure it would stay charged during the update since updates can take a while. But when I checked my phone next, it had gone into fast-boot mode with this message:
Start Up Failed:
Your device didn't start up successfully. Use the Software Repair Assistant on computer to repair your device.
Connect your device to your computer to get the Software Repair Assistant.
Turning it off and on again just results in the same thing. I thought maybe if I tried to do a reset to factory settings maybe it would work again. But unfortunately, I can't seem to access recovery mode, either. When I try to access recovery mode, the phone restarts and still gives me the start-up failed message in bootloader logs as well as a couple of messages in a purplish-pink that's all:
Version downgraded for recovery
Failed to validate recovery image
ERROR: Failed to pass validation, backup to fastboot
Fastboot Reason: Fall-through from recovery boot mode
I tried talking to Motorola Technical Support on their website via Online Chat. They were effectively useless, and at one point recommended I take the phone to a Service Repair Center...
In India. (I live in the United States, and I work as a cashier in retail. I can't afford a trip to India - might as well buy a new phone at that point. Of course, I can't really afford to buy a new phone right now, either).
I've tried doing some research on my own. The only Software Repair Assistant that seems to be available is the one from Verizon Wireless. I tried to get that to work but no dice. No surprise there, I guess, since I'm not actually with Verizon Wireless (I'm on a Republic Wireless phone plan cause cheap). I read that sometimes Republic Wireless can interfere with things update-wise and cause something like this to happen? But I couldn't find anything about how to fix it.
I have no idea how much it would cost if I tried to take it to some kinda other non-official repair service somewhere, and I want to try and avoid that option if I can. Please if you have any suggestions that won't result in my phone ending up in worse condition, I could really use the help. I'm so upset and frustrated by this issue. I knew updating my phone would suck, but I didn't think this would happen!
Click to expand...
Click to collapse
When it is telling you to get the software repair assistant, are you putting your phone into your computer with the message displayed? Just want to make sure it doesn't automate a repair for you.
Do you have an unlocked bootloader, rooted, etc.?
Gotta ask to know where to possibly start.

aybarrap1 said:
When it is telling you to get the software repair assistant, are you putting your phone into your computer with the message displayed? Just want to make sure it doesn't automate a repair for you.
Do you have an unlocked bootloader, rooted, etc.?
Gotta ask to know where to possibly start.
Click to expand...
Click to collapse
I've tried plugging it into the computer, but nothing happens. I've tried downloading the Verizon Wireless Software Repair Assistant, but it just gets stuck on Processing... and nothing happens.
I haven't done anything to the phone. No rooting or anything like that. Dunno if this is relevant, but -
Console (NULL): null
Tools Mode Config: DISABLED
Battery OK
Device is LOCKED. Status Code: 0
Software status: Official

Gigglypuff said:
I've tried plugging it into the computer, but nothing happens. I've tried downloading the Verizon Wireless Software Repair Assistant, but it just gets stuck on Processing... and nothing happens.
I haven't done anything to the phone. No rooting or anything like that. Dunno if this is relevant, but -
Console (NULL): null
Tools Mode Config: DISABLED
Battery OK
Device is LOCKED. Status Code: 0
Software status: Official
Click to expand...
Click to collapse
Do you have any idea what version of Android you were running (MM, N)? What specific model do you have (XT1572, XT1570, XT1575)

I'm really not sure what version I was running. The model is XT1575, though.

XT1575 is not enough to determine the exact error. Is your phone Verizon wireless locked SIM or all SIM type? If it is in first case, so hard to fix it. Bring it to Verizon.
If phone works with any SIM (2nd case), you can try to reflash your recovery via adb (google it). If it doesnt work, you may have to unlock your bootloader (warranty ended), flash the newest firmware corresponds to XT1575. If all is done without error, your phone may start again like a brand new. You have to set up everything again.
Do it with your own risk.

Updated to Android 10. Now I get zero service.

Hello
I just upgraded my Essential to Android 10 and now I don't have ANY service so I want to downgrade. Yes I have done a factory reset, reset the network settings, and reinserted the sim, etc. I'm familiar enough with it, but it's been giving me issues when I try to flash anything. It'll just wait... and wait... and wait... nothing will happen. Or I'll get a messaging saying A/B device support is outdated and to update my bootloader. It will also say that target didn't report max download size. I've used different ports and different cords, I use the most recent platform tools, drivers are installed, bootloader is unlocked, but I'm stuck. Any suggestions? Fastboot and ADB devices will register just fine, but that's it.

Sounds like you should start by checking the APN my bet is it's blank.

subcomponent said:
Hello
I just upgraded my Essential to Android 10 and now I don't have ANY service so I want to downgrade. Yes I have done a factory reset, reset the network settings, and reinserted the sim, etc. I'm familiar enough with it, but it's been giving me issues when I try to flash anything. It'll just wait... and wait... and wait... nothing will happen. Or I'll get a messaging saying A/B device support is outdated and to update my bootloader. It will also say that target didn't report max download size. I've used different ports and different cords, I use the most recent platform tools, drivers are installed, bootloader is unlocked, but I'm stuck. Any suggestions? Fastboot and ADB devices will register just fine, but that's it.
Click to expand...
Click to collapse
Want help? Right now?

Try to fastboot install a really old stock Nougat image