[How-To] Update to G900V_OC4 - 5.0 and KeepRoot (3/30/2015) - Verizon Galaxy S 5 General

**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!
Download:
- G900V_OC4_Stock_Rooted_ROM
- G900V_OC4_Stock_DeOdexed_ROM
Set your screen timeout setting to 10 mins 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 (10 - 15 mins for DeOdexed version) before completely rebooting. Done!
Tip: for blazing fast speed turn off animations from Developer Options and reboot!
Known Issues:
- None!
Optional - Enable Native Tethering:
- G900V_OC4_TetherAddOn (Flash using FlashFire's "Flash zip or ota" option).
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 OC4.
3. No need to wipe prior to flashing, the ROM will automatically perform a factory data reset. If you prefer not to wipe User Data replace the Updater-Script in the ROM's META-INF/com/google/android folder with the version attached to this post (remove ".txt" extension before placing in folder). Bear in mind that carrying over incompatible User Data from a prior Android version may cause issues.
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:
@ChadH42 - for capturing the ota update.
@Chainfire

What is new in this update? I saw your other thread was closing and I'm confused

xdnax said:
What is new in this update? I saw your other thread was closing and I'm confused
Click to expand...
Click to collapse
Let's just say the initial 5.0 release had a few bugs. Let's hope this release works better.

Thanks. I did your previous update with this method, and it worked great. Can you give the steps that are needed to get to where you need to be to now install this update? I think I know, but I'm not sure. Also, what about apps and settings? It does not seem they are preserved. It looks like the previous write up has been edited and no longer includes these steps. I had no problems with this part. Is it still an option to do that? Thanks for the awesome work!

update
So this will work fine updating if on rooted 0A8?

I would assume we could do a data backup, then restore data after flashing is done

So there's no need to flash a firmware or kernel in Odin after flashing the rom? Are we still going to be on 0A8 baseband? Or should we flash the OC4 kernel?
Sent from my SM-G900V using XDA Free mobile app

killa408shark said:
So there's no need to flash a firmware or kernel in Odin after flashing the rom? Are we still going to be on 0A8 baseband? Or should we flash the OC4 kernel?
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
Correct, all necessary OC4 partitions including the kernel, modem, etc are included in the ROM.

Mr. Boom said:
I would assume we could do a data backup, then restore data after flashing is done
Click to expand...
Click to collapse
Only recommended if your Data backup is from 5.0. Those updating from 4.4 should not restore Data for compatibility reasons.

jake20fc said:
So this will work fine updating if on rooted 0A8?
Click to expand...
Click to collapse
Yes

mkitchin said:
Thanks. I did your previous update with this method, and it worked great. Can you give the steps that are needed to get to where you need to be to now install this update? I think I know, but I'm not sure. Also, what about apps and settings? It does not seem they are preserved. It looks like the previous write up has been edited and no longer includes these steps. I had no problems with this part. Is it still an option to do that? Thanks for the awesome work!
Click to expand...
Click to collapse
See Notes section #3.

awesome @muniz_ri ! was just helping a family member update to the new lollipop and i saw this. gonna do some tinkering with safestrap and try and see if i can see whats breaking it on lollipop.. fingers crossed

muniz_ri said:
Only recommended if your Data backup is from 5.0. Those updating from 4.4 should not restore Data for compatibility reasons.
Click to expand...
Click to collapse
How did it work going 4.4.4 to 5.0?

BeansTown106 said:
awesome @muniz_ri ! was just helping a family member update to the new lollipop and i saw this. gonna do some tinkering with safestrap and try and see if i can see whats breaking it on lollipop.. fingers crossed
Click to expand...
Click to collapse
No worries, good luck with SS.
Also fyi.....there is a guy in the N900V forum that has developed a safestrap replacement called multisystem. He is waiting for 5.0 before releasing and claims it will work on 5.0. If so, it can likely be easily ported to the S5.

Got it. I did see that. I guess it is just that simple. I thought there might be a little more detail needed, but I will give it a shot. Hopefully safestrap comes to lollipop one day to make it a little easier!

mkitchin said:
Got it. I did see that. I guess it is just that simple. I thought there might be a little more detail needed, but I will give it a shot. Hopefully safestrap comes to lollipop one day to make it a little easier!
Click to expand...
Click to collapse
After flashing the ROM you can just reboot, no need to re-flash the OC4 kernel since the new ROM already flashed it.

Does anyone know if the Alarm clock works on silent now? I think they got rid of the interruption settings did they not?

I have run into a problem i can't figure out. When i try to run safestrap it just wont boot into it when i boot from the app. Have tried it many times. Thinking back wasn't safestrap broken when you are on 5.0? I went from kit kat, rooted and did the keep root tutorial to have it in 5.0. Not really sure what to do.

jake20fc said:
I have run into a problem i can't figure out. When i try to run safestrap it just wont boot into it when i boot from the app. Have tried it many times. Thinking back wasn't safestrap broken when you are on 5.0? I went from kit kat, rooted and did the keep root tutorial to have it in 5.0. Not really sure what to do.
Click to expand...
Click to collapse
Safe-strap doesn't work on 5.0. You have to flash G900V_NK2_Stock_Kernel to access it.

ejc1214 said:
Safe-strap doesn't work on 5.0. You have to flash G900V_NK2_Stock_Kernel to access it.
Click to expand...
Click to collapse
Ty. I'm not new to flashing but i was just wondering what the hell i was doing that it wouldn't boot. Appreciate it.

Related

[FIRMWARE] Flash KitKat the EASY Way!!!! or Go back to JellyBean

KitKat the EASY Way!!!!
Or, go back to 4.2.2 JellyBean
If you are going to return your phone back to warranty, I would suggest this method in this thread as it does a COMPLETE wipe of your device and puts it back to 'Factory'. It removes Root Flags so it does not show having been rooted, and removes ALL data.
Disclaimer: This is not MY method, but a method I used. The information and files have been figured out over time by many individuals and it's been combined in this thread.
This thread is to help Noobs AND Veterans to flash their ATT D800 LG G2 to KitKat. This will be very spelled out, and I’ve even included a video (see below), so NO Mistakes. Yes, that means you!
PLEASE refer to the Video Below before asking questions, as too many questions get a little overwhelming.
Warning! Please Read!​
This WILL erase everything on your phone and put it back to FACTORY STATE, so be sure you’ve backed up!
Ok, first thing you need to do is download the version you want. I’ve got KitKat 4.4.2 version D80020c, and I’ve got JellyBean 4.2.2 version D80010o. These are VERY LARGE files, so be patient, although I am able to get as much as 6MB/s download speeds from this server.
BIG THANKS TO bigfau for the KitKat TOT and DLL files!!!​
Download Installer - KitKat 4.4.2 D80020c - This Flashes Stock KitKat, WITHOUT Root, and WITHOUT Recovery. - Use TowelRoot and AutoRec to get Root and Custom Recovery. - Single File LARGE archive. KK MIRROR DOWNLOAD
D80020c Split Archive Download - This is the same archive as above, but split into smaller pieces for easy download.
Download Installer - JellyBean 4.2.2 D80010o - Single File LARGE archive. JB MIRROR DOWNLOAD
D80010o Split Archive Download - This is the same archive as above, but split into smaller pieces for easy download..
Download Installer - JellyBean 4.2.2 D80010d - This is for those who want to install Custom Recovery and not update to KK... - Single File LARGE archive.
Now, for the fun stuff (You may want to print this out for reference and check them off as you go)
Pre-requisites:
1. Be sure your phone is currently running a Compatible based ROM. If not, please flash a Custom Compatible Based ROM onto your phone. (ie: If you have a D800, be sure you have a D800 ROM on it. If you have a D802, be sure you have a D802 based ROM on it.)
2. Be sure you have turned on USB Debugging before starting.
Step #1: Program Installation:
1. Save the installer to your desktop
2. Run the Installer by double clicking
3. Wait a while for everything to extract (It might look like nothing is happening. This can take a few minutes, be patient, it’s HUGE)
4. (On Win7 or Win8, Accept User Account Control)
5. Accept my License
6. Don't Change Anything and click ‘Install’
7. Wait some more… and more… Large files are extracting…
8. When it pops up, click ‘Next’ to install the LG drivers. Even if you’ve already installed them, install again! This is to verify you’ve got the right ones installed.
9. Click ‘OK’ to finish the Driver install
10. Click ‘Next to install the LG Flash Tool
11. Don't Change Anything and click ‘Install’
12. Uncheck ‘Run LGFlashTool 1.8.1.1023 and click ‘Finish’ (If you forget to uncheck this, just close the program when it opens)
13. Click ‘Next’ to start the LGFlashTool Patch. (This makes it so you don’t need to change the date back on your PC)
14. Click ‘Next’ again
15. Click the bullet to ‘Agree to my License’ and then click ‘Next’
16. Don't Change Anything and click ‘Next’
17. Click ‘Start’
18. Click ‘Next’
19. Click ‘Exit’ to finish Patch Installer
20. Congratulations, Program Installations are all DONE!
Step #2: Place Phone into Download Mode:
1. With phone NOT plugged into a USB Cable, Hold the Power button to turn off phone
2. Plug your USB cable into your computer
3. Hold the Volume UP Button on your Phone
4. While Still Holding the Volume UP button, plug in the USB cable to your Phone
5. Continue to hold the Volume UP button until your phone enters Download Mode
6. If this does not work, pull the USB cable and start from #1 of this section
Step #3: Change Com Port to 41
1. With your phone STILL in Download Mode and STILL Plugged into Computer
2. Go into Device Manager
---a. Press and hold your Windows Key (Between CTRL and ALT)
---b. Tap the ‘Pause/Break’ Key (Usually Top Right of Keyboard, might be different on yours)
---c. Click on ‘Device Manager’
3. In the Device List, scroll down to ‘Ports (COM & LPT) and double click to expand
4. Find the ‘LGE AndroidNet USB Serial Port (COM4)’ (Your COM Port Number might be different, that’s OK)
5. Double click to open the port
6. On the Tabs at the top of that screen, click on ‘Port Settings’
7. Click on ‘Advanced…’
8. Click on the Com Port number to drop down the list
9. Scroll down to ‘COM41’ and select it
10. Click ‘OK’ Button to save that
11. Click ‘OK’ Button to close the Com Port Properties
12. Close the Device Manager
13. Close the System Window
14. Go back to the Desktop
15. That’s it, You’ve Changed the Com Port to 41
Step #4: Run LGFlashTool:
1. Double Click the ‘LGFlashTool’ icon on the Desktop (Win7 or Win8 accept ‘User Account Control’)
2. In the ‘Model Config’ window, check the box ‘Select Manual Mode’
3. Next to the DLL space, click the Three Dots ‘…’
4. Select the DLL file named ‘LGD800_.....v160.dll’
---a. For 4.4.2 KitKat, select ‘LGD800_20130811_LGFLASHv160.dll’
---b. For 4.2.2 JellyBean, select ‘LGD800_20130904_LGFLASHv160.dll’
5. Click the ‘Open’ Button
6. Next to the S/W space, click the ‘Remove ALL’ Button
7. Next to the S/W space, click the ‘Add’ Button
8. Select the tot file for the version you are flashing
---a. For 4.4.2 KitKat, select ‘LGD800AT-01-V20c-310-410-FEB-02-2014+0.tot’
---b. For 4.2.2 JellyBean, select ‘LGD800AT-01-V10o-310-410-OCT-19-2013+0.tot’
9. Click the ‘Open’ Button
10. Click ‘OK’ Button to save choices
11. In the LG FlashTool program, click the ‘Yellow Arrow’ pointing to the Right.
12. Wait for the program to verify your DLL and TOT selections (This takes a while)
13. If successful, you will see ‘READY!!’ on ‘Port 1 (COM41)’
14. If you DON’T see ‘READY!!’, you may need to start over
15. If you see ‘READY!!’ unplug your phone from the USB cable and Plug it right back in. DO NOT PRESS ANY BUTTONS ON YOUR PHONE. It should STILL be in Download Mode.
16. The LG FlashTool progam will now start flashing your phone!!
17. At around 80%, the program will restart your phone.
18. It takes a while for the phone to restart, but it will boot to Android. Wait for the flash program to finish and it will turn your phone back OFF. And give you a ‘SUCCESS”
19. Close FlashTool
IF for some reason, the LG FlashTool does not finish 100%, and you get a ‘Fail’, as long as your phone has now rebooted into Android, you don’t need to worry about this. Just close the program, and enjoy your Freshly Restored LG G2!
For anyone having issue with the device check not passing due to mismatched device (caused by flashing a Custom ROM with Different device model ID to your D800: ie, D801 to a D800 or vice versa.), try using the attached dll file instead of the device specific one. It has been reported to work for many... You will need to extract the zip file to get the dll.
good stuff bud!
Thanks SuperSport. I have added a link to your thread in my guide.
Can we get an installer for 80100d . It will be easier for newbies
Just so you know, in step #4 you have 4.4.2 twice But great job man! You might want to use the 10d 4.2 as that is the one that recoveries work best with. Just a thought.
epapsiou said:
Thanks SuperSport. I have added a link to your thread in my guide.
Can we get an installer for 80100d . It will be easier for newbies
Click to expand...
Click to collapse
What variant is the 801? Sprint, Verizon? Sorry, on my phone at the moement.
EDIT: Doh! Now I know what you meant... Sorry...
BAM1789 said:
Just so you know, in step #4 you have 4.4.2 twice But great job man! You might want to use the 10d 4.2 as that is the one that recoveries work best with. Just a thought.
Click to expand...
Click to collapse
Thank you for that. FIXED.
EDIT: Why is 10d easier? Is it due to the script in ioroot22? I keep flashing 10o, then use ioroot22, then use FreeGee to install TWRP. Easy Peasy. BUT, I might have modified ioroot22 script for that, I don't remember ATM.
You my friend are a very nice person lol. Taking the time to put this together.
Sent from my LG-D800 using Tapatalk
SuperSport said:
EDIT: Why is 10d easier? Is it due to the script in ioroot22? I keep flashing 10o, then use ioroot22, then use FreeGee to install TWRP. Easy Peasy. BUT, I might have modified ioroot22 script for that, I don't remember ATM.
Click to expand...
Click to collapse
I haven't had my G2 very long so I haven't been able to test myself, but just looking around the forum seems the 10o firmware causes boot issues with some custom ROMs. I could be wrong though. Maybe the problem doesn't exist anymore and I'm reading old info.
SuperSport said:
What variant is the 801? Sprint, Verizon? Sorry, on my phone at the moement.
EDIT: Doh! Now I know what you meant... Sorry...
Thank you for that. FIXED.
EDIT: Why is 10d easier? Is it due to the script in ioroot22? I keep flashing 10o, then use ioroot22, then use FreeGee to install TWRP. Easy Peasy. BUT, I might have modified ioroot22 script for that, I don't remember ATM.
Click to expand...
Click to collapse
Ioroot and then freegee TWRP route works on 80100o. Unfortunately, flashing ROMs (stock based and flex based especially) causes issues. I do not think anyone figured out the reason but going to 80100d solves the issue.
epapsiou said:
Ioroot and then freegee TWRP route works on 80100o. Unfortunately, flashing ROMs (stock based and flex based especially) causes issues. I do not think anyone figured out the reason but going to 80100d solves the issue.
Click to expand...
Click to collapse
So I understand... If you flash Stock 10o, then Root and Flash Custom Recovery, you have issues flashing other ROMs? But if you Flash back to Stock 10d, you do not have issues flashing Custom ROMs?
Also, FYI: ioroot23 was just released... I don't know if that will make a difference. It has 10o support built in.
SuperSport bro u made my life so much easier. Thank u for your hard work bro.
Sent from my LG-D800 using Tapatalk
SuperSport said:
So I understand... If you flash Stock 10o, then Root and Flash Custom Recovery, you have issues flashing other ROMs? But if you Flash back to Stock 10d, you do not have issues flashing Custom ROMs?
Also, FYI: ioroot23 was just released... I don't know if that will make a difference. It has 10o support built in.
Click to expand...
Click to collapse
Yes that is correct.
I am not sure if rooting was an issue. It was the recovery that seemed to be the issue. Not sure though and I guess since 10d worked not many people bothered to investigate further.
epapsiou said:
Yes that is correct.
I am not sure if rooting was an issue. It was the recovery that seemed to be the issue. Not sure though and I guess since 10d worked not many people bothered to investigate further.
Click to expand...
Click to collapse
I'm having the same issue flashing any stock based rom on 800o. It throws me in a bootloop. How would I get the 800d fw?
Sent from my LG-D800 using Tapatalk
SuperSport said:
So I understand... If you flash Stock 10o, then Root and Flash Custom Recovery, you have issues flashing other ROMs? But if you Flash back to Stock 10d, you do not have issues flashing Custom ROMs?
Also, FYI: ioroot23 was just released... I don't know if that will make a difference. It has 10o support built in.
Click to expand...
Click to collapse
i can confirm this is true. i lg flash tool'ed back to 10o, while i could get root i couldnt get twrp or philz recovery to work. when i went back to 10d with lg flash tool, i could get root and recovery to work. i even loki'd a couple recoveries and the recoveries wouldnt only give me a black screen when i tried to enter them on 10o. and i used ioroot23 to do all of this with.
Is this tool safe to use if the phone shows rooted after you go into download mode? Although I swore I unrooted the phone.
Took a chance and did this anyway and all is good. Upgraded successfully! Thank you so much for providing this tool! It was such a pain searching for a serial for lgflashtool. Will be donating asap for the help. Thank you thank you thank you. Directions were perfect as well and very easy to follow.
Downloads not working for me... 68% complete is furthest I've gotten. Tried seven or 8 times.
Sent from my LG-D800 using xda app-developers app
Success! after using this I called AT&T and they pushed me another small update then after that the kitkta update. I know there's no recovery available yet right?
Sorry Everyone, I've been out of town and only on my phone, but mostly busy with family stuff.
freebee269 said:
i can confirm this is true. i lg flash tool'ed back to 10o, while i could get root i couldnt get twrp or philz recovery to work. when i went back to 10d with lg flash tool, i could get root and recovery to work. i even loki'd a couple recoveries and the recoveries wouldnt only give me a black screen when i tried to enter them on 10o. and i used ioroot23 to do all of this with.
Click to expand...
Click to collapse
Thank you for the clear info. I will build a 10d version. Hopefully tomorrow.
strose09 said:
Is this tool safe to use if the phone shows rooted after you go into download mode? Although I swore I unrooted the phone.
Took a chance and did this anyway and all is good. Upgraded successfully! Thank you so much for providing this tool! It was such a pain searching for a serial for lgflashtool. Will be donating asap for the help. Thank you thank you thank you. Directions were perfect as well and very easy to follow.
Click to expand...
Click to collapse
I'm sorry, I have been away from home. Just read this. Yes, you are fine if your phone is rooted. This Flash will remove Root. As mentioned in the First post, there is currently no way to root KitKat, (Unless I've missed something since last night). So root, then go to KitKat.
mjgspr95 said:
Downloads not working for me... 68% complete is furthest I've gotten. Tried seven or 8 times.
Sent from my LG-D800 using xda app-developers app
Click to expand...
Click to collapse
Some people have issues with Internet Explorer on Mega Website. You might install Chrome or Firefox and try it that way, or use a Download Manager of your choice.
humblehyper said:
Success! after using this I called AT&T and they pushed me another small update then after that the kitkta update. I know there's no recovery available yet right?
Click to expand...
Click to collapse
That is Correct, no Custom Recovery. Not unless something has appeared since last night when I last went through the forums.
Usefull guide thanks
but i think there is not a difference between those Flash DLL i had 20130904 and just freshy flashed KitKat
also if anyone cares about a LG Flash tools "PASS" then while it stops on 80-94% and boot into OS itself, do a Factory Reset of phone and it will check a Factory Flag (it sets to 5) and gives message a PASS
Doesn't sound like an easy way!!!:what:
Sent from my Nexus S using Tapatalk
pcoruganti said:
Doesn't sound like an easy way!!!:what:
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Oh but indeed it is.
Sent from my LG-D800 using Tapatalk

