Related
I am a newbie in android and rooting. i previously had sony xperia x8 which i had rooted and installed custom roms. i shifted to galaxy tab 2 months ago. i had a harrowing experience with rooting since last two days. let me tell you how it all started. i rooted my device to install titanium backup. it worked fine for few days . then i installed cmw recovery and it worked fine too. no issues what so ever. there were random FC's and hanging about once or twice a day.
Then all of sudden while browsing tablet hanged and it went into bootloop. i tried everything .. from factory reset to flashing firmware. it did not work. it was stuck on samsung logo. when i had lost all hope after about 2 hours or so it started working again. i got scared and unrooted the device and removed cmw.
for two days it was working fine. Then again i had this urge to root it . i rooted it . it worked fine for a week or so .. And then all of sudden it started having force closes . TW and google play and all other apps. i got scared and removed root and cmw again. this time however i decide to take it to service center. i did not tell them i had rooted and all . just told them i was having problem with reboots and all . they gave me full warranty. After two days i got a call from them that it was not booting and they have to replace motherboard
i asked them to return the tab to me for a night and i will give it back to them in morning since it was going to take two days for board to arrive. when i checked i found it was possible to go into download mode and not recovery mode. i tried flashing firmware via odin but it was stuck at factory.img.
i read somewhere in Galaxy note forum that it was superbrick bug and i had to use .pit file to repartition. i downloaded the file from google and repartioned it and installed firmware for my country via odin.
and it worked
Now my question is ....
Should i get a motherboard replacement or demand a new tab ? or is this tab ok now ? will i get such problems in future .
om0 said:
I am a newbie in android and rooting. i previously had sony xperia x8 which i had rooted and installed custom roms. i shifted to galaxy tab 2 months ago. i had a harrowing experience with rooting since last two days. let me tell you how it all started. i rooted my device to install titanium backup. it worked fine for few days . then i installed cmw recovery and it worked fine too. no issues what so ever. there were random FC's and hanging about once or twice a day.
Then all of sudden while browsing tablet hanged and it went into bootloop. i tried everything .. from factory reset to flashing firmware. it did not work. it was stuck on samsung logo. when i had lost all hope after about 2 hours or so it started working again. i got scared and unrooted the device and removed cmw.
for two days it was working fine. Then again i had this urge to root it . i rooted it . it worked fine for a week or so .. And then all of sudden it started having force closes . TW and google play and all other apps. i got scared and removed root and cmw again. this time however i decide to take it to service center. i did not tell them i had rooted and all . just told them i was having problem with reboots and all . they gave me full warranty. After two days i got a call from them that it was not booting and they have to replace motherboard
i asked them to return the tab to me for a night and i will give it back to them in morning since it was going to take two days for board to arrive. when i checked i found it was possible to go into download mode and not recovery mode. i tried flashing firmware via odin but it was stuck at factory.img.
i read somewhere in Galaxy note forum that it was superbrick bug and i had to use .pit file to repartition. i downloaded the file from google and repartioned it and installed firmware for my country via odin.
and it worked
Now my question is ....
Should i get a motherboard replacement or demand a new tab ? or is this tab ok now ? will i get such problems in future .
Click to expand...
Click to collapse
Superbick bug? Isnt that on leaked ICS kernels??
I had an issue like this a while ago it looked like my data partitions got corrupted. Just had to e2fs em
Well if they want to replace it, I'd let them. I personally don't think it was root and cwm causing your issues but that's just opinion
Sent from my DROID BIONIC using Tapatalk 2
nicduim said:
I had an issue like this a while ago it looked like my data partitions got corrupted. Just had to e2fs em
Well if they want to replace it, I'd let them. I personally don't think it was root and cwm causing your issues but that's just opinion
Sent from my DROID BIONIC using Tapatalk 2
Click to expand...
Click to collapse
What is e2fs? And is the OP saying there's a solution to superbrick bug?
--thanks for tolerating my lack of familiarity with repartitioning mobile devices (i still get nervous repartitioning regular HD's)
The indefinite microcosm becomes the indefinite macrocosm in a definite manner and by definite means...and vice versa.
aletheus said:
What is e2fs? And is the OP saying there's a solution to superbrick bug?
--thanks for tolerating my lack of familiarity with repartitioning mobile devices (i still get nervous repartitioning regular HD's)
The indefinite microcosm becomes the indefinite macrocosm in a definite manner and by definite means...and vice versa.
Click to expand...
Click to collapse
Sorry tired but here is a link where to the thread I came across in the past
http://forum.xda-developers.com/showthread.php?p=25848578
I did something similar to what was posted in here after checking the partition thread. Looks like it's mentioned in the link. Hope it helps. Will look it over later and try to find the exact steps I had done and looked up but it did help fix my loops and they're been gone for like 2 months.
Sent from my GT-P6800 using Tapatalk 2
Superbrick ?
i dont know if my tab was stuck on superbrick or not
it was stuck on factoryfs.img while odin flash. i read this thread where it mentions that if a phone is stuck on factoryfs.img then its super brick. i followed the method mentioned in this thread to get it unblocked and it worked .
http://forum.xda-developers.com/showthread.php?t=1656635
Nobody wants to ruin a $28 per square inch tablet, but I REALLY don't want to. So I'm just doing what research I can before the official ics update rolls out. It's looking alot sunnier knowing that the thing isn't DOOMED, even if samsung doesn't compensate for the superbrick bug...
i'd say they'd be fools not to, but we've all gotten real up close and personal with samsung and how they treat their customers with the release of the p6800, so....
Thanks ALOT guys for getting down into the trenches and figuring all this out.
-----------
The indefinite microcosm becomes the indefinite macrocosm in a definite manner and by definite means...and vice versa.
I have used custom roms for a while about 4 years on various models, I consider myself to know enough to get the job done and sometimes I know enough to get myself in trouble.
I ungraded my Galaxy S4 Sprint phone firmware to NAE from (http://forum.xda-developers.com/showthread.php?t=2338919), and then I put the KitKat rom from (http://forum.xda-developers.com/showthread.php?t=2650706), and when it came up, it did not have Data or Cell connectivity, (Said Unknown in settings screen) it had Wifi, and it had NO SOUND at all. So I moved back and put a 4.3 rom on there, and I got back the Data and Cell connectiviy, but still no SOUND at all, and when I used the Dialer app and dial a number it went to a white screen and then locked up and Force Closed.
Then I tried to go back and put MK2 firmware on from that same post above with same results. I have tried many ROM's of many varieties of Android and NO SOUND at all.
I am using Philz Recovery and doing the Wipe for Clean Install many times and then rebooting back into recovery mode before I install any Rom. I am using Odin 3.07 for the Modem firmware updates and have no indication that they are installing wrong.
I have searched for the solution on these forums and googleing it for the better part of 4 hours (At a late night job). I have not been able to fix it.
Please help. I have wifi, I can text and receive texts. I can not make phone calls or recieve phone calls. I can not play sounds or hear any sounds come from phone. Haptic response happens when it should.
I plan on going and downloading one of the Sprint Stock Roms to take it back to stock through and through to see if that helps and will post it that works, but if there is another solution with detailed steps to take, let me know.
[SOLVED] No SOUND after update.
micah.weihert said:
... I plan on going and downloading one of the Sprint Stock Roms to take it back to stock through and through to see if that helps and will post it that works, but if there is another solution with detailed steps to take, let me know.
Click to expand...
Click to collapse
And that Plan worked. I downloaded the stock MK2 rom from sammobile website, using the free signup and then I used Odin 3.09 putting that rom in the AP spot.
Afterwards, I was Knoxed and Un Rooted, but I had SOUND where as before I did not.
So back to the process of de-knoxing and rooting.
I did find this process on XDA finally. Thanks.
micah.weihert said:
And that Plan worked. I downloaded the stock MK2 rom from sammobile website, using the free signup and then I used Odin 3.09 putting that rom in the AP spot.
Afterwards, I was Knoxed and Un Rooted, but I had SOUND where as before I did not.
So back to the process of de-knoxing and rooting.
I did find this process on XDA finally. Thanks.
Click to expand...
Click to collapse
i'm having thesame issue, flashed NAE modem and every ROM after that has had no sound, constant re-boots, locking up, some ROMS work fine, others are unusable, but they all have the same problem: no sound. I'm goin g to flash back stock like you did, glad i searched before i created a thread just like yours, wish me luck.
I just swapped from my Amaze 4g, to a used Note 3, and I'm a little lost as far as where I should start.
It says that it's on 4.4.2, and that I cannot update due to a modified system.
Basically, I would like to get updated to 5.1.1 (or as close as is official for the Note 3), and root it.
I'm afraid I'm not familiar with Samsung devices, and because I purchased this from ebay, I don't know how to tell the exact state that the former user put it in (I expected they would return it to stock prior to selling).
It's currently a T-Mobile branded, SM-N900T, on 4.4.2, build is KOT49H, security software MDF v1.0 release 2. Kernel is 3.4.0-660648.
It is supposedly unlocked for carriers, though I have not attempted a SIM card use yet, until I can tell that what I have is a valid device and the IMEI is checked out.
Any thoughts on how to validate the IMEI, and sort out how to get my new phone up to date would be appreciated. As I stated, I expected the vendor would have returned it to stock, but that is clearly not the case, so I don't want to accidentally boot loop it by doing something I shouldn't. I have not owned a Samsung before, so I want to be careful on how it differs from my Nexus 7, Amaze 4g, and Droid X, as they're all obviously very different in the OS area.
Thank you for the help1
Download tbe stock 4.4.2 rom and use odin to install. Then you will get the OTA updates.
Sent from my SM-N900P using Tapatalk
There is no stock 5.1.1 for note 3, only cm12.1/ aosp. Latest is 5.0 and you can use odin to flash. Maybe it's rooted that's why you can't update.
bladebarrier said:
I just swapped from my Amaze 4g, to a used Note 3, and I'm a little lost as far as where I should start.
It says that it's on 4.4.2, and that I cannot update due to a modified system.
Basically, I would like to get updated to 5.1.1 (or as close as is official for the Note 3), and root it.
...
Thank you for the help1
Click to expand...
Click to collapse
Some apps to install from Play Store...
Phone INFO Samsung - this will tell you all about your phone and the firmware etc.
Root Checker Basic - tells you if you are rooted or not.
SuperSU - this is so valuable you should buy the Pro licence. Chainfire does some great work for our phones.
TWRP - I have the zip version on my extSDCard and an Odin version on PC in case I have to rebuild from a Stock firmware. CWN works OK but most ROM builds seem to be for TWRP I think and a backup from one will not work on the other.
I don't know your previous phone so you probably need Odin v3.09 - this sits on PC and lets you flash firmware to the phone. (connected by USB)
For which you need Samsung USB drivers so the PC will recognise the phone. Install on PC before connecting phone.
Then do some browsing and find the processes to root your phone and install the ROM you want. If you just want Stock and access to all your phone, you can root it after flashing the original v5.0 download (from Sammobile or similar site - note on Sammobile you need a free account to DL) and then install Custom recovery (if wanted - it WILL trip the Knox flag but that may not matter given it's 2nd hand and might already be tripped anyway)
Read, make SURE you understand what is being said BEFORE you do anything - ask if you don't.
Good luck...
N9005 Lollipop brick
Hi All, just need a huge help here, a friend of mine has been using a N9005 which was auto restarting, she went online and downloaded this firmware...N900AUCUEOC1_N900AATTEOC1_N900AUCUEOC1_HOME.tar.md5....2.5GB in size...and flashed it, but the phone is stuck in boot loop even after recovery wiping data and cache, the phone can boot into download mode but re flashing the firmware always fails.....is there a solution for this.....please help
Thank you all for the info, especially the detailed info from Journyman16. I checked, and it is flagged as custom, which is fine, so I'm going to go ahead and try to return to mostly stock, update it, and root it.
Ok, everything went well. I had to do two attempts at rooting, but I think it's just one of those things where sometimes it doesn't restart into the process every time.
All seems good. I'm on 5.0, rooted, busyboxed, and smooth sailing.
Thank you all, again, for the tips. The Note 3 is running very well. Thank you to all of the devs that have made this process so refined. I've donated to you before, and did so again today. It's outstanding to have such well versed coders, on XDA, helping out the community.
mjmbirige said:
Hi All, just need a huge help here, a friend of mine has been using a N9005 which was auto restarting, she went online and downloaded this firmware...N900AUCUEOC1_N900AATTEOC1_N900AUCUEOC1_HOME.tar.md5....2.5GB in size...and flashed it, but the phone is stuck in boot loop even after recovery wiping data and cache, the phone can boot into download mode but re flashing the firmware always fails.....is there a solution for this.....please help
Click to expand...
Click to collapse
You have never learned not to ask in others posts? What does your problem has to do with this topic at all?
When you need help. Just click on Q&A then Create a new thread. How hard is it?
I've rooted and replaced the ROM on 3 other Android devices. I've spent two or three nights on this. Googling and reading page after page to try to get this right. I know I'm seriously lacking in knowledge, but I just can't stand the bloatware and lack of control over an OEM ROM. I knew I was taking a risk, but I did my best to be diligent without spending an excessive amount of time. All that said, I appreciate, in advance any help anyone can offer me. Whether that's direct advice or directing me to proper resources that I can't seem to find.
Samsung S5 SM-G900P (kltespr)
I had rooted it. I replaced the Sprint stock ROM (5.0.1 I think) with CM12.1 (which just got an OTA). I had TWRP 2.8.7 on it.
Unfortunately, I needed my research suggested I needed a Touchwiz ROM in order to activate phone service on the cell provider I'd chosen (Ting).
So I selected MOAR v7 and started following the directions here:
at galaxys5root.com/sprint-galaxy-s5-custom-roms/moar-lollipop-rom-for-sprint-galaxy-s5-w-2-8ghz-oc
I made a backup. I wiped the system/cache/davlik/etc.
I installed the Android 5.0 Bootloader TAR (G900P NDK Lollipop) per the instructions via Odin and using the Bootloader option. The flash failed. I can repeat the failure (ran Odin as admin, tried multiple USB ports, restarted the computer etc). I've since tried to send several recovery ROMS or OS ROMS (pardon if I'm using the wrong terminology here) to the device, but all I can get is download mode or a screen that says Samsung Galaxy S5 powered by Android (with Kernel is not Seandroid enforcing at the top). Sending TWRP via Odin has worked with a PASS, but still can't startup the device.
I can provide more detailed logs or information about where I'm stuck and how, but on the off chance that this is an obvious thing I'm going to stop here unless more detail would be useful.
Again, I'm grateful in advance for any help.
Moshker
Follow up and how I fixed my brick
This post is intended as a follow up in case anyone runs into a similiar problem and stumbles onto my post.
After trying several different bootloaders, including the stock ones from Samsung (multiple download attempts, very slow speeds, some didn't pass md5 check), and full ROM efforts via Odin 3.10.7 I was finally able to get one ROM to take.
G900PVPU3BOG1_G900PSPT3BOG1_SPR from androidfilehost.com/?fid=24052804347794921
After getting the phone activated on Ting I used Odin to push Chainfire Auto Root (408). I verified root after restart. Used Nandroid to make a new backup. I used Flashify to install TWRP 2.8.7. I restarted to recovery and DID NOT use TWRP to wipe the system/data/etc and instead loaded the MOAR7.0.OA6 ROM. During the ROM install process it asked if I'd like to wipe system/cache/davlik/etc. I did. The ROM installed successfully. I ran a Nandroid restore to bring back my apps and data. Most restored properly.
I still don't really understand what went wrong, why my efforts to fix it failed, and why the last thing I tried worked.
Really loving MOAR. I'm using the Numix theme and it's just incredibly clean and fast. CM12.1 had intermittent micro-freezes/lags that were driving me a little nuts and MOAR is really smooth and quite fast. I was pretty disappointed in CM as I had it a long time ago on an original DInc (7.2!).
Anyway, if you're phone is bricked, keep on fighting the good fight.
I have a Verizon GS5 that has been towelrooted on 4.4.4 for close to 2 years. It's worked ok, but I've started seeing various issues that required a factory reset. Since I'm back to no settings, I was thinking updating the OS would be a good idea. I would like to move to either Lollipop or Mashmallow but it looks like the latter may be a problem with my phone (CID 11 and Verizon) while keeping Knox 0x0.
I'm having a problem following the guide that I've found here:
https://www.androidinfotech.com/2016/07/root-samsung-galaxy-s5-sm-g900v-verizon.html
The issue is that I can't get the phone to connect to my PC for Kies or ODIN. It fails to load the MTP driver for my GS5 but works fine with my wife's GS5. Hers is stock Lollipop or Marshmallow and mine is still on JB but is rooted.
I guess what I'm wondering is what my options are. Should I remove root so that I can hopefully connect to the PC to transfer the files over and updating? Or, is there something else I should try first? I haven't worked on many phones and I'm a little nervous about doing something irreversible at this point. I don't know that I need Knox at 0x0, but since I can't get back if I trip it, I'd rather not trip it.
bkenobi69 said:
The issue is that I can't get the phone to connect to my PC for Kies or ODIN. It fails to load the MTP driver for my GS5 but works fine with my wife's GS5. Hers is stock Lollipop or Marshmallow and mine is still on JB but is rooted.
I guess what I'm wondering is what my options are. Should I remove root so that I can hopefully connect to the PC to transfer the files over and updating? Or, is there something else I should try first? I haven't worked on many phones and I'm a little nervous about doing something irreversible at this point. I don't know that I need Knox at 0x0, but since I can't get back if I trip it, I'd rather not trip it.
Click to expand...
Click to collapse
Try to dial *#0808# in the stock phone application.
You should see a menu with several options.
Select "MTP+ADB" under USB settings and press "OK".
Then you'll be able to connect your phone via MTP or ADB to your PC.
If there's no menu, then (assuming you're rooted) open a good file browser (ES, Root Explorer or something) and open the file /efs/carrier/HiddenMenu (it's a simple text file) and replace OFF with ON there.
Save the changes and reboot the phone.
Now the menu should be operational.
Unfortunately, I already tried to update to 6.0.1 so this very helpful info is a little to late.
I followed all directions on the linked page above but didn't get things working. I repeated 2 or 3 times now and I'm clearly missing something. I can get through installing busybox, but then when I reset, it hangs at the samsung screen and just vibrates 3 times repeatedly. I'm going to have to figure this out tonight as I don't really have a backup phone.
bkenobi69 said:
Unfortunately, I already tried to update to 6.0.1 so this very helpful info is a little to late.
I followed all directions on the linked page above but didn't get things working. I repeated 2 or 3 times now and I'm clearly missing something. I can get through installing busybox, but then when I reset, it hangs at the samsung screen and just vibrates 3 times repeatedly. I'm going to have to figure this out tonight as I don't really have a backup phone.
Click to expand...
Click to collapse
Currently root is impossible for MM on G900V CID11.
Impossible means you cannot gain it now, most likely it's forever.
There's no internet site which can help.
You must choose: root on LP or unrooted MM.
You must decide if you want a stock ROM or something (TW-based) else too.
It's a good idea to flash and use a stock firmware for the time while you're thinking.
Interesting... I guess I must have been reading things wrong because I thought I could go to MM with root. I'll try going to Lollipop then but first I'm going to just flash back to JB 4.4.4.
I downloaded 4.4.4 from Samsung and was going to write it with Odin, but it says FAIL when I try to flash. I suspect I just tripped Knox...
SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
I'll look around to find a guide, but if you have a suggestion, I'd certainly listen!
bkenobi69 said:
SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
Click to expand...
Click to collapse
This means that you've upgraded your phone's firmware while experimenting.
Now you cannot directly flash 4.4.4 with Odin, you're limited to 5.0 (BOK3) and above.
Ok. I'll read the guides on the head of this list and see if I can find the right information.
FWIW, I was following the same how-to that most of the stickies point to and say is safe. I wonder how I got to a position that I'm in now when I did the same as recommended. Painiac's thread points to the same thing I did:
https://forum.xda-developers.com/ve...al/guide-painiacs-essential-guide-to-t3319848
I think I may have tried to flash a MM stock rom though when it got into a boot loop. I suspect that would be the issue.
Bootloop is not a problem in this case.
Just reboot to the recovery and perform a factory reset from there.
The phone will boot but the first boot will take 10-15 min.
bkenobi69 said:
I have a Verizon GS5 that has been towelrooted on 4.4.4 for close to 2 years. It's worked ok, but I've started seeing various issues that required a factory reset. Since I'm back to no settings, I was thinking updating the OS would be a good idea. I would like to move to either Lollipop or Mashmallow but it looks like the latter may be a problem with my phone (CID 11 and Verizon) while keeping Knox 0x0.
I'm having a problem following the guide that I've found here:
https://www.androidinfotech.com/2016/07/root-samsung-galaxy-s5-sm-g900v-verizon.html
The issue is that I can't get the phone to connect to my PC for Kies or ODIN. It fails to load the MTP driver for my GS5 but works fine with my wife's GS5. Hers is stock Lollipop or Marshmallow and mine is still on JB but is rooted.
I guess what I'm wondering is what my options are. Should I remove root so that I can hopefully connect to the PC to transfer the files over and updating? Or, is there something else I should try first? I haven't worked on many phones and I'm a little nervous about doing something irreversible at this point. I don't know that I need Knox at 0x0, but since I can't get back if I trip it, I'd rather not trip it.
Click to expand...
Click to collapse
Marshmallow can not be rooted on CID 11 devices. The Samsung drivers are found here: https://www.samsung.com/us/support/owners/product/galaxy-s5-verizon You can follow the 5.0 root guide here: https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529 to downgrade to 5.0. If you want to downgrade past that to a version lower than 5.0, you will still have to follow that guide then follow the instructions here (I recommend you to follow the root guide for 5.0 above then skip steps 1 and 2 on this page): https://forum.xda-developers.com/ve.../guide-downgrade-to-kk-nk2-ncg-mm-lp-t3686858 . You can find stock firmwares here: https://forum.xda-developers.com/showthread.php?t=2784880 (stock firmware, kernel, and modem files) and if you get bootlooped or bricked, just reflash the combination file from the root guide. If you want to root 4.4.4, follow the downgrade method using all of the NK2 files but the flash the NGC kernel, run through the setup, then use towelroot and flash the NK2 kernel after that. If you ever get stuck on the red Verizon screen, just pop the battery out and reboot.
That's about all anyone can do and a run down of everything.
Thank you for posting specific guides. I'll go back to step 1 and try again. The primary issue I have at this point isn't reading the guide and following directions, its finding the right guide to reduce the number of images I need to download. I'm on 1.5mbps DSL so d/l a 2GB file takes most of a day. I have several that don't appear useful at this point which means I've lost several days.
bkenobi69 said:
Thank you for posting specific guides. I'll go back to step 1 and try again. The primary issue I have at this point isn't reading the guide and following directions, its finding the right guide to reduce the number of images I need to download. I'm on 1.5mbps DSL so d/l a 2GB file takes most of a day. I have several that don't appear useful at this point which means I've lost several days.
Click to expand...
Click to collapse
Understandable, I can't believe it is 2018 and we still haven't invented a way to compress 1.7GB into 1.7MB archives to make life easy on low connections. How is battery life on 4.4.4 and which update of 4.4.4 are you on? I've been having an issue with my phone dropping a percent every 2 minutes on 5.0/6.0. It would be nice find a version to root along with excellent battery life.
The reason I was looking at updating was due to battery issues. I had the phone for around a week before I rooted it (a couple years ago). After rooting, I started seeing immediate battery issues. My wife has the same unrooted phone (currently on MM) and has never had the type of issues I have. I figured the issue was likely a bad kernel and was thinking I'd just update to something newer (LL or MM) to help. I assume a new battery would help since mine is 1-2 years old, but I swapped with my wife's phone and she still gets lots better performance. Once I get this back up, I'll probably buy a new battery for each phone.
So it appears that I must have upgraded the bootloader to a point where towelroot no longer works as was previously suggested. I believe then that I need to follow the second guide to be able to downgrade to a rootable Lollipop version:
https://forum.xda-developers.com/ve.../guide-downgrade-to-kk-nk2-ncg-mm-lp-t3686858
I am downloading the PB1 rom and lolliroot and need to also get a system restore, kernel, and modem. As I said, my connection is terrible so it would be great if someone could suggest which version of restore I should go with. I was going to install Lollipop in the end (that was the original goal). I figured I'd just get OC4 since it's likely to have the least bugs and best performance. If that is a mistake and I should go with an earlier version of LL PLEASE throw it out there!
Ok, I tethered to my wife's phone and am burning her data (shhhh, don't tell her).
I grabbed all of the OC4 files, the PB1 rom, and lolliroot. I think I have everything I need so long as OC4 is a good place to end up.
bkenobi69 said:
The reason I was looking at updating was due to battery issues. I had the phone for around a week before I rooted it (a couple years ago). After rooting, I started seeing immediate battery issues. My wife has the same unrooted phone (currently on MM) and has never had the type of issues I have. I figured the issue was likely a bad kernel and was thinking I'd just update to something newer (LL or MM) to help. I assume a new battery would help since mine is 1-2 years old, but I swapped with my wife's phone and she still gets lots better performance. Once I get this back up, I'll probably buy a new battery for each phone.
So it appears that I must have upgraded the bootloader to a point where towelroot no longer works as was previously suggested. I believe then that I need to follow the second guide to be able to downgrade to a rootable Lollipop version:
https://forum.xda-developers.com/ve.../guide-downgrade-to-kk-nk2-ncg-mm-lp-t3686858
I am downloading the PB1 rom and lolliroot and need to also get a system restore, kernel, and modem. As I said, my connection is terrible so it would be great if someone could suggest which version of restore I should go with. I was going to install Lollipop in the end (that was the original goal). I figured I'd just get OC4 since it's likely to have the least bugs and best performance. If that is a mistake and I should go with an earlier version of LL PLEASE throw it out there!
Click to expand...
Click to collapse
Here are some files (that I been hunting for about an hour for). Just gonna reference this for future use and anyone who comes across this thread. http://rootjunkysdl.com/files/?dir=Galaxy S5
Nice find!
I have the phone up and running on stock PB1 currently. I'm going to let it sit to see what the battery is like prior to rooting. While I haven't gotten it hooked back up to my account yet nor do I have it rooted, I feel pretty confident now that I'm on the right track. Thanks!
Just to finish out this topic, I have not successfully completed attaining root on 5.0. I flashed PB1 to the phone and then followed this guide for installing KingRoot:
https://androidforums.com/threads/root-question.1120150/
I got the lolliroot files from here:
https://www.androidfilehost.com/?fid=312968873555011514
Thanks to all who offered help!
Qyuck question... I've got my phone working well bow, but there's one issue with apps I'm not sure how to address. I want to use Verizon Visual Voicemail but I can't find it on the Play store. I disabled updates so I wouldn't get the marshmallow update and break root. but, with updates turned off, VVM won't get pushed. Any suggestions?