Database Develop

[SAFESTRAP ROM] MotoBlur 5.7.894 for Droid 3

This is a Safestrap flashable ROM of an OTA leak that was pulled from the staging servers on 11/03.
[EDIT: 11/05] This ROM was kind of a test to see how well this would run w/o the kernal and BP. And to be honest, it's meh. The kernel + BP improvements in the actual OTA are probably what will make this better. I don't really recommend running this ROM for anything other than .. curiosity.
The Build ID is: 5.5.1_84_D3G-64
Download Here
The download link takes you to the "Android Downloads" section of my blog where you can grab the .zip file at the bottom in the "Other ROMs" section.
Instructions:
- Download the ROM
- Verify the MD5
- Place it on your SD card
- To run this you need to install Safestap which can also be downloaded from the same page on my blog. Please remove Koush's Bootstrap before installing Safestrap. 2 Bootstraps = Bad.
- Once Safestrap is installed, reboot and use the [ menu ] key during the splash screen to enter recovery.
- Make a backup, don't need the original system. We're going to use the /data partition in this backup in 4 steps.
- Turn on Safe System and wait for the swap process to finish
- Format /system
- Wipe data/cache
- Flash the MotoBlur ROM 5.7.894 .zip file
- Now do an advanced restore of "data" from the backup you made earlier. This should bring across all your apps from your primary ROM.
- Reboot and enjoy.
NOTE: The OTA leak also has a kernel and BP update which can't be included in a ROM like this.
I can release the actual OTA file if there's interest.
LEAK OTA WARNING: While using this ROM should be safe, flashing the actual OTA leak through stock recovery is a semi-dangerous decision as they may or may not release this update to the public for mass support. Do so at your own risk.

Kernel and BP update seems like a useful thing to have, can you post a link to the full OTA?

Why backup/restroe /data，that is no change.

thanks for all these goodies.

So if I understand this correctly.. a new update is coming?

DoubleYouPee said:
So if I understand this correctly.. a new update is coming?
Click to expand...
Click to collapse
yes but this may or may not be the final version of it. that is why it is recommended for now to install it this way so that you can preserve your original system to go back to if they dont release this version.
---------- Post added at 08:22 AM ---------- Previous post was at 08:16 AM ----------
Hashcode said:
This is a Safestrap flashable ROM of an OTA leak that was pulled from the staging servers on 11/03.
The Build ID is: 5.5.1_84_D3G-64
Download Here
The download link takes you to the "Android Downloads" section of my blog where you can grab the .zip file at the bottom in the "Other ROMs" section.
Click to expand...
Click to collapse
edit - grabbed wrong file

What does this OTA bring? Any ideas? What kernel changes are significant?

All I can say is I wonder how much Verizon techs know about the planned updates. Back at the end of September a day before the OTA rolled out I took in my phone, the tech was talking about an update that had just been released and another coming in November.
I pushed that there was no November update, and she must have it confused with the update that was about to roll out, she rolled her eyes at me and dropped it, but it turns out she may have been right.

Hash wouldn't be better with kernel intact in case of any incompatability?
-smc

Im running it right now and things seem fine. There are a few things I don't use so can't confirm everything works but, my download speeds have been normal finally if not excellent. Im about to test that theory here in a minute cause I get poor signal a work. Will report back later.
Sent from my DROID3 using XDA App

I'm guessing applying the OTA would also unroot and patch the exploit we use to gain root?
One of the biggest failings of this recovery method is we are still using the boot image's kernel, as opposed to the recovery's own kernel. Will this cause a problem for us to update the boot image? Isn't it all loaded into memory on startup by the bootloader anyway? Is the boot image touched at all after that?
I guess, worst case, we could apply the OTA, and then replace system with the 5.6.890 version using fastboot - assuming they don't change the signing keys to prevent downgrading...

slvrarrow said:
What does this OTA bring? Any ideas? What kernel changes are significant?
Click to expand...
Click to collapse
i used it for half a day and it seemed worse than current stock for radio and camera. i was dropping 3G a lot and the camera seemed even slower if that is possible.
went to Liberty and that is running perfect

Ok my signal went back to crap again. But it was crap before I installed so it might be the towers in my area.
Sent from my DROID3 using XDA App

