Database Develop

[ROM][TW][RB1][KitKat][4.4.4] FyrestoneROM [SM-T113][27 July 2018]

FyrestoneROM T113​The simplicity of TouchWiz system without superfluous​
Code:
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
Introduction:
This Rom is the stock samsung without annoying apps and with some tweaks made to make your life easier.
I have a lot to do for make it better, but I hope you appreciate my work, if you don't thanks for giving me a chance.​
Features:
Based on T113XXU0ARB1
Debolated - Samsung and Google apps (350 MB of useless apps)
Deodexed
Zipaligned
Faster animation scale
Knox Free
Removed boot sound
Rooted with SuperSu
Busybox
Sony System signature - Feel free to install sony apps from play store!
AOSP Keyboard
Removed Samsung Update
Allow apps access to external storage
Removed Loud volume warning
Cyanogen/LineageOS UI sounds
Tweaks:
Battery Tweaks
Better scrolling
Video acceleration and HW debugging
Better RAM management
Google DNS
Download Link:
DOWNLOAD​MD5: b7694314c6cfe88f013522b86319210d
Old version [4 Feb 2017]: DOWNLOAD
MD5: 283aa300c00ae227b4362945925db4b4
Old version [4 Jan 2017]: DOWNLOAD
MD5: 6f97e788b0b2571742b256e6fcaf1e86
How to install The Rom:
Update your bootloader and baseband to XXU0ARB1 before flash!
1. Flash TWRP 2.8.7.0.tar with Odin 3.12.10.
2. Flash TWRP 3.0.2-0.img inside the recovery (Select Install image and choose Recovery partition).
3. Reboot into TWRP 3.0.2-0.
4. Copy FyrestoneROM_T113_XXXXX.zip in your SD Card.
5. Wipe: System, Data, Cache and Dalvik.
6. Optional – Wipe Internal Storage.
7. Install FyrestoneROM_T113_XXXXX.
8. Reboot and wait about 10 minutes.
How to install The Firmware:
1. Download and extract a zip file containing your desired firmware.
2. Open Odin Tool.
3. Boot your device in the "Download Mode":
(Press Volume Down, Power and Home buttons at same time for 5-8 seconds until download mode is active.)
4. Connect your device to PC via the USB cable while in download mode.
5. Next, check the "Auto Reboot" and "F. Reset Time" options in Odin Tool.
6. Hit the AP/PDA button then browse and select a tar.md5 file from the extracted folder.
7. Finally press the start button to begin flashing the firmware update on your device.
Credits:
Google for Android OS
Samsung for FW and source
Sony for System signature
Cyanogenmod for File manager
@SuperR for the kitchen
@bravonova for Build.prop Tweaks
@Chainfire for SuperSu
@mrRobinson for AdAway
XDA:DevDB Information
FyrestoneROM, ROM for the Samsung Galaxy Tab 3
Contributors
Jimbus369
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: T113XXU0AQA1
Based On: STOCK Samsung
Version Information
Status: Stable
Current Stable Version: 2.0
Stable Release Date: 2017-02-04
Created 2017-01-04
Last Updated 2018-08-18

Reserved
Changelog:
27 July 2018:
Updated to XXU0ARB1
Fixed all previous issues
Removed Cyanogen File manager and Adawey
Now Thunderoar Kernel v5.0 is fully compatible
Updated Busybox and SuperSu
4 Feb 2017:
Updated to XXU0AQA1
Removed some Bloatware
Deodexed
Zipaligned
Faster animation scale
Allow apps access to external storage
Loud volume warning removed
Cyanogen/LineageOS UI sounds
Battery Tweaks
Increase Quality Of Media Streaming
Fixed Google DNS
Fixed Calendar Sync
Various build.prop changes
Various fix
4 Jan 2017:
Initial release
Known issues:
Calendar doesn't synchronize --> Calendar_sync_fix.zip
Tablet doesn't support vpn functionality --> VPN_FIX.zip
Print spooler does not works --> PrintSpooler_FIX.zip

