I just got the Note 2 from Newegg (for verizon) and after reading through a lot of the threads on this forum like:
How to Unlock Your Bootloader - Firmware Version VRALJB
and
[Q] Stock restore Fail at sboot.bin
and
Questions about Unlocking or Recovering from a Soft Brick
I guess there's issues with the OTA verizon pushed out and the first guide won't work if you have the OTA. Well long story short, how can I tell for sure if the phone I've received had the latest updates put on it before I got it?
My build says VRALJB, does that mean I'm good and I still have the older version? Would it say VRALL4 if the OTA had been applied?
In a related question, would it be wise to simply update to VRALL4 now, use the new method to jailbreak, and then continue on my merry way? Would this alleviate any worries of the OTA getting applied and breaking my root / possibly bricking my phone??
Thanks for any help for a noob. I tried to do research first!
You do not have the ota..... Use original method!!
Sent from my most awesome phone EVER!!!!
As stated above you are on the original baseband VRAJB so you can use the original root and unlock method. Once you are unlocked, do not take a OTA ever as you may get relocked and who knows if there will be a future unlock method. Most of the custom ROMs block the updates, but just in case don't take it if you ever get the message.
Once you are unlocked you will use TWRP custom recovery (which is the screen that will appear at the end of the unlock process). You can flash the VRALL4 baseband when you flash a ROM if you want to be on the latest baseband (flash ROM first then immediately flash VRALL4, no reboot in between). The download can be found here: http://forum.xda-developers.com/showthread.php?t=2108510
Thanks for the replies.
There's a video on the Adam Outler Jailbreak Guide that actually suggest getting the OTA first and then just doing the CASUAL thing afterwards. Personal preference or is there some advantage?
The video in question is the first one in the thread, it is titled "Jailbreak video for Windows users only!
This video desmonstrates CASUAL used with Odin to flash the Galaxy Note 2 firmware Thanks to DroidModderX" and the timeframe in question is 00:50 to 01:10
Just wondering, thanks!
No real advantage either way (the update to VRALL4 was very minor but did relock the bootloader). If you want to be on the latest update you either need to take it OTA or flash it yourself. I was on VRAJB and unlocked before the update so I only had the original method to work with. I updated to VRALL4 manually by flashing it.
Bottom line, either way will work, just make sure if you take the OTA before doing anything that you use the correct unlock method (the "new" one). The whole thing will take you maybe 10 minutes, its really easy. The video is a great guide.
Related
Just curious if the new 2.3.4 gingerbread OTA can be unlocked using pudding. I'm having to get my atrix replaced via warranty and if the replacement happens to come with gingerbread already on it i want to know if i'll be able to unlock it or if i'll be stuck using p-roms.
You should be able to unlock it with pudding since its the same version of gingerbread that we have. Also, don't flash any sbf files (except pudding) because it has the new bootloader and you'll hard brick it if you do.
You can unlock with pudding and fastboot BUT there's a high chance you'll soft brick first with 0x1000 ... all you need to do is get into fastboot mode and redo the oem unlock command.
mysticdrew said:
You can unlock with pudding and fastboot BUT there's a high chance you'll soft brick first with 0x1000 ... all you need to do is get into fastboot mode and redo the oem unlock command.
Click to expand...
Click to collapse
Alright, just to be absolutely, completely, all the way, 101% sure: does this OTA have ANY bootloader restrictions, be they a brick or non-unlockable bootloader. Has anybody tried to unlock the bootloader and run a custom ROM on the AT&T OTA? I just want to be able to run custom ROM's down the road (as in full ROM's, as in Cyanogenmod).
Do the OTA and never, never go back to any older stock version via RSD. Or you'll brick your phone.
@Chairsofter1138: the ota bootloader is locked. flash the pudding to unlock.
Alright, has anyone actually attempted to unlock the OTA via the pudding method? I'm being extra cautious here because I don't want to be stuck with a permanently locked down phone. Does it matter, then, if I use Kenthepenns (sp?) installation method or OTA straight from AT&T/ Motorola?
Chairsofter1138 said:
Alright, has anyone actually attempted to unlock the OTA via the pudding method? I'm being extra cautious here because I don't want to be stuck with a permanently locked down phone. Does it matter, then, if I use Kenthepenns (sp?) installation method or OTA straight from AT&T/ Motorola?
Click to expand...
Click to collapse
Yes everyone has been unlocking via pudidng because it's the same leaked version that has been out for the past couple weeks.
Yes Going to this OTA will make a brickable phone. You WILL NOT BE ABLE TO DOWNGRADE via traditional SBF.
This is the question everyone has been asking on every thread and the devs aren't answering.
I am locked and stock on 1.83. My fuse HAS not been burnt. I want to be
1. On Gingerbread
2. Unlocked
The problem is that all the current gingerbread sbfs said you had to be ALREADY unlocked to flash them, so I don't know how anyone has been testing this OTA with a locked bootloader. If you had the new Gingerbread, you were already unlocked, is how I understood it.
Questions in follow up to the above:
1. If I OTA before unlocking, what do I flash afterwards to unlock? Saying 'pudding' because there's 10,000 files in that thread, including links to an 'unlocker.sbf', as well as a full sbf operating system. What specific file?
2. Lots of new builds say they have an 'unlocked bootloader' built in, but nobody can figure out what that means. Does that mean you can flash them without being unlocked to unlock? What do you need to do to unlock after you flash them?
3. If I unlock now at stock 1.83, and take the OTA, what happens, is the bootloader locked again? I know OTA installs a new bootloader.
Please someone help me understand. There's too much hard bricking and misinformation out there on all the dev threads. What's true (and please tell us how you know).
I noticed everyone talking about the OTA. I saw on the Moto site that the new update is only available OTA but there's a link for download for the file "Blur_Version.4.5.91.MB860.ATT.en.US". Can anyone confirm that this can be installed without brick on an unlocked bootloader? I've seen other threads stating so but they're not really clear on what's being said.
m0use1 said:
This is the question everyone has been asking on every thread and the devs aren't answering.
I am locked and stock on 1.83. My fuse HAS not been burnt. I want to be
1. On Gingerbread
2. Unlocked
The problem is that all the current gingerbread sbfs said you had to be ALREADY unlocked to flash them, so I don't know how anyone has been testing this OTA with a locked bootloader. If you had the new Gingerbread, you were already unlocked, is how I understood it.
Questions in follow up to the above:
1. If I OTA before unlocking, what do I flash afterwards to unlock? Saying 'pudding' because there's 10,000 files in that thread, including links to an 'unlocker.sbf', as well as a full sbf operating system. What specific file?
2. Lots of new builds say they have an 'unlocked bootloader' built in, but nobody can figure out what that means. Does that mean you can flash them without being unlocked to unlock? What do you need to do to unlock after you flash them?
3. If I unlock now at stock 1.83, and take the OTA, what happens, is the bootloader locked again? I know OTA installs a new bootloader.
Please someone help me understand. There's too much hard bricking and misinformation out there on all the dev threads. What's true (and please tell us how you know).
Click to expand...
Click to collapse
+1 to everything this guy said..There is a ton of guests in this forum wondering the same **** too. Devs are doing a fantastic job, but us end users (including myself) don't really have a sense of direction right now.
Ok Iv noticed that things are getting really really confusing around here with people saying one thing then someone else saying something else. I want to have a thread that is straight forward coming from people that know what they are talking about and not just assuming.
Now my phone has never had an unlocked bootloader. Before I updated to GB OTA i was on .83 rooted with all the mods added to it (webtop dock, blah, blah blah) I RSD back to .26 (that very old file) and just started doing OTA updates one by one once i logged in with my blurr account. I updated to GB via the official OTA update that was pushed to my phone when i selected to system update under settings.
I was able to Root this ATT OFFICIAL version pushed to my phone using This Pre-install method and that is all that i have done.
What i want to do now is Unlock the bootloader. From what i have read Pudding is the best way of doing this.
Q1: Does this method (Pudding) work with the Official ATT OTA version pushed to phones and not Kenns modded version, and is it the only way to unlock the bootloader?
Q2: Once unlocked what version of CWR do I install to be able to flash ROMs? Would i be able to just install ROM Manager and do the installation from there, Or possibly both ROM Manager and CWR?
Q3: Since RSD is out of the picture for me, if for some reason I'm to soft brick my phone and can still get into Recovery mode, what .sbf do i flash, would it have to be the same one that was pushed to phones that if not already available on here will be really soon?
Thanks for all the help if anyone helps out.
StyleUkno
Q2, if you unlock your phone, cwM of tenfars, the 2nd version for unlocked. Rom manager with official CWM have released before some days, but yet it doesn't support external sd.
As for question 1, and the unlocking pudding. The OTA gb you installed, might updated you bootloader, and maybe can't use that pudding.
For that be very carefull of your next steps.. Personally I would have send a pm to the2dcour, or another dev that knows as much..
Sent from my MB860 using XDA App
Bump to see if any other responses come.
Q1: Does this method (Pudding) work with the Official ATT OTA version pushed to phones and not Kenns modded version, and is it the only way to unlock the bootloader?
Yes, pudding works and is the only way. Have to Flash pudding and run OEM unlock command in fastboot. Because you are already on OTA, there's a high chance you will need an extra couple steps. It will likely soft brick with 0x1000 error but wit fastboot option. From there you need to fastboot and re do the oem unlock command another time. Then you are fine.
Q2: Once unlocked what version of CWR do I install to be able to flash ROMs? Would i be able to just install ROM Manager and do the installation from there, Or possibly both ROM Manager and CWR?
Tenfar's 6/30 unlocked CWM. ROM Manager version doesn't properly wipe as of yet. You can update if you dont' care about wiping, but that usually leads to boot loops when installing roms. Also most devs here are using update scripts tailored for tenfars version
Q3: Since RSD is out of the picture for me, if for some reason I'm to soft brick my phone and can still get into Recovery mode, what .sbf do i flash, would it have to be the same one that was pushed to phones that if not already available on here will be really soon?
if you softbrick (other than the initial unlock soft brick where you just run oem unlock again) then depends on what you want to get to. CWM a rom.zip/fruitcake for the version you want would be ideal. If not then a fastboot version if available. I'd RSD the GB 4.5 with pudding sbf as a last resort.
StyleUkno said:
Ok Iv noticed that things are getting really really confusing around here with people saying one thing then someone else saying something else. I want to have a thread that is straight forward coming from people that know what they are talking about and not just assuming.
Now my phone has never had an unlocked bootloader. Before I updated to GB OTA i was on .83 rooted with all the mods added to it (webtop dock, blah, blah blah) I RSD back to .26 (that very old file) and just started doing OTA updates one by one once i logged in with my blurr account. I updated to GB via the official OTA update that was pushed to my phone when i selected to system update under settings.
I was able to Root this ATT OFFICIAL version pushed to my phone using This Pre-install method and that is all that i have done.
What i want to do now is Unlock the bootloader. From what i have read Pudding is the best way of doing this.
Q1: Does this method (Pudding) work with the Official ATT OTA version pushed to phones and not Kenns modded version, and is it the only way to unlock the bootloader?
If you use the pudding you will hard brick on the OTA (from what people have been saying)
Q2: Once unlocked what version of CWR do I install to be able to flash ROMs? Would i be able to just install ROM Manager and do the installation from there, Or possibly both ROM Manager and CWR?
Out of the picture becuase you cant unlock I think
Q3: Since RSD is out of the picture for me, if for some reason I'm to soft brick my phone and can still get into Recovery mode, what .sbf do i flash, would it have to be the same one that was pushed to phones that if not already available on here will be really soon?
Thanks for all the help if anyone helps out.
StyleUkno
Click to expand...
Click to collapse
asldkjghaa
My husband and I got our phones through AT&T (US) on Froyo; after the Gingerbread update I unlocked my bootloader & went the custom rom route while he stuck with root access.
So he unrooted & took the 4.5.141 update OTA; I took mine via Nottachtrix. Now he's asking about unlocking his BL too.
a) Is it possible without bricking? Seriously. Was the bricking issue earlier this year related to folks with unlocked BLs taking the OTA update, or folks trying to unlock after taking the OTA update?
b) I did mine by flashing pudding and unlocking through fastboot (then soft-bricking, then proceeding with fastboot anyway yada yada). Now I see this one-click-tool thing being thrown about. Should I be using that instead, or is there an updated "pudding" SBF I should be using?
c) Since megaupload went to pot, how valid are the original threads that contain these files? Still feels weird to think of "old" things as being ~10 months past. Ah well.
Use the unlocking sbf in the Android Development section sticky (pudding thread). It shouldn't give you any chance of a brick. It's called "try sbf" or something along those lines. Once flashed via RSD Lite, you fastboot oem unlock, copy your unique code and fastboot oem unlock "code" (without quotations). You have a chance of brick if you SBF down to a firmware lower than your current one, as it tries to flash new bootloader and will fail. AFAIK, you're even safe to reflash 4.5.141 OTA but people don't encourage it as you can easily confuse yourself and flash Froyo instead which WILL make you brick.
Biggest question is should I root before taking any OTA's (like 4.1.2) it wants to get something but I keep saying no until I know better.
Next is OF COURSE what root and bootloader unlock is best?
From what I have read it looks like the toolkit or ExynosAbuse APK v1.40.
Thanks in advance
There is only one bootloader unlock method (which will include root) for each baseband (VRALJB or VRALL4). Determine which you are on (settings > about phone > baseband version) and then follow Adam Outler's method for your baseband. Easy. From there you will be able to flash ROMs, etc. Once you are unlocked, rely on the dev community for updates, not OTAs...they are faster than Verizon every time and you know what you are getting. When Verizon rolls out an OTA, you never know what's included ( for example with the VRALL4 update they relocked everyone's bootloader).
Im sorry if this has been answered in other threads im simply trying to help a friend out with rooting and possibly unlocking the boot loader? Can someone point me in the rite direction? It would be most appreciated
I would check the Verizon LG G3 forums where there are many instances of your questions having been already thoroughly answered.
What you will find is that you must be on v10b firmware, which you can downgrade to using either the .kdz or the .TOT method, then you can root v10b (only) with StumpRoot, or ioRoot, or PurpleDrake, before the phone updates back to v12b. With SuperSu in survival mode root can be retained through either of the current OTA updates (which provide very little enhancement beyond patching root exploits), so far, and with root you can install a specially modified TWRP recovery which will allow the flashing of unsigned kernels and roms.
There. You are on your own from hete on.
Sent from my VS985 4G using Tapatalk
use flashify to install the bumped version of twrp (get it from the original development section). Worked like a charm. Plenty of bumped roms to grab in the dev section.
gothicasshole said:
Im sorry if this has been answered in other threads im simply trying to help a friend out with rooting and possibly unlocking the boot loader? Can someone point me in the rite direction? It would be most appreciated
Click to expand...
Click to collapse
There is no unlocking of the bootloader. Bumping doesn't unlock the bootloader. However, it fools the phone into allowing the flashing of custom ROMs and kernels without unlocking the bootloader. Basically, the phone "believes" that whatever is being flashed (via TWRP) is acceptable and allows the image to pass the "security check" that is done when flashing. It's the same thing as IF the bootloader were unlocked, but in reality, it isn't unlocked. It's a security exploit, kind of like rooting this phone is a security exploit.
However, a quick OTA patch from Verizon or LG could make either or both no longer work. In fact, some OTAs have fixed the root exploit on some models, so you have to flash back to a previous version to root.
You have to root first, then you can flash TWRP.
As stated, there are plenty of FAQs in the general G3 section that help explain all of this.
OK thanks guys. Um just used to seeing a sticky on root under original android development I have no idea what firm ware he's running ik how restrictive big red can be at&t is no better but that's why when they offered a nexus I went and grabbed it
He's wanting a lollipop rom
gothicasshole said:
He's wanting a lollipop rom
Click to expand...
Click to collapse
Go here which gives a whole list of things, including how to root, how to bump, how to flash, etc:
http://forum.xda-developers.com/lg-g3/help/help-thread-lg-g3-question-t2947298
It's where I went before I got this phone to be sure I could do all the things I wanted to.
Thank you
I'll definitely refer him