unbricking hard brick - moto x style - X Style (Pure) Q&A, Help & Troubleshooting

hey guys
i just brick my phone (no idea how, flashed android 7 firmware) after flash my phone was working for like 2 hours, then i let himself update a security options. After update my phone went brick
As far i found :
- installed Qualcoom QDLOADER 9008 driver
- found QFIL programmer
i need to have programmer path (something related to JTAG) and build xmp path
Where i can find them? Or is it a other way to resscue my phone?

I feel your pain. My timeline:
- The phone was unlocked but still in Stock Nougat (7.0?). Got that from OTA in Brazil.
- I tried to update to LineageOS 7 via TWRP. After a full wipe (everything, system, data, card, cache etc) I installed the new ROM. Turned on, bootlooped forever.
- Searching around I found out that there was no modem in the Nougat roms and for some reason I needed to flash a Marshmallow modem for my region to make that work (I think there is no Nougat modems around or something).
- I found a LA_DS modem for 6.0, flashed that using TWRP, still bootloop. Tried other roms using TWRP, still bootloop.
- I then downloaded a full stock old 6.0 firmware to go back to stock but the phone wouldn't accept some files ("preflash validation failed").
- Searched around and found out that you can't downgrade a bootloader from Moto.
- Using fastboot, I flashed the files the phone was willing to accept and it finally booted the 6.0 Marshmallow stock rom, but with no networking (radio/modem/baseband/IMEI missing).
- Flashed the 6.0 modem for my region again and everything worked. Connected on WiFi, dual sim cards detected etc.
- I started to install every update the phone showed to try to update it back to latest MM version.
- The three first updates went ok, the fourth turned off the phone to never turn on again.
Looks like there is no way out of this. My phone is pretty old and MotoCare in Brazil will charge a lung and a half for repair.

dsnunes said:
I feel your pain. My timeline:
- The phone was unlocked but still in Stock Nougat (7.0?). Got that from OTA in Brazil.
- I tried to update to LineageOS 7 via TWRP. After a full wipe (everything, system, data, card, cache etc) I installed the new ROM. Turned on, bootlooped forever.
- Searching around I found out that there was no modem in the Nougat roms and for some reason I needed to flash a Marshmallow modem for my region to make that work (I think there is no Nougat modems around or something).
- I found a LA_DS modem for 6.0, flashed that using TWRP, still bootloop. Tried other roms using TWRP, still bootloop.
- I then downloaded a full stock old 6.0 firmware to go back to stock but the phone wouldn't accept some files ("preflash validation failed").
- Searched around and found out that you can't downgrade a bootloader from Moto.
- Using fastboot, I flashed the files the phone was willing to accept and it finally booted the 6.0 Marshmallow stock rom, but with no networking (radio/modem/baseband/IMEI missing).
- Flashed the 6.0 modem for my region again and everything worked. Connected on WiFi, dual sim cards detected etc.
- I started to install every update the phone showed to try to update it back to latest MM version.
- The three first updates went ok, the fourth turned off the phone to never turn on again.
Looks like there is no way out of this. My phone is pretty old and MotoCare in Brazil will charge a lung and a half for repair.
Click to expand...
Click to collapse
Pretty similar situation on my part. I downgraded back to 6.0 and when it tried to take the December update I ended up with the same thing as you. I ended up getting a replacement from Moto for under 100 dollars which was worth it rather than trying to find a solution that doesn't exist.

Related

[Q] Soft Bricked handset

