Flashed GOF1 by mistake from sammmobile using Odin. Now can't find a root method that works. Tried to flash COF1 using Odin but get fail message. Anyone have any suggestions? I'm really just needing root to get backups restored from TiBu. Much appreciated if anyone has suggestions.
Same here. Looking for a way to root OF1. Tried to downgrade to OC1 using method here:
http://forum.xda-developers.com/gal...-to-update-to-i545of1-5-0-1-keeproot-t3182544
It starts to install, but then fails and soft-bricks the phone and I have to use Repair Assistant get reinstall OF1. Any help to root from OF1 appreciated. TIA
I was able to downgrade to oc1 baseband and build. I got the idea from how I use to jump from android to Tizen on my first generation watch. I ran the of1 md5 and intentionally pulled the cord from my phone about 3/4 of the way through the install. Rebooted and had the white monitors telling me to hook up to kies. Then I loaded the PIT file in Odin, and put I545_OC1_Bootloader.tar.md5 in pda, ticked Re-Partition, Auto Reboot, and Nand Erase All boxes in options, and flashed it. After my bootloader flashed sucessfullly, I ran a stock md5 of the OC1 rom. Once flashed I booted into recovery, wiped cache, wiped system data both two times just to be safe, rebooted and I was on stock OC1 baseband and build ready to root with kingroot.
So you tried to reflash of1 using kies? Would you posible have the files you used to go back?
Thanks, really good idea
HeeyMaan said:
I was able to downgrade to oc1 baseband and build. I got the idea from how I use to jump from android to Tizen on my first generation watch. I ran the of1 md5 and intentionally pulled the cord from my phone about 3/4 of the way through the install. Rebooted and had the white monitors telling me to hook up to kies. Then I loaded the PIT file in Odin, and put I545_OC1_Bootloader.tar.md5 in pda, ticked Re-Partition, Auto Reboot, and Nand Erase All boxes in options, and flashed it. After my bootloader flashed sucessfullly, I ran a stock md5 of the OC1 rom. Once flashed I booted into recovery, wiped cache, wiped system data both two times just to be safe, rebooted and I was on stock OC1 baseband and build ready to root with kingroot.
Click to expand...
Click to collapse
This is exactly what i need. I have just lost root by taking OTA to OF1, and i think what you mentioned might work to get me back to OC1 Rooted until someone comes up with something better. Sound feasible? Does this method only work when you pull the plug like that? still not sure what white monitors is, sorry.
I am on OF1 and was rooted, flashed the stock rooted ROM and it didn't take. I Odin flashed this - http://forum.xda-developers.com/galaxy-s4-verizon/development/odin-i545vrugof1-neutered-bl-t3203361 and it got me back to unrooted OF1. I then went and did the re-root process for OF1 and am back rooted again. I think this file is a stock OF1 image, just doesn't have the bootloader which if you're on OF1 already then you have the OF1 bootloader.
What options do we have if we have the OF1 bootloader.
Sent from my SCH-I545 using Tapatalk
shiz0id said:
What options do we have if we have the OF1 bootloader.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
As far as I know stang5litre has a OF1 compatible ROM and of course the stock deodex ROM/stock ROM. I'm not sure of any past those.
Related
So I've been really confused about all this MJ4 updating and such lately. My Note 3 was running a stock rooted M15. But I wanted to get these new fixes for the call quality in MJ4.
So here is what I did......
I downloaded MJ4 tar and Kernel from the Samsung updates site. I installed via Odin 3.07. It apparently updated my phone to MJ4 according to the "About Device" screen on my phone. However I was still having bad audio issues. So I ran "Root Checker" back to back 3 times while I was at work this evening and of course it said I didn't have root. So i then tried to installed the MJ4 update again via the "Updates" menu on my phone and it said I couldn't because my phone was modified.
So when I got home, I reran that tar and kernel again, with same result. So then I stared hunting around the forum for answers. I ran across a thread that said there were two ways to restore root: 1.)Install TWRP via Odin, Use a nanadroid back up and restore the rom from the M15 backup but without reinstalling the modem or 2.)install TWRP via Odin, disconnect my phone reboot into TWRP and then Flash the ChainFire SU 1.65 zip.
Well I couldnt do method 1.) because I forgot to do a nandroid before performing the update (I know....Idiot). So I tried option 2.) after rerunning the tar and kernel again. Then I tried to install Freeza's [ROM|StockRooted] 11/6/13 Sprint TouchWiz Jelly Bean 4.3 (N900PVPUBMJ4) Odex/DeOdex which of course failed.
So I then rebooted to recovery again and wiped dalvik and cache. Then rebooted my device in order to be disappointed. So I ran "Root Checker" again and low and behold , it says my device is rooted. So confused,. I ran it again and it say's I'm rooted. So I open Titanium Backup to see if I get a error and I dont. It acts as if I'm rooted.
Now key things to remember in the process:
When I initially updated to M15 I used a rooted stock version of the M15 firmware.
I NEVER wiped anything (dalvik, cache, data or system) before flashing. Also none of my data, apps, internal or external storage were wiped in this process. So all of my apps are installed and running. To answer the first question, Yes...Knox is still saying I have 0x1 void warranty.
So am I really rooted or is my system just fooled into thinking I'm rooted and how do I find out?
ANY IDEAS?
Is superuser installed? If it is just try a new app that requires root, if it asks form permission and you can grant it then you are rooted. Personally I would reflash MJ4 tar from odin. Run cf auto root from Odin and you will be on stock rooted MJ4. If you want to flash a custom ROM then flash twrp from Odin and you can then flash a ROM through twrp. Bonsai ROM is working great, freeza's stock MJ4 ROM had a couple minor issues which are ironed out with Bonsai.
SGS4 Sent
ifly4vamerica said:
Is superuser installed? If it is just try a new app that requires root, if it asks form permission and you can grant it then you are rooted. Personally I would reflash MJ4 tar from odin. Run cf auto root from Odin and you will be on stock rooted MJ4. If you want to flash a custom ROM then flash twrp from Odin and you can then flash a ROM through twrp. Bonsai ROM is working great, freeza's stock MJ4 ROM had a couple minor issues which are ironed out with Bonsai.
SGS4 Sent
Click to expand...
Click to collapse
Thanks for the reply bro. Yeah I was thinking to try the whole thing over again. I heard people were not able to root MJ4 with CF Autoroot right now. I just flashed a couple of mods and they worked. I also gave Superusers permission to two apps and they are working.
shaun0207 said:
Thanks for the reply bro. Yeah I was thinking to try the whole thing over again. I heard people were not able to root MJ4 with CF Autoroot right now. I just flashed a couple of mods and they worked. I also gave Superusers permission to two apps and they are working.
Click to expand...
Click to collapse
You should be good to go then. As long as you are happy with the ROM you have etc I wouldn't mess with it. If you do go back to stock there is always kingoroot, people seems to have good luck with that.
Note 3 or Gear Sent
I rooted my s4 and installed twrp a long time ago used the phone for a little while then stashed it away. It had the following rom installed I545VRVFNC5 stock root oder I believe it was 4.4.2. The other night I installed flash fire and attempted to flash I545_OC1_Stock_rooted_rom mdk. It flashed ok but now I'm getting the verizon warning message and I can't bypass. I can no longer boot into twrp. I think the bootloader is still unlocked, padlock is unlocked upon boot. How do I get myself out of this message?
looneyk said:
I rooted my s4 and installed twrp a long time ago used the phone for a little while then stashed it away. It had the following rom installed I545VRVFNC5 stock root oder I believe it was 4.4.2. The other night I installed flash fire and attempted to flash I545_OC1_Stock_rooted_rom mdk. It flashed ok but now I'm getting the verizon warning message and I can't bypass. I can no longer boot into twrp. I think the bootloader is still unlocked, padlock is unlocked upon boot. How do I get myself out of this message?
Click to expand...
Click to collapse
Try to Odin back to MDK, if you had TWRP... If that doesn't work, nc5. You can't do custom ROM's like Cynanogenmod, but you have a limited amount of freedom with safestrap.
looneyk said:
I rooted my s4 and installed twrp a long time ago used the phone for a little while then stashed it away. It had the following rom installed I545VRVFNC5 stock root oder I believe it was 4.4.2. The other night I installed flash fire and attempted to flash I545_OC1_Stock_rooted_rom mdk. It flashed ok but now I'm getting the verizon warning message and I can't bypass. I can no longer boot into twrp. I think the bootloader is still unlocked, padlock is unlocked upon boot. How do I get myself out of this message?
Click to expand...
Click to collapse
The open padlock means the firmware you have installed is custom and not stock, doesn't mean your boot loader is unlocked. I would simply boot into download mode and re-image your device back to MDK, if that's where you were. What's your current boot loader version?
looneyk said:
I rooted my s4 and installed twrp a long time ago used the phone for a little while then stashed it away. It had the following rom installed I545VRVFNC5 stock root oder I believe it was 4.4.2. The other night I installed flash fire and attempted to flash I545_OC1_Stock_rooted_rom mdk. It flashed ok but now I'm getting the verizon warning message and I can't bypass. I can no longer boot into twrp. I think the bootloader is still unlocked, padlock is unlocked upon boot. How do I get myself out of this message?
Click to expand...
Click to collapse
Sent from my SCH-I545
SnyderGuy said:
The open padlock means the firmware you have installed is custom and not stock, doesn't mean your boot loader is unlocked. I would simply boot into download mode and re-image your device back to MDK, if that's where you were. What's your current boot loader version?
Sent from my SCH-I545
Click to expand...
Click to collapse
I am using an MDK S4.
I can bit to room, but cannot reboot to recovery.
Corrupted recovery after update via TWRP app.
How exactly, do I re-image my device back to MDK?
Do I use this stock MDK ROM? http://forum.xda-developers.com/gal...ment/rom-i545oc1-5-0-1-100-stock-mdk-t3097902
Do I put it in the BL or AP box in ODIN?
No, that is a ROM. You need the stock official software.
http://forum.xda-developers.com/showthread.php?t=2289325
SHOULD be that one...
Put that in AP
XxD34THxX said:
No, that is a ROM. You need the stock official software.
http://forum.xda-developers.com/showthread.php?t=2289325
SHOULD be that one...
Put that in AP
Click to expand...
Click to collapse
I just read it all. Looks like fun!
I sure would like to know what I did wrong. I only used the TWRP app to update TWRP.
pizza_pablo said:
I just read it all. Looks like fun!
I sure would like to know what I did wrong. I only used the TWRP app to update TWRP.
Click to expand...
Click to collapse
That I cannot answer since I do not have MDK. My assumption is a corrupted download of TWRP or a partial install that was interrupted for some reason.
XxD34THxX said:
That I cannot answer since I do not have MDK. My assumption is a corrupted download of TWRP or a partial install that was interrupted for some reason.
Click to expand...
Click to collapse
That may have been the case, since my connection was weak.
I'm just about to do the deed and I checked phone info and the bootloader is now I545VRUFNK4, vice MDK.
Here I go....
Well....I tried these to .tar files with no luck:
http://www.rwilco12.com/downloads.p...Galaxy S4 (Verizon) (SCH-I545)/Stock ROMs/TAR
https://www.androidfilehost.com/?fid=22979706399752783
I did get the "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
Now, I no longer have the option to cancel Download Mode and bot ROM.
I didn't want to do anything in Kies, for fear of taking an OTA.
Do I have any options?
Even just taking an OTA and selling a former MDK treasure?
This seems to be happening a lot. A LOT. Before you try kies, go into device manager and uninstall the Samsung USB drivers. Then download the DRIVERS ONLY from Sammobile/Samsung. THEN use Odin with a full wipe and repartition of MDK. If you get the same message again, then you have lost the MDK bootloader, and will have to repeat the process with an nc5 tar, which will loose custom ROMs, but you will have root and safestrap.
XxD34THxX said:
This seems to be happening a lot. A LOT. Before you try kies, go into device manager and uninstall the Samsung USB drivers. Then download the DRIVERS ONLY from Sammobile/Samsung. THEN use Odin with a full wipe and repartition of MDK. If you get the same message again, then you have lost the MDK bootloader, and will have to repeat the process with an nc5 tar, which will loose custom ROMs, but you will have root and safestrap.
Click to expand...
Click to collapse
OK. So I am going to uninstall Kies, just for safety sake. Uninstall the Samsung PC drivers. Reinstall the PC drivers.
Use ODIN to flash this http://www.rwilco12.com/downloads.php?dir=Files/Devices/Samsung%20Galaxy%20S4%20%28Verizon%29%20%28SCH-I545%29/Stock%20ROMs/TAR in the AP box. Sacrifice a chicken and dance with snakes.
What do you think may have caused the bootloader to change?
At this point I guess any use of the phone will be a positive and somehow retaining MDK will be a miracle.
Thanks, for your assistance, as I am at a loss, at this point!
that is a .gz, so make sure to unip it/ delete that extension so Odin can use it.
My assumption is you may have accidently flashed the entire nk4, not just one with the MDK stuff still in.
XxD34THxX said:
that is a .gz, so make sure to unip it/ delete that extension so Odin can use it.
My assumption is you may have accidently flashed the entire nk4, not just one with the MDK stuff still in.
Click to expand...
Click to collapse
I used the link file, from my last post.
After I unzip it, delete the " .gz "
Got it. Thanks, again!
XxD34THxX said:
that is a .gz, so make sure to unip it/ delete that extension so Odin can use it.
My assumption is you may have accidently flashed the entire nk4, not just one with the MDK stuff still in.
Click to expand...
Click to collapse
So I just looked at the computer file and there was no .gz extention on the file I flashed thru ODIN.
It was not zipped, either.
On the xda page that you link, there was another choice on thier link. It was titled "one click". It is an .exe, titled "SCH-I545_MDK_562219_Stock_Restore.exe" .
What could ODIN do with this?
The other file I found, that I tried, but no change, was titled "VRUAMDK_NoWipe.tar.md5" .
Do you have any other suggestions,please?
Use the Full wipe in this thread:
http://forum.xda-developers.com/showthread.php?t=2301259
If that does not fix anything you have either
A)Hard Brick(unlikely since the device is semi-working)
B) lost MDK.
XxD34THxX said:
Use the Full wipe in this thread:
http://forum.xda-developers.com/showthread.php?t=2301259
If that does not fix anything you have either
A)Hard Brick(unlikely since the device is semi-working)
B) lost MDK.
Click to expand...
Click to collapse
I used this one, the other night, with no change, but this time I will delete Kies and phone drivers, then reinstall phone drivers, before ODIN.
You're a champ!
XxD34THxX said:
Use the Full wipe in this thread:
http://forum.xda-developers.com/showthread.php?t=2301259
If that does not fix anything you have either
A)Hard Brick(unlikely since the device is semi-working)
B) lost MDK.
Click to expand...
Click to collapse
Do I remove the .md5 extension as well as the .gz and just leave the .tar on the end?
ETA: Well, I tried removing both extensions and ODIN would not take it. Received error pop up.
I tried, with no success, ODIN flashing the full wipe and no wipe tars, with no success.
Giving up for the night.
XxD34THxX said:
This seems to be happening a lot. A LOT. Before you try kies, go into device manager and uninstall the Samsung USB drivers. Then download the DRIVERS ONLY from Sammobile/Samsung. THEN use Odin with a full wipe and repartition of MDK. If you get the same message again, then you have lost the MDK bootloader, and will have to repeat the process with an nc5 tar, which will loose custom ROMs, but you will have root and safestrap.
Click to expand...
Click to collapse
I woke up in the middle of the night and something popped into my head and I couldn't get back to sleep, so here we go....
The phone was on Echoe v49 which is Lollipop and I didn't like it. So I decided to go to the last Echoe version that was KitKat, v34.
I flashed this https://www.androidfilehost.com/?fid=95747613655044521 Which apparently is T-Mobile based, and the v20 international patch.
What popped into my head was that maybe my phone was thinking it was a T-Mobile S4, because I picked the wrong kernel. At the time everything seemed to work, except sending SMS. I could make phone calls and receive SMS.
This is was got me out of bed. I went to my notes for the Aroma install, to see what kernel I chose. I recalled picking the stock kernel, which may have been T-Mobile, but my notes say that I picked KTOONES kerenel in Aroma and in the Patcher, picked ADD VZW FILES AND BUILD PROP and NO KERNEL.
I was thinking that I had put a VZW version of TWRP onto a "T-Mobile" S4, getting me stuck to bootup in Download mode only, but still able to cancel Download and boot to system. Then I ODINed the VZW MDK stock firmware and am now with either Download mode or the yellow PC connected to phone screen, with the "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I woke up thinking that maybe I had a T=mobile kernel and when I lost TWRP and only had stock recovery, downloaded the VZW version of TWRP on top of T=Mobile install. But the note makes it look like I would have been OK as far as the phone thinking it was a VZW S4.
Sorry if rambling, just trying to pass as many details and thoughts as possible.
Do I have any options, now?
I downloaded the stuff to do Heimdall One Click and was thinking about trying that route, with a file named "SCH-I545_MDK_562219_Stock_Restore.exe"
I have a 32GB MDK VZW SCH-i545 S4 that is running fine on ECHOE v29. Can I copy anything from that phone and flash in ODIN to recover the 16GB (was MDK) VZW SCH-i545 that is stuck on Download mode only?
Is there any way to flash a NANDROID via ODIN or some other program from a PC thru ODIN?
hmmm.. The Ktoonez kernal works on any s4. But if you flashed T mobile Files, which I don't think was the case since you flashed the Verizon stuff... I have never used Heimdall, so I can't comment on that. I don't know what to say. There might be a way to make a debrick image... Someone more experienced will have to help, sorry.
XxD34THxX said:
hmmm.. The Ktoonez kernal works on any s4. But if you flashed T mobile Files, which I don't think was the case since you flashed the Verizon stuff... I have never used Heimdall, so I can't comment on that. I don't know what to say. There might be a way to make a debrick image... Someone more experienced will have to help, sorry.
Click to expand...
Click to collapse
No need to apologize! You have helped all you can. I appreciate it greatly!
I just want to ensure that I exhaust ALL possibilities of recovering the MDK, before I throw in the Kies upgrade towel.
I wonder if I'll get in hot water for starting a new thread.....
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
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!