Heh, sorry guys. I had forgotten to post the actual OTA for those that felt the need to apply it.
I believe this OTA is harder to root (current method does not work). So you'll need to have a "root keeper" method installed before applying it or risk having to do a lot of work to get root back (downgrade via fastboot, etc).
Once I get back to a computer I'll put the OTA .zip up (probably a few hours).
But you've been warned!

Can't you just SBF back to 890?

root keeper would be the best way but there's also zergRush it works works with the xt883 2.35 so i've read or me883 what ever its called
Or the loadpreinstalls.sh trick, not sure what's been patched.

VS980 39A - Stock Lollipop Flashable Firmware

!!! PLEASE READ THIS ENTIRE POST BEFORE PROCEEDING !!!
!!! I AM NOT RESPONSIBLE FOR ANY PROBLEMS THAT OCCUR WHILE INSTALLING/USING THIS !!!
This is a stock VS98039A firmware in flashable format.
FAQ:
Why isn't this debloated?
This is intended to be a stock firmware that can easily be restored to 100% stock. There's no need to "debloat" in the first place as most of the apps that would ordinarily be removed can simply be disabled via the built-in Application Manager. The 2nd post has a list of apps to disable so you can customize the install to your liking.
But even when they are disabled they're using memory!
No, they aren't. They aren't resident in memory, and you can't use the storage space they take up in the system partition anyway. You aren't missing out on anything.
Will you be updating this?
Unless I goofed and missed something on the initial upload, no.
What exactly has been modified?
It has been rooted with SuperSU 2.46, has busybox, and the ramdisk was slightly modified to allow adb access for OSX/Linux users and to remove a few known LG Security checks.
Can I take an OTA with this installed?
No. You should NOT take an OTA with this before following the instructions in the next question. Even then, if you have made ANY changes to the system (no matter how minor) you will need to manually revert them before attempting it.
OK. How do I make this COMPLETELY stock so I can take an OTA?
If you want to return to a 100% stock/unrooted/unmodified state, simply unroot (within the SuperSU app), reboot into recovery, and LASTLY flash the "Restore to 100% stock" below. Again, if you have made ANY changes elsewhere or applied any mods you SHOULD NOT take an OTA until you have reverted them first.
Will you be actively supporting this?
As this is a stock firmware package, any issues you have while using it are in LG/Google/Verizon's code. As such, I will not be supporting this. XDA has a Q&A section for general help.
Click to expand...
Click to collapse
Installing:
Make sure you have a backup in case anything goes wrong.
Download and flash the 39A bootstack zip from the VS980 Resources thread in this forum.
Wipe data & cache in TWRP (do not wipe internal storage)
Download and flash the VS98039A FW zip below.
Click to expand...
Click to collapse
Downloads:
Firmware:
VS980 39A Firmware
Extras:
Stock kernel - modified to enable adb for OSX/Linux users (This is already included in the above zip)
Stock kernel (permissive) - same as above, but with SEAndroid in permissive mode
Restore to 100% stock - ONLY USE if you wish to take an OTA and haven't made ANY other changes on your own. Otherwise this zip is to be avoided!!!!
Click to expand...
Click to collapse
Devs: Feel free to use any/all of this. There's no need to ask for permission. Just give credit.

The following is a list of apps that can be disabled without any problems. The ones in the recommended section are there because they're truly useless and can even be used to report information back to Verizon if you let them. The ones in the safe section can be disabled if you don't require their functionality. If you decide you want them again, just enable them.
Recommended:
Accessories
Caller Name ID
My InfoZone
My Verizon Mobile
Support & Protection
Verizon Login
Verizon Tones
VZ Navigator
Safe:
Amazon
Amazon app suite
Amazon Kindle
Amazon Music
Appstore
Audible
Clock Widget
Cloud
Cloud Print
com.android.partnerbrowsercustomizations.example
com.android.providers.partnerbookmarks
Favorite contacts Widget
Feather
Games
Google Play Games
LG TTS+
LG VoiceCommand SpeechPack
Media-in-One
Multi-photo
Music (the first one is the widget, the 2nd is the app)
NFL Mobile
Polar Bear
POLARIS Office 5
Print Spooler
QuickRemote
QuickTranslator
Slacker
SmartShare.DLNA
SmartShare.MediaServer
SmartShare.Provider
Softcard
Sync Service
Text Link
Text Link Agent
Text Link Engine
The Little Prince
Voice Command
Voice Mate Speech Pack
* Most of the Google apps can also be disabled (i.e. Books, Movies, etc).