Hello,
I've got (had) an SM-G900W8 running the XtreStoLite v2.0 LP BETA5 ROM on the XXU1BOA3 kernel. I installed TWRP 2.7 via Odin, and left the latest modem and bootloader updates I got through KIES3.
At which point I got the chance to sell the handset on Kijiji, provided I could get the stock ROM back on.
I downloaded the latest Odin (3.09) and the correct Firmware for my handset from sam mobile, and factory reset the device. I pulled the battery, let it sit, and tried to flash once I got it back up in download mode, and it wouldn't work.
This isn't too much of a surprise to me, because since I flashed TWRP, Odin hasn't ever worked for me. Regardless of how many times I've tried to flash the modem and/or BL that XtreStoLite asked me to use in their how to thread, it wouldn't work. I was willing to ignore it b/c the ROM worked with the modem and BL it was running.
My problem is that once I tried to reboot, the system hung at the BL animation. I went back into recovery, and tried to move my backups off my external storage (I had 2 back ups that were about 2 or 3 gigs each, too much for the local storage) to the local card and restore (b/c TWRP won't restore from the external card) and the back ups failed.
Now I've got the BL screen, but it won't advance to the animation, and it won't boot to TWRP either.
I tried to restore from KEIS, but it says my device isn't supported by KIES 3 (it is). I could really use a hand here. Every time I try something this gets worse. I'm no pro, but I've had no problem figuring this out on my old HTC handsets.

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

No Sim Detected

Hey all......I created a thread awhile back when I borked my phone trying out a new treble rom that was supposed to be so easy even a nOOb could flash it, and it ended up messing up my phone to the point where the only way for me to get it back was to follow the thread to disassemble the phone and short the chip out.
Then, the screen was not responsive on ANY rom I flash except for MM and it worked with any up to B29. I tried a few times to upgrade all in vain but I was always able to flash MM B29 and have it work again.
Flash forward to last night and my itchy trigger upgrade finger did it again and I attempted to flash the Oreo from ZTE. It flashed fine but, again, no responsive screen. I thought well, maybe I could try Nougat again and I flash many different versions and in different ways (used miFlash, EDL tool, MiFavor recovery, twrp) and all resulted in the screen not being responsive. Sigh, so I flashed MM B29 but now it will not detect any sim or even allow wifi to be turned on.
I have tried multiple times to reflash MM B29 using all the different ways above and even went back and forth between roms. I tried the original way most of us first unlocked the bootloader and flashed through all those stepped zip packages from B20 to B29 and still nothing. I finally used twrp to erase/format all data and made certain the partitions were formatted as ext4 and tried again, still no sim.
I realize that my imei is not showing and even tried a program to flash? that to the phone.
NOW, what needs to be said is during ALL of this flashing the phone signal/sim DID show......yes.......the sim DID WORK......when I flashed anything other than MM B29. LOL. Of course, the issue is none of those roms allow the screen to work.
Please, if anyone can help I would appreciate it very much. I'm thinking by flashing the Oreo from ZTE it may have changed something that the MM B29 rom is not changing to allow the phone to read the imei/sims.
I'm not sure but I think the DFU multitool posted by @raystef66 can fix the IMEI issue.
You have installed the correct modem for you device? EG: if you've flashed a U modem on a G device the sim and WiFi won't work.
If this is correct check APN and network setting in the phones software.
I hope this helps ?
Syberclone said:
I'm not sure but I think the DFU multitool posted by @raystef66 can fix the IMEI issue.
You have installed the correct modem for you device? EG: if you've flashed a U modem on a G device the sim and WiFi won't work.
If this is correct check APN and network setting in the phones software.
I hope this helps
Click to expand...
Click to collapse
I appreciate the suggestions. Unfortunately, the DFU tool doesn't seem to work for me as it remains listed as Disconnected even after choosing the correct port.
I have always flashed the MM B29 EDL rom (A2017U_B29_MARSHMALLOW_FULL_EDL) that contains the correct modem. As I said, it always worked before.
As far as checking APN/network settings, well, there are none to check because the sim is not detected so all of those choices are greyed out. The signal bars fr both sims are blank in the notification area and of course wifi does not turn on.
I just finished another round of trying different roms to flash including LOS 15. LOS came up to the welcome screen (just like all the others) AND the AT&T logo with LTE full signal bars showing. Again, the screen does not respond to touch so it's all useless. I am at a loss as to why flashing MM B29 is no longer working for me.
Stop using guides mentioned in Axon7 thread,or stop listening to other users.Only thing i see here are bricks.
Probably you have hardware fault
The Axon 7 has been the worst phone for being bricked.
I've flashed ROMs on HTC's, Motorola and Google phones all without problems.
There are way too many packages and bootstacks etc, etc that cause problems and confusion.
So I wouldn't say don't follow threads or users advice.
My advice is research, research and research some more.
Thanks for the suggestions.
Something to get clear.....
I can successfully flash the roms and get to the Welcome screen to begin setup.
MARSHMALLOW:
-screen does respond to touch
-sims are NOT detected
-no AT&T logo
-no phone signal
ANY OTHER VERSION (Nougat, Oreo):
-screen does NOT respond to touch
-sims are recognized
-AT&T logo appears
-phone signal strength meter shows full bars
So, it's not a hardware fault. The phone was working perfectly fine when I had Marshmallow flashed. It's only this last time I flashed the Oreo from ZTE's website and when that did not work I tried a few other roms and then went back to the Marshmallow B29 EDL that I had been using all along.
Isn't there a way to COMPLETELY wipe this phone and start from scratch? As in, when your Windows is so full of crap and running slow you can format the hard drive and reinstall Windows from scratch. I have tried TWRP and format data (have to type yes to format) etc........is there a way to format w=everything that might affect the sim from being detected in Marshmallow? Better yet, the screen from being responsive in other ROMS after marshmallow?
djprez said:
Thanks for the suggestions.
Something to get clear.....
I can successfully flash the roms and get to the Welcome screen to begin setup.
MARSHMALLOW:
-screen does respond to touch
-sims are NOT detected
-no AT&T logo
-no phone signal
ANY OTHER VERSION (Nougat, Oreo):
-screen does NOT respond to touch
-sims are recognized
-AT&T logo appears
-phone signal strength meter shows full bars
So, it's not a hardware fault. The phone was working perfectly fine when I had Marshmallow flashed. It's only this last time I flashed the Oreo from ZTE's website and when that did not work I tried a few other roms and then went back to the Marshmallow B29 EDL that I had been using all along.
Isn't there a way to COMPLETELY wipe this phone and start from scratch? As in, when your Windows is so full of crap and running slow you can format the hard drive and reinstall Windows from scratch. I have tried TWRP and format data (have to type yes to format) etc........is there a way to format w=everything that might affect the sim from being detected in Marshmallow? Better yet, the screen from being responsive in other ROMS after marshmallow?
Click to expand...
Click to collapse
Did you installed a vendor partition?
Predatorhaze said:
Did you installed a vendor partition?
Click to expand...
Click to collapse
I am not certain. If the Oreo update that I downloaded directly off the ZTE site has one, then yes. If that is the cause, how would I modify it?
@djprez: To my knowledge, ZTE's official B12/B20 do not have a vendor partition. ZTE will almost certainly never add Treble support for the A7, if they are going to do so then now is an ideal time, since the A7 is an end-of-life device and no longer being manufactured.

Axon 7 Mini Soft Brick cannot apply update from SD

I have only used stock roms on this phone. I originally upgraded my phone from a UK carphone warehouse rom 6.1 (B2017G UKV1.0.0B01)? I think?? That was a few years ago and upgraded to Nougat using the methods used in this forum.
I found that the wifi would sometimes disappear from the phone and you would have to reboot the phone to get wifi working again. That is ok but after about 3 times of having to do this over a period of a few months it would go again BUT then would then need a factory reset to get the wifi going again! After a year of doing three factory resets
i tried to revert to the older MM 6.1.
I used a ROM that i downloaded from here when i first done upgraded
anyhow i placed ROM in SD and proceeded with the downgrade it went fine up to 81% then got stuck then i restarted the phone again and it got stuck again, so i tried to flash from the SD in recovery mode instead and it says "sorry you can`t sdcard upgrade" so i then pressed reboot system and then it just hangs a the logo.!!
I have rooted phones in the past my last was an LGG2, and a brilliant tool was available so you could flash any stock rom back onto the phone if you had any trouble with custom or stock roms. but there does not seem to be any such tool from ZTE.
If you can help in any way?, i would be delighted!!
THANKS!!
(Soz if i posted in wrong area!)
I got the phone booted through EDL and EDL tool & backup files provided by this site. It took me a while to find all the info i needed.
Also renaming the files from boot to boot.img etc in the edl folder took a bit to work out as the tool kept telling me the files were insufficient!
All good now managed to downgrade to 6.1 UK ...Thanks XDA!!

Trouble flashing stock kdz

I have an H872 on Havoc 4.4. I have upgraded to a Pixel and will be giving the H872 to my father-in-law. He will only be using it for phone calls - very unlikely he will text, and definitely won't use data. It will also be his first smart phone. Since the H872 is rooted, when it boots up it gives the warning display that the phone may be "Corrupted". I don't want to have to explain all that "root" stuff to him, etc... I want the phone as basic and simple as can be, hence , I want to reflash the stock firmware.
I am having troubles though. Booting the phone into download mode and starting LGUP fails to recognize the phone. I've tried with Uppercut as well and it says I'm missing a file in Apps/Roaming, etc...
Not sure the problem because I have reflashed stock many times with LGUP. Could it be that Havoc has changed the "identity" of the phone, or that it's on Android 11?
Any help to get this back to stock is much appreciated!
Got it figured out. Flashed back to an older TWRP (was on Orange Fox), flashed an old stock Oreo ROM, and then was able to flash kdz with LGUP.

Categories

Resources