Database Users

[Q] i337 - MF3 v4.2.2; unable to change ROM

I currently have the Samsung Galaxy S4 - MF3; v4.2.2; i337. I got the phone unlocked (direct from AT&T); and then
1. followed this method to root my phone - http://forum.xda-developers.com/showthread.php?t=2387577- Worked.
2. Got Safestrap v3.65 - http://blog.hash-of-codes.com/downloads/safestrap/ - Worked.
3. Tried 3-4 different ROMs, none of them have worked.
a. http://forum.xda-developers.com/showthread.php?t=2356276
b. http://forum.xda-developers.com/showthread.php?t=2418522
c. http://forum.xda-developers.com/showthread.php?t=2630085
d. http://forum.xda-developers.com/showthread.php?t=2537495
4. Tried above ROMs with kernels from here - http://forum.xda-developers.com/showthread.php?t=2292341 (v4.2.2 or v4.4 - depending on the ROM) and also the MF3 kernel (can't find the link)
But, irrespective of what I try, I still get stuck while loading the ROM - blank screen, not moving forward. Could you please shed some light on what I should try to do?
Thanks!

Vishoka said:
I currently have the Samsung Galaxy S4 - MF3; v4.2.2; i337. I got the phone unlocked (direct from AT&T); and then
1. followed this method to root my phone - http://forum.xda-developers.com/showthread.php?t=2387577- Worked.
2. Got Safestrap v3.65 - http://blog.hash-of-codes.com/downloads/safestrap/ - Worked.
3. Tried 3-4 different ROMs, none of them have worked.
a. http://forum.xda-developers.com/showthread.php?t=2356276
b. http://forum.xda-developers.com/showthread.php?t=2418522
c. http://forum.xda-developers.com/showthread.php?t=2630085
d. http://forum.xda-developers.com/showthread.php?t=2537495
4. Tried above ROMs with kernels from here - http://forum.xda-developers.com/showthread.php?t=2292341 (v4.2.2 or v4.4 - depending on the ROM) and also the MF3 kernel (can't find the link)
But, irrespective of what I try, I still get stuck while loading the ROM - blank screen, not moving forward. Could you please shed some light on what I should try to do?
Thanks!
Click to expand...
Click to collapse
ROM's C and D didn't work because they're AOSP ROMs, and 4.4. You can't cross versions. Besides that, I'd get the safestrap 3.65 APK from our own safestrap thread to make sure you get the correct JFLTEATT version and the MF3 kernel modules which you need to flash after every ROM. What exactly is your process for flashing, and what slot are you flashing to?

DeadlySin9 said:
ROM's C and D didn't work because they're AOSP ROMs, and 4.4. You can't cross versions. Besides that, I'd get the safestrap 3.65 APK from our own safestrap thread to make sure you get the correct JFLTEATT version and the MF3 kernel modules which you need to flash after every ROM. What exactly is your process for flashing, and what slot are you flashing to?
Click to expand...
Click to collapse
Thanks for the prompt reply! Appreciate it. I did get the exact safestrap 3.65 APK from my JFLTEATT version.
I'm flashing into Slot 1. Size - 1GB, 1GB, 300MB. I'm not entirely sure what you mean by what process, by here goes - Factory Wipe, Flash ROM, Flash MF3/v4.2.2 Kernal, Wipe Dalvik/Cache, attempt to fix permissions (always fails with same message). Restart into slot 1.

Vishoka said:
Thanks for the prompt reply! Appreciate it. I did get the exact safestrap 3.65 APK from my JFLTEATT version.
I'm flashing into Slot 1. Size - 1GB, 1GB, 300MB. I'm not entirely sure what you mean by what process, by here goes - Factory Wipe, Flash ROM, Flash MF3/v4.2.2 Kernal, Wipe Dalvik/Cache, attempt to fix permissions (always fails with same message). Restart into slot 1.
Click to expand...
Click to collapse
I would try bigger partition sizes. Leave them at their defaults, because sizing them down likes to cause issues sometimes. Also, flashing that kernel does nothing as safestrap never touches the kernel partition. You do still need the MF3 module zip from the Safestrap thread however. Also, if you've previously flashed a ROM in the slot, you need to wipe the system in that slot too.

