[Q] lollipop broke my phone. I have questions about fixing it. - Verizon Galaxy Note 3 Q&A, Help & Troubleshooting

Verizon Note 3 - SM-N900V - Lollipop 5.0 - OB6
Lollipop pretty much wrecked my phone. Apps crash, wireless turned very sporadic especially when changing hotspots, I've had to pop the battery out of it multiple times now due to it completely freezing, I like using the weather widget but now my GPS locator goes off the grid at times, and battery life is just dead overall with 70-80% spiked battery usage from the OS at 1-2am when I'm sleeping. I've done a full format on my phone to no avail.
That said, I'm new to the game and I've been doing a lot of research on how this all works and have questions/want to do this properly and cleanly. It seems like my 2 options are to:
1. Revert my phone back to 4.4.4 somehow(haven't figured that part out yet), root it, and install JasmineRom 5.0 then dirty flash it to JasmineRom 5.3
2. Leave Lollipop 5.0 on it, buy a nice microSD card (I have a 2gb card but I think it may be too small for JasmineRom), get multisystem running in it from here: http://forum.xda-developers.com/android/software-hacking/tool-multirom-recovery-replacement-t3102395 Then get JasmineRom on the multisystem setup and boot to that.
I would prefer option 1 honestly and any advice would be appreciated. Thanks!

Grotick said:
Verizon Note 3 - SM-N900V - Lollipop 5.0 - OB6
Lollipop pretty much wrecked my phone. Apps crash, wireless turned very sporadic especially when changing hotspots, I've had to pop the battery out of it multiple times now due to it completely freezing, I like using the weather widget but now my GPS locator goes off the grid at times, and battery life is just dead overall with 70-80% spiked battery usage from the OS at 1-2am when I'm sleeping. I've done a full format on my phone to no avail.
That said, I'm new to the game and I've been doing a lot of research on how this all works and have questions/want to do this properly and cleanly. It seems like my 2 options are to:
1. Revert my phone back to 4.4.4 somehow(haven't figured that part out yet), root it, and install JasmineRom 5.0 then dirty flash it to JasmineRom 5.3
2. Leave Lollipop 5.0 on it, buy a nice microSD card (I have a 2gb card but I think it may be too small for JasmineRom), get multisystem running in it from here: http://forum.xda-developers.com/android/software-hacking/tool-multirom-recovery-replacement-t3102395 Then get JasmineRom on the multisystem setup and boot to that.
I would prefer option 1 honestly and any advice would be appreciated. Thanks!
Click to expand...
Click to collapse
only thing you can do is go back to 4.4.4 , http://forum.xda-developers.com/verizon-galaxy-note-3/general/to-4-4-4-lollipop-t3090936
as of now there is no root for 4.4.4 or 5.0

ncsuwolfs said:
only thing you can do is go back to 4.4.4 , http://forum.xda-developers.com/verizon-galaxy-note-3/general/to-4-4-4-lollipop-t3090936
as of now there is no root for 4.4.4 or 5.0
Click to expand...
Click to collapse
Do you know if there is a step by step guide for this? I read through the forum posts you linked me but all they said is that they did it with Odin and it worked. I'm a scrub when it comes to tinkering with phones because I usually end up selling them on Craigslist and buying new ones or doing trades so I usually keep them stock but I really like this phone. Once again any information would be appreciated. I'm going to dig around XDA a bit more to try and find one specific to my phone.

I can write one if you like, but their are step by steps on using odin. I used Odin 3.09 along with NK1 firmware from sammobile. It's extremely easy. There is a link on here and a few other Android forums tho.
Sent from my SM-N900V using XDA Free mobile app

1. Download Odin 3.09 and NK1
2. Backup applicable data (photos, exports contacts to SD card, or internal storage then move everything onto your PC for now..)
3. Turn phone off, launch Odin on your PC. Put the phone into download mode by holding down volume down and home button. Press power button while holding vol down and home, release when Launching recovery appears. When the phone is in download mode and Odin is open in your computer, connect the two. A blue COM1 should appear and odin should say something roughly along the lines of device connected (language may differ.)
4. The NK1 firmware file you downloaded, check off the AP slot and select it in browse. Make sure the only checkmarks are next to F.Reset time and Auto Reboot!!
5. Flash it. It'll take around ten minutes, then odin will reboot the phone.
The phone will probably bootloop, and that's okay..infact as soon as I saw the Samsung logo then the verizon one after it had restarted i pulled the battery and went into recovery. (with phone off, volume up home+power) and select factory data reset (don't worry, it's already gone anyway!!)
This will put you back on NK1. When and if you get the update nag, select 'no thanks.'
Download links
Odin 3.09: http://androidhost.org/PVAIv
4.4.4 VZW Build NK1 (second one down) http://www.sammobile.com/firmwares/database/SM-N900V/
Do not trash to flash any other firmware, it has been blacklisted..and NK1 will probably be blacklisted after the next update to the Note 3. I don't know why it wasn't in the firstplace..

Related

Note 4 Stuck in Boot Loop - Help - Recovery not working - Flash stock Rom not working

Note 4 Stuck in Boot Loop - Help
I have a Note 4 SM-N910F, never been rooted, stock rom upgraded to 5.1.1 back in October, working fine until yesterday when it got stuck in a Boot loop.
Not sure what caused it but before it got stuck I was messing around with Google Photos which was running a bit slow.
Also I put it on the Qi Charger just before the loop started. It has an aftermarket Fone charger stuck to the battery. I’ve had this and the Qi Charger for 6mths with no problems before now.
It gets to the Samsung page waits a couple of seconds then boots again.
Here’s what I’ve tried - unsuccessfully - to fix the boot loop:
1: recovery mode.
I can get the little recovery text to appear in the top left but after a few seconds it boots again.
2: volume down, home
This gets me to the screen with up/down for continue/cancel.
This is the _only_ screen I can get to stay up without rebooting. It sits there waiting for input.
- Cancel, causes restart, of course, but back into the bootloop
3: Mashing on power button. Banging it, wiggling it, blowing on it.
I read somewhere this could cause a boot loop, but I doubt it is my case because
a. I’ve never had problems with the power button before
b: When I take out the battery and put it back in, it does NOT turn on. If I do the same holding the power button, it powers into the boot loop. So if the button were jammed on I would expect it to never remain off with the battery in.
3: flashing stock rom
I’m not 100% sure what build I had before. I know it was stock 5.1.1 OTA, and I’m pretty sure it was unlocked (my wife bought the phone and i inserted my old sim, but she may have bought it from my carrier and can’t remember)
So anyway I tried all three versions of TPH (unlocked) 5.1.1 from Sammobile.
Installed Odin 3.10.7 and flashed them.
It reboots to recovery but immediately boot loops again.
I doubt its to do with the version of the rom anyway since the symptoms are identical after flashing. Only now the boot loop always shows the little ‘recovery booting...’ text in the top left.
Here’s what I have NOT tried but am thinking about:
A: Re-partition option in Odin
B: Nand Erase All option in Odin
C: Buying a new battery.
On A/B: as far as I can tell what I have done so far should have left the data intact. I’m prepared to wipe all my data if it fixes my phone (no lectures about backups please!) and I’m tempted to do one of these on the off chance that the problem is caused by data or the “disk" problems.
But I don’t want to brick it. Can someone recommend how likely these are to help
And what they actually do?
(Please refrain from responses I see elsewhere like “this will brick your phone if you don’t know what you’re doing”. I don’t know what I’m doing, thats why I’m asking - just the facts please)
On C: the battery seems ok in that the power is solid even after not being plugged in for a long time, but since it was on the Qi Charger with that aftermarket thing stuck to it when it happened, I’m suspicious. Can any one say if this is a likely cause?
If so, it might be worth waiting till I get a new batter before doing A or B (can I wait days for Amazon!?)
[UPDATE] Got a new (genuine) battery at a local electronics store. No dice. Same problem, so it's not the battery. Shall I go ahead and re-partition.
[UPDATE] Got a PIT file from another forum, and flashed again with re-partition checked and PIT loaded. same results.
Is Nand-rease worth trying?
The phone is still under warranty so maybe I can return it.
But in that case I want to erase what's on it first.
thanks for any help
rhubarb
I don't think that the Samsung service center will accept cuz u have unofficiall custom
Simple Go to ur any nearby SOFTWARE ENGINEER may be he will help u out
Even I had the same problem with my NOTE 4 EDGE
Try downloading and flashing any "COJ5" build of 5.1.1 from sammobile. Samsung has recently issued a new update "COJ5" it basically locks down the bootloader and will not allow the device to run any previous builds.....Maybe your phone updated to COJ5 in the background and then it started messing around because the phone is rooted. Flashing "COJ5" will lock your bootloader and you will not be able to flash 4.4.4 or 5.0.2 but there is nothing to lose when your phone is already pretty much dead?.....ORRR if this is not a software issue then it could be related to hardware maybe the memory of your phone is done. I am not an expert on this but this is just an advice.....i have told you what will happen if u flash coj5 build now its up to you to decide. I would suggest you wait and wait if you are lucky to get a response from an expert and do what they say .......if not then give this a try!
**EDIT** another idea....First flash a custom recovery such as TWRP....see if it lets you boot into recovery and if it does then perform all sorts of formats.....and factory resets in there see if it works....if its still rebooting after format then flash the coj5 build of 5.1.1....note that you "MUST" format it with TWRP first and then check if its working because once you have coj5...it might not let you flash custom recoveries.
dork997 said:
Try downloading and flashing any "COJ5" build of 5.1.1 from sammobile. Samsung has recently issued a new update "COJ5" it basically locks down the bootloader and will not allow the device to run any previous builds.....Maybe your phone updated to COJ5 in the background and then it started messing around because the phone is rooted. Flashing "COJ5" will lock your bootloader and you will not be able to flash 4.4.4 or 5.0.2 but there is nothing to lose when your phone is already pretty much dead?.....ORRR if this is not a software issue then it could be related to hardware maybe the memory of your phone is done. I am not an expert on this but this is just an advice.....i have told you what will happen if u flash coj5 build now its up to you to decide. I would suggest you wait and wait if you are lucky to get a response from an expert and do what they say .......if not then give this a try!
**EDIT** another idea....First flash a custom recovery such as TWRP....see if it lets you boot into recovery and if it does then perform all sorts of formats.....and factory resets in there see if it works....if its still rebooting after format then flash the coj5 build of 5.1.1....note that you "MUST" format it with TWRP first and then check if its working because once you have coj5...it might not let you flash custom recoveries.
Click to expand...
Click to collapse
You can flash TWRP through ODIN while on COJ5 bootloader. It's locked but you still can flash recoveries and kernel and 5.1.1 ROMS
I am very interested in this thread. I have the EXACT same problem as you have after installing SimplRom, which was a ROM prior to COJ5. It could indeed be that our bootloaders are locked now?
I am using the N910F and just like you, installing any ROM/Custom Recovery/Bootloader/Kernel doesn't help. Perhaps installing a COJ5 ROM might help. I will give that a try, but I've recently used Kies to install the latest official firmware, but it didn't fix the issue.
I will report back here and we'll work on this together to make our phones work again!
Osama lakdawala said:
I don't think that the Samsung service center will accept cuz u have unofficiall custom
Simple Go to ur any nearby SOFTWARE ENGINEER may be he will help u out
Even I had the same problem with my NOTE 4 EDGE
Click to expand...
Click to collapse
Thanks but:
1: I have no custom rom. I have never had a custom rom on this device. I want to take it to Samsung, but want to clear the memory first. How can I do that?
2: I _am_ a software engineer_
dork997 said:
Try downloading and flashing any "COJ5" build of 5.1.1 from sammobile. Samsung has recently issued a new update "COJ5" it basically locks down the bootloader and will not allow the device to run any previous builds.....Maybe your phone updated to COJ5 in the background and then it started messing around because the phone is rooted. Flashing "COJ5" will lock your bootloader and you will not be able to flash 4.4.4 or 5.0.2 but there is nothing to lose when your phone is already pretty much dead?.....ORRR if this is not a software issue then it could be related to hardware maybe the memory of your phone is done. I am not an expert on this but this is just an advice.....i have told you what will happen if u flash coj5 build now its up to you to decide. I would suggest you wait and wait if you are lucky to get a response from an expert and do what they say .......if not then give this a try!
**EDIT** another idea....First flash a custom recovery such as TWRP....see if it lets you boot into recovery and if it does then perform all sorts of formats.....and factory resets in there see if it works....if its still rebooting after format then flash the coj5 build of 5.1.1....note that you "MUST" format it with TWRP first and then check if its working because once you have coj5...it might not let you flash custom recoveries.
Click to expand...
Click to collapse
Thanks to you and dork97 for the ideas. First some notes:
- I have never flashed a custom ROM, nor ROOTed this Note 4. The recent upgrade to 5.1.1 was official.
the first upgrade to 5.0.1 was automatic and after that I turned off automatic upgrades and upgraded to 5.1.1. manually. So I dont think it was an upgrade that caused it and it certainly was NOT a custom ROM or ROOT. I was doing nothing at all when the boot loop started.
- I'm not sure what ROM I had, but when I went looking for the available Portugal unlocked ROM, which _should_ be what I had, the latest were CJ03 (3, not 5) and before that CH03, CI03. Presumably I had one of those (my last update was October, so probably CH03).
I have tried all 3 of these, but the symptoms are the same.
I'm tempted to try the TWRP option - but would like some more details on what is and what it does, or what problem I might have that it would fix.
However I am probably still in time for a warranty repair - especially since I didnt actually do anything for this to happen. I would like to avoid losing that chance.
If I do take it in for warranty, I'd like to wipe the memory first though. How can I do that?
Finally can anyone actually tell me if the NAND ERASE is likely to help? How does flashing TWRP compare?
I get the feeling in fact, that I have a hardware problem. Especially given there were not software system changes around the time it happened, and given that it loops while trying to boot into recovery mode. In fact the only mode that doesnt constantly cycle is download mode. (Even holding the power button in dl mode does nothing which makes me suspect that, but pulling the battery out and replacing it leaves it off until I press the power button so perhaps not)
Thanks for the replies so far. Any more ideas, details?
roverrhubarb said:
I get the feeling in fact, that I have a hardware problem. Especially given there were not software system changes around the time it happened, and given that it loops while trying to boot into recovery mode. In fact the only mode that doesnt constantly cycle is download mode. (Even holding the power button in dl mode does nothing which makes me suspect that, but pulling the battery out and replacing it leaves it off until I press the power button so perhaps not)
Click to expand...
Click to collapse
I have the exact same as you. I did install a custom recovery (multiple) and still get the bootloop. From my tries yesterday, I indeed also suspect it may be a hardware issue. Perhaps to do with the battery/charging port. When I have my device unplugged and try to start in recovery/normalboot, it does not have a bootloop but simply turns off (and then doesn't respond until I pull the battery out). I think a NAND erase wouldn't do anything as I've personally tried that already.
Have you prior (upto a week) before you got the issues had your phone in a moist environment (bathroom while showering for example). I got my problems a week after I accidentally left my phone in the bathroom and installed custom ROM (which was done earlier and had no issues).
I've read online that it may have caused oxidation on the inside and may need some cleaning/drying with alcohol.
I still hold hope that we just have a software issue as download mode is working fine (apart from the Power off not working unless we pull out the battery).
Anybody have any experience with oxidation on their phone? Perhaps have had a similar bootloop due to hardware failure?
roverrhubarb said:
Thanks to you and dork97 for the ideas. First some notes:
- I have never flashed a custom ROM, nor ROOTed this Note 4. The recent upgrade to 5.1.1 was official.
the first upgrade to 5.0.1 was automatic and after that I turned off automatic upgrades and upgraded to 5.1.1. manually. So I dont think it was an upgrade that caused it and it certainly was NOT a custom ROM or ROOT. I was doing nothing at all when the boot loop started.
- I'm not sure what ROM I had, but when I went looking for the available Portugal unlocked ROM, which _should_ be what I had, the latest were CJ03 (3, not 5) and before that CH03, CI03. Presumably I had one of those (my last update was October, so probably CH03).
I have tried all 3 of these, but the symptoms are the same.
I'm tempted to try the TWRP option - but would like some more details on what is and what it does, or what problem I might have that it would fix.
However I am probably still in time for a warranty repair - especially since I didnt actually do anything for this to happen. I would like to avoid losing that chance.
If I do take it in for warranty, I'd like to wipe the memory first though. How can I do that?
Finally can anyone actually tell me if the NAND ERASE is likely to help? How does flashing TWRP compare?
I get the feeling in fact, that I have a hardware problem. Especially given there were not software system changes around the time it happened, and given that it loops while trying to boot into recovery mode. In fact the only mode that doesnt constantly cycle is download mode. (Even holding the power button in dl mode does nothing which makes me suspect that, but pulling the battery out and replacing it leaves it off until I press the power button so perhaps not)
Thanks for the replies so far. Any more ideas, details?
Click to expand...
Click to collapse
Well if you still have warranty then don't try anything on your own and go for the warranty repairs.
dork997 said:
Well if you still have warranty then don't try anything on your own and go for the warranty repairs.
Click to expand...
Click to collapse
thanks. How can I wipe personal data without voiding the warranty, using odin or kies? Given I canNOT get it into recovery mode, only download mode.
roverrhubarb said:
thanks. How can I wipe personal data without voiding the warranty, using odin or kies? Given I canNOT get it into recovery mode, only download mode.
Click to expand...
Click to collapse
Since you can get into download mode I'd flash firmware through ODIN again after verifying it's correct.
I'm seeing off the sammobile site for the 910F not all are the COJ5 locked bootloader.
Since you did update in Oct you may be on the COJ3. I'd try one of those and see if it works.
If it doesn't work and stops on the sboot.bin file then you have the COJ5
roverrhubarb said:
thanks. How can I wipe personal data without voiding the warranty, using odin or kies? Given I canNOT get it into recovery mode, only download mode.
Click to expand...
Click to collapse
i am sorry i don't know any way to remove personal data other than doing it via recovery. There is an option of "nand erase" in odin it is used while flashing firmware and it wipes everything on the phone but i have never used it (and also don't know whether it can help you or not) ... Senior members kindly help us with this.
Any update to your situation?
very interested as I am in the same situation as you are. Download mode works, recovery+normal boot not. No matter what ROMs/recoveries I install
Same issue I think
I am also in the same situation, although I can enter the recovery mode - home power and volume up - I have tried the wipe cache and then factory wipe to no avail - I have also entered download mode and flashed the stock recovery and even though Odin says pass, it is still in a boot loop. Also when I go to the download screen it has a line saying knox warranty void 0x1(4) does this mean I have voided the warranty even though I only used Odin to flash stock recovery?
Did anyone found a solution
Did anyone ever found a solution to this problem I'm having the exact same issue on a note 4 smn910a
I have a slightly different issue with my Note 4 SM-N910G, wherein am not able to start the phone at all, it is completely dead, if i put the cell phone on charge then also there is no LED on the top but if i connect the device to the PC it does make the connected sound on the PC but Odin is still not able to recognize the device neither kies. I tried draining the power by removing the battery, connected the device to PC without battery and then inserting it but the same problem. Please suggest me any resolution for this dead body am carrying from past few weeks.
hi Op,
did you find any solution for this issue?
Hello all. This is advice to use as a very last resort if you are experiencing the recovery bootloop issue AND you don't have the emmc failure bug. I had the recovery reboot, sudden shutdown with no warning, etc. issue for the past two weeks. I tried everything on Google and Youtube to fix my problem with no success. I flashed multiple stock ROMS and recovery tars (stock and TWRP) via ODIN, but nothing worked. Oddly enough, I never received the emmc error that I have read about. Also, in the few times that my phone booted normally, I even loaded the Wakelock Power Manager app, set it to partial wakelock and my phone STILL continued to bootloop. As a last resort, I bought a new battery, but the reboot problems continued in Android 4.4.4 Kitkat, 6.0 Marshmallow, 7.1 Nougat and 8.1 Oreo ROMS. Well, here is what finally helped me to get my phone back operational. I had a backup ROM from a previous install and a TWRP flashable version of the same ROM on my SD card (in case the phone did not stay on for the full restore). I put the phone into a ziplock bag into a freezer for about 20 min. (thankfully this time TWRP stayed on long enough for me to do the following):
1) copy all the files I wanted to save from internal storage to a computer.
2) performed a full wipe (Dalvic, Cache, System, etc. Like when flashing a ROM, but this time also internal storage. Note: Please do not wipe both internal and SD card, as you may have a difficult time trying to load the ROM file back on the sd card (assuming you don't have a card reader).
3) After wiping, I was able to restore my stock ROM backup (or you can just flash the stock ROM).
I can't be 100% sure, but I think my wiping internal and then flashing the stock ROM finally did the trick. Since this morning, the phone has been pretty much back to as it was before. In either case, I'm sharing this with the hope that it helps someone else.
Sent from my SM-N910T using Tapatalk

Oops-a-daisy (flashed wrong version of stock rom)

I wanted to root my Galaxy Note 4 (SM-N910F UK carrier H3G) so I could use the mirroring option in Airdroid.
Long story short, I'm severely disabled so wanted full access to my phone whilst on my pc, without struggling to get my phone all the time. (SWTOR Security Key is one of the many reasons for wanting to not have to grab my phone every time I need to do something on it)
(I can't put phone where it's easily accessible whilst on pc, because of the board I use for keyboard and mouse rested across the arms of my chair)
I THOUGHT I had it sussed, as I had successfully rooted and booted my S3, S4 and Note 2, 3 and 8.0 devices.
However, I didn't read the fine print when using CF-autoroot in that it doesn't work on 5.1.1 atm. Or something along those lines...
Anyway, with my usual eagerness and impatience to do geeky/nerdy deeds, I ended up with my phone in a constant boot loop no matter what I tried.
I scoured the Internet for 3 hours, trying to find the original stock rom for my device and was livid that my usual Google-Fu was failing miserably.
I found one, so I thought, installed the kernel, (couldn't find stock kernel either) installed SuperSU, installed Twprs or whatever it is, (excuse my lack of knowledge please) then installed this "stock" rom.
Turns out it possibly IS the H3G network's Stock Note 4 (SM-N910F) ROM. IF I lived in Italy.
I still would like root access on my phone, but I would like to try and get stock rom back, or something EXCEPTIONALLY similar.
Please, again, excuse my apparent thickness... (and I'm not talking sliced bread here) is it the kernel where rooting takes place, the ROM, or do both have to be involved in the adaptation?
I know very very little about Linux and kernels etc.
I hope that I have described my predicament clearly, and that when one has picked oneself up off the floor from rolling around with much merriment, one (anyone) is able to assist with my screw up.
Best wishes,
(Applebogies for waffling on more than the meat content of a Belgian Blue, (I'm not talking Blue Waffle, but of four legged animals that chew the cud)
(Applebogies also for mentioning The Waffle of Blue-ness in more than one sense of the word, if it makes you Google it and you only just ate and you've never seen it before)
(Finally, applebogies for my rotten and feeble attempts humour, please try to cut through my crap and get to the point ofwhat my conundrum actually is)
So basically in a nutshell, you've bricked your phone? I do know that when I flashed stock ROM the other day, I had to pull the battery, boot into recovery (vol up + home + power) and wipe data/factory reset and wipe cache too. Then it booted just fine try that.
you can find different stock roms for your phone at sammobile (google it) download the firmware from there and flash it with odin. Watch youtube videos on how to flash firmware with odin. its simple
See if you can boot the phone into Download Mode via volume up+home+power. If it boots into download mode that means its not hard bricked. If it doesnt boot into DL the first time you try, do a battery pull for 15-20 seconds, then try again. If that doesnt work, then check your specific device versions forum for an unbrick method, and check for a general unbrick that can be used for all N4's.
If it does boot into download mode, download the stock firmware for your specific N4, flash it via Odin, (instructions are generally included in the thread where you find the stock ROM download) and you should be good to go after that.
Edit: SamMobile does indeed have a firmware for your specific device. Do a google search for sammobile, go to that site, and input SM-N910F into the device search bar. That will take you to a page with a list of firmwares. Theres a list box where you can select your country, that includes country and carrier combinations. Yours will be listed as United Kingdom (H3G)(H3G). Select firmware with PDA version N910FXXU1COJ3.
Not sure why you all think my phone is bricked, I am on it now?
I am however, currently running the Italian version of 3 mobile rom. Looks like asrah has solved that problem though xD
To shorten my previous post:
Where does root happen, on kernel or rom?
Ie - can I have stock rom but still have root access on my phone?
Thank you to asrah for finding my rom.
Thanks all and a very Merry Christmas!

Successful Recovery Note7 from last Samsung "Death Update" Disabled Battery Charging!

Successful Recovery Note7 from last Samsung "Death Update" Disabled Battery Charging!
Ok, so here it goes, Im getting one more piece of Note7, addictive, I know... this piece has latest samsung's "Death Update" installed, thus its reportedly only working while plugged in with usb cable or charger but otherwise does not charge battery anywhere beyond 0%... so thats that.
My goal is to root this unit, and install custom rom (like hydra rom) and after probably reflash with ODIN with earlier version that did not have battery charging @ 0% cap , then again root the phone, install root package blocking program and just run stock rooted rom with updates disabled, thus having battery charging feature enabled. Ultimately my options of course are to attempt retrofit another battery to it like one discussed here in this thread:
https://forum.xda-developers.com/note-7/themes/note7-battery-swap-mod-note5-s6-s7e-t3545371
, since the model Im receiving has no warranty and it is already refunded unit to the original owner but was "written off" by samsung or whatever you call it, I dont care as long as I get it, I know me trading it in for S7e even aint an option so its going to be my test-unit for DIY and such.
Im wondering would charging features still be disabled if phone was powered via Download / Recovery modes? Anybody had first hand experience? Otherwise, is there anything else in place after the latest death update that prevents phone from being rooted and alternatively flashed with custom recovery/rom to enable charging?
Mega curious...
Hope ya'll having great weekend people
Mr.Ultimate said:
Ok, so here it goes, Im getting one more piece of Note7, addictive, I know... this piece has latest samsung's "Death Update" installed, thus its reportedly only working while plugged in with usb cable or charger but otherwise does not charge battery anywhere beyond 0%... so thats that.
My goal is to root this unit, and install custom rom (like hydra rom) and after probably reflash with ODIN with earlier version that did not have battery charging @ 0% cap , then again root the phone, install root package blocking program and just run stock rooted rom with updates disabled, thus having battery charging feature enabled. Ultimately my options of course are to attempt retrofit another battery to it like one discussed here in this thread:
https://forum.xda-developers.com/note-7/themes/note7-battery-swap-mod-note5-s6-s7e-t3545371
, since the model Im receiving has no warranty and it is already refunded unit to the original owner but was "written off" by samsung or whatever you call it, I dont care as long as I get it, I know me trading it in for S7e even aint an option so its going to be my test-unit for DIY and such.
Im wondering would charging features still be disabled if phone was powered via Download / Recovery modes? Anybody had first hand experience? Otherwise, is there anything else in place after the latest death update that prevents phone from being rooted and alternatively flashed with custom recovery/rom to enable charging?
Mega curious...
Hope ya'll having great weekend people
Click to expand...
Click to collapse
Not sure why you think that retrofitting a battery would allow the device to charge. The update on your device is what is preventing the charge cycle and also is stopping the device from using any radios.
You need to try to flash via Odin a complete rom, probably the last version that had the battery limited.
If you can manage this then you should be disable oem unlock under developer options and then install hydra by following the detailed instructions.
clearbox said:
Not sure why you think that retrofitting a battery would allow the device to charge. The update on your device is what is preventing the charge cycle and also is stopping the device from using any radios.
You need to try to flash via Odin a complete rom, probably the last version that had the battery limited.
If you can manage this then you should be disable oem unlock under developer options and then install hydra by following the detailed instructions.
Click to expand...
Click to collapse
Battery retrofitting mod is not to get battery charging - is to keep note7 fail-proof, and with this specific unit that Im talking about it is especially the case only after getting it back to firmware that did not have it bricked.
I know about "OEM unlock" feature in dev mode is a must before any software tampering, so thats not an issue. I am aware phone works while on cable, so I should be able to navigate and activate OEM Unlock from dev menu, also I should be able to do straight ODIN flash with firmware that is of an earlier version without any battery cap's , so my question still remains - is there anything in this latest deadly update from samsung that prevents ODIN from flashing anything to the phone, or is it just charging orientated?
we shall all see once it comes across, should be following week, Im actually eager to start working with it. May as well just go ahead and order myself a S7 battery too so less time to waste waiting
I have a Note 7 that's on the "Death update".
1) Phone cannot be charge in normal mode or download mode.
2) I did not check on whether it could still function with a cable plug in.
3) Attempting to flash older Samsung firmware from ODIN will not work. It will give some errors and stop there.
4) Could not flash anything through ODIN. BL, CSC, CP, AP could not be flash into the phone.
5) Could not flash recovery from ODIN either.
6) Enabling OEM unlock doesn't help in anything. See point 3 and 4 above.
Hope the above helps.
teslapolaris said:
I have a Note 7 that's on the "Death update".
1) Phone cannot be charge in normal mode or download mode.
2) I did not check on whether it could still function with a cable plug in.
3) Attempting to flash older Samsung firmware from ODIN will not work. It will give some errors and stop there.
4) Could not flash anything through ODIN. BL, CSC, CP, AP could not be flash into the phone.
5) Could not flash recovery from ODIN either.
6) Enabling OEM unlock doesn't help in anything. See point 3 and 4 above.
Hope the above helps.
Click to expand...
Click to collapse
Vey well, I have some extra ideas too, we shall see
Besides, what are your current plans for your note7?
are you willing to sell it by any chance?
Mr.Ultimate said:
Besides, what are your current plans for your note7?
are you willing to sell it by any chance?
Click to expand...
Click to collapse
I'm hoping to revive the Note 7 and use it if this is possible at all.
Won't mind selling if there are no other option.
Ok, so got my disabled charging note7, it has about 24% battery remaining and it stays this way if I keep it plugged in on USB or on wireless charger.
I tried flashing TWRP both versions available, both had flashed OK with ODIN however, it still has standard recovery...? wtf...
I remember my S7edge did have very similar behavior, odin would flash TWRP just perfectly fine but when going in to recovery on the phone it still starts in standard recovery, and this would continue until I flashed CF-Autoroot IMG.TAR file , but this time I cannot find it anywhere for note7....
Im thinking trying KingoRoot or OneClickRoot tools but I wanna hold back a little before I launch on those.
Ok good news (so far) , flashed custom kernel via ODIN, worked, but now I figured phone takes charge again while phone is off just on USB, so charge disable mode is within latest kernel update only.
I can still enter my standard recovery and do all I want there (havent tried factory reset yet!)
When powered off from recovery, phone began charging! now I have noticed it went from 23% to 24% and it is showing it is charging, where as before it would vibrate for second when plugged in and then show battery symbol which soon after would go offline and phone would be unresponsive like it is not plugged in - in not charging state. So for now 1:0 me vs note7
EDIT!
YESSS! IT IS CHARGING! NOW @ 26%!!!
Now @ 30% ... ok I should let it charge to 50% and then try perform more firmware DIY
ok, I will confess, I could not wait any longer, thought screw this sh*t, went in to recovery and wiped cache/factory reset, rebooted phone, then witness phone startup OK, welcome wizard started OK with 30% on battery and indicator on shows On-charge thought "yess!!!" , then I get this notification about battery is gonna run out and no longer recharge blah blah blah, but hey , it still charges and now Im at 33%
Yes, latest firmware and custom kernel and VIOLA , note7 is back in the game!
Also got this notification from device security thing asking me to reboot phone to try undo the changes... I guess I will not try just yet out of curiosity will try again to do TWRP reflash, this time it should work
Confirmed, now TWRP flash via ODIN worked liek a charm, so I should root via TWRP now and see if I can disable something in current latest software to disable these notifications playing around now
ok now rooted and lots knox stuff disabled with package disabler and etc, still getting this one notification about discharging battery warning when plugged in, anyone could advice me which file to edit in system root to bypass this?
Thanks
Wow, that's great. I've been trying for weeks but unable to get through to anything. Will it be possible to share on how you get to flash TWRP successfully? Thanks
---------- Post added at 12:36 AM ---------- Previous post was at 12:32 AM ----------
Mr.Ultimate said:
ok now rooted and lots knox stuff disabled with package disabler and etc, still getting this one notification about discharging battery warning when plugged in, anyone could advice me which file to edit in system root to bypass this?
Thanks
Click to expand...
Click to collapse
I'm don't know about the editing stuff but if you could get TWRP to work, wouldn't it be simpler to flash custom ROM that already have KNOX etc disabled?
I was disabling all kind of random packages just to see what results will I get from doing it all , was expecting to somehow find package that relates to USB/wireless pad power circuit monitoring so I could work on it while maintaining the latest patched firmware but no nagging popups every time phone is powered on or plugged in to USB/wireles pad. Otherwise I observe phone is 99.99% perfect aside from the notification that I have described and security centre prompts warning time to time that device has been modified , click restart to undo-modification, which I actually tried and it undone-nothing, so it is permanently patched this way regardless what you try to do within the phone now.
I am in favor of keeping stock rom and stock appearance of note7 as much as possible.... dont know if it makes much sense but I love the way note7 is... with all functions working as much as possible as close to standard as much as possible, so thats why my reasoning trying to make this latest rom work.
I have few firmwares which were the original ones V.1 and V.2 but not V.3, which is what I have, so even if I install custom rom now, there is no way going back to factory firmware since V.3 full factory rom is nowhere to be found.
I am going to look in to ways on how to extract entire current firmware so I can go and learn a bit and maybe do few ROM builds myself, this is actually exciting now once I got this far.
Able to link me to the custom Kernel that you use?
teslapolaris said:
Able to link me to the custom Kernel that you use?
Click to expand...
Click to collapse
do it on your own risk folks, I mean - enjoy...
https://www.androidfilehost.com/?w=files&flid=98347
Mr.Ultimate said:
do it on your own risk folks, I mean - enjoy...
https://www.androidfilehost.com/?w=files&flid=98347
Click to expand...
Click to collapse
Thanks. It works!!!. Thank you so much.
I managed to flash TWRP and Hydra ROM onto it. Everything works except mobile network. Somehow it is unable to detect the SIM card.
Will fiddle with it further. Hopefully I could get it up and running.
Thanks again.
only downside I see so far with current latest kill firmware and this patched kernel are those nagging notifications regardless battery charging to 100% ok, security center notification about modifications and about restart with attempt undoing them, which obviously will fail anyway anytime, and just now noticed it takes a little more time to activate wifi to show available networks, usually its instant, like 0.1second, and now its like 3-5 second delay once switch is toggled to ON position. Also, found out that when network sim card inserted, now phone prompts for network customization and asks to restart now or later to apply settings changes, and I tried restarting but this keeps coming on anyway, so finding the service package and disabling it solves this issue.
Besides no any network issues here, signal comes on every time I change sim cards around and all connectivity is there with data and all is OK, maybe try different kernel? I tried one with APO ,mine is European exynos SM-N930F model
I tried out Hydra kernel but it didn't work. Then I found this https://forum.xda-developers.com/note-7/how-to/spacex7-rom-kernel-kill-galaxy-note7-t3536693. I flash it and my SIM card works again.
This may help someone
Hi.
As I've read that there are people in the forum with problems after the last update from samsung, I decided to write my experience.
My first Note 7 was the Hong Kong version. It was amazing, because it had an fm radio built in, but of corse I couldn't flsh a costum rom on it, as there as none in the forum. In time, a gave up and send it to samsung, and I am glad for, since by now, I would have a death phone.
Anyway, after 2 months with a s7 edge, I found a person selling is international note 7, cause he would go to Brasil, and was afraid to had it apprehended at the aeroport. So I bought it, even with the limited charge at 60% problem.
First, I tried the Dr. Keatan rom, but the limited battery charge still persisted.
So I tried the TEKXodus rom, and I say its amazing.
My phone now as the batery charging to 100%, and even the shealth works fine, if you don't update it.
If it as an automatic update by google, just downgrad it and is fine.
When I received the samsung notification for the last update, I just needed to be sure that the update function was turn off, that the processes in the background were off too, and, with titanium backup, to freeze 2 "urgent update" apks.
Everything works fine.
So, for those who have problems, I recommend the TEKXodus rom.
Best regards