Thnx a lot for the file.
If i understand it correctly as iam currently on 26A (modem+bootstack) i just need to flash 39a bootstack zip from your other thread and the 39A fw zip from this thread to be on LG stock lollipop.
No need to do anything else ?

amit_sen said:
Thnx a lot for the file.
If i understand it correctly as iam currently on 26A (modem+bootstack) i just need to flash 39a bootstack zip from your other thread and the 39A fw zip from this thread to be on LG stock lollipop.
No need to do anything else ?
Click to expand...
Click to collapse
That's correct.

Bugs: dim power led on is fixed in this rom?

bookerok said:
Bugs: dim power led on is fixed in this rom?
Click to expand...
Click to collapse
Yes, it is fixed.

There does not appear to be a Q&A thread for this yet, so I'll ask here:
1) Does AutoRec work on the manual OTA 39A or does a recovery image need to be flashed in fastboot?
2) In either case, can any of the previously working TWRP recoveries be used with 39A?
3) After flashing a custom recovery, does this thread's 39A firmware need to be flashed in order to have the phone successfully boot or will the 39A manual OTA boot with a custom recovery?

doublej713 said:
There does not appear to be a Q&A thread for this yet, so I'll ask here:
1) Does AutoRec work on the manual OTA 39A or does a recovery image need to be flashed in fastboot?
2) In either case, can any of the previously working TWRP recoveries be used with 39A?
3) After flashing a custom recovery, does this thread's 39A firmware need to be flashed in order to have the phone successfully boot or will the 39A manual OTA boot with a custom recovery?
Click to expand...
Click to collapse
1. AutoRec does not work. If you're already on rooted 39A without a custom recovery, you need to manually push one. This means downgrading the bootloader to 27A/28A, pushing a bumped boot.img, and then pushing TWRP. @bouchigo provided excellent instructions for that here
2. Technically no recoveries work on the 39A bootloader (LG patched the exploit), but if you downgrade to 27/28A, then any bumped recovery should work (assuming your ROM is bumped). The 27A bootloader is included in the 39A bootstack zip the OP instructs to flash
3. If you flash a custom recovery you need a bumped boot.img. So an unmodified 39A manual OTA won't boot - you can either flash this rom or follow the guide I mentioned in answer #1
---------- Post added at 08:41 AM ---------- Previous post was at 08:30 AM ----------
bookerok said:
Bugs: dim power led on is fixed in this rom?
Click to expand...
Click to collapse
Something I noticed about the power key led - LG added "downloaded apps" (among other things) to the notification options for the the power key led. My power led was still staying on, but I realized it was my ongoing weather notification app that was causing this. When I unchecked the downloaded apps options, it stayed off.

In case anyone is wondering, Xposed does not work with this. You'll get constant LG Cover crashes among others. I'm currently trying to see if I can get it to work by freezing the apps that are crashing and then reinstalling. I'll let you know if I'm able to get it to work.

SupahDave said:
In case anyone is wondering, Xposed does not work with this. You'll get constant LG Cover crashes among others. I'm currently trying to see if I can get it to work by freezing the apps that are crashing and then reinstalling. I'll let you know if I'm able to get it to work.
Click to expand...
Click to collapse
I think I read that freezing the LG Cover app solved this. Could be mistaken tho.
Edit: Actually this is what I'm referring to http://forum.xda-developers.com/showthread.php?p=59285552

I had to freeze LG SmartCover and also Weather/Weather Platform. No more force closes and I've been able to get a few modules working.

SupahDave said:
I had to freeze LG SmartCover and also Weather/Weather Platform. No more force closes and I've been able to get a few modules working.
Click to expand...
Click to collapse
Have you tried G3 Tweaksbox?