[4.4.4][ktu84p]STOCK Rooted with busybox for tilapia[6/19/14]

It is cooked from the Google stock image for tilpia and is NOT deodexed
This is the first time i am posting a ROM on XDA.
Been cooking ROM's for a while for my old Samsung devices.
The whole reason for this thread is to have a flashable zip for any Nexus 7(2012) 3g user who wishes to stay stock.
I have tested it on my Nexus 7, if anyone has any issues do let me and please bear with me as im not a developer and just sharing what i personally use.
Will try and help with what ever i can.​
************** For some Reason the boot logo does not show up, dont worry, wait for sometime, the ROM will boot up***********
Note:
1. Works with multirom.
2. Odexed for my personal use, if anyone wishes to de-odex it, do let me know.
3. This includes the stock kernel. I also tested the latest stable mkernel which is for 4.4.2 and works fine.(works with the new kitkat 4.4.4 too)
Screenshot attached
Downloads:
4.4.4:
tilapia.v2
Mirror
Radio for 4.4.4
md5 for Radio: 64920d406852d92b478c3ab17383ecce
4.4.3:
tilapia.v1
md5 : 5c4d3b47274000cf6d5326d14ab7cc81
Click to expand...
Click to collapse
Installation:
1. Reboot to recovery
2. Do a factory reset.
3. Go to advanced wipe settings and select system, dalvik and cache and format them.
4. Flash Rom
First boot takes time, wait patiently. There wont be any boot animation, so wait on that black screen for sometime
Profit :good:
Click to expand...
Click to collapse
credits: @JustArchi
Let me know guys if there is any issue. Im little busy this weekend, will take little time to add things like Advanced reboot menu, battery % and debloat.
phanitej said:
Let me know guys if there is any issue. Im little busy this weekend, will take little time to add things like Advanced reboot menu, battery % and debloat.
Click to expand...
Click to collapse
Hi, Can I flash this over 4.4 [KRT16O]? Please advise. Thanks.
gwong76 said:
Hi, Can I flash this over 4.4 [KRT16O]? Please advise. Thanks.
Click to expand...
Click to collapse
Update your bootloader and radio first. And clean flash is recommended though there are not much of changes from 4.4.2 but as you mentioned you are using 4.4 clean wipe and installing is preferred.
thank you very much! stock rocks! :good::good:
PS: root & bbox?
Thanks alot
Hi!
First of all - thanks for your clean/xposed ROM.
I only have one question. Would it still be possible to send SMS from my Tilapia-tablet (Nexus 7-2012/3G) after flashing your ROM?
BTW : @RomerGG - The threads' header should already have answered your question...
Regards,
Roy
roygaard said:
Hi!
First of all - thanks for your clean/xposed ROM.
I only have one question. Would it still be possible to send SMS from my Tilapia-tablet (Nexus 7-2012/3G) after flashing your ROM?
BTW : @RomerGG - The threads' header should already have answered your question...
Regards,
Roy
Click to expand...
Click to collapse
Haven't tried that. Unfortunately i have a pure data plan, so my provider restricts sms by default. And i cant take out the sim and replace as i was once trying to break open my sim slot and take out the sim, during that crazy struggle i guess i broke that sim holder. so once the sim comes out, i have to struggle a lot to get the network back on by replacing it
Edit: dont think hangouts will give the sms sending option by any chance. So try with a third party app and let us know
Thanks for the stock rooted rom. FYI, I had flashed CF SuperSU v1.99r4 and also MKernel a67, looks okay so far. I'm updating the Google apps from Play store now. Once done, I'll be installing TB to restore my apps.
One word of caution to those flashing this rom. Note that there seems to be no bootanimation, so don't be mistaken that the rom is not working. Give it time to boot up. :good:
Edit:
One thing I noticed strange is in TB, System ROM is showing 670MB (8.45 MB free). Before this, I was on 4.4.2 stock rooted, before I manually flashed boot.img and system.img. It was showing same results, but 9.XX MB free. Is this correct? I vaguely remembered that it should be almost 900 plus MB. Can anyone confirm?
phanitej said:
Update your bootloader and radio first. And clean flash is recommended though there are not much of changes from 4.4.2 but as you mentioned you are using 4.4 clean wipe and installing is preferred.
Click to expand...
Click to collapse
Sorry for this stupid question. How can I updated these .img files ?
Thank you for this work!! I had the slimkat, I did a wipe recovery and then I installed. Where is the menu button?
Art is not activated?
apinun_po said:
Sorry for this stupid question. How can I updated these .img files ?
Click to expand...
Click to collapse
To flash them you need to enable USB debugging and then reboot to bootloader. Here use the following fastboot commands.
For Updating bootloader:
fastboot flash bootloader name_of_the_bootloader_file.img
For radio:
fastboot flash radio name_of_the_radio_file.img
If you want a detailed instruction, go here and follow Method 2.
sbarrett said:
Thank you for this work!! I had the slimkat, I did a wipe recovery and then I installed. Where is the menu button?
Art is not activated?
Click to expand...
Click to collapse
It is the same file as the one google pushes for Nexus 7 device. So what ever is present in the original stock image, will be there.
Menu button is only active in apps that give it by default, there is an xposed module which can activate menu button in every app.
For ART, not sure why google misses the option to switch to ART every time on Nexus 7 devices. Will check and see how to add that option.
phanitej said:
To flash them you need to enable USB debugging
Click to expand...
Click to collapse
Thank you very much.
Kitkat 4.4.4 is out and the stock rooted version is tested and :good:uploaded.
One quick question my all friend here. 4.4.4 still dalvik or run as ART
Sent from my GT-I9205 using Tapatalk
yusopa said:
One quick question my all friend here. 4.4.4 still dalvik or run as ART
Sent from my GT-I9205 using Tapatalk
Click to expand...
Click to collapse
It is dalvik. Google does not seem to want including ART for the nexus 7. Read somewhere on google forums that it might be a hardware issue cos of which they are not including it.
flashing aborted
Version tilapia2 flashing aborted, version tilapia 1 ok. Do you know where is the problem? Using the latest version of the recovery v6.0.4.3.
Good work! I maintain BSZKitKat for grouper (ODEX and DEODEX). Awesome job getting right in front of the 4.4.4 update!
---------- Post added at 05:30 PM ---------- Previous post was at 05:29 PM ----------
phanitej said:
It is dalvik. Google does not seem to want including ART for the nexus 7. Read somewhere on google forums that it might be a hardware issue cos of which they are not including it.
Click to expand...
Click to collapse
Correct - we lack sufficient space on the /system partition for the binaries required for switching to ART
Cant' flash this rom, i get an error and the message FAILED.
I'm using TWRP recovery 2.7.
Can we have a flashable zip please?
It is much easier to deal with!
Thanks

