Database Users

{DEV}[ThinkTank] Getting ZIPs to Flash

Ok, as many of you know, the only thing between custom ROMs and your phone is the fact that we can not get the ROMs that we make to flash correctly in our current CWM recovery. We either get status 0, status 1, status 6, or status 7 errors when flashing. Most of these errors directly correlate with the boot.img command line(s) in the updater script.
uoY_redruM and I have spent over ten hours a piece trying to figure this out and have made progress but are still stuck.
We soon found out that the kitchens we were using to cook our ROMs did not have the latest directory for our phones partitions and their addressess (mmcblk0p1, etc.) This directed us to where we need to look to fix this.
The critical partitions we need to make ROMs flash are
1. Data
2. System
3. Boot
4. Cache
5. (optional) SDCard
It was easy enough to find 1,2, & 4, however the boot was a little bit trickier.
There are drives on our phone that had the following IDs:
1. mmcblk0p5 aboot
2. mmcblk0p7 boot
3. mmcblk0boot1 disk
4. mmcblk0boot0 disk
We believe that the real boot partition is 7, however we have yet to get a fully functional ROM up and running, despite writing the boot.img to p7.
With certain modifications to the boot.img lines in the updater script, I have been able to flash a ROM, but upon boot I lose SU permissions and the radio is borked (does not detect SIM card). Clearly this is still not functional and is caused by the boot.img (kernel) not being included in the ROM.
Attached is a scanned copy of a list of all of the partitions in our phone, along with their ID.
This is a thread where we can easily bounce ideas off of each other and hopefully get to the root of this problem ASAP.
Let's please keep this on topic. Thanks.

Status 7 is updater-script which means ur close I'm pretty sure or the Recovery needs to be remade for our phone like I said before.

Reviewers said:
Status 7 is updater-script which means ur close I'm pretty sure or the Recovery needs to be remade for our phone like I said before.
Click to expand...
Click to collapse
Yeah, we're starting to think it's recovery related.
We've (well most he) got the ROM to boot up now....but......and that's a big but.....it reads as if we have no SIM card. So, that's where we're currently stuck.

Same place boots loads kernel but no root or radio same sim card error

Wildchld said:
Same place boots loads kernel but no root or radio same sim card error
Click to expand...
Click to collapse
Are you using an insecure boot.img?

FiveOhFox said:
Are you using an insecure boot.img?
Click to expand...
Click to collapse
yep
Built in the kitchen
---------- Post added at 06:46 PM ---------- Previous post was at 06:41 PM ----------
I think it maybe the recovery too because I have lost root on restores

Wildchld said:
yep
Built in the kitchen
Click to expand...
Click to collapse
Ok. I'm trying it with secure boot.img files to see if that has any bearing on our results but so far nothing.
Ok well I'm going to shelf working on the script for a while and instead start working on my ROM and possibly learning how to make a recovery lol.

It's the recovery then.
We need a recovery made for our phone, should have listened to my thread of what I said.
Oh well, we just need somebody to work on a Recovery.
Wish I could help but I don't know ANYTHING about compiling a recovery.

Reviewers said:
It's the recovery then.
We need a recovery made for our phone, should have listened to my thread of what I said.
Oh well, we just need somebody to work on a Recovery.
Wish I could help but I don't know ANYTHING about compiling a recovery.
Click to expand...
Click to collapse
Why are you so adamant that it's the recovery?? You don't even own the phone!

I owned the amaze before and it didn't flash with 1 recovery but it worked on another.
I know this is Samsung but another user is agreeing with me as well.
Read the thread I made in General.
Flashing something from another phone will never work 100% as made for that phone.
---------- Post added at 01:24 AM ---------- Previous post was at 01:23 AM ----------
Plus when I get the phone I'll look into it as well.
I might not be much help in this area but I'll do what I can.

Anybody have any insight?
We've about hit our ceiling. I know I have for sure, I think Five still has some tricks up his sleeves somewhere
Using his updater-script we can get a boot but no radio. My thought is the radio isn't flashing properly (maybe a corrupt img file?) or it's not mounting properly somewhere?
Also, if you look at the International Galaxy SIII ROMs, some of them have flash_image, modem.bin and recovery.bin in their update script and the updater-script points to them to be written. That leads me to believe perhaps we have to make the radio flash...I'm just spit balling here. Also, the modem.bin files in the international ROM kind of makes me think there is a file missing somewhere in ours.
I pulled the system.4ext.tar/boot.img rom our ROM and used Cygwin kitchen to build it fresh, replaced the updater-script with Five's, got a boot and no radio. If I replace the updater-script with the one from the International ROM (and change the mount points in the script) I get Status 6 error.
Anybody have an opportunity to look at this, or maybe has experience in fixing this, speak up please!!
Another ~10 hours put into this today and no farther then yesterday

