DON'T ACCEPT OTA UPDATES

[meatyfist]

2200 3255669

And yet another reason I don't bother hooking my phone up to corporate email. If you want me 24x7 on corporate email, you can provide me a device. Otherwise, I'll login to email via the web assuming you've at least provided that access.

agreed

 

[T0eT4g]

Dagnabbit

I REEEEEAAALLLLYYYY wish I would've read this before I took the 4.3 ota last month. LAAAMEE. I also just bricked my phone today using clockworkmod and honestly my fingers and eyes are sore from hours of scouring the interwebs for answers and looking for the stock rom for VRUEMJ9 which THANKFULLY i found it on here! thanks to that imnuts d00d!

 

[flametai1]

Samsung...

Huh... I wonder if this is going to turn out to be a thing like Motorola did. Hopefully it doesn't considering Motorola pretty much killed their phones in my opinion. I love how Samsung is still pretty easy/open to get unlocked and rooted on.

 

[atomic_monkey]

root is possible with 4.3

This worked easy for me. Just need the bootloader cracked now...

http://forum.xda-developers.com/showpost.php?p=48392009&postcount=1

 

[mlutzow]

OTA Updates, want to Accept and Fails

When I first received the Note 2 I immediately installed the Exynos... app and rooted the device and have been running that since then.

I just like the root for various reasons.

Anyway decided I wanted to unroot and accept the OTA's to the just released 4.3 (been reading good things about rooting that version)

I reversed Exynos process removed the root and uninstalled all the apps that I thought would cause problems. I forgot that I had installed OTA Rootkeeper and had made a backup of root some time ago. I didn't remove the root backup.

The first update to 4.1.2 (I think) was received and updated just fine but the second update continuously fails.

Are there any ideas why, I've left the root backup in-place but have temporarily unrooted.

I haven't been able to find any answers to the dilemma I'm having.

Any assistance is much appreciated.

 

[TonikJDK]

Plug the phone into your computer as an installer. It should install the VZW software tool. Run that and update through that n

 

[mlutzow]

Thanks, I'll give it a try.

Sent from my Galaxy Note II using Tapatalk 2

 

[zsudas]

UPDATE: New Jailbreak here: http://forum.xda-developers.com/showthread.php?t=2118348

Here's the bottom line up-front
Samsung has inserted code to blacklist our baseline and mitigate our exploits in the bootloader patch they began pushing out last night. You will need to flash the updated bootloader baseline and stock pit in order to restore your device to operational status. The How-To Unlock your Bootloader thread is invalid at this time.

Going Forward
I need your help with CASUAL. In order to mitigate this problem, I began working on a CASUAL update system on January 13. If you feel inconvienced now, contribute to the Casual Update System beta by testing it. Currently, CASUAL is dumb. If there is a problem you won't know until after you flash. The idea behind the Update System is to either update the CASUAL to work again, or kill-switch it and automatically bring you to a thread like this one. Obviously it's infinitely more helpful than a simple failure and I need testing on Windows, Linux, Mac and firewalls.

The CASUAL Unlock method will be updated when we figure it out and it will be possible to auto-update or do a helpful kill-switch in the next version.

Addressing Security Patches:
Recognized Developer Ralekdev has began work on a new exploit. It's not going to be as simple as it was before.

Bootloader Blacklisting
You can view the updated code here: http://pastie.org/private/zzfhwlrgeeuzweiccjdpvg#22
Previously, Odin Mode would accept any SBOOT with the proper signature. Samsung has implemented a blacklist which causes properly signed flashes to fail if they are contained in the blacklist.

      bytes_to_hexstr(BL1_blacklist_str, base_addr + 0x1BF0, 16);
      if ( !strcmp(BL1_blacklist_str, BL1_blacklists[i]) )
      {
        sub_43E03A00("BL1 of the blacklist - %s\n", BL1_blacklists[i]);
        return -1;
      }

The old bootloader contained random ARM hex data "CD D2 04 85 63 83 52 7C C9 8A 97 1A CD 30 78 FB".. The new one contains an identifier "EXYNOS_4412 1220". The new bootloader is also programmed to not be able to flash itself.

Non-Header Code Execution
You can view the updated code here: http://pastie.org/private/ryxaraypnnhbmtt6nswvq
Previously, if the ANDROID header was missing from the kernel, SBOOT would execute the partition as raw ARM code. This allowed Ralekdev's exploit to jump into the SBOOT.bin and execute download mode without security checks. However the code has been replaced..

  if ( !memcmp(v5, "ANDROID!", 8) )
  {
    *** DO NORMAL SECURE BOOT ****
  }
  else
  {
    dprintf("Could not do normal boot. (invalid magic)\n");// this is where we exploited it last time to load my code
    s5p_start_download_mode(v9);
  }
  return 0;
}

So obviously, this execution of arbitrary code exploit has been patched.



Conclusion
We are working to bring a new exploit and make it easier that the last one. Ralekdev will be analyzing and working on a new exploit. I will work on deployment techniques. For now if youre having problems, flash back to stock and root your device.

Sorry for the n00b questions here but I got burned with this about 8 months ago and could not get my phone fixed. I ended up doing a warranty claim on it and haven't rooted since. I have read up quite a bit since then and see that Samsung/VZW really sucks with this stuff. My questions:

1. Can you block these updates permanently? I only did mine after many times where I had to delay them and they only let you delay them about 5 days I think.

2. Will the updates still try to apply if you are running a custom ROM? If I ever root again I will use an alternate ROM if this is the case