tholmes8291 said:
Have you tried G3 Tweaksbox?
Click to expand...
Click to collapse
Is that supposed to play nice with G2's? I never even thought to try it.

2nd post updated with detailed list of apps that can (or should be) disabled.

tholmes8291 said:
Have you tried G3 Tweaksbox?
Click to expand...
Click to collapse
SupahDave said:
Is that supposed to play nice with G2's? I never even thought to try it.
Click to expand...
Click to collapse
I think he means G2 Tweaksbox. G3 Tweaksbox will only work on G2s with G3 ROMs installed.

doublej713 said:
I think he means G2 Tweaksbox. G3 Tweaksbox will only work on G2s with G3 ROMs installed.
Click to expand...
Click to collapse
Yep my bad. I've been on xdabbeb's 982.5 which is a G3 ROM so you are correct sir.

SupahDave said:
Is that supposed to play nice with G2's? I never even thought to try it.
Click to expand...
Click to collapse
I think we're way OT and I've posted this info few days ago in one of our threads http://forum.xda-developers.com/showthread.php?p=59307974
G2/G3 TweaksBox might never work correctly according to the dev.
Sent from my VS98039A using XDA Free mobile app

Hi,
If I flash the 39A bootstack do I still retain custom recovery (i. e TWRP) ?
Thanks,
Gil.

lucifergil said:
Hi,
If I flash the 39A bootstack do I still retain custom recovery (i. e TWRP) ?
Thanks,
Gil.
Click to expand...
Click to collapse
Yes

Never mind. Read in the other thread the 39a bootstack contains the 27a aboot and it's bumped

Note4 IMEI loss on v2.66

Moving this here to a separate thread.
I hope both of you are willing to test, because I have not been able to reproduce the issue on my own (international) Note 4 so far.
dbzgod, which firmware are you running?
dbzgod said:
@Chainfire updating from 2.65 to 2.66 breaks data on Canadian Note 4.
IMEI and baseband become unknown. Downgrading back to 2.65 restored it.
Not sure what log to provide or how to go about getting one in this case, as it installs fine in twrp and apps get root access without issue.
Click to expand...
Click to collapse
ShrekOpher said:
Trouble with v2.66 beta.
I flashed the 2.66 beta with TWRP on my Note 4 (910T). after reboot I lost signal and IMEI. I am not sure what changed, but it looks like something from 2.65 to 2.66 broke the cell signal on the Note 4.
I am running stock firmware 5.1.1 DOK2
Just wanted to let you know.
Click to expand...
Click to collapse

Yeah I'm down. Let me know what you need.

Log for no signal issue.
https://mega.nz/#!zxJXwAxA!pWCkObE1PrwRz4ZhYAHhEw8bJKhk-fyjlqpuL7bCwmo

Chainfire said:
Moving this here to a separate thread.
I hope both of you are willing to test, because I have not been able to reproduce the issue on my own (international) Note 4 so far.
dbzgod, which firmware are you running?
Click to expand...
Click to collapse
For sure ill test.
I am running the latest stock Canadian rom 5.1.1 N910W8VLU1COK3
Which logs to provide? Is there an app that will quickly provide all the logs like you did @ShrekOpher

dbzgod said:
For sure ill test.
I am running the latest stock Canadian rom 5.1.1 N910W8VLU1COK3
Which logs to provide? Is there an app that will quickly provide all the logs like you did @ShrekOpher
Click to expand...
Click to collapse
Yeah I used sys log. Link below.
https://play.google.com/store/apps/details?id=com.tortel.syslog

Thanks for the logs and info. Trying to use them combined with dissected firmwares to figure out what the issue is.

What can we do to help test? I just moved back to the stock 5.1.1 firmware (DOK2) from having been using VisionX Rom (A port from the international note 4). I flashed the stock image using odin and then flashed TWRP. I jumped straight to SU version 2.66. I had an IMEI before I flashed that file. Afterwards, it was null. I re-flashed the stock image using odin, which restored the system image and effectively deleted any ramdisk mods. I restarted and had my IMEI back and full lte signal. Each flash that I did was dirty, I have not factory reset. The custom ROM that I was running prior to going back to stock was pre-rooted with the xposed framework running. Please let me know what other information you require and I will get it to you. Thanks.

