Related
Some people like sticking with stock, and there isn't a huge issue with that as the stock ROM is pretty good on the Note 2. However, if you want to be stock and remained unlocked, it's quite difficult to do as every new OTA re-locks the bootloader. It's also difficult to stay stock and keep a custom recovery as it will be over-written on every boot.
Now, users that want to stay unlocked and have custom recovery have an option available. This will require you to be fully stock, if you've modified anything in /system, it won't work. The only change you can have is root, but if you've modified build.prop, the kernel, or removed any files, you need to restore. If you have any doubts, flash the alternate restore file (after extracting it) from here.
There is one other requirement for this, and that is you need a custom recovery installed. If you've unlocked, you'll already have one. If not, you'll need to be rooted and you can use ROM manager or GooManager to flash a custom recovery (after going back to stock of course).
Now you have the pre-requisites down, stock rom and custom recovery, so all you need are the files. There are two updates available, so there are currently two files to flash to be on the latest OTA. You can download them below, and installation is as simple as downloading them to your phone and installing them via recovery. If you went back to stock VRALJB, you'll start with the VRALJB to VRALL4 file, then flash VRALL4 to VRAMC3 to get to the latest system. It should be fairly easy to figure out.
If you have any errors when flashing, odds are, you did something to files in /system and caused a problem. If that is the case, start over and flash the alternate restore file and proceed from there. I'll continue to update this as new OTAs are released then as well.
[size=+2]Downloads[/size]
VRALJB to VRALL4
VRALL4 to VRAMC3
Will this update baseband also?
Sent from my SCH-I605 using XDA Premium HD app
Digbob said:
Will this update baseband also?
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
It updates everything except for sboot.bin, tz.img (both bootloader files), and recovery.
hey thanks for this!
I'm on VRALJB stock, rooted and unlocked with CWM.
But I added Google Wallet working, and using a different kernel for overclock.
I tried the first update to LL4 just to see what it would say, and errored when applying the NFC.apk file, which is from the Wallet patch.
Not sure if it's easier for me to try and get the phone back to stock by restoring the original NFC files and kernel, and then try the LL4 update again, or just flash the phone with the rooted C3 ROM, but then would have to reinstall all my apps and settings.
FAUguy said:
I'm on VRALJB stock, rooted and unlocked with CWM.
But I added Google Wallet working, and using a different kernel for overclock.
I tried the first update to LL4 just to see what it would say, and errored when applying the NFC.apk file, which is from the Wallet patch.
Not sure if it's easier for me to try and get the phone back to stock by restoring the original NFC files and kernel, and then try the LL4 update again, or just flash the phone with the rooted C3 ROM, but then would have to reinstall all my apps and settings.
Click to expand...
Click to collapse
it says you must be on completely stock rooted with a custom recovery. being you have a custom kernel is most likely the problem. anything modified in /system will cause a fail. flash back to vraljb alternate restore file, then upgrade...or boot into recovery and flash beans mc3 stock rooted .zip rom
either way you will most likely need to wipe data to upgrade...atleast thats normallya prerequisite when changing bases.
FAUguy said:
I'm on VRALJB stock, rooted and unlocked with CWM.
But I added Google Wallet working, and using a different kernel for overclock.
I tried the first update to LL4 just to see what it would say, and errored when applying the NFC.apk file, which is from the Wallet patch.
Not sure if it's easier for me to try and get the phone back to stock by restoring the original NFC files and kernel, and then try the LL4 update again, or just flash the phone with the rooted C3 ROM, but then would have to reinstall all my apps and settings.
Click to expand...
Click to collapse
I said completely stock, and if you modified anything on /system it would fail, and you're surprised that it failed? You installed the Google Wallet hack, which modifies files on /system, and then you have a custom kernel as well, both of which will cause this to fail (as I already stated). Just be happy that the file checks were left in place and your phone still works at this point.
imnuts said:
I said completely stock, and if you modified anything on /system it would fail, and you're surprised that it failed? You installed the Google Wallet hack, which modifies files on /system, and then you have a custom kernel as well, both of which will cause this to fail (as I already stated). Just be happy that the file checks were left in place and your phone still works at this point.
Click to expand...
Click to collapse
I knew that it wouldn't work, but have tried it just to see which error message it would show, which it stopped when it got to the NFC.apk. I know it needed to be fully stock with nothing changed in the /system.
I was just asking, at this point, would it be easier (or better) to try and get it back to stock by replacing the modified files with the original ones and try again.....or flash the modified C3 rooted ROM. I think Adam is still trying the get his root/unlock for C3 to work right for everyone.
Hey thanks for this! This'll make my wife very happy. I thought I'd have to clean install beans stock rom. She just loves stock.
Sent from my Note II using Tapatalk 2
If you have to go all the way back to stock, why not just take all of the OTA updates and then root/unlock your phone?
I am unlocked with recovery running beans stock vramc3. I flashed the new modem afterwards. How is this different?
radio five said:
If you have to go all the way back to stock, why not just take all of the OTA updates and then root/unlock your phone?
Click to expand...
Click to collapse
OTA fails if you have a custom recovery.
Sent from my Note II using Tapatalk 2
If I deleted a couple of apps that were pre installed after rooting, will it fail? Its all stock otherwise, rooted, custom recovery.
FAUguy said:
I knew that it wouldn't work, but have tried it just to see which error message it would show, which it stopped when it got to the NFC.apk. I know it needed to be fully stock with nothing changed in the /system.
I was just asking, at this point, would it be easier (or better) to try and get it back to stock by replacing the modified files with the original ones and try again.....or flash the modified C3 rooted ROM. I think Adam is still trying the get his root/unlock for C3 to work right for everyone.
Click to expand...
Click to collapse
You're setting your phone up again either way.
radio five said:
If you have to go all the way back to stock, why not just take all of the OTA updates and then root/unlock your phone?
Click to expand...
Click to collapse
Not everyone is running a custom ROM. Some people are unlocked and on stock rooted with custom recovery and that's it. This is meant so they can stay up to date and remain on stock, rooted, and custom recovery.
TonikJDK said:
I am unlocked with recovery running beans stock vramc3. I flashed the new modem afterwards. How is this different?
Click to expand...
Click to collapse
This will be fully stock (minus recovery over-write). Beans did some other stuff to his ROM package from what I saw the last time I looked at the thread. Nothing major or groundbreaking, but it isn't as close to stock as this is.
pmazz850 said:
If I deleted a couple of apps that were pre installed after rooting, will it fail? Its all stock otherwise, rooted, custom recovery.
Click to expand...
Click to collapse
Really?
VRALL4 to VRAMC3
Update fails, verified hash matches;
E: Error in /sdcard/Download/vrall4_to_ramc3.zip
(status 7)
I don't think I changed anything on this phone...all I did was unlock bootloader/flash custom recovery TWRP 2.3.2.3, just to NAND & Wifi Tether, completely stock.
Systom said:
VRALL4 to VRAMC3
Update fails, verified hash matches;
E: Error in /sdcard/Download/vrall4_to_ramc3.zip
(status 7)
I don't think I changed anything on this phone...all I did was unlock bootloader/flash custom recovery TWRP 2.3.2.3, just to NAND & Wifi Tether, completely stock.
Click to expand...
Click to collapse
It did it to me too. I'm just going to clean flash beans stock.
Sent from my Note II using Tapatalk 2
Mac of York said:
It did it to me too. I'm just going to clean flash beans stock.
Sent from my Note II using Tapatalk 2
Click to expand...
Click to collapse
Yah, I think I'm gonna wipe/flash beans odex rom VRAMC3 & radio/restore data from NAND backup from VRALL4, hopefully it should be fine. Unless anyone would know otherwise?
Systom said:
VRALL4 to VRAMC3
Update fails, verified hash matches;
E: Error in /sdcard/Download/vrall4_to_ramc3.zip
(status 7)
I don't think I changed anything on this phone...all I did was unlock bootloader/flash custom recovery TWRP 2.3.2.3, just to NAND & Wifi Tether, completely stock.
Click to expand...
Click to collapse
What change for Wifi Tether?
imnuts said:
What change for Wifi Tether?
Click to expand...
Click to collapse
WifiTether_TrevE_Mod_11_22_2012.apk
As the title says, I really don't want to lose my (Rooted) heavily modded ROM, has anyone tried to update OTA and kept Root?
It either wont verify update or if it somehow does you will lose root with your mods and changes
Envious_Data said:
It either wont verify update or if it somehow does you will lose root with your mods and changes
Click to expand...
Click to collapse
You`ll never get past that "verify" error while your phone is rooted and/or custom recovery installed. If you want to update and keep ROOT you need to flash a prerooted zip found here on the forums.
what about the mods and stuff?
karim-ps said:
what about the mods and stuff?
Click to expand...
Click to collapse
you will have to start all over again on a clean system
That sucks, I might just skip this update until Android M, as it's not worthy and also, I have heard of many battery drain reports, one of which just a few minutes ago from a friend of mine
I am trying to install CWM so I can run Cyanogen like I used to before lollipop came out and locked me out. I am using a rooted sch-i545 via kingroot, and CWM claims to have installed. However, I cannot get cyanogen to install (Signature authentication failed) or something along those lines. Any idea how I can get past this and get Cyanogen to install?
Nanometer45 said:
I am trying to install CWM so I can run Cyanogen like I used to before lollipop came out and locked me out. I am using a rooted sch-i545 via kingroot, and CWM claims to have installed. However, I cannot get cyanogen to install (Signature authentication failed) or something along those lines. Any idea how I can get past this and get Cyanogen to install?
Click to expand...
Click to collapse
If you had to root via KingRoot then your bootloader is locked and have no recovery option.
Only flashfire is what you can use and currently you only have stock OC1/deodex or stang5litre OC1 rom to choose from.
That's too bad. Annoying Samsung... What do you recommend for a clean android experience?
Nanometer45 said:
That's too bad. Annoying Samsung... What do you recommend for a clean android experience?
Click to expand...
Click to collapse
Stang5litre rom just got on version 2 it is nice and smooth.
No problems battery life is about average for lollipop but not much can be done about that except for greenify and whatnot.
you can check out the changelogs here http://forum.xda-developers.com/galaxy-s4-verizon/development/stang5litre-ediition-5-0-t3132555
Thanks for the reply. Do you ever presume we will get a full root back? I would like the ability to take this phone over sees where I can buy any such sim card and it will just work. I don't suspect I could do that with just a Odex rom could I?
Nanometer45 said:
Thanks for the reply. Do you ever presume we will get a full root back? I would like the ability to take this phone over sees where I can buy any such sim card and it will just work. I don't suspect I could do that with just a Odex rom could I?
Click to expand...
Click to collapse
The device is sim unlocked of of the box so any other sim should work no problem.
Dont no suddenly what happened, I had rooted my onyx and had flashed with cm13 ROM, got bored with it n now flashed with H2 os , but after flashing with this, it says u have not rooted your device, any solutions.
riz18 said:
Dont no suddenly what happened, I had rooted my onyx and had flashed with cm13 ROM, got bored with it n now flashed with H2 os , but after flashing with this, it says u have not rooted your device, any solutions.
Click to expand...
Click to collapse
Only thing you have to do is flash superuser, than you phone is fully root again.
riz18 said:
Dont no suddenly what happened, I had rooted my onyx and had flashed with cm13 ROM, got bored with it n now flashed with H2 os , but after flashing with this, it says u have not rooted your device, any solutions.
Click to expand...
Click to collapse
Hi,
you have to flash Supersu then its will be rooted . super su not included in H2os .
Everytime you change rom, root will disappear, unless it's explicitly said in the rom description something like "pre-rooted". If you want to root again just flash supersu
Various applications have been installed on my one plus X but when I tried to install Fasttag, I suddenly get the instruction " your phone is rooted. You cannot use this app". How to rectify
Beardedon said:
Various applications have been installed on my one plus X but when I tried to install Fasttag, I suddenly get the instruction " your phone is rooted. You cannot use this app". How to rectify
Click to expand...
Click to collapse
Maybe you have to put it totally offical...
Or trying with Magisk using Magisk Hide option...
So after having a metric f**k ton of issues trying to get a custom recovery to work on 6.0.1, I gave up trying to install a custom rom and eventually went back to stock unrooted. After updating to 7.0 and waiting a bit, I gave it another go and managed to get TWRP to work and rooted my phone. Now I'm looking to install a custom ROM and have a few questions.
Is there anything I should know before going in? Any prerequisites I need to get before/after flashing a custom ROM so certain features will work?
Can I use any custom ROM that is listed as compatible with 7.0/G925F? Or do I have to be more specific as to what version I get?
What should I keep an eye out for? Any features that are good/bad?
Anything else I should know?
As for my choices, it's currently between Nemesis and Noble. Anyone used either and care to share your experience? Any other recommendations?
ProdigyThirteen said:
So after having a metric f**k ton of issues trying to get a custom recovery to work on 6.0.1, I gave up trying to install a custom rom and eventually went back to stock unrooted. After updating to 7.0 and waiting a bit, I gave it another go and managed to get TWRP to work and rooted my phone. Now I'm looking to install a custom ROM and have a few questions.
Is there anything I should know before going in? Any prerequisites I need to get before/after flashing a custom ROM so certain features will work?
Can I use any custom ROM that is listed as compatible with 7.0/G925F? Or do I have to be more specific as to what version I get?
What should I keep an eye out for? Any features that are good/bad?
Anything else I should know?
As for my choices, it's currently between Nemesis and Noble. Anyone used either and care to share your experience? Any other recommendations?
Click to expand...
Click to collapse
The first and most important thing to do is make a backup. A nandroid backup is fine but make sure you back up your EFS folder. If this gets corrupted you will corrupt your IMEI and have no signal permanently. So backup efs and store somewhere safe like your pc.
I recommend doing full wipe before installing a custom ROM just so it's a clean install.
After that your pretty much good to go.
You can use any ROM that's compatible for your model only. So any G925F ROMs will work fine. Most support a number of models like G925F/I/V etc.
Most s6 edge custom ROMs are stable and have very few issues, and if there are issues then generally there are fixes for them.
Nemesis and Noble are both good stable ROMs. Also Omega ROM is a good choice. But my favourite that I used for over a year is CarHD ROM. It's customisation is endless.
One more is AlexisROM. Good ROM used for a while.
Hope this helps.
callumbr1 said:
snip
Click to expand...
Click to collapse
So after a painfully long download, I installed CarHD and I'm liking everything I see. My only issue is trying to get SafetyNet to pass. I've removed SuperSU, installed Magisk and its kernel and now whenever I check SafetyNet, it fails with "CTS profile mismatch". I've looked around on a few different threads about it and everything I've tried hasn't worked. Mostly because they revolve around MagiskHide, which isn't showing up for me.
My first thought is to completely uninstall magisk, go back to a stock kernel and start off fresh, but I'm not going to do that just yet as I wanted your opinion first. Is that the best thing to do or would it cause more harm than good?
And if it wasn't already obvious, yes I'm still pretty damn new to this, but I'm trying not to **** up as I quite like my phone working.
Edit: solved the MagiskHide not showing.. I'm an idiot and forgot it was under settings and not enabled by default.
ProdigyThirteen said:
So after a painfully long download, I installed CarHD and I'm liking everything I see. My only issue is trying to get SafetyNet to pass. I've removed SuperSU, installed Magisk and its kernel and now whenever I check SafetyNet, it fails with "CTS profile mismatch". I've looked around on a few different threads about it and everything I've tried hasn't worked. Mostly because they revolve around MagiskHide, which isn't showing up for me.
My first thought is to completely uninstall magisk, go back to a stock kernel and start off fresh, but I'm not going to do that just yet as I wanted your opinion first. Is that the best thing to do or would it cause more harm than good?
And if it wasn't already obvious, yes I'm still pretty damn new to this, but I'm trying not to **** up as I quite like my phone working.
Click to expand...
Click to collapse
You don't need any kind of custom kernel to use magisk, or at least you shouldn't. It should work perfectly fine with stock.
Try updating magisk manager app from xda labs and magisk hide should appear.
If it does then just enable magisk hide and hide all apps that require safety net, hide knox also if it's still on the ROM. Then you should pass.
If this fails I recommend to flash the ROM again, no need to wipe data and then choose magisk in aroma installer and flash again.
Let me know if you need help :good:
callumbr1 said:
You don't need any kind of custom kernel to use magisk, or at least you shouldn't. It should work perfectly fine with stock.
Try updating magisk manager app from xda labs and magisk hide should appear.
If it does then just enable magisk hide and hide all apps that require safety net, hide knox also if it's still on the ROM. Then you should pass.
If this fails I recommend to flash the ROM again, no need to wipe data and then choose magisk in aroma installer and flash again.
Let me know if you need help :good:
Click to expand...
Click to collapse
Fixed the MagiskHide issue, but simply enabling hide on the apps that I want to use doesn't work. I tried reinstalling the ROM as you said, but it never gave the option to choose Magisk over SuperSU. Then when I switched from SuperSU to Magisk, SuperSU was removed normally, but Magisk is installed and saying I don't have root access. Flashed Magisk kernel from CarHD as TWRP wasn't allowing install of Magisk with the other that came stock, then flashed Magisk again. Magisk saying I now have root access, but Magisk isn't installed and when I try to install it, the app crashes. Currently checking Magisk threads for a solution for that.
Tried reinstalling Magisk and clearning data/cache to no avail... I still have root access, but can't install Magisk through the manager.
Uninstalled Magisk, flashed stock kernel, re flashed magisk and now SafetyNet is passing, but still can't install Magisk through the Manager
ProdigyThirteen said:
Uninstalled Magisk, flashed stock kernel, re flashed magisk and now SafetyNet is passing, but still can't install Magisk through the Manager
Click to expand...
Click to collapse
If you have root access and safety net pass then I don't understand what you mean by can't install magisk through the app?
So you have magisk manager app installed?
callumbr1 said:
If you have root access and safety net pass then I don't understand what you mean by can't install magisk through the app?
So you have magisk manager app installed?
Click to expand...
Click to collapse
Yeah, the manager is installed, but when I open it, it says there is an update available and under status says Magisk is not installed, v130 is available. There is no option to enable Magisk hide or any other extras available for download.
Screenshot of magisk
ProdigyThirteen said:
Screenshot of magisk
Click to expand...
Click to collapse
It's the magisk manager app. You need to install the new one. Delete the one you currently have installed and download latest one from magisk Thread here or from xda labs.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Should look similar to this.
callumbr1 said:
It's the magisk manager app. You need to install the new one. Delete the one you currently have installed and download latest one from magisk Thread here or from xda labs.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Should look similar to this.
Click to expand...
Click to collapse
Tried to uninstall it, no option to. Downloaded something to uninstall system apps, tried to uninstall it, still there. Tried to install a new app over it, gave an error saying app already installed with same name.
ProdigyThirteen said:
Tried to uninstall it, no option to. Downloaded something to uninstall system apps, tried to uninstall it, still there. Tried to install a new app over it, gave an error saying app already installed with same name.
Click to expand...
Click to collapse
You should be able to uninstall it with titanium backup or any app to remove system app.
Infact you should be able to just remove it as you would remove any other app.
Use what you used before to remove it when it didn't go and then reboot and it should go. If not flash the uninstaller from magisk thread.
Then start again, if you flash the newest magisk from the thread on here then it also should install newest magisk manager app.
callumbr1 said:
You should be able to uninstall it with titanium backup or any app to remove system app.
Infact you should be able to just remove it as you would remove any other app.
Use what you used before to remove it when it didn't go and then reboot and it should go. If not flash the uninstaller from magisk thread.
Then start again, if you flash the newest magisk from the thread on here then it also should install newest magisk manager app.
Click to expand...
Click to collapse
No app that removes system apps can remove Magisk Manager it seems... TB says "Failed to locate the apk file", NoBloat Free says it removed it, but even after rebooting it's still there. Flashing the uninstall doesn't remove it either. I would manually uninstall through root explorer, but there's a risk I delete the wrong file and screw something else up.
Edit: Found Magisk Manger in root/system/app/magisk, backed it up, deleted it, rebooted, seems to be gone. Will try intalling new APK
Fixed it. Had to manually delete the apk, then installed the updated version and now it's showing as magisk is installed perfectly fine. Thanks for all the help.
Third and hopefully final edit: Getting kernel is not seandroid enforcing. Tried uninstalling magisk, flashing stock kernel, reinstalling magisk and still getting it. But it doesn't seem to be messing with anything, can still boot fine, safetynet is still passing so all looks pretty good.
callumbr1 said:
snip
Click to expand...
Click to collapse
No point starting a new thread when I can just ask here as it's a somewhat follow on question. I can't seem to get V4A to work. I've installed the module from Magisk, installed the APK, restarted my phone, loaded up the app and checked the driver just for it to say Status: Abnormal / Audio Format: Unsupported. Can't seem to find anything about a fix for it, been searching for about an hour, so either I'm blind or there's nothing on it (I'm betting it's the former).
When I open the app, I get a message prompting me to update/install the driver, despite it already being installed through Magisk. I've tried both the standard v2.5.0.5 apk and Nougat test fix, standard doesn't do anything and test fix has update/install prompt.
ProdigyThirteen said:
No point starting a new thread when I can just ask here as it's a somewhat follow on question. I can't seem to get V4A to work. I've installed the module from Magisk, installed the APK, restarted my phone, loaded up the app and checked the driver just for it to say Status: Abnormal / Audio Format: Unsupported. Can't seem to find anything about a fix for it, been searching for about an hour, so either I'm blind or there's nothing on it (I'm betting it's the former).
When I open the app, I get a message prompting me to update/install the driver, despite it already being installed through Magisk. I've tried both the standard v2.5.0.5 apk and Nougat test fix, standard doesn't do anything and test fix has update/install prompt.
Click to expand...
Click to collapse
Good stuff. As for the seandroid message on boot you can just ignore it. It's not an error and will stay but doesn't affect anything.
As for viper first thing to try is remove the currently installed app and remove it from magisk manager modules.
Install busybox.
Freeze sound alive with titanium backup (don't delete just freeze)
Then flash this through TWRP
https://mega.nz/#!CV5wQYSa!i-V1UvJ_Lh9YoZDPN9rUUXuJNgXWcXRlhBE83fYH7e8
After this if it doesn't work let me know and I'll tell you next steps.
callumbr1 said:
Good stuff. As for the seandroid message on boot you can just ignore it. It's not an error and will stay but doesn't affect anything.
As for viper first thing to try is remove the currently installed app and remove it from magisk manager modules.
Install busybox.
Freeze sound alive with titanium backup (don't delete just freeze)
Then flash this through TWRP
https://mega.nz/#!CV5wQYSa!i-V1UvJ_Lh9YoZDPN9rUUXuJNgXWcXRlhBE83fYH7e8
After this if it doesn't work let me know and I'll tell you next steps.
Click to expand...
Click to collapse
Tried that, still getting abnormal/unsupported.
ProdigyThirteen said:
Tried that, still getting abnormal/unsupported.
Click to expand...
Click to collapse
Now check that magisk module is enabled and the audio modification module is enabled.
You may also need a permissive kernel to get viper to work.
callumbr1 said:
Now check that magisk module is enabled and the audio modification module is enabled.
You may also need a permissive kernel to get viper to work.
Click to expand...
Click to collapse
Googling permissive kernel is just coming back with a bunch of threads saying get a terminal emulator, type su / setenforce 0. Tried that, trips safetynet and doesn't change Viper.
I feel like it's not changing viper because I need it to stick through reboots, enable it, then reboot, but it's not persistent. How would one go about making it stick?
And honestly, is viper really worth all this hassle?
ProdigyThirteen said:
Googling permissive kernel is just coming back with a bunch of threads saying get a terminal emulator, type su / setenforce 0. Tried that, trips safetynet and doesn't change Viper.
I feel like it's not changing viper because I need it to stick through reboots, enable it, then reboot, but it's not persistent. How would one go about making it stick?
And honestly, is viper really worth all this hassle?
Click to expand...
Click to collapse
You can try Hacker kernel
https://forum.xda-developers.com/ga...l-hacker-kernel-s6-universal-t3254487/page234
Or arter kernel
http://arter97.com/browse/exynos7420/kernel/22.0/g925fi/
As for is it worth it? In my opinion yes 100%.
It depends really if you like the stock effects enough. Personally I love music and love been able to customise it. It sounds 10000x better in my opinion.