DeadlySin9 said:
I would try bigger partition sizes. Leave them at their defaults, because sizing them down likes to cause issues sometimes. Also, flashing that kernel does nothing as safestrap never touches the kernel partition. You do still need the MF3 module zip from the Safestrap thread however. Also, if you've previously flashed a ROM in the slot, you need to wipe the system in that slot too.
Click to expand...
Click to collapse
Thanks again for the prompt reply, I hope you don't mind me taking more of your time. But, I'm having a hard time finding "latest" ROMs for my version, could you point me to one? I've been scouring through Android Original Development, but they're all 4.3 and 4.4, versions you said I couldn't cross-install. Thank in advance!

DeadlySin9 said:
I would try bigger partition sizes. Leave them at their defaults, because sizing them down likes to cause issues sometimes. Also, flashing that kernel does nothing as safestrap never touches the kernel partition. You do still need the MF3 module zip from the Safestrap thread however. Also, if you've previously flashed a ROM in the slot, you need to wipe the system in that slot too.
Click to expand...
Click to collapse
I tried what you said, and it worked! With ROM (a), I'm now running into System UI ran into an error, problem. Still looking around.

Vishoka said:
I tried what you said, and it worked! With ROM (a), I'm now running into System UI ran into an error, problem. Still looking around.
Click to expand...
Click to collapse
Did you sign in to a google account at the initial setup? I know there's some issues involving that on the Google ROMs.

Installation Aborted - Status 7 (expected 5 arguments, got 4)

I've been trying to flash TheAxman 's [ROMS][ViSiON-X STOCK SHOP][i9505/i337][ViS-STOCK][STABLE BASES][03-18] but i keep getting a status 7, installation aborted error which claims that the the expected number of arguments is 5, got 4.
the steps i did to get this error message were:
wipe data/ factory reset --> wipe cache --> format system --> wipe dalvik --> install VisionX's rom
My device is the i337m, its unlocked im with telus
i attached a screenshot of the about phone info for reference.
The device is rooted using cf-auto, and has cwm 6.0.4.7 installed, running on 4.2.2 stock ROM
Now from what i understood in the installation instructions, I should be flashing my carrier's kernel after installing the new ROM, but i cant even get past the rom installation.. I read around the forums that this might be due to a broken updater script, I 'm also iffy as to where/ how I could get a hold of my carriers kernel file to use after (hopefully) i get Vision-X installed on the device..
according to ktoonsez, I should use [KERNEL][TMO][AOSP/TW/GE - 4.4/4.3/4.2][03/12/2014] KT-SGS4 - MJ5 - KTweaker
lastly, i dont know if this is relevant, but in the CWM log i have a message that shows up saying the following
"can't partition non mmcblk device: /devices/platform/msm_sdcc . 2/mmc_host/mmc2"
thank you in advance for your time and assistance

Anyone?
happiness is a warm mug

The French Tickl3r said:
I've been trying to flash TheAxman 's [ROMS][ViSiON-X STOCK SHOP][i9505/i337][ViS-STOCK][STABLE BASES][03-18] but i keep getting a status 7, installation aborted error which claims that the the expected number of arguments is 5, got 4.
the steps i did to get this error message were:
wipe data/ factory reset --> wipe cache --> format system --> wipe dalvik --> install VisionX's rom
My device is the i337m, its unlocked im with telus
i attached a screenshot of the about phone info for reference.
The device is rooted using cf-auto, and has cwm 6.0.4.7 installed, running on 4.2.2 stock ROM
Now from what i understood in the installation instructions, I should be flashing my carrier's kernel after installing the new ROM, but i cant even get past the rom installation.. I read around the forums that this might be due to a broken updater script, I 'm also iffy as to where/ how I could get a hold of my carriers kernel file to use after (hopefully) i get Vision-X installed on the device..
according to ktoonsez, I should use [KERNEL][TMO][AOSP/TW/GE - 4.4/4.3/4.2][03/12/2014] KT-SGS4 - MJ5 - KTweaker
lastly, i dont know if this is relevant, but in the CWM log i have a message that shows up saying the following
"can't partition non mmcblk device: /devices/platform/msm_sdcc . 2/mmc_host/mmc2"
thank you in advance for your time and assistance
Click to expand...
Click to collapse
Check if your download is good first. However, I don't believe you can use that kernel as it says I337 and not I337m.

Installation Aborted - Status 7 (expected 5 arguments, got 4) > Reply to Thread
DeadlySin9 said:
Check if your download is good first. However, I don't believe you can use that kernel as it says I337 and not I337m.
Click to expand...
Click to collapse
thank you for your input, I will redownload the file to cross that out. as for the kernel, how/where might I be able to find it? Can I simply use the stock kernel on 4.2.2 from telus ?