Guide to unroot and install Nougat on Galaxy S7

Note - this is for the SM-G930A AKA AT&T model only. Unrooting and flashing firmware works the same way for other carriers, but with different files.
Hi everyone, I just thought I should share how I went about unrooting my S7. I initially rooted it while it was running Nougat already, and I liked the extra customization options. However, I found after several months of using it that the only real feature that I personally liked about having a rooted S7 was the ability to "try" paid apps for free using Lucky Patcher.
The downside of rooting, for me anyway, was severely slow laggy touch inputs and general phone performance. Sometimes - especially after a reboot - I experienced slightly better performance, but overall it just got too annoying. The app that gave me the most trouble was Google Maps. That's why I decided to cut my losses and unroot; I'd figured out which apps I actually wanted to buy since I'd already used them for a while (I will miss free in-app purchases though ).
So after some Googling and reading up, I decided to try for myself. I was already running baseband version G930AUCU4BQA4 before I rooted, so I thought maybe I could just flash stock Nougat and be done. However, all the guides I read say to flash a stock firmware, so that's what I did to be safe.
So first I downloaded the stock firmware for my phone from a website called rootmygalaxy, on the Download Stock ROM For AT&T Galaxy S7/S7 Edge (SM-G930A/SM-G935A) page (being a new user sucks).
After that, I used the stock, unpatched version of Odin v3.12.3, (from Odin's website) to flash the stock firmware onto my phone. It should be noted that the steps you take to flash a firmware to download mode should be 1. Open Odin, 2. Put phone in download mode, 3. plug the phone in. I had some failures in Odin because I was doing that wrong. Steps one and two are probably interchangeable, but just make sure plugging in the phone is the last thing you do. Also, make sure you have ticked USB Debugging and OEM Unlock under developer options before you do any flashing.
Once that was complete, I rebooted my phone and set up Android 6.0.1 on the phone. After a full 24 hours, I still couldn't get any OTA updates, so I decided to manually flash Nougat because it is so much better than Marshmallow.
This guide on the website droidviews called Install Android 7.0 Nougat on AT&T Galaxy S7/ S7 Edge (SM-G930A/ G935A) was very helpful.
Take note of the fact that the guide references baseband versions by the last 4 characters, i.e. G930AUCU4BQA4 becomes just BQA4. I checked my baseband version, which ended in APJ4. According to that guide, all I had to do was flash APK1 and then I'd be set to update to Nougat, so that's exactly what I did.
After again flashing via the 4-file method with Odin, I set up the phone again so I was back at the home screen. I downloaded both the APK1 and the .zip file containing Nougat while my phone was charging (from 90%, my phone was at ~50% by the time I had Nougat up and running), and I placed the .zip Nougat update onto an SD card that I usually keep in the phone. Once APK1 was set up, I put the SD card back in, rebooted into Recovery Mode, and waited until the manual screen came up. Then I simply chose update from SD card, chose the .zip file I'd placed in there, and waited. After a while, I was greeted by a new setup screen. I set up Nougat and now it's running just fine.
The only issue I'm seeing is that I'm still not getting any OTA updates. I hope that doesn't continue, but if it does I can just update via .zip or something.
Thanks for reading!
where did you get the nougat.zip?

GS5 verizon 4.4.4 to rooted marshmallow

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?

Categories

Resources