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!
Related
I'm seeing an available firmware upgrade via kies (MK7).
I'm a little skeptical to try it. Has anyone else upgraded to this firmware?
If so, have you been able to root your mega and install a custom recovery after the upgrade?
I don't want to install this firmware upgrade only to find out that afterwards that knox is on it and prevents me from rooting the phone or unlocking the bootloader.
By the way, I tried downloading the firmware without my phone connected but kies keeps force closing on me before the download is complete.
I'm afraid to connect my phone and try the download because I think it will automatically install the upgrade which I don't want to do until I'm sure I can re-root it and re-install TWRP.
Sent from my SGH-M819N using xda app-developers app
Installed Update, Re-rooted, re-installed TWRP
curgervending said:
I'm seeing an available firmware upgrade via kies (MK7).
I'm a little skeptical to try it. Has anyone else upgraded to this firmware?
If so, have you been able to root your mega and install a custom recovery after the upgrade?
I don't want to install this firmware upgrade only to find out that afterwards that knox is on it and prevents me from rooting the phone or unlocking the bootloader.
By the way, I tried downloading the firmware without my phone connected but kies keeps force closing on me before the download is complete.
I'm afraid to connect my phone and try the download because I think it will automatically install the upgrade which I don't want to do until I'm sure I can re-root it and re-install TWRP.
Sent from my SGH-M819N using xda app-developers app
Click to expand...
Click to collapse
I bit the bullet and gave it a shot. I am happy to report that the firmware upgrade was successful using Kies, I was able to root the device via the Kingo Root app, and was able to re-install TWRP. I am now on firmware M819NUVUAMK7. It is still Android version 4.2.2, and the baseband is also M819NUVUAMK7. The kernel version is dated Fri Nov 22, 2013
I installed superSU and when I ran it, it asked me if I wanted to disable knox (YES OR NO). OF COURSE I DISABLED KNOX!!
I afterward performed a nandroid backup in TWRP (the first order of business).
I am more comfortable now deleting, freezing, uninstalling system apps now because (in the event of a softbrick or bootloop) I can always revert to my nandroid backup or in extreme cases, restart all over again by re-installing the firmware via Kies, re-rooting the device via the kingo root app, and reinstalling TWRP via ODIN.
Not sure what changed from the original firmware (no change log). In any event, the device is snappy and I'm not experiencing any lags.
curgervending said:
I bit the bullet and gave it a shot. I am happy to report that the firmware upgrade was successful using Kies, I was able to root the device via the Kingo Root app, and was able to re-install TWRP. I am now on firmware M819NUVUAMK7. It is still Android version 4.2.2, and the baseband is also M819NUVUAMK7. The kernel version is dated Fri Nov 22, 2013
I installed superSU and when I ran it, it asked me if I wanted to disable knox (YES OR NO). OF COURSE I DISABLED KNOX!!
I afterward performed a nandroid backup in TWRP (the first order of business).
I am more comfortable now deleting, freezing, uninstalling system apps now because (in the event of a softbrick or bootloop) I can always revert to my nandroid backup or in extreme cases, restart all over again by re-installing the firmware via Kies, re-rooting the device via the kingo root app, and reinstalling TWRP via ODIN.
Not sure what changed from the original firmware (no change log). In any event, the device is snappy and I'm not experiencing any lags.
Click to expand...
Click to collapse
never mind I got it. I had a brain fart and was doing the process back words. I put it in download mode for the root.
hotspot mod
I am rooted with stock rom just looking for a hotspot mod for my sgh m819n been searching and searching
reesemtk60 said:
I am rooted with stock rom just looking for a hotspot mod for my sgh m819n been searching and searching
Click to expand...
Click to collapse
as far as i know. there isn't a mod for Metro's phone. there are a few custom ROM's you can use that have free tethering built in. This one is the closest to stock. http://forum.xda-developers.com/showthread.php?t=2608110
It works fine on my M819N :good:
Deodex or odex
thanks one more question how can i tell if my phone is deodex or odex
reesemtk60 said:
thanks one more question how can i tell if my phone is deodex or odex
Click to expand...
Click to collapse
well easiest way is. if its your stock ROM that came with the phone when you bought it. it is odex.
if you are rooted, you can use root explorer to go into your system/app file and see if it shows odex settings for apps
I did and had no problem rooting with kingo. What I cannot find is a way around sim lock without going through metro and that sucks.
curgervending said:
I'm seeing an available firmware upgrade via kies (MK7).
I'm a little skeptical to try it. Has anyone else upgraded to this firmware?
If so, have you been able to root your mega and install a custom recovery after the upgrade?
I don't want to install this firmware upgrade only to find out that afterwards that knox is on it and prevents me from rooting the phone or unlocking the bootloader.
By the way, I tried downloading the firmware without my phone connected but kies keeps force closing on me before the download is complete.
I'm afraid to connect my phone and try the download because I think it will automatically install the upgrade which I don't want to do until I'm sure I can re-root it and re-install TWRP.
Sent from my SGH-M819N using xda app-developers app
Click to expand...
Click to collapse
bnb25 said:
as far as i know. there isn't a mod for Metro's phone. there are a few custom ROM's you can use that have free tethering built in. This one is the closest to stock. http://forum.xda-developers.com/showthread.php?t=2608110
It works fine on my M819N :good:
Click to expand...
Click to collapse
is that rom odex of deodex because my is odex
reesemtk60 said:
is that rom odex of deodex because my is odex
Click to expand...
Click to collapse
deodex
curgervending said:
I bit the bullet and gave it a shot. I am happy to report that the firmware upgrade was successful using Kies, I was able to root the device via the Kingo Root app, and was able to re-install TWRP. I am now on firmware M819NUVUAMK7. It is still Android version 4.2.2, and the baseband is also M819NUVUAMK7. The kernel version is dated Fri Nov 22, 2013
I installed superSU and when I ran it, it asked me if I wanted to disable knox (YES OR NO). OF COURSE I DISABLED KNOX!!
I afterward performed a nandroid backup in TWRP (the first order of business).
I am more comfortable now deleting, freezing, uninstalling system apps now because (in the event of a softbrick or bootloop) I can always revert to my nandroid backup or in extreme cases, restart all over again by re-installing the firmware via Kies, re-rooting the device via the kingo root app, and reinstalling TWRP via ODIN.
Not sure what changed from the original firmware (no change log). In any event, the device is snappy and I'm not experiencing any lags.
Click to expand...
Click to collapse
Almost had a heart attack from this upgrade. My phone was already rooted when I applied the update from Kies. Everything went through fine except when it restarted, I couldn't turn on Wifi at all and I was getting an E in the cell signal. I managed to download the TWRP tar file and Kingo app to root again. I was able to restore my previous backed up image and everything was when I last left it! WHEW!
That's strange. I had no problem. wifi worked and I haven't seen E at all (only 4g lte or 4g). My signal appears to be stronger and more stable with this update than with the original firmware (most of the time I have full bars). As mentioned I don't know what changes were made (no change log around) but this is my observation so far.
Sent from my SGH-M819N using xda app-developers app
Can somebody running MK7 please boot into download mode quickly to check whether this update has a new Knox bootloader?
(Vol - , Home, Power)
Need to know if the following strings are present or not:
KNOX KERNEL LOCK:
KNOX WARRANTY VOID:
BOOTLOADER RP SWREV:
Thanks in advance.
[QUOT1.0razykipa;50763526]Can somebody running MK7 please boot into download mode quickly to check whether this update has a new Knox bootloader?
(Vol - , Home, Power)
Need to know if the following strings are present or not:
KNOX KERNEL LOCK:
KNOX WARRANTY VOID:
BOOTLOADER RP SWREV:
Thanks in advance.[/QUOTE]
This string is present on my phone in download mode:
BOOTLOADER RP SWREV: 3
I have no lines displaying anything about KNOX.
In titanium backup I froze knox 1.0, knox notification manager 1.0, and knox store 1.0.
So it appears that knox is in the rom somewhere but it's had no impact on me. I'm rooted, have twrp installed and have flashed multiple custom roms on my device (both tw and aosp based roms).
Perfect, thanks! Glad you guys got spared from the horrid new Knox bootloaders. There's a small chance that the M819 can be downgraded to the older bootloader to remove Knox entirely, but if the update came with the newest bootloader (I got stuck with it on my i527M) there is no hope at all of downgrading.
Thanks to whoever posted this and the creator of this rom
bnb25 said:
as far as i know. there isn't a mod for Metro's phone. there are a few custom ROM's you can use that have free tethering built in. This one is the closest to stock. http://forum.xda-developers.com/showthread.php?t=2608110
It works fine on my M819N :good:
Click to expand...
Click to collapse
I have the sgh-m819n metro pcs model running the mk7 firmware. This was the only rom that worked 100% for me. Im running twrp recovery,super user and free hotspot. Not to mention all the extra cool apps that it comes with. Big props to the developers of this software may your days be blessed with many more hacks.
Must be unrooted to perform update thru kies without errors..
Galaxy Mega 6.3 On Liquidsmooth rom posted this
question to everyone....
ok not sure if am in the right area to post this but. I have a metro galaxy mega 6.3 (sgh m819n) successfully rooted with kingo. what im trying to find is how to put a custom recovery like twrp and how to do it like step by step. help would be greatly appreciated. or to point me in the right direction. thanks guys.
http://forum.xda-developers.com/showthread.php?t=2608110 this is a great rom for our mega(metropcs) imho. now in order to install CWM or TWRP you simply need to download the version thats for meliusltexx which is for the i9205 version of the mega.. These Roms and procedures are compatable with the M819n(metropcs) mega
thanksss
[email protected] said:
http://forum.xda-developers.com/showthread.php?t=2608110 this is a great rom for our mega(metropcs) imho. now in order to install CWM or TWRP you simply need to download the version thats for meliusltexx which is for the i9205 version of the mega.. These Roms and procedures are compatable with the M819n(metropcs) mega
Click to expand...
Click to collapse
ok thanks and this will work correct.... also before I add a new rom on the m819n I have another question... I used to get 4LTE every where and now I get only 4G or edge after rooting with stock rom. signal apps dont do crap. is there a way to fix this... I miss my LTE data speeds. if you know how to fix or anything please point me in the right direction thanks.
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.
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!
So I was on lineage 7.1 when I decided to update TWRP for some reason . Anyway after that my phone only booted to download mode and Unauthorized software warning thingi.
So I thought hmm well I can fix this by going back all the way to VRUAMDK. So I flash VRUAMDK-No-Wipe with odin 3.07 but now get a boot loop at the verizon logo.
Followed this guide:
https://forum.xda-developers.com/showthread.php?t=2301259
My question is, does anyone have the fully stock VRUAMDK firmware? I cant find an active link anywhere. OR Should I just try flashing some available stock firmware and lose my unlocked bootloader?
Really any advice would be welcome.
Thanks!
Edit- after exhaustive searching I have found https://www.rwilco12.com/Files/Devices/Samsung Galaxy S4 (Verizon) (SCH-I545)/Stock ROMs/ with a stock rom that worked. I hope that link helps anyone out there looking for a working mdk rom.