The link for vbmeta_Mod-MT6761-10.img is here. The boot-oss-yesmagisk.img is a thread or two prior to the vbmeta link but do not use this image as it is no longer needed and since I've come across some issues with it. On a side note, Magisk is not working at this time. There has been much development work and progress with Magisk unfortunately a problem remains with the rooting on this device.
There is no harm in trying as you can always flash back a working boot.img in SPFT all by itselt however in my hunt for a working older versions of Magisk all fail to root so best to sit tight and hope for the best with the next update.
Did you happen to make a full backup image for each phone? It would involve using both WWR and SPFT. There is a link in an earlier post from jasonmerc on how to do this. The video is from a guy that goes by the name Hovatek.Thanks for this. Would be happy to wait around or be as a guinea pig (I have 2 of these phones laying around unused) as needed. I'll keep an eye on the thread for any requests.
We could always use a second oem image as there is only mine for testing. You would need to do a factory restore to make sure is clean then do a full image backup. No pressure though.I have not. For my purposes, there isn't much data on it to be worth backing up. I've using these to farm some beer money basically (play ads and earn some coin on it).
We could always use a second oem image as there is only mine for testing. You would need to do a factory restore to make sure is clean then do a full image backup. No pressure though.
Those two posts are for something else we were trying to get working.Do you want me to do this base on the yahoo stock rom or visible stock rom (both phones are visible phones, but the one i have been playing around with for the last few days has the yahoo stock rom loaded) or both stock roms?
I just did a quick search and can't seem to find a step by step instruction on how to do a full image backup. If you can point me to that, this is something I can do this weekend.
Edit: Is post 134 and 135 the right instructions using patcher-oss?
Those two posts are for something else we were trying to get working.
The instructional video link is here. I'd suggest watching the video at least once to get some idea of what it involves. Essentially after WwR generates a watered down version of the scatter file you will use it in SPFT to get three files off the phone and those are used to whip up the actual phone 's image using WwR. It's not difficult just time consuming.
It would be great to get both the Visible and Yahoo for second backups though I am more interested in the Visible. I know I may be asking a lot but if you run into any difficulties let me know.
If successful at creating an image it would be best to zip it and put it on the cloud like mediafire or something similar and link it here for all to have access.
Update: You can put the three dump files and final WwR generated scatter file for each phone on the cloud and I can generate the image. Generally try to make those available in a separate zip download. Don't put them in with the zipped images. Keep everything separate as the Visible and Yahoo files are different.
The scatter file for the Visible ROM is in the same folder where you got the image from. Look foryeah id be happy to have actually root to debloat. wasnt successful in my attempt... getting a new one waiting for it to shipp but have 2 others i dont want to mess with, hubbys and my standby that we use for various reasons... mine went fubar.. thought all the files are here in the thread... the last image i was given in this thread for visible works... will have to hunt hte scatter in this thread and it did work for me... the yahoo would load for a few minutes and then reboot and repeat for me... not sure why and never did get root...
idk every single time i flashed the yahoo one before i lost my imei somehow would reboot repeatedly... couldnt even get into setting before another reboot... was VERY unuseable for meThe scatter file for the Visible ROM is in the same folder where you got the image from. Look for
Scatter.zip. Inside that folder is the scatter file and 3 other files you would use to unpack the entire Visible OEM image from scratch. You load those into WwR and presto!
Also is unusual to hear the Yahoo image is unstable. I go back and forth between the Visible and the Yahoo at a blink of a bats eye. No issues that I can see.
Both Visible and Yahoo use the Verizon towers and the phone is specifically locked to each operator that provides the ZTE Blade A3 Prime. Let's go a step further. If you were to use a sim that is activated with Verizon the phone will not work as it is locked and can only work with the original carrier's sim. So basically either a Visible or Yahoo branded sim with either stock firmware loaded.just for ****s and giggles, for a visible phone with yahoo rom loaded. is that now locked to yahoo? it doesn't matter to me (I'm on Tmobile), but just curious how the phone is locked. I assume Visible locked their phones down upon shipment
This is quite strange that the Yahoo does that yet the Visible does not. Did you try to first format and afterwards load the image? It's possible you have a corrupt Yahoo image when you downloaded it. May want to re-download and try again.idk every single time i flashed the yahoo one before i lost my imei somehow would reboot repeatedly... couldnt even get into setting before another reboot... was VERY unuseable for me
i have no clue what WwR is lol never used it very leery with out a step by step and currently dont have a device im willing to play with.. they are cheap though so i might buy one with no service and mess with that one that way Im not in the position im currently in with no phone until the new one arrives as they wanted me to ship "defective" device back first...
Two observations from my own experience. First, when the phone is in bootloop there is no way that I have found to restore normal operation hence the need to FORMAT + Download. Second using the NvRam, NvData and NvCfg should be done only if you have an original NANDroid backup for your own phone otherwise it will restore the IMEI from another device and not the original one.Hi guys,
I warned jasonmerc a time ago about lost IMEI with FORMAT + Download or Firmware Upgrade in the SPFT.
Now I see one memeber here with that situation. Now you and other need know about how to prevent this discomfort in the future.
The scatter file have 3 partitions about NvRam, NvData and NvCfg. Each user can remove/backup these partitions with SPFT before any actions!
After that so you can make anything. If lost IMEI so reflashing that files the IMEI return.
I can help one member abut that process or search in the internet about IMEI backup with SPFT.
Agree. Yes! Each user SHOULD know how to do. Each device so each IMEI number.Two observations from my own experience. First, when the phone is in bootloop there is no way that I have found to restore normal operation hence the need to FORMAT + Download. Second using the NvRam, NvData and NvCfg should be done only if you have an original NANDroid backup for your own phone otherwise it will restore the IMEI from another device and not the original one.
Now every utility or app that claims to work on the MTK 6761 platform fails to work on the Blade A3 Prime as it is a read only file system and most of these utilities requires root. My guess is if you can root the phone you should be able to have access to input the correct IMEI info.
On a last note. If there is a way to restore from a bootloop on the Blade A3 Prime phone and not have to resort to doing a FORMAT + Download I'd like for someone to share those steps. There are exceptions but when you flash a magisk patch and the vbmeta filled with zeros and get bootloop you're stuck no matter what.
I tried 2 different versions of the MauiMeta and they did not work. The bootloader was unlocked and had the Orange state which is what you get once you do the fastboot flashing unlock. Will retry on a clean flash and no unlocking.Agree. Yes! Each user SHOULD know how to do. Each device so each IMEI number.
Unfortunately some 32 bits devices has a problem with very tools at the moment.
You can test MauiMETA (ModemMETA) DOWNLOAD the tool with your device.
But as I know so 3~5 devices with same 32 bits cannot solving IMEI with that GREAT tool.
So I help ZTE A7 2020 device & users with restoring IMEI for him. But need IMEI number original and TWRP. That's need time and time.
In Blade A3 Prime (Visible) is not different. But all security is need!
A10 for NvRam, NvData and NvCfg files haven't logical partition!
Yeah! MTK device can backuped with SPFT and obvius each file/partition too.
Well, write instructions for new members about IMEI and if need using FORMAT option. So more security has after with that's files (NvRam, NvData and NvCfg) backuped.