No Wifi/Cell/Cell data after attempted restore in TWRP - ZTE Axon 7 Questions & Answers

Did Axon 7 root without bootloader unlocked. Phone is rooted but bootloader is still locked. I attempted to restore with TWRP to my original backup and got some sort of error. Restored from a second backup and the phone boots up but there is no cell signal or wifi. Should I try to restore to one of the images from other users? I have TWRP 3.0.2.0.

does this help:
http://forum.xda-developers.com/axon-7/how-to/please-check-wifi-flashing-bootloops-t3451544

JKSurf said:
Did Axon 7 root without bootloader unlocked. Phone is rooted but bootloader is still locked. I attempted to restore with TWRP to my original backup and got some sort of error. Restored from a second backup and the phone boots up but there is no cell signal or wifi. Should I try to restore to one of the images from other users? I have TWRP 3.0.2.0.
Click to expand...
Click to collapse
Followed guide here to get radio working again:
http://forum.xda-developers.com/axon-7/how-to/please-check-wifi-flashing-bootloops-t3451544

Related

Stuck in Bootloop after Nandroid restore using TWRP

Hello,
I was using custom ROM but I had to return to stock T-Mobile for a short while to apply SIM network unlock. I made a nandriod backup before flashing back to stock ROM. Now I want to restore everything after I unlocked my phone. The problem is my phone is stuck in bootloop. I even tried factory rest but still won't boot.
Thanks in advance

Weird Cellular/IMEI/EFS issue.

