Hello Everyone,
I'm a first time poster but have been reading this site for weeks trying to find the answer to my questions. I've acquired a good bit of info but still wanted to clarify some things before I take the plunge.
I'm currently using a Verizon GS4 (I-545) running rooted stock MK2 jellybean. I rooted ~2 years ago to get rid of the bloatware and just never bothered upgrading/keeping up with the firmware updates. There are some new apps that won't work on my phone, but are working on my wife's stock GS4 on OF1. I'd like to upgrade my firmware (and keep root) so that I don't have to keep stealing her phone.
I've come across several threads discussing upgrading from one baseband to the next - none quite match my scenario. Most threads talk about how to upgrade and keep root but now that I'm late to the party, it seems like root methods have been discovered for all stock firmware versions (even OF1 by flashing OC1 kernel, rooting, and flashing back to OF1 kernel). So with this in mind, can I just skip all the complicated stuff and just use Odin to flash OF1 and then follow Edgardo_Uchicha's OF1 root method?
If I can use Odin to flash OF1, will the file I load in the "AP" slot also includes the proper modules, bootloaders, etc. to upgrade everything to OF1? Will it do a factory reset/wipe or will I keep all my data like an OTA? As for getting the Odin file, it looks like I should just use the Samsung site to get it directly?
If I can use the Odin method, are there any drawbacks? If I don't like lollipop I realize I'm stuck and can't go back, but is there anyway to upgrade and be able to go back (downgrade)?
Thanks again for your help!
Mike
Hello Mike,
You can flash OF1 and root via the method others and I posted, some people wrote that other rooting software/apps are starting to work on lollipop builds, I haven't tested yet(since my device have a custom rom and it's rooted) but soon I will and will update the thread. Btw, my suggestion to you is flashing this specific odin package:
[Odin][TAR] I545VRUGOF1 neutered (No BL)
I was on kitkat bootloader, flashed this OF1 build and went back to kitkat without problems
Good luck!
Edgardo_Uchiha said:
Hello Mike,
You can flash OF1 and root via the method others and I posted, some people wrote that other rooting software/apps are starting to work on lollipop builds, I haven't tested yet(since my device have a custom rom and it's rooted) but soon I will and will update the thread. Btw, my suggestion to you is flashing this specific odin package:
[Odin][TAR] I545VRUGOF1 neutered (No BL)
I was on kitkat bootloader, flashed this OF1 build and went back to kitkat without problems
Good luck!
Click to expand...
Click to collapse
So I followed the thread you linked and it looked like my phone upgraded OK. However, even at lock screen I get the message "Unfortunately, the process com.android.phone has stopped". It reappears as soon as I dismiss it...basically making my phone useless. I was able to navigate to the Settings page though and it says I'm on 5.0.1 but under baseband it says "Unknown" rather than OF1. It does show OF1 under the build number though. I'm guessing it didn't like the MK2 bootloader?
Any ideas how to fix? Help!!
mike2914 said:
So I followed the thread you linked and it looked like my phone upgraded OK. However, even at lock screen I get the message "Unfortunately, the process com.android.phone has stopped". It reappears as soon as I dismiss it...basically making my phone useless. I was able to navigate to the Settings page though and it says I'm on 5.0.1 but under baseband it says "Unknown" rather than OF1. It does show OF1 under the build number though. I'm guessing it didn't like the MK2 bootloader?
Any ideas how to fix? Help!!
Click to expand...
Click to collapse
Try wiping via recovery, if I'm not wrong this package does not wipe your phone so maybe there are some leftovers that are messing up the new system
You are correct, the OF1 Odin file you recommended did not wipe my data/apps. You were also correct in that doing a factory reset/wipe fixed the issue. I had some apps that were previously "frozen/disabled" while I had root so I have a feeling that didn't help things when it got updated.
Is there any way to confirm that I still have the MK2 bootloader?
mike2914 said:
You are correct, the OF1 Odin file you recommended did not wipe my data/apps. You were also correct in that doing a factory reset/wipe fixed the issue. I had some apps that were previously "frozen/disabled" while I had root so I have a feeling that didn't help things when it got updated.
Is there any way to confirm that I still have the MK2 bootloader?
Click to expand...
Click to collapse
Download and install terminal emulator, the run these commands:
1. su
2. getprop ro.bootloader
Awesome! I was able to confirm I'm still using the MK2 bootloader. Thanks for all your help!
Related
New member here. Bear with me, please, for possible n00b questions.
I'm not new to rooting & ROM'ing. I've been rooting and ROM'ing for years, but I haven't done much in a while due to excessive work schedule and family obligations. But I'm looking to get back into it.
I've had my VZW S4 for about 9 months. I'm rooted, but running stock ROM.
Phone: i545
Android: 4.2.2
Baseband: I545VRUAME7
Kernal: 3.4.0-690088
Build Number: ...ME7
As I said, I've got lots of experience with rooting and ROMs. I flashed my prior phone easily over 100x experimenting with different ROMs. But since I'm going from 4.2.2 to 4.4.2, I think I better ask regarding my strategy to be sure I don't end up with a brick.
My general plan is to: update my phone to 4.4.2 via OTA update, root, flash recovery, then experiment with various ROMs. Specifically, these are the steps I'm setup to follow:
Back up everything (App's, contacts, bookmarks, SMS, etc.) via Titanium -- actually, I've already done this
Perform factory reset in its current state (4.2.2)
Accept OTA 4.4.2 upgrade from VZW ==> I assume this will revert phone back to UNroot status??
Re-root via Towelroot
Download SuperSU
(Remove KNOX??)
Install recovery
Install ROM
Questions:
I've read about Samsung KNOX. If KNOX is "triggered", Samsung won't honor the warranty. But I don't care about the warranty at this point, so is the whole KNOX thing a moot point for me?
Anything else I should be aware of? Any experienced users of S4 that see an obvious gap in the above plan, I would be much appreciated in hearing your advice.
For what it's worth, I've been studying the following YouTube video for what lies ahead.
"CyanogenMod 11 (CM11) on the Samsung Galaxy S4! (Install, Setup, First Look, and etc)"
uniroot said:
New member here. Bear with me, please, for possible n00b questions.
I'm not new to rooting & ROM'ing. I've been rooting and ROM'ing for years, but I haven't done much in a while due to excessive work schedule and family obligations. But I'm looking to get back into it.
I've had my VZW S4 for about 9 months. I'm rooted, but running stock ROM.
Phone: i545
Android: 4.2.2
Baseband: I545VRUAME7
Kernal: 3.4.0-690088
Build Number: ...ME7
As I said, I've got lots of experience with rooting and ROMs. I flashed my prior phone easily over 100x experimenting with different ROMs. But since I'm going from 4.2.2 to 4.4.2, I think I better ask regarding my strategy to be sure I don't end up with a brick.
My general plan is to: update my phone to 4.4.2 via OTA update, root, flash recovery, then experiment with various ROMs. Specifically, these are the steps I'm setup to follow:
Back up everything (App's, contacts, bookmarks, SMS, etc.) via Titanium -- actually, I've already done this
Perform factory reset in its current state (4.2.2)
Accept OTA 4.4.2 upgrade from VZW ==> I assume this will revert phone back to UNroot status??
Re-root via Towelroot
Download SuperSU
(Remove KNOX??)
Install recovery
Install ROM
Questions:
I've read about Samsung KNOX. If KNOX is "triggered", Samsung won't honor the warranty. But I don't care about the warranty at this point, so is the whole KNOX thing a moot point for me?
Anything else I should be aware of? Any experienced users of S4 that see an obvious gap in the above plan, I would be much appreciated in hearing your advice.
For what it's worth, I've been studying the following YouTube video for what lies ahead.
"CyanogenMod 11 (CM11) on the Samsung Galaxy S4! (Install, Setup, First Look, and etc)"
Click to expand...
Click to collapse
1. DO NOT TAKE THE OTA
2. read the forums regarding what your options for recovery. Don't try to flash cyanogenmod or you'll end up with a brick.
Sent from my SCH-I545 using XDA Free mobile app
I've been researching this for a couple of days, and obviously I'm missing some details.
Why not take the OTA for 4.4.x? What am I missing? What's the issue?
Doing some more research this morning...
When you say: "read the forums regarding what your options for recovery. Don't try to flash cyanogenmod or you'll end up with a brick."
I read from another post: loki allows you to install whatever you want, not just Touchwiz-based ROMs. If you want to install CM, you've got to use Loki.
So I need to perform the loki hack first, right? If I install CM without the loki hack, I will brick my phone?
uniroot said:
Doing some more research this morning...
When you say: "read the forums regarding what your options for recovery. Don't try to flash cyanogenmod or you'll end up with a brick."
I read from another post: loki allows you to install whatever you want, not just Touchwiz-based ROMs. If you want to install CM, you've got to use Loki.
So I need to perform the loki hack first, right? If I install CM without the loki hack, I will brick my phone?
Click to expand...
Click to collapse
Loki only works on MDK, the firmware version before me7. everything after MDK can only run safestrap. Can't downgrade.
You can use the OTA but it will fail if your system is modified at all. If you know all modifications you've done and can remove them, go ahead. If not, use the NC5 tar file in Odin to upgrade.
joshm.1219 said:
Loki only works on MDK, the firmware version before me7. everything after MDK can only run safestrap. Can't downgrade.
You can use the OTA but it will fail if your system is modified at all. If you know all modifications you've done and can remove them, go ahead. If not, use the NC5 tar file in Odin to upgrade.
Click to expand...
Click to collapse
Excellent, thank you for providing this info! I'll look into Odin.
For clarification...I have performed certain "modifications" since I've owned the phone. If I perform a factory reset on it in its current state, does that not remove/reset all of the mods I've done??
uniroot said:
Excellent, thank you for providing this info! I'll look into Odin.
For clarification...I have performed certain "modifications" since I've owned the phone. If I perform a factory reset on it in its current state, does that not remove/reset all of the mods I've done??
Click to expand...
Click to collapse
It should, but not always. Also you have to use the unroot from the supersu app.
---------- Post added at 01:27 PM ---------- Previous post was at 01:27 PM ----------
Oh and the tar files are here: http://forum.xda-developers.com/showthread.php?t=2735172
I recommend using Odin 3.09
You're saying I will need to un-root prior to performing the NC5 Odin?
Do I need to worry about changing/updating my old ME7 build before the NC5 Odin?
uniroot said:
You're saying I will need to un-root prior to performing the NC5 Odin?
Do I need to worry about changing/updating my old ME7 build before the NC5 Odin?
Click to expand...
Click to collapse
No, you only need the unroot if you try the OTA. Nothing else needs to be done to use the tar file with Odin, but I would recommend backing up important data to an external SD and flashing the full wipe file to ensure you have a clean system.
Latest OTA "patches" TowelRoot
I've read recently I've read that the OTA will fix the vulnerability that TowelRoot exploits to gain root. But most if not all of the articles were specific to the S5. It is possible that taking the OTA will patch the same vulnerability and remove root again. It's been a long time since I've had to work this hard to root/ROM anything...so I'm not sure if I'm correct or not, but it's something to consider before taking the OTA...if you haven't already.
~JohnnyB~ said:
I've read recently I've read that the OTA will fix the vulnerability that TowelRoot exploits to gain root. But most if not all of the articles were specific to the S5. It is possible that taking the OTA will patch the same vulnerability and remove root again. It's been a long time since I've had to work this hard to root/ROM anything...so I'm not sure if I'm correct or not, but it's something to consider before taking the OTA...if you haven't already.
Click to expand...
Click to collapse
Towelroot works on NC5, the latest OTA for this device. Towelroot came well after the OTA. If we get another firmware update, I'm sure it will patch towelroot.
Hi everyone, I haven't been active in awhile, and decided to upgrade from 4.4.4 to 5.0.1.
Device is:
Verizon Galaxy S4
MDK / Loki
TWRO 2.8.7.0
was on 4.4.4
I used the FlashFire upgrade method, because I wanted to have that upgrade modem, baseband etc. everything I needed.
Prior to root, I upgraded my TWRP, I did a TWRP backup.
I downloaded Odexed 5.0.1 stock update from the thread, and followed the instructions, it installed but on final reboot, it just got stuck at the Samsung / Custom screen. When I went to boot into recovery, it's now the stock system recovery LRX22c.I545VRUG0C1
Gives an error on the bottom as
Code:
#MANUAL MODE#
Appling Multi-CSC
Applied The CSC-code: VZW
remove failed file /system/csc_contents/ (read only file system)
If I try to apply update via external storage, using stock update I get:
Code:
footer is wrong
signature verification failed
Anyway I can flash TWRP via adb, then just re-flash the rom with loki manually? Or anyway without having to use odin and downgrade? I won't lose loki root will I? What do I do? Thanks in advanced.
well I'm trying to flash back to MDK via odin, and I keep getting aboot.img failure.. i'm really at a loss here, I can't even odin back to MDK.
notstevek said:
well I'm trying to flash back to MDK via odin, and I keep getting aboot.img failure.. i'm really at a loss here, I can't even odin back to MDK.
Click to expand...
Click to collapse
What instructions did you use? SS and FF were made specifically for locked bootloaders so they require a different instructions for flashing. You basically ignored the benefits of being on MDK by doing whatever you did. Doesn't sound like you're on MDK anymore and I need more details to help. Someone else might be able to help you.
If all you wanted was the OC1 modem, could have just flashed it from here. People have reported issues with TWRP versions above 2.8.4.0-jfltexx.
Neffy27 said:
What instructions did you use? SS and FF were made specifically for locked bootloaders so they require a different instructions for flashing. You basically ignored the benefits of being on MDK by doing whatever you did. Doesn't sound like you're on MDK anymore and I need more details to help. Someone else might be able to help you.
If all you wanted was the OC1 modem, could have just flashed it from here. People have reported issues with TWRP versions above 2.8.4.0-jfltexx.
Click to expand...
Click to collapse
The tutorial said for mdk, I followed it exactly and it didn't work. I then ****ed up by flashing lollipop through stock recovery so it flashed the new baseband, and I removed loki. That's my bad, however I did follow the instructions and it didn't work. I should have just flashed 5.1 manually. Oh well. Is there safestrap for lollipop, or a way to downgrade to me7 to use safestrap?
Sent from my SCH-I545 using Tapatalk
SS isn't compatible with Lollipop. Recommend switching to FF, apparently it can flash Stang's ROM on stock OC1. Still need root. Or look into MultiSystem but I'm not knowledgeable with them but hear of success with them.
Sent from my SCH-I545 using Tapatalk 2.4.15
You can use king root to get root, then search for instructions to swap to supersu. From here should be able to install FF.
Good luck.
Sent from my SCH-I545 using Tapatalk 2.4.15
Warning: VRUGOC1 is impervious to previous bootloader bypass methods, and cannot be downgraded. Proceed with caution.
I managed to hose my phone while rooting it somehow, so I had to track down the factory image for I545VRUGOC1 / I545VZWGOC1. To actually flash it, I had to use Odin 3.10.6 rather than 3.09 for some reason, which is available in the links below. I also replaced Odin's SS_DL.dll with the one from the zip that contains the tar file, but I'm not sure if that was necessary.
Hope this helps anyone else from who's stuck
TAR
https://mega.nz/#!T0tTDZKA!tIw4ebWEWhsTJWTbyWVx9e07aSBSc_1_Xm2mWWkdu8I
Mirror: http://upple.it/4b1331ec4f4dd04e/VZW-I545VRUGOC1-20150502144520.zip
Slower / crappier mirrors I found in case the above doesn't work:
http://rapidgator.net/file/6f4fd8106796c1bba92dd20a7b5a5c51
http://uploaded.net/file/zcbqwyz5
Odin
http://odindownload.com/download/Odin3_v3.10.6.zip
Mirror: https://mega.nz/#!qh9UTJ6Q!gLDkj2xwXRb8Wa2YTbPODpdrhqowK-s6eZjXI_bTrhQ
kd- said:
Warning: VRUGOC1 is impervious to previous bootloader bypass methods. Proceed with caution.
Click to expand...
Click to collapse
Thanks! I found the file here too:
http://d-h.st/LNQV
My question is, I have a Kitkat Verizon phone here, I assume upgrading it restricts custom ROMs that can be loaded to it?
Thanks for another mirror - the more the better
Yes, I don't think any current custom ROMs work with the VRUGOC1 bootloader, etc. FlashFire has worked for a couple experiments I've run (flashing wireless hotspot fix, for example), but I'm hesitant to flash anything more substantial. I have not tried SafeStrap but I have not seen anything about it working yet.
kd- said:
Thanks for another mirror - the more the better
Yes, I don't think any current custom ROMs work with the VRUGOC1 bootloader, etc. FlashFire has worked for a couple experiments I've run (flashing wireless hotspot fix, for example), but I'm hesitant to flash anything more substantial. I have not tried SafeStrap but I have not seen anything about it working yet.
Click to expand...
Click to collapse
muniz_ri has posted a stock, de-odexed (and odexed, too of course) that should work with OC1 bootloader (it doesn't have a bootloader in it, so the current bootloader should stay)
http://forum.xda-developers.com/gal...ment/rom-i545oc1-5-0-1-100-stock-mdk-t3097902
I haven't installed flashfire yet, but i am on OC1 and already went through the rooting process.
Does this boot if I flash it and the NK4 bootloader?
Oishikatta said:
Does this boot if I flash it and the NK4 bootloader?
Click to expand...
Click to collapse
muniz_ri has a tar with the oc1 build and the nk4 bootloader, look in either general or Android development
^^
It's in android development. Only two or three ROMs work on OC1(at most). I only know of one confirmed.
XxD34THxX said:
^^
It's in android development. Only two or three ROMs work on OC1(at most). I only know of one confirmed.
Click to expand...
Click to collapse
muniz has a stock rooted ROM for the oc1 people, which makes sense if you're going from stock. you can flash deodexed ROM and be able to use xposed framework
skepticmisfit said:
muniz has a stock rooted ROM for the oc1 people, which makes sense if you're going from stock. you can flash deodexed ROM and be able to use xposed framework
Click to expand...
Click to collapse
Yep, it works just fine, flashed with FlashFire.
https://docs.google.com/file/d/0B4RU_ZH5QUASaU9LcDJ3WWZfdXM/edit?usp=docslist_api&pli=1 I found it here two
Can somebody please help me? First, my phone is locked and I was in NK1, so I decided to flash OC1 by the flashfire method (I don't remember who's the author of the topic), everything went fine and I started to use lollipop, but then I was about to sell my phone and I went to settings, then factory reset and the phone restarted, wiped data and cache by itself and then turned on, I thought everything was ok, but then it just stayed in the samsung's wizard screen, it never passed from that screen. So, I decided to manually enter recovery and do a factory reset again, but the result was the same. In order to unbrick the phone I had to use odin and install the NC5 original firmware .
So, my question is, If I want to install lollipop and I don't care to stay with an unlockable bootloader I justt need to use this Firmware and install it through odin? Or do I need to have an specific firmware (e.g nc5, nk1) and unlocked bootloader?
bayron_olaff said:
Can somebody please help me? First, my phone is locked and I was in NK1, so I decided to flash OC1 by the flashfire method (I don't remember who's the author of the topic), everything went fine and I started to use lollipop, but then I was about to sell my phone and I went to settings, then factory reset and the phone restarted, wiped data and cache by itself and then turned on, I thought everything was ok, but then it just stayed in the samsung's wizard screen, it never passed from that screen. So, I decided to manually enter recovery and do a factory reset again, but the result was the same. In order to unbrick the phone I had to use odin and install the NC5 original firmware .
So, my question is, If I want to install lollipop and I don't care to stay with an unlockable bootloader I justt need to use this Firmware and install it through odin? Or do I need to have an specific firmware (e.g nc5, nk1) and unlocked bootloader?
Click to expand...
Click to collapse
Yes, that sounds correct. Personally, I wouldn't flash the OC1 factory image unless you have to - I'd flash the NK1 image, which should reset everything, then upgrade to Lollipop using a method that doesn't upgrade the bootloader so whoever gets the phone next can downgrade if they want to.
Can anyone confirm the mega link is a no-wipe oc1 package?
persdata.img doesnt appear in it just making sure.
Edit : been tested it appears to be a no wipe Odin package
After an unsuccessful flash of Xposed Framework with Chainfire's FlashFire Beta, my device wouldn't boot past the AT&T logo. I attempted to flash NB1 stock firmware using Odin from OC4, but I have the same issue.
Specifics
Device - Samsung Galaxy S4 AT&T (jflteatt)
Firmware - NB1 Stock I think, KNOX flag is untripped but download says I have custom Android version. Tried flashing with Odin and got reset/pass. KNOX flag was tripped before, I read its an eFuse so I'm confused
Should I try flashing again or what... I'd like a quick answer as I currently have no phone. Mod feel free to move this if its in the wrong forum. If you need more information just let me know
Samsung devices are know to have issue with xposed. They made changes to the art runtime and last I heard xposed has not fixed it yet.
So if I want Xposesd I should stay on KitKat
How can I get my device working... I've tried what other threads suggested (cache wipe, factory reset, battery pull for thirty seconds). Should I try the stock image again with Odin or try Kies?
bsch27 said:
So if I want Xposesd I should stay on KitKat
How can I get my device working... I've tried what other threads suggested (cache wipe, factory reset, battery pull for thirty seconds). Should I try the stock image again with Odin or try Kies?
Click to expand...
Click to collapse
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
xposed works fine on lollipop, but you have to use wanams version of the framework for tw
OK, thanks for the advice. FlashFire can run with a locked bootloader, right?
Also, I still can't figure out how to get my phone booting again I would greatly appreciate advice on how to get past the at&t logo
EDIT
My bootloader is locked so I can only flash with Odin and stock recovery. Took the AT&T OTA before I knew what I was doing.
I found the solution! I was trying to flash a MBL stock AIO with Odin, but after I took an OTA from AT&T a while back, they locked downgrading that far because it's vulnerable to Loki. I found a thread on another forums that stated the firmware was mislabeled. I feel lucky, could have hard bricked it! I managed to install a (proper) deodexed NB1 firmware, rooted it with Towelroot, and upgraded to Lollipop through a FlashFire flash. I was able to install Xposed successfully. Thanks for all the help! It's greatly appreciated!
Just bought a refurbished Galaxy S4 as my other phone was stolen. I am on Verizon. My S4 looks brand new and it's running 4.4.2! I would love to root and then probably flash to cm12. How would I root right now? The s4 has been out for some time and maybe the threads are old. Do I root before activating?
Build kot49h.i545vrufnc5
Please help. I have been without root on another phone for over a year. You can imagine my pain.
NO CM12. Nc5 does not have an unlocked bootloader.
As far as rootz towelroot still works. 1 click apk by geohot.
nc5
Tried the towelroot apk and it does not root, work. i get this message
"Only the Galaxy S4 active is currently supported. If you see this error and you think you have the right phone, email geohot at... i know i have an S4 but cant tell if it is an s4 Active. i just left verizon with an activated phone and it is already trying to push an update. I dont know if i should or what to do.
bbiigg said:
Tried the towelroot apk and it does not root, work. i get this message
"Only the Galaxy S4 active is currently supported. If you see this error and you think you have the right phone, email geohot at... i know i have an S4 but cant tell if it is an s4 Active. i just left verizon with an activated phone and it is already trying to push an update. I dont know if i should or what to do.
Click to expand...
Click to collapse
Make sure you are on nc5. Screenshot your settings if you want.
Next, make sure you got it from the real site... That doesn't sound like the right one.
If you have physical menu and back buttons, that's the s4 active. It's ATT only, in which case, this is the wrong device.
NC5
I just gave it a go again after rebooting and it worked. I have root. Now I need to figure out how to remove all this bloated crap. Any ideas. Wish I could flash a custom though. I'm still getting this annoying update window.
bbiigg said:
I just gave it a go again after rebooting and it worked. I have root. Now I need to figure out how to remove all this bloated crap. Any ideas. Wish I could flash a custom though. I'm still getting this annoying update window.
Click to expand...
Click to collapse
There are some debloater scripts on general forum, but I think the best choise to debloat is installing some file explorer (E.G. MiXplorer) and go to /system/app and /system/priv-app and delete everything you don't want. If you don't know what apps to delete This guide it's great
Btw, if you want a rom you can choose any 4.4.2 or newer, don't try any lower android version rom. To install custom roms on this device you can use Flashfire or Safestrap(only for kitkat or lower), I suggest you to use safestrap if you're on kitkat (keep in mind that rom slots doesn't work, you have to flash in stock slot any rom).
oops
I had a rom Hyperdrive installed and it was running well for a minute but I just had to try another rom "Galaxy S6 Port by Albe95"! Now i can make calls and recieve texts but not send them. i have no internet unless its wifi. Im not rooted and Towelroot wont work. No recovery available now and my Android Version is 5.0.2. Im really stuck and nervous. I need my phone for work. Any ideas?
bbiigg said:
I had a rom Hyperdrive installed and it was running well for a minute but I just had to try another rom "Galaxy S6 Port by Albe95"! Now i can make calls and recieve texts but not send them. i have no internet unless its wifi. Im not rooted and Towelroot wont work. No recovery available now and my Android Version is 5.0.2. Im really stuck and nervous. I need my phone for work. Any ideas?
Click to expand...
Click to collapse
No worries. I think you have to flash the OC1 modems for lollipop roms to work when coming from kk. Check your bootloader version, if it is a NC[place number here] you can odin back to the right update and use the flashfire or safestrap to use the installation instructions in the second post of the ROM forum. Your other option is to stay and flash modems. This is how to do it:
If you lost your recovery:
1)Get root (NOTE: you don't need to do the kernel flashing part because you are already on of1
http://forum.xda-developers.com/galaxy-s4-verizon/general/root-of1-t3249971
http://forum.xda-developers.com/galaxy-s4-verizon/general/samsung-s4-i545-verizon-of1-root-t3254434
2)Get Flashfire
3)Flash this (fist link) if it fails to solve the problem this
If this doesn't solve your problem and you can't go back to kitkat, you should odin OC1 and root. All credit goes to their respective contributors. Hope I helped
S4 flashing
whowatchlist said:
No worries. I think you have to flash the OC1 modems for lollipop roms to work when coming from kk. Check your bootloader version, if it is a NC[place number here] you can odin back to the right update and use the flashfire or safestrap to use the installation instructions in the second post of the ROM forum. Your other option is to stay and flash modems. This is how to do it:
If you lost your recovery:
1)Get root (NOTE: you don't need to do the kernel flashing part because you are already on of1
http://forum.xda-developers.com/galaxy-s4-verizon/general/root-of1-t3249971
http://forum.xda-developers.com/galaxy-s4-verizon/general/samsung-s4-i545-verizon-of1-root-t3254434
2)Get Flashfire
3)Flash this (fist link) if it fails to solve the problem this
If this doesn't solve your problem and you can't go back to kitkat, you should odin OC1 and root. All credit goes to their respective contributors. Hope I helped
Click to expand...
Click to collapse
I tried the 2nd option of rooting and it didn't work. I'm still on oc1. How would I Odin back or what files would I use? It's getting confusing.