What I hate most is when carriers (yes AT&T and Verizon am pointing at you) lock down bootloaders, but what I love most is when developers say “Up Yours” by hacking into them. AT&T LG Optimus G Pro is another example, the bootloader was locked by AT&T but enter djrbliss aka Dan and the bootloader on the AT&T LG Optimus G Pro has been hacked aka lokified.

Warning

Please note this is for AT&T LG Optimus G Pro, build E98010g only. Please do not try to flash any custom roms, kernels or anything from the recovery. This is just proof that the bootloader on the AT&T LG Optimus G pro has been hacked.

Here are the steps if you want to do them, please proceed at your own risk.

1. Download lokified cwm from here
2. untar the file and put it in internal memory of device
3. open adb session and check if your device is being detected by doing adb devices
4. get super user access by typing in su in the adb session
5. do a dd if=/sdcard/cwm-recovery.lok of=/dev/block/mmcblk0p28 to push lokified cwm to  your device
6. Do not do a reboot into recovery, instead turn off your device
7. Once device is turned off volume UP + home + power until you get into recovery

Please and I repeat please do not flash anything from this recovery, this is just a test recovery.

Source:-xda-developers

The post AT&T LG Optimus G Pro Bootloader Hacked appeared first on Android Fan Network.

When AT&T locked the bootloader on their version of the Samsung Galaxy S4 there was an outrage over the internet, but enter djrbliss and the bootloader was hacked, the exploit though was not released immediately because Verizon was yet to ship their version of the Samsung Galaxy S4. As soon as the Verizon Galaxy S4 landed in the hands of people who pre-ordered it the bootloader on the Verizon Galaxy S4 was also hacked.

It’s been a long wait for AT&T users but finally djrbliss has finally released the exploit which will hack the bootloader on the AT&T and Verizon versions of Samsung Galaxy S4. This might be your only chance to hack the bootloaders as Verizon is know for blocking it via software updates and it looks like AT&T is also taking the same route so go for it peeps. Let’s quote djrbliss for a second :-

I just released Loki, a set of tools for developers and users to flash custom kernels and recoveries on the AT&T and Verizon branded Samsung Galaxy S4.

The tool is available at:
https://github.com/djrbliss/loki

The technical details on how the exploit works are described at:
http://blog.azimuthsecurity.com/2013…cure-boot.html

Does this make any permanent changes to the device?

No permanent changes are made to your device when using loki_flash. The bootloader itself is untouched. By restoring the original system, boot, and recovery images (via Odin or otherwise), the device will be in a stock state.

Can this be patched?

Absolutely. Any update that includes a new aboot will almost definitely cause your custom kernel or recovery to fail to boot without running it through loki_patch again, and if the update contains a fix for the vulnerability Loki exploits, it may permanently prevent using the tool. It’s possible for Samsung to ship an update that prevents downgrading aboot to a vulnerable version, so I recommend avoiding installing any OTA updates without confirmation that it’s safe.

This all seems complicated. What about a step-by-step guide?

These tools are primarily intended for developers, who will be able to use them and provide ordinary users with easy ways to flash custom ROMs. Be patient, I’m sure your favorite ROM developer will come up with something for you.

I’ve installed a Loki-patched recovery. Can I just install regular custom ROMs now?

Any ROMs that include a replacement boot.img must be modified to include a Loki-patched boot.lok file instead. Otherwise, your phone will fail to boot until you restore a Samsung-signed boot.img or a custom boot.lok image via your custom recovery, or flash a stock image via Odin.

So this is just like kexec?

This is similar to kexec in that it works around a locked bootloader, but this approach is much more flexible and robust. Kernel and recovery developers can build their projects just as they would for an unlocked device, run the final result through Loki, and then it’s ready to be flashed. No hackery and brokenness required.

And now we wait for our favorite ROM & Kernel developers to use this and bring custom ROMS & kernels to the AT&T & Verizon Galaxy S4.

Please note neither we nor djrbliss is responsible for any bricked devices, you are doing this at your own risk.

Source:-xda

The post Bootloader Hack for Verizon & AT&T Samsung Galaxy S4 Released appeared first on Android Fan Network.

Inspite of AT&T’s efforts (all I can say is “You’ll never shut down the real Napster!”, yes I watched Italian Job last night) the bootloader has been unlocked. The method though will be released once the Verizon Galaxy S4 are shipped . Now for some more good news, a few minutes ago @djrbliss tweeted :-

Successfully booted CyanogenMod on the AT&T Samsung Galaxy S4 with no issues.

It looks like once the bootloader unlock method is made public, we wouldn’t have to wait long to play with CyanogenMod on our AT&T Samsung Galaxy S4. Kudos to you @djrbliss, we all love you!

The post Coming Soon:CyanogenMod for the AT&T Samsung Galaxy S4 appeared first on Android Fan Network.

Dan Rosenberg aka @djrbliss just tweeted the above picture, it says “Samsung Galaxy S4 bootloader hacked by Dan Rosenberg (djrbliss).”. Even though we have no confirmation from Dan that’s it for AT&T Samsung Galaxy S4 but considering the bootloader on the AT&T Samsung Galaxy S4 is the only one which is locked, it’s obvious that he has hacked the bootloader on the AT&T Samsung Galaxy S4.

We will keep you updated once the how to do it is available.

Update

djrbliss has confirmed that the picture above infact is the AT&T Samsung Galaxy S4, and it does allow to flash custom kernels and recoveries, the release will not be until the Verizon Galaxy S4 starts shipping (which will be in late May). The reason for the delayed release being that Verizon is notorious for locking bootloaders as well and in all probability the bootloader on the Verizon Samsung Galaxy S4 will be locked as well, to prevent his exploit from being patched (in case it is released) the release of the exploit has been delayed which makes sense.

Also, we and djrbliss ask you not to take any updates if you want to unlock your bootloader once the exploit is made public.

Source:- djrbliss & xda

The post AT&T Samsung Galaxy S4 Bootloader Hacked appeared first on Android Fan Network.

djrbliss is at it again, the recent root exploit published by him called Motochopper for Motorola devices is working on Qualcomm based versions of Galaxy S4. This means it should work on all versions of Samsung Galaxy S4 released by US Carriers.

Instructions:-

1. Extract the entire contents of the zip file.
2. If you are using Windows, ensure you have installed the latest Samsung USB drivers available for your phone.
3. Ensure USB Debugging mode is enabled on your device.
4. Connect your device to your PC via USB.
5. If you are using Windows, navigate to the extracted directory and execute “run.bat”. If you are using Linux or OS X, navigate to the extracted directory in a terminal and execute “./run.sh”.
6. Approve the ADB connection from your PC on your device.

Download the exploit here.

Happy rooting to all Samsung Galaxy S4 owners.

Source – xda

The post Root Comes to Qualcomm based Samsung Galaxy S4 appeared first on Android Fan Network.

The guy to thank is djrbliss again, you need a 32bit Linux machine to run the exploit (a live cd will also work). It is and will not be possible to run the exploit on a windows machine. The instructions are pretty easy if you follow what’s written. We are not going to copy paste the instructions on here as we find it unethical to do so. Anyways, instructions can be found here (yes you need to register).

The post Root Comes to Droid Bionic and Original Razr (XT910) on JellyBean appeared first on Android Fan Network.