Related
I have Note 3 Sprint, 4.3 phone was rooted, wanted to update to kitkat, said cant because device modified, used wanam mod to fake status, was then allowed to update, when restarted note 3 was still on 4.3 but not rooted. I tried to root again, when restarted after attempt root with cf-auto phone says (RECOVERY IS NOT SEANDROID ENFORCING) (Set Warranty Bit: recovery) Please Help Thanx.....
Mecdemo said:
I have Note 3 Sprint, 4.3 phone was rooted, wanted to update to kitkat, said cant because device modified, used wanam mod to fake status, was then allowed to update, when restarted note 3 was still on 4.3 but not rooted. I tried to root again, when restarted after attempt root with cf-auto phone says (RECOVERY IS NOT SEANDROID ENFORCING) (Set Warranty Bit: recovery) Please Help Thanx.....
Click to expand...
Click to collapse
I would just flash one of the 4.4 tar files via odin as opposed to hassling with getting OTA. Freeza and other's have some in the Sprint Android Development forum, just follow the instruction in the OP. If you're hellbent on getting it via OTA. I'd suggest flashing the tar for stock MJ4 (4.3) then taking the OTA that way.
Gack69 said:
I would just flash one of the 4.4 tar files via odin as opposed to hassling with getting OTA. Freeza and other's have some in the Sprint Android Development forum, just follow the instruction in the OP. If you're hellbent on getting it via OTA. I'd suggest flashing the tar for stock MJ4 (4.3) then taking the OTA that way.
Click to expand...
Click to collapse
Hey Gack69, I appreciate that, will try your method. OTA method not important just didnt no which direction to take. Thanx again
You're welcome. There are already some custom 4.4 ROMs up too. Sacs is nice and mostly stock in appearance. .. Then there's JB's KitKatKiller (K3) which is themed and modded. Depends on what your personal preference are.
Sent from my SM-N900P using Tapatalk
Yeah Odin a 4.4 tar, you can't take a Ota while being rooted even with Wanam. It will always fail or can in some cases brick your device. Odin a kitkat then root with Cf and then add your recovery just be sure you download a Kitkat recovery. After you can use any rom you wish.
My mega installed cwm and rooted fine without a problem. I got it unlocked though. it is a carrier version but the guy unlocked it before selling to me.
I try doing the same to my friend's mega who's a locked rogers carrier version and not only did cwm recovery refuse to install, root would not work, and i kept getting some yellow message at the top right called "warranty bit: kernel"
I tried flashing the stock rom via odin and did a full factory reset. wifi will not switch on..it just stays in the off position.
does this have something to do with knox? How come my mega rooted no problem and i never had these problems with my mega yet my friend's mega is basically locked out? Do I need to unlock his phone before rooting? Is this because the bootloader is locked due to the fact that it's a locked phone?
Help please
Thanks.
EDIT
I was able to flash cwm philz touch version and rooted successfully. I still get the Warranty Bit Kernel message at the top and the phone boots a lot slower than it should I also downloaded wifi fixer and it states my wifi is "stuck".
d4ndr0id said:
My mega installed cwm and rooted fine without a problem. I got it unlocked though. it is a carrier version but the guy unlocked it before selling to me.
I try doing the same to my friend's mega who's a locked rogers carrier version and not only did cwm recovery refuse to install, root would not work, and i kept getting some yellow message at the top right called "warranty bit: kernel"
I tried flashing the stock rom via odin and did a full factory reset. wifi will not switch on..it just stays in the off position.
does this have something to do with knox? How come my mega rooted no problem and i never had these problems with my mega yet my friend's mega is basically locked out? Do I need to unlock his phone before rooting? Is this because the bootloader is locked due to the fact that it's a locked phone?
Help please
Thanks.
EDIT
I was able to flash cwm philz touch version and rooted successfully. I still get the Warranty Bit Kernel message at the top and the phone boots a lot slower than it should I also downloaded wifi fixer and it states my wifi is "stuck".
Click to expand...
Click to collapse
That yellow warranty you see is because knox is present in the phone..what model is your mega.?
i have same problem. My model is mega 6.3.
i also have same problem with i9205 no wifi and gallery cannot open
starmaster10 said:
That yellow warranty you see is because knox is present in the phone..what model is your mega.?
Click to expand...
Click to collapse
It's the same sgh-i527. I figured out the problem. Newer Megas plus all future Samsung devices will come with with a permanent knox bootloader. Once the knox kernel goes 0x01, not only is your warranty void but it ****s your stock Rom up.
My first mega was a older version without the knox crap on it. Solution is to go custom Rom, I installed pacrom on my friends mega and all is working again.
We must boycott Samsung as they are taking the apple route.
Sent from my GT-I9205 using Tapatalk
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
Apologies if this has been posted, but I couldn't find it. Thanks for any help!
Before softbricking, my VZW S4 had OF1 with root (rooted while on OC1 and flashed via FlashFire to OF1).
While trying to set up new payment cards with Android Pay, I tried to temporarily uninstall Xposed framework by flashing the Xposed uninstaller with FlashFire. Android Pay apparently checks for su and Xposed and blocks addition of payment cards if present. After flashing the uninstaller, boot sticks on verizon screen.
I did not have a bootloader like safestrap present to restore backups before boot.
I do have a full backup from FlashFire stored to my SD, but I don't know how I can restore it when stuck in boot...
I'm currently downloading Stock OF1 found here http://forum.xda-developers.com/galaxy-s4-verizon/general/of1-stock-tar-t3216417
...but I expect that will take root from me, if it even works to unbrick it. Then of course, I won't be able to restore my backup via FlashFire...
Any chance I can unbrick and keep root?
Thanks!
Can you give me you number and I write with wa
im in the same boat man. Got phone back up but now kingroot cant root.
EDIT. Used this http://www.wondershare.com/mobile-p...teID=je6NUbpObpQ-lm5T20.ZhJbL1BJ3RULuew#part2 to root OC1. Try it on of1. Otherwise your only choice is to odin back to stock bloated nonroot of1 and have a functional phone. Or wait perhaps
nemisans13 said:
im in the same boat man. Got phone back up but now kingroot cant root.
EDIT. Used this http://www.wondershare.com/mobile-p...teID=je6NUbpObpQ-lm5T20.ZhJbL1BJ3RULuew#part2 to root OC1. Try it on of1. Otherwise your only choice is to odin back to stock bloated nonroot of1 and have a functional phone. Or wait perhaps
Click to expand...
Click to collapse
Nice job figuring out a solution! I gave up and flashed a downgrade oc1 to unbrick, then accepted the of1 OTA out of frustration. No more s4 root for me. A little bittersweet...
Sent from my SCH-I545 using Tapatalk
mercerudy said:
Nice job figuring out a solution! I gave up and flashed a downgrade oc1 to unbrick, then accepted the of1 OTA out of frustration. No more s4 root for me. A little bittersweet...
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Bro all u needed to do was root oc1 with my link, download root file explorer and browse to system/apps/ delete sdm.apk
That disables ota updates. Hold on i found a thread here with a oc1 downgrade tar to use with odin
Yeah, I know. I did it before you posted your solution. That tar is the one I used to unbrick. I doubt it will work now that I OTA'd.
Sent from my SCH-I545 using Tapatalk
mercerudy said:
Yeah, I know. I did it before you posted your solution. That tar is the one I used to unbrick. I doubt it will work now that I OTA'd.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Try this http://forum.xda-developers.com/showpost.php?p=62472003&postcount=65
I used a similar method to root kitkat ng6 by flashing nc1 kernel rooting and flashing back to ng6 kernal. They're actual Samsung signed kernals so odin should have no issue flashing them. Root using wondershare then flash back to OF1 kernal. Keep in mind oc1 kernal on of1 can cause your phone to run weird make sure u enable usb debug prior to putting the phone in download mode for oc1 kernal flash then root with wondershare and flash back to of1
nemisans13 said:
Try this http://forum.xda-developers.com/showpost.php?p=62472003&postcount=65
I used a similar method to root kitkat ng6 by flashing nc1 kernel rooting and flashing back to ng6 kernal. They're actual Samsung signed kernals so odin should have no issue flashing them. Root using wondershare then flash back to OF1 kernal. Keep in mind oc1 kernal on of1 can cause your phone to run weird make sure u enable usb debug prior to putting the phone in download mode for oc1 kernal flash then root with wondershare and flash back to of1
Click to expand...
Click to collapse
Ok, I may give that a try when I have some time. Will post back with the results. Thanks man!
If this worked, then it would probably help a lot of people. I haven't seen anyone go back from the OTA of1 yet.
Sent from my SCH-I545 using Tapatalk
mercerudy said:
Ok, I may give that a try when I have some time. Will post back with the results. Thanks man!
If this worked, then it would probably help a lot of people. I haven't seen anyone go back from the OTA of1 yet.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
There's no downgrading from of1 because your bootloader was flashed to of1 when u updated BUT you should SHOULD NOT WILL BE ABLE TO be able to root it with oc1 kernal and flash back to of1 kernal then proceed to flashfire of1 DeOdexed and xposed it. Don't take my word for it though do your research you could always brick and that's all on you I'm only suggesting what rocks to look under I've read of people having rooted of1 with xposed working. The kernal switch rooting is fairly new to of1 it was common on kitkat
---------- Post added at 08:33 PM ---------- Previous post was at 08:32 PM ----------
In other words you're stuck on of1 but shouldn't be a big deal if u have root and xposed working then you're better off than oc1 because of1 got some bugs fixed over oc1
I had rooted of1 with xposed before I softbricked. Rooted oc1 with kingroot then flashfired the "rooted" deodexed of1 to maintain root and xposed it. It worked but was a little buggy compared to xposed on kitkat. I think I'm just going to hold off anyway. I actually accepted the OTA as a way to futureproof me from messing with it anymore I was spending too much time tinkering.
Sent from my SCH-I545 using Tapatalk
Try this http://www.wondershare.com/mobile-ph...J3RULuew#part2 rooted my phone when nothin else would. Download mobile go and use the one click root. Ten minutes later bam! Verizon Samsung Galaxy s4 i545 oc1 rooted baby!
mercerudy said:
I had rooted of1 with xposed before I softbricked. Rooted oc1 with kingroot then flashfired the "rooted" deodexed of1 to maintain root and xposed it. It worked but was a little buggy compared to xposed on kitkat. I think I'm just going to hold off anyway. I actually accepted the OTA as a way to futureproof me from messing with it anymore I was spending too much time tinkering.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
My rooted oc1 with xposed is running flawless. Battery life is also better than before I soft bricked. Weird. Screw that. I got an s3 on jellybean rooted for backup. I still got unlimited so an unrooted phone is useless to me. I don't have home Internet I tether all day errday
So I softbricked my verizon galaxy s4 of1 bootloader using flashfire to install a rom. It's stuck on the screen with the unlock and custom sign. How did you get your phone back to normal?
Flash the OF1 tar file in Odin. Use the AP slot and make sure it's checked. http://forum.xda-developers.com/showthread.php?t=3203361 That's the tar file thread.
problem with fire flash
hi guys,i have problem with flashing via fire flash...i have of1 rom,root,su app,all what i need....i instal fire flash from google play vs 0.55.1....i set up all with fire flash,but when i push fire button,only restart my device,led blinking blue and only restarting to verizon rom...root i have from xda discussion,i flash oc1 kernel,then root with wondershare and then i flash back of1 kernel....i use flash fire 0.55.1,i search for oldest version,but any work in my phone,still fall
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!