The French Tickl3r said:
thank you for your input, I will redownload the file to cross that out. as for the kernel, how/where might I be able to find it? Can I simply use the stock kernel on 4.2.2 from telus ?
Click to expand...
Click to collapse
Stock kernel will work as long as you're only using other 4.2.2 Touchwiz ROMs. Otherwise, you can check the development section for any kernel thread that lists I337m

DeadlySin9 said:
Stock kernel will work as long as you're only using other 4.2.2 Touchwiz ROMs. Otherwise, you can check the development section for any kernel thread that lists I337m
Click to expand...
Click to collapse
Kernel is right. TMO for the I337M.
I've had status 7 errors before using philz and they were solved using 1 of 2 methods. First, I would check the rom for asserts (txt at the beginning of the updater-script that checks ur device version code against those intended for the roms use). If u find an assert in the script, just delete it and try the install again.
Second thing u could try that worked for me was (idk if standard cwm has this option but philz does) checking the 'allow old update binary' box in the settings. If it's not there, try philz or twrp.
Lastly, like deadly said, don't flash the kernel til u get the ROM to boot. That way troubleshooting is easier

thank you both for your valuable input. I will give it another shot

Recovery..
The French Tickl3r said:
I've been trying to flash TheAxman 's [ROMS][ViSiON-X STOCK SHOP][i9505/i337][ViS-STOCK][STABLE BASES][03-18] but i keep getting a status 7, installation aborted error which claims that the the expected number of arguments is 5, got 4.
the steps i did to get this error message were:
wipe data/ factory reset --> wipe cache --> format system --> wipe dalvik --> install VisionX's rom
My device is the i337m, its unlocked im with telus
i attached a screenshot of the about phone info for reference.
The device is rooted using cf-auto, and has cwm 6.0.4.7 installed, running on 4.2.2 stock ROM
Now from what i understood in the installation instructions, I should be flashing my carrier's kernel after installing the new ROM, but i cant even get past the rom installation.. I read around the forums that this might be due to a broken updater script, I 'm also iffy as to where/ how I could get a hold of my carriers kernel file to use after (hopefully) i get Vision-X installed on the device..
according to ktoonsez, I should use [KERNEL][TMO][AOSP/TW/GE - 4.4/4.3/4.2][03/12/2014] KT-SGS4 - MJ5 - KTweaker
lastly, i dont know if this is relevant, but in the CWM log i have a message that shows up saying the following
"can't partition non mmcblk device: /devices/platform/msm_sdcc . 2/mmc_host/mmc2"
thank you in advance for your time and assistance
Click to expand...
Click to collapse
that recovery using these?

I switched to twrp 2.6.3.0, and im not getting the stat7 error anymore. granted, im also trying to flash a different rom, slimkat.
problem now is that im getting stuck on the splash screen with the sammie logo..

The French Tickl3r said:
I switched to twrp 2.6.3.0, and im not getting the stat7 error anymore. granted, im also trying to flash a different rom, slimkat.
problem now is that im getting stuck on the splash screen with the sammie logo..
Click to expand...
Click to collapse
You flashed the ROM and Gapps and made sure to wipe data right? Also, which one are you flashing (which model)?

DeadlySin9 said:
You flashed the ROM and Gapps and made sure to wipe data right? Also, which one are you flashing (which model)?
Click to expand...
Click to collapse
hi deadlysin9,
thank you for the follow up
steps were:
boot to twrp 2.6.3.0 recovery, wipe data, cache, system and dalvik
then flash rom and gapps
my device is the i337m (telus but unlocked) and im using the jflteatt found here,

The French Tickl3r said:
hi deadlysin9,
thank you for the follow up
steps were:
boot to twrp 2.6.3.0 recovery, wipe data, cache, system and dalvik
then flash rom and gapps
my device is the i337m (telus but unlocked) and im using the jflteatt found here,
Click to expand...
Click to collapse
Try using the jfltetmo build, from what I've read t-mobile ROMs and kernels work on the I337m. If that doesn't work the international build is the next best bet.

hello,
just a quick update on our latest discussion, it seems that the tmo build is indeed the right one to flash, ive finally rid myself of TW, and running on slimkat. many thanks for your valuable input.