uoY_redruM said:
Anybody have any insight?
We've about hit our ceiling. I know I have for sure, I think Five still has some tricks up his sleeves somewhere
Using his updater-script we can get a boot but no radio. My thought is the radio isn't flashing properly (maybe a corrupt img file?) or it's not mounting properly somewhere?
Also, if you look at the International Galaxy SIII ROMs, some of them have flash_image, modem.bin and recovery.bin in their update script and the updater-script points to them to be written. That leads me to believe perhaps we have to make the radio flash...I'm just spit balling here. Also, the modem.bin files in the international ROM kind of makes me think there is a file missing somewhere in ours.
I pulled the system.4ext.tar/boot.img rom our ROM and used Cygwin kitchen to build it fresh, replaced the updater-script with Five's, got a boot and no radio. If I replace the updater-script with the one from the International ROM (and change the mount points in the script) I get Status 6 error.
Anybody have an opportunity to look at this, or maybe has experience in fixing this, speak up please!!
Another ~10 hours put into this today and no farther then yesterday
Click to expand...
Click to collapse
If you use the update-binary from the EU rom the status 6 error goes away but same results but the kernel will load. Status 6 error is a syntex error not because of the script but the binary is looking for different parameters.
Also I see no Sprint roms being dev maybe they have the same problem
One last shot before work... Attached is a working script and binary
Rom boots fine and about shows baseline unknown so maybe we need to load the radio in the rom also.
Also when I restore a nandroid radio comes back but won't connect till I turn off wifi then service returns.

Here's the thing I found odd....
If you use CWM to pull a backup, the boot.img/recovery.img are both 10MB in size.
If you use the Toolkit to pull a backup, the boot.img/recovery.img are 2MB/512KB.
Why is that? That doesn't make any sense to me. They should be duplicate but they're not.
....the only thing that comes to mind is maybe the Toolkit (since it was designed for the international phone) points to different partition points and aren't pulling the correct files? Then again, why would they be named properly?
That's where I'm at for today.

OK, could have a problem.
I ran it with your updater-script and it booted up like you said with no radio. However, when I turned it off and tried to get back into recovery, I keep getting put into Odin. It appears my recovery was overwritten? I can boot the phone back up but I cannot restore my working Nandroid now *yikes*
Got to figure this one out...
Yeah, that's exactly what happened. I can't get into recovery now. Need to figure out how to flash the recovery back.
In the mean time, my phone is useless. At least it boots up but I have no radio...
EDIT-
Fixed. Re-ran Odin/CWM Install. We're good.
Now I know the recovery.img I pulled from the backup is bad! That's the recovery I had it flash and ended up with no recovery. Hmmmm...

uoY_redruM said:
OK, could have a problem.
I ran it with your updater-script and it booted up like you said with no radio. However, when I turned it off and tried to get back into recovery, I keep getting put into Odin. It appears my recovery was overwritten? I can boot the phone back up but I cannot restore my working Nandroid now *yikes*
Got to figure this one out...
Yeah, that's exactly what happened. I can't get into recovery now. Need to figure out how to flash the recovery back.
In the mean time, my phone is useless. At least it boots up but I have no radio...
EDIT-
Fixed. Re-ran Odin/CWM Install. We're good.
Now I know the recovery.img I pulled from the backup is bad! That's the recovery I had it flash and ended up with no recovery. Hmmmm...
Click to expand...
Click to collapse
You used the recovery.img from what, again? And the script posted above writes to p18 which is recovery so that's not a problem.
So it boots but is missing radio? Do you have root?

I used the above script and binary it boots and loads the kernel and recovery fine and everything works but no root or radio. I have not tried removing the boot and recovery but don't think that will make a diff. I will try tonight. Also will pull boot and recovery from my working nandroid to see if that works.
Sent from my SGH-T999 using Tapatalk 2

