Database Users

How to unbrick my ZTE Axon 7 mini b2017g

Dear Seniors.
I am facing great hardship because my phone is stuck at boot logo.
No booting in recovery mode to flash another rom.
I did unlock bootloader of it by using tuliptool with success. After that i flashed custom rom in it. after reboot it is happening that.
Please suggest to recover it.

Did you flash twrp after unlocking? Did you make backup of stock ROM? Perhaps find a version of the factory firmware and flash that.

Dear I have no backup and i flashed TWRP recovery.......
It is to aware you that i did relock bootloader now my phone is working properly. but i am unable to enter recovery mode. !!!
Now my phone is running android 6.0.1 B02
But i am failed to root this rom uptill now due above mentioned problem.

modorate said:
Dear I have no backup and i flashed TWRP recovery.......
It is to aware you that i did relock bootloader now my phone is working properly. but i am unable to enter recovery mode. !!!
Now my phone is running android 6.0.1 B02
But i am failed to root this rom uptill now due above mentioned problem.
Click to expand...
Click to collapse
I found software update notification but when i update an error accruing while update. (This update not compatible with this device"
In easy words......... my recovery.img has been corrupted. I have no idea to get rid of this situation.

I planned to unlock my Mini's bootloader this weekend. After reading this post, I decided to act later until the root cause has been figured out.

bao_gg said:
I planned to unlock my Mini's bootloader this weekend. After reading this post, I decided to act later until the root cause has been figured out.
Click to expand...
Click to collapse
Several people myself included have been able to use tuliptool to successfully unlock and root the device.

mine is hard bricked too. but I think it is worse than the case listed on the op.
if you want to hard bricked these are the steps:
follow the procedure to install the Spanish ROM 6.1, than another android m b12, than finally the android seven......use tulip tool and install twpr fine, root ect. amazing ROM.......buuuuut......I lost my IMEI somewhere in this process, and the original FTM which had a small menu changes to another static one, without the menu.
I needed this menu to open the com port to fix the IMEI. than I had the brilliant idea to re-flash android M via twrp (without modifying the zip file to remove the recovery, something I knew so well from the older axon mini).
results:
-lost twpr because the stock ROM wrote over it,
-cannot boot the OS because I flashed android m but the phone had the aboot 7.
-i now have a brick
I need a genious to sujest something to bring it back to life........sh....t...sh...t.....sh...t
any chances I could inject aboot7 via ADB through my dead recovery which somehow the phone recognises? ADB shell still seems to be working
thanks

Problems to update

Hi!!
I'm having problems to update from android 8.0.0. My phone is no rooted, the bootloader is open (I have learned that it's so expensive to close it xD xD, when you close it the phone makes briked) and when the update is downloading and the phone needs to reboot to install it, I can't because apears TWRP and I can't to install from here, and I don't find the normal or stock recovery to install it.
What can I do?
Thanks in advance!

You can flash this in twrp just like any other rom.
https://forum.xda-developers.com/lg-g6/development/rom-eu-lg-h870-20a-rom-t3794503

I had my phone unlocked and rooted with Fulmics 4.2 onboard.
Right when Oreo dropped, I locked my phone and flashed the update straight away.
No brick occured.

Alpha-Retard said:
You can flash this in twrp just like any other rom.
https://forum.xda-developers.com/lg-g6/development/rom-eu-lg-h870-20a-rom-t3794503
Click to expand...
Click to collapse
So I not need another OS, in fact, I have this oreo installed, but when the system sais that there are updates (now I have one update pending of 700mb) and when it's need reboot for install, this can't finish because TWRP appear, and doesn't let it finish to install the update...
I don't know exactly what I need to do, and I don't want to lose mine actual OS.
Could be possible to update the updates, likely manual mode or similar? Without reboot the phone and avoid the reboot and pass by twrp?
Thanks again

T-Mobile 6T OTA Error, Can't update.

Tried everything including searching the forums for an answer. My device is bootloader unlocked, was formally rooted and had a few modules installed, as well as TWRP. It is now simply bootloader unlocked with no root and stock recovery, and even tried a factory data reset as well as multiple attempts at flashing the stock TMo rom for the 6T to no avail. The flash-all.bat can't proceed without the "images.zip" file and that is nowhere to be found in the rom's zip or anywhere else. I'm still running the software that came out of the box on launch day because I've had this issue persist since the first OTA update was released. The OTA will download and then installation comes to a halt with error message "Couldn't update. Installation problem."
Please help, I just want to update this phone. Never had this much trouble with something so mundane.
edit: MSM download tool successfully reverted to stock rom and fixed update issue. Thanks XDA

How to install OTA updates with unlocked bootloader?

I have PPW29.116-20 update installed on my G6 Plus. On that same update, I followed the instructions from the other thread to unlock bootloader and install Magisk for root. Now, I am trying to figure out how to install latest OTA security update that started showing up few days ago. I couldn't find any clear instructions around here, as most of them are either from Oreo times, or not very clear. Hopefully, someone has run into this issue on Pie already and knows how to deal with it. Any help would be greatly appreciated.