[HOWTO] My journey from Stock MJE to Hyperdrive KK RLS8 (rooted) w/ Safestrap 3.72

I am posting this here because I saw others asking and with my experience last night these are the links and software guides and downloads I used to piece together the process of going to HD KK RLS8 from MJE.
Thanks and credit go to the people in the links who originally created these methods and small guides. I just brought them together in one easy to find resource based on my experience of performing this process. You do this at your own risk.
I decided to take this plunge last night after my phone was damaged and my new replacement arrived in the mail. Here are my steps on how I went from Stock MJE (no root) to Hyperdrive Kitkat 4.4.2 rom with root and Safestrap 3.72
This guide assumes you already have your Samsung USB drivers installed as well as Odin downloaded. (As well as a basic knowledge on how to use it).
Step one: I was having problems with Kingo saying failing to root so I downloaded vroot from http://www.mgyun.com/en/getvroot
Parts of this are in Chinese, but you can use the common guess that OK is on the Right side of the popup, Cancel on the left. ETC. At some point it will ask to install the mlkcamera and root security app, you need to accept the install of these to obtain root. After doing so, vroot rooted my phone in under 2 minutes. It leaves behind two apps. You can follow http://www.w0lfdroid.com/2013/11/How-to-Remove-Replace-VRoot-Chinese-superuser-with-SuperSU.html for how to replace these two Chinese apps with the normal popular SuperSU.
Step two: Once rooted and with the new SuperSU installed, I then proceeded to install Safestrap 3.65. Found at http://forum.xda-developers.com/showthread.php?t=2517610 (Both 3.65 and 3.72 download links are here, download both as you will need both).
Step three: Download and place the rom you wish to use onto your external SD CARD in your phone, for this example we will use the Stock 4.4.2 Kitkat with root available in Odex or Deodex. http://forum.xda-developers.com/showthread.php?t=2726558
Step four: Next make sure to download the FIRMWARE link from the same link above, it is directly below the Odex or Deodex links. Make sure to extract this from its zip as it is currently in .md5.zip format which once extracted will be n900v_kk_firmware.tar.md5
Step five: Boot into safestrap recovery. Perform a default wipe of the system. Next make sure you are on the STOCK slot (should be by default). Now select Install and select the new hltevzw_root_odex_nc2.zip file. This will flash to your stock slot. DO NOT REBOOT HERE ONCE DONE, hit the back button in the bottom right corner to get back to the main page, then choose to reboot to DOWNLOAD mode.
Step six: Now your in download mode (and have already hit UP to start download mode). Open ODIN on your PC, plug in your phone and wait for it to identify its COM port. Now select the FIRMWARE file you previously downloaded and extracted: n900v_kk_firmware.tar.md5 in AP and click on Start. This now flashes the new firmware needed for Kitkat.
Step seven: Boot back into recovery and do one more wipe (I originally skipped this step but had a TON of FC app errors which I fixed by wiping again, hence adding this step) Then reboot into the stock Kit Kat 4.4.2 with root.
Step eight: Download safestrap 3.72, Run the new Safestrap and click the Uninstall recovery button, then click Install, next reboot to recovery!
At this point I booted into recovery and installed the ROM Hyperdrive, which is a 4.4.2 rooted highly tweaked rom which I have to say is ABSOLUTELY awesome. http://forum.xda-developers.com/showthread.php?t=2520550 I flashed this to the STOCK spot and then wiped the data on the phone once more and rebooted! DO NOT FLASH THE FIRMWARE AGAIN from the NC2 rom.
Now I again reinstalled Safestrap 3.72 and am currently running Hyperdrive KK RLS8 w/ Safestrap 3.72 successfully!

[SM-P905] Upgrade to Rooted Official Lollipop 5.0.2 - can be downgraded