Wildchld said:
I used the above script and binary it boots and loads the kernel and recovery fine and everything works but no root or radio. I have not tried removing the boot and recovery but don't think that will make a diff. I will try tonight. Also will pull boot and recovery from my working nandroid to see if that works.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Be careful when you do that. I included the recovery.img from the Nandroid in the root of the zip and that's what caused me to not be able to access recovery (I had to re-flash recovery using Odin).

Wildchld said:
I used the above script and binary it boots and loads the kernel and recovery fine and everything works but no root or radio. I have not tried removing the boot and recovery but don't think that will make a diff. I will try tonight. Also will pull boot and recovery from my working nandroid to see if that works.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Ok. We are adding files and commands to flash the modem.bin that Rum pulled from his phone to see if that fixes radio issues.

uoY_redruM said:
Be careful when you do that. I included the recovery.img from the Nandroid in the root of the zip and that's what caused me to not be able to access recovery (I had to re-flash recovery using Odin).
Click to expand...
Click to collapse
Lol your right but i have loaded this nandroid like 30 times i know its good
Sent from my SGH-T999 using Tapatalk 2

FiveOhFox said:
Ok. We are adding files and commands to flash the modem.bin that Rum pulled from his phone to see if that fixes radio issues.
Click to expand...
Click to collapse
Found a few more files that could be of use. Five is writing up some commands to try flashing them.
I'm starting to feel really good about today!

[STOCK] VERIZON Nexus 6 [5.1][LMY47E] Firmware Image

For anyone interested here is the firmware image for Verizon Nexus 6 [5.1] [ LMY47E].
VRZ_XT1103_5.1_SHAMU_LMY47E_release-keys_subsidy-default_CFC.xml.zip
http://www.filefactory.com/file/12c...Y47E_release-keys_subsidy-default_CFC.xml.zip
Nexus 6 Firmware Folder
http://www.filefactory.com/folder/74e3c3d68254b075
This where I upload my stuff so sorry if I offend anyone for doing so.

So the difference in between whats out there and this is? I'm curious as the build is different.

coldconfession13 said:
So the difference in between whats out there and this is? I'm curious as the build is different.
Click to expand...
Click to collapse
Not sure what's actually different but the build number is different, LMY47D vs LMY47E.

Could this be flashed with twrp without losing custom recovery?
Sent from my Nexus 6 using XDA Free mobile app

Hopefully we will find out if there are any significant changes or additions. I really hope that I do not need to follow a Verizon firmware through the life of this phone. I hope that there is nothing meaningful in the E version.

Not positive as I am just downloading it, but pretty sure it is the factory image for the Nexus 6 for VZW so I imagine it will remove root and probably custom recovery.
But the nice thing about the Nexus 6 is that you are NOT tied to your carrier's firmware/ROM's for it. Unlike previous phones, there are only two versions, US and International. So we don't have to worry if 'x ROM' is for the T-Mobile version, the Sprint version, etc., etc.

Well no worries this all but confirms vzw is rootable and unlockable

Anyone Flash this yet?
Has anyone flashed this yet...very interested how you went about it and what the results are.....thx

Is there a rooted version??

Parsing the image filename
coldconfession13 said:
So the difference in between whats out there and this is? I'm curious as the build is different.
Click to expand...
Click to collapse
Also waiting another few hours for download to complete. In the mean time, just parsing all the attributes of the file name:
LMY47E: Newer than LMY47D, which is explicitly called 5.1.0 on the Nexus Factory Image page (not the usual numbering convention, which would be 5.1; possibly foreshadowing that they know 5.1.1 is hot on its heels)
release-keys: signed by Google
subsidy-default: Includes parameters that resets the SIM Lock on the radio to "default" status, which we assume is factory-unlocked.
CFC: any idea what means?
I would assume this also gives us an image for the /oem partition

Judging by the name this was made on the same day as the image on Google's website, so it is very unlikely that there are major changes.

Nexus 6 subsidy lock config
@autoprime:
1. Does the contents of the included slcf_rev_b_default_v1.0.nvm look like plain QMI commands to you?
2. Do you still have a user-friendly one-click tool that can send DFS commands to a device in diag mode?

How to Flash
Maybe a dumb question... but can this be TWRP flashed (I thinking no) or is there some other method? I was thinking this was a standard recovery image that could be flashed in stock recovery?? Other than that, I am not sure... if anyone has success flashing let me know!
edit...
duh.... ok sorry... my bad for not looking into the zip.... I see the flash all .bat