mrh45Zed said:
I have PPW29.116-20 update installed on my G6 Plus. On that same update, I followed the instructions from the other thread to unlock bootloader and install Magisk for root. Now, I am trying to figure out how to install latest OTA security update that started showing up few days ago. I couldn't find any clear instructions around here, as most of them are either from Oreo times, or not very clear. Hopefully, someone has run into this issue on Pie already and knows how to deal with it. Any help would be greatly appreciated.
Click to expand...
Click to collapse
As far as I know, You can't. You have to be on stock ROM, re-lock the bootloader, take the OTA. There are some risks in re-locking, you can't have any modifications active or you might brick. But if you know what you're doing, it's safe.

weazie said:
As far as I know, You can't. You have to be on stock ROM, re-lock the bootloader, take the OTA. There are some risks in re-locking, you can't have any modifications active or you might brick. But if you know what you're doing, it's safe.
Click to expand...
Click to collapse
Does locking need to be in the original stock or the latest version also works?

dangelfire said:
Does locking need to be in the original stock or the latest version also works?
Click to expand...
Click to collapse
Latest also works. That way you get the newest one and the OTA update is not needed until the next possible update.

You have to uninstall root, if you had a custom.bootlogo you have to replace it with original bootlogo and you can take the OTA.
Or you can just download full fastboot firmware and flash it
https://mirrors.lolinet.com/firmware/moto/evert/official/
Select your channel (don't know what's your channel? Go to settings> about phone and software channel)
If your channel don't have the lastest build version download from retail folder
Sent from my Motorola Moto G6 Plus using XDA Labs

I tried to relock my bootloader, and while it was successfully relocked, I am still unable to get updates.
I unlocked it back on Oreo, but never made any other software changes.
The device boots up with the 'different OS has been installed' message and the updater tells me the system integrity is compromised. The device is also decertified from Google play.
Has anyone got any tips?

awdAvenger said:
I tried to relock my bootloader, and while it was successfully relocked, I am still unable to get updates.
I unlocked it back on Oreo, but never made any other software changes.
The device boots up with the 'different OS has been installed' message and the updater tells me the system integrity is compromised. The device is also decertified from Google play.
Has anyone got any tips?
Click to expand...
Click to collapse
Maybe get the latest version for your channel and flash it using fastboot (as in, full wipe OS reinstall). But wait to see if anyone here has a better idea.

