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
I have an SCH-i545 MDK build.
I am trying to upgrade from 4.2.2 to 4.3 and get root working.
On a 4.2.2 ROM, the motochopper exploit works perfectly. However, if I load a 4.3 ROM and follow the same method, when I flash the kernel to the pre-release kernel, the phone hangs and never boots. I've tried it several times with the same result, clearing cache before the process starts also seems to have no effect.
So what's the deal? Why is this happening? I know I have the right build. I went back to stock 4.2 and re-rooted using these files to make sure it would work at all. It worked perfectly. WTF? I flashed back to the stock kernel before installing the 4.3 ROM and trying again. Same deal, no booting after flashing the pre-release kernel.
Is there an updated root exploit for 4.3 that I missed?
I am following this guide: http://forum.xda-developers.com/showthread.php?t=2290798
This is my desired 4.3 ROM: http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/582-jfltevzw
forkbomb said:
I have an SCH-i545 MDK build.
I am trying to upgrade from 4.2.2 to 4.3 and get root working.
On a 4.2.2 ROM, the motochopper exploit works perfectly. However, if I load a 4.3 ROM and follow the same method, when I flash the kernel to the pre-release kernel, the phone hangs and never boots. I've tried it several times with the same result, clearing cache before the process starts also seems to have no effect.
So what's the deal? Why is this happening? I know I have the right build. I went back to stock 4.2 and re-rooted using these files to make sure it would work at all. It worked perfectly. WTF? I flashed back to the stock kernel before installing the 4.3 ROM and trying again. Same deal, no booting after flashing the pre-release kernel.
Is there an updated root exploit for 4.3 that I missed?
I am following this guide: http://forum.xda-developers.com/showthread.php?t=2290798
This is my desired 4.3 ROM: http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/582-jfltevzw
Click to expand...
Click to collapse
I've never seen a custom ROM that didn't come rooted. I suspect that your 4.3 ROM doesn't need to be exploited to be rooted.
k1mu said:
I've never seen a custom ROM that didn't come rooted. I suspect that your 4.3 ROM doesn't need to be exploited to be rooted.
Click to expand...
Click to collapse
Ok with the 4.3 ROM installed, it has SuperSU installed but it says my device is not rooted. SuperSU says it needs to update it's binaries.
I click install normal, it says failed. I click CWM, it never reboots. Rebooting into recovery doesn't continue the process.
Is this the ROM's fault? Should I just pick another 4.3 ROM?
forkbomb said:
Ok with the 4.3 ROM installed, it has SuperSU installed but it says my device is not rooted. SuperSU says it needs to update it's binaries.
I click install normal, it says failed. I click CWM, it never reboots. Rebooting into recovery doesn't continue the process.
Is this the ROM's fault? Should I just pick another 4.3 ROM?
Click to expand...
Click to collapse
I'd ask the developer of that ROM what's up.
forkbomb said:
Ok with the 4.3 ROM installed, it has SuperSU installed but it says my device is not rooted. SuperSU says it needs to update it's binaries.
I click install normal, it says failed. I click CWM, it never reboots. Rebooting into recovery doesn't continue the process.
Is this the ROM's fault? Should I just pick another 4.3 ROM?
Click to expand...
Click to collapse
You must go to setting, about phone, tap the build number repeatedly until developer options are granted.
Now go to settings, developer options, look for Root. Select it and choose "ADB & Apps"
dynospectrum said:
You must go to setting, about phone, tap the build number repeatedly until developer options are granted.
Now go to settings, developer options, look for Root. Select it and choose "ADB & Apps"
Click to expand...
Click to collapse
Oh wow, that was simple. Thank you.
I have been searching everywhere to try and find a way to load CM11 on my USC Galaxy Mega. All I can find is a ROM for the I9200/I9205. I have been in other forums that you can flash this CM11 release on a Metro PCS Mega. Is it possible to flash this on my USC R-960 Mega or have any of you here tried?
Depends on your phone setup. You will need an unlocked bootloader and should be running knox free firmware on your phone.
If the above criteria are met, then you can try flashing after backing up your stock rom. CM11 works on a lot of Mega versions.
Silesh.Nair said:
Depends on your phone setup. You will need an unlocked bootloader and should be running knox free firmware on your phone.
If the above criteria are met, then you can try flashing after backing up your stock rom. CM11 works on a lot of Mega versions.
Click to expand...
Click to collapse
Here is my setup.
I have rooted my device and have flashed CWM. Sounds like the boat loader is a different process than above? Also havent heard of knox free firmware, is that just something you flash with odin or something?
All the latest firmware releases come with Samsung's proprietary Security feature called knox. If you install a knox enabled firmware, then you will not be able to do the following.
Flash custom rom
Go back to a older stock rom
Go back to an older nandroid backup.
Trying to do any of the following will result in an insecure kernel error which can be rectified only by flashing a knox enabled firmware through Odin.
Post a snapshot of the bootloader screen.
is this what your talking about
Looks ok. First make a backup of your custom rom. Then you can try flashing a custom rom of your choice. You may/may not get LTE to work.
I presume you have not installed any ota update from your provider.
Silesh.Nair said:
Looks ok. First make a backup of your custom rom. Then you can try flashing a custom rom of your choice. You may/may not get LTE to work.
I presume you have not installed any ota update from your provider.
Click to expand...
Click to collapse
No ota updates, even when I checked manually I got a message saying you phone is modified or something.
dpetes262 said:
No ota updates, even when I checked manually I got a message saying you phone is modified or something.
Click to expand...
Click to collapse
Thats because your system status is custom. OTA's work only system and binary status are official.
Silesh.Nair said:
Thats because your system status is custom. OTA's work only system and binary status are official.
Click to expand...
Click to collapse
so I was able to flash/cm11 for i9200/i9205 and no touchscreen at all. I then flashed slimcat, same thing no touchscreen and accelerometer was acting weird. I then restored from the backup and touchscreen is back. I have 4g but its saying im roaming now. I wiped everything before all installs too. Any ideas?
dpetes262 said:
so I was able to flash/cm11 for i9200/i9205 and no touchscreen at all. I then flashed slimcat, same thing no touchscreen and accelerometer was acting weird. I then restored from the backup and touchscreen is back. I have 4g but its saying im roaming now. I wiped everything before all installs too. Any ideas?
Click to expand...
Click to collapse
So after I booted back to my backup,I had service but could not make calls or send texts. So what I did was a factory reset from with that ROM. This restored my service completely. Now I am just wondering why the touchscreen doesn't work on the other roms.
Silesh.Nair said:
Thats because your system status is custom. OTA's work only system and binary status are official.
Click to expand...
Click to collapse
Just a side note, when I flash either Phils CWM touch version, I get no touch or if I flash any other recovery, I get no touch functionality. Does this have something to do with the ROM not having touch?
Guestn/a posts Thanks: 0
So.. The Android 5.1.1 version is here and I've unrooted my phone for the update, but it still shows "Could not verify." Are there any files that cause the verifying process to know that I had rooted my device? If yes, can I delete it or what? Or are there any other ways to update without flashing a ftf file? (1. Because that ftf file is very big and my Internet speed couldn't afford it. 2. Because I don't want to wipe my apps and data) Any help would be appreciated!
@OP, If I understand right, it's the custom recovery you might have that prevents the OTA update from completing successfully. Which, in a way, is a good thing.
Step 1: reroot your phone while you still can.
Step 2: download any of a number of flashable, pre-rooted 5.1.1 ROMs with recovery (*.zip) floating around now and flash it with your current recovery, wiping only cache and Dalvik upon exit. This is what I've done to keep all my date and settings and still be rooted and have recovery on 5.1.1.
wicozani said:
@OP, If I understand right, it's the custom recovery you might have that prevents the OTA update from completing successfully. Which, in a way, is a good thing.
Step 1: reroot your phone while you still can.
Step 2: download any of a number of flashable, pre-rooted 5.1.1 ROMs with recovery (*.zip) floating around now and flash it with your current recovery, wiping only cache and Dalvik upon exit. This is what I've done to keep all my date and settings and still be rooted and have recovery on 5.1.1.
Click to expand...
Click to collapse
After I flash this, can my phone update OTA or the same problem will happen?
As far as we know, custom recoveries will always prevent OTA updates to our Xperia devices. Why are OTA updates seemingly so important to you? With your custom recovery installed, you can always simply flash the new update when it becomes available; often before the OTA update is released.
Sent from my D6503 using Tapatalk
wicozani said:
As far as we know, custom recoveries will always prevent OTA updates to our Xperia devices. Why are OTA updates seemingly so important to you? With your custom recovery installed, you can always simply flash the new update when it becomes available; often before the OTA update is released.
Sent from my D6503 using Tapatalk
Click to expand...
Click to collapse
Hmm okay thankyou
wicozani said:
As far as we know, custom recoveries will always prevent OTA updates to our Xperia devices. Why are OTA updates seemingly so important to you? With your custom recovery installed, you can always simply flash the new update when it becomes available; often before the OTA update is released.
Sent from my D6503 using Tapatalk
Click to expand...
Click to collapse
Can you give me a link for the official ROM? Thanks!
Can I use the AOSPA ROM? Does it need to unlock my bootloader to flash it?
Some consideration about this thread.
1) Not never the OTA updade overwrite the ROOT, example I passed from .627 to .28 through OTA update without lose the root and recovery. This depend of kind of update.
2) I think that to install a pre-rooted rom is not a good thing, because the baseband is almost always different an this can create issue related the WI-fi and carrier signal (3G, 4G).
3) I always installed the root, recovery and mod as well. But now I have understand that is not really necessary to install this. At least the stock Z2 have a good/beautiful OS and good hardware and there is no need to change some colors or icons to improve it.
I'm boring to flash and restore my data every new firmware or new mod. (now a new firmware is already certified and will be ready soon).
Maybe I will think to change the room when my phone will be obsolete
Regards
giancaleone said:
Some consideration about this thread.
1) Not never the OTA updade overwrite the ROOT, example I passed from .627 to .28 through OTA update without lose the root and recovery. This depend of kind of update.
2) I think that to install a pre-rooted rom is not a good thing, because the baseband is almost always different an this can create issue related the WI-fi and carrier signal (3G, 4G).
3) I always installed the root, recovery and mod as well. But now I have understand that is not really necessary to install this. At least the stock Z2 have a good/beautiful OS and good hardware and there is no need to change some colors or icons to improve it.
I'm boring to flash and restore my data every new firmware or new mod. (now a new firmware is already certified and will be ready soon).
Maybe I will think to change the room when my phone will be obsolete
Regards
Click to expand...
Click to collapse
Totally understand, thankyou, so I just flash the original ROM from AOSPA and without root is enough right?
Wayhome said:
Totally understand, thankyou, so I just flash the original ROM from AOSPA and without root is enough right?
Click to expand...
Click to collapse
If you do not have an unlocked bootloader, you cannot flash anything but a pre-rooted stock 5.1.1 ROM with recovery. There are several types available in the General Z2 column.
Sent from my D6503 using Tapatalk
I have a crazy thought flashed across my mind haha, that file that I downloaded via OTA SYSTEM UPDATE is still there, can I make it as a zip file and flash it?
Wayhome said:
I have a crazy thought flashed across my mind haha, that file that I downloaded via OTA SYSTEM UPDATE is still there, can I make it as a zip file and flash it?
Click to expand...
Click to collapse
Why would you do that? You wouldn't have root and you wouldn't have a recovery; you'd be stuck, unable to root and install a recovery. Do what I said and you'll be fine.
Sent from my D6503 using Tapatalk
Can you help me to find one? That doesn't need to unlock bootloader to flash.
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