mahst68 said:
Maybe a dumb question... but can this be TWRP flashed (I thinking no) or is there some other method? I was thinking this was a standard recovery image that could be flashed in stock recovery?? Other than that, I am not sure... if anyone has success flashing let me know!
Click to expand...
Click to collapse
I believe you will need the Motorola Fastboot tool (mfastboot) to flash this in the motoboot mode. You can get it from the MotoDev site, or search on the forums. Note that this is NOT the same as the standard fastboot that ships with the Android SDK (which will also work with the Nexus 6, but not with this particular zip file).

Did It!!!
DA6030 said:
I believe you will need the Motorola Fastboot tool (mfastboot) to flash this in the motoboot mode. You can get it from the MotoDev site, or search on the forums. Note that this is NOT the same as the standard fastboot that ships with the Android SDK (which will also work with the Nexus 6, but not with this particular zip file).
Click to expand...
Click to collapse
As described, used mfastboot... flashed each individual image file based on the steps in the flashfile.xml!!! Booted up everything real nice.... download myverizon and voicemail as soon as I went through initial setup.... rooting now!!! :good:
bootloader remained unlocked the whole time!!!!

mahst68 said:
As described, used mfastboot... flashed each individual image file based on the steps in the flashfile.xml!!! Booted up everything real nice.... download myverizon and voicemail as soon as I went through initial setup.... rooting now!!! :good:
bootloader remained unlocked the whole time!!!!
Click to expand...
Click to collapse
Does the firmware seem configured for VZW? VZW ringtones and boot animation and the like? Or does it appear like something that Google will drop on us in the near future? I wonder if it will ever hit the factory images page?

elreydenj said:
Does the firmware seem configured for VZW? VZW ringtones and boot animation and the like? Or does it appear like something that Google will drop on us in the near future? I wonder if it will ever hit the factory images page?
Click to expand...
Click to collapse
only thing Verizon really are the 2 app downloads.... everything else is the same... not boot animations nothing. Root and TWRP setup worked fine as well.... Not going to relock bootloader though... I know the horror stories of Hard Bricks.... Not going to take off force encrypt either.... was having trouble with the phone wanting to go bootloopy with the regular image from google when I made it force before... I will let everyone know bugs and post some pictures as well once I set it up fully!! :highfive:

mahst68 said:
only thing Verizon really are the 2 app downloads.... everything else is the same... not boot animations nothing. Root and TWRP setup worked fine as well.... Not going to relock bootloader though... I know the horror stories of Hard Bricks.... Not going to take off force encrypt either.... was having trouble with the phone wanting to go bootloopy with the regular image from google when I made it force before... I will let everyone know bugs and post some pictures as well once I set it up fully!! :highfive:
Click to expand...
Click to collapse
Question: I think I may have been under the same circumstances as you. I am rooted, with TWRP, and bootloader unlocked. I am however, running a custom rom (5.0.1 encrypted). I won't be relocking the bootloader. What steps (if you are able to provide them) should I take to achieve 5.1 with bootloader still locked and then root and install TWRP. (Please keep in mind I a have not had a Nexus device since the very first one).
Edit: I am on VZW network but Google Play Store Nexus 6.
TIA

Will do... I am still setting up the phone. Once I complete it and make sure it works fine for a little bit then I'll post. Don't want to cause any issues that might lead to someone bricking their phone

Initial observations
DA6030 said:
LMY47E: Newer than LMY47D, which is explicitly called 5.1.0 on the Nexus Factory Image page (not the usual numbering convention, which would be 5.1; possibly foreshadowing that they know 5.1.1 is hot on its heels)
Click to expand...
Click to collapse
System partition looks complete, but I won't have time to do a diff between the two until next week. But by then, we might have an official changelog.
DA6030 said:
subsidy-default: Implies there's something within this file that sets the SIM Lock parameters on the radio? Extracting that could be very interesting to AT&T and Sprint customers.
Click to expand...
Click to collapse
I don't have an AT&T device to test, but applying this file certainly attempts to set the SIM lock to it's default factory-unlocked state. But it's also possible the radio firmware could reject the unlock commands if it has been previously locked by a carrier. Only way to know is to test.
DA6030 said:
I would assume this also gives us an image for the /oem partition
Click to expand...
Click to collapse
There is an oem partition file within the zip, but it's literally just the string "Hi, Fly Guy". Just open oem.img with a text editor to see it. I cannot imagine that is a valid ext img file, so I'm shocked that it was able to be flashed. If so, that would suggest that the Verizon devices will ship with no unique customizations (e.g., bootanimation, ringtones, that cannot be removed without root), and has a sense of humor.
---------- Post added at 10:39 AM ---------- Previous post was at 10:32 AM ----------
mahst68 said:
As described, used mfastboot... flashed each individual image file based on the steps in the flashfile.xml!!!
Click to expand...
Click to collapse
@mahst68, did you flash only the image files, or also the subsidy_lock_config file (slcf....nvm)? What mfastboot command did you use to send the slcf? What was the response did you get back from that command? And when you flashed the oem.img what response did you get back?