[How-To] Enable Native Tethering (I337 4.4.2 - Stock NI1, NB1, & NC1 ROM's Only)

The following files will enable tethering on your I337. Make certain that you use the version applicable to your current build and only use on stock ROM. Use on custom ROM's may cause issues with the ROM. Proceed at your own risk!
Note: This will modify your system causing future ota updates to fail!
Here they are:
I337UCUFNI1_Safestrap_TetherAddOn.zip
(To undo the mod flash the I337_NI1_TetherAddOn_Revert-to-Stock.zip using the same instructions below).
I337UCUFNC1_Safestrap_TetherAddOn.zip
I337UCUFNB1_Safestrap_TetherAddOn.zip
Instructions:
1. Root your device(See Post #2 for rooting options).
2. Install the latest Safestrap.apk.
3. Place the applicable Safestrap_TetherAddOn.zip on ext sdcard.
4. Reboot into Safestrap Recovery and flash the Safestrap_TetherAddOn.zip in Stock Slot (Do Not Wipe Prior to Flashing!)
5. Reboot. Done!
NI1, NC1 & NB1 Rooting Methods
NI1 Users: http://forum.xda-developers.com/galaxy-s4-att/general/how-to-root-i337ucufni1-t2881298
NC1 Users: Use Towelroot.apk
NB1 Users: Flash the NC1_Stock_Kernel in PDA Slot in Odin(AP in Odin v3.09+), then use Towelroot.apk to root your device. (Optional: flash the NB1_Stock_Kernel once rooted).
Alternatively, flash the I337UCUFNB1_4.4_Rootable_Stock_Odin_tar to get back to factory stock NB1 then use Towelroot.apk to root your device.
reserved
thanks. been waiting for a method to install safestrap and to get hotspot. gonna test it out and see how long before AT&T or Net10 lock me out or send me a notice.
After I flashed zip on Golden Eye Rom I get stuck on Samsung boot screen. I did not wipe anything before flashing
Is this only for stock rooted nc1/nb1 or can this applied on top of a custom rom like ShoStock?
smokeythebear3 said:
Is this only for stock rooted nc1/nb1 or can this applied on top of a custom rom like ShoStock?
Click to expand...
Click to collapse
Most custom roms already offer tethering built in. Also they may already have a modified framework-res.apk(which these files replace) and may cause issues. So to answer your question I recommend only using this hack on stock.
I have an att i337 stock mf3, rooted using towel and su access. unlocked sim using tmo sim, which file should i download? also im on 4.2.2.. or if i update to atleast 4.3 with the newer modem will that fix this problem?
muniz_ri said:
Most custom roms already offer tethering built in. Also they may already have a modified framework-res.apk(which these files replace) and may cause issues. So to answer your question I recommend only using this hack on stock.
Click to expand...
Click to collapse
Cuda70383 said:
I have an att i337 stock mf3, rooted using towel and su access. unlocked sim using tmo sim, which file should i download? also im on 4.2.2.. or if i update to atleast 4.3 with the newer modem will that fix this problem?
Click to expand...
Click to collapse
I'm surprised that you are one of the few that still has att i337 mf3 phone. if so, stay on it, root it and disable the update. else, you'll lost pretty much everything unless something else happen. however, the only thing i can recommend is that you follow another guide that can do it or use foxfi and the paid key.
Holy crap dude! Super cool! If only I didn't have a faulty motherboard everything would be almost perfect, only thing I I'm missing is wifi calling but whatever. I'm gonna have to live without it cause the tmobile roms just don't work for me. Thanks so much man! Hey you think tmobile detects this? I have 3gb free a month.
I337UCUFNI1_Safestrap_TetherAddOn.zip
@guut13, @kbraun
I337UCUFNI1_Safestrap_TetherAddOn.zip added to OP.
Reading up on Safestrap now... i didn't think about it until now if I needed it, apparently I've been running without Recovery since I rooted 4.2.2, amateur move!!
I assume this wont wipe anything, just allows me to setup a recovery and flash the tether add on? correct
Pardon the seemingly easy question ( that I haven't found answers to yet)
[alot of updated reading lately since I updated from MF3 4.2.2 and my age old root method]
muniz_ri said:
@guut13, @kbraun
Thanks for the update.
I337UCUFNI1_Safestrap_TetherAddOn.zip added to OP.
Click to expand...
Click to collapse
kbraun said:
Reading up on Safestrap now... i didn't think about it until now if I needed it, apparently I've been running without Recovery since I rooted 4.2.2, amateur move!!
I assume this wont wipe anything, just allows me to setup a recovery and flash the tether add on? correct
Pardon the seemingly easy question ( that I haven't found answers to yet)
[alot of updated reading lately since I updated from MF3 4.2.2 and my age old root method]
Click to expand...
Click to collapse
Correct. Installing safestrap will not wipe anything.
Awesome, installed without issues.
The connection does appear to be quite a bit slower than using the previous theringprovision.apk with 4.2.2.
Would flashing a different modem help this?
kbraun said:
Awesome, installed without issues.
The connection does appear to be quite a bit slower than using the previous theringprovision.apk with 4.2.2.
Would flashing a different modem help this?
Click to expand...
Click to collapse
I don't believe a new modem will help. And I only briefly tested so other users should chime in as to whether they are also experiencing a slow connection.
kbraun said:
Awesome, installed without issues.
The connection does appear to be quite a bit slower than using the previous theringprovision.apk with 4.2.2.
Would flashing a different modem help this?
Click to expand...
Click to collapse
Can you try this version and see if the speed is better? I believe that I made a mistake on the first one: https://www.androidfilehost.com/?fid=23622183712475370
Downloading now...
Is it just as simple as flashing over the previous one, or do I have any maintenance to do first?
kbraun said:
Downloading now...
Is it just as simple as flashing over the previous one, or do I have any maintenance to do first?
Click to expand...
Click to collapse
Nope just flash over previous version.
Flashing it now, I'll get you an update in the morning.
Edit: Seems quite a bit faster after flashing the new file.
I wish I had done a speed test first but the results below are from my second install
36.64Mb down 12.95 up.
Once I rebooted I got the message "Safestrap disabled"
is that ok? I noticed the security policy in the 4.4.2 update with Samsung seems to like the ban hammer with alot of rooted stuff.
kbraun said:
Flashing it now, I'll get you an update in the morning.
Edit: Seems quite a bit faster after flashing the new file.
I wish I had done a speed test first but the results below are from my second install
36.64Mb down 12.95 up.
Once I rebooted I got the message "Safestrap disabled"
is that ok? I noticed the security policy in the 4.4.2 update with Samsung seems to like the ban hammer with alot of rooted stuff.
Click to expand...
Click to collapse
I don't know what kind of LTE speeds you normally get in your location but those speeds that you posted are more than decent. And I wouldn't worry about the safestrap disabled message, that's normal. I definitely made a mistake when compiling the first version of the tether add on but this latest version is definitely correct enjoy.

SM-G360V general info, root on latest firmware, xposed framework, viper4android*

I've taken note of the severely limited amount of organized information available for the Verizon variant of the core prime, (see the amalgamation of posts in the main sm-g360v post...) and I'll attempt to provide what information I do have. Currently no recoveries or custom roms have been made publicly available, to my knowledge. This is a Verizon device after all, don't hold much hope towards unlocking the bootloader of this one. Root on latest firmware, setup for xposed framework, and viper4android setup detailed below in respective order.
Root on latest firmware
*Skip to step 7 if already rooted with supersu, data partition not overwritten to my knowledge, proceed with cation
Backup all data before proceeding. Acknowledge these steps will delete all content of your device. Proceeding with the following steps gives the implied understanding I am not responsible for any data on your device. You are responsible for your own data.
1. Setup Odin and d/l the lollipop stock rom here
2. Backup your data then extract the tar.md5 from the rar archive from above then flash it with odin
3. Setup your accounts with the setup wizard when finished if you'd like, then grab the latest version of kingroot. Either android or pc versions work. May need to attempt multiple times.
4. Once rooted with latest kingroot, (5.0.3 at the time of writing) open kingroot, open the main settings from the menu on the top right, press 'Uninstall Kingroot' press continue, ensure 'leave root backup' is enabled in the next dialog, then wait for uninstall
5. Find a kingroot 4.5 apk and install, disable automatic updates in kingroot main settings, then reroot
6. Using either super sume, or a script replace kinguser with supersu
7. Install flashfire, should work properly if using supersu
8. Go here and d/l latest firmware, move tar.md5 file to device, may need external sd due to little internal storage
9. In flashfire, press the addition symbol, select 'flash firmware package,' locate updated tar.md5, select 'modem firmware' and 'Firmware' in addition to pre-selected partitions, then select the check, when prompted, do not split flashing process. Ensure EverRoot is set to inject SuperSU, then flash, wait patiently for device to update.
When finished, check SuperSU for root, if prompted to manually install, flash first stock and try again
Xposed Framework
1. Get the appropriate zip (ARM for sm-g360v, do not use the ARM64) from here, no issues apparent between versions, latest will most likely work (87.1 at the time of writing, no issues seem thus far)
2. Flash as zip with Flashfire, (See above for root) do not mount /system with flashfire, installer fails.
3. Install this Xposed Framework app when reboot finished (should rebuild system apps)
4. Finished
Viper4Android
1. Get V4A apk, do not install drivers yet
2. Install busybox
3. Get this and this, flash both with flashfire
4. Disable/delete SoudAlive to prevent conflicts
5. Install driver/reboot
6. Finished *I personally installed the 2.5 version, though the above method did work with a little bit of toying with the above
I'm assuming that the Odin tar file is an older firmware version for the device?
Jrhotrod said:
I'm assuming that the Odin tar file is an older firmware version for the device?
Click to expand...
Click to collapse
The first tar is lollipop with a security patch from 2015 for kingroot, the second tar that gets flashed through flashfire can be any of the three available, I believe the 2017 build being latest
WARNING:
DO NOT, I repeat DO NOT flash the updated tar.md5!! I flashed it to my device and I lost all calling and texting functionality, PLUS a very outdated ROM.
Jrhotrod said:
WARNING:
DO NOT, I repeat DO NOT flash the updated tar.md5!! I flashed it to my device and I lost all calling and texting functionality, PLUS a very outdated ROM.
Click to expand...
Click to collapse
Use the latest build, the 2017 build is latest, update your modem partitions when you update. Following the steps PROPERLY and using the proper update package will result in a functional device. Complain to Verizon about the outdated nature of the firmware available, and to yourself about your own mistakes, I have used this procedure for my own device and have not had a single issue.
LeafyDeerVoid said:
Use the latest build, the 2017 build is latest, update your modem partitions when you update. Following the steps PROPERLY and using the proper update package will result in a functional device. Complain to Verizon about the outdated nature of the firmware available, and to yourself about your own mistakes, I have used this procedure for my own device and have not had a single issue.
Click to expand...
Click to collapse
I used the 30.10.2016 firmware (G360VVRU3CPJ1) and that's what gave me the issues. Now that I actually observe, I can see a 2017 firmware that I was actually using before I went back and rooted... I will test it soon.
How long should the final update take? I'm up to 30 mins now on the red Verizon screen (blue light strobing).
Chadtheguru said:
How long should the final update take? I'm up to 30 mins now on the red Verizon screen (blue light strobing).
Click to expand...
Click to collapse
Final update meaning what? An update package flashed via FlashFire? Or something else?
Step 9 in the op root process. I did everything up to that point, downloaded latest update, followed the flashfire steps and got 2 hours of the red Verizon screen. Any ideas?
I'm starting over. I screwed up something else anyhow trying to utilize the sd card for apps.
Okay, I started over from the beginning. I just can't get Flashfire to flash the updated firmware. It sticks on the red "Verizon" screen. I've let it sit for 3 hours and it is genuinely stuck. Help!
Chadtheguru said:
I'm starting over. I screwed up something else anyhow trying to utilize the sd card for apps.
Click to expand...
Click to collapse
I never attempted to update my software. Too risky. Stick with the G360VVRU3BOK2 baseband, there is virtually no difference between that and the new 2017 firmware.
Yeah, I've about come to the same conclusion. The only thing I don't like is the nagging OTA Update Notification. I've tried all these and I'm still getting the notify.
http://www.droidviews.com/disable-ota-notifications-android-devices/
Chadtheguru said:
Yeah, I've about come to the same conclusion. The only thing I don't like is the nagging OTA Update Notification. I've tried all these and I'm still getting the notify.
http://www.droidviews.com/disable-ota-notifications-android-devices/
Click to expand...
Click to collapse
Download the device control app from the Play Store and disable the Verizon "Software updates" app
Hah! That did it. Thanks!
Chadtheguru said:
Hah! That did it. Thanks!
Click to expand...
Click to collapse
Thanks for leaving a thanks :good:
---------- Post added at 10:43 PM ---------- Previous post was at 10:39 PM ----------
Jrhotrod said:
Thanks for leaving a thanks :good:
Click to expand...
Click to collapse
For future reference, OTAs are stored in /cache. If you feel like re-enabling the update app, you can let the update download and see if you can flash it with FlashFire. Never tried it myself, but FlashFire does come with an OTA update flasher that attempts to sustain root.
I almost tried that but I couldn't catch it with the OTA downloaded. I may fiddle with it later. Just glad to be rooted for now. Thanks again!
So I've done everything right, and all I've been wanting to install is Xposed. But I've done everything correct up to this point. But I put the framework zip into Flashfire, everything goes fine, until I'm at the Verizon red screen. It just hangs there for hours. Any suggestions?
Sent from my SM-G360V using Tapatalk
iiBootMii said:
So I've done everything right, and all I've been wanting to install is Xposed. But I've done everything correct up to this point. But I put the framework zip into Flashfire, everything goes fine, until I'm at the Verizon red screen. It just hangs there for hours. Any suggestions?
Click to expand...
Click to collapse
Better make sure you have the custom Wanam build.
Download link: https://www.androidfilehost.com/?w=files&flid=37508
Jrhotrod said:
Better make sure you have the custom Wanam build.
Download link: https://www.androidfilehost.com/?w=files&flid=37508
Click to expand...
Click to collapse
I'm pretty sure I'm using the right one. I followed the link, then went 87.1 > Lollipop > xposed-v87.1-sdk22-arm-custom-build-by-wanam-20161125.zip
Isn't that correct?
Sent from my SM-G360V using Tapatalk

[HOW TO] [GUIDE] - How to completely disable Reactivation Lock on SM-G900V

This is a guide how to completely disable Reactivation Lock on SM-G900V in simple steps.
Schematically, we will install Android 4.4.2, bypass Samsung Account login, register a new one and then turn Reactivation Lock OFF.
The phone will be clear after this and ready for any suitable firmware.
1. Download this file: kltevzw_NCG_eLLiKat1_0.zip. It's simply a stock-based 4.4.2 ROM for SafeStrap Recovery.
2. Open kltevzw_NCG_eLLiKat1_0.zip with Windows File Explorer (just click it) and remove this file from it: system\app\SamsungSetupWizard.apk (just navigate to this file, highlite it and hit Del button).
Close Windows File Explorer, the file's size should decrease by about 2 MB.
3. Charge the battery to 50% or above.
4. Download Combination ROM COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_2572656_REV00_user_mid_noship_MULTI_CERT.tar
5. Download zip-file with apks, attached to this post.
6. Run Odin (suppose, you have it and are familiar with flashing), point it to COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_2572656_REV00_user_mid_noship_MULTI_CERT.tar.md5 in AP slot, boot the phone to Download mode, connect it with a cable, press Start and wait till the flashing process ends. Press Exit, wait till the phone completes boot.
7. Disconnect the cable from the phone and connect again.
8. Extract apks.zip to the Desktop.
9. Copy everything from apks folder on your Desktop to the phone's memory root.
10. Copy your new modyfied kltevzw_NCG_eLLiKat1_0.zip file to the phone's memory root.
11. Disconnect the cable.
12. Press Menu (dotted button) - My Files - All - RootS5.
13. Apex_Launcher.apk - Settings - Unknown Sourches - Ok - Back - Apex_Launcher.apk - Next - Install - Done.
14. BusyBox.apk - Install - Done.
15. Safestrap_KK.apk - Install - Done.
16. tr_v2.apk - Install - Open - make it rain (you should see "You should have root, no reboot required" message) - Back.
17. Superuser.apk - Install - Open - Continue - Normal - Reboot.
18. After reboot in a pop-up window - Apex Launcher - Always - Ok.
19. Menu (dotted button) - BusyBox Free - Grant - close balloon - Install - close balloon - Back.
20. Safestrap - Grant - Agree - Install Recovery - Reboot to recovery.
21. Swipe to Allow modifications - Wipe - Advanced Wipe - Dalvik/Data/Cache - Swipe to Wipe.
22. Back - Back - Back - Install, install kltevzw_NCG_eLLiKat1_0.zip.
23. Reboot System - Do not install.
24. After reboot (8 mins or so) you should see the phone's home screen.
25. Set up a wireless connection or use your SIM-card and internet connection from your provider.
26. Navigate to Settings - Security, find Reactivation Lock and untick it. The phone will ask you for your existing credentials or to register a new Samsung account. Just do it (the second, I guess ).
27. Login to your new account and you will be able to untick Reactivation Lock.
28. When it unticked, the phone is clear and ready to accept any suitable firmware.
Will be glad to hear about your success
Hi I just bought a galaxy s5 used and found out about reactivation lock afterward, is this method working with a s5 with locked bootloader? with any firmware (mine is in MM QC2)
Thank you for the guide anyway I was about to give out
Current firmware version and bootloader status do not matter in this case.
Just move through the guide and never give up
Thank you very much, I followed the guide and I(ve been able to install AEX without problems ! I owe you one
isisky said:
I followed the guide and I(ve been able to install AEX without problems !
Click to expand...
Click to collapse
Oh, really?
I thought my guide is only for Reactivation Lock disabling.
Anyway, you are welcome
Thank you very much. This was exactly what i was looking for. The instructions were very well written and easy to follow.
rialsi6 said:
Thank you very much. This was exactly what i was looking for. The instructions were very well written and easy to follow.
Click to expand...
Click to collapse
You're welcome.
Glad to hear that it helped.
Thanks a Lot
:good::good::good::good:
Someone give a kiss to this men, jajaja
amazin We appreciate
so i can let me phone do ota update to 6.0 and it will not lock my phone ?
buckeyes#1 said:
so i can let me phone do ota update to 6.0 and it will not lock my phone ?
Click to expand...
Click to collapse
Yes, of course.
This is a complete solution, not a workaround/bypass/etc.
bbsc said:
Yes, of course.
This is a complete solution, not a workaround/bypass/etc.
Click to expand...
Click to collapse
my phone is rooted already , i just basically use my root for being able to load custom apk , so i can still do this from doing this above and then take a ota update to 6.0.1 and still be able to load custom apk's?
buckeyes#1 said:
so i can still do this from doing this above and then take a ota update to 6.0.1 and still be able to load custom apk's?
Click to expand...
Click to collapse
Excuse me, I cannot understand what you are asking about.
Reread the first post please and try to be more specific.
bbsc said:
Excuse me, I cannot understand what you are asking about.
Reread the first post please and try to be more specific.
Click to expand...
Click to collapse
im rooted now on android 5.0 , but some of my apps are not allowing usage because im not on 6.0
so im looking for a way to upgrade to 6.0 and keep my phone rooted ,
there is just so much going on in this forum tends to a lot of confusion sometimes
buckeyes#1 said:
im rooted now on android 5.0 , but some of my apps are not allowing usage because im not on 6.0
so im looking for a way to upgrade to 6.0 and keep my phone rooted ,
there is just so much going on in this forum tends to a lot of confusion sometimes
Click to expand...
Click to collapse
Is your bootloader unlocked? If you have an unlocked bootloader you can upgrade all the way to pie by flashing a custom ROM. There are lots of tutorials around. The catch is not all g900v's can be unlocked. You need to find out if your phone is able to be bootloader unlocked by checking you cid. First two numbers of cid= 15 and you can have root on custom ROM till android pie (9.0). First two numbers of cid= || no root for you on (6.0) Lollipop and you can only uprated to 6.1
This explains it all, with details and instructions. Good luck!
https://forum.xda-developers.com/ve...ired-easier-root-method-t3561529/post71147687
Sent from my kltevzw using XDA Labs
buckeyes#1 said:
im rooted now on android 5.0 , but some of my apps are not allowing usage because im not on 6.0
so im looking for a way to upgrade to 6.0 and keep my phone rooted ,
there is just so much going on in this forum tends to a lot of confusion sometimes
Click to expand...
Click to collapse
This thread is about completely another thing.
As for you qutestion, generally, you cannot "keep" sm-g900v rooted while upgrading from 5.0 to 6.0.
You will have to root it again on 6.0.
The rest is said by swiftbones74 in his post above.
bbsc said:
This thread is about completely another thing.
As for you qutestion, generally, you cannot "keep" sm-g900v rooted while upgrading from 5.0 to 6.0.
You will have to root it again on 6.0.
The rest is said by swiftbones74 in his post above.
Click to expand...
Click to collapse
yes i started with this my cid is 11 , so i just ill follow these steps , im just trying to figure out what i can do with this phone ? can i still load my own apk's with a non-rooted marshmallow?
I was rooting my 900v and did not untick reactivation lock. I went back to stock 6.0.1 but the option to untick reactivation lock was grayed out. Thanks to these crystal clear and simple instructions I had it unticked permanently in around a hour . Thanks a bunch!
Will it work on my G900P? I've tried to get rid of that since I got it but there is not much support for this problem in the sprint variant.
EDIT: IT WORKED!!! The only thing I did different was I flashed the combination rom of my device instead of the one on this post. Also I had to wipe data after kltevzw_NCG_eLLiKat1_0.zip flash because it was crashing a lot and turned the screen black after 30 second. So after I wiped data the process was the same as the post. Thank you so much!!!! I'm running lastest Pie rom now.
I didn't expect to kltevzw_NCG_eLLiKat1_0.zip to work because mine is the Sprint variant but after a data wipe I got no errors, so it may work on similar variants with this problem. Now I'm going to start a thread on the Sprint variant linking to this one.
DanniX01 said:
IT WORKED!!! The only thing I did different was I flashed the combination rom of my device instead of the one on this post. Also I had to wipe data after kltevzw_NCG_eLLiKat1_0.zip flash because it was crashing a lot and turned the screen black after 30 second.
Click to expand...
Click to collapse
Well done.
It worked because the "P" variant bootloader is unlocked, so it was able to boot an alien kernel (from the "V" variant).
If it was locked, you would have to replace the boot.img file inside the kltevzw_NCG_eLLiKat1_0.zip with a native "P" 4.4.2 kernel.
It's important, say, for the "A" variant.
Besides, the alien kernel demanded cache cleaning, that's why you had to wipe data.
And it was the right decision to use a native Combination ROM file.
The rest of the files should work on any SGS5 (Qualcomm-based, at least).
It worked .
Thanks !

Categories

Resources