I'm looking to update my mom's phone, I honestly don't remember what I did to it in the past. As far as I can tell it's rooted on NC5, with a lock boot loader (I assume although when booting up I see an unlocked lock with the words "custom" underneath it) and knox is 0x0. Does that mean my bootloader is actually unlocked? and am I following this guide (http://forum.xda-developers.com/gal...-to-root-i545vrufnk1-4-4-2-12-1-2014-t2959613) to update to the latest version?
Thanks
You are most likely rooted but for sure your bootloader is still locked. As far as updating, if you don't want to keep root or anything then just odin back to stock and accept an OTA. If you want root then there are other ways to update posted in this forum.
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.
I thought it was necessary to unlock the bootloader on android phones before i could root them and flash different roms. A buddy of mine had rooted his old s3 but forgot to unlock the bootloader, so when he tried restarting it, it soft bricked. For the longest time I thought you had to unlock the bootloader then root the phone in order to flash custom roms, have I been wrong all this time?
Think of the Loki workaround as a way to trick the bootloader into flashing improperly signed files. Its like using a credit card on the bolt of a locked door. The door is still locked but you get through anyway.
brizey said:
Think of the Loki workaround as a way to trick the bootloader into flashing improperly signed files. Its like using a credit card on the bolt of a locked door. The door is still locked but you get through anyway.
Click to expand...
Click to collapse
And what are the risks of using the loki tool if you use it correctly? if there is an OTA update to the phone, will it mess it all up?
You don't you the tool...the developers do. And technically, it is only used for flashing a recovery and flashing ROMS with the recovery. You can root without unlocking the bootloader because there is an pre-release official rootable kernel than can be flashed with Odin. It flashes because it is legit.
So I should be able to just go to the how to root page on here http://forum.xda-developers.com/showthread.php?t=2290798 and follow the instructions and flash one of the roms as usual?
yes,go ahead
It's a tough thing to search for. Google thinks I'm looking to root or unlock my phone.
I've followed the steps in a video thread entitled "[HOW TO] Unbrick, Unroot, Relock Verizon Galaxy S4" successfully. However the padlock icon is unlocked when the device boots up.
Can Odin or similar tool re-lock the bootloader of an ME7 Galaxy S4?
Do I need to PDA back to MDK?
Not concerned with losing files. Just need to return the device to factory stock.
Well first of all you might be a little confused here... the ME7 firmware currently has no way to unlock the bootloader yet so if you somehow found a way please share with us and collect your money
Anyway, you can get back to stock using this guide: http://forum.xda-developers.com/showthread.php?t=2301259
I have a locked brand new s4 if you wanna trade lol
Sent from my SCH-I535 using Tapatalk
b237696 said:
It's a tough thing to search for. Google thinks I'm looking to root or unlock my phone.
I've followed the steps in a video thread entitled "[HOW TO] Unbrick, Unroot, Relock Verizon Galaxy S4" successfully. However the padlock icon is unlocked when the device boots up.
Can Odin or similar tool re-lock the bootloader of an ME7 Galaxy S4?
Do I need to PDA back to MDK?
Not concerned with losing files. Just need to return the device to factory stock.
Click to expand...
Click to collapse
Boot into recovery and clear the cache.
My phone is rooted with xposed framework with Wanam Xposed and I don't have the screen that indicates "custom" and my device shows up as official in the about screen.
I also have taken the recent OTA.
That worked, Craw.
Thank you & goodnight.
Want some Views of YOu All . Currently i am on MJ7 Bootloader and 4.3 firnware version and thinking of getting an update to NC5 With Bootloader . What you guys think Or should i wait for some Miracle .?? Dont tell me to upgrade without bootloader because there is an annoying Bug where i cant charge my phone in power off(IT turns on automatically) because off bootloader and firmware incompatibility. Thanx.
You just need to upgrade your bootloader to mk2 to get rid of the bug. That's a problem with mj7, which is why mk2 came out so quick after. You can even downgrade the mk2 bootloader back to mj7. But between staying on mk2 bootloader or moving on to nc5, I would move on. Theoretically something COULD happen but you won't find anyone on the net who is still working on unlocking that firmware.
joshm.1219 said:
You just need to upgrade your bootloader to mk2 to get rid of the bug. That's a problem with mj7, which is why mk2 came out so quick after. You can even downgrade the mk2 bootloader back to mj7. But between staying on mk2 bootloader or moving on to nc5, I would move on. Theoretically something COULD happen but you won't find anyone on the net who is still working on unlocking that firmware.
Click to expand...
Click to collapse
Thanx . Gonna try it.
Hey everyone, I've done some research and found plenty of people trying to keep root while accepting an OTA, but couldn't find anything pertaining exactly to my question. does anyone know if i accept the next OTA from att will it unroot and remove the tampered banner on my m8? all i've done is root my device. haven't changed anything or flashed anything other than twrp recovery. just want to go back to stock as easily as possible.
thanks for any help
stumcmahan said:
Hey everyone, I've done some research and found plenty of people trying to keep root while accepting an OTA, but couldn't find anything pertaining exactly to my question. does anyone know if i accept the next OTA from att will it unroot and remove the tampered banner on my m8? all i've done is root my device. haven't changed anything or flashed anything other than twrp recovery. just want to go back to stock as easily as possible.
thanks for any help
Click to expand...
Click to collapse
You need to flash stock recovery, or the OTA won't install. In fact, you might even get stuck in a bootloop as the phone repeatedly boots into TWRP, looking for stock recovery (to install the OTA) and not finding it.
Also, if any system files have been modified by root, you need to return them to "stock" state. Otherwise the OTA will fail to install, saying the system has been modified. You can either return any system files to stock manually, or flash a stock ROM, nandroid, or RUU.
You will lose root when you OTA. But its an easy manner to just flash TWRP again, and flash SU/SuperSU to gain root. Unlocked bootloader is okay for OTA, so you don't even need to relock, unlock again, etc. to flash TWRP. But locked bootloader is required for RUU (unless you have s-off) if you choose that route in the paragraph above.