EFIDroid

Just wondering if anyone has looked into this, and what it could possibly mean for our device if we could be merged. Apparently there's no need for special kernel modules, bootloader edits, or KEXEC, and I think it would be pretty cool to be able to use multi ROM to boot back and forth between stock and AOSP.

Why don't you explain what this is and provide a few links?

lafester said:
Why don't you explain what this is and provide a few links?
Click to expand...
Click to collapse
https://www.xda-developers.com/efidroid-is-a-second-stage-bootloader/
This article was the first I'd heard of it. But it does seem like it might be something easy to implement. It's basically multi ROM, but without all the requirements.

Looks interesting.

is it possible to dualboot into that one OS called sailfish or something? even ubuntu mobile?

gecko702 said:
is it possible to dualboot into that one OS called sailfish or something? even ubuntu mobile?
Click to expand...
Click to collapse
This is to make the phone able to boot two different working roms. Say, you will be able to boot stock or RR without changing roms in TWRP. It won't boot roms that haven't been ported to our phone...

This is very, very interesting. I love the thought of just using LineageOS or RR for everyday things and then just switching to stock when I want to use media and enjoy the fantastic sound.
I'm not a developer, but I'd like to help/contribute in any way possible if someone's working on bringing unofficial support to the Axon 7.

jimbo77 said:
This is to make the phone able to boot two different working roms. Say, you will be able to boot stock or RR without changing roms in TWRP. It won't boot roms that haven't been ported to our phone...
Click to expand...
Click to collapse
Very true. However, it makes ROMs easier to port and for more people to test, as then people can try them out without wiping their phone each time they want to try.

I was able to port and build right up until the last step where you generate lk.img and fastboot it to the phone. I'm running Linux inside a virtual machine and it doesn't seem to want to communicate, though adb does work.
I might try on the weekend to boot linux off a hard drive and see if it will work..
In the mean time, if someone else wants to try to build, it's really simple just follow these two guides:
https://github.com/efidroid/projectmanagement/wiki/[EFIDroid]-Getting-Started
https://github.com/efidroid/projectmanagement/wiki/[EFIDroid]-Porting-a-new-device

I tried again, but when I fastboot the generated lk.img to the phone, it just turns off instead of loading the splash screen.
I used the TWRP recovery .img for the create_device step. Maybe that's unacceptable, though it built the lk.img without error.
Anyone else trying this?

twoi said:
I tried again, but when I fastboot the generated lk.img to the phone, it just turns off instead of loading the splash screen.
I used the TWRP recovery .img for the create_device step. Maybe that's unacceptable, though it built the lk.img without error.
Anyone else trying this?
Click to expand...
Click to collapse
Did you try this fix for arm64 devices?
https://github.com/efidroid/projectmanagement/issues/89
Seems you need to dump aboot to check what's the correct address for LK to boot.
Edit: also did you try using freeza Beastmode boot.img? Probably that's better

Thanks for the reply.
I dumped aboot and replaced the address but sadly it just makes the phone reboot, I used the beastmode boot.img at the same time.
I'm a bit in over my head at this point hah, but someone in that thread had the same results..

twoi said:
Thanks for the reply.
I dumped aboot and replaced the address but sadly it just makes the phone reboot, I used the beastmode boot.img at the same time.
I'm a bit in over my head at this point hah, but someone in that thread had the same results..
Click to expand...
Click to collapse
Yeah that's he creator of Efidroid... Why don't you reply to that issue tracker and add the Axon 7 to the list of devices that don't boot because of the arm64 arch

twoi said:
Thanks for the reply.
I dumped aboot and replaced the address but sadly it just makes the phone reboot, I used the beastmode boot.img at the same time.
I'm a bit in over my head at this point hah, but someone in that thread had the same results..
Click to expand...
Click to collapse
yes you are on right track

