So been on HD since the beginning and had no issues until today.
Installed rls21 per the OP and everything ran pretty smooth. Was unable to get HD Tweaks to load
and it would cause settings to FC then touchwiz home would FC.
I went into recovery, cleared cache and rebooted. Still had the same issues. Re-installed the rom from
the beginning and still same problem.
Downloaded new copies of rls21 and the UI and installed. Now my phone wont boot past the samsung logo with the lock.
I tried to odin back to stock and it is still stuck at the logo.
I can get into recovery and the download screen but cant get anything to boot after that.
It will let me run aroma and install any build but wont boot the OS.
Seems I've lost root as well.
I'm on an MDK build. Please someone help me figure this out...
Update: Tried re-partitioning and loading stock MDK firmware and also tried to load stock recovery via Odin.
Now I can still get into download mode, phone wont boot past samsung screen and when i try to enter recovery I have the yellow triangle and a statement about unauthorized software...
TJ2713 said:
So been on HD since the beginning and had no issues until today.
Installed rls21 per the OP and everything ran pretty smooth. Was unable to get HD Tweaks to load
and it would cause settings to FC then touchwiz home would FC.
I went into recovery, cleared cache and rebooted. Still had the same issues. Re-installed the rom from
the beginning and still same problem.
Downloaded new copies of rls21 and the UI and installed. Now my phone wont boot past the samsung logo with the lock.
I tried to odin back to stock and it is still stuck at the logo.
I can get into recovery and the download screen but cant get anything to boot after that.
It will let me run aroma and install any build but wont boot the OS.
Seems I've lost root as well.
I'm on an MDK build. Please someone help me figure this out...
Update: Tried re-partitioning and loading stock MDK firmware and also tried to load stock recovery via Odin.
Now I can still get into download mode, phone wont boot past samsung screen and when i try to enter recovery I have the yellow triangle and a statement about unauthorized software...
Click to expand...
Click to collapse
Did you also flash the stock MDK recovery as well? Which package did you flash no wipe or full?
Illogi.xbone said:
Did you also flash the stock MDK recovery as well? Which package did you flash no wipe or full?
Click to expand...
Click to collapse
I flashed pretty much every file I could in odin to restore mdk. Failed to notice all the file sizes on every site I downloaded
from were 8MB or smaller. Am downloading the full 1.83GB MDK system file now to see if that will work.
TJ2713 said:
I flashed pretty much every file I could in odin to restore mdk. Failed to notice all the file sizes on every site I downloaded
from were 8MB or smaller. Am downloading the full 1.83GB MDK system file now to see if that will work.
Click to expand...
Click to collapse
You probably got the MD5 file I have done that before.
So I was unable to Odin back to MDK. Think I lost root and my boot image. I was able to Odin to the newest build fnk1 which is MDF.
Guess I'm gonna figure out this whole safe strap game now :*(
TJ2713 said:
So I was unable to Odin back to MDK. Think I lost root and my boot image. I was able to Odin to the newest build fnk1 which is MDF.
Guess I'm gonna figure out this whole safe strap game now :*(
Click to expand...
Click to collapse
Well good news is HD is good for Safestrap =D
Illogi.xbone said:
Well good news is HD is good for Safestrap =D
Click to expand...
Click to collapse
Yeah but cant get rls 21 to work without tons of fc's. So now im no better than where i started since safestrap blows and i'm back on rls20
TJ2713 said:
Yeah but cant get rls 21 to work without tons of fc's. So now im no better than where i started since safestrap blows and i'm back on rls20
Click to expand...
Click to collapse
You could always go stock rooted until they get SS working with custom kernels. Just sayin.
Illogi.xbone said:
You could always go stock rooted until they get SS working with custom kernels. Just sayin.
Click to expand...
Click to collapse
Been on hyperdrive for almost 2 years. The concept of stock is just gross lol
TJ2713 said:
Been on hyperdrive for almost 2 years. The concept of stock is just gross lol
Click to expand...
Click to collapse
I know the feeling, personally with MDK I prefer lollipop, but I use S Translator all the time now (Dating a Chinese girl) and the optical reader and I have found 0 apps that could compare for free so HD is my DD for now until we get an S4 Lollipop rom with those included.
Related
Hey guys,
I thought I would come here because I have tried all other options besides going to Bestbuy. My Samsung Galaxy S4 model SCH-I545 is currently without an operating system for it seems in the Odin process to flash it back to stock it failed and now I am in quite the bind. I cannot access the stock recovery mode or boot normally. Whenever I boot my phone I get the message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". I'm kinda stuck at this point help would be much appreciated
I can still access Odin mode and the computer still recognizes my phone so that is a plus
Thanks,
Adog115
ADog115 said:
Hey guys,
I thought I would come here because I have tried all other options besides going to Bestbuy. My Samsung Galaxy S4 model SCH-I545 is currently without an operating system for it seems in the Odin process to flash it back to stock it failed and now I am in quite the bind. I cannot access the stock recovery mode or boot normally. Whenever I boot my phone I get the message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". I'm kinda stuck at this point help would be much appreciated
I can still access Odin mode and the computer still recognizes my phone so that is a plus
Thanks,
Adog115
Click to expand...
Click to collapse
Need more info. What version are you on? MDK? ME7?
Sent from my SCH-I545 using Tapatalk 2
heath2805 said:
Need more info. What version are you on? MDK? ME7?
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
I actually followed a different thread and got the correct version ME7 and had a successful flash. All is well right now thanks anyways
What was the correct version of ME7 and where did you get it?
cal0987 said:
What was the correct version of ME7 and where did you get it?
Click to expand...
Click to collapse
Theres a copy of the stock me7 imaged posted here on xda, in the development section.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
ADog115 said:
Hey guys,
I thought I would come here because I have tried all other options besides going to Bestbuy. My Samsung Galaxy S4 model SCH-I545 is currently without an operating system for it seems in the Odin process to flash it back to stock it failed and now I am in quite the bind. I cannot access the stock recovery mode or boot normally. Whenever I boot my phone I get the message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". I'm kinda stuck at this point help would be much appreciated
I can still access Odin mode and the computer still recognizes my phone so that is a plus
Thanks,
Adog115
Click to expand...
Click to collapse
Dog,
What did you do to fix it, specifically?
All, I am having an issue very similar to this, I'm on MJ7 and have the developers unlocked phone. Even thought the bootloader is unlocked the root functionality is not enabled. In trying to achieve root through flashing a file (it failed because of signiture validation error it went into a boot mode where it sounds like it is booting normally but there is no visual indicators and the LED light is a pulsing blue color (don't know what that means). Does anyone know where i can find an original factory firmware file and instructions to flash it successfully? I noticed there are several people in these forums who say they have had luck with a couple of the restore methods yet none have succeeded for me. If this is a developers edition why is the bootloader unlocked but not rooted? Thanks for any help you might be.
ADog115 said:
Hey guys,
I thought I would come here because I have tried all other options besides going to Bestbuy. My Samsung Galaxy S4 model SCH-I545 is currently without an operating system for it seems in the Odin process to flash it back to stock it failed and now I am in quite the bind. I cannot access the stock recovery mode or boot normally. Whenever I boot my phone I get the message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". I'm kinda stuck at this point help would be much appreciated
I can still access Odin mode and the computer still recognizes my phone so that is a plus
Thanks,
Adog115
Click to expand...
Click to collapse
I used the one from Kies
still not working
****s ****ed.
I have a gs4 was on me7 running hyperdrive 9.1. Hyperdrive had been bugging me to update for months, so I finally did. I had installed 9.1 on my stock rom slot so I wiped and tried to update to rls 15 of hyperdrive. I got a black screen with a pulsing blue led. so I wiped and tried to go to rls 14 same thing. I wiped and created a new rom slot installed rls 15 and got stuck in boot loop. Rls 14 did the same thing here. Then I tried to restore my stock rooted back up and just call it a day, but it didn't work everytime I tried it said failed. So then I went to Odin and tried to flash the stock firmware, being very cautious to pick the verizon one every time. I would say I have downloaded three separate firmware files with no luck even tried a one click stock restore with no luck. Please if you have any thoughts. I just need my phone to work.
Dazac said:
****s ****ed.
I have a gs4 was on me7 running hyperdrive 9.1. Hyperdrive had been bugging me to update for months, so I finally did. I had installed 9.1 on my stock rom slot so I wiped and tried to update to rls 15 of hyperdrive. I got a black screen with a pulsing blue led. so I wiped and tried to go to rls 14 same thing. I wiped and created a new rom slot installed rls 15 and got stuck in boot loop. Rls 14 did the same thing here. Then I tried to restore my stock rooted back up and just call it a day, but it didn't work everytime I tried it said failed. So then I went to Odin and tried to flash the stock firmware, being very cautious to pick the verizon one every time. I would say I have downloaded three separate firmware files with no luck even tried a one click stock restore with no luck. Please if you have any thoughts. I just need my phone to work.
Click to expand...
Click to collapse
Follow this but flash hyperdrive 15 instead of 11
http://forum.xda-developers.com/showthread.php?t=2579278
joshuabg said:
Follow this but flash hyperdrive 15 instead of 11
http://forum.xda-developers.com/showthread.php?t=2579278
Click to expand...
Click to collapse
Thanks for the reply but I have already solved the problem.
It wasn't that I couldn't follow directions. My **** was soft bricked.
After hours (26 to be exact) of scouring the forums, I finally found a combo that worked.
For any one else having this problem I posted steps to fix it here
I was originally trying to just go to the new kitkat rom, i believe that was CM11 or something of the sort. But for some reason i cannot do anything with my phone when it comes to installing or changing the recovery. Odin fails every time. One-Click-Root fails every time (which i think is what i used from the beginning to root). I even upgraded ROM manager to pro so i could try the touch based recovery and it will not successfully install a recovery that i can boot into even though it says that it has and shows(ed) the current recovery being the most up-to-date version. And now since ive tried several different today, i have lost root somehow...even thought i just had it and didnt change anything with the root process...just trying to regain even the stock recovery. Basically what happens if i try to boot into recovery mode is it tries for half a second then boots to ODIN mode and in the top left corner it says failed normal boot or something of the sort.
Can someone point me in the right direction? would a factory reset within the android OS help anything? every thing is backed up, so that wont be an issue as far as apps/data and important files goes.
The phone still boots to my "rooted" 4.3 that i have installed, just dont have root privelages any longer...the phone still works as normal...just cant do anything root based...like run titanium backup or supersu, and even ROM manager is NOW giving me an error when trying to install a custom recovery.
I would like to restore to stock MDK so i can start from scratch and install the CM11 KitKat Rom if at all possible...
So you were mdk and loki'd correct...
safestrap powered Hyperdrive 12
decaturbob said:
So you were mdk and loki'd correct...
safestrap powered Hyperdrive 12
Click to expand...
Click to collapse
MDK yes, the loki part im not sure of...but i did try to do that again since having this problem...with no success...
MURD3RD said:
MDK yes, the loki part im not sure of...but i did try to do that again since having this problem...with no success...
Click to expand...
Click to collapse
you would have to to use the loki process to gain root and install the custom recovery at the time. I really can't help as I got into the S4 with ME7 base and been using safestrap.
i also tried following this link
http://forum.xda-developers.com/showthread.php?t=2290798
and it doesnt get past the first ODIN step and gets a fail
attached are some snips of the ODIN screen when it fails
decaturbob said:
you would have to to use the loki process to gain root and install the custom recovery at the time. I really can't help as I got into the S4 with ME7 base and been using safestrap.
Click to expand...
Click to collapse
you got a link to a good working Loki tutorial?
Here's a link to the stock mdk tar file. This will totally wipe your phone. http://www.sxtpdevelopers.com/showthread.php?t=237
Ryno77 said:
Here's a link to the stock mdk tar file. This will totally wipe your phone.
Click to expand...
Click to collapse
i did find that link before and am currently downloading it...but it is taking forever...everything else i download is blazing fast (50Mb D/L speed here at my buddies apartment) but yet this file is only downloading at 50KB/s...and is showing over 9-10 hours for the download to be complete...does anybody have a faster download source?
i know my connection is phenomenal since i downloaded a 9 gig file last night from a different source and it took under an hour...this .tar is less than 2 gigs...shouldnt take that damn long...
i also tried flashing the recovery .tar.md5 from that link...same exact result...
Questions and Help issues go in Q&A and Help section
Thread moved
Thanks
FNSM
kennyglass123 said:
Questions and Help issues go in Q&A and Help section
Thread moved
Thanks
FNSM
Click to expand...
Click to collapse
THANKS!!!
I knew i hadn't put it in the right place...hopefully it'll get more view here...and i can get this thing sorted out
so right now the screen shows (phone)--(yellow triangle)--(computer) and says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
this is after trying to install the stock restore .tar files in the link mentioned above...the device will NO LONGER boot the os and goes to this screen every time. I can still get it into download (Odin) mode though.
MURD3RD said:
i also tried following this link
http://forum.xda-developers.com/showthread.php?t=2290798
and it doesnt get past the first ODIN step and gets a fail
attached are some snips of the ODIN screen when it fails
Click to expand...
Click to collapse
The "fail (auth)" means that you're likely no longer running an MDK bootloader. It's refusing to load the MD2 that's used by Loki.
Do you get the same failure when you try to flash the stock MDK ROM image? What text shows up on your phone when you try to flash the stock?
Since you're stuck at the "Firmware upgrade encountered an issue." it indicates that the bootloader rejected a flash, which means you may have somehow updated to MI1 or later. The message on the phone when the flash fails will tell for sure.
k1mu said:
The "fail (auth)" means that you're likely no longer running an MDK bootloader. It's refusing to load the MD2 that's used by Loki.
Do you get the same failure when you try to flash the stock MDK ROM image? What text shows up on your phone when you try to flash the stock?
Since you're stuck at the "Firmware upgrade encountered an issue." it indicates that the bootloader rejected a flash, which means you may have somehow updated to MI1 or later. The message on the phone when the flash fails will tell for sure.
Click to expand...
Click to collapse
i can't remember what exactly the messages were right now...but currently Kies is trying a recovery "upgrade and initialization"...hopefully this works and my phone can at least be usable again...and THEN ill get back at trying to get the new KitKat, lol
MURD3RD said:
i can't remember what exactly the messages were right now...but currently Kies is trying a recovery "upgrade and initialization"...hopefully this works and my phone can at least be usable again...and THEN ill get back at trying to get the new KitKat, lol
Click to expand...
Click to collapse
You won't be on MDK, so no KitKat.
k1mu said:
You won't be on MDK, so no KitKat.
Click to expand...
Click to collapse
but i have had no problem flashing back to get rooted when i first got the device...even though several threads said it couldnt be done...all i need is to get back to stock and start from scratch...at least i hope this is the case. If it goes ahead and installs the newest 4.3 update...and i truly cant change it due to no exploits yet...then i guess ill have to wait...lol, it could be worse, haha
so kies just finished doing its thing and the phone booted up and is now running 4.3 MK2
MURD3RD said:
so kies just finished doing its thing and the phone booted up and is now running 4.3 MK2
Click to expand...
Click to collapse
That means you lost the mdk bootloader and can only use Safestrap to boot custom rooms :/ you will need to root via saferoot in the development thread first. Then load Safestrap which only has one ROM that currently works (hyper drive 12).
gnubian said:
That means you lost the mdk bootloader and can only use Safestrap to boot custom rooms :/ you will need to root via saferoot in the development thread first. Then load Safestrap which only has one ROM that currently works (hyper drive 12).
Click to expand...
Click to collapse
EDIT: well nevermind...i think i was just crazy to think something different...i am definitely running the latest release of 4.3 from vzw...fml...well at least it can still be rooted. Is there any development for KitKat on the new MK2 software? Ill do some searching around...
i do remember, however, doing something that a tutorial said specifically not to do...and it worked anyway...even though several people responding to the thread said not to do or it would brick the phone...o well i guess...if i find the link ill post it up...
gnubian said:
That means you lost the mdk bootloader and can only use Safestrap to boot custom rooms :/ you will need to root via saferoot in the development thread first. Then load Safestrap which only has one ROM that currently works (hyper drive 12).
Click to expand...
Click to collapse
would you happen to have a link to the safestrap tutorial? i cant seem to locate it...im gunna do some more searching, but if you had a link at the ready, that'd be awesome!!!
EDIT: Found it...no worries
gnubian said:
That means you lost the mdk bootloader and can only use Safestrap to boot custom rooms :/ you will need to root via saferoot in the development thread first. Then load Safestrap which only has one ROM that currently works (hyper drive 12).
Click to expand...
Click to collapse
so i found the thread for this ROM and it doesnt say anything about being able to run on MK2 build...can anyone shed some light on this? it only says MJ7...
Brother-in-law dropped his s4 in the sink. After panicked drying it will turn on but the rom is scrambled. So he gave it to me. I can get it into recovery (odin) but I'm afraid I don't know much about odin. I found the most recent stock rom but it keeps giving me an error "Secure check failed: hidden". Is this because I'm using the wrong rom file or is it just permabricked?
DieKatzchen said:
Brother-in-law dropped his s4 in the sink. After panicked drying it will turn on but the rom is scrambled. So he gave it to me. I can get it into recovery (odin) but I'm afraid I don't know much about odin. I found the most recent stock rom but it keeps giving me an error "Secure check failed: hidden". Is this because I'm using the wrong rom file or is it just permabricked?
Click to expand...
Click to collapse
You can Odin back to stock & use Odin to flash a recovery like Philz Touch or TWRP. Unless, of course, it's a later build than MDK. In that case you are going to have to use Safestrap as a recovery and will be limited to the roms compatible with it. Roms are flashed from a recovery program, not from Odin.
wtherrell said:
You can Odin back to stock & use Odin to flash a recovery like Philz Touch or TWRP. Unless, of course, it's a later build than MDK. In that case you are going to have to use Safestrap as a recovery and will be limited to the roms compatible with it. Roms are flashed from a recovery program, not from Odin.
Click to expand...
Click to collapse
I'm /trying/ to Odin back to stock. I'm just not sure how to do that.
DieKatzchen said:
I'm /trying/ to Odin back to stock. I'm just not sure how to do that.
Click to expand...
Click to collapse
Several threads and YouTube videos about odin
Sent from my SCH-I545 using XDA Premium 4 mobile app
DieKatzchen said:
Brother-in-law dropped his s4 in the sink. After panicked drying it will turn on but the rom is scrambled. So he gave it to me. I can get it into recovery (odin) but I'm afraid I don't know much about odin. I found the most recent stock rom but it keeps giving me an error "Secure check failed: hidden". Is this because I'm using the wrong rom file or is it just permabricked?
Click to expand...
Click to collapse
I haven't done much with the SGS4 yet, but I think the problem you are having is the phone was not running the most recent software release (MK2) From what I've gathered in reading through other threads is you're going to have to try flashing each stock rom version until you find the right one. Of course the phone could just be completely screwed and nothing will work. I'd start by trying to flash MDK, if that works, consider yourself lucky because that is the holy grail version to have. You can actually unlock the bootloader and put a custom recovery on.
jgulig79 said:
I haven't done much with the SGS4 yet, but I think the problem you are having is the phone was not running the most recent software release (MK2) From what I've gathered in reading through other threads is you're going to have to try flashing each stock rom version until you find the right one. Of course the phone could just be completely screwed and nothing will work. I'd start by trying to flash MDK, if that works, consider yourself lucky because that is the holy grail version to have. You can actually unlock the bootloader and put a custom recovery on.
Click to expand...
Click to collapse
Thanks, I'll try that.
Hi all, I recently rooted my Verizon galaxy s4 i545vrufng6 4.4.2 and ever since I did I have had some issues. The way I did it was by flashing the ng5 kernel and using towelroot then reflashing ng6. After I did that my wifi was stuck on the dull green light but I read on a forum on how to fix that by going into the system and deleting one of the wifi files. After I did that everything worked fine for a few days! Then I went out of state and when I got on the airplane my phone was put on airplane mode, by the time I landed and took off airplane mode wifi wouldn't work at all. I tried to do the same thing I did earlier but it didn't work. Matter of fact, i cannot even find that file anymore Wifi will no longer even go dull green, i can hit it as many times as I want and it will stay in the off position. I thought if I flashed a custom rom it would restart the wifi, so I looked up how to install cyanogenmod and followed the YouTube vid from wwjoshdew (30minute). I didn't get through the whole thing because when my phone restarted it had an unlocked padlock at the bottom of the Samsung start up logo and when it went into recovery mode it came up with a yellow triangle saying that system software is not authorized by Verizon wireless. I can boot it up normally or I can go into download mode but I can't access recovery mode meaning I cannot do a factory reset. I took it to Verizon and they said they couldn't help me cuz I void the warranty. If anyone could please help me get my phone back to normal I would appreciate it so much! Thank you!
Garrett11 said:
Hi all, I recently rooted my Verizon galaxy s4 i545vrufng6 4.4.2 and ever since I did I have had some issues. The way I did it was by flashing the ng5 kernel and using towelroot then reflashing ng6. After I did that my wifi was stuck on the dull green light but I read on a forum on how to fix that by going into the system and deleting one of the wifi files. After I did that everything worked fine for a few days! Then I went out of state and when I got on the airplane my phone was put on airplane mode, by the time I landed and took off airplane mode wifi wouldn't work at all. I tried to do the same thing I did earlier but it didn't work. Matter of fact, i cannot even find that file anymore Wifi will no longer even go dull green, i can hit it as many times as I want and it will stay in the off position. I thought if I flashed a custom rom it would restart the wifi, so I looked up how to install cyanogenmod and followed the YouTube vid from wwjoshdew (30minute). I didn't get through the whole thing because when my phone restarted it had an unlocked padlock at the bottom of the Samsung start up logo and when it went into recovery mode it came up with a yellow triangle saying that system software is not authorized by Verizon wireless. I can boot it up normally or I can go into download mode but I can't access recovery mode meaning I cannot do a factory reset. I took it to Verizon and they said they couldn't help me cuz I void the warranty. If anyone could please help me get my phone back to normal I would appreciate it so much! Thank you!
Click to expand...
Click to collapse
Sooooo.... you soft bricked your phone by flashing an unsupported ROM on your particular firmware. Cynanogenmod or ANY OTHER pure AOSP Rom is not compatible with firmwares later than MDK. Don't do that again.
You need to flash one of these http://forum.xda-developers.com/showthread.php?t=2735172 in Odin. Instructions are in the thread. You are going to be downgrading back to NC5 (the firmware version before NG6). This may fix your wifi issues as well.
Sent from my SCH-I545
liljoe727 said:
Sooooo.... you soft bricked your phone by flashing an unsupported ROM on your particular firmware. Cynanogenmod or ANY OTHER pure AOSP Rom is not compatible with firmwares later than MDK. Don't do that again.
You need to flash one of these http://forum.xda-developers.com/showthread.php?t=2735172 in Odin. Instructions are in the thread. You are going to be downgrading back to NC5 (the firmware version before NG6). This may fix your wifi issues as well.
Sent from my SCH-I545
Click to expand...
Click to collapse
Thanks so much for the reply. I have downloaded the full wipe and have unzipped it. When i try to put it in Odin it says "md5 error! Binary is invalid" i cannot continue to start the process because of this.
Garrett11 said:
Thanks so much for the reply. I have downloaded the full wipe and have unzipped it. When i try to put it in Odin it says "md5 error! Binary is invalid" i cannot continue to start the process because of this.
Click to expand...
Click to collapse
Download the file zip again and check the md5. You may have a bad download.
Sent from my SCH-I545
liljoe727 said:
Download the file zip again and check the md5. You may have a bad download.
Sent from my SCH-I545
Click to expand...
Click to collapse
Thanks so much for everything. I got it passed in Odin and everything is working this far . One last question, will I be able to root without it messing up again? Id love to have my phone rooted but if it means it wont work while rooted i would rather have it just be able to work regularly
Thanks for everything!
Garrett11 said:
Thanks so much for everything. I got it passed in Odin and everything is working this far . One last question, will I be able to root without it messing up again? Id love to have my phone rooted but if it means it wont work while rooted i would rather have it just be able to work regularly
Thanks for everything!
Click to expand...
Click to collapse
Towelroot.com will work for you as far as root goes as long as you stay on NC5 firmware. Just download the APK, install it and go into the app to "make it rain"...profit.
Sent from my SCH-I545
liljoe727 said:
Towelroot.com will work for you as far as root goes as long as you stay on NC5 firmware. Just download the APK, install it and go into the app to "make it rain"...profit.
Sent from my SCH-I545
Click to expand...
Click to collapse
Awesome. Much thanks man!!!!
I saw alot of people asking about these, so I've repacked the stock Modem, Bootloader, Kernel and Recovery from the full .tar separately as Odin flashable .tar's for anyone who needs them. And also created a recovery flashable stock kernel.
I've tested them all out and they work correctly for me, use at your own risk though. For G900T ONLY
Also, consider this: Warning flashing Bootloader/Modem/ FULL FIRMWARE LOLLIPOP
Flashable in Odin:
Bootloader/BL:
Bootloader
Bootloader Mirror
Phone/CP:
Modem
PDA/AP:
Kernel
Recovery
Full .tar thanks to @GSXeclipsePSI and SamMobile
Flashable in recovery(I used TWRP):
Stock Recovery Flashable .zip
Thanks so much for posting these. I upgraded modem, bootloader and kernel no problem.
Stock kernel seems to work better than the ktoonsez one (for me at least), but i don't think I can get SElinux to be permissive on the stock kernel (doesn't seem to stick when I use SElinux mode changer app), which in turn seems to mean I can't use Viper...so I flashed back ktoonsez kernel since I can't live without Viper
Any thoughts on what I may be doing wrong...I know this isn't a Viper thread, but I'm pretty sure I read over there that SElinux permissive was a must for Viper to work, so if stock kernel doesn't allow for that, then my next thought is it possible to have stock kernel that's SElinux permissive?
How did you guys install the stock kernel? I used odin, wiped cache, and all I get is the initial Galaxy S5 Power By Android logo and it never goes past this.
did you try pulling the battery before you start the phone up on download mode? I always have to do that first and the always works for me.
cyhamada said:
Thanks so much for posting these. I upgraded modem, bootloader and kernel no problem.
Stock kernel seems to work better than the ktoonsez one (for me at least), but i don't think I can get SElinux to be permissive on the stock kernel (doesn't seem to stick when I use SElinux mode changer app), which in turn seems to mean I can't use Viper...so I flashed back ktoonsez kernel since I can't live without Viper
Any thoughts on what I may be doing wrong...I know this isn't a Viper thread, but I'm pretty sure I read over there that SElinux permissive was a must for Viper to work, so if stock kernel doesn't allow for that, then my next thought is it possible to have stock kernel that's SElinux permissive?
Click to expand...
Click to collapse
I have the same problem, nothing sounds as good without Viper But i'm dealing with the stock kernel for now.
ALaz502 said:
How did you guys install the stock kernel? I used odin, wiped cache, and all I get is the initial Galaxy S5 Power By Android logo and it never goes past this.
Click to expand...
Click to collapse
As cyhamada says above, you sometimes have to pull the battery before going into Download mode. Also, try a different version of Odin. With Odin 3.09 flashing the full .tar results with my phone sitting on the boot logo.
Updated Bootloader/Modem, yet my Baseband hasn't changed from NK2, shouldn't it change to the OB1?
I'm running CM12, boots fine, LTE signal's been junk since upgrading to NK2 and was hoping this new modem would have some corrections. (Phoenix, AZ)
Paulenski said:
Updated Bootloader/Modem, yet my Baseband hasn't changed from NK2, shouldn't it change to the OB1?
I'm running CM12, boots fine, LTE signal's been junk since upgrading to NK2 and was hoping this new modem would have some corrections. (Phoenix, AZ)
Click to expand...
Click to collapse
You have to be on stock for it to stick, and sometimes it will take a couple tries of lashing it even then, usually the best way is to pull battery and then boot into download.
aaricchavez said:
You have to be on stock for it to stick, and sometimes it will take a couple tries of lashing it even then, usually the best way is to pull battery and then boot into download.
Click to expand...
Click to collapse
I actually got it to stick on cm12 after pulling battery.
spidey2483 said:
I actually got it to stick on cm12 after pulling battery.
Click to expand...
Click to collapse
Really? What i've always seen and experienced is that you have to be on stock, on previous updates I had to go to stock to get it to stick. I guess ymmv.
aaricchavez said:
Really? What i've always seen and experienced is that you have to be on stock, on previous updates I had to go to stock to get it to stick. I guess ymmv.
Click to expand...
Click to collapse
It stuck after I did a battery pull on the 3rd or 4th try, the blue "secure boot: enabled" appeared when it actually worked. I went from Recovery > Download, odin flashed, pulled battery, odin flashed and it worked.
bootloader went fine but modem causing me to hang on sammy screen and i cant seem to get past it no matter what i try.
tried kernel now im hung on GS5 screen. lol
aaricchavez said:
I saw alot of people asking about these, so I've repacked the stock Modem, Bootloader, Kernel and Recovery from the full .tar separately as Odin flashable .tar's for anyone who needs them. And also created a recovery flashable stock kernel.
I've tested them all out and they work correctly for me, use at your own risk though. For G900T ONLY
Also, consider this: Warning flashing Bootloader/Modem/ FULL FIRMWARE LOLLIPOP
Flashable in Odin:
Bootloader/BL:
Bootloader
Phone/CP:
Modem
PDA/AP:
Kernel
Recovery
Full .tar thanks to @GSXeclipsePSI and SamMobile
Flashable in recovery(I used TWRP):
Stock Recovery Flashable .zip
Click to expand...
Click to collapse
Bootloader link is not working for me can anyone provide working link? Thank you all in advance.
ledezma2003 said:
Bootloader link is not working for me can anyone provide working link? Thank you all in advance.
Click to expand...
Click to collapse
It looks like it's up from here. Here's a mirror though.
Bootloader Mirror
aaricchavez said:
It looks like it's up from here. Here's a mirror though.
Bootloader Mirror
Click to expand...
Click to collapse
Thank you this one worked.
is there a way to root if were on lolipop?
darren.wlsn1 said:
is there a way to root if were on lolipop?
Click to expand...
Click to collapse
Have you tried CF-Auto-Root? Next thing after that I would say install TWRP and exit, it will ask to root if it doesn't detect root.
aaricchavez said:
Have you tried CF-Auto-Root? Next thing after that I would say install TWRP and exit, it will ask to root if it doesn't detect root.
Click to expand...
Click to collapse
ya i got twrp on through cf but had to sideload in twrp but never got sideload to open but now in stuck on tmo screen and never been stuck there
darren.wlsn1 said:
ya i got twrp on through cf but had to sideload in twrp but never got sideload to open but now in stuck on tmo screen and never been stuck there
Click to expand...
Click to collapse
How long has it been on the boot animation? First boot/first clean boot(new kernel, etc.) for Lollipop takes a while to build ART.
aaricchavez said:
How long has it been on the boot animation? First boot/first clean boot(new kernel, etc.) for Lollipop takes a while to build ART.
Click to expand...
Click to collapse
any tar i flash now is hanging on tmo screen for as long as i let it sit, im at point i just want it vto boot no matter what build i use
bit the bullet and reset in stock recovery
darren.wlsn1 said:
any tar i flash now is hanging on tmo screen for as long as i let it sit, im at point i just want it vto boot no matter what build i use
Click to expand...
Click to collapse
Here's what I would do if I were in your situation. Grab the full OB1 .tar and Odin 3.07 along with TWRP. I would: Odin TWRP>Do a factory reset>Pull battery>Boot into Download mode>Flash OB1>Let it sit for about 20 min. If you have adb set up on your computer I would also do "adb logcat" to see what exactly is going on. Although I don't recall if it'll pickup after a factory reset, I just do it so often on mine I never pay attention.
If that failed I would Odin TWRP and grab one of the Lollipop roms and flash that.