BJHiltbrand said:
What can we do to help test? I just moved back to the stock 5.1.1 firmware (DOK2) from having been using VisionX Rom (A port from the international note 4). I flashed the stock image using odin and then flashed TWRP. I jumped straight to SU version 2.66. I had an IMEI before I flashed that file. Afterwards, it was null. I re-flashed the stock image using odin, which restored the system image and effectively deleted any ramdisk mods. I restarted and had my IMEI back and full lte signal. Each flash that I did was dirty, I have not factory reset. The custom ROM that I was running prior to going back to stock was pre-rooted with the xposed framework running. Please let me know what other information you require and I will get it to you. Thanks.
Click to expand...
Click to collapse
Which exact device is this?

Chainfire said:
Which exact device is this?
Click to expand...
Click to collapse
Sorry, I forgot to mention. It's a T-Mobile Note 4 (SM-910T). I am using it on the Cricket Cell network, however, so I have had to manually enter the settings for their APN to get it to connect. Don't know if that's relevant.

@dbzgod @ShrekOpher @BJHiltbrand
Please try the attached version.
I'm more or less stabbing in the dark here, I don't have too much hope of this fixing it, but it just might. Let me know.
(download removed, try newer one below)

Chainfire said:
@dbzgod @ShrekOpher @BJHiltbrand
Please try the attached version.
I'm more or less stabbing in the dark here, I don't have too much hope of this fixing it, but it just might. Let me know.
Click to expand...
Click to collapse
No Dice still could not get Cell signal. No Idea why either. I got another sys log for you though. thanks for the help.
Is there a reason why on 2.65 beta the cell signal works fine, but on 2.66 its broken. Maybe looking at what changed is the only way to figure it out.
thanks for the effort either way, as you know all of the Android community appreciates your hard work.
https://mega.nz/#!30xBDJaS!mos23pH9RtqumWEbPof4cGy5wLW6JsGF_EWPmtztgzo

I am in fact looking at what has changed. The problem is that some of these things cannot be rolled back without breaking other phones/firmwares.
I really only have two options left on what the issue is. Either the rollback in the attached version fixes the problem, or its likely the problem is in the ZIP installer script or your recovery. Which recovery and version are you running?
(download removed, try newer one below)

@ShrekOpher btw I can't really see anything obvious in your logs either. But its a lot of logs

Chainfire said:
I am in fact looking at what has changed. The problem is that some of these things cannot be rolled back without breaking other phones/firmwares.
I really only have two options left on what the issue is. Either the rollback in the attached version fixes the problem, or its likely the problem is in the ZIP installer script or your recovery. Which recovery and version are you running?
Click to expand...
Click to collapse
I'm using TWRP 2.8.7.0. Trltetmo.
What can I do to help you get a log with the issue visable?

ShrekOpher said:
I'm using TWRP 2.8.7.0. Trltetmo.
What can I do to help you get a log with the issue visable?
Click to expand...
Click to collapse
Honestly, I don't know. I do need you to test that ZIP a few posts above, though.
If that one still doesn't work, I'll revert the ZIP installer script changes as well, see if that solves the issue.
EDIT: Something that might help is a log of the same device with 2.65 and without the signal issue

SUCESS the last zip SuperSU-v2.66-20160119182909 worked. Data and cell service is up and running great.

ShrekOpher said:
SUCESS the last zip SuperSU-v2.66-20160119182909 worked. Data and cell service is up and running great.
Click to expand...
Click to collapse
That is unfortunate. To further narrow it down, how about the attached ZIP ?
(download removed, try newer one below)

Chainfire said:
That is unfortunate. To further narrow it down, how about the attached ZIP ?
Click to expand...
Click to collapse
I'm using TWRP 2.8.7.0 for trltecan
Same results as ShrekOpher SuperSU-v2.66-20160119182909.zip works and restores cell data.
Just try'd SuperSU-v2.66-20160119205512.zip and it went back to no cell data/imei.
I would guess that what's killing it is changes in what gets patched to the boot img?