I installed TWRP 3.0.2-0 on my axon A2017G B03, unlocked the bootloader, installed CM13 after a small hiccup (had to temporarily install A2017G B06 and Bootstack).
All went well, I really enjoyed my phone. The only problem was that I'm an audiophile and there was a big distortion on the speakers.
I tried to install a Dolby zip via TWRP to improve this. Before I did that, I took a full TWRP backup.
The Dolby app didn't help one bit, after which I wanted to rollback by restoring the backup. Appearently, restoring the EFS is a really bad idea, since after that, CM13 wouldn't boot anymore. So, I tried using DrakenFX' B06 bootstack and stock image. When I did that, my phone could not connect to Wi-Fi nor detect my SIM-card.
Using the commands
Code:
adb shell dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1 and dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2
I restored my Wi-Fi. My phone now recognises my SIM-card, but I can't connect to the cellular networks. I have no IMEI. It can detect cellular networks, but not connect to them.
I have "efs1.emmc.win" and "efs1.emmc.win.md5" files from the TWRP backup of CM13 from just before I killed my cellular and another EFS backup I took just before unlocking BL and flashing TWRP (A2017G B06).
When I do a clean install of A2017G B06 and restore the TWRP EFS backup I made when on B06, when the phone boots, the phone doesn't detect my SIM.
When I do a clean install of CM13 and restore the TWRP EFS backup I made when on CM, CM13 doesn't boot at all.
I've spent about a day trying just about anything. Nothing seems to work. Can someone pull their modem file? Or would flashing NON-HLOS.bin help? Is there a different way of restoring my EFS backups? I read something about TWRP 3.0.2-0 not playing nice with EFS. Would flashing TWRP 3.0.2-2 and then restoring EFS work? Or is there a way to restore the phone back to "just-out-of-the-box" status? I don't mind losing unlocked BL or TWRP, I can do that all again. I thought as long as I backup everything including EFS, nothing can really go wrong. A user in XDA posted that "shady" guides that "don't get discussed at XDA" can usually help you get IMEI back. I don't want to illicit illegal practices here, but I'm desperate enough to try just about anything.
Thanks a lot for your help. If no-one here can help me, I suppose it's back to amazon. And probably pay a decent amount for it, too
Perhaps try flashing newer twrp version and restore your efs backup?
Controllerboy said:
I installed TWRP 3.0.2-0 on my axon A2017G B03, unlocked the bootloader, installed CM13 after a small hiccup (had to temporarily install A2017G B06 and Bootstack).
All went well, I really enjoyed my phone. The only problem was that I'm an audiophile and there was a big distortion on the speakers.
I tried to install a Dolby zip via TWRP to improve this. Before I did that, I took a full TWRP backup.
The Dolby app didn't help one bit, after which I wanted to rollback by restoring the backup. Appearently, restoring the EFS is a really bad idea, since after that, CM13 wouldn't boot anymore. So, I tried using DrakenFX' B06 bootstack and stock image. When I did that, my phone could not connect to Wi-Fi nor detect my SIM-card.
Using the commands
Code:
adb shell dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1 and dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2
I restored my Wi-Fi. My phone now recognises my SIM-card, but I can't connect to the cellular networks. I have no IMEI. It can detect cellular networks, but not connect to them.
I have "efs1.emmc.win" and "efs1.emmc.win.md5" files from the TWRP backup of CM13 from just before I killed my cellular and another EFS backup I took just before unlocking BL and flashing TWRP (A2017G B06).
When I do a clean install of A2017G B06 and restore the TWRP EFS backup I made when on B06, when the phone boots, the phone doesn't detect my SIM.
When I do a clean install of CM13 and restore the TWRP EFS backup I made when on CM, CM13 doesn't boot at all.
I've spent about a day trying just about anything. Nothing seems to work. Can someone pull their modem file? Or would flashing NON-HLOS.bin help? Is there a different way of restoring my EFS backups? I read something about TWRP 3.0.2-0 not playing nice with EFS. Would flashing TWRP 3.0.2-2 and then restoring EFS work? Or is there a way to restore the phone back to "just-out-of-the-box" status? I don't mind losing unlocked BL or TWRP, I can do that all again. I thought as long as I backup everything including EFS, nothing can really go wrong. A user in XDA posted that "shady" guides that "don't get discussed at XDA" can usually help you get IMEI back. I don't want to illicit illegal practices here, but I'm desperate enough to try just about anything.
Thanks a lot for your help. If no-one here can help me, I suppose it's back to amazon. And probably pay a decent amount for it, too
Click to expand...
Click to collapse
It seems that I am having the same kind of issue with the newest version of TWRP. After having some issues with incoming and outgoing phone calls, I stumbled across the above command. After using the command I lost my ability to connect to my network operator. Therefore I tried to do a recovery from TWRP and now I'm stuck with an IMEI which shows "0".
Sadly it seems that I don't have a backup of my efs partition (noob) and now I'm desperately finding possible solutions.
Any ideas? I feel that the trying to connect to the network with no IMEI is the cause of my problem...
Dawacko87 said:
It seems that I am having the same kind of issue with the newest version of TWRP. After having some issues with incoming and outgoing phone calls, I stumbled across the above command. After using the command I lost my ability to connect to my network operator. Therefore I tried to do a recovery from TWRP and now I'm stuck with an IMEI which shows "0".
Sadly it seems that I don't have a backup of my efs partition (noob) and now I'm desperately finding possible solutions.
Any ideas? I feel that the trying to connect to the network with no IMEI is the cause of my problem...
Click to expand...
Click to collapse
Both myself, Controllerboy and many others pretty much tried everything to restore working imei numbers to no avail. Only solution for both of us was to RMA our phones unfortunately.
Tebor said:
Both myself, Controllerboy and many others pretty much tried everything to restore working imei numbers to no avail. Only solution for both of us was to RMA our phones unfortunately.
Click to expand...
Click to collapse
That's exactly not the answer I wanted to hear
I think in that case it would be advisable to go back t stock and lock the bootloader? And have you been presented with a bill from Amazon/ZTE?
Flash modemst won't work anyway, you have to flash full bootstack.
Install TWRP, then flash A2016G bootstack file that DrakenFX provided
tamahouse02 said:
Flash modemst won't work anyway, you have to flash full bootstack.
Install TWRP, then flash A2016G bootstack file that DrakenFX provided
Click to expand...
Click to collapse
Already tried going back to stock with the bootstack and files provided by DrakenFX, but the mobile network connection won't work.
It started of with connecting to the mobile network, at least it showed full bars, but without a data connection. After a few minutes
the connection to the network was lost and I haven't been able to register again.
So it seems that Trebor is right, sadly...

Axon7 bricked

