Search results

OP, did you ever get an answer on this? I'm interested in using block copy as well to pull down a complete stock image.

The latter. The bootloader performs a signature check of either the kernel or the recovery, if the check fails you get the unauthorized software screen. I haven't actually read the documentation for the loki exploit, but from memory I believe loki signs the kernel or recovery with insecure...

I've loki patched the latest version. Image is available here.

Connect your phone to your computer via the USB cable. Boot into download mode by holding Volume Down while the phone starts up. Launch Odin, it should say "<Added!>" in the output window. Click "AP" and select the tar file. You can have auto reboot and F-reset Time checked. Flash it. It's...

Relax... I've done it for you... Image or tarball is here: https://www.androidfilehost.com/?a=show&w=files&flid=165084

Please read like the last 10 posts.

Oops - minor oversight. :) There is now a tarball there for you.

You guys are nuts. Look, this is really simple... You go to TWRP.me, and find the build for your phone model. i337 = jflteatt i337m = jfltecan i9505 = jfltexx i545 = jfltevzw M919 = jfltetmo ect. Download it and install it... or install it from GooManager. In this case, you have the "M"...

That's the problem. The download is for jflteatt only. The major difference in the i337 (jflteatt) and i337m (jfltecan) is the bootloader - the former is locked and requires an exploit, the latter is not and does not.

I'm confused... did the patched version not work? If not, what is your phone model and bootloader version?

All of the TWRP 3x builds are unpatched and will fail signature verification by the bootloader. I posted on the TWRP thread about it. But if you'd like to just download the patched version, I put it on AFH for everyone.

As with all of the 3X builds, the new version 3.1.0-0 is not patched with loki, and will fail signature verification by the bootloader. If you flash the new version and get the triangle error, in order to boot back to system, press and hold power to manually restart the phone, and hold the...

Does the device model stop with the "F" in G900F? Therefore I can flash any region firmware/bootloader/modem for the G900F? Or is the initial region firmware relevant in some way? Also, is there any bootloader locking or other security features of newer firmwares that prevent downgrading...

Good morning everyone, Is there any danger to flashing new firmwares? This includes flashing firmwares from other regions. For example, I currently have the Hong Kong region firmware G900FZHUBOA1 (Lollipop) or something like that. Is there any danger in flashing a newer European one (XXU)? I'm...

Good evening S5 users, I see tons of threads with various and sometimes contradictory information about the safety of flashing various things. Can someone who is knowledgeable on the subject enlighten me as to the safety (or not) of flashing newer bootloaders, baseband modems and NON-HLOS? I...

The i337M is the Canadian version of S4 otherwise known as 'jfltecan'. I do not believe it has a locked bootloader. Therefore, you should be able to flash a custom recovery via Odin without any additional effort. Please make sure that you use a recovery that is compatible with jfltecan - this...

Actually, I'm glad you said that because I wasn't sure it would work for others. The loki tool uses your phone's aboot to insert insecure code into the recovery/system image that you are patching. As I don't have a lot of experience, I wasn't sure if aboot was device specific or not - good news!

Where did you hear that? Possibly from the post directly above yours? From TWRP.me, the last patched version is 2.8.7. Both 2.8.4 and 2.8.7 should work for flashing current ROMs. The functionality that you won't have is stuff like F2FS support and earlier versions have issues with encryption...

Hello, The problem with the 3x builds available on twrp.me is that they are not properly patched with the loki exploit. This is required in order for the recovery to not be rejected by the bootloader. The fix is simply patching the recovery image using the loki tool and procedure located here...