dbzgod said:
I'm using TWRP 2.8.7.0 for trltecan
Same results as ShrekOpher SuperSU-v2.66-20160119182909.zip works and restores cell data.
Just try'd SuperSU-v2.66-20160119205512.zip and it went back to no cell data/imei.
I would guess that what's killing it is changes in what gets patched to the boot img?
Click to expand...
Click to collapse
(also @ShrekOpher )
Please try the attached version.
What's killing it are the latest sepolicy patches. A patch that is needed for Android 6.0 to work is apparently messing with your Note4 (on 5.1). I'm trying to fix it so it works on both, and shouldn't pose a problem in the future for other devices.
Also, do you guys just get no cell signal, or also no Wi-Fi ?

Chainfire said:
(also @ShrekOpher )
Please try the attached version.
Also, do you guys just get no cell signal, or also no Wi-Fi ?
Click to expand...
Click to collapse
WiFi is working fine on all of them so far. The most current BETA-SuperSU-v2.66-20160119220513.zip - killed the data/cell signal again.

Aroma FlashFire ATT S5 finally!

Hi all,
Aroma is now working on our ATT S5 and S5 Active. through FlashFire emulation in their latest beta. Tested it, it works. Still stuck on lollipoop 5.0. but we can flash other Roms through aroma now.
Steps:
1. Start on muniz nce downgrade (4.4)
2. Towelroot
3. Install SuperSU
4. Install latest FlashFire.
5. Install muniz OF3 (I used deodexed prerooted) with flashfire. No need to wipe either, it's built into the install. Btw, change screen timeout to 10 min. Don't forget to install OA1 bootloader through download (using Odin) mode after rom installs. You can select reboot to download mode in flashfire.
Here's the link to the instructions for the S5 http://forum.xda-developers.com/att...w-to-update-to-g900aof2-5-0-keeproot-t3149146
And the active: http://forum.xda-developers.com/att...w-to-update-to-g870aof2-5-0-keeproot-t3161733
6. Select your g900f Android 5.0 custom (TouchWiz only) rom. I am currently on Alliance v10, installed through FlashFire (change screen timeout to 10 min.) aroma emulator. I did a wipe of cache, system and dalvik in flashfire and selected "factory wipe" in aroma. Do not select any kernels in aroma. Takes 10+ min. To boot, just wait. I installed SuperSU 3.76 after boot and I'm still rooted.
Any questions, just ask. I have tried some 5.1 and 6.0.1 and they are a no go (probably a kernel issue).
I have attached a screenshot, yes, it says g900f, it should, look at the baseband, it's ATT of3.
I don't take any credit for any of this. I just tried installing a few different Roms with this method. Give credit where credit is due: chainfire-supersu, muniz-many times thank you for your unblock and upgrades to 5.0 whilst keeping root, Alliance rom-thank you for your awesome rom, and yes it works great on g900a! I haven't tested it on the active, so if you try it, let us know.

Question
Hi dude, thanks for share this information, but, where can I get the OA3 kernel? - Are you sure about the kernel version?

Interesting anybody else try this?
Sent from my SAMSUNG-SM-G900A using Tapatalk

Any love for the S5 Active? (870A)
My Samsung S5 Active. Yes I read pages. Thanks

l0gandroid said:
Hi dude, thanks for share this information, but, where can I get the OA3 kernel? - Are you sure about the kernel version?
Click to expand...
Click to collapse
Yes. I'm sure it works. Take a look at the screenshot. I'm on it right now, used aroma to install.
I did make a mistake in the original post. You need to be on the oa1 bootloader, a link is included in muniz upgrade to of3 post (sorry about that). http://forum.xda-developers.com/att...w-to-update-to-g900aof2-5-0-keeproot-t3149146

gitardan17 said:
Any love for the S5 Active? (870A)
My Samsung S5 Active. Yes I read pages. Thanks
Click to expand...
Click to collapse
Should work for the active too. You have to use muniz rom, the latest one that still has root.

Here is the rom you need to be on for the active. http://forum.xda-developers.com/att...w-to-update-to-g870aof2-5-0-keeproot-t3161733
You need root, flashfire and BusyBox. Aroma is a little slow, however, and doesn't register check boxes right away, but it does work.

Discussions that don't involve actual development by the OP belong in the general section, not development. Please read the sticky titled "Rules for Posting in Development" and be sure to post in the correct section.
THREAD MOVED