** DISCLAIMER: I AM NOT A DEVELOPER. I DO THIS AS A HOBBY AND SHARE MY FINDINGS IN CASE SOMEONE ELSE FINDS THEM USEFUL. **
** THIS WORKED ON MY DEVICE BUT IT MAY NOT WORK ON YOURS. APPLY AT YOUR OWN RISK **​
This has been tested with the Italian firmware released on 4/30/2015, PDA: P905XXUABOD7, CSC: P905ITVABOD7 (of course the language can be set to English after installation). This method should however work for other Lollipop releases as they become available in your region. This method does not trip the knox flag.
Requirements
1- Rooted KitKat (the easiest way to get root is to flash a ROM dated before June 2014 and root it with Towelroot).
2- FlashFire app v 0.17 or higher: The only way to get it is by following the instructions at: http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
Procedure
1- Make a back up of all your files.
2- Download your Lollipop ROM from Sammobile and unzip the .zip file to get the tar.md5 file. Copy the tar.md5 file to your sdcard.
3- Run FlashFire. Tap the +, Flash Firmware Package, and select the tar.md5 file. It will scan the file and opens a menu of option to choose.
4- Choose: Boot, Recovery, System, Cache, Preloaded/Hidden.
Also choose Highly recommended but optional: Modem Firmware (modem.bin) and Firmware (NON-HLOS). If you select these you should answer NO when it asks you "You are flashing both normal and ..."
The rest should be unchecked. Now tap the check mark at the top right corner of the dialog box.
5- When that is done, FlashFire adds two items to the list of actions: Process Cache and EverRoot. Open process cache and uncheck all the items. Open EverRoot and select Inject SuperSU and unckeck the other options.
6- Tap the + again and choose Wipe. Select System, Dalvik, and Cache. I highly recommend that you check 3rd party apps too, which will erase your existing apps and settings but it will give you a clean install. Do not select Internal storage.
7- Tap and hold to move the boxes containing the actions to get them in this order: Wipe, Flash Firmware Package, followed by the rest.
8- Tap the Reboot box and select Reboot to Recovery.
9- Hit the FLASH sign at the bottom of the page and hit OK. THE SCREEN WILL GO COMPLETELY BLANK DURING THE FLASHING OPERATION. Do not freak out. This is a bug in the tool and will hopefully be fixed in a future version. After 5-10 minutes your tablet reboots. If it takes longer than 20 minutes something is wrong.
10- During the first reboot it may take 5-10 minutes before you get the initial setup dialog. (If it takes longer than 20 minutes something is wrong.) Complete it and you will be on rooted Lollipop.
TiP: Settings -> General -> Security -> Security Policy Updates -> Uncheck Automatic Updates, and also Settings -> General -> About Device -> Software Updates -> Uncheck Auto Updates
Troubleshooting
If after the upgrade you suspect something does not work, install Flashfire on your rooted lollipop and start from step 4 again.
If you experience random reboots freeze or otherwise disable knox and update programs.
Downgrade
If you are not happy with the results, or something goes wrong, download a KitKat firmware from Sammobile and flash it in ODIN. Make sure to clean cache and data in recovery.

najoor said:
** DISCLAIMER: I AM NOT A DEVELOPER. I DO THIS AS A HOBBY AND SHARE MY FINDINGS IN CASE SOMEONE ELSE FINDS THEM USEFUL. **
** THIS WORKED ON MY DEVICE BUT IT MAY NOT WORK ON YOURS. APPLY AT YOUR OWN RISK **​
This has been tested with the Italian firmware released on 4/30/2015, PDA: P905XXUABOD7, CSC: P905ITVABOD7. This method should however work for other Lollipop releases as they become available in your region. This method does not trip the knox flag.
Requirements
1- Rooted KitKat (the easiest way to get root is to flash a ROM dated before July 2014 and root it with Towelroot).
2- FlashFire app v 0.16 or higher: The only way to get it is by following the instructions at: http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
3- SuperSU update zip version 2.46 or higher.
Procedure
1- Make a back up of all your files
2- Download your Lollipop ROM from Sammobile, unzip it and copy the tar.md5 file to your sdcard
3- Download SuperSU update zip and copy it to the sdcard.
4- Run FlashFire.
5- Tap the +, Flash Firmware Package, and select the tar.md5 file. It will scan the file and opens a menu of option to choose.
6- Choose: Boot, Recovery, System, Cache, Preloaded/Hidden.
Optional: Modem Firmware (modem.bin) and Firmware (NON-HLOS). If you select these you should answer NO when it asks you "You are flashing both normal and ..."
The rest should be unchecked. Now tap the check mark at the top right corner of the dialog box.
7- When that is done, FlashFire adds two items to the list of actions: Process Cache and EverRoot. Open each one and uncheck all the items under both
8- Tap the + again and choose Wipe. Select System, Dalvik, and Cache. I highly recommend that you check 3rd party apps too, which will erase your existing apps and settings but it will give you a clean install. Do not select Internal storage unless you want your internal SD card erased too.
9- Tap the + again, Flash Zip or OTA, and select the SuperSU update Zip. Leave Automount unchecked
10- Tap and hold to move the boxes containing the actions to get them in this order: Wipe, Flash Firmware Package, Flash Zip or OTA, followed by the rest.
11- Hit the FLASH sign at the bottom of the page and hit OK. THE SCREEN WILL GO COMPLETELY BLANK DURING THE FLASHING OPERATION. Do not freak out. This is a bug in the tool and will hopefully be fixed in a future version. After 5-10 minutes your tablet reboots. If it takes longer than 20 minutes something is wrong.
12- During the first reboot it may take 5-10 minutes before you get the initial setup dialog. (If it takes longer than 20 minutes something is wrong.) Complete it and you will be on rooted Lollipop.
TiP: Settings -> General -> Security -> Security Policy Updates -> Uncheck Automatic Updates, and also Settings -> General -> About Device -> Software Updates -> Uncheck Auto Updates
Downgrade
If you are not happy with the results, or something goes wrong, download a KitKat firmware from Sammobile and flash it in ODIN. Make sure to clean cache and data in recovery.
Click to expand...
Click to collapse
Thank you very much for this!
I wonder if could you please attach the odin files as you did with 4.4.2 thread.
Thanks in advance.