twoi said:
Thanks for the reply.
I dumped aboot and replaced the address but sadly it just makes the phone reboot, I used the beastmode boot.img at the same time.
I'm a bit in over my head at this point hah, but someone in that thread had the same results..
Click to expand...
Click to collapse
have you replied or keep track of this
https://github.com/efidroid/projectmanagement/issues/89
the dev was asking for something

Druboo666 said:
have you replied or keep track of this
https://github.com/efidroid/projectmanagement/issues/89
the dev was asking for something
Click to expand...
Click to collapse
I'll try the suggestion of using lk_origdtb.img. I'll have to ask about his instructions to rebuild lk.img, I'm not sure how to repack it.
This might get me close http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
But this is lower level than I'm used to, I'm not sure which file(s) constitutes the ramdisk.

twoi said:
I'll try the suggestion of using lk_origdtb.img. I'll have to ask about his instructions to rebuild lk.img, I'm not sure how to repack it.
This might get me close http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
But this is lower level than I'm used to, I'm not sure which file(s) constitutes the ramdisk.
Click to expand...
Click to collapse
you should contact with the dev he may help you OP3 and A7 got same chipset so yeah it will help

I tried lk_origdtb.img and the repacked lk.img (Image.gz-dtb) but got the same results, device reboot.
I would love someone else to try this. If you have linux and coding experience at all I think you could manage building it.

twoi said:
I tried lk_origdtb.img and the repacked lk.img (Image.gz-dtb) but got the same results, device reboot.
I would love someone else to try this. If you have linux and coding experience at all I think you could manage building it.
Click to expand...
Click to collapse
you can contact @npjohnson or @m1cha with your compiled LK or boot maybe they can help
as they have fix Nexus 6P LK with no uefi boot

[SOFTWARE UPDATE] A2017U - B35 Rolling out

Software Update: Axon 7 (A2017U) owners... Within the next 48 hours, an update will bring a security patch to your device. Bluebourne and KRACK vulnerabilities will be remedied with this patch.
https://community.zteusa.com/discussion/52369/software-update-axon-7-a2017u-now-on-b35

DrakenFX said:
Software Update: Axon 7 (A2017U) owners... Within the next 48 hours, an update will bring a security patch to your device. Bluebourne and KRACK vulnerabilities will be remedied with this patch.
https://community.zteusa.com/discussion/52369/software-update-axon-7-a2017u-now-on-b35
Click to expand...
Click to collapse
Which is the patch date? G B09 has the December 1 patch, just wanted to know which one fixes this stuff

Can someone provide a B35 update zip? It's no issue for me to connect to Wi-Fi to install it, but I like to keep offline cached copies of files for recovery purposes, so that I can update even without Internet.
Thanks!
Edit: I have A2017U.

When will the B35 firmware will be available as flashable TWRP zip across a2017 devices?Does it have a improved battery life?

Predatorhaze said:
When will the B35 firmware will be available as flashable TWRP zip across a2017 devices?Does it have a improved battery life?
Click to expand...
Click to collapse
As soon as you make one?
Pretty sure it's available now. Let us know how the battery life is.

I know I asked before, but if someone can post a direct URL link to the B35 update file (whether it be a zip or something else) then it would be much appreciated. I know @DrakenFX released a system and bootstack zip, but I would rather use official files. I can't save an offline copy of the file since I'm not currently rooted, I suspect it is stored in the /cache partition. The file size is close to 700MB. I just want a copy for offline use. Maybe someone with root can capture a copy of the file after it has downloaded, but before the phone reboots to apply it. Or maybe the URL can be sniffed with WireShark or whatever. A B35 full OTA zip is better, but ZTE hasn't posted an SD card update download on the zteusa.com website yet.
Thanks!

I was able to grab the B35 update zip without rooting. I let the updater download the file, then quickly powered off the phone before it had a chance to reboot and install. Then I booted into EDL mode, and used @tennear's Axon7Tool to write TWRP. From TWRP I went to /data/data/com.zte.zdm/files, and grabbed a file called fota_update.zip. Then I reflashed the stock recovery with Axon7Tool, and installed the zip. All went fine. I suspect you can grab any OTA zip this way. Maybe I'll upload a copy of the file later.

If there's any interest in a B35 SL!M➀ aroma-version let me know