How to update R1 to the latest OTA Update?

Hey All,
I'm looking for some help nito update this device to the latest OTA update. I have installed TWRP 3.0.2.0 that came with the dirtycow method. The device found the latest updated released in the past few days but when going to install it, it brings up the TWRP (which is how it should install). Now I don't mind if I can't grab this latest version due to whatever reason, but how would I go about updating the device? Currently it's running the stock version 6.1 6/17/2016.
Sorry if this has been answered somewhere, but still kinda new with Android devices and the whole rooting process. I'd like to be able to keep TWRP if at all possible and keep this device updated. Also I saw there was a updated TWRP released, how would I go about updating the recovery?
Thanks a lot for the help anyone can give!

KyleStilkey said:
Hey All,
I'm looking for some help nito update this device to the latest OTA update. I have installed TWRP 3.0.2.0 that came with the dirtycow method. The device found the latest updated released in the past few days but when going to install it, it brings up the TWRP (which is how it should install). Now I don't mind if I can't grab this latest version due to whatever reason, but how would I go about updating the device? Currently it's running the stock version 6.1 6/17/2016.
Sorry if this has been answered somewhere, but still kinda new with Android devices and the whole rooting process. I'd like to be able to keep TWRP if at all possible and keep this device updated. Also I saw there was a updated TWRP released, how would I go about updating the recovery?
Thanks a lot for the help anyone can give!
Click to expand...
Click to collapse
As long as you have twrp installed, you can install the modified update 8.3 i just finished.
==>>it is here

mrmazak said:
As long as you have twrp installed, you can install the modified update 8.3 i just finished.
==>>it is here
Click to expand...
Click to collapse
Already tried it and it doesn't work. She uses the phone to play Pokemon Go and sadly the modified version you've made gives the error that the device or software is not supported. I believe this is due to the method you are using to remove the ads and custom changes made to the ROM, which I don't personally care if the phone has them or not. I'm wanting to install OTA updates without any heavy modifications made, just the ability to keep TWRP but have an updated phone.

KyleStilkey said:
Already tried it and it doesn't work. She uses the phone to play Pokemon Go and sadly the modified version you've made gives the error that the device or software is not supported. I believe this is due to the method you are using to remove the ads and custom changes made to the ROM, which I don't personally care if the phone has them or not. I'm wanting to install OTA updates without any heavy modifications made, just the ability to keep TWRP but have an updated phone.
Click to expand...
Click to collapse
Will be redoing the patch again and making not pre-rooted version. But if your app is not working on the modified 7.4.2 there is nothing I can do.

mrmazak said:
Will be redoing the patch again and making not predicted version. But if your app is not working on the modified 7.4.2 there is nothing I can do.
Click to expand...
Click to collapse
I see V8 but do not see a 7.4.2 on there.
EDIT: Nevermind I found it, will try the modified 7.4.2 and get back to you.

KyleStilkey said:
I see V8 but do not see a 7.4.2 on there.
EDIT: Nevermind I found it, will try the modified 7.4.2 and get back to you.
Click to expand...
Click to collapse
Non-rooted rom finished. uploaded to android file host.
Link and description in my other post.
==>>Unrooted rom

mrmazak said:
Non-rooted rom finished. uploaded to android file host.
Link and description in my other post.
==>>Unrooted rom
Click to expand...
Click to collapse
I want to say thank you a lot, this worked wonderfully! Only issue is Google Plus doesn't work (not a huge deal for the wife) but everything else is working great!
One last question, what is the recommended TWRP to use with this phone, I currently have the 3.0.2.0 Vampire version installed.

KyleStilkey said:
I want to say thank you a lot, this worked wonderfully! Only issue is Google Plus doesn't work (not a huge deal for the wife) but everything else is working great!
One last question, what is the recommended TWRP to use with this phone, I currently have the 3.0.2.0 Vampire version installed.
Click to expand...
Click to collapse
I have seen it mentioned that Google + does not work on 8.3 in general not just this modified one.
That recovery is the one I use and has advantage over the other one (lopestom's versio) in that in recovery you can use external sdcard and also mtp connection.