I guess Xposed will not work on our lovely Touchwizzed-Lolipop device?
Please let me know if anyone tried it.

perce_ption said:
I guess Xposed will not work on our lovely Touchwizzed-Lolipop device?
Please let me know if anyone tried it.
Click to expand...
Click to collapse
Don't need to try.... Straight from the developer...
https://github.com/rovo89/XposedTools/issues/3#issuecomment-96386801

Screenshots
Please can u post screenshots for the updated apps or launcher!!
I have sm-p901

Thanks. Follow the instructions exactly and everything works.
PS: Set from Singapore.

works great, thanks
(sm-p905) italy.

Impossible
can't even register at the website to download the Rom. Its impossible to solve the puzzle- even though Ke done it 22 times!!!website to d
ownload the Rom. Its impossible to solve the puzzle- even though Ke done it 22 times!!! HELP!

AdjoX said:
can't even register at the website to download the Rom. Its impossible to solve the puzzle- even though Ke done it 22 times!!!website to d
ownload the Rom. Its impossible to solve the puzzle- even though Ke done it 22 times!!! HELP!
Click to expand...
Click to collapse
did you try to register from a mobile device? If so try to register from a PC or a laptop and download the files there.

Thanks for the instructions.
Does anyone have a flashable bootloader package? From experience Lollipop is unstable with the old bootloader....at least it was on the N9005.
EDIT: Have successfully upgraded. Initially left the Apps and data but the tablet got stock on "checking connection" during the initial setup. A fectory reset did dix that but also cleared the internal Sd card

Well, I did two simple steps: upgraded up to 5.0.2 and flashed http://forum.xda-developers.com/showpost.php?p=50498424&postcount=235 CF-Root via Odin. Works fine.

sudo.sh said:
Well, I did two simple steps: upgraded up to 5.0.2 and flashed http://forum.xda-developers.com/showpost.php?p=50498424&postcount=235 CF-Root via Odin. Works fine.
Click to expand...
Click to collapse
Pleasee note that flashing CF autoroot trips your knox flag irreversibly, if that is important for you.

najoor said:
Pleasee note that flashing CF autoroot trips your knox flag irreversibly, if that is important for you.
Click to expand...
Click to collapse
at the loading?

sudo.sh said:
at the loading?
Click to expand...
Click to collapse
The knox is knocked at the first reboot after the Odin flash. For you it shouldn't matter because you have already done it. Not a big deal. People have differing opinions about the consequences of tripping knox. I normally try to keep it unchanged on my devices but I don't have a personal opinion on that.

Yes, the Knox is knocked, and it doesn't matter for me.

sudo.sh said:
Yes, the Knox is knocked, and it doesn't matter for me.
Click to expand...
Click to collapse
Will this work for the 905V, Verizon with locked bootloader?
Sent from my SM-P905V using Tapatalk

Works fine, but I had a huge battery consumption until I flashed with Odin the Bootloader, the Kernel and the modem.

aviator1 said:
Works fine, but I had a huge battery consumption until I flashed with Odin the Bootloader, the Kernel and the modem.
Click to expand...
Click to collapse
You don't need to flash bootloader, just make sure you flash the modem when you use flashfire.