Fantastic! Finally we've got a rom of our very own, for which you've got my immense thanks. I'm very much looking forward to trying it out.
Unfortunately when I flashed it there was a loooong wait on the Samsung logo, and then... Well, after an hour I booted back to recovery to start over.
I honestly don't think your rom was the problem though, because from some point last night everything I tried - custom rom flashing and nandroid backup restores - wound up the same way. Odin + stock + root got a usable system at least, and today's been too busy to try again. But when I do I'll post back about how it goes.
(Sadly, I can't go back in time to see what order I did things and look for a pattern if this happens again. In case it might be useful to anyone, I know for sure I'd gotten stock set up comfortably and made a complete backup before giving thunderoar's T113 kernel a whirl, and that went swimmingly. Even had mounts2sd properly recognizing external sd set up after a long struggle, though not actually enabled yet. Don't know what else i did between making that backup and trying to flash this, but it's likely I just screwed something up somehow.)

PushyPhoenix said:
Fantastic! Finally we've got a rom of our very own, for which you've got my immense thanks. I'm very much looking forward to trying it out.
Unfortunately when I flashed it there was a loooong wait on the Samsung logo, and then... Well, after an hour I booted back to recovery to start over.
I honestly don't think your rom was the problem though, because from some point last night everything I tried - custom rom flashing and nandroid backup restores - wound up the same way. Odin + stock + root got a usable system at least, and today's been too busy to try again. But when I do I'll post back about how it goes.
(Sadly, I can't go back in time to see what order I did things and look for a pattern if this happens again. In case it might be useful to anyone, I know for sure I'd gotten stock set up comfortably and made a complete backup before giving thunderoar's T113 kernel a whirl, and that went swimmingly. Even had mounts2sd properly recognizing external sd set up after a long struggle, though not actually enabled yet. Don't know what else i did between making that backup and trying to flash this, but it's likely I just screwed something up somehow.)
Click to expand...
Click to collapse
Upgrade your firmware to PH5 before flash and use TWRP 3.0.2-0.
Firmware: http://samsung-updates.com/device/?id=SM-T113
TWRP: https://dl.twrp.me/goyave/
Wipe all partition in TWRP:
System, Cache, Dalvik and if you can internal Storage.
Thunderoar Kernel isn't compatible with PH5 firmware for the moment.
Let me know how it goes

Thanks so much for responding even though I didn't specifically ask.
Pretty much all my knowledge comes from following instructions in these forums and piecing little bits of information together, so I've got a few questions - trying to understand the "why" behind these things in order to be more self-sufficient. Please feel free to point me towards resources where I can learn more!
Jimbus369 said:
Upgrade your firmware to PH5 before flash and use TWRP 3.0.2-0.
Click to expand...
Click to collapse
This is a surprise to me - I'd always thought that when flashing a new ROM, everything gets replaced. I never would have figured this part out on my own!
Firmware: http://samsung-updates.com/device/?id=SM-T113
Click to expand...
Click to collapse
There's no Canadian version - but should I presume that, since this is a Wi-Fi only device, the CSC isn't too important?
How much does this matter even when using a device with a network connection?
TWRP: https://dl.twrp.me/goyave/
Click to expand...
Click to collapse
(Ooops, forgot to do this right off the bat. My bad!)
Does recovery version generally make a big difference?
Wipe all partition in TWRP:
System, Cache, Dalvik and if you can internal Storage.
Click to expand...
Click to collapse
I've been wiping Data as well - is that not necessary?
Does wiping Internal Storage have a big effect? I suppose there's a fair bit of app-specific stuff in there that could cause issues?
Thunderoar Kernel isn't compatible with PH5 firmware for the moment.
Click to expand...
Click to collapse
Ah well, soon enough!
Let me know how it goes
Click to expand...
Click to collapse
Of course! You're investing time in putting this together, and helping out users; the very least I can do is let you know what's going on with that time you've invested!
Okay, about to check on the firmware installation!

PushyPhoenix said:
This is a surprise to me - I'd always thought that when flashing a new ROM, everything gets replaced. I never would have figured this part out on my own!
Click to expand...
Click to collapse
When you install a rom, especially a TW one, in most case you need a specific Bootloader to cause it to start and work smoothly.
Wikipedia:
A boot loader is a computer program that loads an operating system or some other system software for the computer after completion of the power-on self-tests; it is the loader for the operating system itself. Within the hard reboot process, it runs after completion of the self-tests, then loads and runs the software. A boot loader is loaded into main memory from persistent memory, such as a hard disk drive or, in some older computers, from a medium such as punched cards, punched tape, or magnetic tape. The boot loader then loads and executes the processes that finalize the boot. Like POST processes, the boot loader code comes from a "hard-wired" and persistent location; if that location is too limited for some reason, that primary boot loader calls a second-stage boot loader or a secondary program loader.
The bootloader runs your rom with specific instructions, if the rom does not support an older bootloader simply does not boot. My rom does not support the older bootloader. A zip flash in this case cannot upgrade a delicate part like the bootloader. You need to flash the newer one with Odin.
There's no Canadian version - but should I presume that, since this is a Wi-Fi only device, the CSC isn't too important?
How much does this matter even when using a device with a network connection?
Click to expand...
Click to collapse
The latest update for your country is PA5. Try with THIS.
Your country code is XAC.
The CSC (Sale Country Code) Is that part of the firmware that contains all the telephone operator customizations (e.g. WAP, MMS) for the intended country. As far as i know, It is not important for us.
(Ooops, forgot to do this right off the bat. My bad!)
Does recovery version generally make a big difference?
Click to expand...
Click to collapse
Yes, the Recovery can make the difference.
I've been wiping Data as well - is that not necessary?
Does wiping Internal Storage have a big effect? I suppose there's a fair bit of app-specific stuff in there that could cause issues?
Click to expand...
Click to collapse
I forgot to write data, my bad! But i wrote it in the instructions in the first topic. For personal experience i had different issues when I didn't formatted the Internal Storage. The Android folder, .thumbnails and others, can create issues.
Ah well, soon enough!
Click to expand...
Click to collapse
I hope that in the next update we could use this kernel. :fingers-crossed:
Of course! You're investing time in putting this together, and helping out users; the very least I can do is let you know what's going on with that time you've invested!
Okay, about to check on the firmware installation!
Click to expand...
Click to collapse
I want to give my best support at all users in difficulty, if you have a problem just ask. :good: :good:
Sorry for my english

Jimbus369 said:
Sorry for my english
Click to expand...
Click to collapse
You're doing just fine!
I'll reply more later, but wanted to report that it's installed and running very smoothly! Haven't played around much but will do at home later.
If you've got any tips for getting mounts2sd up and running I'd really appreciate it!

PushyPhoenix said:
You're doing just fine!
I'll reply more later, but wanted to report that it's installed and running very smoothly! Haven't played around much but will do at home later.
If you've got any tips for getting mounts2sd up and running I'd really appreciate it!
Click to expand...
Click to collapse
I'm happy to hear it. Anyway, I don't know how mounts2sd works. Have you already tried HERE?

Jimbus369 said:
I'm happy to hear it. Anyway, I don't know how mounts2sd works. Have you already tried HERE?
Click to expand...
Click to collapse
Yup, that's the app I'm using, but haven't been able to get my external partition mounted properly. I did manage it once, think it was with thunderoar's kernel though.
Sent from my SM-G900W8 using XDA Labs

Jimbus369 said:
I'm happy to hear it.
Click to expand...
Click to collapse
Life has gotten in the way of playing around with this, but thought I'd send you an update as I said I would...
Your rom is running really nicely on my tablet as I use it daily. It's smooth and small, with no unexpected reboots or fc's on installed apps. Didn't wipe internal SD but it hasn't given me any issues with existing data (probably because there wasn't much to start with).
One thing that has caused a problem is calendar sync. It looks like you've taken out the actual syncing service, so when I try to access my calendars through any app I'm asked to add a new Google account, even though everything's already set up in "Accounts" under Settings. I haven't tried running the "calendars.providers.apk" from my other phone, that should fix the problem - but I don't want to use the wrong version and break something!
Also, I've confirmed that the only time I got mounts2sd working, it was with thunderoar's kernel. So guess that's going to have to wait.
A few adjustments I made to the setup were to uninstall all "unnecessary" system apps (not needed to run the device), and re-install them from the store. This way I've got 676mb free on /system and still over 1.5GB free on internal storage.
I've also added a multi-reboot menu to make getting into recovery or download mode simpler, and this is loading more quickly on your rom than stock. I've also had to modify permissions.xml to allow apps to access external storage by default, and made another tweak to disable the "loud volume warning" (don't remember quite what it was offhand).
Would you consider adding these to a future version?
Again, thanks SO much for putting this together, answering questions, and doing your thing. It's greatly appreciated!

PushyPhoenix said:
Life has gotten in the way of playing around with this, but thought I'd send you an update as I said I would...
Your rom is running really nicely on my tablet as I use it daily. It's smooth and small, with no unexpected reboots or fc's on installed apps. Didn't wipe internal SD but it hasn't given me any issues with existing data (probably because there wasn't much to start with).
One thing that has caused a problem is calendar sync. It looks like you've taken out the actual syncing service, so when I try to access my calendars through any app I'm asked to add a new Google account, even though everything's already set up in "Accounts" under Settings. I haven't tried running the "calendars.providers.apk" from my other phone, that should fix the problem - but I don't want to use the wrong version and break something!
Also, I've confirmed that the only time I got mounts2sd working, it was with thunderoar's kernel. So guess that's going to have to wait.
A few adjustments I made to the setup were to uninstall all "unnecessary" system apps (not needed to run the device), and re-install them from the store. This way I've got 676mb free on /system and still over 1.5GB free on internal storage.
I've also added a multi-reboot menu to make getting into recovery or download mode simpler, and this is loading more quickly on your rom than stock. I've also had to modify permissions.xml to allow apps to access external storage by default, and made another tweak to disable the "loud volume warning" (don't remember quite what it was offhand).
Would you consider adding these to a future version?
Again, thanks SO much for putting this together, answering questions, and doing your thing. It's greatly appreciated!
Click to expand...
Click to collapse
The calendar sync issue should be fixed in the next update.
Anyway, If I have enough time, the next update should contain a lot of new features. Your suggestions are already planned :good:

Jimbus369 said:
When you install a rom, especially a TW one, in most case you need a specific Bootloader to cause it to start and work smoothly.
....
The bootloader runs your rom with specific instructions, if the rom does not support an older bootloader simply does not boot. My rom does not support the older bootloader. A zip flash in this case cannot upgrade a delicate part like the bootloader. You need to flash the newer one with Odin.
Click to expand...
Click to collapse
One more question about this: The way you've worded the second paragraph seems to imply only that older bootloaders don't work with newer roms, so are newer bootloaders backwards compatible? Say I've got the PH5 bootloader installed and I want to restore a backup of the previous firmware, do I have to flash that firmware first?
Sorry if it seems obvious, this is how we learn!
Sent from my SM-G900W8 using XDA Labs

PushyPhoenix said:
One more question about this: The way you've worded the second paragraph seems to imply only that older bootloaders don't work with newer roms, so are newer bootloaders backwards compatible? Say I've got the PH5 bootloader installed and I want to restore a backup of the previous firmware, do I have to flash that firmware first?
Sorry if it seems obvious, this is how we learn!
Sent from my SM-G900W8 using XDA Labs
Click to expand...
Click to collapse
Absolutely it isn't obvious, don't worry . The Bootloader, for my personal experience, are backwards compatible. I don't have a scientific knowledge about this, but for what I did with other device it can work. Just try :fingers-crossed:, don't forget a full backup.

Calendar_sync_fix.zip
Here is a fix for calendar sync.
@PushyPhoenix Thanks for reporting this issue

Jimbus369 said:
Calendar_sync_fix.zip
Here is a fix for calendar sync.
@PushyPhoenix Thanks for reporting this issue
Click to expand...
Click to collapse
This is a huge help, as one reason for getting this tablet was to use the calendar on a bigger screen.... Thanks so much!
---------- Post added at 10:58 PM ---------- Previous post was at 10:50 PM ----------
Jimbus369 said:
The Bootloader, for my personal experience, are backwards compatible. I don't have a scientific knowledge about this, but for what I did with other device it can work. Just try :fingers-crossed:
Click to expand...
Click to collapse
Fantastic - it worked on my S5 (had to restore a backup to retrieve some data).
don't forget a full backup.
Click to expand...
Click to collapse
Never! The most important thing, along with wiping.

When is coming to FyrestoneROM V2 ?
And thank you very much. So love...

Does this work on sm-t116ny ?
Because no development for sm-t116ny .

dhruvpatel_9880 said:
Does this work on sm-t116ny ?
Because no development for sm-t116ny .
Click to expand...
Click to collapse
I don't think it can work. If your device codename is Goyave you can try. Let me know if it works

Jimbus369 said:
I don't think it can work. If your device codename is Goyave you can try. Let me know if it works
Click to expand...
Click to collapse
First of all thanks for replying
My device codename is Goyave3g5m probably .
Can you please tell me which all models have same codename "Goyave"?
And cm 11 for sm-t116 works well on my sm-t116ny.
I will try and let you know does it boots .
---------- Post added at 01:55 PM ---------- Previous post was at 01:40 PM ----------
It is working on sm-t116ny
But wifi hotspot not working
Please help

dhruvpatel_9880 said:
First of all thanks for replying
My device codename is Goyave3g5m probably .
Can you please tell me which all models have same codename "Goyave"?
And cm 11 for sm-t116 works well on my sm-t116ny.
I will try and let you know does it boots .
---------- Post added at 01:55 PM ---------- Previous post was at 01:40 PM ----------
It is working on sm-t116ny
But wifi hotspot not working
Click to expand...
Click to collapse
T113/T113nu and T116/T116ny have a similar codename and hardware (The recovery have goyave codename, therefore any rom with goyave codename can be flashed). For the hotspot, maybe some missing libraries, a different driver or a different kernel makes hotspot broken. Try to restore your kernel from a previous backup.

[STOCK][DUMPS][FIRMWARE] Essential stock firmware and rom dumps

I am not responsible if you break your phone in any way, these are here for your aid. I will help as much as i can, but it is on YOU, the user to read the OP and understand exactly what it is you are doing at ALL times.
READ THIS: http://mata.readthedocs.io/en/latest/ LEARN FROM IT, DONT EVEN CONTINUE UNLESS YOU HAVE READ THIS
These can be used to return to 100% stock as long as you can get into fastboot mode on the device, and have unlocked the bootloader and critical partitions. All images contained in the zips are directly from the essential Fastboot zips and OTA's, and dumps for the rest
Prerequisites:
1. Working fastboot environment in bootloader: (test using the command fastboot devices should return your s/n) Windows drivers are at the bottom of the OP.
Essentials windows drivers contain working ADB/Fastboot and places an environment variable to link to these binaries, i would HIGHLY recommend ditching any and all adb/fastboots you may have (minimal, HTC, etc) and use what is supplied by essential, they just work (Not gonna help you either if your hellbent on using your adb/fastboot).
The zips contain all the firmware (19 Images), TWRP11.img (the latest version), and a stockboot.img (so you can conveniently place on your phone and flash in twrp) when rooting with magisk, and boot.fix.red.img (In case you kill verity).
2. Bootloader unlocked: run the command fastboot flashing unlock in bootloader (THIS WIPES USER DATA, BACKUP BEFOREHAND), conversely fastboot flashing lock will relock the bootloader. I dont recommend this, as there are lots of bricks from messing up a flash and locking yourself out afterward.
3. Critical partition unlocked: run the command fastboot flashing unlock_critical in bootloader (THIS WIPES USER DATA, BACKUP BEFOREHAND), conversely fastboot flashing lock_critical will relock the critical partition flashability. I dont recommend this, as there are lots of bricks from messing up a flash and locking yourself out afterward.
4. Common Sense: Use IT!!!!!
Downloads
Android 10 BTS Folder: https://sourceforge.net/projects/mata-bts/files/10
Q Beta BTS Folder: https://sourceforge.net/projects/mata-bts/files/Q-Beta/
Pie BTS & Novendor Folder: https://sourceforge.net/projects/mata-bts/files/Pie
P Beta BTS: https://sourceforge.net/projects/mata-bts/files/P-Beta/
Oreo BTS & NOVENDOR: https://sourceforge.net/projects/mata-bts/files/Oreo/
The Files below are OLD as dirt BTS
OPM1.180104.010 mega.nz (oreo 8.1 beta1)
OPM1.170911.254 mega.nz (oreo 8.0 beta3)
OPM1.170911.213 mega.nz (oreo 8.0 beta2)
OPM1.170911.130 mega.nz (oreo 8.0 beta)
NMK32F AFH (latest nougat 7.1)
NMJ88C mega.nz (nougat 7.1)
NMJ51B AFH (nougat 7.1)
NMJ32F AFH (nougat 7.1)
NMJ20D mega.nz (nougat 7.1)
NMI81C AFH (nougat 7.1)
Drive Folder of Patched Essential Boot images Credit Goes to @dazeone
Some OLD AS DIRT Novendor zips aswell... if anyone still cares
OPM1.180104.010 mega.nz (oreo 8.1 beta1)
OPM1.170911.254 mega.nz (oreo 8.0 beta3)
OPM1.170911.213 mega.nz (oreo 8.0 beta2)
Windows Drivers
drivers
Unzip this and check out the flash-all.[bat,sh] scripts for win/lin (they're identical but provided for easier flashability).
They're set up to flash to both slots. Most people will want to do this on a back to stock mission, but they can be adjusted if your goal is something else.
If coming from some other rom, you're also going to want to wipe your data, or you're not going to boot. This can be accomplished by the command in the bootloader: fastboot -w keep in mind there are multiple scripts to wipe for you in the zips.
These can also be used to make custom roms/rooted boot images/etc too, so have fun with it!
Thanks:
@invisiblek - aer0zer0 stole his thread, he put most of it together
@aer0zer0 - i stole the thread from aer0, his 2yr old son makes more use of the PH-1 than he does.
@bmg1001 - Root thread, found here root
@dazeone - Provides independent patched boot images and has an awesome YouTube Channel of Guides! DazeOne Youtube Channel
Enjoy

Heck ya

Yesssss

Ill be giving this a shot in a few days hoping to return my phone back to complete stock.

Hot diggity... been fun reading/watching you all work on this through Discord, think I'll go ahead and unlock it while I still have my S8 in case I trash things

Anyone planning on trying to make some custom roms for this phone? I am waiting to see if there will be any decent dev community for this phone before I actually buy it.

vekenti said:
Anyone planning on trying to make some custom roms for this phone? I am waiting to see if there will be any decent dev community for this phone before I actually buy it.
Click to expand...
Click to collapse
Lineage okay for you lol?
You've got one of the top devs on Lineage working on this so I think you're good.

Thank you! I'll be rooting now that we have a safety net!

I am trying this out now got a lot of errors saying:
FAILED (remote: Flashing is not allowed for Critical Partitions
However the main partitions like modem and system seem to work fine.

invisiblek said:
So as we're still waiting for Essential to release official factory images, I thought it'd be helpful to link the dumps that we've produced. These can be used to return to 100% stock as long as you can get into fastboot mode on the device.
Click to expand...
Click to collapse
Thanks for this. My fingerprint sensor was not working for some reason after rooting and I thought i would go completely stock. This thread helped me to go completely stock and get the fingerprint back to working.
Thought I haven't locked the bootloader yet. Will try it later.
---------- Post added at 05:55 AM ---------- Previous post was at 05:48 AM ----------
sarcoptic said:
I am trying this out now got a lot of errors saying:
FAILED (remote: Flashing is not allowed for Critical Partitions
However the main partitions like modem and system seem to work fine.
Click to expand...
Click to collapse
For flashing to critical partition you need to unlock them. The command is similar to unlock boot-loader.
Code:
fastboot flashing unlock_critical
And to lock it again
Code:
fastboot flashing lock_critical

The unlock_critical command worked fine....have you tried updating to the latest build from essential? I tried a couple times and I keep getting a installation problem.

sarcoptic said:
The unlock_critical command worked fine....have you tried updating to the latest build from essential? I tried a couple times and I keep getting a installation problem.
Click to expand...
Click to collapse
New zip on the way. I know why that is. The system image was modified (I had forgot I mounted it once which broke its signature).
I'll update once its ready. Sorry about that.
EDIT: OP updated with new link. Again, sorry about that. Slight oversight. With the new zip the OTA will take fine.

invisiblek said:
New zip on the way. I know why that is. The system image was modified (I had forgot I mounted it once which broke its signature).
I'll update once its ready. Sorry about that.
EDIT: OP updated with new link. Again, sorry about that. Slight oversight. With the new zip the OTA will take fine.
Click to expand...
Click to collapse
Freaking rockstar thanks!

invisiblek said:
New zip on the way. I know why that is. The system image was modified (I had forgot I mounted it once which broke its signature).
I'll update once its ready. Sorry about that.
EDIT: OP updated with new link. Again, sorry about that. Slight oversight. With the new zip the OTA will take fine.
Click to expand...
Click to collapse
Thanks mate.

Thanks for the dump! Just yesterday I was trying to figure out how to do the adb backup command but I gave up cause I couldn't get a good reliable connection to my phone (driver issues, then to failed to connect to device, then to using the adb shell and a mouse on recovery, fun times.)

Great

please can someone guide on how to root it

chambar said:
please can someone guide on how to root it
Click to expand...
Click to collapse
I'm not sure how you missed this:
https://forum.xda-developers.com/es.../guide-rooting-essential-ph-1-magisk-t3701976

charlie.s said:
I'm not sure how you missed this:
https://forum.xda-developers.com/es.../guide-rooting-essential-ph-1-magisk-t3701976
Click to expand...
Click to collapse
Much appreciated, indeed dunno how i missed it.

free XDA points for @invisiblek .......Thanks for putting it all together, hopefully you can get a teiko sports watch when you turn all the points in, LOL
Seriously, thanks for putting it all together

Can't update

I made the mistake of installing TWRP and Magisk before updating, and all I get is the "update unsucessful" screen, so now I'm stuck with 7.1.1 on my Android One Moto X4.
I found a factory image of Oreo on firmware.center (can't link it here because new user, but the filename was PAYTON_FI_8.0.0_OPW27.57-25-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip) for my device, and would like to know if it's safe to use and how to install it (sites seem to give conflicting information). This thing is brand new, so I'm a bit nervous about messing it up.

Hey, just try this Guide: https://forum.xda-developers.com/moto-x4/development/flash-official-frmware-moto-x4-t3730750
And use this ROM as it is current Oreo with March Security patch: https://androidfilehost.com/?fid=673956719939834159
If you have further issues feel free to ask again

sleeptab said:
Hey, just try this Guide: https://forum.xda-developers.com/moto-x4/development/flash-official-frmware-moto-x4-t3730750
And use this ROM as it is current Oreo with March Security patch: https://androidfilehost.com/?fid=673956719939834159
If you have further issues feel free to ask again
Click to expand...
Click to collapse
One last thing, that guide mentions using mfastboot, where do I get it? Is it any different from the regular fastboot?

No it's just normal fastboot.

Flashed it, works great! Thank you! (However, Android File Host was having issues and it took multiple times before a successful download)

[ROM] TMO Z2 Force 27.1.5 / 27.1.7 FlashAll (Mar/Aug 2019)

This is a Motorola Z2 Flash T-Mobile FlashAll. It is based on @texasaggie1's October 2018 version and does not wipe user data.
Disclaimer: Flash at your own risk. Not responsible for damages if this stuff goes south. If you don't know what a flashall is, or twrp, or fastboot, you may not be ready for this.
Similarities to @texasaggie1's:
The image was downloaded from https://mirrors.lolinet.com/firmware/moto/nash/official/TMO/,
ADB + Fastboot are included
Windows Only (FOR NOW)
Differences:
Updated for 27.1.5 / 27.1.7
Updated included TWRP
Cleaned up batch files
Upcoming Changes:
Bash script version for Linux/Mac
Include TWRP 3.3.1-0 instead of TWRP 3.2.3-2
Batch prompt to install black logo fix
Prerequisites:
Windows
Oreo or newer
Unlocked bootloader
(bootloader) _______: not found OR FAILED (remote: unknown command):
This is a known issue with Motorola devices. Here are some steps you should try:
Try another USB port
Use another ADB version
Try another USB cable
Use Windows 7
How To:
Unzip the Flashall
Open a command prompt in the folder it created
Connect the phone with ADB debugging enabled
Follow the section below based on what you would like to do
Return to Stock
Run flashall.bat
Return to Stock with Root
Run flashall_then_recovery.bat
Choose Install, then select the TWRP installer .zip
Choose Reboot, then Recovery
Choose Install, then the Magisk (recommended), or another SU .zip
Choose Reboot, then System
Return to Stock and Wipe All Data
Run flashall_erase.bat
Downloads
27.1.5 March Flashall
27.1.7 August Flashall - WARNING: USE 27.1.7 AT OWN RISK. Reports of WIFI+DATA bricking on LineageOS
Updated Flashall scripts - Updated 8/28/19, drop into an existing flashall above.
If this helps you please hit the "Thanks" button. Reply to this post if you have questions or need any assistance.

Can't Wait to Try It
I will download it later and attempt to update my Z2 (now my wifes )
Thanks for doing this!
What command do I run if I just want to update the phone, but keep all of my data?

texasaggie1 said:
I will download it later and attempt to update my Z2 (now my wifes )
Thanks for doing this!
What command do I run if I just want to update the phone, but keep all of my data?
Click to expand...
Click to collapse
Assuming your on an older build of stock (e.g. 27.1.3) and want to update to this version, flashall.bat will update you. flashall_then_recovery.bat will also upgrade and also setup for installing root. For non-stock builds and newer android versions (Pie) there may be some issues with database versions and other niche issues (e.g. Camera and root based apps storing files in different locations because of new Pie limitations). I always back up all my apps+data using Titanium backup before any changes, helps prevent a lot of hassle.
Edit: Additionally, if you've checked for updates before the updater may still think you have an update. It's best to clear the updater's appdata once the flashall completes. (I may add this to a future version)

rcmaehl said:
Assuming your on an older build of stock (e.g. 27.1.3) and want to update to this version, flashall.bat will update you. flashall_then_recovery.bat will also upgrade and also setup for installing root. For non-stock builds and newer android versions (Pie) there may be some issues with database versions and other niche issues (e.g. Camera and root based apps storing files in different locations because of new Pie limitations). I always back up all my apps+data using Titanium backup before any changes, helps prevent a lot of hassle.
Edit: Additionally, if you've checked for updates before the updater may still think you have an update. It's best to clear the updater's appdata once the flashall completes. (I may add this to a future version)
Click to expand...
Click to collapse
Didn't work for me....it hangs and fails to flash. Here is a screenshot showing how far it gets for me. Ideas?

tr4sh80 said:
Didn't work for me....it hangs and fails to flash. Here is a screenshot showing how far it gets for me. Ideas?
Click to expand...
Click to collapse
I've replied to you in the Z2 discord. I may need to make the file a bit more verbose. I'll update it after work today.

Worked for me, thank you OP. Said update unsuccessful after booting, but the build number shows 27.1.5 now.

Hi, isn't there Screenshot of the rom ?

mf2fx said:
Hi, isn't there Screenshot of the rom ?
Click to expand...
Click to collapse
Define screenshot? A screenshot of the version info? Or are you referring to a system image?

stuck
Mine is stuck like this. Any ideas?

I know this is for T-Mobile, but does anyone have the Verizon one? I am running a Sprint Z2 with Verizon and the update is failing for me :|

Same here
pacotort said:
Mine is stuck like this. Any ideas?
Click to expand...
Click to collapse
I get the exact same. On 27.1.3

How would I install this coming from Lineage 16.0

Thanks so much for this!!

pacotort said:
Mine is stuck like this. Any ideas?
Click to expand...
Click to collapse
Commands aren't being fully sent to the device and are being cut off past a certain point. You can tell because of things like
slot-suffi: not found
partition-typ: not found
Click to expand...
Click to collapse
Do you have another version of fastboot and ADB installed somewhere? Additionally try another cable/USB port.

I was trying to go with LineageOS 16.0 (to get me some PIE!!!) but it kept borking on me... and then I was in boot-loop hell!!! This FlashAll got me back to functional and I may just stick with it. Pie might be newer, but stable & reliable are most important for me. Thanks so much for putting this package together! Maybe T-mobile/ATT/Sprint should hire the devs from this forum to help them 1) get Pie out for the Z2 Force and 2) honor their commitments. Boohoo... it's too much work for them to build & test the package.... but it wasn't too much for them to hold our their hand and take hundreds of $$$ from each of us, was it?

papadelogan said:
I was trying to go with LineageOS 16.0 (to get me some PIE!!!) but it kept borking on me... and then I was in boot-loop hell!!! This FlashAll got me back to functional and I may just stick with it. Pie might be newer, but stable & reliable are most important for me. Thanks so much for putting this package together! Maybe T-mobile/ATT/Sprint should hire the devs from this forum to help them 1) get Pie out for the Z2 Force and 2) honor their commitments. Boohoo... it's too much work for them to build & test the package.... but it wasn't too much for them to hold our their hand and take hundreds of $$$ from each of us, was it?
Click to expand...
Click to collapse
Thanks for the feedback! I do agree that it's extremely disappointing only the Verizon variants are getting Pie, but hey, they gotta upsell that 5G mod somehow...

I am aware of the 27.1.7 update and will be creating an flashall for it soon

Various users have reported 27.1.7 is causing networking issues. I will not be releasing a flashall for this until this is fixed

rcmaehl said:
Various users have reported 27.1.7 is causing networking issues. I will not be releasing a flashall for this until this is fixed
Click to expand...
Click to collapse
What sort of networking issues? WiFi or issues with service?

rcmaehl said:
Various users have reported 27.1.7 is causing networking issues. I will not be releasing a flashall for this until this is fixed
Click to expand...
Click to collapse
Can you post the link to 27.1.7?
I looked on mirrors.lolinet.com and it is not posted there yet.
I will try my own flashall and report back

Please help, need boot.img with Android 10

I have tried multiple times to install TWRP and every time it seems to get overwritten by stock recovery. I've tried everything I can find online. After successfully flashing recovery.img and sending command "fastboot reboot recovery" or command "fastboot reboot 'recovery.img'" it flashes orange for a fraction of a second then vibrates a second time and shows boot logo screen with orange state warning, then either boots to stock recovery, or it boots to the home screen. One person said he was running into the same issue as I was and was only successful by deleting all the partitions on the device and reflashing it. He doesn't remember the steps he used and I would like to avoid even trying to do that anyway.
My only goal is to obtain root on my device, even if I'm using AOSP, as long as it's AOSP Android 10 v222, however I'm having issues trying to build a version of AOSP for this device without being able to find the binaries for it.
With all that being said, my question is if anyone who has the Blu Bold N1 running with the Android 10 update and working TWRP installed could please dump the rom and send it to me or upload it for me somewhere. There is no way I can dump the rom of my own device because I cannot get TWRP to successfully boot, and Blu does not host the Android 10 iso for this phone anywhere.
Alternatively, if someone could find the binaries for this device or knows how to find them, I could successfully build my image of AOSP and obtain root that way. I would rather be on the stock android that comes with the phone, but if I can't root it then I don't care to move to something else.
On an unrelated note, this is the first time I've ever posted on this forum and I apologize if anything I'm asking for or saying goes against the guidelines.

Hey, I pulled the Android 10 OTA. Can that b of help ?

greeneyez15o said:
Hey, I pulled the Android 10 OTA. Can that b of help ?
Click to expand...
Click to collapse
YESS! I've been using this phone without root for months now, you'd be a lifesaver if you could show me where I can download it.

greeneyez15o said:
Hey, I pulled the Android 10 OTA. Can that b of help ?
Click to expand...
Click to collapse
Sorry, I am the original poster of this thread, "emooverlord" I guess I signed in with my Facebook when I posted this and signed in with my email this time on accident.

emooverlord said:
Sorry, I am the original poster of this thread, "emooverlord" I guess I signed in with my Facebook when I posted this and signed in with my email this time on accident.
Click to expand...
Click to collapse
Ugh...sorry I don't have it anymore. I was annoyed I couldn't get it rooted.

greeneyez15o said:
Ugh...sorry I don't have it anymore. I was annoyed I couldn't get it rooted.
Click to expand...
Click to collapse
I can't seem to get TWRP on it at all, with the boot img or the rom would it not work with magisk?

The 3 files attached are:
boot.bin: The contents of the original 'boot' partition.
boot-stripped.bin: Patched with an empty vbmeta image, to allow custom ROM flashing and the like. Generated by:
Code:
cp boot.bin boot-stripped.bin
avbtool erase_footer --image boot-stripped.bin
avbtool append_vbmeta_image --image boot-stripped.bin --partition-size 33554432 --vbmeta_image /path/to/google-empty-vbmeta.img
boot-magisk.img: Pre-patched with Magisk 23 Canary (23016).
These are all from the November 2021 security patch of A10 on the Bold N1.

Also: you can extract everything off of the live device with https://github.com/bkerler/mtkclient:
Code:
python ./mtk rl <path to backup>
will give you a dump of all of the partitions on the device. (Since 'userdata' is encrypted and the last one, when it gets there, just hit ctrl-C when it gets there and you'll have everything out of the backup.)

irony_delerium said:
These are all from the November 2021 security patch of A10 on the Bold N1.
Click to expand...
Click to collapse
Any idea where I can get the Nov security patch? I'm stuck on Feb update.

GMSS75 said:
Any idea where I can get the Nov security patch? I'm stuck on Feb update.
Click to expand...
Click to collapse
Not off the top of my head. Mine updated to the November SP pretty quickly after turning it on the first time.

irony_delerium said:
Not off the top of my head. Mine updated to the November SP pretty quickly after turning it on the first time.
Click to expand...
Click to collapse
Ok thanks, I can't disable dm-verity, how do you patch vbmeta in the boot image?

GMSS75 said:
Ok thanks, I can't disable dm-verity, how do you patch vbmeta in the bootee image?
Click to expand...
Click to collapse
I used avbtool on the stock image. Check how I created boot-stripped.bin.