Vendor partition gone/cannot mount - ZTE Axon 7 Questions & Answers

Ive come across a very odd issue while rooting a used A2017U I purchased off ebay to replace my old one that finally broke.
In summary, fastboot will NOT activate, and my vendor partition is totally missing/unmountable.
The phone came with Nougat B32 installed, I sideloaded the Oreo B20 successfully to bring the OS up to date. Then I started the normal unlocking/rooting procedure.
Was having a ton of issues enabling fastboot, so I flashed an image of TWRP.
Got the bootloader unlocked.
At some point the vendor partition had become corrupted/went missing. I am no longer able to see it in the mountable partitions tab in TWRP
I have tried the vendor creation tool, which crashes and forces a device restart, I have tried Okis Party tool, and I have tried the make_vendor_800mb.zip all without success.
This phone does NOT have root. I have also tried every EDL package available for the A2017U to see if it can recover my vendor partition. Has anyone had this problem or been able to fix it?

me too have the same issue

Related

Can't flash ROM's or use USB to ADB to flash/restore original Android OS.

HI all,
I've come from flashing Samsung S4's for years but after trying to flash an update I got the boot screen and nothing happens.
Here's the situation.
I had originally installed PureNexus, rooted, unlocked the boot loader and probably turned off USB ADB settings (and I don't typically want an alert when plugging in the USB cable) as I usually transfer media and ROM's to the download folder for future flashing.
I saw that 6.01 was released and saw that the bootloader and radio were updated. So I tried to flash those before updating with PureNexus 6.01.
I did a nandroid backup before I did this, knowing something might go wrong.
I think my camera wasn't working so I tried a nandroid recovery to get it back.
Unfortunately I didn't read about the password encryption bug which TWRP had as I did the restore in my car and didn't have internet as it was free down time. When it was completed, I got the failed password issue. So I decided just to format everything. I used TWRP and formatted everything including the vendor partition. Of course, I forgot it would delete the Nandroid, too. I'm too used to having a spare external SD card to store all of the Nandroids on.
Anyway after that I can only get to TWRP.
I've tried installing the original 6.0 ROM, PureNexus ROM through TWRP with the appropriate ZIP files. It says it's completed, no errors but just the boot screen.
I've tried restoring through ADB with Windows 10 and through the USB. I don't get to an ADB selection on the bootloader, but can get to the ADB sideload throught TWRP. The problem is when I tried to restore through ADB nothing happens as it says "waiting" when I use fastboot flash-all. ADB devices does give me an ID when I do ADB so it is connecting. However, I believe ADB is waiting for the USB-ADB to be turned on which I can't do because I can't get to the OS system partition.
I've tried using several of the Skip Soft Toolkit and again, it waits and says closed.
I'm assuming that USB-ADB is closed and not turned on. I don't know why TWRP can't overwrite the system partitions if I try to flash, unless it's still encrypted but shouldn't be as I formatted everything, except for the boot loader and that is unlocked as I get the screen that I should lock the bootloader because the OS can't tell if it is corrupted.
Any ideas? I can only think if someone sends me a Nandroid of a configuration that may flash it back to a level I can get into Android and then get back to USB ADB and do a clean install with fastboot flash-all.
Please help!! Thanks in advance for your suggestions. I hope I gave you enough information to help me out.
Update. I apparently found a way. Luckily TWRP has a Flash image feature as well as flashing the vendor image. Flashed PureNexus 6.01 and PureNexus Gapps and thank goodness that worked! No idea why ADB was not flashing except for the configuration for USB ADB was turned off on the ROM originally.

[Brick?] How to solve problem with A2017G (every mode available)

Good evening, guys,
I'm at a loss as to what is happening with my A2017G.
I had TWRP 3.1.0-2, B04 and SuperSU, but the SU wasn't working properly (the message that root privileges were given to my root apps kept popping up but the actual apps didn't work as intended, so to flash the alternative file that I found somewhere in the forums here.
After that, I could not pass the ZTE logo in order to boot the system.
Went back to TWRP, flashed bootstack and stock system by tron again, SuperSU - and the same result.
Without knowing what else to do, I grabbed the full stock B04 file and tried to flash it.
Now, I have a phone whith stock recovery working, without fastboot, with FTM mode, with EDL mode all working, but I can't seem to use one of those in order to restore my phone that, when I try to boot to system, keeps stuck at the screen with the message that the bootloader has been unlocked.
I tried flashing twrp and the update.zip through Mi Flash, but I get a syntax error (my device shows as COM3);
In recovery, when I choose to apply upgrade through SD, a message appears "You can't upgrade from SD card, sorry";
FTM mode works and my phone loads as an adb device (seeing in Axon 7 tool), but if I try to sideload the update.zip through the Windows 10 cmd it crashes with a message saying "bad alloc", or something.
So, I'm at a loss here. I have every modes working, and I still cannot flash anything to my device?
Or am I doing it wrong?
Thank you.
I'm almost sure you can't just flash an official update zip with MiFlash, so do this:
Download this zip, comes from djkuz. It is the full A2017G system with fbop and fastboot
https://mega.nz/#!ZhwR1BAD!PuIWa5Viv...iR-j1U8wZZidTw
After that unpack it and use MiFlash to get it flashed nicely on your device. When you finish, you'll have B10 I think. I experienced random reboots without any thermal problems (even rebooted while it was in my pocket) so you might be better off going to RR but be real careful if/when going back to stock if you decide to do this (i had a DFU brick )
Choose an username... said:
I'm almost sure you can't just flash an official update zip with MiFlash, so do this:
Download this zip, comes from djkuz. It is the full A2017G system with fbop and fastboot
https://mega.nz/#!ZhwR1BAD!PuIWa5Viv...iR-j1U8wZZidTw
After that unpack it and use MiFlash to get it flashed nicely on your device. When you finish, you'll have B10 I think. I experienced random reboots without any thermal problems (even rebooted while it was in my pocket) so you might be better off going to RR but be real careful if/when going back to stock if you decide to do this (i had a DFU brick )
Click to expand...
Click to collapse
Flashing the extracted B10 package solved it, thanks!
Until now, everything's smooth, running B04.
Thank you.

I screwed up. "Your device is corrupt." on boot.

Pixel 3a. Bootloader unlocked. Stock. Previously have used Magisk although I didn't have it installed or setup at the moment. I was neglectful and hadn't updated OTA or factory images since updating to Android 10. My current boot slot is b. I've tried updating via Magisk OTA or system OTA but they both fail, so I use factory images manually to keep my data partition.
Today I downloaded the sargo November 2019 image. The process I've been using across a few Pixel phones the past few years has been to manually unpack the Factory image ZIP and the update ZIP, then manually fastboot flash bootloader, reboot, radio, reboot, then boot_a and boot_b, system, system_b, vendor, and modem.
It should have been a hint to me that I got an error when I went to flash system. My console told me I need to use fastbootd. So I switched there, flashed the system partitions. Went to reboot and got "Your device is corrupt. It can't be trusted and may not work properly.", which I've never encountered before. Press Power - ignore the device-is-unlocked message, and get to the Google boot screen. And then the device appears to be frozen.
Right now I'm thinking to go back to my first Android 10 factory image and see if I can reverse whatever I did... but figured I should check here to see if I had missed something important. Low and behold this forum says to only flash one slot at a time, to switch and boot into the other slot, etc. Okay, so I messed up. Any good ideas on how to fix what I did?
UPDATE: I don't normally sideload updates, but I got into recovery mode, sideloaded the OTA for November, and I'm back in business. I'll do a few reboots to be sure I'm good but the phone did boot up, my user data is intact. The phone still starts out with a "your phone is corrupt" message, which is then followed by the "you have an unlocked bootloader" message. That second screen has some messed up characters on it.
If anyone has advice on the "right" way to maintain slots A vs. B and how to be careful, how to combine this with Magisk etc and can point me to posts in threads, that'd be helpful for the future. Thanks!
I don't understand why so many people even mess with A/B partition commands. If you follow the normal flashing instructions, you don't specify a boot partition. Entering specific boot partition commands will greatly increase the odds that you mess something up.
ohioDroid said:
Pixel 3a. Bootloader unlocked. Stock. Previously have used Magisk although I didn't have it installed or setup at the moment. I was neglectful and hadn't updated OTA or factory images since updating to Android 10. My current boot slot is b. I've tried updating via Magisk OTA or system OTA but they both fail, so I use factory images manually to keep my data partition.
Today I downloaded the sargo November 2019 image. The process I've been using across a few Pixel phones the past few years has been to manually unpack the Factory image ZIP and the update ZIP, then manually fastboot flash bootloader, reboot, radio, reboot, then boot_a and boot_b, system, system_b, vendor, and modem.
It should have been a hint to me that I got an error when I went to flash system. My console told me I need to use fastbootd. So I switched there, flashed the system partitions. Went to reboot and got "Your device is corrupt. It can't be trusted and may not work properly.", which I've never encountered before. Press Power - ignore the device-is-unlocked message, and get to the Google boot screen. And then the device appears to be frozen.
Right now I'm thinking to go back to my first Android 10 factory image and see if I can reverse whatever I did... but figured I should check here to see if I had missed something important. Low and behold this forum says to only flash one slot at a time, to switch and boot into the other slot, etc. Okay, so I messed up. Any good ideas on how to fix what I did?
UPDATE: I don't normally sideload updates, but I got into recovery mode, sideloaded the OTA for November, and I'm back in business. I'll do a few reboots to be sure I'm good but the phone did boot up, my user data is intact. The phone still starts out with a "your phone is corrupt" message, which is then followed by the "you have an unlocked bootloader" message. That second screen has some messed up characters on it.
If anyone has advice on the "right" way to maintain slots A vs. B and how to be careful, how to combine this with Magisk etc and can point me to posts in threads, that'd be helpful for the future. Thanks!
Click to expand...
Click to collapse
Just unpack the factory images and remove the -w. Then either do flash-all or open the flash-all and follow the steps inside to see what you need to flash. The portion that says update will fail if you have not followed the initial steps. Don't specify boot partitions the factory images should flash to both slots. That should take care of your corrupted message.
Sent from my Pixel 3a using Tapatalk
sic0048 said:
I don't understand why so many people even mess with A/B partition commands. If you follow the normal flashing instructions, you don't specify a boot partition. Entering specific boot partition commands will greatly increase the odds that you mess something up.
Click to expand...
Click to collapse
Probably because there are references around saying to do so. And the threads have so many posts it can be difficult to read it all and learn something is right or wrong.
3-ish years ago I had come across this post that specifically says to flash A/B both:
https://forum.xda-developers.com/pixel-xl/how-to/guide-update-fastboot-t3498187
I've been following it on Pixel phones every since then. I never gave a second thought to the A/B partitions up until this happened. The main thing that was different now from my perspective was having to use fastbootd to flash the system, which I've never done before.
By manually flashing the bootloader and radio, and then using Recovery to install an OTA update (instead of using the Factory image) I was able to get the phone to boot properly. It still starts up by saying it is corrupt and requiring me to hit the power button to proceed, and then showing the 'phone is unlocked' message with some garbled characters, but then starts up and works fine (as far as I can tell). Maybe I can OTA the future December update and that will fix things? Or is there something I can do now?
Just want to try to provide some sound advice, next time maybe look to use the flash-all.sh script. There is absolutely zero reason not to, and going outside of that just means you're just tinkering around way more than necessary.
I think you're over complicating things. Just download latest factory image, unzip it, connect the phone to PC and double click the run me bat file. I always clean flash, but if you want to keep data, as others have said, delete the - w .
Just an update on the status...
I decided to not try to install magisk or anything during November. With the December update I ran it OTA the standard format. The "Corrupt" message is gone. I assume (haven't yet checked) that I've switched over to boot_a.
Okay so going forward if I want to install Factory Images while keeping data just use the flash_all.bat but remove the -w switch. Got it.
Now I just need to get Magisk back on there and figure out the current way to enable WiFi Tether/hotspot.

Find device storage corrupted your device is unsafe now.

So I unlocked bootloader on my redmi note 7.
Then I flashed twrp and rooted my device.
Then I flashed pixel experience but it stuck on the Google logo after reboot. I tried factory reset in twrp but it didn't work.
So I restored the backup I did before flashing pixel experience.
And then my phone stuck on bootloop.
So I booted into fastboot mode and flashed the fastboot rom and it worked. I have successfully unbricked my device.
But now it shows "find device storage corrupted your device is unsafe now"
Everything works fine except I can't turn on find device and also can't install miui ota updates via twrp.
(And also when flashing twrp for the first time when I reboot it showed the stock recovery because I hadn't flashed disable dm-verify because when I am in twrp and try to mount my system to my computer my phone doesn't show up in the computer. So first I copied the disable dm-verify file then again flashed twrp then booted into twrp and then flashed disable dm-verify. I don't know if it is necessary to format data when flashing twrp. Maybe that's why the problem occured. I don't know.)
Please help.
Thank you.
Extract persist.img from official fastboot rom and replace the existing persist in Orangefox.
At least it helped me.
Persist.img flash through recovery gonna fix the problem but forget about Netflix and L1!!
Personally speaking had that problem with corrupted message pop up every time i reboot my device and when i flashed the persist.img through OrangeFox recovery i lost L1 forever (and there is no turning back).
If you wanna try that method i highly suggest you to Backup your Persist Partition first.
Yes, but isn't the original persist partition already lost, when you get the "storage corrupted" message?
Lucky-thirteen said:
Yes, but isn't the original persist partition already lost, when you get the "storage corrupted" message?
Click to expand...
Click to collapse
I tried may hours to define the problem's source but i think that's unclear in every situation. Others say that's a persist.img corruption while others had that problem with Mi Account corruption, etc.
Mine corrupted message came when i tried to flash Global Official MIUI in a EU variant device through normal process that doesn't engage any kind of Persist partition rewrite.
I had a backup of persist.img and flashed original from EU fastboot file and finally after that I repatch my old persist.img. The first time i did that process my device and L1 worked properly (even that spam message disappeared) but after a long time that I tried same process for same problem i completely lost my L1 [strange af!].
So, a safe process to try now is to flash back the official fastboot image of your variant (Erase + Lock [for L1]) through MiFlash tool and check that corruption message if it goes away (be careful to flash the correct fastboot image or you will get a a bricked device).
In conclusion it's Extremely advisable to keep a full backup of your partitions and especially Persist partition if you wanna flash Roms and generally unlock bootloader!
I use twrp recovery
I don't know about orange fox recovery
Strange51 said:
I use twrp recovery
I don't know about orange fox recovery
Click to expand...
Click to collapse
Always use OrangeFox for Lavender here is the link (download and test with latest R10.1_02-Stable)

Nokia x6.1 bootloops to twrp.

So it had been a while since I had tried getting into recovery twrp but I figured I could remember how so I did
fastboot flash boot twrp etc.img
This was a mistake according to the site here > https://twrp.me/nokia/nokia6_1.html
WARNING: If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
Click to expand...
Click to collapse
Which is exactly what I did
So now my phone is either stuck on the Nokia logo, or I can load twrp.
They provide some info on fixing it but I'm not sure I understand what they are saying. Can anyone help with this?
The phone was running Oreo (not sure which version unfortunately) and it was fully rooted and running magisk/xposed/su just fine before my mistake.
I don't have access to fastboot. Only Twrp and adb commands.
Edit, I can get to fastboot/download mode through the twrp terminal.
[SOLVED]
So I was able to use twrp to copy all of my internal files onto an sd card.
Then I set about getting this tool here > https://github.com/RaghuVarma331/Nokia-Tool the firmware specific to my phone, and modifying the bat file found here > https://github.com/RaghuVarma331/Nokia-Tool/blob/master/batscripts/Nokia-Tool-DRG-B2N-PL2-CTL.bat (because windows for some reason gave me a 16 bit application warning when I tried to use the tool exe)
My phone flashed a bunch of time and I was able to load up an almost entirely stock android 10, still capable of using magisk, edxposed, etc.
And now all there is to do is to get everything back onto it and set up which is at this point, the best case scenario.

Categories

Resources