I did flash the modem in flashfire, then observed huge battery consumption. After that I reflashed the modem plus flashed the kernel the kernel, but the battery went from 80 to 50% in less than two hours using it not more than 1/2 hour, then I flashed the bootloader and consumption was back to normal (approximately 1% consumption per hour in idle mode). I know that the bootloader shouldn't affect the battery consumption, but that's what happened to me.

I seem to be having an issue with the security. After following instructions, upon boot I get an error "System software not authorized by Verizon Wireless has been found on your phone."
Anyone have any ideas? I'm gonna try getting on a Windows computer and using Odin (I'm on linux)
Edit: I'm back on stock, seems this is blocked by the Verizon bootloader. It's a shame they feel the need to cripple such a good piece of hardware.
Thanks

[Q] Booting 5.0 Alliance Rom

I tried to root my brother's S5 which was on 5.0 to begin with. Here is what I did:
Odined back to full stock 4.4.2 (NCIG or whatever), booted no problem. Then I rooted, busyboxed, installed safestrap, all worked. Booted into recovery, set up a rom slot, and flashed Alliance 5.0. Then I booted straight into download mode and flashed the OA8 Kernel and firmware via odin and booted the phone back up. It only got to the first boot screen and did the noise thing but didn't continue to the red verizon logo or anything further.
Did I miss a vital step or was I just too impatient waiting for it to boot (waited ~5min)? I figured 5 minutes would be long enough to pass the first boot screen. I put him back onto 4.4.2 rooted for the meantime but need help getting him back to 5.0.
Thanks!

Two problems I can think of. If you installed the rom to any slot other than stock I believe it won't boot properly. Also, Alliance is a deodexed rom which takes 15+ minutes on first boot, so you didn't wait anywhere near long enough.

**You can begin the following process from any Build/ROM but you must already have Root Access**
**Required** FlashFire - Play BETA - PREVIEW
1. Join the G+ community using the same Google account as you're using for Play on your phone/tablet Here.
2. Sign up to receive the BETA versions from Play Here.
- Use the link provided after sign-up to download the app.
**Caution!** The following process is only for the G900V Verizon S5 variant. Use on any other device may result in a hardbrick!
***FlashFire v19 Recommended***
Download:
- G900V_OD5_Stock_Rooted_ROM
- G900V_OD5_Stock_Deodexed_ROM
Set your screen timeout to 10mins before beginning!
1. Place the ROM onto your device (use either internal or ext-sdcard).
2. Open the FlashFire app and "Agree" to the Terms and Conditions.
3. Press "(+)" twice to bring up the "Actions" menu.
4. Select "Flash Zip or OTA" and locate and select the ROM. Leave "Auto-mount" unchecked under the "Options" menu and press the checkmark to continue.
5. From the main menu Uncheck all options under "EverRoot" and use default "Reboot" setting.
6. Last, press the lightning bolt then "Ok" to begin the flash .
The screen will turn black then display the contents of your system before beginning the flash. FlashFire will pause for about 1 minute while flashing the "system" partition. Once complete your device will reboot and pause on the Verizon splash screen for 1 - 2 minutes (15 - 20mins for DeOdexed version) before completely rebooting. Done!
Tip: for blazing fast speed turn off animations from Developer Options and reboot!
Known Issues:
- None!
- When reporting an issue please always include your starting firmware, FF version, ROM version flashed, and relevant details. Should the flash fail please review FF's last log for errors and include info in your post.
Optional (Flash using FlashFire's "Flash zip or ota" option):
- G900V_OD5_TetherAddOn
- G900V_OD5_Write_to_SDCard
Notes:
1. The above process will not affect your Knox Warranty Flag.
2. The process will update your Modem, Non-hlos, System, Kernel, Stock Recovery, and Bootloader to OD5.
3. No need to wipe prior to flashing, the ROM will automatically perform a factory data reset.
4. If you do not already have root access (or to unbrick) you must flash the G900VVRU1ANCG_Full_Odin.tar (flash in Odin's PDA slot(AP in Odin v3.09+)), root with Towelroot (this version does not require internet access), then proceed with the above process.
5. To learn more about FlashFire's capabilities on locked bootloader devices see here: http://forum.xda-developers.com/showpost.php?p=60070810&postcount=2
Credits: @Dudash - for the system.img used in the ROM and testing.
Try this
Sent from my SM-G900V using XDA Free mobile app