Related
I was browsing the Web for the new update for the oneplus one and come across this http://www.androidpolice.com/2014/0...-android-4-4-4-begins-rolling-out-to-devices/ thanks to Android police they have an untouched official update available which I was able to download and install directly from the stock oneplus one recovery, no push through adb needed. The download is located at the bottom of the page, 4 different mirrors. I used the last one though mega.
-please note-
I have an unlocked bootloader.
I am (not) rooted.
I do (not) have a custom recovery. I am using stock.
My system is not modified at all
After you install in recovery, another small update will appear which is safe.
It worked perfectly for me, I hope it is the same for all of you.
-steps-
1. Download from one of the 4 mirrors.
2. Save to a location you will remember.
3. Reboot into recovery.
4. Press apply update.
5. Click the option below push through adb.
6. Find the zip you download.
7. Wait for install.
8. Wipe cache.
9. Reboot system.
10. When system reboots it will optimize apps. Then there will be a system update available, download, install, and you are officially on the latest cyanogenmod 11s.
-----------------------------------------
Thankyou for reading this post I made I hope all of you enjoy the new update. I was a little upset because I was getting the screen Ghost touches and my screen was unresponsive, but this update has improved the ghost touches, but my screen occasionally doesn't work in the middle. But a reboot fixes it temporary. After the next update the screen touch issues will be resolved. Can't wait! ^_^
Does the tiny follow up update change any version number or build number?
Please go here as there is already a thread on this...http://forum.xda-developers.com/oneplus-one/general/cm-11s-30o-ota-slowly-rolling-t2844689
CAUTION TO NOT LOOSE TWRP
I read two posts that say v21, now again on V8.5, put the stock recovery back instead of twrp. This is probably a side effect of a fresh stock /system and wipe of /data.
As a preventive step, when done flashing and wiping reboot to recovery FIRST, before booting the system It will allow recovery to handle removing the recovery-from-boot.p that flashes stock recovery.
I just patched the modified V7.4.2 up to the newly released 8.3 now 8.4. 8.5, 8.7,9.0 -V9.2 Patch
New update has been made from V17 to V21 of the non prime version of R1-HD, Non prime is behind on security patch (2017-05-05)
Copied ROM from phone and made twrp install ROM from it.
* No preloader change (official updates change the preloader to block your ability to use sp flash tools for rom flashing)
* No lk.bin change __ this part is what allows you to choose boot options(boot menu when power and volume pressed together)
* No "FOTA" app Fota has now been left in to make it easier to get next update, if that ever happens.
* No opera browser
* No adds (removed in the modified 7.4.2)
* Custom boot logo (only done on v8.3, there was no interest in this so abandoned)
--Newer versions of rom left stock, Leaving mods up to user.
** while it is not necessary to do a wipe with this ROM, I still recommend it.
**Thanks:
** @vampirefo needed his patched v7.4.2 in order to apply this new 8.3 patch and again for 8.4
** @ColtonDRG OR @jasonmerc I do not remember which one made it: For the image used in the custom logo
and the modified zip is here .
Roms are rootable with SuperSU, flashed in twrp after install. Must be done in systemless mode. In order to patch system veridy in boot.img
Logo update did not work on original rom changing link to updated version
BLU rolled v8.3 back to v7.4.2 because of app compatability issues. V8.4 is there fixed release. Both 8.3 and 8.4 are modified prime roms with ads stripped
V21 is the non prime update.
Unmodified V6.1
==>NON-ROOTED-logo-not-replaced-modified-V8.3
==>Fixed Logo modified NON_ROOTED V8.3
==>>modified V8.4
==>>modified V8.5
==>>Full with Ads V8.7
==>>Full with Ads V9.0
==>>Patch For V9.2 must be flashed on top of fresh V9.0
****Run debloat ==>script to remove ads if you need/ want to, or remove from zip before flashing ****
alt. manual example: before reboot, while still in twrp. Select mount and put checkmark next to system. Then run these two commands in adb terminal
Code:
adb shell rm /system/priv-app/com.amazon.*/com.amazon.*.apk
adb shell rm /system/app/Adups*/*.apk
==>>Modified V21
** stand alone logo installs
I flashed this but I didn't get the custom boot logo.
mendelgordon said:
I flashed this but I didn't get the custom boot logo.
Click to expand...
Click to collapse
I had that happen to my second phone too.
I don't have an explanation yet.
I even made a separate update.zip , that one didn't make the logo change either. I did eventually change it with sp flash tool.
I tried with both recoveries.
and multiple /dev location formats. and for whatever reason my one phone did not accept the logo change from recovery.
And the other test phone it worked.
mendelgordon said:
I flashed this but I didn't get the custom boot logo.
Click to expand...
Click to collapse
Neither did I but it all seems to be working fine
Been using this for about a day now, likewise no custom boot logo, but that's fine. Otherwise, it's been running super well. A lot better than the previous mostly stock version did for me with the bloatware APKs removed after the install. A lot of the general idiosyncrasies of the previous version of the stock rom seem to have gone away for me. It seemed to have weird storage management issues, errors moving to SD, broken symlinks that prevent apps from moving or being reinstalled, and a lot of other little non-storage issues, but so far, none off that here.
Long story short, good work! I hope we eventually see proper 7.x roms through some of the efforts going on, but in the meanwhile, your work here has made life a little bit better on 6.
It seems that I was able to get the logo.bin to update when I applied the original update patch, but not when I used the same line in the rom install.
It is no big deal that it did not work, I was just trying to make it look different at boot time.
edit:
I think i found the problem with the logo not updating.
i used the update-binary from the official patch update. (the one that allowed the logo to change the first time)
and it changes . so since the ROM seems to install the way it is , only the logo didn't flash I put it in a separate update.zip if anyone is interested in it.
EDIT 2:
clarification.
It was not so much the binary allowing the logo to change but the format of the partition location I had been using that needed that binary.
Further test had shown me that I could have used the binary I was using but just change the partition naming line
Code:
package_extract_file("logo.bin", "/dev/block/mmcblk0p9")
the above code works with the same update-binary as rom install
But I was using
Code:
package_extract_file("logo.bin", "/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo")
Taken straight from the official patch, and thats why it needed the update-binary also.
I dont know what is different in the binary other than , major size difference.
The powered by me logo was just a test file to see changes in the logo.
**logo-update is same as composite but with alt updater-binary
**composite-logo screenshot is in op
**stock logo will return to original BLU logo
mrmazak said:
It seems that I was able to get the logo.bin to update when I applied the original update patch, but not when I used the same line in the rom install.
It is no big deal that it did not work, I was just trying to make it look different at boot time.
edit:
I think i found the problem with the logo not updating.
i used the update-binary from the official patch update. (the one that allowed the logo to change the first time)
and it changes . so since the ROM seems to install the way it is , only the logo didn't flash I put it in a separate update.zip if anyone is interested in it.
EDIT 2:
clarification.
It was not so much the binary allowing the logo to change but the format of the partition location I had been using that needed that binary.
Further test had shown me that I could have used the binary I was using but just change the partition naming line
Code:
package_extract_file("logo.bin", "/dev/block/mmcblk0p9")
the above code works with the same update-binary as rom install
But I was using
Code:
package_extract_file("logo.bin", "/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo")
Taken straight from the official patch, and thats why it needed the update-binary also.
I dont know what is different in the binary other than , major size difference.
The powered by me logo was just a test file to see changes in the logo.
Click to expand...
Click to collapse
Hahaha the scribbled "ME" is hilarious. Your work is awesome, I don't think anyone using this rom will have an issue with the boot image but thanks for being so helpful and explaining.
P. S. Do you have any plans with the Nougat update?
Serenitybs said:
Hahaha the scribbled "ME" is hilarious. Your work is awesome, I don't think anyone using this rom will have an issue with the boot image but thanks for being so helpful and explaining.
P. S. Do you have any plans with the Nougat update?
Click to expand...
Click to collapse
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )
linuxsociety said:
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )
Click to expand...
Click to collapse
Somebody already tried this out
linuxsociety said:
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )
Click to expand...
Click to collapse
It was just wishful thinking. I have no idea how all of this is done. All I know is @mrmazak has helped me to fall in love with my phone again with this V8.3. The 7.4.2 did seem a bit buggy for my phone but this update works beautifully and I didn't even root it. If this remains true I will be happy with this phone for awhile even on 6.0
Really confused right now.
I was browsing through the settings menus. And found in the Settings-security- menu a toggle labeled "quick boot" ( not to be confused with "fastboot") . I enabled it then rebooted to see if it booted quicker. Didn't seem to make much if any difference. So I went back to turn it back off. And it wasn't there. I checked in my other phone , it wasn't there on that one either.
Did any body see this menu item, and if so where is is it?
Edit 1:
Few more power off , power on cycles to compare times. With other phone and defiantly seems to have turned on some faster boot option.
This phone goes from off to on in 5-6 seconds other phone takes about 20.
Edit 2:
OK , I panicked for a minute.
Couldn't find the setting and thought that it was another way to block sp flash tool by preventing you from ever being fully powered off.
But the setting was in accessibility not security.
Mrmazak, first of all, thanks for the ROM, installed it yesterday. But I have a problem with SELinuxModeChanger app. First, I'm getting a security warning when installing it, then - when running it. And another message, with this app running - "can't obtain root", although SuperSU shows its status with green #, like every other app it gives root privileges to. On my other Prime phone, running 6.1 out of the box stock ROM, FM radio works just fine with SELinuxModeChanger app behaving flawlessly (no security warnings whatsoever). Any ideas?
detroitredwings said:
Mrmazak, first of all, thanks for the ROM, installed it yesterday. But I have a problem with SELinuxModeChanger app. First, I'm getting a security warning when installing it, then - when running it. And another message, with this app running - "can't obtain root", although SuperSU shows its status with green #, like every other app it gives root privileges to. On my other Prime phone, running 6.1 out of the box stock ROM, FM radio works just fine with SELinuxModeChanger app behaving flawlessly (no security warnings whatsoever). Any ideas?
Click to expand...
Click to collapse
The mode changer app is technically a security issue. I did have that warning a few times when using mode changer app from the XDA thread of the developer, then when I used the app downloaded from f-droid it worked with systemless root and didn't give the security warning.
The app downloaded from f-droid worked for me as well, many thanks!
Big thanks for getting this out, updated from previous debloated, rooted version to this modified 8.3 stock rom, rooted with SU v2.79 SR3, all is good - only App that won't show up nor install, even tried the ones off APK Mirror site - is my Dunkin Donuts App, LOL. Play Store now said it's not compatible and the APK started to install then failed - any ideas or suggestions on what to do ??
Otherwise, it's all good - I will survive without DD App, just run that from another device when I need my caffeine fix.
Letitride said:
Big thanks for getting this out, updated from previous debloated, rooted version to this modified 8.3 stock rom, rooted with SU v2.79 SR3, all is good - only App that won't show up nor install, even tried the ones off APK Mirror site - is my Dunkin Donuts App, LOL. Play Store now said it's not compatible and the APK started to install then failed - any ideas or suggestions on what to do ??
Otherwise, it's all good - I will survive without DD App, just run that from another device when I need my caffeine fix.
Click to expand...
Click to collapse
I also had an app that previously work, say is not compatible now.
Maybe has to do with apps that have links to pay accounts. And that has something to do with trustzone. (Tee1 & tee2)
Those sections I left out of the update. I will add it back in and test. Update when I do. It is also possible this problem is why Blu rolled back there update.
**EDIT**
well that didn't go well at all.
I flashed the new trustzone.bin files from the official update. Now phone no longer turns on and no longer connects to flash tool
**EDIT 2**
After much persistence and many failed attempts to get phone recognized in pc again. Finnaly got to a point that phone was cycling between "preloader" driver and "usb serial device", and with careful timing was able to start sp flash tool at just right time and the flashing back to original trustzone files seems to have recovered phone.
for the record i am not sure what steps made it work. But I was shifting back and forth between leaving phone sit on charge, then on charge with rubber band wrapped around power button, then not plugged in , and not plugged in with rubber band on power button.
Okay... persistence is key in customization, i guess! I am getting somewhere here!
mrmazak said:
The first link is needed to get phone unlocked so you can install twrp.
Click to expand...
Click to collapse
Finally got thru the steps in order (1-2-3-4) then Step (5) and sub-step 1. I can also boot to TWRP.
Now this brings me to this thread, 8.3 Stock ROM. The thread assumes one knows how to install it and I suspect this could be as easy as uploading it to a folder in the phone then booting to TWRP and INSTALLING the ZIP file? Could someone clarify the steps to install this 8.3 ROM?
Thanks!
OldSkewler said:
Okay... persistence is key in customization, i guess! I am getting somewhere here!
Finally got thru the steps in order (1-2-3-4) then Step (5) and sub-step 1. I can also boot to TWRP.
Now this brings me to this thread, 8.3 Stock ROM. The thread assumes one knows how to install it and I suspect this could be as easy as uploading it to a folder in the phone then booting to TWRP and INSTALLING the ZIP file? Could someone clarify the steps to install this 8.3 ROM?
Thanks!
Click to expand...
Click to collapse
Yes. You are correct
Either put the zip file on external sd card , put card into phone boot into recovery mode and install , or put file directly onto phone .
Many ways to do that.
Easiest is to copy to phone while phone is connected to PC.
Cam also download file from internet with your phone.
Bottom line is get zip file to the phone boot to recovery and install
Anyone else having wifi issues after upgrading? While watching videos it seems the internet cuts out. The phone says it's still connected but I have to turn wifi off and back on for anything to work. Could be my router also but it didn't seem to be doing this until I installed 8.3
mrmazak said:
Yes. You are correct
Either put the zip file on external sd card , put card into phone boot into recovery mode and install , or put file directly onto phone .
Easiest is to copy to phone while phone is connected to PC.
Bottom line is get zip file to the phone boot to recovery and install
Click to expand...
Click to collapse
Right on man! I am officially running 8.3 ROM with April 5th 2017 Security Patch Level! Geez.. it was not easy but I got this working!
MrMazak, I followed all your instructions on both links, so could you tell me what exactly I have on my phone? Is it rooted? Bootloader Unlocked? The phone seems to be working fine but I don't know what level of access I have. Honestly I don't even know exactly what the differences between all these terms are.
Also, do I have or not SU? One of the steps under the .bat I believe install it. How do I access it?
Thanks again!
---------- Post added at 10:19 PM ---------- Previous post was at 10:18 PM ----------
Weasel0 said:
Anyone else having wifi issues after upgrading? While watching videos it seems the internet cuts out. The phone says it's still connected but I have to turn wifi off and back on for anything to work. Could be my router also but it didn't seem to be doing this until I installed 8.3
Click to expand...
Click to collapse
My install is pretty fresh, couple of hours, but as far as I can tell all is working fine with Wifi, As a matter of fact this is a new device only connected with Wifi and no SIM Card.... internet works fine.
Sorry if this is the wrong section, basically my S5 (SM G900F) is stuck on Android 5.0, there is no updates for it OTA or on kies, so I went to sammobile to download the marshmallow update searched in my countries carrier, (Lebanon) but it seems there is only the 4.4.2 version. So I don't know what to do, I'm kinda new to all this so excuse my ignorance on the matter.
What if I downloaded the UK firmware? Does it matter at all?
Shadz01 said:
Sorry if this is the wrong section, basically my S5 (SM G900F) is stuck on Android 5.0, there is no updates for it OTA or on kies, so I went to sammobile to download the marshmallow update searched in my countries carrier, (Lebanon) but it seems there is only the 4.4.2 version. So I don't know what to do, I'm kinda new to all this so excuse my ignorance on the matter.
What if I downloaded the UK firmware? Does it matter at all?
Click to expand...
Click to collapse
If you don't really care whether it's Touchwiz or not, maybe try flashing TWRP via Odin and flashing a Lineage 14.1 ROM? (I don't take responsibility if you brick your phone, please follow this guide if you're new and proceed with caution.
Guide: https://www.theandroidsoul.com/how-to-install-twrp-recovery-using-odin
Download link for Odin: https://odindownload.com/download/Odin3_v3.12.3.zip
Download Link for TWRP (G900F / KLTE): https://eu.dl.twrp.me/klte/twrp-3.2.1-0-klte.img.tar.html
Official Lineage 14.1 Build Downloads : https://download.lineageos.org/klte
Open Google Apps Link: http://opengapps.org/ (Choose: ARM > 7.1 > Pico)
The reason I choose LOS 14.1 is because it's very stable and Nougat based. LOS 15.1 is not ready as a reliable daily yet.
(I repeat, I do not take responsibility if you try this and end up bricking your device.)
@Shadz01 it doesn't matter at all what country it says. Just grab the latest 6.0.1 from here and flash away.
CoreyOS said:
If you don't really care whether it's Touchwiz or not, maybe try flashing TWRP via Odin and flashing a Lineage 14.1 ROM? (I don't take responsibility if you brick your phone, please follow this guide if you're new and proceed with caution.
Guide: https://www.theandroidsoul.com/how-to-install-twrp-recovery-using-odin
Download link for Odin: https://odindownload.com/download/Odin3_v3.12.3.zip
Download Link for TWRP (G900F / KLTE): https://eu.dl.twrp.me/klte/twrp-3.2.1-0-klte.img.tar.html
Official Lineage 14.1 Build Downloads : https://download.lineageos.org/klte
Open Google Apps Link: http://opengapps.org/ (Choose: ARM > 7.1 > Pico)
The reason I choose LOS 14.1 is because it's very stable and Nougat based. LOS 15.1 is not ready as a reliable daily yet.
(I repeat, I do not take responsibility if you try this and end up bricking your device.)
Click to expand...
Click to collapse
Are you sure about the guide you linked for installing TWRP? Nowhere does it say to install "samsung driver" which I have seen to be a step in many other tutorials.
Also, in step 3, when the guide says to enable OEM unlock does it mean the enable USB debugging? Because I can't find any checkbox for it in the developer option.
What is this Google Apps link? Is it the same as LOS (the link you provided at first) ?
Do I need to root my device to flash LineageOs via TWRP ? Because it's a custom ROM.
I've heard lineageos drain the battery, or at least is worse than the Stock ROM, also it makes the camera horrible because of improper drivers.
Thank you.
koragg97 said:
@Shadz01 it doesn't matter at all what country it says. Just grab the latest 6.0.1 from here and flash away.
Click to expand...
Click to collapse
I already downloaded it from this thread, it doesn't state which country/carrier https://forum.xda-developers.com/ga...m-official-android-6-0-1-marshmallow-t3319376
Can you check if it's the right one? Thank you.
Shadz01 said:
What if I downloaded the UK firmware? Does it matter at all?
Click to expand...
Click to collapse
Yes, it matters. But not much.
The phone will work but you may lose language and APN settings at least.
Have a look at this ROM.
It's for SM-G900F, it's the most recent ROM for this phone, it's "stock-based" ROM and it contains LEB CSC code you need.
I'd install it without modification (root=noroot) for the first time.
Read several leading posts in the thread to learn how to deal with all that stuff.
bbsc said:
Yes, it matters. But not much.
The phone will work but you may lose language and APN settings at least.
Have a look at this ROM.
It's for SM-G900F, it's the most recent ROM for this phone, it's "stock-based" ROM and it contains LEB CSC code you need.
I'd install it without modification (root=noroot) for the first time.
Read several leading posts in the thread to learn how to deal with all that stuff.
Click to expand...
Click to collapse
If I want the one without the modification, no root, I change the name of the file to "G900Fxxx_DevBase_v4.x_noroot.zip" or "G900FXXU1CRA2_DevBase_v4.6_noroot.zip" ?
I install it with Odin no need for TWRP right?
Shadz01 said:
If I want the one without the modification, no root, I change the name of the file to "G900Fxxx_DevBase_v4.x_noroot.zip" or "G900FXXU1CRA2_DevBase_v4.6_noroot.zip" ?
I install it with Odin no need for TWRP right?
Click to expand...
Click to collapse
There's a small file options.prop inside the zip with the ROM.
Pull it out, modify and put into the root of phone's memory (have a look at the manual).
There are 2 lines only which can be modified:
root=noroot
CSC=LEB
Use Notepad++ or Notepad2 or some other text editor which can handle linux LF, not only Windows CR LF.
The ROM is installed from TWRP.
You'll need to flash TWRP, bootloader and modem (from Odin), then install the ROM.
Shadz01 said:
Are you sure about the guide you linked for installing TWRP? Nowhere does it say to install "samsung driver" which I have seen to be a step in many other tutorials.
Also, in step 3, when the guide says to enable OEM unlock does it mean the enable USB debugging? Because I can't find any checkbox for it in the developer option.
What is this Google Apps link? Is it the same as LOS (the link you provided at first) ?
Do I need to root my device to flash LineageOs via TWRP ? Because it's a custom ROM.
I've heard lineageos drain the battery, or at least is worse than the Stock ROM, also it makes the camera horrible because of improper drivers.
Thank you.
Click to expand...
Click to collapse
I don't mean to sound patronising but it's just common sense to have Samsung drivers installed when using your computer to communicate with your device. (I did not thoroughly check through this guide but only linked it as I followed this before when I first began flashing custom firmware/ROMs to my devices myself.
Also, the google apps link is to get Google play functionality on Lineage OS as it does not come with any Google functionality whatsoever when installed standalone. This adds Google Play Store and Google Play Services to the ROM. You can install Yalp store from F-Droid if you do not wish to install Google apps but please note if you do decide to go without Google apps, you will not have contacts sync so you will have to export and import your contacts manually using a vcard file.
Apps that are dependent on SafetyNet and GPlay Services such as Snapchat also do not work without flashing the Google apps.
Also I only suggested Pico OpenGapps as it only comes with the bare minimum functionality to get Google Play Services running. It's up to you then what you install.
No, you do not need to root your device to flash anything via TWRP.
TWRP is used to flash root tools such as SuperSU or Magisk, it is the control panel to your hardware pretty much.
So...
Flashing TWRP:
1, Install Samsung Smart Switch or USB drivers (If smart switch doesn't work try these:
http://developer.samsung.com/common/download/check.do?actId=698)
2, Download Odin and the TWRP image for your device (Links in my OP)
3, Turn your phone off, hold Power + Home + Volume Down to enter Download Mode. (Follow instructions given on screen once download mode is active)
4, Plug your phone in via a reliable USB port and cable
5, Run ODIN as Admin and tick the AP box and choose the TWRP .tar file by clicking on AP.
6, Click Start at the bottom of ODIN and wait for the recovery to be flashed.
7, Now as your device reboots, hold Power + Home + Volume Up to enter your newly flashed TWRP recovery.
Optional ** If successful, make a backup of your original firmware using the backup section in case you need to get back to it in future.
Installing the ROM:
1, Within TWRP, go to Wipe > Advanced Wipe and tick "Cache", Data" and "System". (You will lose all app settings if you haven't backed up)
2, Go to Mount > Mount USB Storage and plug into PC in order to copy the rom, gapps and other files to your internal storage.
3, Unmount storage, go to "Install" from the main menu and select the ROM and flash it. (Use "add more zips" option to select gapps and others)
4, Once all has installed reboot and fingers crossed you'll see the Lineage boot animation :good:
Like I said yesterday, I take no responsibility, just trying to help out.
Hope you get good results.
It's not all bad if you device won't boot if something goes wrong, you can always just flash the original firmware via ODIN which is provided by Sammobile. (Been there, bricked that, fixed that etc etc)
Keep me posted!
---------- Post added at 11:14 AM ---------- Previous post was at 11:09 AM ----------
Shadz01 said:
Are you sure about the guide you linked for installing TWRP? Nowhere does it say to install "samsung driver" which I have seen to be a step in many other tutorials.
Also, in step 3, when the guide says to enable OEM unlock does it mean the enable USB debugging? Because I can't find any checkbox for it in the developer option.
What is this Google Apps link? Is it the same as LOS (the link you provided at first) ?
Do I need to root my device to flash LineageOs via TWRP ? Because it's a custom ROM.
I've heard lineageos drain the battery, or at least is worse than the Stock ROM, also it makes the camera horrible because of improper drivers.
Thank you.
Click to expand...
Click to collapse
Forgot to mention, also Enable OEM Unlock I've noticed is only present in more recent devices. If you do not have that option and you have thoroughly checked it does not exist, you should not have to worry about it. (Please don't take that ass 100% gospel. I just noticed my Samsung J3 has it (2016 mid) and my S5 does not (2014 Flag)... Up to you, just do some digging but I don't have taht option and I have never been FRP locked... (Only on my J3 )
CoreyOS said:
I don't mean to sound patronising but it's just common sense to have Samsung drivers installed when using your computer to communicate with your device. (I did not thoroughly check through this guide but only linked it as I followed this before when I first began flashing custom firmware/ROMs to my devices myself.
Also, the google apps link is to get Google play functionality on Lineage OS as it does not come with any Google functionality whatsoever when installed standalone. This adds Google Play Store and Google Play Services to the ROM. You can install Yalp store from F-Droid if you do not wish to install Google apps but please note if you do decide to go without Google apps, you will not have contacts sync so you will have to export and import your contacts manually using a vcard file.
Apps that are dependent on SafetyNet and GPlay Services such as Snapchat also do not work without flashing the Google apps.
Also I only suggested Pico OpenGapps as it only comes with the bare minimum functionality to get Google Play Services running. It's up to you then what you install.
No, you do not need to root your device to flash anything via TWRP.
TWRP is used to flash root tools such as SuperSU or Magisk, it is the control panel to your hardware pretty much.
So...
Flashing TWRP:
1, Install Samsung Smart Switch or USB drivers (If smart switch doesn't work try these:
http://developer.samsung.com/common/download/check.do?actId=698)
2, Download Odin and the TWRP image for your device (Links in my OP)
3, Turn your phone off, hold Power + Home + Volume Down to enter Download Mode. (Follow instructions given on screen once download mode is active)
4, Plug your phone in via a reliable USB port and cable
5, Run ODIN as Admin and tick the AP box and choose the TWRP .tar file by clicking on AP.
6, Click Start at the bottom of ODIN and wait for the recovery to be flashed.
7, Now as your device reboots, hold Power + Home + Volume Up to enter your newly flashed TWRP recovery.
Optional ** If successful, make a backup of your original firmware using the backup section in case you need to get back to it in future.
Installing the ROM:
1, Within TWRP, go to Wipe > Advanced Wipe and tick "Cache", Data" and "System". (You will lose all app settings if you haven't backed up)
2, Go to Mount > Mount USB Storage and plug into PC in order to copy the rom, gapps and other files to your internal storage.
3, Unmount storage, go to "Install" from the main menu and select the ROM and flash it. (Use "add more zips" option to select gapps and others)
4, Once all has installed reboot and fingers crossed you'll see the Lineage boot animation :good:
Like I said yesterday, I take no responsibility, just trying to help out.
Hope you get good results.
It's not all bad if you device won't boot if something goes wrong, you can always just flash the original firmware via ODIN which is provided by Sammobile. (Been there, bricked that, fixed that etc etc)
Keep me posted!
---------- Post added at 11:14 AM ---------- Previous post was at 11:09 AM ----------
Forgot to mention, also Enable OEM Unlock I've noticed is only present in more recent devices. If you do not have that option and you have thoroughly checked it does not exist, you should not have to worry about it. (Please don't take that ass 100% gospel. I just noticed my Samsung J3 has it (2016 mid) and my S5 does not (2014 Flag)... Up to you, just do some digging but I don't have taht option and I have never been FRP locked... (Only on my J3 )
Click to expand...
Click to collapse
Thanks so much for your help, I installed TWRP with no problem. Does a nandroid backup include pictures and videos? Have you ever experienced with LOS battery drainage or worse than the stock ROM?
Shadz01 said:
Thanks so much for your help, I installed TWRP with no problem. Does a nandroid backup include pictures and videos? Have you ever experienced with LOS battery drainage or worse than the stock ROM?
Click to expand...
Click to collapse
No it's usually better as there's less services running and it's official and stable (still a Nighlty) but personally I can't use TW it's awful and LOS sh*ts all over stock.
A great way of saving battery like I do is running LOS without GAPPS. Or install AICP and enable the performance mode toggle in quick settings.
If you would like a link to AICP let me know, it's built from Lineage and is very smooth and optimized. (Make sure to enable force scrolling cache in AICP extras app).
And no problem, it's my hobby and I also love helping when I can.
EDIT: Your personal files will not be lost as long as you do not wipe internal and external storage (MicroSD)
For future, if you get to the stage where you change your data and cache partitions to F2FS make sure you copy your files to PC... For some reason it wipes internal storage when you format the data partition.
CoreyOS said:
No it's usually better as there's less services running and it's official and stable (still a Nighlty) but personally I can't use TW it's awful and LOS sh*ts all over stock.
A great way of saving battery like I do is running LOS without GAPPS. Or install AICP and enable the performance mode toggle in quick settings.
If you would like a link to AICP let me know, it's built from Lineage and is very smooth and optimized. (Make sure to enable force scrolling cache in AICP extras app).
And no problem, it's my hobby and I also love helping when I can.
EDIT: Your personal files will not be lost as long as you do not wipe internal and external storage (MicroSD)
For future, if you get to the stage where you change your data and cache partitions to F2FS make sure you copy your files to PC... For some reason it wipes internal storage when you format the data partition.
Click to expand...
Click to collapse
I already flashed LOS, very smooth, I like it, but the battery sucks. I lose 1 % every one and a half minute when I use my phone. Is this AICP a ROM or some mode? I never tried updating my modem and bootloader, would that help the battery? Or maybe installing a kernel manager?
Shadz01 said:
I already flashed LOS, very smooth, I like it, but the battery sucks. I lose 1 % every one and a half minute when I use my phone. Is this AICP a ROM or some mode? I never tried updating my modem and bootloader, would that help the battery? Or maybe installing a kernel manager?
Click to expand...
Click to collapse
Yes it's another rom. It uses Lineage 14.1 as a base but has its own tweaks.
I find what you're saying to be very true too but I can put up with that. I just cannot tolerate anything other than stock AOSP Android.
Try Greenify, I use it to hibernate Facebook and a few other apps that suck the life out of my phone...
Hi. I have a Samsung Galaxy Tab 4 sm-t530nu and it is running on a really old Android version so I am unable to use some of the apps I would like to use. I have searched the internet and I am really finding it difficult to find an easy explanation on how to update it to the latest android version ( currently sit's at 5.0.2 and wont auto update any further ). I have seen some YouTube videos but most of the links they refer to are old and the video quality is quite poor. Can anyone direct me to somewhere that can easily explain what I need to do. Really sorry but I am not very knowledgeable when it comes to android things. Please help and much appreciated.
sandstorm_uk said:
Can anyone direct me to somewhere that can easily explain what I need to do.
Click to expand...
Click to collapse
You are at the right place. Before you can install a new version of Android, you need to install twrp, a replacement for the stock recovery program on your tablet. For most people this is the hardest part of the whole process. If and when you install twrp, installing a new OS is a piece of cake. Please watch this Youtube video:
Samsung Galaxy Tab 4 10.1 T530 How to install Twrp Recovery Tutorial
After watching the video and you still want to proceed, here are the links for where and what to download to install twrp:
Samsung Android USB Driver | Samsung Developers
You need the driver only if you are developing on Windows and want to connect a Samsung Android device to your development environment over USB.
developer.samsung.com
Downloads for : Samsung Galaxy Tab 4 10.1 | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
download twrp-3.6.0_9-0-matisse.tar (Odin likes tar)
Odin download latest version 2021 / 2022 / 2023 - Odin 3.14.4
Samsung Odin tool is a third-party utility that is designed to resolve software-related issues in Android mobile phones. Especially in Samsung handsets. It wasn’t developed for the public at first. However, with time, the software tool becomes available to the public as well. If you own a car, a...
odin3download.com
After you install twrp and are comfortable using the program, reply back and we'll guide you thru the remainder of the process to update Android.
Hi. Thank you so much for the response. So I have TWRP installed now and I am happy to continue. Very much appreciated. Great forum BTW.
Thanks
sandstorm_uk said:
I have TWRP installed now and I am happy to continue.
Click to expand...
Click to collapse
Download the latest LineageOS 18.1 (Android 11) for YOUR tablet here:
lineage-18.1-20220312-UNOFFICIAL-matissewifi.zip | by matteo0026 for Galaxy Tab 4 10.1
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Go here for the Google Apps:
The Open GApps Project
OpenGApps.org offers information and pre-built packages of The Open GApps Project. The Open GApps Project is an open-source effort to script the automatic generation of up-to-date Google Apps packages. All Android versions and platforms supported.
opengapps.org
Very important: Select ARM, Android 11, nano
The website will prepare the ZIP for download
This top and first message will guide you thru the install process:
[ROM][UNOFFICIAL][matisse][millet] LineageOS 18.1
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device. LineageOS is based on the Android Open Source Project with extra...
forum.xda-developers.com
Make sure your tablet is fully charged before flashing. Drag off to your desktop computer any files you want to save, pictures, DCIM, sound. Disable screen timeout in TWRP settings, screen. Installing the new ROM will go by fast. The Google Apps take time to install. Just sit and watch. When the tablet reboots again just sit and watch, lots of things happening under the hood. There may appear a Google app error. Ignore it. It only happens once.
Excellent thanks. I have one query. When Install the above , can I do it without a SD Card ?. Can I drag the files direct to the Tablet ?
Thanks again ,massive help.
Hi. All sorted and go it all installed. Thank you so much for the help and this is a great forum. Appreciate that it was a professional and easy to understand response and no trolling , which is rife these days. Thanks for the effort and time and really really glad I came across this forum. @SteinbeckFan ; thank you so much.
Congrats sandstorm I don't know what I am doing wrong but I have flashed 11 a few times and when I get to set up I get stuck at "can't find sim" so I go back to 5.02 and try again with the same result. Any suggestions for where I am going wrong or step by step to try again?
Just completed again - got it working - picked the correct Gappa - all done
SteinbeckFan said:
You are at the right place. Before you can install a new version of Android, you need to install twrp, a replacement for the stock recovery program on your tablet. For most people this is the hardest part of the whole process. If and when you install twrp, installing a new OS is a piece of cake. Please watch this Youtube video:
...
Click to expand...
Click to collapse
Thanks so much for the links and making it clear! I was able to do it super easily.
Note) I did have to chose an older TWRP version in order to be able to download it from Android File Host.
EDIT: One thing I needed to do extra was flash Magisk to get root (don't bother trying any of the samfirm, frija, samloader, etc (region code XAR) or CF-AutoRoot, SuperSU). To do so, grab the magisk.apk from the GitHub releases, then rename the extension to .zip, then flash it through TWRP. Make sure to also flash this after: "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" here: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389 and rename it to "Disable_ForceEncrypt_10.20.2019.zip"
[SOLVED] Phone gets stuck in bootloop if I try to install Magisk ZIP!
From the forum I followed these step to install magisk: - Patched my boot.img of my current rom using Magisk Manager and flashed via fastboot - After rebooting from fastboot it got stuck in recovery so had to wipe all data and it booted finally...
forum.xda-developers.com
EDIT 2: ...I'm still stuck in bootloop where it tells me to it's "formatting data"... Highly recommend making a backup in TWRP before trying to install Magisk/root.
Hello everyone! I have managed to get Global firmware on VZW UW OnePlus 8 and thought I would share.
Donations are appreciated. PayPal user @igp1490
You will need to download to get started.
1. FastbootEnhance: https://github.com/libxzr/FastbootEnhance/releases
2. Jaguar Rom Full: https://drive.google.com/file/d/1RIIZzz0IyVXeFdjjKRjgqdSphLxaE--w/view
3. Recovery: https://androidfilehost.com/?fid=15664248565197198941
4. PayloadDumper GUI. Download version 2.3: https://forum.xda-developers.com/t/...and-other-img-files-from-payload-bin.4442149/
5. Global OTA Firmware 11.0.11.11.IN21AA: https://www.thecustomdroid.com/download-oneplus-8-pro-oxygenos-ota-updates/
6. OnePlus 8 Visible OTA firmware: https://oxygenos.oneplus.net/OnePlu..._OTA_0080_all_2203082133_56fdf9c8718742cb.zip
7. Platform-tools, I'm using 33.0.3: https://www.techspot.com/downloads/downloadnow/5425/?evp=de0a68064118855fcddcc3980a2143c4&file=6062
Now to get started. First have bootloader unlocked of course.
1. Extract payload.bin from Visible OTA, then dump payload.bin with payload dumper. next find modem.img and move to desktop
2. Install Recovery
3.Be on A11 rom with A11 custom recovery or Install Jaguar Rom and go through setup.
Thanks to Bishop1312! for pointing out any A11 rom with A11 custom recovery works in step 3.
4. When Jaguar is setup reboot to fastboot
5. Run FastbootEnhance, double click your device that says fastboot
6. When in fastbootenhance click fastbootd then click little box to the left of "ignore unknown partitions" then select flash payload.bin and select global firmware zip. When flash is complete "select activate slot" my second slot to flash was slot B, you want to flash global to both slots.
7. After it installs click back in in Jaguar recovery and select "Factory reset", I did f2fs and regular format options
8. Afterformat is done reboot system
9. It may take a few minuets to get into the setup and you may get a message saying phone app has stopped working, don't worry just go through the setup process and connect to wifi.
10. when phone is setup turn off phone and boot into fastboot holding power+Vol down, when in fastboot connect to computer and run FastbootEnhancer. You should see your fastboot device, double click on fastboot, now in fastbootenhancer click reboot to Fastbootd. when in fastbootd go to Partitions tab in fastbootenhancer and look for Modem_b, click on modem_b to highlight it, then click erase then click flash and look for modem.img you put in desktop and select it to flash and after look for modem_a and follow same steps then reboot phone to system.
11. When phone is booted go to system updates and update. After update is finished reboot, after reboot follow steps 10 again for modem, continue step 10 until fully updated to Android 13. Verizon service will work in Android 13 but not 11 or 12.
One problem I have is if I turn on then off airplane mode it wont reconnect to Verizon service, you have to reboot phone and it will work again. I'm thinking maybe because it's an older modem.img, so if anyone can get there hands on the newer modem from Verizon or Visible newest OTA maybe that will fix the issue but no sure. This is my first guide so If anyone has problems let me know and i'll do my best to help you.
Hope ya'll enjoy.
Edit: I got EvolutionX A13 rom working! also airplane mode is working in EvolutionX A13 rom. You have to do step 10 every time after setting up new A13 roms. I Tried step 10 before going through setup but it just goes to bootloader, So make sure to complete rom setup before step 10.
Good work, man!!! This method fully work! I have some little notations:
In step 3, it can be any rom, based on Android 11, but recovery must be from custom A11 rom;
After another installing or updating rom, we must do step 10 every time, for working cellular data. But i think, it's small price for getting fully working custom A13 roms.
UPD. On every reboot, cellular data appears after ~1 min, so don't worry))
Bishop1312 said:
Good work, man!!! This method fully work! I have some little notations:
In step 3, it can be any rom, based on Android 11, but recovery must be from custom A11 rom;
After another installing or updating rom, we must do step 10 every time, for working cellular data. But i think, it's small price for getting fully working custom A13 roms.
Click to expand...
Click to collapse
Thank you. I'll edit step 3.
Bishop1312 said:
Good work, man!!! This method fully work! I have some little notations:
In step 3, it can be any rom, based on Android 11, but recovery must be from custom A11 rom;
After another installing or updating rom, we must do step 10 every time, for working cellular data. But i think, it's small price for getting fully working custom A13 roms.
UPD. On every reboot, cellular data appears after ~1 min, so don't worry))
Click to expand...
Click to collapse
Have you tried watching a video on youtube or any movie/video app? I'm having video playback freeze for a few seconds then video plays for another few seconds then freezes and continues this cycle. I'm wondering if it's just EvolutionX.
Incognit420 said:
Have you tried watching a video on youtube or any movie/video app? I'm having video playback freeze for a few seconds then video plays for another few seconds then freezes and continues this cycle. I'm wondering if it's just EvolutionX.
Click to expand...
Click to collapse
No, video playback i don't test for now. I tried to flash two roms and i apologize for unchecked words - after first flashing modem.img at the beginning, in the future no needs to flash modem, cellular data work fine.
Great work @Incognit420. A video guide will also be helpful for noob like me.
Zombify01 said:
Great work @Incognit420. A video guide will also be helpful for noob like me.
Click to expand...
Click to collapse
Even though reading is fundamental - a how-to video would take it over the top.
Does anyone know if OOS13 is working with this method? Don't you need the OOS12/ 13 firmware in order to be able to use the latest custom ROMs?
Xryphon said:
Does anyone know if OOS13 is working with this method? Don't you need the OOS12/ 13 firmware in order to be able to use the latest custom ROMs?
Click to expand...
Click to collapse
Yes OOS13 works. This method flashes OOS11 global firmware then you update to OOS12 in setting and then update to OOS13 in settings. Make sure to flash modem.img in fastbootd after each update. OOS13 works. Data and calling are not working in OOS12 global, don't know why but does work in OOS13. the only problem I have is OOS13 is if you turn off wifi it won't turn back on but data, calling and text work. I'm on a custom OOS13 rom and it fixed wifi.
Zombify01 said:
Great work @Incognit420. A video guide will also be helpful for noob like me.
Click to expand...
Click to collapse
I'm horrible at making videos lol but I'll give it a try.
hi, after step 7, i chose to back recovery , but show default recovery, and i go next step wipe data and reboot goot qualcom crush dump. any idea?
faritz1903 said:
hi, after step 7, i chose to back recovery , but show default recovery, and i go next step wipe data and reboot goot qualcom crush dump. any idea?
Click to expand...
Click to collapse
What rom were you on before flashing global firmware?
Incognit420 said:
What rom were you on before flashing global firmware?
Click to expand...
Click to collapse
oos 11, then install jaguar rom
after more try, it success. but in after upgrade to OOS 13 my wifi dont work, but cell is work, any idea?
faritz1903 said:
after more try, it success. but in after upgrade to OOS 13 my wifi dont work, but cell is work, any idea?
Click to expand...
Click to collapse
Glad to hear you got it working. Yeah I just realized that yesterday that wifi doesn't work. Install a custom a13 rom and you will get wifi back. I recommend starting with crdroid a13. I was using evolutionx but screen was flashing a little bit when typing so I installed crdroid and it is working perfectly. We need an actual developer to figure out the wifi issue in stock oos13. I'm not by any means a developer. I just messed around with firmware for months to figure out how to get a13 on our vzw devices since verizon is garbage for updates.I personally like the stock oos a13, so it would be nice to have wifi. I think the opeque look in the pixel roms is ugly, Google should have implemented blur in QS and notifications.
Incognit420 said:
Glad to hear you got it working. Yeah I just realized that yesterday that wifi doesn't work. Install a custom a13 rom and you will get wifi back. I recommend starting with crdroid a13. I was using evolutionx but screen was flashing a little bit when typing so I installed crdroid and it is working perfectly. We need an actual developer to figure out the wifi issue in stock oos13. I'm not by any means a developer. I just messed around with firmware for months to figure out how to get a13 on our vzw devices since verizon is garbage for updates.I personally like the stock oos a13, so it would be nice to have wifi. I think the opeque look in the pixel roms is ugly, Google should have implemented blur in QS and notifications.
Click to expand...
Click to collapse
i will try but link recovery and vbmeta is not found, can u share it?
can you try isntall Coloros 13?
faritz1903 said:
i will try but link recovery and vbmeta is not found, can u share it?
can you try isntall Coloros 13?
Click to expand...
Click to collapse
Install EvolutionX 13 and then install Crdroid 9.0. or you can try just using EvolutionX vbmeta and recovery to install Crdroid, both roms use the same method.
Incognit420 said:
Glad to hear you got it working. Yeah I just realized that yesterday that wifi doesn't work. Install a custom a13 rom and you will get wifi back. I recommend starting with crdroid a13. I was using evolutionx but screen was flashing a little bit when typing so I installed crdroid and it is working perfectly. We need an actual developer to figure out the wifi issue in stock oos13. I'm not by any means a developer. I just messed around with firmware for months to figure out how to get a13 on our vzw devices since verizon is garbage for updates.I personally like the stock oos a13, so it would be nice to have wifi. I think the opeque look in the pixel roms is ugly, Google should have implemented blur in QS and notifications.
Click to expand...
Click to collapse
The reason why the various issues on the ROMs exist is because the OOS12/ OOS 13 firmware has not been released by Verizon officially, and there are fundamental changes in the firmware such as the modem (since the Verizon model has the mmWave functionality). This leads to various networking issues such as Wi - Fi not working, cell data not working sometimes, etc. IN2019/ Verizon OnePlus 8 users will never get a stable OOS12/ OOS13 build unless Verizon decides to release the firmware for it - the custom ROMs are the same way since they rely in the OOS12/ OOS13 firmware in order to function properly.
Before I attempt this, is there an easy way to return to stock? Does flashing to stock with MSM undo these changes?
The0919 said:
Before I attempt this, is there an easy way to return to stock? Does flashing to stock with MSM undo these changes?
Click to expand...
Click to collapse
Yes, MSM will bring you back to vzw firmware.