raystef66 said:
If there's any interest in a B35 SL!M➀ aroma-version let me know
Click to expand...
Click to collapse
Yes, sir! Very interested in flashing the update through TWRP while maintaining the advantages of stock for the hardware on board.

raystef66 said:
If there's any interest in a B35 SL!M➀ aroma-version let me know
Click to expand...
Click to collapse
I run Apex Launcher & Magisk on the A2017U Stock, cutomized with a ton of stuff frozen & one of @warBeard_actual's mod. It would be nice to have the Aroma power and ability to "thin" things out. Thanks!

amphi66 said:
I run Apex Launcher & Magisk on the A2017U Stock, cutomized with a ton of stuff frozen & one of @warBeard_actual's mod. It would be nice to have the Aroma power and ability to "thin" things out. Thanks!
Click to expand...
Click to collapse
I think you're referring to this one ?
In general, did you see quite some difference before and after ?
You can PM for the tons of frozen stuff you like to get rid off. Think i might work on it these days to have some fun :cyclops:

raystef66 said:
I think you're referring to this one ?
In general, did you see quite some difference before and after ?
You can PM for the tons of frozen stuff you like to get rid off. Think i might work on it these days to have some fun :cyclops:
Click to expand...
Click to collapse
Yes. I downloaded those 'init' files way back last Spring & found them more effective (at least impression-wise) than the AKT stuff. His "Conservative" mod helps w/ battery w/o a noticeable performance hit.
Early on I found the A7 was not happy when some apps were removed & replaced, but functioned OK if they were kept frozen & then replaced. Fortunately there is enough storage & memory that inefficiency does not (so far) cause issues. Sort of like the legacy SubStratum which could (sort of) work as long as system apps were excluded.
I look forward to your "hobby". Thanks

hi.
if i upgarde my A2017u directly from setting>update on my phone, i loose root and twrp or not?

redhou said:
hi.
if i upgarde my A2017u directly from setting>update on my phone, i loose root and twrp or not?
Click to expand...
Click to collapse
If you are using TWRP and/or are rooted, that setting>update will fail due to modified system files. READ & follow directions in post #2 HERE. Data will be saved & TWRP will be upgraded (if req'd).

davisml said:
Yes, sir! Very interested in flashing the update through TWRP while maintaining the advantages of stock for the hardware on board.
Click to expand...
Click to collapse
amphi66 said:
I run Apex Launcher & Magisk on the A2017U Stock, cutomized with a ton of stuff frozen & one of @warBeard_actual's mod. It would be nice to have the Aroma power and ability to "thin" things out. Thanks!
Click to expand...
Click to collapse
Working on it Was harder then our G version stocksystem to make it boot with aroma. Really weird stocksystem...
But i succeeded. Having bootloader changed, twrp build-in and seperate modems, bootanimation changed, build-in battery tweaks, magisk, supersu, fasterUI....all ok now. Just adding some other stuff in next days. Hope to release it in the weekend :cyclops:

amphi66 said:
If you are using TWRP and/or are rooted, that setting>update will fail due to modified system files. READ & follow directions in post #2 HERE. Data will be saved & TWRP will be upgraded (if req'd).
Click to expand...
Click to collapse
the download file start with no probleme using setting>update. i had stoped it.
can i continu ? i had a lot of difficult before root my phone in past and i don't like to loose it

redhou said:
the download file start with no probleme using setting>update. i had stoped it.
can i continu ? i had a lot of difficult before root my phone in past and i don't like to loose it
Click to expand...
Click to collapse
It will download, but the install will simply fail as it checks the system files, but certainly you are free to do as you wish. Good Luck!

raystef66 said:
Working on it Was harder then our G version stocksystem to make it boot with aroma. Really weird stocksystem...
But i succeeded. Having bootloader changed, twrp build-in and seperate modems, bootanimation changed, build-in battery tweaks, magisk, supersu, fasterUI....all ok now. Just adding some other stuff in next days. Hope to release it in the weekend :cyclops:
Click to expand...
Click to collapse
Uploading A2017(U)(N-B35)_AROMA_SL!M¹_DF!NR now Preparing a seperate thread on ROM section. Keeping you updated when ready :good:
EDIT : DONE ! LINK

hi, i am installing the new OTA update but it when my restarts TWRP asks for password to mount and doesn't allow me to install this new OTA update. I entered my phone password which said it decrypted the pkg but then it only opens the TWRP GUI. I tried to install the zip manually but it said it failed.
How can I let the phone install it without TWRP interfering?
Thanks a lot.