3. Would the same thing happen if I had a "Developer edition" of say a Note 3 (If they ever come off backorder status)?

Thanks in advance

 

[mlutzow]

Plug the phone into your computer as an installer. It should install the VZW software tool. Run that and update through that n

All right finally got around to installing the Verizon software and the phone updated to 4.3 without a hitch. Had it rooted within 20 minutes after that with the tools found on this site.

Thanks for the suggestion.,

Sent from my Galaxy Note II using Tapatalk 2

 

[MunkinDrunky]

Sorry for the n00b questions here but I got burned with this about 8 months ago and could not get my phone fixed. I ended up doing a warranty claim on it and haven't rooted since. I have read up quite a bit since then and see that Samsung/VZW really sucks with this stuff. My questions:

1. Can you block these updates permanently? I only did mine after many times where I had to delay them and they only let you delay them about 5 days I think.

2. Will the updates still try to apply if you are running a custom ROM? If I ever root again I will use an alternate ROM if this is the case

3. Would the same thing happen if I had a "Developer edition" of say a Note 3 (If they ever come off backorder status)?

Thanks in advance

Not sure how to block the updates exactly anymore. I think there is an app responsible you can freeze or delete. But don't take my word on this 100%

Most custom roms have the ota blocking feature. I'm mean if you use CM you'll never see these otas. It would only happen for TW roms and only for those stock rooted ones if at all.

I am pretty certain you see the otas on the developer edition since it would come with stock TW.

 

[mlutzow]

Not sure how to block the updates exactly anymore. I think there is an app responsible you can freeze or delete. But don't take my word on this 100%

Most custom roms have the ota blocking feature. I'm mean if you use CM you'll never see these otas. It would only happen for TW roms and only for those stock rooted ones if at all.

I am pretty certain you see the otas on the developer edition since it would come with stock TW.

I'm not 100% sure but freezing the Knox notifications (Andoid 4.3 from Verizon) might do the trick.

Sent from my Galaxy Note II using Tapatalk 2

 

[mwebb34]

my wife bought a verizon galaxy note 2 and its updated to 4.3 is there a way to root and unlock? will saferoot zip work?

Sent from my SM-N900V using XDA Premium 4 mobile app

 

[bkdodger]

my wife bought a verizon galaxy note 2 and its updated to 4.3 is there a way to root and unlock? will saferoot zip work?

Sent from my SM-N900V using XDA Premium 4 mobile app

I'm sure you already got your answer ..but I rooted today with saferoot...no unlock for latest though

N3 tap

 

[xda-arcane]

Well, I'm on vruemj9 and rooted, hoping to help in any way I can to help unlock the bootloader, so if there is anything that needs tested I am willing to flash anything even if I get brick after brick, as long as I can help I will. PM if there is something to try. Thanks devs!

 

[bollyvu]

Twitter app on Android???

Why cant Samsung and Verizon just leave this **** alone and let android be real AOSP.

i can't find twitter app on my Q Mobile DNORE

 

[sokewel275]

Help a Noob unroot

I did Adams Casual Verizon 1 click root with recovery months ago now I want to return to stock to do the OTA update that's been a defer nag. I'm tired of deferring it. How do I return the phone to stock, I tired of searching for the right forum or u-tube vids for a simple straight forward step by step procedure. Right now I have the I605VRAMC3 Build. Someone please advise, this is my 3rd GN2 and I don't want to brick it again. The 1st one I bricked and the 2nd replacement, the phone just stopped sending/receiving data. Then can I run the 1 click again to re-root?

 

[marcustaz]

No need to return to stock, simply go here and read:

Get the Odexed version and flash in recovery. Then flash the new modem/radio using download mode with Odin.

http://forum.xda-developers.com/showthread.php?t=2578458

Sent from my SCH-I605 using XDA Premium 4 mobile app

 

[sokewel275]

No need to return to stock, simply go here and read:

Get the Odexed version and flash in recovery. Then flash the new modem/radio using download mode with Odin.

http://forum.xda-developers.com/showthread.php?t=2578458

Sent from my SCH-I605 using XDA Premium 4 mobile app

Thx marcustaz, I will take a look.

 

[TonikJDK]

I did Adams Casual Verizon 1 click root with recovery months ago now I want to return to stock to do the OTA update that's been a defer nag. I'm tired of deferring it. How do I return the phone to stock, I tired of searching for the right forum or u-tube vids for a simple straight forward step by step procedure. Right now I have the I605VRAMC3 Build. Someone please advise, this is my 3rd GN2 and I don't want to brick it again. The 1st one I bricked and the 2nd replacement, the phone just stopped sending/receiving data. Then can I run the 1 click again to re-root?

You are rooted, so you could also just freeze the app named SDM 1.0 That will kill the nag.

 

[droidstyle]

I did Adams Casual Verizon 1 click root with recovery months ago now I want to return to stock to do the OTA update that's been a defer nag. I'm tired of deferring it. How do I return the phone to stock, I tired of searching for the right forum or u-tube vids for a simple straight forward step by step procedure. Right now I have the I605VRAMC3 Build. Someone please advise, this is my 3rd GN2 and I don't want to brick it again. The 1st one I bricked and the 2nd replacement, the phone just stopped sending/receiving data. Then can I run the 1 click again to re-root?

Taking the update will permanently lock your bootloader. If you do not care to flash custom roms, recoveries, and kernels then proceed. However there a much simpler ways around your problem. The last couple posts explain your options...