awdAvenger said:
I tried to relock my bootloader, and while it was successfully relocked, I am still unable to get updates.
I unlocked it back on Oreo, but never made any other software changes.
The device boots up with the 'different OS has been installed' message and the updater tells me the system integrity is compromised. The device is also decertified from Google play.
Has anyone got any tips?
Click to expand...
Click to collapse
for now there`s no a perfect way to re lock bootloader, if you want to hide the "different OS has been installed" warn only flash this zip before you re lock your bootloader, dont forget that in stock will still show that system is compromised if you try to search for updates. (so my recommendation is dont relock bootloader! flash full stock rom with fastboot commands if you dont want to loose your apps just erase "fastboot erase userdata" from fastboot commands)
https://drive.google.com/open?id=1VE0kaUxmUbbhhNo075MCaW6VxaOTiDL6
For get certified playstore you need to verify that you can install Netflix if you can only wipe app data and playstore will show as certified device.
if you cant install netflix you need to change device fingerprint with a magisk module Safety Net Patch or with Magisk hide props.

ETA: never mind, figured it out.

Soft brick on oneplus 6T after version upgrade from Lineage OS

Hi there,
So I unknowingly did something kinda risky and of course, it backfired. I used the in-system update feature of linage OS to upgrade my version on my Oneplus 6T. Can't exactly remember which one the old version was, but it was at least 4 versions older than the newest nightly one. Afterward, the phone got stuck in a boot loop. Also, in recovery, it can't bind/ mount the system, because there is no file directory. "E:Failed to bind mount /mnt/staging/emulated/media/0 to /storage/emulated: No such file or directory." I tried the following:
- went into recovery, factory reset the device, then flashed new clean lineage os [multiple different versions]. Gets back to boot loop afterward. (note that Fastboot shows no bootloader version or baseband version)
- tried unlocking the bootloader via fastboot flashing unlock. It fails with error code: (remote: Unrecognized command flashing unlock)
- tried copying the contents of slot a to b, in case one was severely outdated as the cause for the soft brick as stated in this guide. Didn't change mentioned issue after flashing os.
- installed Qualcomm USB drivers, to get the PC to detect the phone as a USB device
- after that, tried using the ms-downloader tool to reset and re-flash the phone. It does not get detected and the downloader tool waits for the full 15s before returning the error for no detected device.
- tried unlocking the bootloader itself via fastboot flashing unlock_critical. same error as with normal unlock: (remote: Unrecognized command flashing unlock)
Maybe overwriting the possibly corrupt bootloader would be a good bet, but as mentioned, I cannot unlock the device to make the command for that useable.

Hey, so I am not really knowledgeable enough to help fix this, but I did notice one thing: Why are you using the wiki page from Lineage for the OnePlus 6 (enchilada) instead of the 6t (fajita)?

state_azure said:
Hey, so I am not really knowledgeable enough to help fix this, but I did notice one thing: Why are you using the wiki page from Lineage for the OnePlus 6 (enchilada) instead of the 6t (fajita)?
Click to expand...
Click to collapse
I didn't even notice it was for enchilada, but iirc the file I loaded was only to copy the contents of slot a to slot b. I could search for a fajita version of this. Still, thanks for your reply.

Hi there,
I have the exact same problem. After updating my OP 6T, the cell phone was broken. It's stuck in a reboot loop. Which surprises me, however, because the documentation for this device type recommends that the update be carried out using the system's internal update process. I also noticed that some OTA updates work and some don't. Unfortunately, this is the only way to make use of it very little fun because you never know if the phone is working again when you update. And the security weaknesses show that updates are also important for Lineageos. thanks for the feedback

Zak0r said:
Hi there,
So I unknowingly did something kinda risky and of course, it backfired. I used the in-system update feature of linage OS to upgrade my version on my Oneplus 6T. Can't exactly remember which one the old version was, but it was at least 4 versions older than the newest nightly one. Afterward, the phone got stuck in a boot loop. Also, in recovery, it can't bind/ mount the system, because there is no file directory. "E:Failed to bind mount /mnt/staging/emulated/media/0 to /storage/emulated: No such file or directory." I tried the following:
- went into recovery, factory reset the device, then flashed new clean lineage os [multiple different versions]. Gets back to boot loop afterward. (note that Fastboot shows no bootloader version or baseband version)
- tried unlocking the bootloader via fastboot flashing unlock. It fails with error code: (remote: Unrecognized command flashing unlock)
- tried copying the contents of slot a to b, in case one was severely outdated as the cause for the soft brick as stated in this guide. Didn't change mentioned issue after flashing os.
- installed Qualcomm USB drivers, to get the PC to detect the phone as a USB device
- after that, tried using the ms-downloader tool to reset and re-flash the phone. It does not get detected and the downloader tool waits for the full 15s before returning the error for no detected device.
- tried unlocking the bootloader itself via fastboot flashing unlock_critical. same error as with normal unlock: (remote: Unrecognized command flashing unlock)
Maybe overwriting the possibly corrupt bootloader would be a good bet, but as mentioned, I cannot unlock the device to make the command for that useable.
Click to expand...
Click to collapse
Whatever you do in your device,they will not touch critical partition such as bootloader and many more of it, do u still have twrp or other recovery on your device?

Prinçe çharming ap said:
Whatever you do in your device,they will not touch critical partition such as bootloader and many more of it, do u still have twrp or other recovery on your device?
Click to expand...
Click to collapse
I still got the stock recovery. Booting from TWRP image didn't work on my last try, I don't remember the exact specifics anymore. I'll try again.

Zak0r said:
I still got the stock recovery. Booting from TWRP image didn't work on my last try, I don't remember the exact specifics anymore. I'll try again.
Click to expand...
Click to collapse
Zak0r said:
I still got the stock recovery. Booting from TWRP image didn't work on my last try, I don't remember the exact specifics anymore. I'll try again.
Click to expand...
Click to collapse
Tell me the exact problem you with your phone and maybe i can help

once again,
today got informed via updater that a new update is available. I try do install it, but now i stuck again in recovery. And the only think i can do is a factory reset and everything is lost.
can anybody give an info if it is safe to update the 6T trough OTA? It doesn't look like that.

zero4one said:
once again,
today got informed via updater that a new update is available. I try do install it, but now i stuck again in recovery. And the only think i can do is a factory reset and everything is lost.
can anybody give an info if it is safe to update the 6T trough OTA? It doesn't look like that.
Click to expand...
Click to collapse
Oof, I thought mine only got bricked because I tried to upgrade across 4 versions. It seems as though even normal updates now cause soft bricks, neat.

I tried again today but there seems to be a connection to the error. I had an update pending, which could be installed without any problems. After the restart, I was informed that there was another update, after installing this update there was a total failure again. Could it be that this is somehow related to slot A / B?

zero4one said:
I tried again today but there seems to be a connection to the error. I had an update pending, which could be installed without any problems. After the restart, I was informed that there was another update, after installing this update there was a total failure again. Could it be that this is somehow related to slot A / B?
Click to expand...
Click to collapse
Why don't you try to flash Stock rom on both slots via MSM tool and then just try ota to update to latest build for you specific device

How can i verify if there is an difference between slot a and slot b?
If i flash the stock rom i will be back on oos and that is not what i want i will continue using los, or do we have an idea missmatch there?
thanks for help

zero4one said:
How can i verify if there is an difference between slot a and slot b?
If i flash the stock rom i will be back on oos and that is not what i want i will continue using los, or do we have an idea missmatch there?
thanks for help
Click to expand...
Click to collapse
What do you exactly want ?