lachdanan said:
How can I let the phone install it without TWRP interfering?
Click to expand...
Click to collapse
You can't. Use stock recovery if you insist on OTA, or use DrakenFx's zips to flash from TWRP. The latter is much more convenient.

Anyone with a TWRP flashable stock rom for MetroPCS xt1765 Perry Qualcomm

Unfortunately all the TWRP flashable roms from GetOffMyLawn&!+¢#{$ are dead and I need the stock rom for the MetroPCS variant. Anyone know where I can find it?

I think I mostly got to where I needed to go with the stock factory roms without using TWRP. After attempting and failing to make a flashable rip with Android Kitchen, I read about and saw a video on RSD Lite here youtube.com/watch?v=njXQYn53SPc (sorry can't hyperlink since my post count) It basically just quickly shows what it should look like and how it should work IF it works once setup. But it was good enough. The images I had were giving me failing to flash gpt and bootloader errors. So I manually took those complete lines out of both the flashfile.xml and the Servicefile.xml. After that it flashed everything and rebooted. To my surprise I'm not bricked and back on stock. I had to go back to enable Device Carrier Unlocking through the metropcs app (oops). Now I have to probly unlock the bootloader and root again but this time I'll make that backup
But if anyone has the flashable zips, a new upload would be nice for others.

unrooty said:
I think I mostly got to where I needed to go with the stock factory roms without using TWRP. After attempting and failing to make a flashable rip with Android Kitchen, I read about and saw a video on RSD Lite here youtube.com/watch?v=njXQYn53SPc (sorry can't hyperlink since my post count) It basically just quickly shows what it should look like and how it should work IF it works once setup. But it was good enough. The images I had were giving me failing to flash gpt and bootloader errors. So I manually took those complete lines out of both the flashfile.xml and the Servicefile.xml. After that it flashed everything and rebooted. To my surprise I'm not bricked and back on stock. I had to go back to enable Device Carrier Unlocking through the metropcs app (oops). Now I have to probly unlock the bootloader and root again but this time I'll make that backup
But if anyone has the flashable zips, a new upload would be nice for others.
Click to expand...
Click to collapse
Send me an untouched stock system.img, boot.img, and oem.img and I'll compile you a TWRP flashable ROM. If you're not sure how to dump partition images, the best way is to download an app called Partition Backup & Restore. It's a free app and was created by an XDA dev @wanam.

Hey, thanks for the offer. I'll do it. I have the img files that you need ripped and rared. Just been having some connection issues today while attempting to upload the file. I don't know how I should upload it so I'm going to use my google drive and share the link with you either here or by PM if I can't link it here due to the spam protection. Hopefully I'll have it to you within the next day if my connection becomes stable enough to upload.

https://drive.google.com/open?id=1x65mPUAWWm1heQsDRpgm6QYnyyOIp8P5
Here you are MotoJunkie01, I decided to keep the extended name on the file to show exactly what Partition Backup and Restore spit out should there be something different that's needed.

unrooty said:
https://drive.google.com/open?id=1x65mPUAWWm1heQsDRpgm6QYnyyOIp8P5
Here you are MotoJunkie01, I decided to keep the extended name on the file to show exactly what Partition Backup and Restore spit out should there be something different that's needed.
Click to expand...
Click to collapse
I made one yesterday. Read my guide carefully. Have fun. https://forum.xda-developers.com/mo...-stock-rom-t3777830/post76234878#post76234878

Quite the write up there, thank you for it it's very informative. But to be fair flashing through RSDLite it working for me so I suppose I'll stick with it. It seems more straightforward afaik.

unrooty said:
Quite the write up there, thank you for it it's very informative. But to be fair flashing through RSDLite it working for me so I suppose I'll stick with it. It seems more straightforward afaik.
Click to expand...
Click to collapse
Good choice. I, personally, don't see how that's a better option than just rsdlite. But to each his, or her, own. If you need no verity, magisk, and all the basics anyway, why not just flash the stock firmware. No risk involved.

unrooty said:
Quite the write up there, thank you for it it's very informative. But to be fair flashing through RSDLite it working for me so I suppose I'll stick with it. It seems more straightforward afaik.
Click to expand...
Click to collapse
Yep - seems a better choice. RSD Lite isn't the friendliness beast but it's not a bad ride once you understand the idiosyncrasies.