Hello everyone,
I tried to install SuperSU on my Axon7 (by flashing SuperSU-v2.65-20151226141550 in TWRP) and after that, my phone doesn't boot anymore.... I still have access to TWRP (3.0.2-2) but I can't access to the system. I tried to restore a backup I made with TWRP and wipe cache, DALVIK and data but it didn't work.
When I try to boot, I'm blocked on the screen "ZTE powered by Android".
How can I restore my stock ROM with TWRP?
PS: I was in stock rom and my model is the B06.
Thanks in advance!!
Is your bootloader unlocked? In such case, my advice is to flash the ZADmix7 ROM to your 2017G from TWRP.
Otherwise you can go back to stock using this guide. If you can access recovery or bootloader, then your brick is a very, very soft brick.
st3ph31 said:
Hello everyone,
I tried to install SuperSU on my Axon7 (by flashing SuperSU-v2.65-20151226141550 in TWRP) and after that, my phone doesn't boot anymore.... I still have access to TWRP (3.0.2-2) but I can't access to the system. I tried to restore a backup I made with TWRP and wipe cache, DALVIK and data but it didn't work.
When I try to boot, I'm blocked on the screen "ZTE powered by Android".
How can I restore my stock ROM with TWRP?
PS: I was in stock rom and my model is the B06.
Thanks in advance!!
Click to expand...
Click to collapse
If your BL is still unlocked and you did flash SU2.65 before you should have unlocked it, than you might follow this thread too to unlock your BL first and then flash SU2.65 again
https://forum.xda-developers.com/showpost.php?p=70562463&postcount=154
https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
Perhaps this might help
Thanks to you two for your help, I followed this tuto: https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484 and everything is fine now
I thought that TWRP was enough to install SuperSU... Next time, I will read more carefully the tutos

sony android update phone bootloop

hello forums,
today I installed an android update onto my sony xperia x compact which resulted in my phone ending up in a boot loop.
I see the sony logo, then the Xperia slogan and then it reeboots again.
The companian app does not recognize my phone.
What can I do to backup data on my phone?
Should I flash the boot loader to use backup / restore functions?
My phone is also encrypted. will backup / ADB even allow me to get the data stored on my phone?
Thanks
Did you unlock your bootloader, I think if you have unlocked bootloader, you can't update straight away from the phone? Mine stuck on "Sony" screen once, and then it restart itself and boot into the system. The update failed,but I can boot back to the system. Maybe you should try starting the device again and if it stuck in "Sony" wait it for a while
Ps: better do a backup before system update.
I am sorry I didnt mention that before.
until now, the phone is using stock bootloader and stock rom
can't I replace the boot loader with a custom one to use adb to backup my data?
that worked with my old flashed phone, because rom and OS are separated from each other.
soomon2 said:
I am sorry I didnt mention that before.
until now, the phone is using stock bootloader and stock rom
can't I replace the boot loader with a custom one to use adb to backup my data?
that worked with my old flashed phone, because rom and OS are separated from each other.
Click to expand...
Click to collapse
Unlocking BL won't help you to backup data. On contrary it will wipe your data. If it is really bootloop, what you probbaly can do is flashing the same firmware (before the failed update) without selecting to wipe data
PS: Regarding the unlocking of bootloader, Don't do it unless you know what you are doing. It will wipe the TA needed for the camera. Please please do research on how to backup TA before you ever unlock your bootoader.
sadly I cannot reflash the same rom as all is stock software, one mistake I will not make again.
Sony support sais I have to do a factory reset and there is no way to save my data beforehand in the current state. also, it seems they just dont care about customer data as they do not make a backup of the data or the OS before screweing it up.
if you know how I could reflash the firmware, please tell me. I don't know how
So I guess I am screwed?

TWRP corrupted? Won't restore, won't backup, won't wipe.

I bought a new XT1575 a couple of weeks ago. Once I'd read enough to have confidence I followed the instructions to extract that long number to paste into the form on the Motorola web site and ask them to send me a code. They did, I input the code, I got a notice that my bootloader was unlocked. Once that was done I installed TWRP via ABD (I think, whatever the directions said). TWRP worked, I wiped the stock OS, flashed a custom ROM (Lineage 14) and everything worked perfectly.
Today I wanted to backup my existing ROM, wipe the device and install a different custom ROM. I booted into TWRP and I think it completed the backup. When I went to wipe though, it would crash partway through and boot back to the bootloader unlocked screen. If I tried to simply overwrite the existing ROM with the new ROM that would crash and boot to the bootloader unlocked screen too. Now I can't complete a backup either.
As I'm writing this I'm wondering if the micro USB card could be at fault, since that's where I want to back up to and that's where the new ROM is. However, if it was a corrupted card wouldn't the wipe function still work?
Any idea if reflashing TWRP would solve my problem? Any better solutions?

Categories

Resources