Sorry I posted this in the wrong area earlier and as you can probably guess I am very new to this. I have looked around on different sites and tried a few things with no success. I have an S4 Galaxy SCH-I545 v.I545VRSGPL1 and I want to upgrade it from it's present status of 5.0.1 to 7.1.2 or better and I have a few questions. 1) Does the phone have to rooted in order to do this and if so what do I use. From what I've read (and I hope I'm wrong) this particular phone from Verizon seems to be a difficult one. 2.) What would be the best performing upgrade for the phones hardware. Thanks to all for their help.
87lwrdr said:
Sorry I posted this in the wrong area earlier and as you can probably guess I am very new to this. I have looked around on different sites and tried a few things with no success. I have an S4 Galaxy SCH-I545 v.I545VRSGPL1 and I want to upgrade it from it's present status of 5.0.1 to 7.1.2 or better and I have a few questions. 1) Does the phone have to rooted in order to do this and if so what do I use. From what I've read (and I hope I'm wrong) this particular phone from Verizon seems to be a difficult one. 2.) What would be the best performing upgrade for the phones hardware. Thanks to all for their help.
Click to expand...
Click to collapse
1) This phone has a locked bootloader and has to remain on Touchwiz. Rooting methods are posted in the General section. You're stuck on Lollipop with this device, however you can flash other ROMs with Flashfire.
2. That would be software. Hardware is things such as the speaker, Home button, or the device itself.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Again, being new to this, what can I actually do to this phone? You say I'm stuck on Lollipop for the OS and Touchwiz for an interface what can I use to increase it's functionality and performance ability? I read where Marshmallow doesn't have as many significant changes from Lollipop as the changes were from KitKat to Lollipop but I always thought having the most current OS would aid you in using programs and security designed for newer OS's, just like with computers. What about security and update issues, will they stop supporting Lollipop leaving vulnerable? Or is that the idea, forcing you into buying a newer phone.
87lwrdr said:
Again, being new to this, what can I actually do to this phone? You say I'm stuck on Lollipop for the OS and Touchwiz for an interface what can I use to increase it's functionality and performance ability? I read where Marshmallow doesn't have as many significant changes from Lollipop as the changes were from KitKat to Lollipop but I always thought having the most current OS would aid you in using programs and security designed for newer OS's, just like with computers. What about security and update issues, will they stop supporting Lollipop leaving vulnerable? Or is that the idea, forcing you into buying a newer phone.
Click to expand...
Click to collapse
Pretty much, after 18-24 months companies just stop putting out new software (to get you to buy a new phone), that's part of the reason for using custom ROMs. This device is much older than that and has a locked bootloader, keeping you from doing a lot of things, like using a ROM with an unofficial kernel, so the latest software is not possible. The Sprint and TMo versions of this phone do not have locked bootloaders and are able to use Marshmallow and Nougat, etc. So root the phone using the one methods outlined in the General section (you need to use one that uses SuperSU to use Flashfire) of this forum and then use Flashfire to flash a custom ROM in the Android Development. New features and better functionality. I also recommend removing apps you don't use to decrease RAM consumption and increase performance.
Are you saying I can root this version of my S4 (Galaxy S4 SCH-I545 v.I545VRSGPL1) and then install a custom rom to it using either SuperSU or Flashfire, right? For this version of phone are there any custom roms you would suggest using that are designed more for it? Sorry for all the questions, I just don't want to do something I'll be sorry for or can't reverse or fix.
Again, thanks for all your help and guidance.
87lwrdr said:
Are you saying I can root this version of my S4 (Galaxy S4 SCH-I545 v.I545VRSGPL1) and then install a custom rom to it using either SuperSU or Flashfire, right? For this version of phone are there any custom roms you would suggest using that are designed more for it? Sorry for all the questions, I just don't want to do something I'll be sorry for or can't reverse or fix.
Again, thanks for all your help and guidance.
Click to expand...
Click to collapse
SuperSU is required to use Flashfire, but yes. I would Odin OF1 first or WiFi won't work, I would suggest Stanglitre's ROM it was the most stable I tried for the short time I had this device.
What do I use on build LRX22C.I545VRSGPL1?
I have seen other roms on the site but how do I know if they will work for my build of phone? I try to read as much as I can but the way some people talk and explain things in some of the posts it might as well be in a foreign language. lol. I hope in time I'll be able to understand all the meanings, but right it's a little tough and I don't want to mess things up because I wasn't sure of something. Are the roms made for specific builds or can any be used?
87lwrdr said:
I have seen other roms on the site but how do I know if they will work for my build of phone? I try to read as much as I can but the way some people talk and explain things in some of the posts it might as well be in a foreign language. lol. I hope in time I'll be able to understand all the meanings, but right it's a little tough and I don't want to mess things up because I wasn't sure of something. Are the roms made for specific builds or can any be used?
Click to expand...
Click to collapse
Yes they are for specific builds. You really picked one of the worst phones to start with. Do you have a PC?
Yes, I have a PC. I didn't know anything about this phone when I got it much less the problems I'm facing with it now. I just don't like these phone companies or anyone else backing you into a corner and forcing you to buy something newer because they quit taking care of that product when it's only a couple years old.
87lwrdr said:
Yes, I have a PC. I didn't know anything about this phone when I got it much less the problems I'm facing with it now. I just don't like these phone companies or anyone else backing you into a corner and forcing you to buy something newer because they quit taking care of that product when it's only a couple years old.
Click to expand...
Click to collapse
This device is more than a couple years old... But I would recommend downloading the OF1 firmware from wwe.sammobile.com and using the Odin program to flash it. Then you can use a few of the ROMs on here.
I believe I've flashed the phone successfully. The Baseband Version was - I545VRSGPL1 and now it is - I545VRUGOF1 The Android Version is still 5.0.1 At this point what can I do with or to it now? Thanks
87lwrdr said:
I believe I've flashed the phone successfully. The Baseband Version was - I545VRSGPL1 and now it is - I545VRUGOF1 The Android Version is still 5.0.1 At this point what can I do with or to it now? Thanks
Click to expand...
Click to collapse
You can now root it and flash a ROM. Just follow the rupturing instructions in the General section of the forum.
Not sure what happened but here goes. I flashed the phone to OF1 and then tried to root it so I could put on a new rom. I used kingoroot to root the phone and it showed rooted but could not load flashfire. tried a couple times but kept getting a message that the bianary was occupied and after that when I tried to boot it the phone would freeze on the verizon red boot logo. I tried to re-flash OF1 and now it's stuck on "software update failed" with a yellow triangle and under that it says " your device didn't update successfully". I'm gonna guess that all of this isn't a good thing and hope there is a possible fix for this. Any insight and help would be greatly appreciated.
87lwrdr said:
Not sure what happened but here goes. I flashed the phone to OF1 and then tried to root it so I could put on a new rom. I used kingoroot to root the phone and it showed rooted but could not load flashfire. tried a couple times but kept getting a message that the bianary was occupied and after that when I tried to boot it the phone would freeze on the verizon red boot logo. I tried to re-flash OF1 and now it's stuck on "software update failed" with a yellow triangle and under that it says " your device didn't update successfully". I'm gonna guess that all of this isn't a good thing and hope there is a possible fix for this. Any insight and help would be greatly appreciated.
Click to expand...
Click to collapse
Reflash OF1 with Odin and start over. I told you SuperSU was needed for Flashfire to work right. You need to use a root method that uses SuperSU. There is a couple guides in the General section of this forum.
It won't re-flash. I can boot the phone to d/l mode, then start odin, load the of1 file, it checks it successfully and when I hit start it starts working and stops in about ten seconds while trying to load "system.img.ext4" and shows FAILED
87lwrdr said:
It won't re-flash. I can boot the phone to d/l mode, then start odin, load the of1 file, it checks it successfully and when I hit start it starts working and stops in about ten seconds while trying to load "system.img.ext4" and shows FAILED
Click to expand...
Click to collapse
Try OC1 tar instead.
After numerous times of trying and using different cables and com ports it finally took the OF1 firmware successfully. I don't know if it was using a different port or cable or just a combination of all, but it worked. I used a root checker and it says it's not rooted. Now, do I root with SuperSU then use FlashFire to install the new rom?
87lwrdr said:
After numerous times of trying and using different cables and com ports it finally took the OF1 firmware successfully. I don't know if it was using a different port or cable or just a combination of all, but it worked. I used a root checker and it says it's not rooted. Now, do I root with SuperSU then use FlashFire to install the new rom?
Click to expand...
Click to collapse
Yes
Hi tell us how it was please...I am with the same trouble can not pass from lollipop don't have any rom mod nothing
Related
Hello All,
Looks like I got myself into a pickle with my DNA......
Right now the only two things I can access on the phone are the bootloader and CWM.
How I got here:
I went into CWM recovery and deleted/formatted everything (absolutely everything that could be deleted and/or formatted), thinking I could flash a radio/firmware upgrade, then the LiquidSmooth rom from adb/fastboot. Been a long time since I've worked with this phone and now all I got is the bootloader and CWM. Thought I could use adb to push the rom zip to the device, then go into recovery and flash it the right way, but when I go to fastboot on the device and use the push command in adb it tells me "error device not found".
Gonna stop right there and seek some advice. What's the best way to correct this mess?
Thanks ahead of time!
PS: Working with a DNA with an unlocked bootloader (S-ON), and it was running the stock rom before the first OTA update. I did make a backup file and save it to my PC before I did anything. But, now adb is suddenly not recognizing that the device is connected so I can't push any files to it.
http://forum.xda-developers.com/showthread.php?t=2632351
HTC DNA
LG Optimus G
d08speed3 said:
http://forum.xda-developers.com/showthread.php?t=2632351
HTC DNA
LG Optimus G
Click to expand...
Click to collapse
Not real sure how this will help me.
I cannot boot into Android, and at this point whenever I try to push files to the device via adb it gives me an error and says device not found.
Tried to sideload in recovery?
RLGL said:
Tried to sideload in recovery?
Click to expand...
Click to collapse
Hmmm, I have not. Wasn't familiar with the term until now.
Actually just tried it and thought I was out of the woods. LiquidSmooth started to install, then failed/aborted. Here is a screen shot if someone can tell me what they can make of it:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hackenstein said:
Hmmm, I have not. Wasn't familiar with the term until now.
Actually just tried it and thought I was out of the woods. LiquidSmooth started to install, then failed/aborted. Here is a screen shot if someone can tell me what they can make of it:
Click to expand...
Click to collapse
The problem with that turned out to be an outdated version of CWM. I updated it, only to find my phone would not get recognized in recovery by adb. Found that with the upgrade I also needed a driver upgrade which I took care of (after I had installed TWRP to test as well, just stuck with TWRP). Was able to flash rom (and it sucks). Looking for another one now that is more of a stock (de-bloated with perks, etc).
When I'm done there, should I run firewater to achieve S-OFF so I can update the radio as well, or is there a better way?
No os installed!!! Need help asap!!!!please
I hope im posting in the correct forum (forgive me if im not i mean no disrespect) im new to this rooting thing and made a choice the other day to root my htc dna thats currently on kit kat 4.4.2. I started out with clockworkmod and didnt like that so i then flashed twrp. The reason i didnt want to continue with clockworkmod is because i notice that there was some storage issues going on, i went to my settings and located my storage and saw that the other field was reading that over 13gb was being used up. I couldnt find out what the 13gb was so i started researching and found out that clockworkmod might have been having some issues with duplicating the os therefore taking up too much space. So what i did was try to flash the twrp thinking that would work and the storage was still being taken, so i started researching again and found out that i would need to do a factory reset and start all over....well when i did some how i erased the os as well now im stuck on the htc screen or i have the option of booting up into twrp but thats it.... I downloaded what i thought was the right ruu but thats not working i keep getting error 158....please somebody help me!!!!!!
CHRIST STARZ said:
I hope im posting in the correct forum (forgive me if im not i mean no disrespect) im new to this rooting thing and made a choice the other day to root my htc dna thats currently on kit kat 4.4.2. I started out with clockworkmod and didnt like that so i then flashed twrp. The reason i didnt want to continue with clockworkmod is because i notice that there was some storage issues going on, i went to my settings and located my storage and saw that the other field was reading that over 13gb was being used up. I couldnt find out what the 13gb was so i started researching and found out that clockworkmod might have been having some issues with duplicating the os therefore taking up too much space. So what i did was try to flash the twrp thinking that would work and the storage was still being taken, so i started researching again and found out that i would need to do a factory reset and start all over....well when i did some how i erased the os as well now im stuck on the htc screen or i have the option of booting up into twrp but thats it.... I downloaded what i thought was the right ruu but thats not working i keep getting error 158....please somebody help me!!!!!!
Click to expand...
Click to collapse
There is a search feature to use for finding out how to recover from your mistakes.
Try searching for error 158.
Hackenstein said:
The problem with that turned out to be an outdated version of CWM. I updated it, only to find my phone would not get recognized in recovery by adb. Found that with the upgrade I also needed a driver upgrade which I took care of (after I had installed TWRP to test as well, just stuck with TWRP). Was able to flash rom (and it sucks). Looking for another one now that is more of a stock (de-bloated with perks, etc).
When I'm done there, should I run firewater to achieve S-OFF so I can update the radio as well, or is there a better way?
Click to expand...
Click to collapse
Just for future reference, if you care to allow the dev community to thrive.
Don't use terms like "it sucks".
Maybe..., I don't like it,....or, I didn't care for it,....or it's not what I wanted, or needed, etc,..
But to know little about Android, and then to say that someone elses hard work sucks, is what makes devs say forget it and stop providing their free services to the community.
Just thought I'd point that out.
You can think I suck for saying so, but I'm honestly just trying to help you and the community by letting you know what impact users comments can have on Devs motivation to provide these things in their free time, with nothing in return.
Take it or leave it. Hope you find what suits you.
santod040 said:
Just for future reference, if you care to allow the dev community to thrive.
Don't use terms like "it sucks".
Maybe..., I don't like it,....or, I didn't care for it,....or it's not what I wanted, or needed, etc,..
But to know little about Android, and then to say that someone elses hard work sucks, is what makes devs say forget it and stop providing their free services to the community.
Just thought I'd point that out.
You can think I suck for saying so, but I'm honestly just trying to help you and the community by letting you know what impact users comments can have on Devs motivation to provide these things in their free time, with nothing in return.
Take it or leave it. Hope you find what suits you.
Click to expand...
Click to collapse
Well Said, and on that note, DEVS - I do appreciate all info that I receive here, whether it's from searching/reading or when a question gets answered. Thanks for all you do!!!
tat
santod040 said:
Just for future reference, if you care to allow the dev community to thrive.
Don't use terms like "it sucks".
Maybe..., I don't like it,....or, I didn't care for it,....or it's not what I wanted, or needed, etc,..
But to know little about Android, and then to say that someone elses hard work sucks, is what makes devs say forget it and stop providing their free services to the community.
Just thought I'd point that out.
You can think I suck for saying so, but I'm honestly just trying to help you and the community by letting you know what impact users comments can have on Devs motivation to provide these things in their free time, with nothing in return.
Take it or leave it. Hope you find what suits you.
Click to expand...
Click to collapse
I really love the fact that so many came in to actually ANSWER my question(s) and give relevant info on the issues I was experiencing (heavy sarcasm obviously). Ironic that only when I took a jab at someone's work (out of frustration) that the thread became active with people only sounding off on that issue, still ignoring the original problems I brought to the table. Top notch support!!!!!!
With that out of the way, to santod040; please accept my apology. I said that out of complete frustration and it was totally unecessary. Contrary to the negative vibes that comment conveyed, I DO appreciate all the devs hard work and allow me to publicly thank you for that. It was bad night of troubleshooting for me as I've been out of the loop for quite sometime and was rusty in several areas. Adding to that was the complete lack of helpful info I was finding not only on this site but several others. Kept going in circles and getting no where.
It is extremely important I point out that out of five different ROM's I tried to install via sideload, your's is the ONLY one that actually worked and in the end, I went back to it as it allowed me to finally boot into Android and enable USB debugging and help get the S-OFF process started via Firewater. Conclusively, I was finally able to get the baseband upgraded and get the phone fully up to date. So, thank you, wholeheartedly, and I apologize again for letting my stress get the better of me that night. LiquidSmooth saved my ass.
Cheers, my friend, and thanks again.
I can help if your s-off
hackenstein said:
the problem with that turned out to be an outdated version of cwm. I updated it, only to find my phone would not get recognized in recovery by adb. Found that with the upgrade i also needed a driver upgrade which i took care of (after i had installed twrp to test as well, just stuck with twrp). Was able to flash rom (and it sucks). Looking for another one now that is more of a stock (de-bloated with perks, etc).
When i'm done there, should i run firewater to achieve s-off so i can update the radio as well, or is there a better way?
Click to expand...
Click to collapse
if your s-off i have a method that will help you .....have you switched to s-off?
This came from Sammobile. I downloaded it so I can start working on a rooted ROM. You will need this to update the baseband, etc. anyway, so I figure I post it in case anyone needs it. This is the one to use to upgrade to stock 5.0.1. or return to full stock.
As usual, all at your own risk. Check MD5 before flashing!!
DOWNLOAD HERE
Enjoy...
snovvman said:
This came from Sammobile. I downloaded it so I can start working on a rooted ROM. You will need this to update the baseband, etc. anyway, so I figure I post it in case anyone needs it. This is the one to use to upgrade to stock 5.0.1. or return to full stock.
As usual, all at your own risk. Check MD5 before flashing!!
DOWNLOAD HERE
Enjoy...
Click to expand...
Click to collapse
MAN!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
...just... man.... i soft-bricked and my router was blocking sammobile for some reason. just finished restoring after kicking out bucks for a fast sammoblie download and playing Ethernet games
thanks though
Damn man if i only would have waited instead of making the jump early.....once u flash the or update via ota there's no way of flashing back to kk unless u didnt flash the lollipop bootloader....right?
dinaps86 said:
Damn man if i only would have waited instead of making the jump early.....once u flash the or update via ota there's no way of flashing back to kk unless u didnt flash the lollipop bootloader....right?
Click to expand...
Click to collapse
yeah, that's what happened to me. the boot loader was not having it. my system is still recovering. the boats are burned!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yeah... in general, if you odin'ed the stock package, which includes the bootloader, you can't go back to KK.
At this point, you guys can root and flash the recovery, and just wait for me to complete the deodexed ROM. At that point, you can just flash the ROM via recovery. You will already have the L bootloader and baseband.
There needs to be a real guide to rooting lollipop
Sent from my SM-N915P using XDA Premium HD app
snovvman said:
Yeah... in general, if you odin'ed the stock package, which includes the bootloader, you can't go back to KK.
At this point, you guys can root and flash the recovery, and just wait for me to complete the deodexed ROM. At that point, you can just flash the ROM via recovery. You will already have the L bootloader and baseband.
Click to expand...
Click to collapse
i accepted the OTA. i should have not done that, now i'm trapped
snovvman said:
Yeah... in general, if you odin'ed the stock package, which includes the bootloader, you can't go back to KK.
At this point, you guys can root and flash the recovery, and just wait for me to complete the deodexed ROM. At that point, you can just flash the ROM via recovery. You will already have the L bootloader and baseband.
Click to expand...
Click to collapse
So your saying you've tried to odin back to kk? Past samsung has always been pretty liberal with going backwards.
Rooting lollipop is the same as kitkat n snovman this .zip u posted can be flashed via recovery? Or u just posted the .tar to be flashed through Odin im goong to try n build a kernel for us to set sulinux to permissive bc i cant take not having viper4android
cvaria said:
i accepted the OTA. i should have not done that, now i'm trapped
Click to expand...
Click to collapse
Not at all. I was waiting for lolly to drop for root.. I just did the chainfire method and you're done.
Rooty
jdidtht said:
So your saying you've tried to odin back to kk? Past samsung has always been pretty liberal with going backwards.
Click to expand...
Click to collapse
I'm saying that based on what I have read and experienced, you *generally* cannot revert to a previous major version. Aside from bootloader issues, you may not be able to flash over the modem. This was the case with the Note 2 and 3. I have not tried with the Edge. If you do, please do report.
dinaps86 said:
Rooting lollipop is the same as kitkat n snovman this .zip u posted can be flashed via recovery? Or u just posted the .tar to be flashed through Odin im goong to try n build a kernel for us to set sulinux to permissive bc i cant take not having viper4android
Click to expand...
Click to collapse
This is the Samsung stock image, so it is not a recovery flashable zip. It is a tar that must be flashed via odin. It contains bootloader, baseband, and system image.
FYI--I am uploading a deodexed/zipaligned PRE-BETA rooted Lollipop as I write this. READ: PRE-BETA.
snovvman said:
FYI--I am uploading a deodexed/zipaligned PRE-BETA rooted Lollipop as I write this. READ: PRE-BETA.
Click to expand...
Click to collapse
Ready to test maybe i get xposed back working
Well, here goes nothing....
http://forum.xda-developers.com/not.../rom-sprint-note-edge-915p-5-0-1-oc8-t3082802
For what it's worth, on the regular Sprint Note 4 you can go back to KK once you have taken the Lollipop ota or odin'd the Lollipop tar. The bootloader is backwards compatible on the regular Note 4. However you cannot run a Lollipop rom using the previous KK bootloader. That definitely causes big problems. Another thing you have to keep in mind is that the Lollipop tar writes carrier partitions and other important partitions so you MUST either odin flash the lollipop tar or have taken the lollipop ota BEFORE you flash ANY stock or custom Lollipop ROM via custom recovery. And before you odin the stock Lollipop rom tar you have to first reboot into custom recovery and do the factory reset several times and also wipe system, cache, dalvic etc several times.Then reboot into download mode and flash the Lollipop tar. Do this first or else you will odin the Lollipop tar and have left over data which I guarantee will cause issues. You would think the rom tar would completely wipe these partitions but apparently this isn't happening because there are reports of left over data from previous roms after flashing the stock Lollipop rom tar. I would assume this would apply to the Sprint Note Edge also. This is just a heads up.
Surf and talk
Quick question. I just bought my edge today and I wanted to verify that If I root it I will be able to surf and talk correct?
platniumrover said:
Quick question. I just bought my edge today and I wanted to verify that If I root it I will be able to surf and talk correct?
Click to expand...
Click to collapse
Sounds like you have some reading to do. Educate yourself before you get started.
primo523 said:
Sounds like you have some reading to do. Educate yourself before you get started.
Click to expand...
Click to collapse
I have done alot of reading, just haven't been able to find much on the forum about it. So its true that the sprint variant only comes with one antenna? But the big question for me is how permanent is it? Because there is a chance of doing voice and data over the one antenna in the future. But I dont know which direction they are going. What are the correct strings to search on xda?
platniumrover said:
I have done alot of reading, just haven't been able to find much on the forum about it. So its true that the sprint variant only comes with one antenna? But the big question for me is how permanent is it? Because there is a chance of doing voice and data over the one antenna in the future. But I dont know which direction they are going. What are the correct strings to search on xda?
Click to expand...
Click to collapse
You can usually find a stock version of any device's firmware. That'll bring it back to unrooted factory condition. HOWEVER, keep in mind that Samsung has included a piece of software called Knox on their newer devices. As soon as you modify the firmware (which you will have to do for root), you will trip a counter that lets Samsung know the device is modified. Basically, your warranty is literally void as soon as you root your phone. There are some apps I've seen that try to undo this, but I'm not sure if they work.
But it really sounds like you don't know enough about root to go messing with it. Do more research first.
Here's a link to a pretty good guide that'll give you an idea of what rooting is for.
http://www.androidauthority.com/root-android-277350/
I decided I would start this thread as no one else has started it yet.
This is how to root your Blu Vivo 5!
****BEFORE BEGINNING MAKE SURE YOU DO NOT HAVE "ENABLE OEM UNLOCK" CHECKED IN DEVELOPER OPTIONS AS THIS WILL BRICK YOUR PHONE***
1. Go To h t t p : / / w w w . k i n g r o o t . n e t / (Can't Post Links Yet, Remove Spaces)
2. Download KingRoot (On Your Phone; Or On Your PC and Copy To Your Phone)
3. Open The App and Click "Try To Root" When It Prompts To
4. Once Done, Click The Orange Button in the Center to Fix Permissions
5. Done!
This method was tested by me and a few others. Confirmed working.
***Optionally, you can replace KingRoot with SuperSU using Super-Sume or Apps of that nature but I have not tested these methods personally so tread carefully at your own risk.
Additionally, I can confirm that all root features have worked so far (Viper4Android, AdAway, LuckyPatcher, etc)
No Custom Recoveries Are Available As of this Post, but let's keep this device alive and start development for it!
< If you guys have any questions leave them down below and I'll try to answer them as best as I can and as soon as I can>:good:
Yes been rooted since day one with king root. Just waiting on recovery like most, the device it self is amazing, besides the mms messages not coming in on third party apps this device is still a best for it's price tag.
Man, I really hope development for this device gets picked up. I would like to offer to do some but I don't have the time right now. If things free up I may tinker around with it. I would love to have twrp 3.0 and cm 13 for it but that's going to need someone to port it.
Never mind... It appears to be loose. If I push on it then it starts working.
Did anyone have a problem with ear speaker not making sound after King root? I ran the purity app that comes with it I am wondering if it disabled it or something. Speaker phone works but calls with the ear speaker I cannot here after the root. Should I uninstall kingroot and try again?
This is not helpful. Kingroot is a fools app. It will root your phone but at a significant cost to your security and privacy. Ever think it was weird that kingroot forced you to use its own SUPER-SU manager? Ever think the "Purify" app was a little weird and unessessery? I'm not going to go into details but kingroot isn't offering you a free service for nothing or out if the goodness of their hearts. They steal your information in return which is why they want you to use their app. They report back to themselves your IMEI number among other things.
When people recommend King root it's not helpful, it only makes the rooting community a worse place because noobs and non developers who are naive to these issues are the ones that pay the price.
Is kingroot really that bad?
I was looking around and there are other methods for older blu phones that use Mediatek chips that don't use KingRoot but do require flashing with a custom recovery.
Same issue
i just got mine and im having the same issue even without root. did you find a fix?
AvariceInfest said:
Never mind... It appears to be loose. If I push on it then it starts working.
Did anyone have a problem with ear speaker not making sound after King root? I ran the purity app that comes with it I am wondering if it disabled it or something. Speaker phone works but calls with the ear speaker I cannot here after the root. Should I uninstall kingroot and try again?
Click to expand...
Click to collapse
Xda284988ir said:
This is not helpful. Kingroot is a fools app. It will root your phone but at a significant cost to your security and privacy. Ever think it was weird that kingroot forced you to use its own SUPER-SU manager? Ever think the "Purify" app was a little weird and unessessery? I'm not going to go into details but kingroot isn't offering you a free service for nothing or out if the goodness of their hearts. They steal your information in return which is why they want you to use their app. They report back to themselves your IMEI number among other things.
When people recommend King root it's not helpful, it only makes the rooting community a worse place because noobs and non developers who are naive to these issues are the ones that pay the price.
Click to expand...
Click to collapse
Complete FUD. After you root, you can remove "purify" and you can install a firewall to block anything you want. And you can than install any SU you choose (and remove theirs). I have used Kingroot on many phones with no security issues at all. This is all just unfounded nonsense from when it was first released (years ago) and some people were concerned because the method was not "open". Everything you said has been shown not to be true after the initial releases. Nothing worse than someone (who calls others "noobs") talking about things which they don't know and trying to sound like they know something. You should really research the latest info before you post about something like this.
How do you unroot i used the unroot option in kingroot so i could do the new update but i get a message that the system is broke
Sent from my VIVO 5 using XDA Free mobile app
mopo01 said:
How do you unroot i used the unroot option in kingroot so i could do the new update but i get a message that the system is broke
Click to expand...
Click to collapse
That is how to unroot. It does look like if this phone has ever been rooted it screws with OTAs.
ethd said:
That is how to unroot. It does look like if this phone has ever been rooted it screws with OTAs.
Click to expand...
Click to collapse
? this update really don't matter as it is for radio which I do not use. But when marshmallow finally comes i would like to make that update. Oh well
Sent from my VIVO 5 using XDA Free mobile app
Thanks for this. Rooted the moment I got my phone!
I have a question... If you root the phone with this way, you could update with ota later? Thanks!
It doesn't appear that you can do any OTA's after you root.
I am trying to do the first radio update with hopes of doing the 6.0 update but this is what you get "Your system is damaged, wireless update is disabled".
If anyone knows a way around this it would be appreciated. Any way to get the updates manually and put on the SD card to update via recovery?
Blu support is not very helpful either.
Zeckond said:
I have a question... If you root the phone with this way, you could update with ota later? Thanks!
Click to expand...
Click to collapse
MikeRogers said:
It doesn't appear that you can do any OTA's after you root.
I am trying to do the first radio update with hopes of doing the 6.0 update but this is what you get "Your system is damaged, wireless update is disabled".
If anyone knows a way around this it would be appreciated. Any way to get the updates manually and put on the SD card to update via recovery?
Blu support is not very helpful either.
Click to expand...
Click to collapse
I flashed back to the 5.1 stock with sp tools and then ota the 6.0. remember to back up data if you do this way as I forgot and lost a lot ?
I did save the ota file it's 1.2 gig not sure how to upload for you to try tho
Sent from my VIVO 5 using XDA Free mobile app
Hmm, maybe google drive or something?
mopo01 said:
I flashed back to the 5.1 stock with sp tools and then ota the 6.0. remember to back up data if you do this way as I forgot and lost a lot ?
I did save the ota file it's 1.2 gig not sure how to upload for you to try tho
Sent from my VIVO 5 using XDA Free mobile app
Click to expand...
Click to collapse
MikeRogers said:
Hmm, maybe google drive or something?
Click to expand...
Click to collapse
try this
https://drive.google.com/file/d/0B3817QHU8ZK1a1M0ZnRzaVdnaUk/view?usp=drivesdk
Sent from my VIVO 5 using XDA Free mobile app
Downloading this now and will let you know how it goes, thanks.
UPDATE: This worked great, thank you!
Just for anyone else who tries this, the actual update.zip file you need is inside this update.zip file so extract it out before putting it on the sdcard.
mopo01 said:
try this
https://drive.google.com/file/d/0B3817QHU8ZK1a1M0ZnRzaVdnaUk/view?usp=drivesdk
Sent from my VIVO 5 using XDA Free mobile app
Click to expand...
Click to collapse
Is anyone else having terrible battery life on this after upgrading to Marshmallow?
After doing the update to Marshmallow in this thread, I flashed TWRP and rooted via this thread.
Now my battery life has been absolutely terrible. Before updating to Marshmallow, I could go almost all day, have 35%+ left at night, goto sleep and then wake up with around 20% of battery all the time. Now if I goto sleep with 50% battery it's dead when I wake up. Seems to be "Wlan" and "Phone Idle" using most of the battery as you can see in the screenshot below. Also, after the phone dies and I plug it back in, it always shows as 13-15% battery life right away (odd), so I used a battery calibration app that seemed to do nothing and still same bad battery.
I'm thinking it may be due to me missing the OTA update right before the Marshmallow OTA update. I know it had to do with the radio, could that be it? Does anyone have that in a zip file I could flash via TWRP? If so, would it be ok to do that?
Any ideas would be appreciated, here's a screenshot of battery usage:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
For anyone wondering, no you cannot run OTA and update your phone if you rooted using Kingroot. Even doing a factory reset won't help. You will have to flash the phone using a stock rom and then rerooting after you update.
Is this at all possible? When attempting to downgrade with LGUP, it interrupts the flashing process (usually) around 9% with this error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is there a way to force-flash it regardless of this error? Or am I stuck without root forever?
Any answers are greatly appreciated.
At this moment in time the answer is NO. This is why you want to not do an upgrade until root is confirmed for the newer OS. Once recovery is available maybe you might be able to get root back.
I should correct myself you can't use the kdz files and go back to lolipop
details here :
http://forum.xda-developers.com/lg-v10/general/guide-lg-v10-stock-firmware-to-stock-t3224170
I was thinking about the TWRP method before, my bad.
LBJM said:
I should correct myself you can't use the kdz files and go back to lolipop
details here :
http://forum.xda-developers.com/lg-v10/general/guide-lg-v10-stock-firmware-to-stock-t3224170
I was thinking about the TWRP method before, my bad.
Click to expand...
Click to collapse
Thank you for the snappy reply! I have been very closely watching these forums on updates to either downgrade to lollipop, or root marshmallow. I sure hope we can get this resolved for people who's phone came with marshmallow
jingTongy said:
Thank you for the snappy reply! I have been very closely watching these forums on updates to either downgrade to lollipop, or root marshmallow. I sure hope we can get this resolved for people who's phone came with marshmallow
Click to expand...
Click to collapse
I had to downgrade using that same software when I purchased my Lg G3 and that alone sold me on the V10. With Samsung phones you are stuck if you have a newer OS.
The main reason you cannot downgrade is that the software won't flash an old version (as it checks your version stub), at all, on Verizon.
mcbeat257 said:
The main reason you cannot downgrade is that the software won't flash an old version (as it checks your version stub), at all, on Verizon.
Click to expand...
Click to collapse
So, with the way you termed it, it sounds like it's a software problem with LGUP?? If so, do you think it can be patched to ignore the version?
jingTongy said:
So, with the way you termed it, it sounds like it's a software problem with LGUP?? If so, do you think it can be patched to ignore the version?
Click to expand...
Click to collapse
The software itself makes it do this, and it is irrevocable and not able to do so in the builds, it reminds me of when I had my galaxy s4 and this happened as well.
According to this thread , you can:
http://forum.xda-developers.com/lg-v10/general/guide-lg-v10-stock-firmware-to-stock-t3224170
I normally do not root my phones, but I am having battery drain problems and I see no advantage to Marshmallow. I may downgrade if I cannot resolve my current problem.
mikekoz said:
According to this thread , you can:
http://forum.xda-developers.com/lg-v10/general/guide-lg-v10-stock-firmware-to-stock-t3224170
I normally do not root my phones, but I am having battery drain problems and I see no advantage to Marshmallow. I may downgrade if I cannot resolve my current problem.
Click to expand...
Click to collapse
Could you quote the part on that post where it talks about downgrading the firmware? As far as I can tell from the link you provided, that post only talks about returning the phone back to stock. And just to be clear, once you install the OTA update to the MM build, your stock is now the MM firmware. Please correct me if I am wrong.
zatanas33 said:
Could you quote the part on that post where it talks about downgrading the firmware? As far as I can tell from the link you provided, that post only talks about returning the phone back to stock. And just to be clear, once you install the OTA update to the MM build, your stock is now the MM firmware. Please correct me if I am wrong.
Click to expand...
Click to collapse
You may be correct, and hopefully somebody more knowledgeable than myself will chime in, but this text is part of the instructions from that thread:
TO GO BACK TO LP FROM MM - Open LGUP on your computer, click on FILE PATH and point it towards your LP KDZ. Close LGUP and re-open LGUP. Make sure you select REFURBISH this will do a FULL wipe, tick BIN file. Press Start. Make cup of tea and be patient
This does not work on the Verizon variant
Sent from my VS990 using XDA-Developers mobile app
mikekoz said:
According to this thread , you can:
http://forum.xda-developers.com/lg-v10/general/guide-lg-v10-stock-firmware-to-stock-t3224170
I normally do not root my phones, but I am having battery drain problems and I see no advantage to Marshmallow. I may downgrade if I cannot resolve my current problem.
Click to expand...
Click to collapse
I was having the same battery drain problem after the Marshmallow update on my V10. I let it go for a couple days to see if things would improve. Unfortunately, things weren't getting any better. While I've rooted a lot of Android phones in the past, I didn't really want to void the warranty on this phone yet.
I went ahead and did a factory reset and the battery is working better than ever. I usually use Titanium Root to backup, but had to rely on LG Backup this time. It worked well enough even though it took a long time to copy everything to the SD Card (about 3 hours for 4 GB). Only things that didn't come through after restoring were my home screen settings and the history for one game. No big deal, about an hour to get everything configured back to original (grab screenshots of your homescreen first).
Pretty thrilled to see the battery performing better than ever. Just got 16 hours out of it yesterday and had 35% left on somewhat light use.
burnsky05 said:
This does not work on the Verizon variant
Sent from my VS990 using XDA-Developers mobile app
Click to expand...
Click to collapse
The instructions say otherwise. There is even links to Verizon drivers. Where do you see that this method does not work for Verizon V10's?
http://forum.xda-developers.com/showthread.php?t=3344828
Sent from my VS990 using XDA-Developers mobile app
The thread also states its for certain models of LG V10 but the LGUP has a anti rollback built into it that will not allow you to go from marshmallow to lollipop on certain models...
burnsky05 said:
http://forum.xda-developers.com/showthread.php?t=3344828
Sent from my VS990 using XDA-Developers mobile app
The thread also states its for certain models of LG V10 but the LGUP has a anti rollback built into it that will not allow you to go from marshmallow to lollipop on certain models...
Click to expand...
Click to collapse
Thanks. :good:
So, maybe someone could come up with a anti rollback work around? Hopefully, or some other alternative.
hann1balk1ng said:
So, maybe someone could come up with a anti rollback work around? Hopefully, or some other alternative.
Click to expand...
Click to collapse
Possible if someone could reverse-engineer LGUP to allow downgrading. I have the lollipop KDZ file, now all I need is a way to flash it to my vs990.
In an attempt to downgrade an error was not seen in LGUP. As far as anyone could tell the phone and LGUP were in sync up until 85% or so and the reboot was initiated. The phone never came back on. LGUP made it to 100% but the phone stayed black. Maybe not,enough time was allowed to pass but the battery was then removed. The phone became a brick and wouldnt start in any mode. When plugged into a computer the computer sees something tries to install a driver then fails. Do not try and downgrade from Marshmallow with LGUP. It will not work.
AMCJUNGLE said:
In an attempt to downgrade an error was not seen in LGUP. As far as anyone could tell the phone and LGUP were in sync up until 85% or so and the reboot was initiated. The phone never came back on. LGUP made it to 100% but the phone stayed black. Maybe not,enough time was allowed to pass but the battery was then removed. The phone became a brick and wouldnt start in any mode. When plugged into a computer the computer sees something tries to install a driver then fails. Do not try and downgrade from Marshmallow with LGUP. It will not work.
Click to expand...
Click to collapse
Oh man that sucks.
Sent from my Nexus 7 using XDA-Developers mobile app
Hello everyone!
I'm new around here and it would be much appreciated if you guys can help me out a little.
As the title says i have a Verizon Samsung galaxy s4
SCH-I545
Android version: 5.0.1
Baseband: I545VRSGPL1
Build number: LRX22C.I545VRSGPL1
Knox version: 2.3
Can i install a custom recovery like TWRP and then install a custom ROM ?
I previously had a HTC One M7 International and i unlocked the bootloader and installed TWRP recovery along with several other ROMS through my usage of the phone. Is there a way to do the same thing with this Verizon S4 ?
Thanks for your help!!
Coincidentally, I just got an S4 yesterday. It has the same build number. I got it rooted with the Kingroot and SuperSU script mentioned here. I've looked on the forums for information about replacing the ROM, but they all mention different build numbers. I'd like to update the ROM in this phone as well.
After getting root, I flashed this ROM, using the OF1 instructions.
https://forum.xda-developers.com/galaxy-s4-verizon/development/stang5litre-ediition-5-0-t3132555
It installed correctly, but once I unlock and get to the home screen, I get a a constant "...gapps has stopped" popup error. It seems to be related to the Google search box on the home screen. Any ideas on how to correct this?
I fixed the gapps problem see "Readers' favorite comments" here:
https://www.androidpit.com/process-com-google-process-gapps-has-stopped-fix
---------- Post added at 07:17 PM ---------- Previous post was at 06:45 PM ----------
Now that I have the STANG5LITRE ROM installed and working, is there any way to flash an earlier ROM/bootloader, so I can install CWM or TWRP? I'd like to try installing other ROMs. Although I got this phone for free, and it is not my primary phone, I'd hate to brick it. If not, are there any other ROMs that I can flash, considering the locked bootloader?
No, there is no TWRP or CMW for this device as the bootloader is locked. Flashfire is the only option to flash ROMs. So make sure you have the latest tar to recover if you have a bootloop or something like that.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks. Where can I find the PL1 original ROM?
I can't get WiFi to turn on with either the STANG5LITRE ROM or this one: https://forum.xda-developers.com/ga...ort-albe95-s6-port-4-5-updt-23-09-15-t3234009
I used the OC1 instructions. I also tried the OF1 WiFi fix. I'm about to try this: https://forum.xda-developers.com/showpost.php?p=67174300&postcount=424
Edit: Well, that FlashFire version doesn't run. It closes right away.
For PL1, what is the best performing, least bloated TW ROM (pre-rooted or rootable) without a bunch of bells and whistles added? It seems that all the really good ROMs need an unlocked bootloader. I won't be using this S4 as a phone (no SIM), but I would like the WiFi to work.
mojoehand said:
Thanks. Where can I find the PL1 original ROM?
I can't get WiFi to turn on with either the STANG5LITRE ROM or this one: https://forum.xda-developers.com/ga...ort-albe95-s6-port-4-5-updt-23-09-15-t3234009
I used the OC1 instructions. I also tried the OF1 WiFi fix. I'm about to try this: https://forum.xda-developers.com/showpost.php?p=67174300&postcount=424
Edit: Well, that FlashFire version doesn't run. It closes right away.
For PL1, what is the best performing, least bloated TW ROM (pre-rooted or rootable) without a bunch of bells and whistles added? It seems that all the really good ROMs need an unlocked bootloader. I won't be using this S4 as a phone (no SIM), but I would like the WiFi to work.
Click to expand...
Click to collapse
You have to use v.53 or older of FF, the newer builds don't work on this device. Stanglitre's was the only one that everything worked for me for the short time I had this device. You can debloat whatever you don't use with ROM Toolbox or whatever app of your choosing.
All Odin flashable tars can be found at www.sammobile.com
bilgerryan said:
You have to use v.53 or older of FF, the newer builds don't work on this device. Stanglitre's was the only one that everything worked for me for the short time I had this device. You can debloat whatever you don't use with ROM Toolbox or whatever app of your choosing.
All Odin flashable tars can be found at www.sammobile.com
Click to expand...
Click to collapse
I did use FF v0.53 to flash both ROMs.. After playing around with it, I really like the S6 ROM. I just wish I could get the WiFi working. Bluetooth seems to work. I side loaded Titanium Backup to remove some apps.
mojoehand said:
I did use FF v0.53 to flash both ROMs.. After playing around with it, I really like the S6 ROM. I just wish I could get the WiFi working. Bluetooth seems to work. I side loaded Titanium Backup to remove some apps.
Click to expand...
Click to collapse
I never flashed with PL1, I would see if you could Odin back to OF1, I was able to switch between OF1 and OC1. That's probably the only way the WiFi fix will work for you.
Because of the locked bootloader, I was hesitant to downgrade. Based on your statement that you were able to go from OF1 to OC1, I took a chance.
I found a stock, rooted OF1 online and flashed with FF. This worked fine. I then used the OF1 instructions to install the S6 ROM. I am happy to say that WiFi is now working.
Thanks for all your help.
mojoehand said:
Because of the locked bootloader, I was hesitant to downgrade. Based on your statement that you were able to go from OF1 to OC1, I took a chance.
I found a stock, rooted OF1 online and flashed with FF. This worked fine. I then used the OF1 instructions to install the S6 ROM. I am happy to say that WiFi is now working.
Thanks for all your help.
Click to expand...
Click to collapse
I know this is an old thread and you've no doubt moved on but if you can recall the stock rooted rom you flashed?
It be greatly appreciated. I'm on pl1 bootloader and there's very little info out there. Thanks
KLit75 said:
I know this is an old thread and you've no doubt moved on but if you can recall the stock rooted rom you flashed?
It be greatly appreciated. I'm on pl1 bootloader and there's very little info out there. Thanks
Click to expand...
Click to collapse
I don't remember where I found it, but the file name is: I545_OF1_Stock_Rooted_ROM.zip
mojoehand said:
I don't remember where I found it, but the file name is: I545_OF1_Stock_Rooted_ROM.zip
Click to expand...
Click to collapse
Thanks man! That was just enough info...
https://androidfilehost.com/?fid=24052804347797371
KLit75 said:
Thanks man! That was just enough info...
https://androidfilehost.com/?fid=24052804347797371
Click to expand...
Click to collapse
I recommend Stanglitre's ROM for this device. Definitely has more options than stock.
mojoehand said:
I did use FF v0.53 to flash both ROMs.. After playing around with it, I really like the S6 ROM. I just wish I could get the WiFi working. Bluetooth seems to work. I side loaded Titanium Backup to remove some apps.
Click to expand...
Click to collapse
So again, this is a little old and you might not recall but figured you'd be my best chance at solving it.
I couldnt get any flashfire .53 or below to work (tried about 5 different versions, immediate FC or itd crash seconds later.) Strangely, the latest version right from play store worked.
I did a full wipe then flashed the stock rooted rom. It started the process, briefly showed the samsung logo then the code rolled down the screen (all seemed fine.) Then it went black and stayed black with the blue led light remaining solid. I let it remain with the black screen for 15 minutes then pulled the battery.
To my surprise, it booted into the previously installed rom, all the data remains.
Do you have any theories? Its almost as if the phone blocked the installation, which would make sense I guess but cant understand why it didn't so much as erase the cache partition...
Anyway, I just thought I'd ask in case you recall encountering or reading anything like this when you were trying to downgrade. Thanks again!
bilgerryan said:
I recommend Stanglitre's ROM for this device. Definitely has more options than stock.
Click to expand...
Click to collapse
How about You? Did u also have a pl1 and successfully downgrade with FF?
My last post details the problem I ran into using FF.
THANKS!
KLit75 said:
How about You? Did u also have a pl1 and successfully downgrade with FF?
My last post details the problem I ran into using FF.
THANKS!
Click to expand...
Click to collapse
No, PL1 wasn't out when I had this device. Flashfire is really touchy, I had to try a bunch of different versions before I found one that worked for this device (v.53 is what worked for me). Make sure you follow the ROM flashing instructions to the letter. I haven't had this device for over a year, so this is all from memory.
bilgerryan said:
I recommend Stanglitre's ROM for this device. Definitely has more options than stock.
Click to expand...
Click to collapse
bilgerryan said:
No, PL1 wasn't out when I had this device. Flashfire is really touchy, I had to try a bunch of different versions before I found one that worked for this device (v.53 is what worked for me). Make sure you follow the ROM flashing instructions to the letter. I haven't had this device for over a year, so this is all from memory.
Click to expand...
Click to collapse
Thanks. I might need to do some more digging. Maybe you can't flash a rom on pl1 (verizon). But on a few posts I did see people saying FF took a really long time (30+ MINS on black screen) but I can't see why it'd take 15 MINS before it even wiped data.
KLit75 said:
Thanks. I might need to do some more digging. Maybe you can't flash a rom on pl1 (verizon). But on a few posts I did see people saying FF took a really long time (30+ MINS on black screen) but I can't see why it'd take 15 MINS before it even wiped data.
Click to expand...
Click to collapse
As far as I know, PL1 is just a security update, I am 95% sure you will have to Odin back to OF1 or OC1 to get WiFi to work on any of the available ROMs. Check out this post also - https://forum.xda-developers.com/showthread.php?p=73513294. I would personally try that ROM first too, it's got the most complete instructions and most stable in my opinion. Also make sure you have SuperSU binary. I recommend using the free trial of a Windows program called Wondershare (Google "Wondershare root exe"). It's the easiest way to get SuperSU and root, the trial is only 5 days though, but that should be enough to get the job done.
bilgerryan said:
As far as I know, PL1 is just a security update, I am 95% sure you will have to Odin back to OF1 or OC1 to get WiFi to work on any of the available ROMs. Check out this post also - https://forum.xda-developers.com/showthread.php?p=73513294. I would personally try that ROM first too, it's got the most complete instructions and most stable in my opinion. Also make sure you have SuperSU binary. I recommend using the free trial of a Windows program called Wondershare (Google "Wondershare root exe"). It's the easiest way to get SuperSU and root, the trial is only 5 days though, but that should be enough to get the job done.
Click to expand...
Click to collapse
I really appreciate the help. So pl1 doesn't have an updated bootloader? And I can just flash any lollipop firmware?
I'm relatively new to Samsung but I do have an S7 EDGE. Ive used Odin before but my s7 is unlocked. However I know other s7 users are able to flash U firmware on carrier branded devices. Can I do that on the S4 Verizon?
And I read in multiple places, even if I downgrade, I have to flash a touchwiz based rom. Afaik there's 2 available (stang5litre & an s6 rom). Its my understanding that those are the only roms that'll boot.
Thanks again!